text:
[Integration tests] Split chain backend and miner

This PR alters the integration test setup to use a chain backend separate from the miner. This is done to make it possible to switch the chain backend with a different implementation (currently we are using btcd).
The separation of chain backend and miner increases the delay of transaction and block propagation, since there is one extra node every event must be relayed through. This caused some test flakes to manifest themselves, and they are fixed one by one in the commits before splitting backend and miner.
A follow-up PR will enable bitcoind and neutrino as chain backends.
Blocked by:

[ ] btcd Node RPC: https://github.com/btcsuite/btcd/pull/1217
[x] btcd configurable trickleTimeout: https://github.com/btcsuite/btcd/pull/1222

Builds on:

[x] https://github.com/lightningnetwork/lnd/pull/1608
[x] https://github.com/lightningnetwork/lnd/pull/1613

Making P2.

The two nodes seems to hit the stall detection on INV messages sometimes, will investigate if there's something we can do about it.

The flake I was seeing seems to be related to the change from SimNet to RegTest: https://github.com/btcsuite/btcd/issues/1317
Reverted back to Simnet for now, as we don't need it before enabling the bitcoind backend.

Stall detection is still kicking in. Will see if I can make a workaround.

Added extraction of chain backend and miner logs, should make it easier to debug if the stall detection kicks in again.

To reduce the size of the PR, the actual integration test fixes are split into its own PR: https://github.com/lightningnetwork/lnd/pull/2116

All dependencies are now merged, this is ready for review again 💪


text:
doc: subscribe/cancel/lookup invoices rest

Reminds the user that the payment hash parameter must be base64url/base64 encoded when using REST (for /v2/invoices/subscribe, /v2/invoices/cancel, /v2/invoices/lookup and /v1/invoice).

Will do

Once this has an entry in the 0.15.1 release notes, it can land.

@Roasbeef Done

As someone who uses the REST API a lot and used to struggle with this, this is much appreciated. Cheers.

source: gharchive/pull-request

authors: ErikEk Roasbeef kaloudis

repo: lightningnetwork/lnd

license: MIT

license_type: permissive

license_source: github-api


text:
invoicesrpc: add a minimum of 5 hop hints

Change Description
This PR partly addresses issue #7305.
Previously: we will add up to 20 channels, or enough hints to meet the capacity target
Now: we try to add a minimum of 5 hop hints, then enough hints to meet the capacity target but not more than 20
This is more balanced default behavior until users can set the minimum amount of hop hints themselves. It keeps the invoice size small and makes invoices more reliable.
Steps to Test
Create a private invoice with enough channels.
Pull Request Checklist
Testing

[ ] Your PR passes all CI checks.
[ ] Tests covering the positive and negative (error paths) are included.
[ ] Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

[x] The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
[x] Commits follow the Ideal Git Commit Structure.
[x] Any new logging statements use an appropriate subsystem and logging level.
[x]  There is a change description in the release notes, or [skip ci] in the commit message for small changes.

📝 Please see our  Contribution Guidelines for further guidance.

Thank you for taking care of this @hotorb-code  :tada:
Instead of adding a magic numbe (15) that comes from two other implicit ones (we want at least 5 hints if we have enough peers and we currently set a maximum of 20) we should add a new constant minNumOfHopHints + a new param to sufficientHints(currentNumberOfHints). Then inside the function we can simply compare if we did not added enough hints yet before continuing with the rest of the checks.
We will also have to cover this logic in the tests

@positiveblue: review reminder

@positiveblue: review reminder

@positiveblue: review reminder

Thanks for the reviews. This is turning into a different PR so I have edited the title and description. The new approach is to add a hints flag to the addinvoice command.

@positiveblue: review reminder
@hotorb-code, remember to re-request review from reviewers when ready

What is the correct way to compile the proto files? Is there a Docker image I should use?
I'm following the readmes and have Docker and Go installed. It seems to compile and format in Docker but even the source gives me formatting errors. Here's what I do:
git clone https://github.com/lightningnetwork/lnd
cd lnd
make rpc-check
Errors with "Protos not properly formatted or not compiled with v3.4.0".

You need to run make rpc to compile them. The make rpc-check is for the CI to check that the protos were compiled.

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

Is this still under development? cc @hotorb-code

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

I'm working on this again and made some changes.
Setting hints to 0 doesn't really make sense, right now it then adds the maximum amount of hints. Is that ok or should there be a different behavior?

I'm working on this again and made some changes.

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

@positiveblue: review reminder
@yyforyongyu: review reminder

!lightninglabs-deploy mute

replaced by: https://github.com/lightningnetwork/lnd/pull/8819

authors: ellemouton guggero hotorb-code lightninglabs-deploy positiveblue yyforyongyu


text:
Add a license

Please consider adding a license to this repository. Otherwise this could pose a significant hurdle for people wishing to utilize this library for their project.

Done, thanks for your interest.

source: gharchive/issue

authors: ndarilek zaszi


text:
Is the package suited for handling .idat files?

I have tried to work with the methylsuite module, however it seems to be outdated and the results I got differed a lot from previous projects using R packages.
I would like to try CpGtools, however I couldn't find in the documentation and means to load .idat files.
Thanks

Ok, thanks!

repo: liguowang/cpgtools


text:
Make cmdline options for mill-server mode and repl more clear

We see confusion about the -i option quite a lot in Gitter channel and also advise to use -i very often when things don't work as expected.
I propose to deprecate the current -i, --interactive option in favour of two new options:

--repl - Starts a interactive mill session and will implicitly not use the mill server (same as old --interactive)
--server 0|false|off|no or --no-server - Starts mill without using a server process
--server 1|true|on|yes - Starts mill with a background server process

I'd suggest that while server-related switches are being considered, a switch to force the server to restart or to stop should be added.
There will continue to be things that are frozen at server start time or build init time (whether unintentionally or because there's simply no other choice at the moment.) Not needing to find and kill the old server by hand would be a pleasant improvement.

Looking at this a bit right now. From what I can see, the reason -i is so fundamental (has to be the first argument, etc.) comes from way back in fd8a2567ad32c11bcf8adbaca85bdba72bb4f935.
When -i isn't used, it starts MillClientMain which is Java code and starts faster and then spawns off a separate process for the server which loads up Scala. And then if you do use -i, it starts mill.MillMain which brings in the Scala libraries and is a bit slower.
MillClientMain currently doesn't interpret its arguments at all--it just shoves them all over to the server for handling.
Because of all of this it might be easiest to keep this as simple as possible, so it can be done in the launcher script without too much trouble.  So I'm going to suggest:

--repl - Starts a interactive mill session and will implicitly not use the mill server (same as old --interactive with no target), and complains if a target is given.
--no-server - Starts mill without using a server process (same as old --interactive with a target), and complains if no target is given.
--interactive - Same as the current behavior for compatibility, -i does this. Maybe have this produce a warning that its behavior will be the same as --no-server at some point in the future.

All of these arguments are very simple (presence or absence), and can be restricted to "must be the very first argument". That makes them easy to handle with the current launcher script.

I just tossed up #927 as a first pass at doing this. It does what I suggested in my last comment.

Merged right now. Thank you very much!

authors: hypatian lefou

repo: lihaoyi/mill


text:
AudioInfo has ID field ?

Let me show you my intent:
I add a song named "ABC" with ID: 123 to audioLists. Then when I pause that song in music player, the state song with same ID will change to paused as well
//audio pause handle
  onAudioPause(audioInfo) {
       const currenSong = findSong(audioInfo.ID)
       currentSong.playing = false
       setCurrentSong(currentSong)
  },

How to do that ? Thank you ! I can find the corresponding song by name but I am assuming there are same name songs

hi~ I plan tomorrow release a new version with custom fields in audioInfo

hi~ I plan tomorrow release a new version with custom fields in audioInfo
Awesome. I am looking forward it :)

AudioInfo contains the custom field for audio lists now, upgrade version 4.6.1
function onAudioPause(audioInfo) {
  console.log(audioInfo.id) // 1
  console.log(audioInfo.test) // 2
}
<ReactJkMusicPlayer audioLists={[{id:1, test: 2, ...}]}  onAudioPause={onAudioPlay}/>


text:
Performance enhancement

Currently, depCheck looks for all files under directory to get dependency result.
Some strategies can be used to optimize the performance:

First, it get packages from a part of files, compare with declaring packages.
If all declaring packages are used, stop reading files. Return everything is good. :white_check_mark:
If not all declaring packages are used, continue the step 1.
If all files are searched, but there are some declaring packaged not fulfilled, show them as unused. :x:

Concretely, it need to convert the promise queue in checkDirectory to Array<Func<Promise>> queue. The promises are triggered only then function is invoked.

Use benchmarkjs to compare the performances of different strategies.

What about using regex instead of building an AST for each file? Should be much quicker right?
I just created a package to find the require statements (including ES6 and coffeescript) in a string (https://github.com/mathieudutour/deps-regex)

I tried to implement it (https://github.com/mathieudutour/depcheck-es6/commit/1174755c4f4df87b2ad6dd71be1fd243ef238c64) but tests are failing. I'm not sure where they come from as I'm not familiar with the test suit

Hi, @mathieudutour Thanks for working on this.
Actually, build an AST is not necessary to parse a file. As said in my pluggable design, the parser has a second option - find all package dependencies, and return them as a string list. The main program will handle this case as these packages are required.
So, you can adopt your regex pattern to parse the CoffeeScript file, it should be faster than my implementation in #82. Concretely, you just implement a new parser and map some file extensions on them, as what I do in #82.

Besides, this thread is not discussing the performance about parsing a file with which method (AST, or regex pattern).
It focuses on another problem - currently, we are looking on all files in your package to get the unused packages. However, in most of the case, the developer should have all packages in use. We should stop looking on files once we find out all declaring packages are in use.

make sense

@lijunle do you have solution how to fix it

Read the thread from top to bottom, some clues have mentioned.

This issue was moved to depcheck/depcheck#43

authors: js08 lijunle mathieudutour

license: mit

license_source: bigquery


text:
Fix some error detection logic and caclulate lineup

Fixes some error detection logic surrounding skipping a batter, fixes some logic regarding getting lineup from the batter counts, creates a lineup array from the batter counts to assist in unknown batters, and adds the lineup number to the visualizer.

That's probably smart, I'll add some in the next batch of changes.

repo: lilserf/Cauldron


text:
Integrate Devise for User Authentication

This pull request is a collaborative effort between @lily4178993  and @Ayokunnumi1. The modifications aim to enhance user authentication and the visual presentation of registration and login views.
Changes Made

Removed current_user method from ApplicationController since Devise provides a similar method.

Devise Integration

Installed and set up Devise for user authentication following the Getting Started guide.

Users can now register with a valid email and password.
Authentication is implemented using a combination of email and password.
Hashed passwords are securely stored in the database.
Implemented email confirmation for user accounts.
Added functionality for users to reset their passwords.

View Modifications

Modified the registration and login views in Devise to align with the wireframes provided in the Sneak Peek.
Applied appropriate styling to match the wireframes and enhance the visual design.

Testing

Tested the registration and login functionality to ensure a seamless user experience.
Verified that password reset and email confirmation processes work as expected.

Please review the code changes and provide feedback.

Thank you, @skyv26, for dedicating time to review this pull request. Thank you for your valuable feedback!


text:
Latest NixOS update (unstable) breaks Cosmic deployment?

Since a large NixOS update some 24 hours back, I'm unable to upgrade either of the systems I have running Cosmic. Both give the same error:
nixos-rebuild switch --flake . --use-remote-sudo
building the system configuration...
error:
       … while calling the 'head' builtin

         at /nix/store/xnjw9gmfmpppdj6bxpw6cfkspc3h6xwl-source/lib/attrsets.nix:1575:11:

         1574|         || pred here (elemAt values 1) (head values) then
         1575|           head values
             |           ^
         1576|         else

       … while evaluating the attribute 'value'

         at /nix/store/xnjw9gmfmpppdj6bxpw6cfkspc3h6xwl-source/lib/modules.nix:816:9:

          815|     in warnDeprecation opt //
          816|       { value = addErrorContext "while evaluating the option `${showOption loc}':" value;
             |         ^
          817|         inherit (res.defsFinal') highestPrio;

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: attribute 'targetPlatforms' missing

       at /nix/store/xnjw9gmfmpppdj6bxpw6cfkspc3h6xwl-source/pkgs/build-support/rust/build-rust-package/default.nix:163:7:

          162|       meta.platforms or lib.platforms.all
          163|       rustc.targetPlatforms;
             |       ^
          164|   };
error: Recipe `deploy` failed on line 10 with exit code 1

Fix is already building in #418. Note that this wouldn't have been an issue for anyone using the current flake input pattern recommended in the readme: https://github.com/lilyinstarlight/nixos-cosmic/blob/a1e3c25b1d6fb0a88a5bbb61cc4bd502439a68ff/readme.md?plain=1#L18

Thanks @lilyinstarlight . Missed that flake change somehow. It's working now.

repo: lilyinstarlight/nixos-cosmic


text:
Lima VM doesn't support the existing VPN connections on host

I've integrated the lima software to my MacOS machine as described here: https://blog.carlosnunez.me/post/docker-desktop-alternative-for-mac/
The overall functionality is great, however, I've come across one big problem.
I use the Viscosity VPN  to connect to our internal network, which is required by some tools I use in the container. But when I've moved from Docker Desktop to Lima this connection stopped working inside the container.
Does Lima support this? If so, should I change some configuration in order to solve this issue?
Thank you for help :)

The same for me. I have hit the same issue. The lima looks good as a good alternative for me, but without supporting VPN it does not as I would wish for my work.
Nevertheless, good job with Lima, go ahead.
If you need some more traces, just ask, like serial.log etc.

Same issue here with rancher desktop implementation of lima. It is unable to connect use the VPN of the host.

authors: ljavorsk phracek yevon

repo: lima-vm/lima


text:
空指针问题

                                               java.lang.NullPointerException: Attempt to invoke virtual method 'int java.io.InputStream.read(byte[], int, int)' on a null object reference
                                                   at cn.droidlover.xrichtext.BaseImageLoader.readAndCloseStream(BaseImageLoader.java:77)
                                                   at cn.droidlover.xrichtext.BaseImageLoader.getBitmap(BaseImageLoader.java:47)
                                                   at cn.droidlover.xrichtext.XRichText$LocalImageGetter$1.run(XRichText.java:308)
                                                   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
                                                   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
                                                   at java.lang.Thread.run(Thread.java:818)

我们把这个用在列表中,每一项都有这个.然后快速上下滑动,反复加载刷新的过程中出错程序崩溃.但是比较难出现这个问题,某些手机上可能出现比较容易.

项目已经不维护了吗？ @limedroid

估计是不维护了啊

Same issues here... I recommend this solution: How to display HTML in TextView?

authors: VergeDX baonanhai jackycaojiaqi

repo: limedroid/XRichText


text:
Add FocusZone to other controls

Need to add FocusZone to already created components:

[x] Rating
[x] OverflowSet

Added to OverflowSet https://github.com/limefrogyank/BlazorFabric/commit/866407d826bc3d35f07dee27f8a2448e2ca82095

repo: limefrogyank/BlazorFabric


text:
Renaming newDecorator() to decorator()

I'm curious if it is a good idea to rename our static factory methods for decorator functions. They are currently named as newDecorator(). I wonder if everybody is happy with this decision which occurred long time ago.
Do you think renaming it to decorator() is a good (or bad) idea? If so, why?

Seems like people prefer newDecorator() according to my anecdotal survey from colleagues and customers.

repo: line/armeria


text:
Make HealthCheckedEndpointGroup gracefully update new endpoints

Motivation:
We have added a lot of workarounds and fixed bugs for
the race condition and timing issue for HealthCheckedEndpiontGroup.
https://github.com/line/armeria/blob/43bd08248ba86ab5942f781da33b11a42fe3b1a5/core/src/main/java/com/linecorp/armeria/client/endpoint/healthcheck/HealthCheckedEndpointGroup.java#L145-L161
However, we still got a bug report from HealthCheckedEndpointGroup.
https://github.com/line/armeria/issues/3173#issuecomment-953826146
I think another workaround could not prevent new bugs from edge cages.
We should reconsider the current design of HealthCheckedEndpointGroup
implmentation.
Design note:
If an endpoint group is added, we have to destroy the old endpoint group
after the first health check for the new endpoint group is completed.
Explicit context groups to distinguish the new endpoints with
the old endpoints should be useful to manage the lifecycle of endpoints
and health checker contexts.
For example, endpoints [1, 2, 3] are added, we can allocate them to context1.
If new endpoints [3, 4, 5] are added, they will be allocated to context2.
context1[1(checked), 2(checked), 3(checked)] -> context2[3(checked), 4(unchecked), 5(unchecked)]

Once all endpoints for context2 is checked, we can safely destroy
context1.
context1[deleted] -> context2[3(checked), 4(checked), 5(checked)]

Modifications:

Add HealthCheckContextGroup to cluster a set of endpoints set together.
Remove various workarounds in the constructor of
HealthCheckedEndpointGroup is removed.

The root causes of the workarounds are fixed by the new design.

Manage the lifecycle of an endpoint group using contextGroupChain in
HealthCheckedEndpointGroup.

A new contexts group is fully initialized, old contexts will be destroyed.

Move DefaultHealthCheckerContext to the top level.
Revamp HealthCheckStrategy .

Remove internal states from PartialHealthCheckStrategy.

PartialHealthCheckStrategy maintains its own healthy and unhealthy
endpoints that can delegate to HealthCheckedEndpointGroup.

Simplify the API and implementation.

Remove blocking operations from the constructor of HealthCheckedEndpointGroup.

Note that you should use HealthCheckedEndpointGroup.whenReady() to
wait for or the initial endpoint groups.

Result:

Fix https://github.com/line/armeria/issues/3173#issuecomment-953826146 reported by @imasahiro
Clean up HealthCheckedEndpointGroup implementation
You no longer see an EmptyEndpointGroupException when the entire
endpoints are changed in the HealthCheckedEndpointGroup

Could you check the CI?

Could you check the CI?

Oops...

Fixed by 0e956c7 (#3927)

authors: ikhoon minwoox


text:
Update dependencies

Armeria 0.55.1 -> 0.56.0
JSON unit 1.25.1 -> 1.27.0
Hibernate Validator 6.0.5 -> 6.0.7
Mockito 2.12.0 -> 2.13.0
Spring Boot 1.5.8 -> 1.5.9

Codecov Report

Merging #114 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #114      +/-   ##
==========================================
- Coverage    61.1%   61.09%   -0.02%
==========================================
  Files         254      254
  Lines        8678     8678
  Branches     1005     1005
==========================================
- Hits         5303     5302       -1
- Misses       2759     2760       +1
  Partials      616      616

Impacted Files
Coverage Δ

...erver/internal/mirror/DefaultMirroringService.java
62.02% <0%> (-1.27%)
:arrow_down:

Continue to review full report at Codecov.

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

authors: codecov-io trustin

repo: line/centraldogma


text:
Fix our publish can't get version from tag

Motivation:
Currently we don't use bot to create release, so it's easier to just use release event with github.event.release.tag_name
Modifications:

Using release event now.

Result:

Fix the failed release action

The change looks good.
FYI, the tag name could be acquired from github.ref or github.ref_name.

https://docs.github.com/en/actions/learn-github-actions/contexts#github-context
https://github.com/line/centraldogma/blob/c1e7967192f47ad384f774319c29d4a150851e6f/.github/workflows/publish-release.yml#L50-L51

authors: ikhoon kojilin

repo: line/thrift-gradle-plugin


text:
Move Automations Library into docs

Create a new automations library inside the docs.

Migrate contents of /automations into the docs site.
Update Quickstart example page to optimize it for the new library
Add automations/automation-library to site nav

Sorry about the wonky commits, I'm not sure what the deal was.

repo: linear-b/gitstream


text:
simple svg radial gradient implementation.

minor improvement for svg rendering.
before:

after:

goal

this still lacks application of the transforms the gradients can have. both linear and radial.
errors still being generated relate to the following elements:
unsupported element: ClipPath
unsupported element: Filter
unsupported element: Mask

Closing this one, because it's a subset of #1972. Let me know if I misunderstood...

authors: james-lawrence jneem

repo: linebender/druid


text:
Resume the download of same file from mirror(different) URL?

Hello,
Thanks for this great library.
I'm trying to use your library in one of my project but I'm facing an issue.
My application is going to download files from intranet networks. There are multiple intranet networks for multiple providers.
If I download a file named "FILE_1" from "URL_1" with 50% progress in "INTRANET_1" network now I moved out from the "INTRANET_1" network and after some time I moved into to "INTRANET_2" network where the same file reside with same name and length but the base ip address will be different from "INTRANET_1" network.
eg: URL for both network:
INTRANET_1: http://192.168.1.50/FILE_1.MOV
INTRANET_2: http://192.168.1.29/FILE_1.MOV
in this case resume feature will not work as the file url is different and If I try to download the same file in "INTRANET_2" it will be considered as different file and the download will start from beginning.
Am I missing any functionality of this library which can enable resume feature for same file with different urls?
Can you please guide me how can I achive this? I need to resume the download of same file but from mirror or different urls.
Thanks

The present you provide is very clear, I know what is you want.
FileDownloader didn't support your case yet because FileDownloader generates the task identify through the md5 from the path and the Url, Sorry about that.
But I will support that as soon as possible, you can follow this issue: #224

Since I join the new job these days, my free time is less than before recently, so this feature may be delayed a few weeks until the 1.4.0 has already released, hope you understand.

authors: Jacksgong vipulpurohit

repo: lingochamp/FileDownloader


text:
Feature request - Email notifier exclude topic

Hello,
Currently Burrow allow to exclude topics, which is great.
Will it be possible to exclude topics as well ?
Some topics in our prod env are not consumed all the time but we must have them in our prod group.
I think this feature could also help many other users.
Thank you

@imneo1 Seems you want to exclude some topics in the email notifier, not all in the Burrow's global?

Yes
On Aug 8, 2016 4:30 AM, "Delweng Zheng" notifications@github.com wrote:

@imneo1 https://github.com/imneo1 Seems you want to exclude some topics
in the email notifier, not all in the Burrow's global?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/linkedin/Burrow/issues/97#issuecomment-238123238, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AD_E-4Di0CgLZo2rvDFU2wlEGg0_dRq4ks5qdoasgaJpZM4JOSrR
.

Any update on this ?

authors: haim-ari imneo1 jimymodi jsvisa

repo: linkedin/Burrow


text:
Updating instructions for publishing to maven.

Making clearer the substeps, reorganizing steps, and fixed some incorrect parts.

Thanks @blee1234 . Seems there were some format changes so there are conflicts so maybe you can also fix this. otherwise looks good to me.

Thanks @blee1234 ! Adding @jainr to review here

repo: linkedin/feathr


text:
Integrate Iris & Oncall into a single UI

Technically, Iris and Oncall perform their duties quite well. We have found however that our (company) user base is always baffled by the fact that they have to log in to two different websites at times, just to get things done.
It would be immensely beneficial to the user experience, if both products were brought under a single UI.

I would chime in. While we do not use oncall, I think it would make sense to run them together, as this simplifies deployment massively.
Also right now some scripts, like iris-sync-targets, really do not work without oncall available.

authors: baryluk wleese

repo: linkedin/iris


text:
Load creation metadata from the index directory tree

Load creation metadata from the first available file in the
index directory tree (just like metadata). Added unit tests
to verify that metadata is loaded correctly from top-level
index file.

Current coverage is 64.40% (diff: 100%)

Merging #767 into master will decrease coverage by 0.05%

@@             master       #767   diff @@
==========================================
  Files           737        737
  Lines         34581      34593    +12
  Methods           0          0
  Messages          0          0
  Branches       5325       5328     +3
==========================================
- Hits          22292      22280    -12
- Misses        10728      10754    +26
+ Partials       1561       1559     -2

Powered by Codecov. Last update 670d77d...08cfd56

authors: antumbde codecov-io

repo: linkedin/pinot


text:
Add "dcat:temporalResolution" to dataset

Add support for dcat:temporalResolution to Dataset.
This includes validation of xsd:duration and corresponding help texts explaining, how to construct valid value. For validation, see this stackoverflow post.

 Druhá várka vylepšení formulářů směrem k DCAT-AP 2.0.0

https://github.com/SEMICeu/DCAT-AP/issues/76

Fix typos, add a few (3) specific examples.

In the output JSON-LD, the value is missing the xsd:duration datatype (https://w3c.github.io/dxwg/dcat/#Property:dataset_temporal_resolution)
 "http://www.w3.org/ns/dcat#temporalResolution": {
    "@value": "P1D"
  }

 Pracovat na issues k DCAT-AP-Forms ohledně DCAT2

This is still incorrect:
 "http://www.w3.org/ns/dcat#temporalResolution": {
    "@literal": "P1D",
    "@datatype": "xsd:duration"
  },

The correct form should be:
"http://www.w3.org/ns/dcat#temporalResolution": {
    "@literal": "P1D",
    "@type": "http://www.w3.org/2001/XMLSchema#duration"
  },

we do not use a context here, so we cannot use prefixes.

repo: linkedpipes/dcat-ap-forms


text:
fix: [PDI-3057] - Users unable to upgrade Kubernetes version from landing page

Description 📝

Fixes a bug 🐛 preventing users from upgrading their Kubernetes cluster from the Kubernetes landing page ⬆
I believe the bug was caused by https://github.com/linode/manager/pull/10756

Specifically switching isLoading ➡ isFetching - see comment for explanation

Adds Cypress test that would have caught this bug 🧪

(the test uses mocked API data)

Preview 📷

Before
After

How to test 🧪
Reproduction steps

Spin up a Kubernetes cluster that is not on the latest version
Attempt the upgrade flow on the Kubernetes landing page
Observe that when clicking "Upgrade Version", the dialog will not proceed to step 2

Verification steps

Spin up a Kubernetes cluster that is not on the latest version
Test the upgrade flow on the Kubernetes landing page
Verify you see step 1 and step 2

As an Author I have considered 🤔

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

The recent test addition was failing on my end when I ran it locally, but I saw it passed in this run here (and then I tried rerunning the tests but received a couple errors - not sure if I'm missing permissions or something?). Will look into some more!

authors: bnussman-akamai coliu-akamai

repo: linode/manager


text:
M3 1692 test linoderow clickable tags

Added a test for M3-1657 and an additional flag for logLevel. To verify the test run and logLevel flag run:
yarn e2e --file e2e/specs/linodes/smoke-linodes.spec.js --logLevel (silent | verbose | command | data | result | error)

Coverage remained the same at 27.198% when pulling ea837a315af3c7f4b16f53448bfa709062bf16c6 on nwisnewski:M3-1692-test-linoderow-clickable-tags into f4d6ed2c4ae7069529542f19b05bf5569fadfdc0 on linode:develop.

authors: coveralls nwisnewski


text:
M3 6045: Add modal content, tabs and validation check

Description 📝
Show the API awareness modal after validation check passes.
What does this PR do?

Adds content and respective links to the API awareness modal.
Adds Tabs component.
Add installation guides.
Wired GA events
Validation check to show / hide modal

Preview 📷

How to test 🧪

Navigate to Create Linode page
Click on "Create using command line" button - Try with out filling required data.
Should show the inline error messages.
Enter data for all required fields.
Click on "Create using command line"
Show show the API awareness modal.
Validate all the links.

How do I run relevant unit or e2e tests?
yarn test

Can we make the dialog height smaller/scrollable so it doesn't take up the whole screen?

I believe this is our standard practice for dialogs (the Resize, Rescue, Migrate, etc. dialogs are all full size)

The functionality is mostly in place and the UI mostly matches the mockups but I noticed a few things while testing:

The Check out our collection of integrations ... notice appears to be bold in the mockups
Can we some top padding to create more space between the "cURL" / "Linode CLI" tabbed section and the modal instruction text above it? (per the mockups)
Right now it seems that we're unable to use keyboard navigation to switch between the "cURL" and "Linode CLI" tabs
If you fill in all the required fields and open the modal, but then close the modal and clear out one or more of the required fields, you're able to still click "Create Using Command Line" and successfully open the modal.

Great feedback @dwiley-akamai @hana-linode Addressed above feedback and PR is ready for review.

As we got some design changes and specs, bottom notice content will be part of it. We have story(6606) to cover that along with other language changes.

Added styes ( for spacing) as suggested by Andrew.

As I was able to navigate thru tabs. I think we are using common component for Tabs. If you still have issues, lmk, we can pair on that. (Attached screen recording for reference)

As we discussed, Image field is not required to create Linode. So we are covered for the fourth point.

Reduced model height

https://user-images.githubusercontent.com/119517080/212423555-fd14a7c5-5e72-44a1-8cda-c269b576fb8c.mov

Leaving some comments on copy, spacing, and linkage, then I realized that you may already plan on addressing these in a follow up ticket (M3-6067), but I wasn't certain.
I also noticed the Linode plan selection table is defaulting the Shared CPU rather than Default CPU for the plan type and we'll want to make sure this is rebased on develop given the bugfix last week.

@mjac0bs Once it is merged to feature branch api-cli, we can rebase the feature branch.

Great feedback @bnussman-akamai @carrillo-erik @dwiley-akamai @mjac0bs.

authors: cpathipa dwiley-akamai


text:
32-bit support?

Can Linorobot 2 and ROS 2 be installed on a 32 bit ARM like raspberry PI2 or orange PI?
Thank you

I think it’s technically possible. However I haven’t personally tried running Nav2 on pi2 so can’t comment much on the performance

you can check out the hardware repo here https://github.com/linorobot/linorobot2_hardware

closing this for now. feel free to open if needed. Thanks

authors: grassjelly tbop-R


text:
泛型上界问题

但是生成的代码报错，如下

但是我用set编译器就不会报错

这个是mapstruct处理集合默认策略的问题。
MapStruct 提供的解决方案是在 Mapper 注解中，配置  collectionMappingStrategy = CollectionMappingStrategy.TARGET_IMMUTABLE。
但 MapStructPlus 的 AutoMapper 注解暂时没有增加该配置项。
可以通过如下方式临时解决：
自定义两个转换接口：

LoginUserToLoginUserVOMapper 继承自 BaseMapper<LoginUser, LoginUserVO>，增加 Mapper 注解，及配置项：collectionMappingStrategy
同理增加 LoingUserVOToLoginUserMapper

这样子可以临时解决该问题，下个版本增加 collectionMappingStrategy 配置项

增加自定义转换接口后，LoginUser 和 LoginUserVO 的 AutoMapper 注解需要去掉

authors: linpeilie wzkris

repo: linpeilie/mapstruct-plus


text:
Gpu jobs (aws) failing due to permissions

Description
When running tasks on the cpu instance an error that includes you are not authorized to perform this operation. us thrown
Steps to Reproduce
Create CF stack and run rastervision against the stack
Actual Behaviour
bellow error
 INVALID - CLIENT_ERROR - You are not authorized to perform this operation. Encoded authorization failure message: sp6uRxBgkIvW1GGZ7hbmPzDABzdc25dC24vnfaroVZWIjhvA1Z1di5g8z-_czeGIZJTr9-wcyNIYE0wSoHGgDU670O1k6bfifZxhbSnhuJO2lIuf0vRKgq38l6PVPBzcbeIzSxBzIBSdlnZkuNxalM5FZWy8x1bkUFBesmmxqMEHxqTzLvE72iCO4W2mlAuYFzTfif9-KkYBXkb15ZduIUWyoOc4nxh_Md6pGFuXPMYbYgO3DmvnoKaujN7RFQcbPeTSQgwO6Qw8b6k3Po5k-Ewt-gOPgawtLEM3hmNf3KbUCFk-JutqW5XcLZRuSyDdV9Bq7gJPZC8s6sMAGE0Eb_IGMYLhEw2Cy8YNc5hh5XYFqsONR4bveV6STcBdyi7ucaAs5JAzgOdaZL1HsoHA_JMggwGO1bRZYHQ18sg__QGsUbhc4SZp3wtgabfLG4IFgYaUBX8w761ylB3Q4ZZYJHfD8FuwFKW8H8jpRFRgqXriqHWYJciCUd4g3fgDi2H56Bhmk8-HES_E_YIod6e7AGaa3YmH4Bq-zxYFlcQFU_TcO4_qTMMPUEgUF6irnIz71WnzuknS1XTSvBZ7B7nAe7P68_ulBOKtvvUOSY_-U52DbcaMd6uGkjRiqq9dp9ax-T8PhWbEC5LKC-vYqr4NpgT4CuntxyoWwE4TyHCxEQyyTqjKchuKet8RloL8khP1l8oC-Yf4Fq1cn68CHxAGqHqWZcJdgv52VDj_Ia1bhHbJvs5U7NZQBk-J2CWF92DKk_6W0sJGdhuen_8RnVQwnf_bb3Ld7klmMKCbctKg8kjXLWCiDRHmJ1fEH6iOBJi2TYVVRs7iN2B6DPF_AkVGscjiw6GZ6Jql0pYswyVMIGaqyfIicCj417-CXSxZteAbm7KydKFFBUuki0_J0cyfvlThfhtEHoJZzW9CJhry43gBf_Job_a3oI6uFqXFBdnduWdRUoXF6dNy-l_G5Sms7EzxzDLI77q1-AV1KvWfmt_D6bAnJpbVQjO9OAhhm9Jg_qMwWffM7HjjSN9VyxY5-nn5UDgy_MPFc6Be0rM6fqhaGtF-uBRCJ-OIldXxn9bhxMOPiWv9NRaf45cgJRWO-K-QRPN4ZHjkThBT4N5bagzFhuRR2_8PaK384G5ZNXy-k4DU5TAkevcbeQP2L-_7OXi34-Vi1i7ipr4fpB7DiH5rH1VjVPdnDEpKhrRjQ_B4v20Eby-Wu1evSpxjW2ZZehATGIL9-fo48diMIiUdtXhOHp6W9IRKufIn1Ypuow24uzpcJdoQY3E80zMy61xGEFC_czK3zKFh0YM_At3DDT_0jwRCDYhclGBFPin1x_oQAaUFnZBZ-7NO3zGV4ywEiWEmSx74mWhXQ1h1Y8UvTGrhnTWeFWZL9j1GzM8jjX7BOypFFWk7C0dRD4RKMnWwiy26xuI9Pa-M4HEU05couiw0rTK_upWDfWw

Expected Behaviour
CPU process to be executed without error
System
aws batch via rastervison CF template
Screenshots

Additional Context

migrating CF to CDK solved this

repo: linz/building-detection


text:
Variable passthrough broken

Hey there,
I assume that something isn't working after you redid the Docker file. I had to update the container yesterday and there seems to be something wrong with the pass through of the variables.

indeed, sorry about that, poor cache testing from my end, let me know if 2.0.2 solves it

Seems to work now. Thanks for the quick fix.

Ok, update. There's no output. The logs say it's writing a file, but it doesn't show up. I set the output folder to several different local and SMB directories to rule out permission issues on my side, but it wont write to any of them. Are you able to reproduce that?

so far I dont reproduce it, if I startup the container without mounting up any volume it writes down the file in a download folder within the container, are you using docker desktop? if yes, on macOS something similar happen to me when I ran vistiofs

here is a sample of it running in a code spaces environment, be mindful if you use the docker compose container, that the userid must have privileges to write to the output

found it, should be fixed now, sorry about that...

is this fixed for you too?

authors: liofal too-many-bees

repo: liofal/streamlink


text:
How can i play device local video.

How can i play device local video.

see Demo，

It's not working. My requirement is i have video URI and i want to play video form uri. How can i do this

this function url is object,  you can put uri

I am talking about android Uri Object not string url.
When i select video from gallery or record video from camera it return android Uri object so how can i play video from android Uri.

LinkedHashMap map = new LinkedHashMap();
map.put("URL_KEY_DEFAULT", uri);
Object[] dataSourceObjects = new Object[1];
dataSourceObjects[0] = map;
          mJzVideoPlayerStandard.setUp(dataSourceObjects,0
                        , JZVideoPlayer.SCREEN_WINDOW_NORMAL, "");

use the uri in android.media.MediaPlayer check if play

I have done this thank for reply.

repo: lipangit/JiaoZiVideoPlayer


text:
When pause start or quit fullscreen no image

Can we start play video when start fullscreen when the video pause
在暂停视频切换全屏的时候没有图像，大家觉得可不可以这时候直接自动播放

最新的develop分支已经完善了这个图像问题。

authors: flztsj lipangit

repo: lipangit/JieCaoVideoPlayer


text:
Request for functionality: get response with selected subprotocol

Hi!
Another one problem: if websocket client send multiple ws subprotocols, then server can choose one, and answer with corresponding header. On client side we should have a possibility to know that answer. Cause application logic may rely on that.

agree. we can add a second return value to connect
local ok,protocol = ws:connect('ws://foo.bar', {'proto1','proto2'})

May be client/server also can get all headers from handshake?

ok, so you suggest:
local ok,headers = ws:connect(...)

or
local ok,protocol,headers = ws:connect(...)

i am ok with both options

I suggest ok,protocol,headers.
Also may be allows client/server add some headers manually. But I do not know for what it may be needed.

ok, great.
regarding specifying header when connecting: i dont like to add functionality without somebody nedding it, though. every feature has to be tested and maintained, espacially if they are seldom or rather never used.

Hi guys! I vote for local ok,protocol,headers = ws:connect(...)
That would be enough.

Hi, guys! On this weekend i decided to implement this feature. But i was a bit confused: in client_ev we can not simply return headers, 'cause things are async. So i extended response form on_open function — now it returns websocket object, server selected protocol and all response headers.
For sync client — all return points in connect function are extended appropriately.

there is a new PR #73

authors: KSDaemon lipp moteus

repo: lipp/lua-websockets


text:
AllowList-based and DenyList-based Resource Reflection

Description
Fixes #1855
How Has This Been Tested?

[x] locally (Kind)
[x] unit tests
[ ] e2e tests

One of the most useful feature for us. Looking forward to test it out. Thanks

/hold

/test

/test

/test

/unhold

repo: liqotech/liqo


text:
crdReplicator finalizer on foreigncluster resources

Description
Each time a foreigncluster.discovery.liqo.io resource is created the crdReplicator creates a dynamic client to the remote api-server. A finalizer is added to the foreigncluster resources in order to close the connection to the remote api-servers when the resource is deleted.
Using two kind clusters:

peering then unpeering and then peering again the cluster.
deleting the foreigcluster resource and checking that the crdReplicator removes the connection and then recreates the client to the remote api-server once the foreigncluster resource is recreated.

/rebase

/rebase

/rebase

/rebase

/merge

/merge


text:
Improve use of generics in code

Impact

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

Description
<!--
Avoid generic classes with omitted type parameters.  Such raw use of generic types is valid in Java, but it defeats the purpose of type parameters and may mask bugs.

Initial/Pre-Review Thoughts
Thanks! More generics are always good. We will need to make sure to watch the API compatibility in the full review.
I don't remember the details on what impact this can have on compatibity, though. To some degree, java does generic type erasure so maybe it doesn't survive compilation to cause a problem? But it also seems like it maybe does?
If it does get saved enough to impact people using liquibase as a library, we'll need to make sure the types are correct and not too narrow or to wide. It looked like it was mainly on variables and not methods which are also probably less API-impacting and so less of a worry?

Approved.
Review and testing results:
Based on my knowledge and understanding about generics this looks ok to me, but I would appreciate if you @filipelautert can also look at this quickly to this. We have already discuss about some points (same with @nvoxland). I haven't notice any API compatibility issue/risk, but I think a second quick look would be nice.
Again, thank you @arturobernalg for another contribution.
Things to be aware of:

None

Things to worry about:

None

In Java, both new ArrayList() and new ArrayList<>() create a new instance of the ArrayList class. However, there is a subtle difference between the two.
new ArrayList() is known as the raw type, while new ArrayList<>() is known as the diamond operator. The diamond operator was introduced in Java 7 to make it easier to declare generic types.
When using the diamond operator, the compiler can infer the type of the ArrayList based on the type of the variable it is assigned to. This can make code easier to read and less error-prone.
Additionally, using the diamond operator can help prevent type mismatch errors at compile time, as the compiler can ensure that the type of the ArrayList matches the type of the variable it is being assigned to.
Therefore, the benefit of changing new ArrayList() to new ArrayList<>() is that it makes the code more concise, easier to read, and less prone to type mismatch errors.

@MalloD12 can you fix the conflicts for this pr so we can merge it? thanks!

authors: arturobernalg filipelautert nvoxland

repo: liquibase/liquibase


text:
fix: update supported node versions

Update supported Node.js versions to LTS

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: lirantal/create-node-lib


text:
Better management of output filenames and previous run directories

While programming the diff utility, I realized I wanted access to the Pipeline's knowledge of its
output filenames, so the diff utility knows which files to compare in which order.
Working on making that available led to a whole bunch of related improvements:

moved the logic that decides on filenames to class methods which can be overridden easily when developers subclass Pipeline and want to change the names of things
Picked the name for the "prev run dir" based on the timestamp of the PREVIOUS run, not the current timestamp!
Moved the logic that moves old run files in to the previous run dir into one place - previously I had hacked it into several different places
Removed the logic that added incremental number to phase names for saving - this just wasn't needed any more because phases have their own logic to pick a name from the class name if not set otherwise
Added safety checking to make sure that none of the files are going to overwrite each other - while at it, also checked that the developer hadn't saved the source file into the output directory with a name that would collide (or more likely, that the developer would enter a name of a previous output file into the pipeline as input)

I like this all better overall; with the previous arrangement of logic we had choosing the run dir name in a different place than creating it, as well as moving old files to prev run dir in too many places.

This PR looks great.  I like the refactorings.

authors: jeffkole lisad

repo: lisad/phaser


text:
WorkflowService interface leaks internal WorkflowService.replace function

The WorkflowService interface declares a .replace function which is used internally whenever a workflow should be replaced.
It is

leaking internal functionality
poorly documented
poorly named
possibly missing the deletion/cancellation of scheduled jobs

It should therefore be refactored.

Best would be to deprecate the interface method and remove it in an upcoming version.

@bobmazy Can you remember why this function has been added?
Currently the difference between delete and replace is, that replace doesn't:

load the workflow to be deleted
delete jobs
publish the WorkflowDeletedEvent

I understand why one wouldn't want to publish the event. But do you know why jobs are not deleted?
    override fun delete(identifierToDelete: WorkflowIdentifier) {
        val workflowToDelete = persistence.find(identifierToDelete)
            ?: throw WorkflowNotFoundException(identifierToDelete)

        persistence.delete(identifierToDelete)
        stepService.deleteAllForWorkflow(identifierToDelete)
        jobService.deleteAllForWorkflow(identifierToDelete)

        eventService.publish(
            WorkflowDeletedEvent(
                WorkflowImpl<Any>(workflowToDelete)
            )
        )
    }

    override fun replace(identifierToDelete: WorkflowIdentifier) {
        persistence.delete(identifierToDelete)
        stepService.deleteAllForWorkflow(identifierToDelete)
    }

@masinger
We had to dynamically adjust the type of the workflow model, which previously could only be done by starting a new workflow and deleting the current one. This also resulted in a new workflow identifier being assigned, which we did not want.
Therefore, we added the replace method to keep the workflow identifier and be able to change the type of the workflow model.

@masinger
We had to dynamically adjust the type of the workflow model, which previously could only be done by starting a new workflow and deleting the current one. This also resulted in a new workflow identifier being assigned, which we did not want.
Therefore, we added the replace method to keep the workflow identifier and be able to change the type of the workflow model.

Yeah, I know about the reason/need for the "replace functionality". But I am wondering why the implementation would need a dedicated Workflow.replace functionality, which deletes everything (like Workflow.remove) except jobs?

authors: bobmazy masinger

repo: lisegmbh/fluxflow


text:
improving readability

Proposed changes
Currently when providing a name via the UI for a new scenario, if the end user uses a name that has an uppercase letter they are presented with this error message:
Chaos Scenario name can only contain - and alphanumeric characters

This change updates the English text to be more clear to the end user.
Types of changes
What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

[ ] New feature (non-breaking change which adds functionality)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x ] Documentation Update (if none of the other choices applies)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ x] I have read the CONTRIBUTING doc
[ x] I have signed the commit for DCO to be passed.
[ x] Lint and unit tests pass locally with my changes
[ x] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x ] I have added necessary documentation (if appropriate)

Dependency

None

Special notes for your reviewer:
This is only an error message update to make the message more helpful for the end user.

no longer care

repo: litmuschaos/litmus


text:
Clothing Encoder?

Which model do you use as the clothing encoder?

follow the  IDM-VTON，we use ip-adapter and garment unet as the clothing encoder

follow the IDM-VTON，we use ip-adapter and garment unet as the clothing encoder

ok, got it, thx

authors: Dorniwang little-misfit

repo: little-misfit/BooW-VTON


text:
itchat.send是否还能发送消息

在提交前，请确保您已经检查了以下内容!

[ ] 您可以在浏览器中登陆微信账号，但不能使用itchat登陆
[√ ] 我已经阅读并按文档 中的指引进行了操作
[ ] 您的问题没有在issues报告，否则请在原有issue下报告
[ ] 本问题确实关于itchat, 而不是其他项目.
[ ] 如果你的问题关于稳定性，建议尝试对网络稳定性要求极低的itchatmp项目

请使用itchat.run(debug=True)运行，并将输出粘贴在下面:
[在这里粘贴完整日志]

您的itchat版本为：[1.3.10]。（可通过python -c "import itchat;print(itchat.__version__)"获取）
两个问题请帮忙解答下，多谢
1，请问itchat.send()中toUsername该使用哪个参数，username、nickname、remarkname均不能给好友发送消息
2，search_friends()函数中使用nickname，remarkname返回的列表都是空的

找到问题了  ，这个readme要更新了，py2版本在查找和发送过程中中文要写成 u'中文'

repo: littlecodersh/ItChat


text:
Fix remaining instances of LV_HOR_RES/LV_VER_RES in drawing code.

Based on #957. Thanks to @manison for reporting this.

(cc @kisvegabor)

Great! Thank you!

authors: embeddedt kisvegabor

repo: littlevgl/lvgl


text:
Better Dwolla account handling

This PR separates the dwolla account info off into a separate model, which is only referenced by orders, people, and orgs. This allows for centralized updates of access tokens related to a particular account, and prevents a bug whereby attaching both your org and your account to the same dwolla account results in access token invalidation. (See #714, which this PR resolves.)
This PR transfers dwolla account info for organizations over to the new model, but encourages them to update as soon as possible. (Though that isn't, strictly speaking, necessary... the access tokens would be properly updated and re-scoped the next time they attach their user account or an order. Maybe we just shouldn't say anything?)
This PR doesn't remove the old dwolla fields from the respective models, but it does remove them from the admin. If these changes are successful, a followup PR should remove the old fields and the data stored in them.

This generally looks good, though the VCR-enabled test would only pass if I removed the ../ from the beginning of the path. I went through the reauthorization flow and everything seemed to check out for the testing dwolla account.
Maybe others want to weigh in on whether to display the message?

I think that in the light of day, it just doesn't make sense to ask them to re-authorize. The old tokens do everything orgs need, and as soon as someone authorizes for their personal account (or another org, or whatever) the scope will be expanded automatically.

authors: chigby melinath

repo: littleweaver/django-brambling


text:
:+1: Improve documentation

Add more detailed description of NeoVim related g:clap_enable_background_shadow.
It's mentioned to #670.

Merged, thank you!

authors: gniw liuchengxu

repo: liuchengxu/vim-clap


text:
Newer version of samtools works?

Hi,
I have already deployed samtools and htslib ( both version 1.14 ) on my Ubuntu 18.04, how could i make binaries using that version of samtools instead of 0.1.19 provided from TRUST4 repo since samtools v0.1.19 was released 8 years ago? I have found some legacy APIs ( e.g. samopen() ,samclose() ) in 'alignments.hpp' is deprecated in samtools v1.14, so i wonder what i should do next?
Best

Though v0.1.19 is relatively old, we do not use all the complicated functions in htslib. So I stick with the older version for its lightweight. If the API does not exist anymore, then it will some effort to change the alignment.h file.
Is there any reason you don't want to use the 0.1.19 to compile? If you only need to process fastq files, you can remove the bam-extractor from the makefile, so there is no need to use samtools library.

authors: MingwuDuan mourisl


repo: livekit/egress


text:
added events for parameter changes

What does this pull request do? Explain your changes. (required)

added events to be emitted when the dependencies change via setters.
Specific updates (required)

check history

How did you test each of these updates (required)

Updated tests to check for these emitted events.
Does this pull request close any open issues?

Checklist:

[x] README and other documentation updated
[x] All tests using yarn test pass

Pull Request Test Coverage Report for Build 1778659195

8 of 8 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1778426589:
0.0%

Covered Lines:
258

Relevant Lines:
258

💛  - Coveralls

authors: coveralls kautukkundan

repo: livepeer/arbitrum-lpt-bridge


text:
Usage API endpoint and admin page

What does this pull request do? Explain your changes. (required)
/user/usage endpoint - returns usage data for the user in the specified time interval

Specific updates (required)

-

How did you test each of these updates (required)

Does this pull request close any open issues?
Fixes #78
Screenshots (optional):

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.

The Usage page UI is helpful for reviewing what is available with the endpoint, but @adamsoffer will create a differently designed one based on the user's billing cycle dates. @adamsoffer your call if you want to keep the UI in the PR.
This is super helpful, @darkdarkdragon, thanks!

Thanks Ivan great thanks @darkdarkdragon !
@wohlner I see the UI introduced in this PR is for the admin page; it doesn't interfere with the usage page I already implemented which is user facing and would be a nice internal tool for us to look up a user's usage for a given time period so I'm inclined to keep it.

@adamsoffer fixed

authors: adamsoffer darkdarkdragon wohlner

repo: livepeer/livepeer-com


text:
-nooption

Note: the -nooption syntax cannot be used for boolean AVOptions, use -option 0/-option 1.

https://ffmpeg.org/ffmpeg.html#Stream-specifiers-1

Options which do not take arguments are boolean options, and set the corresponding value to true. They can be set to false by prefixing the option name with "no". For example using "-nofoo" will set the boolean option with name "foo" to false.

Note: the -nooption syntax cannot be used for boolean AVOptions, use -option 0/-option 1.

When used as an input option (before -i), seeks in this input file to position. Note that in most formats it is not possible to seek exactly, so ffmpeg will seek to the closest seek point before position. When transcoding and -accurate_seek is enabled (the default), this extra segment between the seek point and position will be decoded and discarded. When doing stream copy or when -noaccurate_seek is used, it will be preserved.

-stats (global)
Print encoding progress/statistics. It is on by default, to explicitly disable it you need to specify -nostats.

-stdin
Enable interaction on standard input. On by default unless standard input is used as an input. To explicitly disable interaction you need to specify -nostdin.

Disabling interaction on standard input is useful, for example, if ffmpeg is in the background process group. Roughly the same result can be achieved with ffmpeg ... < /dev/null but it requires a shell.

-auto_conversion_filters (global)
Enable automatically inserting format conversion filters in all filter graphs, including those defined by -vf, -af, -filter_complex and -lavfi. If filter format negotiation requires a conversion, the initialization of the filters will fail. Conversions can still be performed by inserting the relevant conversion filter (scale, aresample) in the graph. On by default, to explicitly disable it you need to specify -noauto_conversion_filters.

-autorotate
Automatically rotate the video according to file metadata. Enabled by default, use -noautorotate to disable it.
-autoscale
Automatically scale the video according to the resolution of first frame. Enabled by default, use -noautoscale to disable it. When autoscale is disabled, all output frames of filter graph might not be in the same resolution and may be inadequate for some encoder/muxer. Therefore, it is not recommended to disable it unless you really know what you are doing. Disable autoscale at your own risk.

repo: livingbio/typed-ffmpeg


text:
Add Support for RedisGraph

RedisGraph supports Cypher

how can we test this?

authors: bionicles gkorland

repo: livioribeiro/rusted-cypher


text:
visualize more than 10 motifs

how can I visualize more than 10 motifs from MEME?
thanks for your useful package.

Hey, the sample code below can visualize all the motifs from MEME:
filepath <- system.file("examples", "meme.txt", package = "ggmotif")
motif.info <- getMotifFromMEME(data = filepath, format = "txt")
show all motif
plot.list <- NULL
for (i in unique(motif.info$motif.num)) {
motif.info %>%
dplyr::select(2, 4) %>%
dplyr::filter(motif.num == i) %>%
dplyr::select(2) %>%
ggseqlogo::ggseqlogo() +
labs(title = i) +
theme_bw() -> plot.list[[i]]
}
cowplot::plot_grid(plotlist = plot.list, ncol = 2)

it's really helpful. Thanks


text:
Could you please tell me the detail that how do you produce HM compressed images?

I use ffmpeg to convert a png image to yuv, and then I use this command to convert it to hevc formmat:
subprocess.run([
'x265',
f'--input-res={width}x{height}',  # 指定输入分辨率
f'--fps={fps}',                   # 指定帧率
'--input',yuv_path,
'--qp','32',
'-o', compressed_path
], check=True)
and then I convert the hevc back to yuv formmat with this command:
subprocess.run([
'ffmpeg',
'-f', 'hevc',                      # 指定输入格式为 HEVC
'-i', compressed_path,                # 输入 HEVC 文件
'-pix_fmt', 'yuv420p',            # 指定输出像素格式
'-s', f'{width}x{height}',        # 指定输出分辨率
decompressed_path                         # 输出 YUV 文件
], check=True)
I set the param qp to be 32. However, I calculate the psnr between ground truth yuv and  compressed yuv, the value is very high. The average psnr of Set14 is up to 37, I only use y channel to calculate psnr. I think may be there is something wrong with my compression? In your paper, even after processed by the model, the psnr is sitll lower than 30. I wonder how do you produce HM compressed images(yuv)?

Sorry for the late response, we utilize standard codec HM reference such as HM16.19

authors: Qinluyi lixinustc

repo: lixinustc/UCIP


text:
Type hinting

I have started to use mypy. Aaaand it is not so good right now.
Libraries lack typing support. And I know that mimesis support only python3.
Do you consider adding type hints?
There are some advantages:

stricter API
static analysis support to improve quality

There are some disadvantages:

type hinting was introduced in python3.5, so any version prior to that will have to use special comments or other hacks
a lot of manual work
possible API changes

Do you mean annotations?
Something like this:
def function(num: int) -> float:
    pass

Right?

Yes.

I thinks that we can add annotations. What about Python 3.4?

Seems like annotations was added in Python 3.0. And we we lose nothing.

https://www.python.org/dev/peps/pep-0484/

@sobolevn Soooo... What shall we do? Refusing to support Python 3.4 doesn't seem to be a good idea.

It actually is in some cases. Since upgrading from 3.4 to 3.5 is painless in 90% of situations.

@sobolevn Let's do this!

Please, note that variable annotations is not supported in 3.5. https://stackoverflow.com/questions/39971929/what-are-variable-annotations-in-python-3-6/39973133#39973133

@sobolevn I will add annotations for functions and methods. Can i hope for your help with situations which confuse me?

Example:
    def randints(self, amount: int = None, a: int = 1, b: int = 100) -> list:
        """Generate list of random integers.

        :param amount: Amount of elements.
        :param a: Minimum value of range.
        :param b: Maximum value of range.
        :return: List of random integers.
        """

        if not amount:
            amount = 3

        return [self.randint(a, b)
                for _ in range(amount)]

Is it right amout: int = None. I mean Is it should be integer default value?

@sobolevn How to be if the function returns multiple types using? Should we use typing module?

Yet another example which illustrate syntax:
from typing import Callable, Union

def type_to(new_type: Callable[Union[tuple, list],
                               Union[tuple, list]], check_len=False):
    def inner(func):
        @functools.wraps(func)
        def wrapper(*args, **kwargs):
            result = func(*args, **kwargs)
            result = new_type(result)

            if check_len and len(result) == 1:
                return result[0]
            return result

        return wrapper

    return inner

Is it okay?

In regular python without types I would say that None is perfectly fine.
But in this particular situation it is possible to change amount=None to amount: int = 3. That what it does anyway, doesn't it?

@sobolevn Problem is in standard python library. json module returns both list and dict.

So, seems like i have found a solution.

With the provided solution there are a lot of uncovered cases, which are valid json:

[1, [], {}, "z"]
1 and "a"

@lk-geimfari I've already mentioned this in #267, but if one is defaulting the argument to None, which is automatically pushed to type(None) or NoneType, then we should use typing.Optional[the_type]. In the example above, we'd have
def randints(self, amount: Optional[int] = None, a: int = 1, b: int = 100) -> list:
        """Generate list of random integers.

        :param amount: Amount of elements.
        :param a: Minimum value of range.
        :param b: Maximum value of range.
        :return: List of random integers.
        """

        if amount is None:
            amount = 3

        return [self.randint(a, b) for _ in range(amount)]

@bjd2385 I'll update code using Optional.

Sooo, it's done!

authors: bjd2385 lk-geimfari sobolevn

repo: lk-geimfari/mimesis


text:
🛑 스타필드 www.starfield.co.kr is down

In 7840c9e, 스타필드 www.starfield.co.kr (http://www.starfield.co.kr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 스타필드 www.starfield.co.kr is back up in 3524691 after 5 minutes.

repo: lksjames/monitoring


text:
🛑 까사미아 www.guud.com is down

In 709ab9e, 까사미아 www.guud.com (http://www.guud.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 까사미아 www.guud.com is back up in 251ec05 after 20 minutes.


text:
Any plan to support local host deployment

Instead of hosted version or self-hosted version, can I run it on local host. Seems not support this option yet, any plan to support this pattern? Thanks

Hi @gyliu513,
We're definitively plan to support this option, but we have high priority bugs to fix first.
Would a docker compose work for you?

Would a docker compose work for you?

Yes, that works, thanks @hughcrt !

@hughcrt hi, how is the process of getting an official docker image?

Hi @uhlhosting, we've been quite busy recently, but we haven't forgotten about it. We'll update you as soon as it's ready 🙂

Hi, @uhlhosting @gyliu513, you can find our pricing for docker compose support: https://lunary.ai/pricing/self-hosted
We've had several companies using that and they're really happy about it. We still allow local deployment for free.
Please let me know if you need assistance to set up a dev environment.

@hughcrt sorry excuse me? Prices for docker compose support, is this a joke, or it's 1st of april?

authors: gyliu513 hughcrt uhlhosting

repo: llmonitor/llmonitor


text:
Will not auto break if using nil pointer

To repro, try running in "test" mode or "debug".
Just access a value from a nil pointer. You will see in the log :
Error: bad access
delve closed with code 0

While for other exception/panics it will break in the last state before the panic just as expected

Interesting... dlv on the command line breaks in such cases. Let's see how delve is doing this.

Hm, I'm not able to reproduce it anymore, neither on ubuntu nor on windows...
I only updated delve using go get -u github.com/derekparker/delve/cmd/dlv.
This was my really simple test code, maybe you can provide other code that causes this problem:
package issue_test

import (
	"fmt"
	"testing"
)

type myStruct struct {
	asdf string
}

func TestIssue(t *testing.T) {
	var m *myStruct
	fmt.Println(m.asdf)
}

Sorry for the delayed answer.
I ran your test, it does fail on my system.
Here are some more information about my setup
MacOS 13.3.3
go version go1.10.1 darwin/amd64
go debug 1.6.0
Delve Debugger
Version: 1.0.0
Build: v1.0.0

Btw, I tested adding a breakpoint just before the supposed exception, then resume execution, then I get this error (and the debugger is stuck in play mode)

Note: testing on my system, it seems it might be related to delve issue, what do you think?

After checking, it seems the latest version of go debug does break on that case now! However, the stack trace is empty, and the scope variables giving weird unexpected informations... Can you reproduce this / any idea why?
Thanks!

Sry I cannot reproduce it using your code above and the latest version of delve. It automatically opens panic.go and I can go through the stacktrace and everything.
Do you have any warnings/errors in the developer tools?

authors: LouAdrien lloiser

repo: lloiser/go-debug


text:
atom-ide support

Would this plugin support atom-ide-ui?

I tried a while ago to support it but the infrastructure was not ready back then. see https://github.com/facebook/nuclide/issues/1502
I have not checked since then if anything has changed...

@lloiser Thanks for the response! There was no activity in debugger modules 😭

:cry:

You can disable the atom-ui support by adjusting configuration options on the package.
https://github.com/atom/atom/issues/17693

authors: Nicolab alexmironof jhg03a lloiser


text:
go debug is not able to stop

go-debug starts wel, but does not respond to the stop button.
trying to remove breakpoints at that point won't remove breakpoints, looks like the application "hangs",
Occurence: ever since the update to 1.0 (did not occur in earlier versions)
how to reproduce, add a couple of breakpoints to a go script, start debugging, after go-debug reaches the first breakpoint, press the stop button... this does not work

Please copy & paste the content of the Debug tab in the go-plus panel (it opens whenever you start the debugger)
Also provide some source code if possible.

me too...

Update to v1.0.1

Update to v1.0.1

authors: UksKim lloiser rjboer


text:
About the EWTA loss

Hi, Thanks for your great work!
I am wondering how do you make the parameter K in the ewta loss decay ,as there is no guidance in the config file you provided.
Looking forward to your reply and thank you in advance

Hi,
Thanks for your interest in our work.
Regarding your question: we do follow the same mechansim in decaying K as the original paper "Overcoming Limitations of Mixture Density Networks ....", where we start with penalizing all hypotheses K=20, and then after some time of training, we reduce K to its half K=10 and so on until we end up with K=1.
Hope that helps,

Thank you，that helps alot！


text:
expint is now in SpecialFunctions

https://github.com/JuliaMath/SpecialFunctions.jl/pull/236 should replace the version in src/EiFunction.jl (once a new version of SpecialFunctions is tagged).

Great, thanks a lot!

authors: lnacquaroli stevengj


text:
test: Ext upgrade test

Add two new test suites.
One testing conflicts for the redirect paths

And one for testing that the extension upgrade works fine.
It check both the UI and the API call:

install v1 -> check UI and API
install v2 -> check UI and API
...

UI and API contains different values based on the extension version.

Core PR merged: https://github.com/lnbits/lnbits/pull/2671

repo: lnbits/lnbits-extensions


text:
Don't create user if allowed users is set

When allowed users is set, the new user is created and then invalidated in the backend. This PR aims to not create the user at all and fail before creating the user.
Needs some more testing and edge cases... or possible issues from tackling the issue like this (or it it's worth it). From local testing, it works as expected: block creation of new users, if allowed_users is set and has at least a user!
Closes #1747

i think it ok that usermanager cant create users when allowed users is used... they are not compatible.
we should though return a proper error message, that creating is not allowed due to this feature beeing enabled.
and i should not be checked in crud it should be on api level.

What if i'm an admin creating users that way? otherwise, how are new users
created?
Probably this is not a bug... it's a feature, and not worth tackling, or
best wait for login?
On Tue, Jul 18, 2023 at 1:39 PM dni ⚡ @.***> wrote:

i think it ok that usermanager cant create users when allowed users is
used... they are not compatible.
we should though return a proper error message, that creating is not
allowed due to this feature beeing enabled.
and i should not be checked in crud it should be on api level.
—
Reply to this email directly, view it on GitHub
https://github.com/lnbits/lnbits/pull/1822#issuecomment-1640135746, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AC4F74RO4BAYJXIHWNDADS3XQZ7WRANCNFSM6AAAAAA2OF23IY
.
You are receiving this because you authored the thread.Message ID:
@.***>

is this PR still relevant?
it is in draft and tests fail

It should be specified in the .env.example that new users will not be created if LNBITS_ALLOWED_USERS is set.
# Allow users and admins by user IDs (comma separated list)
LNBITS_ALLOWED_USERS=""
LNBITS_ADMIN_USERS=""

authors: dni motorina0 talvasconcelos

repo: lnbits/lnbits


text:
fix(git): enfore lowercase commit.type

At the moment commit messages like "Fix(git) something" are grouped with 'Other Changes' instead of 'Bug Fixes'.
This PR makes sure caps in the commit.type are all grouped under their lowercase type.

Good fix @fvdm! Thanks for the contribution! I'll let you know whenever we publish a new version on npm.

v1.0.2 has been published! Thanks again!

Awesome! That was quick 👍

repo: lob/generate-changelog


text:
🛑 Løbner.dk is down

In 1e84b5f, Løbner.dk (https://www.løbner.dk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Løbner.dk is back up in 145ef97.

repo: lobner/status


text:
Migrate to User-Agent Client Hints

Below navigator apis will be deprecated in near future.

navigator.userAgent
navigator.platform

What is the plan to migrate these to the new introdued below apis.

navigator.userAgentData.brands (Gives an array)
navigator.userAgentData.platform

Please refer below article for more info:
https://web.dev/migrate-to-ua-ch/

It looks like there are only two user-agent checks in the codebase:

https://github.com/localForage/localForage/blob/master/src/drivers/indexeddb.js#L67
https://github.com/localForage/localForage/blob/master/src/utils/isIndexedDBValid.js#L16

From the comments, both seem to be self described "hacky workarounds" to support very old browsers (Chrome around v40, Safari below v10).  Might it make sense to just go ahead and drop support for ancient browsers officially instead?  Library consumers that want to maintain support could do their own detection (via whatever means) and force a supported driver.

repo: localForage/localForage


text:
doesn't working with Microsoft edge

anyone knows why ?

It depends what exactly doesn't work. If you use WebSQL, then it won't work anywhere as it's been deprecated. If you used IndexedDB or localStorage, it should work just fine, but if you use in a special context, for example Service Worker or Shared Workers, then only IndexedDB drive should work.

It depends what exactly doesn't work. If you use WebSQL, then it won't work anywhere as it's been deprecated. If you used IndexedDB or localStorage, it should work just fine, but if you use in a special context, for example Service Worker or Shared Workers, then only IndexedDB drive should work.

thanks, but it's working on linux & mac just doesn't working as expected on microsoft edge

authors: nicolasembleton tribhuwan-kumar


text:
GEOMESA-2870 Option to not cache HBase connections

Prevent corrupted connections from making all data stores unusable

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

Merged as d701377056ee5dc55c92694e3805fc3ef76d7192 on master.

repo: locationtech/geomesa


text:
GEOMESA-596,GEOMESA-603 Ingest from lon/lat without lon/lat in SFT

Ingest from lon/lat fields from a csv/tsv to a geom in the SFT without requiring
the lon/lat fields to exist in the SFT
Throw exception when lon/lat fields don't exist and don't overwrite wkt geom

Looks good.

Committed as e3175bad1dfb864e25485ce39e6598924e53bcf4 on 1.5.


text:
apple: massively improve markdown editing experience

[x] Eliminate a bunch of dead code
[x] Properly use NSTextStore's beginEditing() and endEditing() for BIG performance gains
[ ] Re-write Notepad from the ground up to eliminate more deadcode and strange behaviors
[ ] Investigate paragraph styles for regions like code block background
[ ] Fix our use of utf-8 and utf-16 to prevent weird characters from showing up at document boundaries
[ ] Make typesetting more beautiful (maybe separate pr)

[ ] Bullets properly indented
[ ] Bullets automatically inserted

[ ] Make editing feel better

[ ] Automatic insertion of bullets on return
[ ] Be able to click on links

Reading

https://developer.apple.com/library/archive/documentation/StringsTextFonts/Conceptual/TextAndWebiPhoneOS/CustomTextProcessing/CustomTextProcessing.html
https://developer.apple.com/videos/play/wwdc2021/10061/
https://www.objc.io/issues/5-ios7/getting-to-know-textkit/
https://github.com/kyle-n/HighlightedTextEditor
https://github.com/lockbook/lockbook/tree/f09eb0756572aae21e1012a0d9697c09d802802e/clients/apple/Notepad
https://blog.vinhis.me/2017/04/16/bullet-list-on-ios-with-textkit.html

Early experiments with automatic insertion of bullets:
https://user-images.githubusercontent.com/821972/154593870-660c9981-8ae8-43ed-adba-f946aed04574.mov

repo: lockbook/lockbook

license: Unlicense


text:
Cost Model Momentum

In GitLab by @proyan on Nov 6, 2019, 18:11
Create a cost which tracks the centroidal momentum

In GitLab by @proyan on Nov 6, 2019, 18:11
assigned to @proyan

In GitLab by @proyan on Nov 6, 2019, 20:23
mentioned in merge request !257

In GitLab by @cmastalli on Nov 15, 2019, 15:13
closed


text:
Plotting the convergence parameters to analyse DDP solver - [merged]

In GitLab by @cmastalli on Nov 15, 2018, 17:46
Merges solver -> devel
This PR allows us to record the solver performance through the iterates inside the solverParams. This feature is important to  compare the actual DDP solver against previous one (see #6), and it tackles the task #27.

In GitLab by @cmastalli on Nov 16, 2018, 08:48
@rbudhira I guess you're not available. I would merge this request since it's not affecting any fundamental function of the DDP software.
If you find a problem here, please create an issue

In GitLab by @cmastalli on Nov 16, 2018, 08:48
merged

In GitLab by @cmastalli on Nov 16, 2018, 08:48
mentioned in commit 850efe1f5110ca5df26129f12e0b9c3caa1bebea


text:
Defining an abstract class for action models and datas - [merged]

In GitLab by @cmastalli on Mar 8, 2019, 14:22
Merges topics/action-abstraction -> devel
The main target of this PR is to create an abstraction class for action models and datas as pointed out here #79. The tasks achieved were:

Creation of abstract classes for action models and datas.
Used this class to implement unicycles, LQR and NumDiff classes (both model and data)
Added g and L variables in differential action and action data classes. This is convenient for saving time in some cases.
Used standard naming for AMLQR formulation.
Removed setUpRandom from AMLQR. With this, we preserve the same structure of DAMLQR.
Added recalc option for AMLQR.calcDiff.
Removed UnicycleData classes since we don't need special implementatio (with the abstract it's enough).

In GitLab by @cmastalli on Mar 8, 2019, 14:23
changed title from {-Topics/action abstraction-} to {+Defining an abstract class for action models and datas+}

In GitLab by @cmastalli on Mar 8, 2019, 14:23
changed the description

In GitLab by @nmansard on Mar 8, 2019, 15:27
I think a AM should come with a State. Then nx and ndx can be deduced from the State. nu has to be provided.
def __init(self,State,nu):
  self.State = State
  self.nx = State.nx
  self.ndx = State.ndx
  self.nu = nu

In GitLab by @nmansard on Mar 8, 2019, 15:28
Thanks, nice job.
It seems that this MR is merged with !131 , is it not? You should first finalize !131 before proposing this one.

In GitLab by @cmastalli on Mar 8, 2019, 17:11
changed this line in version 2 of the diff

In GitLab by @cmastalli on Mar 8, 2019, 17:11
added 2 commits
974eb866 - [action] Passing the state as an argument in the action model abstraction7c8f6ec7 - [action] Random values for full rank matrices
Compare with previous version

In GitLab by @cmastalli on Mar 8, 2019, 17:12
It's a nice idea. Done!

In GitLab by @cmastalli on Mar 8, 2019, 17:12
resolved all discussions

In GitLab by @cmastalli on Mar 8, 2019, 17:14
I add random generation of orthogonal matrix inside AMLQR. It was a similar issue as reported for DAMLQR (see https://gepgitlab.laas.fr/loco-3d/crocoddyl/merge_requests/131#note_3531).
This PR doesn't contain commit from !131. We can merge it.

In GitLab by @nmansard on Mar 12, 2019, 08:33
Sure? Because you modified some tests using the LQR to rename it. Is it a late patch for a mistake introduced after the initial changes in the AMLQR?

In GitLab by @cmastalli on Mar 12, 2019, 14:21
As discussed orally, there is not connection with !131. You can merge it

In GitLab by @nmansard on Mar 12, 2019, 15:55
merged

In GitLab by @nmansard on Mar 12, 2019, 15:55
mentioned in commit 3269cf78551143253c687ce41039901368bd4766


text:
Include LICENSE file in sdist

It would be good to include the LICENSE file in the source distribution on pypi.

this is done.  configured in setup.cfg.

authors: carlodri cgoldberg

repo: locustio/locust


text:
Ensure to wait a second before next tick()

When developing a custom TestShape, a developer needs to implement tick() method, that manages Users spawning. As mentioned in the official documentation:

Locust will call the tick() method approximately once per second.

Therefore, a developer may design a TestShape with a strong assumption that the number of Users will be adjusted with ~1 second interval. Unfortunately, the interval is indeed kept only when no adjustment in Users number is made - hence it seems useless, as any interval is meaningful only during some changes. Here's an example of logs from Locust master when a custom TestShape was implemented and  the tick() method is clearly triggered too often:

the timestamps of log messages show, that 20 Users were spawned within ~6 seconds, while the spawn rate is set to 1.0. In fact I was able to achieve much bigger discrepancies between expected/declared and actual number of users.
In this PR I provide a small adjustment in Runner's code to ensure the ~1 second interval is maintained. Also a small code optimization in handling the current_tick Tuple was added to keep the file length almost unchanged :)

@cyberw I've also added a dedicated test case that doesn't base on get_run_time when modifying the Users count, but relies on 1-sec interval

nice!!

@wiatrak2 is it possible that one of the test cases got a little flaky from this change?  Perhaps it should be adjusted? https://github.com/locustio/locust/actions/runs/6919408511/job/18822743361?pr=2472

@wiatrak2 Can you have a look at the occasionally failing test case? While I do believe your change is good, it did break the test case and I dont have time to analyze why it is breaking, so I might have to revert it...

@cyberw it happened in the worst possible moment - I'm on vacation and away from my computer until December 16th :( I won't be able to have a look before

No worries! I can disable the tests for now (I dont think anything is actually broken, and if it is its a small issue)

Yep, the change was not a sufficient one. If you can disable the test - let's do it. I will have a (very fresh) look once I'm back to the business ;)


text:
exec_container does not respect devImage

What happened?
When adding an exec_container command to a pipeline, the resulting deployment overrides the dev.<service_name>.devImage property of the service and instead causes the runtime.images.<service_name> value to be referenced.
This results in an ImagePullBackOff error when no image has been pushed to the registry.
It appears to happen irrespective of matching image/label selections and which pipeline it is is run from.
What did you expect to happen instead?
The exec_container command would not modify which image is referenced in the deployment, using devImage when one is specified, and image otherwise.
How can we reproduce the bug? (as minimally and precisely as possible)
My devspace.yaml:
version: v2beta1
name: exec_container_bug

vars:
  REGISTRY_HOST:
    name: REGISTRY_HOST
    source: env
    default: registry-push:5000
  REGISTRY_NAME:
    name: REGISTRY_NAME
    source: env
    default: frontend

pipelines:
  dev:
    run: |-
      run_dependencies --all
      create_deployments --all
      # comment this command out to observe how `devImage` is respected
      exec_container --label-selector "app.kubernetes.io/component=web-server,app.kubernetes.io/name=frontend" -- \
                      sh -c 'echo hi'
      start_dev --all

images:
  next-server:
    image: ${REGISTRY_HOST}/${REGISTRY_NAME}/frontend
    tags:
      - 'devspace-${devspace.git.commit}-####'
    dockerfile: ./frontend/Dockerfile
    context: frontend/
    target: app
    appendDockerfileInstructions:
      - USER root
      - RUN apt update -y
      - RUN apt install curl vim -y
    rebuildStrategy: default

deployments:
  next-server:
    helm:
      releaseName: frontend
      chart:
        path: ./helm

dev:
  web-server:
    labelSelector:
      app.kubernetes.io/component: web-server
      app.kubernetes.io/name: frontend
    devImage: ghcr.io/loft-sh/devspace-containers/typescript:17-alpine
    sync:
      - path: .:.
        disableDownload: true
        initialSync: preferLocal
        waitInitialSync: true
        excludeFile: .gitignore
        excludePaths:
          - ".git/"
        uploadExcludePaths:
          - Dockerfile
          - .dockerignore
        onUpload:
          restartContainer: true
          exec:
          - command: |-
              npm install
            name: 'Install node modules'
            onChange: ["./package.json"]
    restartHelper:
      inject: true
    command: ["node", "server.js"]

Local Environment:

DevSpace Version: [use devspace --version] devspace version 6.0.1
Operating System: debian linux bullseye
ARCH of the OS:  ARM64
Kubernetes Cluster:
Cloud Provider:  aws
Kubernetes Version: [use kubectl version] v1.25.0

/kind bug

@joshuamanns thanks for reporting this issue! The problem seems to be that you first exec into the container and then it will be replaced by the dev configuration. Would reordering it be an option for you like this:
pipelines:
  dev:
    run: |-
      run_dependencies --all
      create_deployments --all
      # comment this command out to observe how `devImage` is respected
      start_dev --all
      exec_container --label-selector "app.kubernetes.io/component=web-server,app.kubernetes.io/name=frontend" -- \
                      sh -c 'echo hi'

Thanks @FabianKramm. So my use case is that I would like to take a devImage, install some build tools inside of it, and build some dependencies from source in the devImage container itself when I sync files (if you're truly curious I can explain "why" later 😄 ), then start the process using the compiled build output. exec_container seemed like the way I should approach that, but perhaps it is not?

Hey @joshuamanns ! I understand, with DevSpace v6.1.0 you can do that via:
dev:
  web-server:
    labelSelector:
      app.kubernetes.io/component: web-server
      app.kubernetes.io/name: frontend
    devImage: ghcr.io/loft-sh/devspace-containers/typescript:17-alpine
    sync:
      - path: .:.
        disableDownload: true
        excludeFile: .gitignore
        excludePaths:
          - ".git/"
          - Dockerfile
          - .dockerignore
        onUpload:
          restartContainer: true
          exec:
          - command: |-
              # Your init commands
              apt install ...
            once: true # <- Only execute this one time during the pod's lifecycle
          - command: |-
              npm install
            name: 'Install node modules'
            onChange: ["./package.json"]
    command: ["node", "server.js"]

Ah, interesting @FabianKramm  - I've just tested and it does not seem to play well if the file in the dev.*.command is not available until after onUpload.exec.command is run. So in my case, server.js isn't built until the init commands finish, which results in the the container spinning.

@joshuamanns but isn't that what you want? Or do you want to start the container first and then run the init script?

Hello, @joshuamanns!
Seems that we might have misunderstood the flow you are trying to achieve.
We would be happy to further support you in this matter if you could provide us with more details about your desired outcome.
Please let us know if there is anything else we could help with!
Thank you for your contribution!

repo: loft-sh/devspace


text:
error: can't start new thread

The logger.warning(e) happens in a loop and this can try to send a lot of logs.
Traceback:
File "[...]/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 114, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)

File "[...]/local/lib/python2.7/site-packages/django/views/generic/base.py", line 69, in view
return self.dispatch(request, *args, **kwargs)

File "[...]/local/lib/python2.7/site-packages/newrelic-2.40.0.34/newrelic/hooks/component_djangorestframework.py", line 8, in _nr_wrapper_APIView_dispatch_
return wrapped(*args, **kwargs)

File "[...]/local/lib/python2.7/site-packages/django/views/decorators/csrf.py", line 57, in wrapped_view
return view_func(*args, **kwargs)

File "[...]/local/lib/python2.7/site-packages/rest_framework/views.py", line 400, in dispatch
response = self.handle_exception(exc)

File "[...]/local/lib/python2.7/site-packages/rest_framework/views.py", line 397, in dispatch
response = handler(request, *args, **kwargs)

File "./api/views/filemanager.py", line 49, in get
return Response(serializer.list_files_in_folder(path, images_only), 200)

File "./api/serializers/filemanager.py", line 156, in list_files_in_folder
logger.warning(e)

File "/usr/lib/python2.7/logging/__init__.py", line 1152, in warning
self._log(WARNING, msg, args, **kwargs)

File "/usr/lib/python2.7/logging/__init__.py", line 1258, in _log
self.handle(record)

File "/usr/lib/python2.7/logging/__init__.py", line 1268, in handle
self.callHandlers(record)

File "/usr/lib/python2.7/logging/__init__.py", line 1308, in callHandlers
hdlr.handle(record)

File "/usr/lib/python2.7/logging/__init__.py", line 748, in handle
self.emit(record)

File "[...]/local/lib/python2.7/site-packages/logentries/utils.py", line 124, in emit
self._thread.start()

File "/usr/lib/python2.7/threading.py", line 494, in start
_start_new_thread(self.__bootstrap, ())

error: can't start new thread

Can you try the latest version? https://pypi.python.org/pypi/Logentries

Hi guys,
Still having this issue with Celery workers - see my comment in https://github.com/logentries/le_python/issues/3 - are there any plans to address it? I contacted support, but they just told me it's not a priority.

@rsaftoiu hoping to have a branch hopefully with a fix for this soon. Ill let you know when it's available

@StephenHynes7 thanks, appreciate it!

@rsaftoiu Have a fork here of this https://github.com/StephenHynes7/le_python/blob/cddf42285cb59e88afeb2ce16e7de6867ff3b5a4/logentries/utils.py. We will be doing our own tests on this aswell

Thanks @StephenHynes7, I will take a look. We switched from using this to just using syslog though, so not as critical for us anymore. Still appreciate the fix :)

I (apparently) worked around this by removing logentries from the logger configuration:
    'loggers': {
        ...
        'logentries': {
            'handlers': ['null'],
            'propagate': False,
        },
    },

Necro bumping to get this pushed upstream to PyPi so I don't have to maintain a copy.

^^ Seconded.  Right now we have to manually apply this patch after installing LE with pip.

Maybe the PR #46 solve this issue

hi, still seeing issue after PR #46 in celery workers.  Logentries is upgraded to version 0.17 as per advised.
File "/app/.heroku/python/lib/python2.7/site-packages/logentries/utils.py", line 195, in emit


text:
关于容器采集的疑问？

In what area(s)?

/area discovery

Ask your question here:
看文档，loggie是采用list watch的方式监听容器的事件。想请教两个问题：

请问这种方式是否对api server造成比较大的压力？
每个采集器都会收到集群内所有的pod变化，那对每个pod都会生成一个采集配置吗？最终又是如何过滤出只针对本宿主机的容器进行采集的呢？

loggie只会监听自身所在节点的pod的事件，并不会list&watch所有的pod变化。
只有logconfig/clusterlogconfig匹配到所在节点的pod，才会生成相应的配置。

loggie只会监听自身所在节点的pod的事件，并不会list&watch所有的pod变化。 只有logconfig/clusterlogconfig匹配到所在节点的pod，才会生成相应的配置。

我对kubeinformers的包不是特别熟悉，能告诉一下大致的代码路径，是怎么只监听自身所在节点的pod事件的吗？

https://github.com/loggie-io/loggie/blob/main/pkg/discovery/kubernetes/kubernetes.go#LL114C2-L114C21

authors: aivinray ethfoo

repo: loggie-io/loggie


text:
Crashes

When i open it, it runs fine and then i type in the codes and it crashes pls help

Please supply your full error

When i open it, it runs fine and then i type in the codes and it crashes pls help

Bro just install the requirements.

Closed due to inactivity


text:
Add timeline to the report

This PR adds support for log line timestamps to create a chronological view of the anomalies found across multiple files. This can be useful for distributed systems where the earliest anomalies are likely to be most important compared to the last ones which are often emitted by the failure logs collections.

[x] timestamp parser
[x] timeline render in the web view
[x] documentation/changelog

This PR is still missing a better timeline rendering in the UI to link to the full logfile, otherwise I think the logic is pretty good.

repo: logjuicer/logjuicer


text:
Links without trailing / fail

eg:
www.logsearch.io/docs/ works, but www.logsearch.io/docs doesn't - seems to redirect to http://www.logsearch.io:61003/docs/

Fix by adding port_in_redirect off; to nginx.conf. (see)
Have raised  to get this fixed in the upstream in the staticfile buildpack (so a custom nginx.conf isn't needed)

repo: logsearch/logsearch-website


text:
Bug in Disappearance of Custom Component

Describe the bug
A clear and concise description of what the bug is.
As shown in Figure 1, the custom component added cannot be loaded in the new version of the code. After comparing the code before and after, it was found that the logic of assigning values to output_types has changed, as shown in Figures 2 and 3. When storing the output_type in the collection at the end, components with the same name are overwritten because output_type is used as the key, as shown in Figures 4 and 5.

Here is the code snippet from the "langflow/src/backend/langflow/interface/custom/directory_reader/directory_reader.py" file, where the assignment of the "output_types" variable has been modified, causing it to be duplicated. Later, when it is added to the set, the objects are overwritten due to the same key, and the corresponding component menu cannot be loaded:
` if validation_result:
try:
output_types = self.get_output_types_from_code(result_content)
except Exception as exc:
logger.exception(f"Error while getting output types from code: {str(exc)}")
output_types = [component_name_camelcase]
else:
output_types = [component_name_camelcase]
        component_info = {
            "name": "CustomComponent",
            "output_types": output_types,
            "file": filename,
            "code": result_content if validation_result else "",
            "error": "" if validation_result else result_content,
        }`

repo: logspace-ai/langflow


text:
Replaced atomic and thread_safe for concurrent_ruby.

Fixes #17

Hi @driverpt, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile?

@karmi , fixed.

Since this has not been merged, is this why the plugin is broken?

Hi guys
Is there a reason, why this pull request has not been merged yet?
Kind regards
Elmar

authors: MikeKemmerer driverpt evonlanthen karmi