Doc: Added <> operator in getting started

Codecov Report

Merging #910 (e240e25) into main (23011a9) will increase coverage by 0.22%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #910      +/-   ##
==========================================
+ Coverage   53.40%   53.62%   +0.22%
==========================================
  Files          73       73
  Lines        2159     2178      +19
  Branches       54       54
==========================================
+ Hits         1153     1168      +15
- Misses       1006     1010       +4

Impacted Files
Coverage Δ

...ttp/src/main/scala/zhttp/service/HttpRuntime.scala
53.19% <0.00%> (+17.47%)
:arrow_up:

Continue to review full report at Codecov.

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


Update scalameta to 4.4.1

Updates org.scalameta:scalameta from 4.3.24 to 4.4.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalameta" } ]

labels: library-update, semver-minor

Codecov Report

Merging #866 (730e62c) into master (0f0873c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #866   +/-   ##
=======================================
  Coverage   82.82%   82.82%
=======================================
  Files          73       73
  Lines        5409     5409
  Branches      148      148
=======================================
  Hits         4480     4480
  Misses        929      929

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 0f0873c...730e62c. Read the comment docs.


multiple apps with a single button

you know, a microservice/microlith thing as a button

Please be more descriptive. I cannot understand what you’re saying.

[
  {app1},
  {app2}
]

Are you thinking for monorepos or for multirepo?
Also, you could do this today with a pre/post create script, but that is kinda messy.

I think for both... but the use case I have in mind is in 6 different repos (although if I had the time and energy I would merge them to one monorepo)
What about adding support to specify image: in the app.json ? like this way the button could be anywhere..?

But really what I'm talking about that if I have an app that has services like "frontend" that connect to  "billing" and "users" and as a true microlith does... then it would be cool to deploy that kind of app with one click.

What about adding support to specify image: in the app.json ? like this way the button could be anywhere..?

Can you elaborate on that?

good question - I started to explain and I realized that it would mean that the image version is set to something and it's not updated when the repository is updated. so scratch that.
So yeah, something like
[
  {app1},
  {app2}
]

or
{
  name: "mainapp",
  env: {...},
  subapps: [
    {
       name: "mainapp-sub1"
       env: {....
    },
    {
       name: "mainapp-sub2"
       env: {....
    },
  ]
}

This came up in other forms like "can you add support for docker compose".
Right now, there's nothing preventing someone from deploying a multi-tier application by placing 2 different buttons in their readme with ?dir= parameter.
Since there's not enough demand volume, I'm not sure if it will be worth rearchitecting everything.

Sure that works. So for a six service app you need six buttons.

Suggest close. Multi isolated services with multi buttons works now. Multiple things on one install button (like docker-compose) logically extends to something like Terraform. So I feel like the outstanding scope of this issue is a dupe of (https://github.com/GoogleCloudPlatform/cloud-run-button/issues/137)


Added type definitions for typescript

What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[ ] Bug fix
[x] New feature
[ ] Other, please explain:
What changes did you make? (Give an overview)
Added typescript definitions to this library.
Which issue (if any) does this pull request address?
Is there anything you'd like reviewers to focus on?

Doesn't there also need to be a "types" key in package.json?

Doesn't there also need to be a "types" key in package.json?

Oh, maybe. I'll look in to it.

Looks like it's advisable: https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html#including-declarations-in-your-npm-package

Fixed!


Generate release?

Would it be possible to generate a release for these extensions on github? Thanks!

In progress right now.

I set up a couple of GitHub Actions workflows for this (something we've been working on across the Apicurio projects).  One of those workflows is a Release workflow, which I triggered to generate a 9.0.1.Final release of this project. :)
Part of that should be a release into Central.  Give it an hour or two and hopefully it should be there!


Feat/civ 5680 | CCJ repayment plan

JIRA link
https://tools.hmcts.net/jira/browse/CIV-5680
Change description
Adding a screen to show payment options for repayment, containing the payment amount, first payment date and frequency of payment
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

Closing as pipeline build errors
Opening a new one as advised by Sampan


Problem running  RNN PTB sample on both Linux and Windows

during running the RNN PTB sample lstm_ptb.py, it fails while calulcalting NLL due to zero len label vector here:  nll = -np.sum(np.log(seq_label_probs.asnumpy())) / len(X[0,:])
Logs:
Loading ./data/ptb.train.txt, size of data = 929590
Unique token: 10000
Loading ./data/ptb.valid.txt, size of data = 73761
Unique token: 10000
Vocab=10000
Training with train.shape=(46445, 20)
Training with val.shape=(3675, 20)
batch_size=20
seq_len=35
Epoch [28] Train: NLL=19.903, Perp=440413635.196
Epoch [56] Train: NLL=18.576, Perp=116847727.676
Epoch [84] Train: NLL=17.796, Perp=53529230.425
/home/hanyh/MXNet/mxnet/example/rnn/lstm.py:184: RuntimeWarning: divide by zero encountered in log
nll = -np.sum(np.log(seq_label_probs.asnumpy())) / len(X[0,:])
Epoch [112] Train: NLL=inf, Perp=inf
Epoch [140] Train: NLL=inf, Perp=inf
Epoch [168] Train: NLL=inf, Perp=inf

I noticed this a well. For me on os x. But the issue is not that len(X) is 0, its that you are taking logs of zeros. The probabilities assigned by the output layer have lots of zeros in them so np.log(0) gives an error.

Looks like the same issue as https://github.com/dmlc/mxnet/issues/1322


Commonize shared xacros and robot_hw constants

yeah. I think its best to keep it as just a string until we create a package for it to avoid duplicate definitions everywhere. Probably like a top level uwrt_mars_rover_hw package like what i did for shared custom interfaces in the ros1 branch
Originally posted by @wmmc88 in https://github.com/uwrobotics/uwrt_mars_rover/pull/171#discussion_r783400593

Not sure if this should be a single package or multiple. Stuff that needs to be added includes iq_current hw state, any sort of shared transmission stuff, shared xacros, custom controllers?
I could see these being split up into their respective uwrt_mars_rover_description,(xacros), uwrt_mars_rover_hw(shared state handles, shared custom transmissions) and uwrt_mars_rover_controllers packages(shared custom controllers).

I agree. I really got to learn how you create issues from comments of other PRs - that's just too cool.

I agree. I really got to learn how you create issues from comments of other PRs - that's just too cool.

Right here: https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-discussion


Fixes & reformat

This PR has commits that are mostly sane, to clean up the build process. Headers names are now uniform, inclusion use quotes " for project headers and angle brackets for standard libraries. CMake now enforces C++11, and adds compiler warnings. CMake can also be used to build packages for all OS, and I started to work on that.
Commit 0c54dd7 fixes all warnings I encountered, and also simplifies the code.
The controversial commit is e1498d5 that formats the whole project according to the Google C++ Style Guide, using the clang-format tool. IMO, this document should be loosely followed, but the style guide is useful to enforce uniform coding style across the project (for instance, many files were using mixed indentation with tabs and space).
This commit can be dropped if too controversial, the main problem is that it is impossible after that to follow the history line-by-line (git blame) because it effectively rewrites all the files. If you prefer to chose another style, this is easy. I don’t want to spend time creating a style that follows as much as possible NeneQuest current state, because NeneQuest is not consistent.
cd nenequest
clang-format -i src/**/*.cpp headers/**/*.hpp

I'm quite surprised you tried to improve the current state of the coding style we have there. I'm actually started to purge and rework a lot of the stuff we made because we took way too complexes approaches for a such a simple project, and add to this the fact that some of us were using C++ for the first time (at least it was my case), it is now currently very difficult to dig into and improve it.
I'll take a look at your changes as soon as possible.

Okay, took a brief look into it. I'm okay with the Google coding style guidelines, but I guess we can use any sort of coding style guideline as long as it looks somewhat clean. Instead of using an external software, I think it should be better to configure our respective IDEs with the said guidelines, to avoid that history rewrite you mentioned.
The CMake update is nice. I redid it on my end but since I'm absolutely not familiar with it, your input is more than welcome, thanks for that.
However I have purged a lot of the files you worked on, so normally I'd keep this PR into a separate branch and merge it on other actives branches, but since my edits are only local on my machine because others were busy when I got back into the project, there's no really use in keeping this PR aside imo.
I'm fine with this branch being merged on master. I'll wait a bit for others to comment on it too. I don't know if they tried to also rework on the project.
cc @engboris @KostiaChardonnet @hokolomopo

Salut

I agree with the convention except for the fact that * and & are close to the type instead of the parameter. For example in dragon.cpp, line 176 you have
void Dragon::draw(sf::RenderTarget& target, sf::RenderStates states)

Instead of
void Dragon::draw(sf::RenderTarget &target, sf::RenderStates states)

Aside from that I'm fine with the PR (with my previous commit).

Sorry for the force-push.
I just integrated some remarks made privately by @KostiaChardonnet into the relevant commits.
There were some CMake fixes, and the alignment of pointer stars and references to right.

The PR has problems with the order of headers. Please, do not merge for the moment.

I was fine with type* param instead of type *param lol.
Also @KostiaChardonnet , you shouldn't push on someone else's PR (and even less force-push on it), because it can breaks the history of the PR like any git repo, but also because it's not your work. Instead, you can make comments on lines when reviewing a PR, or wait until the PR is merged on the main project.

because it's not your work

For @KostiaChardonnet's defence, we were together and I was curious to see if he could actually force-push to the branch. But you’re right in the general case.

The PR has problems with the order of headers.

Fixed.

I agree with the convention except for the fact that * and & are close to the type instead of the parameter.

I was fine with type* param instead of type *param lol.

For me, the problem with left-align appears with multiple declarations:
int* a, b, c;
int *a, *b, *c;

In that case, left-align is not desirable. But I would say that * and & should be part of the type… My preference goes to right-align.

Please, do not merge for the moment.

Sorry for the multiple force-pushes. I’m now more confident that the PR is good to go.
There is still one thing missing: NeneQuest is not able to load assets and configuration from a given path, defined at compilation or run time, so the CMake installer does put the files in sensible locations, but NeneQuest can’t use them.

Okay, I'll try to build with both cmake and windows's cpp compiler when I'm back home and merge the PR if it works.

okay so my Visual Studio environment can compile the program without any inch.
However, CMake isn't working properly, since it tries to use the x64 compiler with my 32bit SFML library. I tried to edit CMakeList.txt to specify a Win32|Debug target but without real success. I managed to generate the whole Visual Studio solution once with a Win32|Debug configuration but it couldn't compile properly, and I think I used a default CMake configuration for it.
I didn't tried to make it work on WSL yet.

I believe you are the only one working on Windows so @MisterDA can't help you. Do you think you can make a OS-dependent build system ?
I have no problems making it work on WSL.

Well, CMake is supposed to be cross-platform, so it creates the building scripts/process for any OS supporting CMake.

I believe you are the only one working on Windows so @MisterDA can't help you. Do you think you can make a OS-dependent build system ?

Is this project still alive? I'd be more than happy to contribute a custom build script/toolchain for Windows MinGW-64

Hello. Thank you for your interest. This project has been abandoned for a long time. I believe that the main problem was a lack of hierarchy, organisation and anticipation. As a result, the project became more complicated than needed (treating a small and simple project as a big ambitious project with a lot of superficial and extensible structure).
Maybe the best solution would be to start from scratch with something simpler (but keeping some functions and ideas, otherwise it would be a waste). If you're motivated enough you're free to use our resources.

Hello. Thank you for your interest. This project has been abandoned for a long time. I believe that the main problem was a lack of hierarchy, organisation and anticipation. As a result, the project became more complicated than needed (treating a small and simple project as a big ambitious project with a lot of superficial and extensible structure).
Maybe the best solution would be to start from scratch with something simpler (but keeping some functions and ideas, otherwise it would be a waste). If you're motivated enough you're free to use our resources.

Thanks! I would be interested to sift through your existing structure and make major changes if need be. I do understand the concept of keeping it simple, but as some of you had mentioned you were new to C++ at the time, and you can only gain plenty of experience in working on a fun project such as this one.
If you could make a pull request to update the latest changes from KostiaChardonnet:master as they have made additional contributions that haven't made it into the official master branch. I'd really like to just go over it and see if it will be a fun project to work on fwiw.

Hi @jmscreation : I actually wanted to finish this project for a while now, I would like to work on it with you if you want. As you said, my branch have a bit more contribution, we can work on it for now, and then pull everything on this repo once its over.

Hi @jmscreation : I actually wanted to finish this project for a while now, I would like to work on it with you if you want. As you said, my branch have a bit more contribution, we can work on it for now, and then pull everything on this repo once its over.

Awesome.
Do you want me to fork yours, or do you want me to directly collaborate on your repository?

I'd be more than happy to contribute a custom build script/toolchain for Windows MinGW-64

CMake should handle that for us.
Good luck ;)

I actually hate CMake quite a bit. I already made a build script for this project that works rather well.


missing next_game_id for double headers in MLB

will be fixed in 0.1.9 which will be released shortly


Accessing Web GUI from EC2 instance running on http://<IP_ADDRESS>:20075/

Thanks for the great product!
I am running zenbot on aws ec2 Ubuntu 16.04. When trading there is an ability to connect to a web available gui -- "Web GUI running on http://<IP_ADDRESS>:20015/"
Any hints or tips to access this Web GUI through ec2 instance? I tried using public_IP:20015 and adjusting security groups but haven't been able to get it to work.
thanks in advance!

Please post zenbot questions in our subreddit: https://www.reddit.com/r/zenbot/
The github issues is reserved for bugs and features.
Thanks!


ci(docker/debian): upgrade debian to bullseye

This PR upgrades all debian-based images to bullseye release. The stretch release is no longer maintained and supported by debian official docker image.

Have tested bullseye-compiled binary that successfully ran on centos:7 image. Plugins also worked well (loaded and executed).


vn_VN to vi_VN

Hello,
Riot announced in this tweet that "Vietnamese language code changed from vn_VN to vi_VN". The LOCALE enum in<EMAIL_ADDRESS>still has vn_VN and not vi_VN. Maybe this needs to change?

@frodos47 good spot, will get this sorted!

@frodos47 sorry for the delay but this has now been fixed

@OllieJennings Happy to help. Thx!


neovide: 2022-02-04 -> 0.8.0

Description of changes
Update Neovide to a released version.
If you test this version of neovide, please run NixOS unstable to avoid following issue https://github.com/NixOS/nixpkgs/issues/168769
Things done

Built on platform(s)

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.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

[x] Fits CONTRIBUTING.md.

works here but the CI fails on darwin.

If you test this version of neovide, please run NixOS unstable to avoid following issue #168769

You also need a new libGL library just for neovide.

It is not easy to add Darwin support:
https://github.com/NixOS/nixpkgs/pull/146052
https://github.com/NixOS/nixpkgs/pull/145526
Since every failed, I will remove Darwin from supported platform.

since neovide is broken on unstable apparently and darwin is not straightforward, we should not put the burden on the current maintainer, if a darwin user wants to comaintain it, fine meanwhile let's merge this.


Can you translate the output log of the script into English?

fujtisu-support_check-warranty-status.ps1

Hi @sinneh,
that's a good idea.
A few minutes ago I pushed a new version of the script. The default language is english. Other translations are welcome.
You can found the newest version here. Please try it out.
Best regards,
Daniel

Thank you for your great work，test work is normal


Alerting user for unusual behaviour

We need to alert the user at the time of the unusual behaviour of the target. This behaviour can be failing of monitoring which can be due to the target being in a downstate, irregular length of response beyond the threshold value, and other reasons.
The alerting medium can involve many ways like mail, slack messaging by bots etc.
The entire implementation should be done as an independent module just like /tsdb.

@Harkishen-Singh I am interested to work on this. Can you give me some context on how to approach this? Do you have some design or methodolgy to acheive this in your mind ? Thanks.

@JayjeetAtGithub Thanks for your interest in the project. The one way, it can be achieved to check if there is any problem in the server is, initially for all the requests the minimum and threshold response length value can be recorded separately, and for every further request if the response length exceeds or lessens the response length we can be assured of any error in the route and alert the user.


Editor enhancements

[x] Don't apply empty content from the editor (CartoCSS or SQL), requested from https://github.com/CartoDB/cartodb/pull/9262#issuecomment-237203212.
[x] Don't apply SQL with ; at the end (fixes #9071).

CR: @nobuti

ping! :)

👍

Feedback applied :)


[Improve] Fix multiple versions scala warning when building project

Purpose of this pull request
fix https://github.com/apache/incubator-seatunnel/issues/1170

Check list

[x] Code changed are covered with tests, or it does not need tests for reason:
[x] If any new Jar binary package adding in you PR, please add License Notice according
New License Guide
[x] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs

@wuchunfu PTAL,Thx


Update Components To Use Lastest Styles And Icons

💡 Description
The header component is using classes to apply styles. Need to update all the components to do the same.
Now that the icons are part of the library the components need to replace placeholders with the actual icon.
⚔ Parent Epic / Related Tickets
No response

Updated Chip, Pagination and Tag.
Breadcrumbs, FeaturedLinkListItem and TextField are expected to be rewritten or have major changes so will hold off on those for now.
Card is to be left alone for now.


[Improvement] Use build options instead of config file

Hi, After reading the script used to build the versions. Here is a tip.
https://jekyllrb.com/docs/configuration/options/#build-command-options In build command options, Why not use the -b flag instead ?
This way we can move from having to create multiple config files.

@annegentle

I think it could be done either way. By encoding baseurl in the _config.yml and _config.4.1.1.yml and so on files, the branches can continue to have those config files so you know precisely what the build used in the past, rather than having to look through logs to see what was passed to the -b parameter at build time. Probably six of one, half a dozen of the other.


Report line and column numbers wherever possible

I'm going to start work in a fork (https://github.com/benedfit/jade-lexer) to report line and column numbers for tokens, and any errors encountered during lexing. Will keep you posted on my progress

Excellent, I've been thinking we should do this for a while.  Specifically, it has the potential to allow us to support source maps.

The sheer volume of test cases to check makes this quite a task, I'm making headway, but it's slow going

70+% of test cases are now working, so I hope to have this cracked next week. I've be merging in upstream as I go to keep up-to-date

@benedfit cool thanks!

This has been merged :+1:


Handle dry point

@WPringle Please document the problem and your current solution. Thanks.

currently, the issue is that a large amount of mesh nodes are dry (NaN water elevation) throughout the ensemble space. These nodes are not all colocated, and such one particular mesh node might be dry in one ensemble member and wet in another. This is problematic for the polynomial fitting, as it expects to be fitting to a continuous function of water elevation.
The initial solution was to assign all dry nodes in the study area a minimum (near-zero) water elevation value. This allowed the polynomial to run, but it is not an ideal solution because the minimum value acts as a totally flat plateau of water elevation, and the accuracy of the resulting surrogate reflected that.
The new solution is to assign dry nodes a "real" water elevation with linear falloff away from the nearest true wet node. This allows the polynomial to fit to a gradient curve instead of to a discontinuous plateau.


.NET Core compatibility

We aim to produce fully-fledged cross-platform solution, and we already support two common CLI implementations: Windows CLR/.NET and cross-platform Mono.
A couple of days ago .NET Core was released, and I think that we want to support it. We'll need to estimate any code and/or infrastructure changes required to add .NET Core support.
Maybe we'll want to define it as our main target platform, because, if I understand correctly, all existing Mono and CLR implementation are somehow compatible with .NET Core (i.e. it's a common denominator), and the new set of .NET Standards is a nice way to define compatibility level of our project (e.g. if we're compatible only with the latest desktop runtime versions then it's sufficient to declare netstandard1.6, and we should try to support most of the lower versions in our own runtime components to make sure programs compiled by Naggum may be run anywhere).

I'll research the current situation and report back here before making any big decisions.


(Testnet Verification) Data migration isn't working on testnet 3.13 release

Description
A clear description of the bug is:
The old deployment from the old testnet version isn't showing up in their deployment page list on the new testnet release.
they are only showing on the your contracts page.

They are not showing on any deployment page, and they aren't even showing as failed to load deployments.

Must include any relevant identifiers, like:

Network: Testnet

Version: 2.3.0-alpha12

Twin ID: 579

Contract ID: different solutions can be found in the picture, contracts ID from 31110 to 31126.

Logs/Alerts
Must include if available:

Logs/Alerts.

dashboard (3).txt

It's still not shown; the testnet needs a new release.

Verified, Testnet 2.3.0-rc3.
VMs

Orchestrators

Solution


Migrate to xstate v5

Just finished with our migration to xstate and now have to migrate to a new version.
https://stately.ai/blog/2023-12-01-xstate-v5#migration-and-breaking-changes
But it does sound like there are plenty of improvements.
Migration guide is here.
https://stately.ai/docs/migration
I've not dug into it yet.

Happy to help if you need.

Ok kicking off the migration discussion again. I just got access to the codebase and will share feedbacks and thoughts here.


Save signature to image

Save a png or image format file using dart:io onto the native device.
Figure out a way to use picture recorder and save to image format.

Figured out the solution


Better dependencies within the anchor repo for development

Doing #716 , i had to iterate the ts lib and test through anchor test
Currently everything points to the global possibly present @project-serum/anchor
For dev purposes i added a package.json so i could build the ts package then use it.
  "name": "events",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "dependencies": {
    "@project-serum/anchor": "file:../../ts"
  }
}```
Should all tests have better dependency management? This will also avoid painful management when someone switches to a PR touching both sides.

Using package.json files in every example/test is a good idea.

@armaniferrante I can take this one (per discord convo).

@armaniferrante I can take this one (per discord convo).

Please do!


Various timeout parameter should be durations instead of int

New Issue Checklist

[x] I have searched for a similar issue in the project and found none

Issue Description and Steps
Currently Dio uses ints to represent milliseconds through out the code. Ideally this should be replaced by Durations to make it easier to read and safer to work with.

Sounds good, we should probably plan a 5.0 release where we can break this.

Sounds good, we should probably plan a 5.0 release where we can break this.

Is there a discussion/board for a 5.0 release?

No, there is no board. But I can probably set one up and add a 5.x branch later.

Fixed by #1376


Release pipeline should upload to packages.grpc.io

Currently, only daily builds are published to packages.grpc.io. It'd be great to unify the release process such that we also archive official release points on that website, which will automatically resolve issues like https://github.com/grpc/grpc/issues/18260. In fact, it would simplify the life of the release manager if they could click a button and the release showed up there and then language owners uploaded from there, instead of hunting for the build package files. This should be quite straightforward and probably requires only minimal changes to grpc_publish_packages.sh script.

Just a note: once this is done, it would probably be helpful to update the installation instructions in the markdown file in this repository to point out that the binaries can be downloaded from here (along with an example using curl and tar). Right now the instructions just say to build from source. Thanks!

You're welcome to come back help us with this, @mehrdada :D

@nicolasnoble it's really hard to test things without proper access :)

Let me know if there's anything I can do to help!

I'm generally not opposed to this, but we're recently added some steps (e.g. nuget package signing) that would need to be figured out first.
Did you mean this script?
https://github.com/grpc/grpc/blob/master/tools/internal_ci/linux/grpc_publish_packages.sh

@jtattermusch yes, I think it is mostly parameterized. Somehow we need to make Kokoro pass the right branch name.

Any updates?

No updates as of yet. But we're planning work for the next quarter soon, so it's possible it'll be prioritized.

What we currently have is automatic uploading of nightly builds to our jfrog artifactory nuget channel, which is something that could relatively easily be done for other languages too.
See https://github.com/grpc/grpc/tree/master/src/csharp#nuget-development-feed-nightly-builds
The challenge with pushing the official packages is that those packages need to be signed (needs t be done on a different VM because of infrastructure limitations) for some languages (C#) and during the build you'd need to specify a "flag" that this is THE build that should upload the official packages (we don't want official stable packages accidentally uploaded by mistake and also for some languages, you can only upload given package version once, so there's no way to fix an accidentally pushed wrong package)

Not stale.

We acknowledge this to be a valid feature request but since no one has come forward to implement this, we are going to close it for now while maintaining the label/Help wanted to indicate that this can be picked up as future work.


Make it build against other GHC versions

https://travis-ci.org/filib/ruby-marshal

Done for HEAD and 7.8.10. Not doing 7.6.3 unless someone wants it.


[clang-format] Turn off include sorting.

:shipit:

:shipit:

Skipping CI build for non-build config file change.


No colors for iOS 14 SwiftUI

I followed the guide: https://github.com/CocoaLumberjack/CocoaLumberjack/blob/master/Documentation/XcodeColors.md
and when I declare: [[DDTTYLogger sharedInstance] setColorsEnabled:YES];    // Enable console debugging colors it says:
Cannot find 'sharedInstance' in scope
this is how I first declared it: DDLog.add(DDOSLogger.sharedInstance) // Uses os_log because if I do [DDLog addLogger:[DDTTYLogger sharedInstance]]; it says it cannot find it in scope.

DDTTYLogger is deprecated and DDOSLogger does not support colors (because OSLog doesn't either).
There's not much we can do here, sorry!
Btw. the reason that [DDLog addLogger:[DDTTYLogger sharedInstance]]; doesn't work, is because it's Objective-C while your project apparently uses Swift 😉


Your API key is exposed

this.apiKey = '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'

Unfortunately, the ChatGPT api key is expired.


(FACT-1277) Add puppetversion to facter -p

When facter -p was restored to Facter 3, the puppetversion fact was
overlooked. It was moved to Puppet, but the code path we call to
initialize facter -p doesn't set it up. Explicitly set it by calling
Puppet.version, with support for a Puppet helper to be setup in
PUP-5508 to future-proof facter -p for new core Puppet facts.

I updated facter's protected branches configs to point to the new appveyor status endpoint.

Should we point this one at stable?

Oops, I'll fix tomorrow.

Retargeted stable as https://github.com/puppetlabs/facter/pull/1222.


Configuring the cache key of related data

I have a API that for some fields returns a summary object for that field. I have another API for which some react query key has already been configured. Can I configure react query in such a way that the react query cache key used for the response of the API and the summary object are the same. Since they represent the same object

Please provide some example, it will be easier for me to understand the issue. Thanks!

I have an API that returns the following data, say, issue.get(id)
{   assignee: { details: { id: 'profile_202', level: 'standard' }, id: 'user_101' },   components: [{ id: 'comp_303', subcomponent: { id: 'sub_404', status: 'active' } }],   id: 'obj_123',   parent: { id: 'parent_456', metadata: { id: 'meta_789', reference: 'REF-001' }, type: 'container' },   status: { current: { id: 'state_606', name: 'in_progress' }, id: 'status_505' },   type: 'primary', };
Now this API data is built up of multiple objects, for example, assignees, components, status, parent, etc.
For each of these objects, I also have APIs the fetch the correct data. something like assignee.get(id)
For the issue.get(id), the react cache key is [issues, id], and for the assignee.get(id), the react cache key is [assignees, id].
Now when I normlize this data, I want normy to cache the assignee data to the react cache key for the assignee object, which is [assignees, id].
Is thie behaviour possible to configure?

Now when I normalize this data, I want normy to cache the assignee data to the react cache key for the assignee object

Normy does not affect at all the way how react query cache data per key. Normy has own cache. React query data is assumed to be denormalized, and normy normalizes it.
I suspect that your use case is hard to translate to generic things which could be added to this library. Normy is very flexible, albeit it is opinionated for what it does, and all it does is adding normalizing feature to data fetching libraries.
Your use case seems different, as you have API which returns normalized data already. I am not sure this will help you, but you could:

use select option in useQuery, for example you could denormalize data there, for instance by using https://github.com/klis87/normy/tree/master/packages/normy-react-query#getObjectById-and-getQueryFragment-arrow_up
you can turn off normalization per query by meta.normalize
if this is not possible to achieve what you need, perhaps you need to build your own abstraction, perhaps using normy primitives. For example you could check https://github.com/klis87/normy/blob/master/packages/normy/src/denormalize.spec.ts and https://github.com/klis87/normy/blob/master/packages/normy/src/normalize.spec.ts to understand how actually normy works under the hood. you can see that on those primitives, the core for data fetching case is built - https://github.com/klis87/normy/blob/master/packages/normy/src/create-normalizer.spec.ts . But really, it is all about those 2 normalize and denormalize functions, the rest is just a glue.

If you need some help to understand some parts, pls let me know and I will try to help.


scrollToBottomAnimated support for multiple UICollectionView dataSource sections

Now the scrollToBottomAnimated method finds the last non-empty section, and uses that section index to find the last item in the collection view.

Thanks @thezonie.
This seems a bit too complicated to simply get the last item of the last section.

It is too complicated if you assumed that there would be no empty sections (which would be the case if you were using an NSFetchedResultsController as the data source) but I didn't want to make that assumption.


COMPRESS-477 : "open when actually needed" for MultiReadOnlySeekableByteChannel

Please refer (#90)[https://github.com/apache/commons-compress/pull/90]
When I was adding zip64 support for split zip, I encountered a problem :
When adding testcases in Zip64SupportIT, I created a split zip with 10,000+ split segments. Then I found that I was unable to unzip it because there would be too many open files when extracting it. We can oepn the files when actually needed and therefore we can successfully extract such split zips with great amount of segments.
I have set a threshold of 20 in MultiReadOnlySeekableByteChannel. The "open when actually needed" procedure will only work when the number of split segments is greater than the threshold.
Actually this is a pretty rare case cause most split zips would not have too many segments. So you can decide whether to merge this PR or not. :-)

@PeterAlfreadLee I think it would be good to track this as a separate JIRA issue.

Sure. I will add a new JIRA issue and modify the name of this PR.

Coverage decreased (-0.2%) to 86.754% when pulling 7ffc7a87236be2fd72b663f2735370a2d183494a on PeterAlfreadLee:COMPRESS-477-improve into 151e0fb3fa241887ae3192cc92c572401c6a182b on apache:master.


No Edge Extension

But that's okay, I made one.
https://github.com/TomFreeman/cloud-to-butt

Excellent!


fix typo in readme

I signed it!

This is already fixed in the latest commit. Thanks for helping anyways!


Spread causes "Expected '}' to match '{'..." error in object literals within nested callbacks

Hi,
It was an issue a few months ago when spead caused errors within object literals, and it was fixed (see: http://jsfiddle.net/KooiInc/tLoc387j/ -- it does not generate errors any more).
However, it turns out that if object literal's spread is nested within callback functions, it still causes an error:
https://jsfiddle.net/fv94x5wd/2/
Can it be fixed?
Thanks in advance.

We've added support for object rest/spread in JSHint version 2.10.0, and JSFiddle has updated to that version, so the example no longer reports a syntax error.


class "Foo" confuses Java??

https://pub.beakernotebook.com/#/publications/56f16616-2566-471e-b97f-28073e2b2e68

Apparently it's already defined somewhere. Takes no arguments and contains only hashcode.

yes it's used in javash.  it should have a more obscure name that users will never use.


Update xslt-transform-engine-grid-property.md

articulation changes. Language edits

I have proposed some changes. Please see #35

Simplified contents for easier reading.


Cleanup download-related code in the rustup_dist crate

This PR is probably easiest to read if you do it commit-wise: the first commit just removes the old, unused download module from rustup_dist. The second commit pulls DownloadCfg (and friends) out into a new download module.
The only other change in there is that I've tried to kill some of the instances where the notify_handler gets needlessly passed around by moving functions to be methods on DownloadCfg + using the field it's already got. I suspect the only reason these weren't done before is that it was difficult to reason about the code, so hopefully this is an improvement.
There aren't any (intentional) functional changes in this, so I haven't made any changes to the tests (aside from those required to get it to compile). No rush to get this merged for the same reason.

This LGTM, thanks! The underscore thing I commented on should probably be fixed separately.
@bors r+

:pushpin: Commit 61f641a has been approved by Diggsey

:hourglass: Testing commit 61f641a with merge d1b851f...

:sunny: Test successful - status-appveyor, status-travis
Approved by: Diggsey
Pushing d1b851f06858213bf5a01df6a4402788df279275 to master...


ci: Add create google account config step

This PR adds a missing step which is essential for proper IT workflow

Codecov Report

Merging #1398 (8c31618) into master (44800ce) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1398   +/-   ##
=========================================
  Coverage     77.61%   77.61%
  Complexity      717      717
=========================================
  Files           248      248
  Lines          4788     4788
  Branches        915      915
=========================================
  Hits           3716     3716
  Misses          572      572
  Partials        500      500


Error when using same attribute names in dependencies for oneOf JSONSchema definition

Question
I've been struggling with this error, I'll appreciate any help and/or workaround:
I am using JSONSchema and the .toFieldConfig method with oneOf dependencies as shown in the example from the website.
When I use fields with the same name as alternatives in a oneOf array, they are throwing an error whenever I set them using different types:
An error thrown in the console:
ERROR TypeError: control.registerOnChange is not a function
Example:
this.formlyJsonschema.toFieldConfig({
        title: 'Configurations',
        description: 'These are configurations',
        type: 'object',
        properties: {
          name: {
            type: 'string',
            title: 'Flag type',
            enum: ['type', 'other'],
          },
        },
        required: ['name'],
        dependencies: {
          name: {
            oneOf: [
              {
                title: 'type',
                properties: {
                  name: {
                    enum: ['type'],
                  },
                  value: {
                    title: 'Value',
                    type: 'array',
                    items: {
                      type: 'string',
                      enum: ['value1', 'value2'],
                    },
                  },
                },
              },
              {
                title: 'other',
                description: 'Other property.',
                properties: {
                  name: {
                    enum: ['other'],
                  },
                  value: {
                    title: 'Value',
                    type: 'boolean',
                  },
                },
              },
            ],
          },
        },
      }),
    ]

And when we submit the form, the value from other field is an empty array [] instead of a boolean.
Minimal Reproduction
https://stackblitz.com/edit/angular-68myfg?file=src%2Fapp%2Fapp.component.ts
Your Environment

Angular version: 14
Formly version: 6

This issue has been fixed and released as part of v6.2.0 release.
Please let us know, in case you are still encountering a similar issue/problem.
Thank you!


fix(TemplateLibrary): Button styling

Issue #184
Added style to button inside TemplateLibrary.
Changes

Added styles for hover and default style for "New Clause Template" Button.

What's the best way to see a preview of this button?

@irmerk showed me how, thanks

Okay, I'll fix it. Thanks!

Hello, I've found out that the icon has the exact same colour, but it doesn't have 100% opacity (.8 opacity instead), that's because it seems to have a different colour, what should I do?

I believe the icon is coming from here (https://github.com/accordproject/cicero-ui/blob/master/src/TemplateLibrary/TemplateActions.js#L53) and should have a color style applied to overwrite the current style?

The thing is, now it has the correct color, what happens is that its opacity is not 100%, that's why its colour looks weird.

The thing is, now it has the correct color, what happens is that its opacity is not 100%, that's why its colour looks weird. Is it okay to override that property?

Ah I see. It should be fine, yes.

Why are the opacities different in the first place? Is it a semantic UI thing?

It's probably a semantic UI thing, looking at its class ".ui.button". I've been researching what to do but I'm not sure what fix to apply as everything I can think of doesn't look that good.

I've come with a fix that is using an specific selector to remove it. What do you think of it? If it's okay, where should I put it?
button.ui.button i {     opacity: 1 !important; }

I've come with a fix that is using an specific selector to remove it. What do you think of it? If it's okay, where should I put it?
button.ui.button i { opacity: 1 !important; }

should be able to put it in src/styles.css

Oh! I put it correctly then, thank you!

@abnazhor looks great, thank you!


Fix most recent commit logic bug.

What?
Here goes your feature/bug-fix proposal
Type of change?

[x] [fix]: A bug fix

Why?
Semantic release most recent commit function was comparing the wrong commits.
It was coincidentally working.
How?
Changing the logic of the function, comparing first element against every elements of commit history.
Before submitting a PR please make sure to check if:

[x] The code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented on my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] The changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

LGTM

LGTM

is it one bugfix without tests? @esequielvirtuoso


CI: Switch to latest Ubuntu (focal)

Fixes issues with installing muFFT

https://travis-ci.com/github/ComputationalMechanics/ContactMechanics/jobs/490997438
Now H5 creates so many warnings at compilation that the CI can't stand the 50000 lines of log.
I guess we need to install a newer version of H5. Any problems with that ?

No, try to switch to a newer version. We need to get rid of this dependency at some point anyway. (All I/O should then go through muGrid's parallel I/O)

Ok I have set it to 0.12.0

Am 15.03.2021 um 10:45 schrieb Lars Pastewka @.***>:
No, try to switch to a newer version. We need to get rid of this dependency at some point anyway. (All I/O should then go through muGrid's parallel I/O)
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub https://github.com/ComputationalMechanics/ContactMechanics/pull/33#issuecomment-799276580, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJXV5WKEKAGMPIWC6BSFZM3TDXJMTANCNFSM4ZGFX2RQ.

muFFT?

No HDF

Am 15.03.2021 um 10:53 schrieb Lars Pastewka @.***>:
muFFT?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub https://github.com/ComputationalMechanics/ContactMechanics/pull/33#issuecomment-799282252, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJXV5WJKFPLUQ5M53ZKGRKTTDXKKBANCNFSM4ZGFX2RQ.

Okay, you mean 5.12.0...

Yes sorry, 1.12.0
https://support.hdfgroup.org/ftp/HDF5/releases/hdf5-1.12/

Am 15.03.2021 um 11:14 schrieb Lars Pastewka @.***>:
Okay, you mean 5.12.0...
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub https://github.com/ComputationalMechanics/ContactMechanics/pull/33#issuecomment-799296683, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJXV5WOEQHAHJGGKHOEZAADTDXMXBANCNFSM4ZGFX2RQ.

Can you merge this or should I merge it @AntoineSIMTEK

I think I can do it once both tests have passed.

I will apply the same changes all over the repositories ...

Sounds good!


RuntimeError: unable to write to file </torch_14471_3616880733_1>: No space left on device (28)

Hi, when running the following test command:
python -m src.main +experiment=re10k checkpointing.load=checkpoints/re10k.ckpt mode=test dataset/view_sampler=evaluation dataset.view_sampler.index_path=assets/evaluation_index_re10k_video.json test.save_video=true test.save_image=false test.compute_scores=false

I get this error:
Saving outputs to /home/ali/git/mvsplat/outputs/2024-04-15/11-22-42.
rm: cannot remove 'outputs/local': No such file or directory
GPU available: True (cuda), used: True
TPU available: False, using: 0 TPU cores
IPU available: False, using: 0 IPUs
HPU available: False, using: 0 HPUs
Setting up [LPIPS] perceptual loss: trunk [vgg], v[0.1], spatial [off]
Loading model from: /opt/conda/envs/mvsplat/lib/python3.10/site-packages/lpips/weights/v0.1/vgg.pth
Restoring states from the checkpoint path at checkpoints/re10k.ckpt
LOCAL_RANK: 0 - CUDA_VISIBLE_DEVICES: [0]
Loaded model weights from the checkpoint at checkpoints/re10k.ckpt
Testing: |                                                                                | 0/? [00:00<?, ?it/s]ERROR: Unexpected bus error encountered in worker. This might be caused by insufficient shared memory (shm).
Error executing job with overrides: ['+experiment=re10k', 'checkpointing.load=checkpoints/re10k.ckpt', 'mode=test', 'dataset/view_sampler=evaluation', 'dataset.view_sampler.index_path=assets/evaluation_index_re10k_video.json', 'test.save_video=true', 'test.save_image=false', 'test.compute_scores=false']
Traceback (most recent call last):
  File "/home/ali/git/mvsplat/src/main.py", line 143, in train
    trainer.test(
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 754, in test
    return call._call_and_handle_interrupt(
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/pytorch_lightning/trainer/call.py", line 44, in _call_and_handle_interrupt
    return trainer_fn(*args, **kwargs)
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 794, in _test_impl
    results = self._run(model, ckpt_path=ckpt_path)
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 987, in _run
    results = self._run_stage()
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 1026, in _run_stage
    return self._evaluation_loop.run()
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/pytorch_lightning/loops/utilities.py", line 182, in _decorator
    return loop_run(self, *args, **kwargs)
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/pytorch_lightning/loops/evaluation_loop.py", line 128, in run
    batch, batch_idx, dataloader_idx = next(data_fetcher)
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/pytorch_lightning/loops/fetchers.py", line 133, in __next__
    batch = super().__next__()
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/pytorch_lightning/loops/fetchers.py", line 60, in __next__
    batch = next(self.iterator)
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/pytorch_lightning/utilities/combined_loader.py", line 341, in __next__
    out = next(self._iterator)
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/pytorch_lightning/utilities/combined_loader.py", line 142, in __next__
    out = next(self.iterators[0])
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 630, in __next__
    data = self._next_data()
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 1345, in _next_data
    return self._process_data(data)
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/utils/data/dataloader.py", line 1371, in _process_data
    data.reraise()
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/_utils.py", line 694, in reraise
    raise exception
RuntimeError: Caught RuntimeError in DataLoader worker process 0.
Original Traceback (most recent call last):
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/utils/data/_utils/worker.py", line 308, in _worker_loop
    data = fetcher.fetch(index)
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/utils/data/_utils/fetch.py", line 42, in fetch
    return self.collate_fn(data)
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/utils/data/_utils/collate.py", line 265, in default_collate
    return collate(batch, collate_fn_map=default_collate_fn_map)
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/utils/data/_utils/collate.py", line 127, in collate
    return elem_type({key: collate([d[key] for d in batch], collate_fn_map=collate_fn_map) for key in elem})
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/utils/data/_utils/collate.py", line 127, in <dictcomp>
    return elem_type({key: collate([d[key] for d in batch], collate_fn_map=collate_fn_map) for key in elem})
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/utils/data/_utils/collate.py", line 127, in collate
    return elem_type({key: collate([d[key] for d in batch], collate_fn_map=collate_fn_map) for key in elem})
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/utils/data/_utils/collate.py", line 127, in <dictcomp>
    return elem_type({key: collate([d[key] for d in batch], collate_fn_map=collate_fn_map) for key in elem})
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/utils/data/_utils/collate.py", line 119, in collate
    return collate_fn_map[elem_type](batch, collate_fn_map=collate_fn_map)
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/utils/data/_utils/collate.py", line 160, in collate_tensor_fn
    storage = elem._typed_storage()._new_shared(numel, device=elem.device)
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/storage.py", line 866, in _new_shared
    untyped_storage = torch.UntypedStorage._new_shared(size * self._element_size(), device=device)
  File "/opt/conda/envs/mvsplat/lib/python3.10/site-packages/torch/storage.py", line 262, in _new_shared
    return cls._new_using_fd_cpu(size)
**RuntimeError: unable to write to file </torch_14471_3616880733_1>: No space left on device (28)**

Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.
Testing: |

I am using an RTX 3070Ti to run the test with 8GB of VRAM. I reckon this is not enough memory for the test to run.
Is it possible to make the test run on a GPU with less memory? (maybe by reducing batch size or the number of test videos loaded in to GPU memory)
Thanks for this great work.

I also tried setting test num_workers to 0 but here was the result:
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 4.32 GiB. GPU 0 has a total capacty of 7.76 GiB of which 3.65 GiB is free. Process 114241 has 3.68 GiB memory in use. Of the allocated memory 953.33 MiB is allocated by PyTorch, and 2.51 GiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

Hi @Ali-Flt, thanks for your interest in our work.
For video rendering on the subset, it requires around 13G VRAM, as tested on a 3090 GPU. The main reason is that we render novel view frames all in one forwarding, and some scenes might contain around 100 frames, therefore, it requires a rather larger VRAM.
A quick solution to fit into a smaller GPU is that you can replace the rendering at https://github.com/donydchen/mvsplat/blob/main/src/model/model_wrapper.py#L191-L200 with a for-loop structure. E.g., use batch["target"]["extrinsics"][:, i:i+3], so as for others like intrinsics, near and far.

@donydchen thanks for your reply.
Based on my understanding of your work you use 2 (or more) frames to predict gaussians of a scene. And after that the forward pass is finished and you can use the predicted gaussians to render novel views using the original 3DGS renderer via rasterization.
So when you say some scenes contain 100 frames are you referring to the input frames used to predict the gaussians or the output frames (novel views) which are the result of rendering?

Hi, @Ali-Flt, sorry for the inconvenience caused. When I said some scenes contain around 100 frames, I was referring to the output frames (i.e., novel views).

Hi @Ali-Flt, thanks for your interest in our work.
For video rendering on the subset, it requires around 13G VRAM, as tested on a 3090 GPU. The main reason is that we render novel view frames all in one forwarding, and some scenes might contain around 100 frames, therefore, it requires a rather larger VRAM.
A quick solution to fit into a smaller GPU is that you can replace the rendering at https://github.com/donydchen/mvsplat/blob/main/src/model/model_wrapper.py#L191-L200 with a for-loop structure. E.g., use batch["target"]["extrinsics"][:, i:i+3], so as for others like intrinsics, near and far.

Should I put the rest of the function in the loop too?

Btw  I ran some benchmarks and found out that more than 30% of the encoder time is spent in this single line:
pixel_size = 1 / torch.tensor((w, h), dtype=torch.float32, device=device)

You probably already knew about this but I thought maybe you missed it and you might find a way to make this diversion faster :shrug:


Issue with a TextField in Flutter for Web

This occurs when I hot reload.
══╡ EXCEPTION CAUGHT BY FOUNDATION LIBRARY ╞════════════════════════════════════════════════════════
The following assertion was thrown while dispatching notifications for FocusNode:
Assertion failed: org-dartlang-app:///packages/flutter/src/rendering/box.dart:1678:12
ssert(h
"RenderBox was not laid out: RenderEditable#7c095 NEEDS-LAYOUT NEEDS-PAINT"

Either the assertion indicates an error in the framework itself, or we should provide substantially
more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
https://github.com/flutter/flutter/issues/new?template=BUG.md

When the exception was thrown, this was the stack:
package:build_web_compilers/src/dev_compiler/dart_sdk.js 3991:11   throw_
package:build_web_compilers/src/dev_compiler/dart_sdk.js 3937:15   assertFailed
package:flutter/src/rendering/box.dart 1678:12                     get size
package:flutter/src/widgets/editable_text.dart 1656:40             [_updateSizeAndTransform]
package:flutter/src/widgets/editable_text.dart 1350:7              [_openInputConnection]
package:flutter/src/widgets/editable_text.dart 1375:7              [_openOrCloseInputConnectionIfNeeded]
package:flutter/src/widgets/editable_text.dart 1631:5              [_handleFocusChanged]
package:flutter/src/foundation/change_notifier.dart 206:21         notifyListeners
package:flutter/src/widgets/focus_manager.dart 765:5               [_notify]
package:flutter/src/widgets/focus_manager.dart 1331:11             [_applyFocusChange]
package:build_web_compilers/src/dev_compiler/dart_sdk.js 41669:13  _microtaskLoop
package:build_web_compilers/src/dev_compiler/dart_sdk.js 41675:13  _startMicrotaskLoop
package:build_web_compilers/src/dev_compiler/dart_sdk.js 38072:9   <fn>

Hi,
please provide us the output of flutter doctor and give us more context. Show us please the full error message and your code.
Are you experience this on windows or mac?
Otherwise we cannot help you.

Thanks for the doctor reminder, @escamoteur.
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.10.4-pre.46, on Mac OS X 10.14.6 18G87, locale en-US)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 10.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 3.5)
[✓] IntelliJ IDEA Community Edition (version 2019.1.3)
[✓] Connected device (3 available)

! Doctor found issues in 3 categories.

Thanks for filing the issue.
Since _updateSizeAndTransform method is on the line 1656, I am assuming this is not the latest code in the master. We resolved an editing issue yesterday. Can you please sync to the latest code?
If the issue persists, can you share code for the text editing widget you are using? It doesn't have to be exact. I am particularly curious to see the focusNode and autofocus properties.
Another question, is there a text editing related problem on the UI when you run flutter first time (I mean before using the hot restart)?

Hi Nurhan, the code is here: https://github.com/flutter/devtools/pull/1106/files
I'm still seeing the issue.  It should be reproducible by pulling down that repo and flutter run -d chrome from packages/devtools_flutter.

I see. Thanks for the reply.
I think this is a hot reload problem we encountered before. I will update the main issue soon.
Duplicate of https://github.com/flutter/flutter/issues/41284


Auto-updater prompting to insert adminstrator password without indication that it's for Toggl Desktop

OS X window saying “Autoupdate wants to make changes” and asks for password. There is noway to determine that the request was from Toggl Desktop.
More info: 193253

"Autoupdate" is the name of the executable that performs the actual update. It's part of the Sparkle framework. We could rename it to "TogglDesktopAutoupdate" or similar.


Fix "Quick Sharing on tmux" example:

The example command of "Quick Sharing on tmux" does not work out of the box, the browser shows only:
sessions should be nested with care, unset $TMUX to force
This PR is a proposal to fix that.
Tested with tmux v1.8 and v2.0 on Ubuntu 14.04

Hi @lhartikk. Thank you for the PR. I'm sorry for the delay to reply.
I could not reproduce the problem you are experiencing.
I'm using tmux 2.1.

@yudai: It's working in your env, because you're probably do not run gotty from tmux by itself.

@seletskiy Thanks.
I think adding TMUX='' to REAMDe by default is too much. May be it's better to mention that you should not run that command on tmux.
Please create another PR if needed.


Make OpenStack CCM version selectable

Currently the version of the OpenStack CCM is hardcoded and should be moved to a variable

https://github.com/inovex/kubernetes-on-openstack/pull/31 is currently doing some work in this direction.

Since the repo will be archived this won't be fixed.


Improve test coverage

Changes Unknown when pulling bffa0e04ea313c2b0a786d8308bf25473a93ac1e on improve-test-coverage into ** on master**.

Changes Unknown when pulling 73510ca81346beec79ff60a4710da83863e6bad7 on improve-test-coverage into ** on master**.


[InputUnstyled] not forwarding textarea specific props (rows, maxRows, minRows)

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
rows, minRows, maxRows props have no effect when the multiline flag is set for an <InputUnstyled /> component.
Expected behavior 🤔
The rows, minRows, maxRows props have the same effect just as they have in the case of a <TextField /> when the multiline flag is set.
Steps to reproduce 🕹
Steps:

Use the <InputUnstyled /> component
Set the multiline flag
Set the rows/minRows/maxRows to any preferred value other than "2" since it's the fallback value

Context 🔦
I was adding a multiline text input to one of the modals I'm working on and found out I cannot control the number of lines.
Your environment 🌎
codesandbox link

Is anyone working on this? I would like to work on this!


Add a "Compute" prefix for the GCE VM external IP access template

@morgante done. Since we've renamed the template, I didn't rev the version. I only added the existing copy in legacy.


Slf4j Dependency Declaration

Describe the bug
The declaration of slf4j as a dependency creates issues with our slf4j version. I think modules should not dictate (logging) dependencies' versions. Check the excerpt and the link from the slf4j site below.
To Reproduce
Steps to reproduce the behavior:

.
..
...
....

Example application to reproduce the issue
Any project that has the latest version of the slf4j.
Expected behavior
Per the documentation on the slf4j site:
Note that embedded components such as libraries or frameworks should not declare a dependency on any SLF4J binding but only depend on slf4j-api. When a library declares a compile-time dependency on a SLF4J binding, it imposes that binding on the end-user, thus negating SLF4J's purpose.
Debug log
The the debug log (set the log level to TRACE) to help explain your problem.
Environment(please complete the following information):

Version used:
Java version:
Operating System and version:
Endpoint Name and version:
Link to your project:

Additional context
Add any other context about the problem here.

This library only depends on slf4j-api as recommended by the documentation. The slf4j-simple dependency is used for testing, just like junit, etc:

Is the problem that you're using a different version of slf4j-api?

No activity and no real issue identified - closing


 and  buttons in the shot details page

From Decent Forum

I have a suggestion for the shot details page in Visualizer: would it be possible to add and buttons, to quickly go to the previous or next shot in the list, rather than having to go back to the list and click on another shot? That would be so cool.

A possible related idea or suggestion: perhaps the drop down menu of shots could be available. Similar to how it is for comparing shots, but also an option for jumping directly to a particular shot. Thanks!


🖨 Debug Printing Improvements

Patch Description
This PR adds a new Debug module, which consists of some simple debugging printers that can be toggled on and off at will. It also adds names to tactics, which allow us to trace what tactics are being executed for easier debugging, along with a new --debug flag for enabling debug printing.

This is so much fun but let me stop now before it goes out of control... :sweat_smile:

In the long run, we could consider the approaches based on ppx to massage the backtraces.


Support for BeforeShowNextStep?

Hi,
I have the scenario where i need to show a modal window before show the last step because the element for last step is in the modal window. When i try to show the window modal in onNext i got an error because the element was not found.
any solution to handle this?

Rolling this into #56


SecurityHub log shards error

Observe the following error while trying view securityhub logs after upgrading to opensearch 2.3
{
"took": 877,
"timed_out": false,
"_shards": {
"total": 31,
"successful": 28,
"skipped": 28,
"failed": 3,
"failures": [
{
"shard": 2,
"index": "log-aws-securityhub-2022-11",
"node": "42eLcdhhStOb3mZFCGBe2Q",
"reason": {
"type": "illegal_argument_exception",
"reason": "Field [Vulnerabilities.VulnerablePackages.Epoch] of type [keyword] does not support custom formats"
}
}
]
},

Thanks for the feedback. It was fixed by https://github.com/aws-samples/siem-on-amazon-opensearch-service/issues/203


rename 463 and add 42

File(s) Submission: problem_0042_trapping_rain_water.cs
Programming Language(s): c#
Submission URL: https://leetcode.com/problems/trapping-rain-water/submissions/917113859/

lgtm


Fixed isometric Twinsen position between scenes

Issue was more evident on LBA1 where Twinsen was not placed correctly on the new scene.

Haven't actually tested since the preview instance doesn't seem to be working but since this is the unusual case when we can't find a zone to snap to it's probably ok.


Fix workflow for publishing guide on release

Closes: https://github.com/informalsystems/ibc-rs/issues/2152

PR author checklist:

[ ] Added changelog entry, using unclog.
[ ] Added tests: integration (for Hermes) or unit/mock tests (for modules).
[ ] Linked to GitHub issue.
[ ] Updated code comments and documentation (e.g., docs/).

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

Does this also close #2154 ?


Critical lack of {total} pseudomods

The problem is that many modes, due to their variability, but at the same time the same essence, will be useless in a search without pseudo-modes namely and most importantly {total} pseudomod.
For example, I have a dagger, with a crafted crit chance for spells, say something like 50% global crit implicit and crafted 30%. At the moment, the search works in such a way that I see in the results only something really similar and it will have exact crafted spellcrit mod only. And no manipulations in the item evaluation window will allow me to get into the search result for example:

30% global + 50% crafted
40% global + 40% natural roll
corrupted in anything implicit + 80% natural roll
... etc.

The same situation will be true for spell damage, cast speed, elemental damage, global crit multi, elemental penetration and so on. That is, this is true for any item base type that has a non-unique implicit that may be present in some form in its rolls/mods.
Ok, in some cases we can skip implicit value coz search can to take into account item class (but not base type, this leads to the opposite - unnecessary narrowing of search results) and just increase the value of the corresponding suffix/prefix (if it is of course available on this item). But this will not work if it is not pseudo or simply absent. In any case this is a crutch.
So I say that all global item mods must be use pseudo {total} otherwise the search becomes, to put it mildly, extremely inaccurate. This problem is mostly unique to weapons.
For other slots it is either not so critical, with the exception of what I would say Opal/Still rings and some Talismans and some corrupts.
Nevertheless, it is present in Marble/Paua/Blue Pearl/Gold Amulets, some Talismans, Rustic Sash, Cloth/Studded/Vanguard Belts, Diamond/Gold/Iron/Vermillion/Cerulean Rings, Shields with Spell Damage/Dodge Spell/Attack Hits implicit, all Quivers (hope I haven’t missed anything).
Or it falls into the category {total} (like Two-Toned Boots will give total res) or you anyway will use this unique implicit/base type to search (like Bone Helmet).
It is necessary that they are either considered as {total} by default, or we had a simple opportunity to change them to {total} in a couple of clicks in the search coz separation to implicit/natural/crafted is not right way for search in most cases.

0.5.16 (2020-02-13)

add additional pseudo mods (#230)

Let me know if there are still some mods missing you require. Thanks for your feedback!

This is a great change!
So, I conducted a fairly large test (unfortunately I could not do it right after the patch, due to the lack of free time).
There are some {total} mods on items where this {total} is useless, because there can be no different mods that can be summed up, but redundancy is better. especially in the future, the mod pool may change and you will have to redo this part of the program again. This is more polishing than ensuring proper performance.
In general, everything works fine and I will simply list below those cases when something went wrong.

Rarity: Rare
Kraken Barb
Cobalt Jewel
--------
Item Level: 85
--------
5% increased Attack Speed while Dual Wielding
6% increased Attack Speed with Wands
+15% to Lightning Resistance
3% increased Attack and Cast Speed
--------
Place into an allocated Jewel Socket on the Passive Skill Tree. Right click to remove from the Socket

"Attack and Cast Speed" mod, in search it separates on two "total Attack Speed" and "total Cast Speed" (and in the menu there is no choice of this particular mod) and for some reason tradesite don't return in result any hybrid "Attack and Cast Speed" if you select them one or both.

Rarity: Rare
Sol Gorget
Citrine Amulet
--------
Requirements:
Level: 64
--------
Item Level: 85
--------
+23 to Strength and Dexterity (implicit)
--------
+29 to Strength
19% increased Lightning Damage
19% increased Evasion Rating
+76 to maximum Life
Regenerate 2.5 Life per second
38% increased Elemental Damage with Attack Skills

{total} "increased Lightning Damage with Attack Skills" don't sum "increased Lightning Damage" and "increased Elemental Damage with Attack Skills" (for example similar "increased Spell Damage" and "increased Fire Damage" sum correctly to "increased Fire Spell Damage").

Implicit (Adds X to Y Physical Damage to Attacks) on Steel/Iron rings and Serrated/Broadhead Arrow Quiver don't have {total} with (Adds X to Y Physical Damage to Attacks) prefix mod.

BTW IMO you can sum dagger's implicit "increased Global Critical Strike Chance" with natural/crafted "increased Critical Strike Chance for Spells", In any case, the tradesite works correctly with such a sum if you use "+#% total Critical Strike Chance for Spells"

P.S. If I find more, I will add a comment in this issue.
P.P.S. This not relevant to this issue, but I would like to mention this - except for the problem of normalizing the quality of armors and weapons, during assessment does not apply search range penalty to final amount of armour/evasion/energy shield and DPS/pDPS/eDPS, attack speed, critical strike chance. Perhaps this is correct decision, but at least we should be able to change these values in the item assessment menu like all other one mods.

"Attack and Cast Speed" mod, in search it separates on two "total Attack Speed" and "total Cast Speed" (and in the menu there is no choice of this particular mod) and for some reason tradesite don't return in result any hybrid "Attack and Cast Speed" if you select them one or both.

I'll remove the 'attack_and_cast_speed_+%' modifier from this group. Seems like the tradesite does not add those. See:

{total} "increased Lightning Damage with Attack Skills" don't sum "increased Lightning Damage" and "increased Elemental Damage with Attack Skills" (for example similar "increased Spell Damage" and "increased Fire Damage" sum correctly to "increased Fire Spell Damage").

Will be added!

Implicit (Adds X to Y Physical Damage to Attacks) on Steel/Iron rings and Serrated/Broadhead Arrow Quiver don't have {total} with (Adds X to Y Physical Damage to Attacks) prefix mod.

There was a missmatch in my stats data which caused this implicit mod not beeing recognized as "Adds # to # ...". Will be fixed.

BTW IMO you can sum dagger's implicit "increased Global Critical Strike Chance" with natural/crafted "increased Critical Strike Chance for Spells", In any case, the tradesite works correctly with such a sum if you use "+#% total Critical Strike Chance for Spells"

Will be changed!

P.P.S. This not relevant to this issue, but I would like to mention this - except for the problem of normalizing the quality of armors and weapons, during assessment does not apply search range penalty to final amount of armour/evasion/energy shield and DPS/pDPS/eDPS, attack speed, critical strike chance. Perhaps this is correct decision, but at least we should be able to change these values in the item assessment menu like all other one mods.

This is more a historical issue. The mod ranges were introduced after the property section have been implemented. Will be added.
Thank you for your great input! 🚀 👍

0.5.18 (2020-02-19)

update pseudo config (#230)

add global critical strike chance to critical strike chance for spells
add increased elemental damage to attack skills
remove hybrid attack/cast speed from total attack/cast speed

Closed in favour of #294


More information about Personas and users

@shubhaat gave me this feedback about onboarding week that I think is worth discussing:

I was reflecting on what would be useful to me and maybe other new recruits in CF to orient themselves better to what a CF deployment looks like for customers...
One thought was to include an example of a typical CF deployment or a few CF deployment topologies to understand the larger picture of how customer deployments look like. I wonder if this could be included in the one week onboarding you run for engineers, PM's and others...
Having a 1 hour discussion on this for folks to ask questions would be useful during the onboarding week.
I am not talking about CF technical architecture so much but what a typical CF customer deployment (maybe which persona is involved in setting up and using what) looks like in terms of configuration and maybe touching on Small Footprint and a scaled up deployment. It's more big picture than details. I think this can actually be documented and shared out before and having an hour long discussion or q/a would be great.
For instance an operator would use bbl to configure the IaaS and a app developer would do a cf push app. I can see this being pretty useful for design and PM, and a good way for engineers to step back and see how the product is used and by whom.

We actually do cover most of the important user workflows, but it sounds like we're not doing a great job articulating how the onboarding stories relate to a persona or their goals.

Some parameters we might consider for this:

Why did an operator choose their IaaS?
Why did they choose a specific deployment topology? Databases/blobstores? Large or small deployments? Different of colocation? Why would somebody a small-footprint deployment?
What kind of security consideration do different operators need to make?


Fix Guidelines Section in Dark Mode

Description
Fix the right side dark image as it gets camouflaged with Dark background with dark mode
Screenshots

Additional information
No response

I would like to work on this issue.

@soustab10 Assigned you

@soustab10 What's the Update?

@soustab10 What's the Update?

working on it. PR will be made soon.

@soustab10 Any Progress?

Please assign this to me is possible. @Debajyoti14 Since @soustab10 has not responsed.

@gaut2003 assigned you

@gaut2003 any updates???


Realtime APIs use the wrong endpoint and 404s unless API base path is set to the realtime endpoint.

Version
3.1.0
What happened
Using the realtime APIs results in 404s since the endpoint is rt.fastly.com per the documentation.
A workaround is to initialize a standalone API client and set its base path accordingly:
const fastlyApi = new ApiClient();
fastlyApi.basePath = "https://rt.fastly.com";
fastlyApi.authenticate(FASTLY_KEY);
const realtimeApi = new RealtimeApi(fastlyApi);

👋🏻 Thanks for opening this issue @caiges I've opened an internal ticket to track this bug.

I'm going to close this issue as I believe this issue was resolved in the 4.2.0 release back in June:
https://github.com/fastly/fastly-js/blob/main/CHANGELOG.md#v420-2023-06-20


add git hook to build site on commit

The out directory should never be out of date on the main repo, and it kind of just makes sense with Travis already set up to compile to gh-pages.

For ref: http://stackoverflow.com/questions/15703065/setup-pre-commit-hook-jshint

Would be better suited as a travis command?
I don't like that my commits are polluted with all of the modifications from the out directory.
What I could do:

Use something like skip-worktree or add a clean git hook to keep the out directory from being pushed.
Add a travis command to build and push the out directory to two places (site and here).

Some complications:

Travis will need to build twice, since for one target it's only pushing the out directory, and for the main repo it's pushing everything.
If I clean the out directory, git will still push those changes...

Bears some additional thought.

Closing.  It's better to just not have the out repo for now, but this could be reopened in the future.


LUTECE-2196 : Allow to reload the log4j configuration at runtime

We should discuss where we want this feature

Thanks for the review, I'll fix the problems you found


Keep initial position of item

Similar to Chrome or Firefox Bookmarks Toolbar. It keeps initial position of item during dragging, showing a line at the position when item is potentially dropped.

Hey, also interested in a solution for this. I have the part when you transform the 	chosenClass: "sortable-chosen" and transform the element to a bar:
:host(.sortable-chosen) {
  visibility: hidden;
  height: 1px;
  position: relative;
  &::before {
    content: '';
    visibility: visible;
    border-bottom: 1px solid $primary;
    width: 100%;
    height: 0;
    position: absolute;
    top: 0;
    left: 0;
  }
}

But I can't achieve to let the item at its initial position  and do the move only on dragEnd...
Thanks in advance for anyone helping on this!

I achieve something which is quite hacky but seems to work so far. I create a clone of my element and reinsert it in the DOM at the same place of the dragged element. And remove it onDragEnd. I have some issue of DOM rendering but it's because I use webcomponent. For normal DOM element this should work perfectly:
import Sortable from 'sortablejs';
import { EventEmitter } from '@stencil/core';

export function initMenuSort(el: HTMLElement, emitter: EventEmitter) {
  let persistentClone: HTMLElement = null;
  const sort = Sortable.create(el, {
    draggable: '.my-draggable',
    handle: '.drag-handle',
    filter: 'my-menu-action',
    group: { name: 'menu' },
    ghostClass: 'sortable-ghost',
    chosenClass: 'my-sortable-chosen',
    sort: true,
    onStart: (e: any) => {
      const el = e.item as HTMLMyComponentElement;
      let index = e.oldIndex;
      if (index < 0) {
        index = 0;
      }
      // @TODO el.cloneNode(true) (deep=true)
      // this cause the component to rerender and display the content <slot> twice
      // when stenciljs will be bulletproof on cloneNode(deep=true) we will have the clone properly displaying
      persistentClone = e.from.insertBefore(
        el.cloneNode(),
        e.from.children[index]
      );
      persistentClone.classList.add('my-sortable-disable');
      persistentClone.classList.remove('my-draggable');
      console.log(persistentClone);
      console.log(e);
      el.dragStart();
    },
    onEnd: (e: any) => {
      const data = {
        oldIndex: e.oldIndex,
        newIndex: e.newIndex,
        item: e.item,
        newParent: e.to,
        oldParent: e.from
      };
      const el = e.item as HTMLMyComponentElement;
      el.dragEnd();
      persistentClone.remove();
      persistentClone = null;
      emitter.emit(data);
    },
    onMove: e => {
      // If it's not draggable, we cancel the move
      if (e.related.classList.contains('my-draggable')) {
        return true;
      }
      return false;
    }
  });
  return sort;
}

Adapte the code to your case ;)

Perhaps a placeholder element option, to stay in the original position of the element?

We are having issues when sorting an item and then re-rendering a stencil component, this causes sortable to repeat the previous drag action - I am not sure why this is occurring. @Nightbr is this the issue you were trying to get around ?

Hey @miguelyoobic95 it's another problem you describe. But we manage to include sortableJS with stenciljs component, we use our fork
-> "sortablejs": "https://github.com/saloonio/Sortable.git#dev-firefoxShadowRoot"
We use a stenciljs component container which instantiate sortablejs:
componentDidLoad() {
    this.sortableElement = Sortable.create(this.el.querySelector('.components') as HTMLElement, {
      handle: '.drag-icon',
      draggable: '.plop-draggable',
      filter: 'plop-new-component-container soon-button',
      animation: 150,
      onStart: e => {
        const el = e.item as HTMLPlopComponentElement;
        el.dragStart();
      },
      onEnd: e => {
        const el = e.item as HTMLPlopComponentElement;
        el.dragEnd();
        this.drop(e);
      },
      onMove: e => {
        // If it's not draggable, we cancel the move
        if (e.related.classList.contains('plop-draggable')) {
          return true;
        }
        return false;
      }
    });
  }

I'm also interested in this feature. Another great example for this is Notion:

This would be a great idea for a plugin. I could try to make it myself, but if anyone else wants to give it a try - the docs for creating a plugin are here: https://github.com/SortableJS/Sortable/blob/master/plugins/README.md

using our code snippet https://github.com/SortableJS/Sortable/issues/1345#issuecomment-434630156 & https://github.com/SortableJS/Sortable/issues/1345#issuecomment-434655435

@Nightbr Would you be interested in making your implementation into a plugin?

I don't think it could be easy because I'm wrapping SortableJS into a Stenciljs webcomponent. But I could try if I have spare time ;)

Is there any plugin or API available to achieve this using just SortableJS?

Is there any plugin or API available to achieve this using just SortableJS?

+1 We need this :D

This would be a great idea for a plugin. I could try to make it myself, but if anyone else wants to give it a try - the docs for creating a plugin are here: https://github.com/SortableJS/Sortable/blob/master/plugins/README.md

Are there still any plans for this?

Just leaving a +1. This is the same functionality we would like to achieve. Thanks!

+1

+1

+1

+1

+1

+1

Any new?

+1

+1

+1

+1

@songispm @Klapik @kotoyama @9brada6 @miroshnichenkoYaroslav @semivori @joaobarcia
This can implemented without a plugin using @Nightbr's method. Here's a more minimal version:
Keep an original copy in place as you drag:
onStart(e) {
	// Add a clone in the original location
	const persistentClone = e.from.insertBefore(
		e.item.cloneNode(true),
		e.from.children[e.oldIndex as number]
	) as HTMLElement

	// give it a class so we can remove it later
	persistentClone.classList.add('sortable-clone')

	// remove irrelevant classes
	persistentClone.classList.remove('sortable-chosen', 'sortable-ghost')
},
onEnd(e){
	// remove persisted clones
	e.from.querySelectorAll('.sortable-clone').forEach(child => child.remove())
}

.sortable-ghost ends up being the blue line you want - but you'll need to do some styling to hide is contents, make it blue, etc.
My elements are table rows so I had to do some css trickery to get the line to work consistently between rows:
tbody {
	// ensure the absolutely positioned table row stays contained within the tbody
	position: relative;
}

// Position the table row line and hide its contents
.sortable-ghost {
	// eliminate goofy layout shifting
	position: absolute;

	// make it full width
	display: block;
	width: 100%;

	// Overly robust hack to hide text contents within the line element
	text-indent: -9999px;
	font-size: 0.001px;
	line-height: 0;
	color: transparent;
}

// Create the actual line
.sortable-ghost::before{
	content: '';
	position: absolute;
	top: 0;
	right: 0;
	left: 0;
	height: 3px;
	background: blue;
}

Use Swap plugin:
https://sortablejs.github.io/Sortable/#swap https://github.com/SortableJS/Sortable/tree/master/plugins/Swap

No, the Swap plugin swaps the dragged element with the destination element. Totally different feature.


spirv-std/Image! should expose AccessQualifier.

I think it would be beneficial to expose the AccessQualifier in the Image! macro, as at least for wgpu, ReadWrite and ReadOnly storage textures are only supported on native platforms. So, it would be benificial for Images allow for WriteOnly.

Oh I'm really sorry I haven't checked what SPIR-V's "Access Qualifier" is.
The reason it's optional and not included in spirv_std::Image seems to be that it's Kernel-only.
That is, this is an OpenCL feature, not a Vulkan one, and wgpu couldn't possibly make use of it (unless they misunderstood the specification, too?).
The Vulkan feature is NonWritable/NonReadable on the OpVariable, seems like, just like StorageBuffers.
It does seem weird to put it in the attribute in the #[spirv(...)] img: Image!(...) declaration, as the Image<...> type could really use the knowledge, and a writable &Image behaves more like a &[Cell<u32>]/&[AtomicU32] (relying on interior mutability), if that makes sense.
It may be possible to pretend that it is a parameter on image types, or even reuse the AccessQualifier (and rewrite it away to the Vulkan equivalent), but that seems a bit sketchy, not sure what to do about it for now.
(cc @Algorhythm-sxv - sorry you ended up implementing a different feature that the needed one)

This is the relevant part of my message:

The Vulkan feature is NonWritable/NonReadable on the OpVariable, seems like, just like StorageBuffers.

We currently support toggling NonWritable for buffers based on whether you use &T vs &mut T with #[spirv(storage_buffer, ...)] entry-point parameter declarations, since:

#1011

In theory, we could do it for images based on &Image vs &mut Image, but like I was saying earlier that doesn't fit very well IMO, since images already behaves as if they wrap interior mutability anyway, and also that doesn't cover NonReadable (because Rust has nothing like a "write-only reference"), which I believe you need?
There's two possible paths, as I see it:

#[spirv(descriptor_set = ..., binding = ..., non_readable)] img: &Image!(...) in the entry-point params

this has been proposed before at least for buffers: #692
this seems potentially problematic in terms of being able to turn off methods on the actual types, as the Image<...> would have no information about how it's used

Image!(..., non_readable) - in the type, even if Vulkan SPIR-V does not store that information there

ideally mapped to e.g. struct Image<..., const READABLE: bool, const WRITABLE: bool> to allow impl blocks to select whether they need one or the other (or work regardless), tho see also the trait HasImageFoo pattern

this might cause problems depending on the exact details, because the SPIR-V spec states:
It is invalid to declare multiple non-aggregate, non-pointer type ``s having the same opcode and operands.

that is, you would want tests which use the same identical Image<...> type with only these new differences being toggled between them, to show that they don't lead to duplicated definitions or ID conflicts

in theory this could even be done with the same syntax and names as for the OpenCL feature (i.e. like in your PR), but at some point those would have to be replaced with the Vulkan equivalent (entry.rs can generate the Vulkan annotations at the same time, and then you have to remove AccessQualifier from the type, replacing all uses of the type, or maybe just never generate the AccessQualifier in the first place, getting you back to what I was saying earlier, but with the downside of seemingly-OpenCL concepts used with Vulkan shaders)


ModSecurity not putting some transactions to audit log

Describe the bug
We are facing a problem when in certain cases ModSecurity is not tracking the blocking in the audit log despite we have set it as a default action and the rule is not having any logging property set. In the error log, we can see only the rule which was triggered due to the anomaly score has been reached but nothing about the rules which actually counted the score. In some other cases, this information is visible.
In modsecurity.conf we have logging of rules enabled
SecAuditLogParts ABCIJDFHKZ
In crs-setup.conf we have default logging set to capture everything in both error and audit log.
SecDefaultAction "phase:1,log,auditlog,pass"
SecDefaultAction "phase:2,log,auditlog,pass"

We have also tried other combinations like using this setup
SecDefaultAction "phase:2,pass, nolog,auditlog"
But nothing helped.
Logs and dumps
The only thing we can see in the log is this part from the error log and when we need more details we need to enable debug and redo the action. In the example below I have changed the IP addresses for security reasons.
2022/03/09 08:32:25 [error] 1149#1149: *13832 [client <IP_ADDRESS>] ModSecurity: Access denied with code 403 (phase 2). Matched "Operator Ge' with parameter 5' against variable TX:ANOMALY_SCORE' (Value: 15' ) [file "/etc/nginx/owasp-modsecurity-crs/rules/REQUEST-949-BLOCKING-EVALUATION.conf"] [line "139"] [id "949110"] [rev ""] [msg "Inbound Anomaly Score Exceeded (Total Score: 15)"] [data ""] [severity "2"] [ver "OWASP_CRS/3.4.0-dev"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-generic"] [hostname "<IP_ADDRESS>"] [uri "/favicon.ico"] [unique_id "1646811145"] [ref ""], client: <IP_ADDRESS>, server: example.com, request: "GET /favicon.ico HTTP/1.1", host: "example.com", referrer: "http://example.com/?q=%22%3E%3Cscript%3Ealert(1)%3C/script%3E%27"
We need to find a way how to make sure every attempt will be logged into the audit log.
Thanks in advance for any help.
Peter
To Reproduce
Steps to reproduce the behavior:
We just ran the URL below to trigger some WAF rules.
http://example.com/?q=%22%3E%3Cscript%3Ealert(1)%3C/script%3E%27
Expected behavior
We expect that every threat will be captured in audit log which is not happening at this time. Only some are captured while many are not. We can see only rule 949110 in the log which is the very last one and missing those others which counted the anomaly score.
Server (please complete the following information):

ModSecurity version (and connector): [ModSecurity v3.0.6 ]
WebServer: [nginx-1.20.2]
OS (and distro): [Oracle Linux 7.9]

Rule Set (please complete the following information):

Running any public or commercial rule set? [e.g. SpiderLabs public rules]
What is the version number? [CRS v3.4.0dev]

@PeterP55P  check directive "SecAuditLog" in your modsecurity.conf, in file this directive must to have all content from match rules.
In logger error normally show only wich generate action the lock.

@PeterP55P check directive "SecAuditLog" in your modsecurity.conf, in file this directive must to have all content from match rules.
In logger error normally show only wich generate action the lock.

I'm not really sure what do you mean. The directive "SecAuditLog" points to the path of the audit log file which is set and some transactions are being captured there. The problem is that many others are not captured in this file.

Hello @PeterP55P,
To summarize your issue:

you get entries in the audit log file for some transactions
for some other transactions, you get nothing in the audit log file, but you still get an entry in nginx's error.log file (including even the triggering rule number)

One way that could happen is if you have set SecAuditEngine Off for some transactions but not for others. This could happen if you are using different ModSecurity configuration directives for different nginx blocks (e.g. different location blocks).
A related way to see this effect is you are using the ctl:auditEngine action (it is not available in the tagged version of v3.0.6, but it is in v3/master.
Beyond that, I would suggest seeing what is happening by checking ModSecurity's DebugLog (level 9).

@PeterP55P do you use ModSecurity with error_page?
If so, please check https://github.com/SpiderLabs/ModSecurity-nginx/pull/273.

@liudongmiao very good point. thanks for this finding. this is exactly our problem. after commenting out the error_page directive the issue is gone.

Thanks for the feedback @martinhsv ! Reason for the aggregated logs is because I have log monitoring already in place on the cluster and all logs that are sent to stdout or stderr will be collected .
So, within the ingress-nginx pods, there are already default symlinks such as:
lrwxrwxrwx    1 www-data www-data        11 Apr 20 18:41 access.log -> /dev/stdout
lrwxrwxrwx    1 www-data www-data        11 Apr 20 18:41 error.log -> /dev/stderr

and i've also tried setting SecAuditLog /dev/stdout to no avail.
That said, I think you are right: my issue is likely different as i have just noticed that many log files do indeed always appear in /var/log/audit/ - so i guess i just need to find a way to collect them and print to stdout/stderr via a sidecar perhaps.
Thanks for the pointers


Support for columns

Hi,
I'm still analyzing if Backpack is a fit for a project that I'm working on. I did not find anything similar with switch present in Laravel-admin: https://laravel-admin.org/docs/en/model-grid-inline-edit#Switch
It would be nice to have the field provided by this package also available for columns and with the possibility to apply the change once the user toggle the value.
Best regards,

Hi @lisotton .
I agree, it'd be useful in some projects to have a toggle column that actually toggles an attribute. We haven't added "active columns" (aka "fields as columns") in Backpack because supporting ONE column is super-easy, but supporting ALL fields as column, with the underlying saving logic to "just work"... that's a monster of an endeavour.
To create what I understand you need in Backpack, you'll have to:

create a custom column type, which is as simple as creating resources/views/vendor/backpack/crud/columns/toggle;
add the JS logic you need, to make an AJAX call to an endpoint you control; you can use the delete button as an example, there's a trick there to push the JS in the after_scripts section;
create the route and controller that processes that request, toggles the attribute and returns a response;
(improvement idea) even better, you could create an operation, something like ToggleAttributeOperation; it's super-easy, and it'd allow you to re-use this operation across as many CrudControllers as you want, to easily add toggle columns without having to re-code the route/controller/etc;

Since this is outside the scope of this package, I'm going to try to move the issue from digitallyhappy/toggle-field-for-backpack in our addons repo. I think this could be a really cool addon, if someone builds it. @lisotton if you do decide to use Backpack, and end up building the above (or similar) let me know, I'll gladly help you turn it into an addon for everybody else to reuse your code too.
Cheers!


[events] dispatch custom events for errors in all components

Code changes

[x] Dispatches any new errors to onError custom event. Errors are held in the ErrorStore when any error is thrown from fetches in components

Readiness checklist

[x] Added changes to component CHANGELOG.md

License
I confirm that this contribution is made under the terms of the MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

@philrenaud good point! I'll test this out.

@philrenaud

Testing question: have you tried this in a situation with two components on the page, each causing 1 error?
Each component will only throw one error, shouldn't produce duplicates.