Windows - npm i - does not install depenencies

After adding this module in package.json and trying to use it I see following error message:
Unknown plugin "transform-function-bind"
I've checked and none from devDependcies were installed.
Please advice.

devDependencies are not installed because those are installed only if you run npm i in package directory. this message can occur in case of misusing this plugin - double-check if you import this package right.
also, I suggest you to install latest rc build that includes some fixes for npm i as a dependency.

I am importing it correctly. My application is in dev mode as well. This is why it wants dev packages.
I was using latest rc

@maxgamurar double-check please that you do not recompile the lib, just use the provided build


SSL Certificate Validation Callback

Hi,
in MailKit it is possible to provide a method to make the SSL certificate validation in code.
Is it possible to add this to NullMailer or is there a way to do that already?
I wonder why I need the Certificate at all as I connect via SMTP port 25.
Thanks

I'm sure it is possible. MailKit/MimeKit seems to have support for certificate based authentication mechanisms built in, though I'm personally not familiar with mail services that require client certificates.
Mostly, I think all I'd need to do is provide support for defining certificate details in settings, and passing that info along to the MailKit services if they're provided in the settings (like it does with username and password settings now).
Thing is, I don't know how to test it, since I don't happen to have a lot of locally installed mail servers just kicking around.
If I made a beta package that had support for this, would be be able to do the code review and test if it works? Or could you point me to a quick way to setup a mail service locally that would let me test certificate scenarios (on windows)?

Hi Stephen, thanks for your reply and sorry for the delay.
We had another admin here and fixed the certificate problem.
The method I was referring to was this
What's missing for me now it that flag to tell the client which SSL we use. Currently only the true / false override is supported, but having this with that would be great.

Thanks for the update. I'll make time in the next few days, or over the weekend, to work on this.

I've look into this in more detail. It seems what you were doing is validating (or overriding the default validation) for the SMTP server's certificate; not using client certificates as I'd initially thought.
Based on the documentation, the best way to accomplish this with the current framework would be for the consuming application to supply it's own instance of the MailKit SMTP client and pass it in via the MkSmtpMailer's overloaded constructor .
var client = new SmtpClient
{
    // setup a validation callback, this one basically just overrides the default check
    //    Useful if the default validation would fail; e.g. server uses an untrusted cert
    ServerCertificateValidationCallback = (s, c, h, e) => true
};
var mkOptions = new OptionsWrapper<MkSmtpMailerSettings>(new MkSmtpMailerSettings
{
    //setup options here
});
var m = new MkSmtpMailer(client, mkOptions);

The SecureSocketOptions is a bit more complex. The way it is setup now, the mailer's setting only chooses if SSL is required, or if it is optional. Yes, the connection will use try to use SSL if the server supports it.
I'm going to do a bit more research before I decide what changes to make related to SMTP authentication. Maybe just changing that option's name would clarify the effect it has when set.
There is still some need for more complex SMTP configuration settings though; for example using GMail would be difficult with the current configuration, and it would be nice to support client certificates and access tokens too.

These are great information. Thank you for your investigation.
If I would have seen this remark about using SSL even when set to false earlier there would have been less confusion.

The code changes are ready, but before calling this done I want to add integration tests specific to working with gmail authentication, and update the documentation.

Gmail and support for token authentication in general seems to work, but in practice some effort would be needed by the consuming application to ensure the mailer instances always have a valid token (since they expire). Typically, this means these consumers will have to manage the token in the settings dynamically, rather than reading them from a static config file.


Add AI Client Support for Multiple Providers and Enhance Workflow Features

Overview of Changes
This PR introduces a series of improvements to the Paper2Code project, including:

Support for multiple AI client providers (OpenAI and Ollama).
Enhanced Docker configuration generation workflows.
Addition of software dependency extraction capabilities.
Expanded workflows to handle Dockerfile and docker-compose.yml generation.
Refactoring for improved logging and error handling.
Support for reading papers in both PDF and plain text formats.

Details

Support Multiple AI Client Providers

Implemented an abstract AIClient class.
Added OllamaClient and OpenAIClient implementations with fallback logic based on environment variables.
Included error handling for OpenAI rate limits and invalid configurations.

Enhanced Docker Workflow

Added DockerConfigGenerator to produce Dockerfile and docker-compose.yml configurations based on extracted dependencies.
Improved dependency and service analysis from code blocks and inferred software mentions.

Software Dependency Extraction

Introduced a SoftwareExtractor agent to identify software dependencies from academic papers.
Utilizes a JSON output format with fields like name, version, purpose, and confidence.

Improved Paper-to-Code Workflow

The PaperToCodeWorkflow now includes Docker configuration generation.
Modularized and enhanced logging for better traceability of each step.

New Features in main.py

Integrated random output directories for storing Dockerfile and docker-compose.yml outputs.
Improved logging for start-to-finish process traceability.

Additions to .gitignore

Added entries for outputs/* and examples/* while preserving .gitkeep files.

Expanded requirements.txt

Added dependencies:

PyPDF2 for PDF text extraction.
regex for pattern matching.
tiktoken for OpenAI token encoding.

New Utility Module for Parsing

Added parsers/paper_parser.py for reading PDF and text files.

Motivation
These changes address the need for:

Flexibility in AI provider usage.
Streamlined generation of infrastructure configurations (Docker).
Enhanced dependency management for academic papers.
Improved robustness and maintainability of the codebase.

Impact

Simplifies the onboarding process for users by automating Docker configuration.
Broadens usability with support for both OpenAI and Ollama.
Provides a more comprehensive toolchain for academic-to-code translation.

Testing

Tested AI client functionality with both OpenAI and Ollama.
Validated Dockerfile and docker-compose.yml generation with sample inputs.
Verified software dependency extraction on various academic papers.
Confirmed compatibility of main.py with both PDF and text inputs.

Additional Notes

Future enhancements could include support for additional AI providers and more granular dependency extraction.
Improved handling of multi-language papers is planned.

I haven't tried running yet, but looks good. Just two comments:

I run the code. Another minor comment is that it is printing out OPENAI_API_KEY. Could be a problem when it runs on CI.


Please add novelfulldotnet back into plugin

Describe your suggested feature
Please add old source back into the plugin for 2.0 located here:
https://github.com/LNReader/lnreader/blob/v1.1.19/src/sources/en/novelfulldotnet.ts
Other details
strangely enough novelfull.com is different than novelfull.net.  Search results differ and therefore content isn't the same.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I have updated the app to version 1.1.19.
[X] I will fill out all of the requested information in this form.

there is already novelfull.com are sites different?

Yes.  Feel free to verify yourself by searching for the keyword "dimensional".  There's about 2x the results on .net


Dead external link.

https://github.com/microsoft/TypeScript-Website/blob/62f87a80f571762ff252eb38b53b890f9f864acb/packages/documentation/copy/en/release-notes/TypeScript 2.6.md?plain=1#L15
This link is dead, and I'm not sure what to link to instead.

While I couldn't find another URL for the page, it looks like the blog was down due to Heroku's decision to shut down its free plan.
I found the archived page by Internet Archive: http://web.archive.org/web/20220823104433/https://www.stephanboyer.com/post/132/what-are-covariance-and-contravariance Maybe we could temporarily replace the dead link with this one.

Looks like this was fixed by OP in #2808

Thanks for the heads-up.🙂  It seems that the new link was broken again so I'd raised a new PR to ensure the stable URL.


Switch to a different parsing library

Due to the lacking performance of ANTLR consider switching to a different parsing library.
Question: Is SPARQL context-free? (i.e. parsable with parser-combinators)
Answer: yes
Possible Libraries to look into (in no particular order):

https://github.com/taocpp/PEGTL (parser combinator)
https://github.com/foonathan/lexy (parser combinator)
https://tree-sitter.github.io/tree-sitter/ ("general enough to parse any programming language")
https://live.boost.org/doc/libs/1_68_0/libs/spirit/doc/x3/html/index.html (LL parser using EBNF)

Important features:

fast
correct
easy to maintain
expressive parsing errors
stream support (optional?)

Also: ANTLR causes stack overflows on deeply nested path queries


Improve websearch

This PR implements case-insensitive search by default and highlighting, to address a few cons from #57.
Case-insensitive search works by building another lookup table and forcing lowercase lookups, but the search function has been upgraded with an extra is_case_sensitive parameter in case someone wants to add a checkbox to toggle  case sensitivity.
For better search third party services are required, like Algolia, or other self hosted solutions. A pure static site can only do so much.

It is a little late now, but the idea of the vendor directory was to keep code third party code separate from the other directories. e.g. normalize.css is copied from the vendor directory and not from the css directory

sorry morgan, I didn't realize this was the directory intention. Can you adjust this in master directly?

ok, I think I fixed here: https://github.com/adventuregamestudio/ags-manual/commit/e28c1b2818226d1018a910b7db37dc73d4abbaf9

ok, I the artifacts are identical and I can't figure this out, I have checked in MacOS.

My apologies for not using the vendor folder

It is no big deal, just that it then doesn't make sense to have the other parts separate.
I'm pretty sure the diff comparison failing will have been because of line ending conversion when the code is checked out. I'll take a look.

If that's the case, please also update the git attributes for this:
https://github.com/adventuregamestudio/ags-manual/blob/master/.gitattributes

It isn't that easy to globally define the line endings because anything read as a template has its line endings ignored by Pandoc on input and set by Pandoc on output, and that is source code that is editable not something that should be preserved regardless of platform.
It should be OK to set wildcard matches for anything within the vendor directory since those files probably shouldn't be manually edited (really it just avoids using a package manager and an Internet connection).


Enable DockerTrustSuite for ARM again

After https://github.com/docker/docker/pull/19471 has been merged I ran a test on Scaleway. And yes, the DockerTrustSuite now works on ARM.
The arm build should show OK: 1145 passed, 41 skipped

First arm build timed out after 180 minutes, increased it for ARM and pushed again.

failing arm test is flaky https://github.com/docker/docker/issues/19368

Jenkins job userns timed out after 90m, arm build timed out after 180m. Seems to me that the timeout is set in Jenkins job itself as the defaults above in make.sh (120m, 210m) aren't used.
@tophj-ibm Thanks for the link. In over 100 Jenkins of our ARM builds I only found it fail 2 times. But good to know.

16:55:00 FAIL: docker_cli_network_unix_test.go:995: DockerNetworkSuite.TestDockerNetworkHostModeUngracefulDaemonRestart
16:55:00
16:55:00 [d16158137] waiting for daemon to start
16:55:00 [d16158137] daemon started
16:55:00 [d16158137] exiting daemon
16:55:00 [d16158137] waiting for daemon to start
16:55:00 [d16158137] daemon started
16:55:00 docker_cli_network_unix_test.go:1016:
16:55:00     c.Assert(err, checker.IsNil)
16:55:00 ... value *exec.ExitError = &exec.ExitError{ProcessState:(*os.ProcessState)(0x11447d60)} ("exit status 1")
16:55:00
16:55:00 [d16158137] exiting daemon
16:55:03
16:55:03 ---------------------------------------------------------------------```

Related?

@icecrime nope, see flaky test https://github.com/docker/docker/issues/19368

Yes, seems flaky. Our Jenkins on Scaleway says: PASS: docker_cli_network_unix_test.go:995: DockerNetworkSuite.TestDockerNetworkHostModeUngracefulDaemonRestart	37.591s

The timeout for the arm build should be increased, 180m is not enough if we add more integration tests. ping @jfrazelle

Any chance for an arm rebuild later on? TestDockerNetworkHostModeUngracefulDaemonRestart is flaky, I've seen the new timeout for arm is 260m, that should make the build pass.

@StefanScherer I say we can merge with enough approvals if its just that one test thats flakey and unrelated.

LGTM

Isn't there a way to specify a "for a single test timeout"? I'm not sure I like the fact that we keep bumping up the overall time our integration suite takes, when in fact we should be limiting every test to take a minimum of x minutes.

@cyphar agreed, if you can find a solution to this I think it'd be welcome.

@tiborvass Well, according to the Go documentation, -test.timeout should be doing that already:
-timeout t
    If a test runs longer than t, panic.
    The default is 10 minutes (10m).

I think this is related to the fact that all of our tests are methods on DockerSuite.

@cyphar interesting find. Thanks let us know.

Let's merge this one, then we can look at the -timeout option separately
LGTM

@thaJeztah SGTM

@cyphar yeah I'm not sure go-check supports that :sweat:

To be honest, that's a bug that needs to be fixed. What use is having a timeout for the entire test suite?

@cyphar form my point of view, having a timeout for the entire is as important as having a timeout on each tests. The timeout on the entire test suite (or in our case right now on all suites) help following the growth in time on our test case and decide how we can improve those.
If you have both, you make sure that all your tests are done in a limit, and that no test is taking longer than X, but you could (and should) have nbOfTest * timeoutOfOneTest != timeoutOfAllTest.

@StefanScherer how much does it add in term of "times", because the current arm queue is sooo full already...

@vdemeester about 6-7 minutes:
09:15:39 PASS: docker_cli_build_test.go:5831: DockerTrustSuite.TestBuildContextDirIsSymlink	3.846s
09:15:45 SKIP: docker_cli_create_test.go:332: DockerTrustSuite.TestCreateWhenCertExpired (Currently changes system time, causing instability)
09:15:51 SKIP: docker_cli_pull_trusted_test.go:65: DockerTrustSuite.TestPullWhenCertExpired (Currently changes system time, causing instability)
09:15:57 SKIP: docker_cli_run_test.go:3200: DockerTrustSuite.TestRunWhenCertExpired (Currently changes system time, causing instability)
09:16:12 PASS: docker_cli_build_test.go:5779: DockerTrustSuite.TestTrustedBuild	9.048s
09:16:18 PASS: docker_cli_build_test.go:5810: DockerTrustSuite.TestTrustedBuildUntrustedTag	0.717s
09:16:32 PASS: docker_cli_create_test.go:282: DockerTrustSuite.TestTrustedCreate	7.526s
09:16:52 PASS: docker_cli_create_test.go:359: DockerTrustSuite.TestTrustedCreateFromBadTrustServer	13.584s
09:17:05 PASS: docker_cli_create_test.go:319: DockerTrustSuite.TestTrustedIsolatedCreate	6.406s
09:17:16 PASS: docker_cli_pull_trusted_test.go:35: DockerTrustSuite.TestTrustedIsolatedPull	5.467s
09:17:29 PASS: docker_cli_pull_trusted_test.go:177: DockerTrustSuite.TestTrustedOfflinePull	6.398s
09:17:40 PASS: docker_cli_pull_trusted_test.go:14: DockerTrustSuite.TestTrustedPull	5.648s
09:17:55 PASS: docker_cli_pull_trusted_test.go:205: DockerTrustSuite.TestTrustedPullDelete	9.150s
09:18:14 PASS: docker_cli_pull_trusted_test.go:93: DockerTrustSuite.TestTrustedPullFromBadTrustServer	12.909s
09:18:20 SKIP: docker_cli_pull_trusted_test.go:147: DockerTrustSuite.TestTrustedPullWithExpiredSnapshot (Currently changes system time, causing instability)
09:18:31 PASS: docker_cli_push_test.go:203: DockerTrustSuite.TestTrustedPush	4.832s
09:18:40 PASS: docker_cli_push_test.go:243: DockerTrustSuite.TestTrustedPushWithDeprecatedEnvPasswords	3.494s
09:18:51 PASS: docker_cli_push_test.go:222: DockerTrustSuite.TestTrustedPushWithEnvPasswords	4.913s
09:19:04 PASS: docker_cli_push_test.go:299: DockerTrustSuite.TestTrustedPushWithExistingSignedTag	7.386s
09:19:16 PASS: docker_cli_push_test.go:279: DockerTrustSuite.TestTrustedPushWithExistingTag	5.417s
09:19:22 SKIP: docker_cli_push_test.go:371: DockerTrustSuite.TestTrustedPushWithExpiredSnapshot (Currently changes system time, causing instability)
09:19:28 SKIP: docker_cli_push_test.go:397: DockerTrustSuite.TestTrustedPushWithExpiredTimestamp (Currently changes system time, causing instability)
09:20:11 PASS: docker_cli_push_test.go:255: DockerTrustSuite.TestTrustedPushWithFailingServer	37.082s
09:20:22 PASS: docker_cli_push_test.go:351: DockerTrustSuite.TestTrustedPushWithIncorrectDeprecatedPassphraseForNonRoot	5.328s
09:20:33 PASS: docker_cli_push_test.go:329: DockerTrustSuite.TestTrustedPushWithIncorrectPassphraseForNonRoot	5.369s
09:20:47 PASS: docker_cli_push_test.go:423: DockerTrustSuite.TestTrustedPushWithReleasesDelegation	7.828s
09:20:55 PASS: docker_cli_push_test.go:267: DockerTrustSuite.TestTrustedPushWithoutServerAndUntrusted	1.849s
09:21:11 PASS: docker_cli_run_test.go:3146: DockerTrustSuite.TestTrustedRun	10.244s
09:21:33 PASS: docker_cli_run_test.go:3238: DockerTrustSuite.TestTrustedRunFromBadTrustServer	15.162s
09:21:42 PASS: docker_cli_create_test.go:303: DockerTrustSuite.TestUntrustedCreate	3.202s
09:21:51 PASS: docker_cli_pull_trusted_test.go:49: DockerTrustSuite.TestUntrustedPull	3.195s
09:22:00 PASS: docker_cli_run_test.go:3178: DockerTrustSuite.TestUntrustedRun	3.337s

What about adding some more arm build slaves? Oh, I just had a look, now there are six slaves. Last time I saw two.

Some PRs have been waiting for more than 12 hours to be tested. I think we should disable ARM testing until we have enough machines to deal with the load?

Whatever we do with ARM CI, this PR is fine, since it reduces timeout on other CIs, so i'm merging.


[Task] Add unit test cases for LoadingSpinner component

Task Description:
Currently, we run unit tests using jest which can be found here.
However, the test cases are not yet comprehensive enough and work can be done to cover more grounds. Specifically for this issue, we hope to add test cases for the LoadingSpinner component.
Deliverable(s):
New unit test cases that cover the testing of the LoadingSpinner component.
Additional Context:

The LoadingSpinner components can be found here
An example for AudioButton can be found here which may serve as a good source for reference

@tjtanjin  would love to work on the issue

@tjtanjin  would love to work on the issue

Go for it!

Hey @Abishkardhenga! Checking in to see if you're facing any problems working on the issue. Feel free to reach out!

Hey @Abishkardhenga! With hacktoberfest drawing closer to the end, I'll be re-opening this issue for others that may be keen in this final stretch. That said, if you're still interested, feel free to open a PR soonest!

Hey i would like to work on this issue could you assign it to me

Hey i would like to work on this issue could you assign it to me

Go for it!

Hello @tjtanjin ! I would like to work on this issue! Could you assign this issue to me please?

Hey @cleobnvntra, go for it! 😊


[BUG] -  "npm run build"  inside "ui-library " not producing any new "player.js"

Branch :
ue5.2
Screenshots

Problem component
Doc and webpack cmd
Steps to Reproduce:
https://github.com/EpicGames/PixelStreamingInfrastructure/blob/UE5.2/Frontend/README.md
accoridng to that doc i have to do this :

The default user interface is provided in /ui-library directory. You can either use it or provide your own user interface. To build the default UI, run:
cd ui-library
npm install
npm run build

Expected behavior

This will produce player.js under the SignallingWebServer/Public directory - this is the default UI.

But i dont see any player.js was produced after excuting "npm run build".
is the doc wrong or i did something wrong ?

Looks like the docs have been updated for 5.3 onward. I've pulled the changed documentation into 5.2 also.


Reduce pin related unsafe code

This removes many of the remaining pin related unsafe code in futures-util and futures-test.
r? @cramertj @Nemo157

This looks great, thanks!


nixos: boot: luks: add option fido2NeedsPIN

Some FIDO2 keys are pin protected but don't provide a facility for PIN entry on the device. Instead a PIN can be provided by the user via the keyboard to unlock the device. Add a new option that allows the --pin option to be passed to fido2luks for entering the PIN on boot.
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2639

I'm not sure this change is necessary? I just setup my system, and I was prompted for my pin.


Add ROS Indigo Support (Ubuntu 14.04)

I modified the Sim to work on ROS Indigo and tested it using our own stack from 2018.
The Sim itself works as expected without issues.
The Track Editor does not work (yet) because it requires PyQt5, which is not directly available as an apt-get package for Ubuntu 14.04 and python2.7 and has to be installed from source (see here for a lead)
The two major modifications I needed to do were uninstalling gazebo2 and installing gazebo7, and adding -fext-numeric-literals as compile options to enable the suffix Q for the float128 type.
Other modifications were just switching to the indigo packages instead of the kinetic packages.

Hey, sorry I totally forgot that you had some open questions.
Yes, it is totally possible to include the stuff in the ./update_dependencies.sh, I will do that and push it when I'm done!

@chriser- can we move on this? Or can I just close it?


gpg Key error in apt-get installation instruction

When executing
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys "D401AB61 DBE1D0A2"

I get the following result:
$ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys "D401AB61 DBE1D0A2"
Executing: /tmp/apt-key-gpghome.B3RuvWpOpZ/gpg.1.sh --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys D401AB61 DBE1D0A2
gpg: "D401AB61 DBE1D0A2" not a key ID: skipping

update:
I only get this error on Ubuntu 17.04.
If I run the same command in an Ubuntu Trusty or Xenial VM then it works as expected.

update 2:
using the new key ID from https://bintray.com/tvheadend/ubuntu (379CE192D401AB61) works on my native Ubuntu 17.04  as well as an Ubuntu Trusty VM.

Same with 18.04 LTS

We need to use the long key id, using twi shirt key ids does not work for all gpg versions it seems.
This is the correct long key id: 379CE192D401AB61


Update service-fabric-networking-modes.md

To mitigate the issue with open network on RS3 (RDBug 12741931) - we recreate the network on VM reboot. The documentation lets users know how to bypass this default behavior, if needed.

@sdkadam2017 : Thanks for your contribution! The author, @mani-ramaswamy, has been notified to review your proposed change.

#sign-off

@sdkadam2017 @mani-ramaswamy - I sent you an email regarding this PR. Thanks

#sign-off


Qowle

I added 2 commit, 1st I added my name and 2nd is removed a duplicate of name that written twice

Shaqo waca, Mahadsanid.


Update

Sir Update your files

I have done composer update but i still get the error

Please be patient, we are still refactoring this and will abandon the v1 release. We're trying to go with v2.


Is double baking fixed?

Hi, I would like to begin using Bakechain but there are some comments on reddit alerting about Bakechain double-baking so I want to clarify them first:

Is that double-baking bug already fixed with the 2 last updates?
It would be safer in order to avoid double-baking to use you own node instead the public setup by default? And if so, is there any guide/tutorial in order to setup your own node using bakechain?
Upon you are using Bakechain with the address created by default by the software, it will be possible when the Ledger Nano upgrade is released to use the same address in order to implement the Ledger Nano with the already baking address?

Thanks in advance Stephen, you are my hero

Double baking has been fixed, unless you run multiple instances of the software with the same keys. I believe the latest user on reddit is not a bakechain user (someone on the Riot channels mentioned they lost bonds due to double baking, and they were not using bakechain - this occurred within the last 12 hours). Another user who lost bonds lately was most likely using an older version.

Running your node is always better, but doesn't really prevent double baking. The best way to setup your own remote-node is to follow this guide: https://github.com/tezoscommunity/FAQ/blob/master/Compile_Mainnet.md - you can buy a VPS from a solid provider, like Linode, AWS, Google Cloud or DigitalOcean. Once setup, you can use the node address within bakechain.

Ledger Nano S baking will be the best, as it will be more secure (due to on-device prevention's of double baking). However, you can not import existing addresses into the Ledger device, so unfortunately you will need to setup a new baking address. In saying that, Ledger baking with Bakechain should be released this week - going through final tests before release.

And thanks for the kind words, means a lot!


Add liveview to app

I made the first steps to get phoenix live view in the app. It just adds the boilerplate necessary for it to get working (and some steps were already done for the livedashboard.
Thus far it doesn't do anything yet but next steps could be to add endless scrolling to the paginated pages etc.

Sweet! @gemantzu and @SophieDeBenedetto you both are far more versed in LiveView than I so I defer to you but this looks good to me :+1:

Yeah, I've got search and pagination running locally though it's a bit of a rough draft. I'll post a WIP PR soon so we can go over it.


fix: go lint errors

What type of PR is this?
/kind enhancement
fix issue https://github.com/openyurtio/openyurt/issues/2234
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

@rambohe-ch @zyjhtangtang  PTAL

/LGTM


reconcile TerasologyTestingEnvironment and ModuleTestingEnvironment

Currently we have TerasologyTestingEnvironment in engine-tests and ModuleTestingEnvironment which is currently in its own repo. They have the same goal, which is to provide a test harness you can use with JUnit that has a full running terasology engine to run your test scenarios in.
It's a complicated subject and it's hard enough to maintain even one of them; I propose we stop trying to have two.
This will also influence https://github.com/Terasology/ModuleTestingEnvironment/issues/39
as if we need this for engine's own tests, I think we'll want to keep it in this repository.

also review the other stuff that engine-test defines in org.terasology: https://github.com/MovingBlocks/Terasology/tree/872f9a53172e1faae13d2b34efd765507e216b38/engine-tests/src/main/java/org/terasology
TerasologyTestingEnvironment is one user of HeadlessEnvironment, but there are other tests out in module-space that use it directly.
ModuleEnvironmentTest makes a ModuleManager and a TypeRegistry for its environment. Not as complex as a full engine with subsystems, but seems relevant when considering about what kind of test extensions we need.


karma fails for Tour of Heroes tutorial, part 3, Multiple Components

Continued from: https://github.com/angular/quickstart/pull/184
I cannot run npm test on the results of the Tour of Heroes tutorial, part 3, Multiple Components.
It produces this error:
    Chrome 52.0.2743 (Mac OS X 10.11.6) AppComponent with TCB should instantiate component FAILED
[1]     Error: Template parse errors:
[1]     Can't bind to 'hero' since it isn't a known property of 'my-hero-detail'.
[1]     1. If 'my-hero-detail' is an Angular component and it has 'hero' input, then verify that it is part of this module.
[1]     2. If 'my-hero-detail' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the<EMAIL_ADDRESS>of this component to suppress this message.
[1]      ("
[1]           </li>
[1]         </ul>
[1]         <my-hero-detail [ERROR ->][hero]="selectedHero"></my-hero-detail>
[1]       "): AppComponent@10:20

It seems to me that hero is a known property of my-hero-detail:
export class HeroDetailComponent {
  @Input()
  hero: Hero;
}

What am I missing?

Found a solution!
Figuring perhaps the spec test needs to know about HeroDetailComponent, I modified  app/app.component.spec.ts, by adding:
import { HeroDetailComponent } from './hero-detail.component';

and changing beforeEach() to include HeroDetailComponent in its declarations:
  beforeEach(() => {
    TestBed.configureTestingModule({
      imports: [FormsModule],
      declarations: [AppComponent, HeroDetailComponent]
    });
  });

Found another solution, that I like better:
Instead of the changing app/app.component.spec.ts as above, modify app/app.component.ts:
add this import at the top:
import { HeroDetailComponent } from './hero-detail.component';

then add this directives field to the @Component decorator:
  directives: [HeroDetailComponent]

Please update the tutorial with whichever change is preferable.

We had similar issues with<EMAIL_ADDRESS>components.
The app runs fine, but the karma/jasmine tests throw errors for these components.
Your first solution works well, but is there an equivalent workaround to your "directives" include?
Because the directives key was replaced with "declarations" and is only available in @NgModule annotations...?!
Thanks for the hint, we were looking for a solution for quite some time now only to get the karma/jasmine tests running again :tropical_drink:

The right solution is to configure your testing module correctly:
  beforeEach(() => {
    TestBed.configureTestingModule({
      imports: [FormsModule],
      declarations: [AppComponent, HeroDetailComponent]
    });
  });

Tour of Heroes doesn't talk about unit tests so it really doesn't make sense to update it with these solutions. Instead, we have the testing chapter at https://angular.io/docs/ts/latest/guide/testing.html

Thanks for clarifying! :)

...
import { HeroDetailComponent }   from './hero-detail.component';
...
declarations: [ AppComponent, HeroDetailComponent ]
In app.module.ts

The tutorial is missing the import in the app.module.ts ; the changes should be added to the tutorial and the final code review section else this doesn't work.
The zip file download of the final code of tutorial 5 actually contains the changes but it isn't mentioned in the tutorial itself or the final code review tabs

It's invalid to have this as a closed issue because it was not fixed or addressed in the documentation.

Agree with farnsworth2008 - shouldn't be closed.
I ran through the tutorial and Ng test errors suggest to me something is structured wrong but I don't know what because the solutions from google/stackoverflow feel like hacks - do I really have to import every sub component and sub-sub-component in a project into the top-level app.component.spec.ts ?
The tutorial doesn't need to cover this, but since it leaves you with a project that fails most of its tests out of the box, an optional section on the right way to get the heroes project testable would be excellent. The Testing section of the Angular starts from the assumption that your project will be automagically ready to test and will pass its tests.

I did not change a thing.
But tried the suggestion by @leb9049 to restart the 'ng serve'
This seemed to fix the issue.


How to get cpu usage

See the examples directory in the repo. Also #84.

I thank cpu usage is different cpu_load_aggregate.

What other kind of usage is there? I'm not aware of any other ways to measure CPU usage than what's implemented as cpu_load_aggregate.


add one switch to webview_flutter to control whether it is interactive or not

Use case
when use WebView_flutter in web, we can't interact with the area of flutter that on top of webview, so we need to use PointerInterceptor  as talked in https://github.com/flutter/flutter/issues/142427#issuecomment-1965628862
but i think WebView_flutter should have a switch to control interactive it self, and when it is not interactive, engine can do a lot optimize, maybe there is no need to copy the picture of webview or pass use input to it;
Proposal
PlatformView is very expressive, as it need to copy texture and react to user input; if one platform view is inactive, maybe it can be put on bottom or top of flutter to avoid copy, as multi-view is coming, this is more available. as webview_flutter is a special PlatfromView, and not always need to be interactive, so I suggest to add such switch, so that we can use webview_flutter more efficient;

@wanjm
Can you provide an example (code sample) which shows current limitation and how would adding a switch would help to resolve it ?

but i think WebView_flutter should have a switch to control interactive it self, and when it is not interactive, engine can do a lot optimize

This is not how the layering works; the engine does not know about individual plugins. There is no way for the engine to query a webview_flutter-specific setting.
If you are proposing a fundamentally new kind of platform view at the engine level, the next step would be a detailed design document describing in detail how it would work and what the benefits would be. Adding a new kind of platform view would require substantial justification for the added complexity, so the discussion of advantages would need to be much more detailed and technical than the high-level discussion here. See below for some specific things the design document would need to address.

maybe there is no need to copy the picture of webview

Platform views do not generally copy the display, nor does "non-interactive" imply "not displayed" or "not visually changing".

or pass use input to it;

It's not clear to me what significant engine optimizations this would allow.

maybe it can be put on bottom or top of flutter

Layering is primarily about visual presentation, not gesture handling, so as above it's not clear how "non-interactive" would allow for changing the way it is rendered.

@wanjm Can you provide an example (code sample) which shows current limitation and how would adding a switch would help to resolve it ?

one example i said in the issue
https://github.com/flutter/flutter/issues/140855#issuecomment-1899462721


onScroll on KeyboardAwareScrollView is not fired

Describe the bug
onScroll on KeyboardAwareScrollView is not fired
Code snippet
Just add onScroll={console.log} in example app.
Repo for reproducing
You can use example app.
To Reproduce
Steps to reproduce the behavior:

Go to KeyboardAwareScrollView
Scroll view
See console output

Expected behavior
You should see events if you scroll ScrollView.
Smartphone (please complete the following information):

Desktop OS: MacOS 14.2.1
Device: iPhone 15 Pro
OS: iOS 15.2
RN version: 0.72.4
RN architecture: old
JS engine: Hermes
Library version: 1.10.2

Additional context
It can be fixed by adding next code into onScroll handler:
const onScroll = useAnimatedScrollHandler(
    {
      onScroll: (e) => {
        position.value = e.contentOffset.y;

+        if (onScrollProp) {
+          runOnJS(onScrollProp)({ nativeEvent: e });
+        }
      },
    },
    [],
  );

or assign our onScroll handler as onScrollReanimated (REA intercept all events for a given view, so there is no difference which prop to use).

This is not fixed. onScroll does NOT fire from KeyboardAwareScrollView. @kirillzyusko please reopen this.

@z1haze thanks for bringing it up 👀 May I kindly ask you to test https://github.com/kirillzyusko/react-native-keyboard-controller/pull/408 and see whether it fixes the problem or not?
I believe it should fix because I just tested example app and had the same issue as you - and this PR resovles the problem. But I'm more than sure that previous approach was working - most likely with a new release of RN or REA it's not working now, but again it was working before 👀 😅 .

Hey @kirillzyusko. Checking your solution, would it not be more effective to use a normal scroll callback?
This is my current patch for it:
    const onScroll = useCallback((event:NativeSyntheticEvent<NativeScrollEvent>) => {
      position.value = event.nativeEvent.contentOffset.y;
      onScroll2?.(event);
    }, [onScroll2]);

Is there an underlying purpose for using the reanimated hook for the callback?

Is there an underlying purpose for using the reanimated hook for the callback?

Yeah, it will update the value on UI thread synchronously. In your case it'll be updated on JS thread and it will not be as efficient as updating on UI thread.
Potentially it's possible to use your solution (I am reading scroll shared value only when keyboard movement happens - that value is not driving any animation, so it's okay to miss some frames during update), but of course I need to check that there is no performance hits 😅

That makes sense. I originally tried the runOnJS solution, but I think it wasn't working correctly because the scroll handler from props needs to be passed to the useAnimatedScrollHandler deps array. My callback wasn't being updated with its own dependencies for that reason, I think.
Aside from that, if the regular callback works, it seems less "hacky" to do that since you can pass the entire event rather than just the nativeEvent properties.

Aside from that, if the regular callback works, it seems less "hacky" to do that since you can pass the entire event rather than just the nativeEvent properties.

Yeah, for sure 👍 I changed a code in my PR - would you mind to test it and confirm whether it fixes the problem in your project? 👀

I've been using the JS implementation since this morning. Everything seems to be fine. My only concern was that it would mess with something since it is not longer using Reanimated's hook. I also wasn't sure what was going on with that mystery onScrollReanimated prop.

@DaltonPelkey onScrollReanimated is an internal prop and was used to intercept onScroll event 🙂 So it shouldn't be a breaking change.

My only concern was that it would mess with something since it is not longer using Reanimated's hook.

I think it shouldn't. And you are right - this implementation looks less hacky so let's try this 👀
I'll merge PR tomorrow 👍

@kirillzyusko we could not find anywhere that prop was being used. Could you shed some light on that?

@z1haze the ScrollView was coming from Reanimated. So output from useAnimatedScrollHandler can be attached as any prop to ScrollView and it'll work (literally it can be abracadabra and it will intercept necessary events - that's how REA works).
But yes, it's kind of hack and it will produce TS issues anyway, so better not use it 👀


Trivial change recheck/repair branch protection

@sinandredemption this should be repaired/reset regarding branch protection.
As mentioned, there might be some local small changes that you need to recreate. I apologize for the confusion. Let's see if branch protedction/CI are fully up and running agin, then please continue. I will be out for a few hours now.
This is you r branch. Sorry i keep fumbling around. Check CI, restart/repaired now.


Could you release a v0.16.2 please?

I tried upgrading from v0.15.1 to v0.16.1, but ran into the regression mentioned in https://github.com/amatsuda/kaminari/issues/516#issuecomment-46291619. As mentioned there, the regression was fixed in d3aab06e1f6aef01ece44ea6a349cb93e7b43fe3 (only 3 commits ahead of the v0.16.1 version cut).
I could have my Gemfile point to the commit on Github, but I would rather not depend on that commit not being rebased :-) A proper version cut would be much preferred.

We're already working on the next version. 0-16-stable is already stable but I still have to tweak Travis builds a bit more to make sure it doesn't break existing behaviors on 1.8.7. But pretty sure we will soon cut a new version. Thanks!


Plotly figure space savings

Log large figures as pngs rather than plotly figures.

Hit the biggest offenders here. There's a clear method to follow along the following lines
    fig.write_image('fig.png', width=1024, height=512)  # save the image rather than the fig, for size reasons     fig_dict['Regression Results'] = wandb.Image('fig.png')     wandb.log(fig_dict, commit=False)


feat: don't crash LSP when there are errors resolving the workspace

Description
Problem
Before this PR, LSP would crash for assumed workspaces (when we can't find a Nargo.toml) or when there were errors in the Nargo.toml.
Summary
Now LSP doesn't crash in the above cases:

for assumed workspaces we don't crash (we used to not crash but I made some changes in the past that broke this)
for errors in Nargo.toml we now output to STDERR, so you can see the error in the output. This is what Rust Analyzer does, except that they also have a "rust-analyzer" thing at the bottom that becomes yellow when there's an error... I didn't implement this (it probably requires some code on the extension side) but I think if something doesn't work you'd check the logs or ask, and it's worse if it crashes.

Additional Context
Documentation
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Done! #6259


Growing memory over time / Memory Leak

Hi,
I've been encountering a weird behaviour on k8s with some nodejs apps and pyroscope, as over the time, memory is growing indefinitely.
I've tried different docker image base OS (Alpine with node 18, node:20-bullseye-slim), setting pods replicas on k8s to 1, but without a luck.
Installed Pyroscope version
"@pyroscope/nodejs": "^0.3.11",

Usage in code

Memory usage over time

As it's getting more strange, the pyroscope itself does not seem any memory growth
Self

Total

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

FWIW, I reported something very similar in #28. I never got a resolution.

Yea I saw it, but IIRC the issue you raise was on the version when this package was still using google pprof. They switched to datadog pprof.
And that surprised me. This package is basically a wrapper for datadog pprof, and I've been using datadog profiler in nodejs environment for years and tbh - never had such a problems


Fix "too many open files" issue

Purpose
$title
Fixes #
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

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

@@           Coverage Diff           @@
##           master   #19181   +/-   ##
=======================================
  Coverage    15.8%    15.8%
=======================================
  Files          47       47
  Lines        1259     1259
  Branches      196      196
=======================================
  Hits          199      199
  Misses       1047     1047
  Partials       13       13

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 3a628d0...c655582. Read the comment docs.


209 add search feature to the header

Fix #209
Test URLs:

Before: https://main--cn-website--netcentric.hlx.page/
After: https://209-add-search-feature-to-the-header--cn-website--netcentric.hlx.page/

The search input has to be included in the header before testing

Did you check the search result page with lighthouse?


rustic-cargo-current-test fails when no test is found

Running rustic-cargo-current-test when (rustic-cargo--get-current-fn-fullname) returns nil will trigger an error. For example when one press C-c C-c C-c on the pub fn.
The bug itself is easily solvable by checking that fullname exists.
But I'm thinking that it can be useful to change this keybinding to cargo-dwim which will either run current test or for example cargo check, if no test can be found. What do you think?

Hmmm. Maybe a prompt should be opened to ask the user which test(s) he wants to run. When running this command the user expects to run a test, why should he suddenly want to use a totally different command ?

The idea is to bind C-c C-c C-c to rustic-cargo-dwim, so it does something meaningful in the current context. If I'm writing a test, run current test for me. If I'm in the /tests or in tests mod, run the whole test suite, otherwise run cargo check.

Ok.

Also, the rustic-cargo--get-current-fn-fullname result is incorrect when there is use ...; inside the test fn, which is a normal case when using diesel, see example.

Please reopen this issue if you notice new issues with this function.


Get global distribution type to fix #468

This PR needs from this other one.
It use global data to generate ramp color.

:es:


Adding generic parametrizable offline_node.launch

And adapting offline_backpack_(2d|3d).launch to use it.
This will be useful for parametrizing evaluation runs as well.

@wally-the-cartographer merge

Merge requested by authorized user sebastianklose. Merge queue now has a length of 1.


Bad sensor detection

Hello,
I've just encounter a big crash with  a backup restauration problem with a lot of lost element and your integration save my life  ... i love you !!!
During this backup and redeployment process i've noted that watchman was making a bad identification of a service and it estimates that as a sensor :
service input_boolean.turn_on  is identify as missing sensor  >>  input_boolean.turn_ [missing] scripts.yaml:494,553,620
i hope it's can help for futur update :)

Watchman should correctly identify input_boolean.turn_on as a service, tested on 0.6.5. It checks every "entity" candidate to be present within HA service registry before adding it to the report. However, if your config/scripts/automations use a part of id (as input_boolean.turn_ in the example above) it will be treated as an entity because HA doesn't have such a service.


Html issue 2

Pull Request Type
What kind of change does this PR introduce?
[X] Solved an issue/task
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:
What is the current behavior?

navigation.html was missing a nav bar
Issue Number: [Insert Issue Number (if applicable)]
What is the new behavior?
created a nav bar with a link to three pages. Home, About, & Contact

Other information

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out our forkcommitmerge.io website repository. The repository contain real issues that you can help to resolve or create some of your own if you see any bugs or want to add new features to the site, etc. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


loadOptions with the callback option fails to load options

I am using the latest build (0.0.37) and when I try to use delayed loading, it would always fail, even when I hard quote the example array. I might have missed something but after hours of failing, I'd like to seek some help here.
Here is the template:
<treeselect
          :load-options="loadOptions"
          :multiple="true"
          :options=treeselectOptions
          :auto-load-root-options="false"
          v-model="searchTerm"
        />

Here is data:
data: function(){
    return {
      treeselectOptions: null,
    }
  },

Here is the method, specifically loadOptions:
loadOptions({ callback }) {
      axios.post('/api/options', {
        var_name: varName,
      })
      .then(function (response) {
        callback(null, [ {
          id: 'success',
          label: 'With children',
          // Declare an unloaded branch node.
          children: null,
        }, {
          id: 'no-children',
          label: 'With no children',
          children: null,
        }, {
          id: 'failure',
          label: 'Demonstrates error handling',
          children: null,
        } ]);
      })
      .catch(function (error) {
        return 'error';
      });
    },

There is no console error but the prompt is always "No options available."
Any advice would help. Thank you!

@ciloi I did get it to work:
Updated template
   <treeselect
          :load-options="loadOptions"
          :multiple="true"
          :loading="true"
          :options=treeselectOptions
          :auto-load-root-options="false"
          :default-expand-level="1"
          :placeholder=filter.options.caption
          v-model="item.searchTerm"
        />

loadOptions
    // load options for the v-treeselect componenet
    loadOptions({callback}) {
      var vm = this;
      axios.post('/api/options', {
        var_name: "my_var_name",
      })
      .then(function (response) {
        var options = parseOptions(response);
        vm.treeselectOptions = options; // this is one critical step - make sure you update the options variable bound to your v-treeselect component
        callback(); // notify vue-treeselect about data population completion
      })
      .catch(function (error) {
        return 'error';
      });

It did take me a while and I wished the documentation had this part explicitly explained. Please try and let me know. If it works I should close this as it's not quite an issue by then.
Thanks


Update index.md

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Updated article with relevant Alt codes

Hi,
Thanks for this pull request (PR).
Unfortunately, we are marking this PR invalid for hacktoberfest. We believe it does not follow the recommended guidelines:

Quality Standards
In line with Hacktoberfest value #2 (Quantity is fun, Quality is key), we have provided examples of the quality standards we encourage. This applies mainly to beginners.

PRs that are automated e.g. scripted opening PRs to remove whitespace / optimize images.
PRs that are disruptive e.g. taking someone else's branch/commits and making a PR.
PRs that are regarded by a project maintainer as a hindrance vs. helping.
Something that's clearly an attempt to simply +1 your PR count for October.

Learn more at https://hacktoberfest.digitalocean.com/details


Trace Logging on Permission Denied & ColorFormat

This PR adds log.Trace(...) calls to Permission Denied events.
It also adds a new additional way for providing colored logs for structs in a semi-standardised way. e.g.
log.Info("Log me a user %-v", user)

Will log Log me a user userID:username with the userID being colored cyan and the username in bold.
Structs that want to implement this need to provide a ColorFormat(s fmt.State) function which is very similar to the Format(...) function expected by fmt (mainly lacking the rune - which would always be 'v'.) If you logged %-v then this function will be called, and if more verbose output is possible a + should be passed in the flags and inspected for with s.Flags('+') in ColorFormat, e.g. log.Info("%-+v", perm) to log a verbose version of models.Permission.

Codecov Report

Merging #6618 into master will decrease coverage by 0.05%.
The diff coverage is 27.56%.

@@            Coverage Diff            @@
##           master   #6618      +/-   ##
=========================================
- Coverage   40.46%   40.4%   -0.06%
=========================================
  Files         406     406
  Lines       54484   54774     +290
=========================================
+ Hits        22045   22134      +89
- Misses      29402   29600     +198
- Partials     3037    3040       +3

Impacted Files
Coverage Δ

routers/repo/issue_watch.go
0% <0%> (ø)
:arrow_up:

routers/api/v1/repo/pull.go
17.58% <0%> (-0.13%)
:arrow_down:

modules/context/permission.go
20.63% <0%> (-20%)
:arrow_down:

routers/repo/issue.go
35.41% <0%> (-1.4%)
:arrow_down:

routers/api/v1/api.go
66.84% <0%> (-5.56%)
:arrow_down:

routers/repo/wiki.go
49.53% <0%> (-1.27%)
:arrow_down:

routers/user/home.go
37.06% <0%> (-0.58%)
:arrow_down:

routers/repo/pull.go
36.13% <0%> (-0.54%)
:arrow_down:

models/user.go
49.95% <100%> (+0.18%)
:arrow_up:

models/repo.go
47.35% <100%> (+0.43%)
:arrow_up:

... and 9 more

Continue to review full report at Codecov.

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

Isn't Trace implementation supposed to be a no-op if !log.IsTrace rather than check if it's Trace level all the time ?

Ah yes but constructing the trace call is not free - so if we can avoid constructing it at all that may make sense.
A lot of the calls there are less complex than I originally had them because I moved functionality into colorformat, so we could remove a few of the IsTrace calls but not all


[Query] A high-complexity path query in Read Query #7

To make the result unique and not too complex, consider to find just those topN or nearest traces, and keep them sorted.

Has modified the max hops to 3. And more tweaks will be applied in further profiling

closed currently


[QUESTION] How change DataKline size?

Only can see 500 data range, how to increase?
Also, can I add horizontal line with a color in the 0 value for the bottom indicators?

https://klinecharts.com/en-US/guide/instance-api.html#setbarspace-space


Blockly for E2

Google has made a very nice system called Blockly, its very simple to use and have a nice interface for making scripts, I propose that using a system similar to it in gmod would bridge the gap between the representation of gates and the raw coding power of E2
https://developers.google.com/blockly/

Since it's basically just another editor for the same language, I don't see much value in that.
Feel free to use Blockly to make a standalone editor for E2.

An interesting project if somebody wants to contribute it, but unlikely to happen.
Wire2 had something similar to this, but it'd require a serious rewrite of most of Wiremod's entities.

Like a gates-within-gates system? Would be nice to have, but nah


3920: Removed broken sites

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information
Removed unsupported sites:
viafree.se
viafree.dk
viafree.no
viasat4play.no
tv3play.no
tv8play.se
tv6play.se
tv3play.se
tv3play.dk
tv10play.se
play.nova.bg
Fixes #3920
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[x] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Copilot Summary

🤖 Generated by Copilot at e5a60dd
Summary
🗑🔥🧹

Remove obsolete and unused code for Viafree and other TVPlay sites. Update documentation and module imports accordingly.

Some extractors were no longer needed
So from the codebase they were deleted
ViafreeIE and more
Were shown to the door
And the docs and imports were updated

Walkthrough

Remove Viafree support from documentation and extractor modules (link, link, link, link, link)

Why are they removed and not fixed instead?

Why are they removed and not fixed instead?

Pluto.tv have bought and taken over these URLs, and would be a new extractor and new task:

viafree.se
viafree.dk
viafree.no

Does not exist anymore:

viasat4play.no
tv3play.no
tv8play.se
tv6play.se
tv3play.se
tv3play.dk
tv10play.se

play.nova.bg already have an extractor at noveplay.py, and was removed from tvplay.py

Pluto.tv have bought and taken over these URLs (already got an extractor plutotv.py):

viafree.se
viafree.dk
viafree.no

Should these be added to plutotv's valid_url then?

Probably not, as the old URLs does not redirect anywhere (I am getting a 403). If you are using plutotv you would only work with plutotv URLs anyway and would have no need for supporting the old URLs.


Added Option to automatically resize Images on Quick Upload not working

Added Option to automatically resize Images on Quick Upload not working
Details:
In the Settings in the Config Tab is a new Setting ResizeImageQuality this enables the autom. Resizing The Settings Resize_MaxHeight and  Resize_MaxWidth will define when the image will be resized. If the width or height is bigger then defined it will be resized.
You can also reduce the file size via the Image Quality the Setting for that is ResizeImageQuality the default value is 80 (means 80%) so if you want to keep the image dimensions and only reduce the file size by decreasing the Quality you can do that.
The above added feature doesn't resize uploaded image but only adds styling of resize after being uploaded to server. Requirement needed is to resize on upload (save space on server) and set image size in same process and not to add resize styling only.

As far as i tested it works as expected. Did you actually enable the setting ResizeImageOnQuickUpload?
Did you test this with the quick upload in the link dialog or with the upload in the Filebrowser?

Hi Ingo,
My Quick Upload plugin licence has expired in fact. I will update it and retest, thanks

No you don't need a license. The quick upload is the upload tab inside the link dialog in the editor

I was referring to the jsplus addon 'Quick Image Upload' plugin but never checked the link dialog in the editor. Do you mean this:

yes thats the quick upload function in the editor i mean.

Hi Ingo, OK I tried it just now and when I click 'OK' after uploading img it doesn't do anything?

And this is the error when I click 'OK' -

I have this selected:

And this is the before/after imgs file sizes:
855 KB (875,997 bytes)
22.2 KB (22,732 bytes)
so it appears to resize correctly just link dialog not working as I'd like
Thx

Yes i'm aware if the issue i just released version 2.1.10 of the editor provider. With the fixed link dialog.

Hi Ingo
That's great, thanks again!


Microsoft has changed things?

Well, looks like the above only applies to version 1703 of Windows 10 perhaps?
I have 1709, and multiple attempts to upgrade to 1803, like a massive number of others worldwide, ends in failure and the dreaded reboot loop.
Tried following the above, but unfortunately, there is no record in Event Viewer in Windows Logs\Application for winsetupdiag02.
There is however an event 1001 from the source Windows Error Reporting, but unfortunately it takes a slightly different method of writing out the information, which makes it  useless in comparison to the above method, whereby the above simply gives you codes to find quick answers.
Perhaps Microsoft could update this document to reflect what to look for in the 1709 version of Windows 10?
Will hold off updating clients pc's until I can work out what is going wrong, and feel that this latest update is far more stable.

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

ID: 68640934-3744-abdd-8c69-1c01c85ddf9b
Version Independent ID: 3821be03-0231-2707-452b-78b375cbde1a
Content: Windows error reporting - Windows IT Pro
Content Source: windows/deployment/upgrade/windows-error-reporting.md
Service: w10
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

@officedocsbot assign @mypil

#Resolved in #3702

@GreggHales - Thank you for submitting feedback.
From our understanding, the issue has been resolved but it may take a few days for the merged content to appear in the article. If you feel it hasn't been resolved, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

@officedocsbot close


Investigate: create installers using JEP 343: Packaging Tool

Let's see if we can ship deb, rpm, dmg and msi installers
https://openjdk.org/jeps/343

https://github.com/fvarrui/JavaPackager

https://graalvm.github.io/native-build-tools/latest/gradle-plugin-quickstart.html

https://github.com/dropwizard/dropwizard/issues/2974

https://www.baeldung.com/spring-native-intro#2-sample-graphql-schema-files

https://github.com/nebula-plugins/gradle-ospackage-plugin

https://github.com/i-net-software/SetupBuilder

Done


Set zipkin service name from resource

https://github.com/open-telemetry/opentelemetry-specification/pull/472

dupe of #919

Oops. Closed as dupe.


java.io.IOException: Server returned HTTP response code: 500

i got this error, my program can not finished , seems hanged at last n tasks, which n is eq to worker number.
java.io.IOException: Server returned HTTP response code: 500 for URL: http://novel-read-wxhpcli-2.wxxdc:4040/api/v1/applications/application_1589120307951_1015477/executors

this is not an error, just every slow!


Document onboarding flow with the new storage provider

Document changes to the onboarding with this new option
Add developer-optional Gaia hub choice during onboarding (#https://github.com/blockstack/blockstack-browser/pull/1723)

This was done.


feat: Support for Vodafone Sercomm H300S

Tested with:
Firmware: Vodafone-H-300s-v<IP_ADDRESS>
Hardware: V2
Changed back to http://{host}/login.html used because with https Python 3.11+ return error: aiohttp.client_exceptions.ClientConnectorSSLError: Cannot connect to host <IP_ADDRESS>:443 ssl:False [[SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:1006)]
processEnterFunc with challenge login: login.js.txt

@myhomeiot, are you going to update the code so we can consider merging ?

@chemelli74 I resolve the conflicts and check resulting code with HA 2024.4.3, working as expected.
PS: I don't understand how to fix the lint errors without delete this pull request and reopen it. If you can, please fix this strange lint errors.
Thanks in advance.

You need to use pre-commit ;-)

How you want to fix PLR2004 error (Magic value used in comparison), should I add this constants into const.py or make an enum?

I think the cleanest approach is to transform LOGIN from const.py in a dict and use values from there.

You are committing to your main branch so I cannot co-author.
Please use always pre-commit in future.

Fix CI problems with new pull request.


Any idea if the NBA will open up playerdashboardbygeneralsplits ??

Where'd you get this endpoint from? Can you send me a URL on stats.nba.com where they make a request to it?

http://stats.nba.com/player/#!/203076/stats/ underlying this url is a API call:
http://stats.nba.com/stats/playerdashboardbygeneralsplits?DateFrom=&DateTo=&GameSegment=&LastNGames=0&LeagueID=00&Location=&MeasureType=Base&Month=0&OpponentTeamID=0&Outcome=&PORound=0&PaceAdjust=N&PerMode=PerGame&Period=0&PlayerID=203076&PlusMinus=N&Rank=N&Season=2015-16&SeasonSegment=&SeasonType=Regular+Season&ShotClockRange=&VsConference=&VsDivision=

this has been pretty handy:
https://github.com/danielwelch/little-pynny. I've used his swaggon.json file on my own site to document some of the endpoints.

Huh! Interesting. Not sure how they are detecting when to respond with Access Denied. Copying as cURL command from Chrome and then executing it from the command line works fine. But using an HTTP API client like Postman from the same cURL command fails, even with the referer and user-agent headers set correctly. No idea how to get around the 403 unfortunately 😕


builtin axaml formatter

maybe we can reuse the xstyler
https://github.com/Xavalon/XamlStyler/wiki/Script-Integration

Why wouldn't you just use XamlStyler? It does support Avalonia XAML.

It would definitely be nice to use the built-in VS Code formatting command to have axaml files formatted, as opposed to using a separate cli tool.

@heartacker @fuzzzerd you might be interested in these topics https://github.com/Xavalon/XamlStyler/issues/349 https://github.com/Xavalon/XamlStyler/wiki/VSCode

@heartacker @fuzzzerd you might be interested in these topics https://github.com/Xavalon/XamlStyler/issues/349 https://github.com/Xavalon/XamlStyler/wiki/VSCode

geart，

and it connot work in linux，
we prefer a built-in tool

@heartacker Avalonia doesn't own XamlStyled, and there are a few reasons to include it in this extension when it should be a dedicated XamlStyler extension.
On the other hand, we could implement our own solution and include it with this extension, but I doubt it is worth spending time on that.

@heartacker @fuzzzerd you might be interested in these topics Xavalon/XamlStyler#349 https://github.com/Xavalon/XamlStyler/wiki/VSCode

Thanks, that appears to be a decent workaround.
If there are no plans to implement formatting natively (or integrate that utility) with this extension I certainly respect that decision. I think most people using a VSCode extension will expect built-in formatting support, and if an external utility is the recommended path it would be nice to have a docs update that specifically recommends this setup.

I also didn't like the use of an external formatter tool that comes with some downsides compared to the integrated formatting option.
For that reason, i decided to create a separate formatter (still very early) extension that mostly is a wrapper around the XamlStyler Command line tool.
You can find it here: https://github.com/dabbinavo/vscode-xamlstyler
Feel free to contribute or make some proposals to improve the extension.


Fixes explorer new folder inputbox duplicates parent folder children when toggling collapse state

This PR fixes #90040

Thanks a lot for this PR, the change makes sense. Merging it in!
☀


checkDataSignature issue

It appears as though despite your fix here, the issue persists in the sense that the /dist folder in your compiler (using npm) is perhaps outdated and needs to be rebuilt as the logged output of the expected types still reflect the naming and type convention prior to your fix? It makes it unusable and the compiler complains either way.

Thanks for reporting the issue. Indeed, PR #50 did not update the src/imports/stdlib.ts file.
That file has been update in the main branch since. I'll cut a new release (v1.2.0) this week, so this issue will go away.
In the meantime, a workaround would be to replace the existing entry files['std/crypto.tact']  in dist/imports/stdlib.js with the following:
files['std/crypto.tact'] =
    'QG5hbWUoY2VsbF9oYXNoKQpleHRlbmRzIG5hdGl2ZSBoYXNoKHNlbGY6IENlbGwpOiBJbnQ7CgpAbmFtZShzbGljZV9oYXNoKQpleHRlbmRzIG5hdGl2ZSBoYXNoKHNl' +
        'bGY6IFNsaWNlKTogSW50OwoKQG5hbWUoY2hlY2tfc2lnbmF0dXJlKQpuYXRpdmUgY2hlY2tTaWduYXR1cmUoaGFzaDogSW50LCBzaWduYXR1cmU6IFNsaWNlLCBwdWJs' +
        'aWNfa2V5OiBJbnQpOiBCb29sOwoKQG5hbWUoY2hlY2tfZGF0YV9zaWduYXR1cmUpCm5hdGl2ZSBjaGVja0RhdGFTaWduYXR1cmUoZGF0YTogU2xpY2UsIHNpZ25hdHVy' +
        'ZTogU2xpY2UsIHB1YmxpY19rZXk6IEludCk6IEJvb2w7Cg==';

Legend, its building now, thanks for the prompt response

Just made a new v1.2.0 release. This should be fixed now. Feel free to reopen if it's somehow not fixed :)


 inside tooltip not receiving clicks

Hi there,
I'm trying to use a tooltip to render a URL input next to a div when I click on it (in my example code, I changed it to dblclick, so the click on the input doesn't close the tooltip). It displays, and all seems well -- however, I cannot click on the input. I can't seem to get focus. I tried setting the z-index of the input to an extremely high value (10000, then something like 99999999), but that didn't help. I also set isCapture={false} on the ReactTooltip component, but that didn't help either.
Here's my code (snipped a bit for brevity's sake):
<PostPlaceholder data-tip data-for="post-prompt" data-event="dblclick" />

<ReactTooltip id="post-prompt" className="post-prompt" place="right" eventOff="dblclick" effect="solid" isCapture={false}>
  <input type="url" placeholder="https://www.instagram.com/..." />
</ReactTooltip>

Could you please tell me what I'm doing wrong, or whether this is a bug/unexpected behavior? Thanks in advance!

This is probably because the tooltip has the pointer-events: none CSS declaration; change it to pointer-events: auto and you'll be good to go.

@ZLevine Thank you you helped me a lot! I thought it was a z-index issue.

@aronhelser This probably should be a property option "clickable" or something right?

That's a good idea! Hopefully someone can work on it and submit a PR.

@aronhelser I would like to work on this if okey?

yes, absolutely!

:tada: This issue has been resolved in version 3.10.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

I'm a bit late to the party, but it's awesome to see this fixed! Thank you everyone for answering, and for fixing this issue! :tada: To be honest, I realized a bit too late I needed a popover, not a tooltip, and I was kind of abusing this tool. But hey, it's great to see this is doable with this tool now. :smile:

Hi, I'm not sure this is fixed.
From the demo site (https://react-tooltip.netlify.com/), the input is still unfocusable.

@timhwang21 You are right, the compiled style.css is missing the new allow_click class in the example site. @aronhelser Did I have to commit src/style.css and src/style.js, I see they get updated through build process.

I don't think the new build is automatically deployed to https://react-tooltip.netlify.com/, I didn't set that up. I'll have to check.

I should have also mentioned that I'm seeing the same incorrect behavior in my application using the latest version. Thanks for the quick response!

Can you look at the styles in your app that are applied to the tooltip and
see what is preventing the "pointer-events: auto" style from taking effect?
On Mon, Mar 18, 2019 at 4:11 PM Tim Hwang<EMAIL_ADDRESS>wrote:

I should have also mentioned that I'm seeing the same incorrect behavior
in my application using the latest version. Thanks for the quick response!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wwayne/react-tooltip/issues/417#issuecomment-474081687,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS_pnRnqBwDR4wkGbR7xqZCFKqTIfW0Zks5vX_L2gaJpZM4WMjOf
.

@aronhelser that fixed it... thanks!

Can you elaborate on what fixed the problem for you? Did you have to change
something using the latest version?
On Tue, Mar 19, 2019 at 6:10 PM Tim Hwang<EMAIL_ADDRESS>wrote:

@aronhelser https://github.com/aronhelser that fixed it... thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wwayne/react-tooltip/issues/417#issuecomment-474604444,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS_pnfezuBluXgYwlXDCCG4nnZ8Qn_CCks5vYWBngaJpZM4WMjOf
.

Sorry, I did in fact have a local style that overwrote that rule. The rule
is being properly applied by the library.
On Wed, Mar 20, 2019 at 9:20 AM Aron Helser<EMAIL_ADDRESS>wrote:

Can you elaborate on what fixed the problem for you? Did you have to change
something using the latest version?
On Tue, Mar 19, 2019 at 6:10 PM Tim Hwang<EMAIL_ADDRESS>wrote:

@aronhelser https://github.com/aronhelser that fixed it... thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/wwayne/react-tooltip/issues/417#issuecomment-474604444
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AS_pnfezuBluXgYwlXDCCG4nnZ8Qn_CCks5vYWBngaJpZM4WMjOf
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wwayne/react-tooltip/issues/417#issuecomment-474825115,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFj7CjI_ndJyXt9dgOCIo6hZjIkORuOdks5vYjWRgaJpZM4WMjOf
.


[Bug]: await is not defined

Package
lucia
Describe the bug
In the docs, it's written that you should write in the adpter the following code:
await mongoose.connect();

and this throws an error Error: await is not defined.
I tried to make a function called getAdapter() like this:
async function getAdpater() {
  await mongoose.connect(uri);

  const User = mongoose.model("User", userSchema);

  const Session = mongoose.model("Session", sessionSchema);

  return new MongodbAdapter(
    mongoose.connection.collection("sessions"),
    mongoose.connection.collection("users")
  );
}

export { getAdpater };

and in lucia.ts file:
export const lucia = new Lucia(await getAdpater(), {
  sessionCookie: {
    attributes: {
      // set to `true` when using HTTPS
      secure: process.env.NODE_ENV === "production",
    },
  },
});

but this don't work, so I recommend making lucia gets a function that returns an adapter or something like that (new Lucia(async () => await getAdapter())), i don't know actually...
btw I'm using nextjs and server actions

The examples uses top-level await, which may or may not be supported by your build/runtime


replace json marshalling with protojson

Signed-off-by: senthil<EMAIL_ADDRESS>

@tock-ibm As rest_client.go is auto generated code, I have not updated it and left it as is.

@tock-ibm As rest_client.go is auto generated code, I have not updated it and left it as is.

@cendhu True! I missed that.


Enrich position APIs to include total fees paid / received and funding

Enrich position APIs to include total fees paid / received and funding

https://github.com/vegaprotocol/vega/issues/10374
Core issue for this

Loss socialisation?

Addressed in https://github.com/vegaprotocol/specs/pull/2329


Manual cherrypick https://github.com/istio/istio/pull/28928

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[X] Does not have any changes that may affect Istio users.

We are freezing 1.8 branch to build a final RC in prep for tomorrow's 1.8.0 release. Will approve this and your other PRs once that is out.

Hi @bianpengyuan sure! Thanks!


WindowCovering: Update cluster definition controller + example

Problem
What is being fixed?  Examples:

WindowCovering Cluster is outdated
New Attributes and Commands required for Test Event

Change overview
This is the first part of a series of PRs to update the examples

Update the Window Covering cluster definitions following the last Specifications
Impact client/controller apps ; chip-tool chip-device-ctrl
all-cluster-app : Add basic clusters behavior into all-cluster-app
Create a folder window-covering-server to gathering common functions; helpers and definitions
Update definition and renaming some functions into EFR32 Window Covering example

Testing
How was this tested? (at least one bullet point required)

Tested via chip-tool driving chip-all-clusters-app example
./out/debug/standalone/chip-tool windowcovering stop-motion 1
[1624368915.824858][537183] CHIP:DMG:
[1624368915.824859][537183] CHIP:DMG: 	],
[1624368915.824861][537183] CHIP:DMG:
[1624368915.824863][537183] CHIP:DMG: }
[1624368915.824867][537183] CHIP:ZCL: Received Cluster Command: Cluster=102 Command=2 Endpoint=1
[1624368915.824869][537183] CHIP:ZCL: StopMotion command received
[1624368915.824897][537183] CHIP:DMG: ICR moving to [AddCommand]
[1624368915.824904][537183] CHIP:EM: Piggybacking Ack for MsgId:00000006 with msg
[1624368915.824911][537183] CHIP:IN: Secure message was encrypted: Msg ID 4
[1624368915.824913][537183] CHIP:IN: Encrypted message 0x559574eeb840 from 0x0000000000BC5C01 to 0x000000000001B669 of type 9 and protocolId 5 on exchange 39017.
[1624368915.824916][537183] CHIP:IN: Sending msg 0x559574eeb840 to 0x000000000001B669 at utc time: 318258282 msec
[1624368915.824939][537183] CHIP:IN: Sending secure msg on generic transport
[1624368915.824954][537183] CHIP:IN: Secure msg send status No Error
[1624368915.824959][537183] CHIP:DMG: ICR moving to [   Sending]
[1624368915.824962][537183] CHIP:DMG: ICR moving to [Uninitiali]
[1624368915.825172][537183] CHIP:IN: Secure transport received message destined to fabric 0, node 0x0000000000BC5C01. Key ID 0
[1624368915.825208][537183] CHIP:EM: Received message of type 16 and protocolId 0 on exchange 39017

Tested via chip-device-ctrl  driving the EFR32 window-app example

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

@vivien-apple @franck-apple
First basic PR needed before others additions
I don't have permissions to add label or reviewers


Update: mmckegg.loopdrop version 3.0.1

Removing old versions to reduce clutter
Microsoft Reviewers: Open in CodeFlow

/azp run


fix: eth_getLogs restriction failures & invalid node response

This PR fixes two things:

As of now, if our altruist were not reachable during the eth_getLogs restrictions, we would propagate an error to the user and have them not use 'latest' as an option.

This behavior is quite overkill for the purpose of this feature, and if our altruists are having a bad time then all of the systems relaying on us, and using 'latest' would take a hit until they are back up.
Solution: if we altruist is unreachable, ignore this restriction and let the relay pass with 'latest' flag. The worse that can happen is having a request from 0 to latest, but that's restricted if our altruist is up.

Invalid node responses were being propagated to the user instead of being exclusively logged and fallback to an altruist. There's no point on propagating this error to the user, it's better to only log this for our use and let an altruist serve it.

Close T-2805

Close T-2801


Mark donators in the pleblist system

Somehow a tag system based on the users paypal email?

Next step: In the pleblist host, do the fun frontend part.
Next to the donators name, there should be a list of tags and a "+" button.
The +-button will open up a modal in which you can type in the tag you want to add to the user.
Make sure the modal is fast.
API Endpoints
GET /api/v1/email/tags
Arguments
email
POST /api/v1/email/tags
Arguments
email
new_tag
GET /api/v1/email/tags
Arguments
email
new_tag

@pajlada You might also be able to remove this too due to logins being removed


Switched to cmake & added install script

Needed a make install, no change to the code

Thanks, but I'm not interested in switching to CMake.


If filename is already correct there is no opportunity to move

Title says it all -- when the filename's already correct the file is skipped before even offering to move it to the destination dir.

Fixed in 15162c7df730538e0f2ccd85b6570ce100be871c


selinuxpolicy: Consume updated deployer with selinux policy updates

We need different selinux policies based on the platform version.
Recently, changes were implemented in the deployer which can be
vendored in here.
Signed-off-by: Swati Sehgal<EMAIL_ADDRESS>

Recently, changes were implemented in the deployer which can be vendored in here.

Good.
Better: "starting with version X.Y AND/OR commit ABCDEF, changes were..."

Additional updates are needed in the controllers and hack directory. Working on that.

/retest

/test ci-install-e2e

/retest

ok, errors are not a glitch and need to be checked. Most likely unrelated to this PR

because #324 is progressing past the point this test was failing

we need extra fixes, added in #338 (preserving the base commits here)


Redirect sync log to their own log file

Do we want to redirect ONLY the debug logging to the sync log file?
Do we want to include the log from aec_peers and the rest of the log from aec_peer_connections?

I am taking the liberty to label as WIP for the moment just for reminding us not to be merged yet.

Normal review&merge rules apply. Removing WIP label.

@lucafavatella: I missed the changes in aecore_app, I'll add it; I tried addingepoch_sync.log in aecore_suitre_utils module but some tests do not seem to sync and that makes the tests fail; I'll add the mining log to system tests check; I'll update ISSUE_TEMPLATE.md.

@dincho How is this degrading docker experience ?

@sylane docker logs and docker run -it ... will stop producing meaningful output.
It's not just docker however, IMO each unix process running in "foreground" should stream it's output to the stderr/stdout. More about the reasoning.
What if you add lager_console_backend as extra backend like in the default handlers ?

@dincho  I could add {lager_console_backend, [{level, info}]} like in the default handler, but that would not change much given most of the log generated are debug lines. @uwiger, you requested the feature, what do you think about @dincho concerns?

@dincho  I added console backend for info log lines.

@dincho I though one of your concern was related to using docker/compose and these are used for that.

@dincho, do you have more issues with this PR ?

@dincho I though one of your concern was related to using docker/compose and these are used for that.

Can you point me where those dev{1..3}/sys.config is used in docker compose? AFAIK it's not, and it's used for development and testing.

@sylane Still the PR is good to go from my perspective and I already approved it, just with additional (optional) comment.


nano: 2.6.2 -> 2.6.3

Motivation for this change
Update nano to the last version
Things done

[X] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Thanks a lot for the feedback and sorry for the delay.
I don't use mac neither clang so I can't help much but that line is inside of a #if defined(__linux__) block.
See http://git.savannah.gnu.org/cgit/nano.git/tree/src/winio.c#n516

Just to clarify, I was referring to the nano changelog; it looked innocent, but obviously wasn't. As long as this doesn't block anything, I suppose we can just wait for a darwin user to notice and debug this ...

This bug is already fixed in master.
https://savannah.gnu.org/bugs/?48751
http://git.savannah.gnu.org/cgit/nano.git/commit/?id=928a24c20444a652212e544a506ed55c44efdf3b
Which would be the best solution, a patch, or revert to the 2.6.2?


Bundler: Fix permission error when vendoring gems

This fixes a permissions error when vendoring gems, when GEM_HOME was
unset it defaulted to /var/lib which isn't writeable.
Attempting to fix the discrepancy between ci and updater here:
https://github.com/dependabot/dependabot-core/pull/3279

Could we somehow test for this?

Yes attempted to do it here https://github.com/dependabot/dependabot-core/pull/3279 but looks like it's breaking a whole tonne of stuff in the process so keen to get this out to fix the issue in prod and then try and get that PR working.
I can reproduce it in the dev container and the vendor specs also fail in the dev container but pass in the ci container because they run as root.

@jurre reproduced the failure here https://github.com/dependabot/dependabot-core/runs/2122196759 🎉

Tested successfully on staging https://github.com/dsp-testing/feelepxyz-testing-git-bundler/pull/12/files


Adding system inktoolbar styles to winui

Description
InkToolbar original version from the OS Xaml styles. Next PR will be incremental on top of this to show the changes.
Motivation and Context
This is InkToolbar original version, winui style updates will be made on top of it
How Has This Been Tested?
Visually verified and test to ensure that the control loads.
Screenshots (if appropriate):

/azp run

Please add screen shot for light mode/ dark mode and random high contrast mode.

/azp run

InkToolbar_OS.docx


Use 'null' instead of 'nil' for json

When describe json response, 'null' is better than 'nil' which is not in
json specification.
Signed-off-by: Yi EungJun<EMAIL_ADDRESS>

agreed, LGTM

LGTM


Update controls prompt icon hand SVG to work with all types of models

Description
The current hand icon svg isn't easily visible for some models. For example, a model that has a lot of white will make the prompt hard to see:
https://abalone-diplodocus.glitch.me/
One solution would be to allow the hand colour to be customized, but that won't work in cases where the model-viewer doesn't know what the input glb will be in advance.
A better solution is to have an icon that works in all scenarios, regardless of background and model materials.
What do you think of something like this:

Proposal
Current

Demo: https://elite-pincushion.glitch.me/

Demo: https://translucent-lunch.glitch.me/

🤷♂ I like the proposed one, subjectively speaking. It's nice that it has a contrasting outline. WDYT @elalish ?

I like it a lot. I'd take a guess they've put more thought into it than we ever did.

Sorry, I just mean they have more resources dedicated to UX design than we do (at least currently).

@maaslalani @pushmatrix is it okay just to take the icon from your demo Glitch? Are you gifting that to our project?

@cdata We are gifting it :), but let us trim it down a bit. I think it has emojis and in the svg for some reason and lots of extra cruft.


New password must be different from the current password

I am not sure if that matters. If you forgot your password, then entering the same one is "new" to you.

@levlaz Yaa true


[CP] Generated Plugin Registrant Null Safety Fix

issue_link
https://github.com/flutter/flutter/issues/109160
Commit Hash
5aad12c
Target
beta
pr_link
https://github.com/flutter/flutter/pull/109906
Impacted Users
All web builds without null safety that target the current beta release
Impact Description
Web is unable to build and releases cannot be made.
Workaround
The only workaround is to use the stable channel or an older build, but unfortunately the current stable channel has other major issues for web that makes using the beta channel very appealing at the moment.
Risk
low
Test Coverage
yes
Validation Steps

Create a flutter application without any null safe code and set the sdk constraints as sdk: ">=2.11.0 <3.0.0" to disable null safety features
Run flutter build web --release
Build should be successful

@yjbanov could you take a look at this cherry-pick request?

LGTM


support for Laravel 9

@Stackedwisdom  what does these changes triying to address as it seems lot of small changes


[FEATURE]: Allow onConflict in SQLite text primary keys

Describe what you want
You can create an integer column with autoIncrement and onConflict properties like the following:
const id = integer('id').primaryKey({ onConflict: 'abort' });

However, text column primary keys does not accept an argument with the onConflict property.
const id = text('id').primaryKey({ onConflict: 'abort' }); // Expected 0 arguments, but got 1

It would be helpful if we could configure the onConflict parameter in other column types as well.

Closing in favor of #200.


clean up di module in core.database package

Thanks for submitting a pull request. Please include the following information.
What I have done and why
Include a summary of what your pull request contains, and why you have made these changes.
Fixes #<issue_number_goes_here>
Do tests pass?

[ ] Run local tests on DemoDebug variant: ./gradlew testDemoDebug
[ ] Check formatting: ./gradlew --init-script gradle/init.gradle.kts spotlessApply

Is this your first pull request?

[x] Sign the CLA
[x] Run ./tools/setup.sh
[x] Import the code formatting style as explained in the setup script.

Thanks for doing this. In future, please include a very brief description of what you have done and why you've done it in the pull request. In this case it could just be:
The package for DaosModule was incorrect. It should be under the di package. I have moved it.

Thanks for doing this. In future, please include a very brief description of what you have done and why you've done it in the pull request. In this case it could just be:
The package for DaosModule was incorrect. It should be under the di package. I have moved it.

Thanks for your feedback. as i accepted your comment, i edit my first pull request description message in which additionally describe '[what i have done]', '[why i have done]'


Add values functions

I was trying to do something similar to https://stackoverflow.com/questions/34708509/how-to-use-returning-with-on-conflict-in-postgresql/42217872#42217872
WITH input_rows(usr, contact, name) AS (
   VALUES
      (text 'foo1', text 'bar1', text 'bob1')  -- type casts in first row
    , ('foo2', 'bar2', 'bob2')
    -- more?
   )

But I don't think there is a VALUES function.

Looking at it, the WRAP function will be needed for that https://github.com/go-jet/jet/pull/67

Looking at it, the WRAP function will be needed for that https://github.com/go-jet/jet/pull/67

Yeah, VALUES statement is not implemented yet.
SELECT can be used for one row and SELECT with UNION ALL can be used for multiple rows. For instance:
input_rows := CTE("input_rows")

stmt := WITH(
	input_rows.AS(
		UNION_ALL(
                        // first row columns has to be aliased
			SELECT(String("foo1").AS("foo"), String("bar1").AS("bar"), String("bob1").AS("bob")),
			SELECT(String("foo2"), String("bar2"), String("bob2")),
		),
	),
)(
	SELECT(input_rows.AllColumns()).
		FROM(input_rows),
)

Yeah, VALUES statement is not implemented yet.
SELECT can be used for one row and SELECT with UNION ALL can be used for multiple rows. For instance:
input_rows := CTE("input_rows")

stmt := WITH(
	input_rows.AS(
		UNION_ALL(
                        // first row columns has to be aliased
			SELECT(String("foo1").AS("foo"), String("bar1").AS("bar"), String("bob1").AS("bob")),
			SELECT(String("foo2"), String("bar2"), String("bob2")),
		),
	),
)(
	SELECT(input_rows.AllColumns()).
		FROM(input_rows),
)

Can you use some public interface in UNION_ALL instead of private jet.SerializerStatement?
When I want to update several rows I have to write something like:
selects := make([]postgres.SelectStatement, 0, len(events))
for _, event := range events {
  // selects filling
}
var eventsToUpdateTable postgres.SelectTable
if len(selects) == 1 {
  eventsToInsertTable = selects[0].AsTable("events_to_insert")
} else {
  set := postgres.UNION_ALL(selects[0], selects[1])
  for i := 2; i < len(selects); i++ {
    set = postgres.UNION_ALL(set, selects[i])
  }
  eventsToInsertTable = set.AsTable("events_to_insert")
}

and I got something like union all (... union all(... union all(...)))
It would be nice to write at least:
selects := make([]postgres.SelectStatement, 0, len(events))
for _, event := range events {
  // selects filling
}
if len(selects) == 1 {
  eventsToInsertTable = selects[0].AsTable("events_to_insert")
} else if len(selects) == 2 {
  set := postgres.UNION_ALL(selects[0], selects[1])
  eventsToInsertTable = set.AsTable("events_to_insert")
} else {
  set := postgres.UNION_ALL(selects[0], selects[1], selects[2:]...)
  eventsToInsertTable = set.AsTable("events_to_insert")
}

but golang fails to use postgres.SelectStatement slice as slice of private jet.SerializerStatement

Can you do it something like this - https://github.com/go-jet/jet/discussions/301#discussioncomment-7911048?

There is a possibility of a small performance penalty for the huge number of rows, but the result should be the same.

So why not fix it and stop adding:

Performance penalty.
Code complexity.
?


JFXDecorator scales off the stage

I am encountering a scaling issue with JFXDecorator. If I try to scale the scene the controls on the right side of the decorator and the right side of the borderPane are always drawn off the stage. I can only see the controls if I resize the window to a much smaller width, but only a portion of the full screen icon.
To see this behavior, try using the demo application and adding the following two lines of code to MainDemo.java and add the import of javafx.scene.transform.Scale :
Scale scale = new Scale(2, 2);
scene.getRoot().getTransforms().add(scale);
Is there something I am missing when I attempt to scale the scene using javafx.scene.transform.Scale?

Hello @bmoore27,
Well, JFXDecorator is also a Node and it's the scene root, so you are scaling the decorator itself instead of its content. You need to scale the content of the decorator instead of the decorator itself.
I tried it myself, and it seems there is a minor clipping issue that needs to be fixed when the content is scaled.
Thanks @bmoore27  for pointing out the issue 👍
Regards,

I pushed a fix for the minor clipping issue, it will be part of the next release.
It works now, when the decorator content is scaled.

Thanks @jfoenixadmin for the update. I appreciate the quick attention.
I intended to scale the decorator and the content. My goal is to define a few layouts for varying aspect ratios/display densities and then scale to fill in between.


Provide a useful error if server appears to already be running during the server end to end test

I was poking around for a couple minutes and couldn't find the offending port, or an open terminal. This makes it easier.

+1.

+1