Create CHANGELOG.md

It would be nice if each release was documented.
Thanks

👍

I'll also create tags


Calculate number of unique for Unknown columns

Calculate nunique for Unknown columns in _get_describe_dict
Closes #1257

I don't think we currently test describe on any Unknown columns, which is why these changes haven't broken any tests. Can we add a test that explicitly sets a logical type as Unknown before running describe so we can confirm that both count and nunique are present?


change tip help for pull screan

(F12 -> F11)

Can one of the admins verify this patch?

@donggyu04 could you clean up this PR by starting from develop and cherrypicking the
e9c26c0

@junoyoon @shfksekdrms2
Mentioned above, in develop branch no longer uses freemarker(.ftl)
so it should be modify Editor.vue.
currently this changes are already applied.

https://github.com/naver/ngrinder/blob/develop/ngrinder-frontend/src/js/components/script/Editor.vue#L76

thanks for your PR and sorry about force update to base branch.


NuGet packages no longer publishing to Appveyor project feed

this is due to X.X.X.X-prerelease not being valid semver.  unfortunately, valid semver of X.X.X-prerelease.X is not a valid nuget version.  will have to translate to X.X.X-prereleaseXX and hope not to have more than 100 prereleases per version

while the version numbers are now valid, this did not fix the issue with appveyor


A JavaScript error occurred in the main process while opening Visual Studio Code

Does this issue occur when all extensions are disabled?: Unable to test, due to VSCode even open.

VS Code Version: Latest
OS Version: Windows 10 Enterprise (19042.1466) (Windows Feature Experience Pack 120.2212.3920.0)

Steps to Reproduce:

Try to open Visual Studio Code

I'm already uninstalled and started installing "x64-1.63.2" version due to the fact that I'm in the middle of some urgent work from our side.

As a workaround I needed to uninstall and install again, but it is not the first time that happens.
I'm using the latest version now, downloaded from the VSCode site: x64-1.63.2, with no problem now.

In order to prevent this from happening again, can you try disabling Windows background updates? Set update.enableWindowsBackgroundUpdates to false.

Thanks, so that I'll be necessary to check periodically for the stable updates, right?


Scope Display Settings

The user should have access to a UI that allows them to adjust various basic things about the way the markings on the scope are displayed. This would include adjustments to:

brightness of aircraft targets, data blocks, control symbols
brightness of background color
brightness and radius of range rings
brightness of video map markings
center of range rings
default direction of data block leader lines
default length of data block leader lines
default length of PTLs (see #715)

The UI should ideally not be hardcoded either, but rather controlled by some sort of configuration file that describes how to draw the buttons, so different ATC systems can be emulated as needed. For example, many newer facilities in the US use the STARS radar system, from which we should emulate the DCB. But for EGLL, it might make sense to develop a UI that looks and feels more like... whatever software it is that they use. Then we can include a property in the airport file that determines what style of scope should be loaded.

I would encourage you to split this into two separate issues; one for the list and one for the scope themes.
The list looks very doable.  The way I see that working in my head will take a new class and a refactor of the CanvasController that would interface with this class.

The ATC repository is being migrated to it's new home at https://github.com/openscope/openscope,
and thus, all issues are being closed. If this is still an issue with the latest version of the sim
(accessible at http://www.openscope.co), or is a feature you still think we are lacking,
please reopen the issue at the new repo.
Please note that the vast majority of these issues have been copied to the new repository, or else are covered by other issues created there. See the below screenshot for what it looks like when your issue is known in the new repo:

Thank you!
Closing this issue.


Add important area support

In Ella CMS, we are considering switching our custom image formatter to sorl (with some additional wrapper to allow for named formats), but there is one dealbreaker that effectively prevents us from doing so. We need to support important area box, which is very often used by our target user group (mostly online news websites).
For each Photo, we need to be able to define important box which is an area, that should not be ever cropped. For reference, see https://github.com/ella/ella/blob/cleanup/ella/photos/formatter.py#L82.
Is there any chance you can add support for this kind of thing?

It sounds like something you can easily do on your own and not something I want to implement since its such a specialized case.. (unless someone provides a patch to do this).


[Currency Bot] Bumped patch/minor dependencies

Tada!

https://www.elastic.co/guide/en/elasticsearch/reference/8.15/migrating-8.15.html#breaking-changes-8.15
https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/8.15/changelog-client.html#_8_15_0
https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/8.15/observability.html#_opentelemetry


An unexpected error occurs when launching Storage Explorer

Storage Explorer Version: 1.2.0
Platform/OS Version: Windows 10/MacOS High Sierra/Linux Ubuntu 16.04
Architecture: ia32/x64
Build Number: 20180628.2
Regression From: Works well on previous build 20180627.6
Steps to Reproduce:

Launch Storage Explorer.

Expected Experience:
No error occurs.
Actual Experience:
An expected error "Can't find module 'junit-report-builder'"occurs.

@MRayermannMSFT, CTI reports that this issue is still occurring in Linux. Can you verify?

Yes, I should have some down time this weekend to investigate.

Hi @craxal @MRayermannMSFT , This issue also reprodces for 32-bit Storage Explorer on Windows64Bit on the latest build 20180701.1

@v-xuanzh, you should get 32-bit Storage Explorer from Windows32Bit and 64-bit Storage Explorer from WIndows64Bit. I don't know why we're getting four sets of bits in these combinations, but you should not be getting stuff from mismatched folders.

This should now be fixed in latest master builds.


[ISSUE #737] Add Netty license

Fixes ISSUE #737
Motivation

Add license files.

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

@xwm1992 @Shoothzj @pjfanning Take a look? If you are interested.

I have recognized add a lot sub dependencies of netty in project, do we need all these sub dependencies now?
@ruanwenjun @Shoothzj

I have recognized add a lot sub dependencies of netty in project, do we need all these sub dependencies now? @ruanwenjun @Shoothzj

I think there are some binary dependencies we don't need, e.g. netty-codec-redis, netty-codec-dns, I am not sure, need to be careful when deleting. Currently, we need to add the missing LICENSE file.

@ruanwenjun If we don't need, I suggest implement these module separately, I can work on this

@ruanwenjun If we don't need, I suggest implement these module separately, I can work on this

Great, you can open a new issue to optimize the dependency.


Use discard/pick on interactive rebase instead of always pick

This is a small remark regarding the interactive rebase panel.
I find counter intuitive to click on a "pick" button to ignore a commit.
I think it would be more intuitive to have by default the label "discard" on the buttons and to toggle it to "pick" when the commit is discarded.
Thanks again for that great tool to learn/teach git!

I remember why -- because these backbone views are a pain in the butt :P
basically I wanted that opacity transition via CSS, which means that I cant rejigger the HTML (in backbone) since that would destroy and remount the view (and cancel the animation)
I did this with some hacky CSS logic instead!

Omit is indeed much better than discard (4 letters just like pick). Thanks for the update.

Please consider changing the language of the lesson itself to use something besides 'pick' to discuss dropping a commit. It's rather confusing given that 'pick' means to use the commit in the actual rebase interactive editor.

whoops, I'll make a new issues for that. apologies.


v0.6.0 Release

Hoping to do this release sometime next week! Here's a few things that would be nice to have:

[ ] https://github.com/tektoncd/chains/pull/284
[ ] https://github.com/tektoncd/chains/issues/279
[ ] https://github.com/tektoncd/chains/issues/249
[ ] Create a release-0.6.0 branch during this release for docs
[ ] Document how to create the release- branch in our release process

After release I found a bug, which should be fixed by https://github.com/tektoncd/chains/pull/298! Will do a v0.6.1 point release once it's merged.


Add CSS 2D/3D transform features

Because transforms exist in multiple other parts of the platform
(DOMMatrix, canvas, SVG) prefix the names with "CSS".

@ddbeck I've added some descriptions, and it was hard. They could probably be improved.
Also I know we'll have some trouble when trying to compute a baseline status for 3D transforms, because parts of it like backface-visibility are quite new. Let's figure out splitting when we get to that.


Implement CI discovery provider

Implement CI Discovery provider compatible with ci-info package which is used by sectester-js

@ostridm  you don't change API nor change the behavior, this is refactoring

@ostridm you know, I would say this is still refactor since CIDiscovery is internal


how to handle recaptcha expiration event

Is there any way to handle expiration event?


[ci] Entrypoints run upon changes in vllm/

Change dependency for entrypoints test to be vllm/

/ready


Update to Gradle 6.8.3

https://docs.gradle.org/6.8.3/release-notes.html

I'll close this in favor of #58. Once that is merged we'll get the automated PR.


[Bug fix][Version 1.6]Fix ingress SDS not getting secret updates and create unit tests

patch ref: https://github.com/istio/istio/issues/18912
Please provide a description for what this PR is for.
Fix ingress SDS not getting secret updates and create unit tests
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@williamaronli: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.6
1570b80b6b142653fd3f48c69e18e5ed96eb77bc
link
/test lint_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@williamaronli: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.6
1570b80b6b142653fd3f48c69e18e5ed96eb77bc
link
/test lint_istio_release-1.6

unit-tests_istio_release-1.6
1570b80b6b142653fd3f48c69e18e5ed96eb77bc
link
/test unit-tests_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@williamaronli: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio_release-1.6
1570b80b6b142653fd3f48c69e18e5ed96eb77bc
link
/test lint_istio_release-1.6

unit-tests_istio_release-1.6
1570b80b6b142653fd3f48c69e18e5ed96eb77bc
link
/test unit-tests_istio_release-1.6

integ-pilot-k8s-tests_istio_release-1.6
1570b80b6b142653fd3f48c69e18e5ed96eb77bc
link
/test integ-pilot-k8s-tests_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

cc @williamaronli We are intending to get 1.6.6 out Tuesday or so. This will have to wait after.

/retest

@williamaronli: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.6
1570b80b6b142653fd3f48c69e18e5ed96eb77bc
link
/test unit-tests_istio_release-1.6

integ-pilot-k8s-tests_istio_release-1.6
1570b80b6b142653fd3f48c69e18e5ed96eb77bc
link
/test integ-pilot-k8s-tests_istio_release-1.6

lint_istio_release-1.6
1570b80b6b142653fd3f48c69e18e5ed96eb77bc
link
/test lint_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@williamaronli: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio_release-1.6
1570b80b6b142653fd3f48c69e18e5ed96eb77bc
link
/test integ-pilot-k8s-tests_istio_release-1.6

lint_istio_release-1.6
1570b80b6b142653fd3f48c69e18e5ed96eb77bc
link
/test lint_istio_release-1.6

unit-tests_istio_release-1.6
1570b80b6b142653fd3f48c69e18e5ed96eb77bc
link
/test unit-tests_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@williamaronli: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio_release-1.6
8ef59ec47d2341d83d1f460a7e3f0f74386b0fb0
link
/test unit-tests_istio_release-1.6

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

cc @williamaronli @JimmyCYJ
Jimmy, can I get an approval from you for this PR? I noticed that it is shorter than the original.

Thanks @jacob-delgado, just reviewed and approved. The original PR has a test file, and the fix is the same.


Economic calculator for Eth2.0

Currently, in order to understand the exact economic implications of being a validator, a very careful reading of the spec is required in order to know what the exact risks and benefits are. We want to create more transparency around this issue by adding a visual calculator, that given a number of inputs will show what the individual validator stands to gain and lose.
Target group: Individuals running validators and economists analysing Eth2.0 incentives for validators
Technology: This should probably be a web app, ideally a node module that can either run standalone or be integrated into another app such as a validator client GUI to give more information to the user
Inputs:

Should be a number of sliders:

expected online time
cost to run validator node (electricity/hardware deprecation/cloud rental)
cost of capital
probability of failures that lead to penalties and/or slashing (equivocation, key reveals, incorrect custody bits, missing of custody deadlines, incorrect attestations (fraud proofs))
probability of those failures being caught by a second "don't slash" layer that polices validator client outputs
probability that these failures are correlated with other validators (fraction of other validators using the same client software)
number of competing validators (with same settings or different settings)

Ability to load custom configurations (mainnet, testnet, etc.)

Outputs:

numerical outputs showing the expected returns with variance and total probability of slashing
a graph that shows expected profits and losses as a diagram per time period
a graph that shows long-term development of the initial deposit with this expected return
a graph illustrating total ETH inflation

Further ideas on how to improve this are very welcome, this is just an initial set of ideas. The goal should be a tool that can allow people to gain a good intuition on validator rewards and penalties.

Inputs:

Plus the functionality of custom configurations (with mainnet` setting by default):

Rewards and penalties configurations
Gwei values

Would also be nice to show global ETH inflation based on number of active/online validators.

Added these :)

Pinging @econoar who may be interested in contributing :)

This seems easily doable with a spreadsheet. Haven't some of these crypto research orgs done one already?

Good point, that may very well be a more maintainable solution to this problem. Would be interested if it exists already?

Here is a spreadsheet some Consensys people worked on: https://docs.google.com/spreadsheets/d/1zU1wzlDsw-BPWp5d4eJMJLHGuCbB_UJ2rPLP7eanW9I

I just updated it with the most recent formulas based on the frozen phase 0 spec.
Perhaps the most surprising (though really not so surprising) finding is just how low issuance gets if you assume even a slightly less than 100% average online rate (eg. 90% gets you 1.11% issuance instead of 1.51%)

Here is a spreadsheet Collin Myers worked on: https://docs.google.com/spreadsheets/d/1zU1wzlDsw-BPWp5d4eJMJLHGuCbB_UJ2rPLP7eanW9I

Haven't seen it before, and it's very informative!
I think the point of this calculator is to get more attention and interactivity. But indeed maintainability is an important factor.
I will ping Collin to get more insight.

Hey Everyone! Excited this topic is getting some traction as I have been focused on it for a while. Shoutout to V for updating the model with the Phase 0 freeze metrics. I am currently working to refine/simplify the model and produce insightful network level sensitivity charts. I will update the group and send the new model when finished!

I will update the group and send the new model when finished!

@collinjmyers Are you still working on the economic calculator? If so, could you share an update? :)

https://docs.google.com/spreadsheets/d/15tmPOvOgi3wKxJw7KQJKoUe-uonbYR6HF7u83LR5Mj4

Check out the Telegram group @eth2calculator - I will be doing a few updates to the model on Tuesday to model out the 500K threshold and include in the graphs

Closing in favor of ConsenSys Codefi team's work :)


Infinate loop in Result iterator for DML commands

Some SQL commands can produce an infinite loop iterating the result set.
Ive tracked this down to them producing either unsupported protobuf types (eg. type 1)
or 0 columns (may be related).
The 0 column problem results in the iterator code to not advance the CSV pointer -- e.g the conditions never call the appropreate methods to read more from the CSV file if there are ' 0 columns' (triggered likely by the former issue) .
Examples to try
SHOW TABLES
MSCK REPAIR TABLE tablename

src/main/java/io/burt/athena/result/csv/VeryBasicCsvParser.java
If columnCount ends up 0 then next() never advances.

src/main/java/io/burt/athena/result/csv/VeryBasicCsvParser.java
If columnCount ends up 0 then next() never advances.

Thank you, good catch. Would you like to take a stab at fixing it? You've already identified the source of the CSV parsing issue. I think you can duplicate this test https://github.com/burtcorp/athena-jdbc/blob/b0268c9ee63f52a10b5713259203f0daf504ff80/src/test/java/io/burt/athena/result/csv/VeryBasicCsvParserTest.java#L100-L111 and change the 3 (the number of columns) to a 0 to trigger the bug (also duplicate the corresponding test for hasNext).

Thank you, good catch. Would you like to take a stab at fixing it? You've already identified the source of the CSV parsing issue. I think you can duplicate this test https://github.com/burtcorp/athena-jdbc/blob/b0268c9ee63f52a10b5713259203f0daf504ff80/src/test/java/io/burt/athena/result/csv/VeryBasicCsvParserTest.java#L100-L111 and change the 3 (the number of columns) to a 0 to trigger the bug (also duplicate the corresponding test for hasNext).

The driver in this repo is no longer maintained, please have a look at the official Amazon Athena JDBC driver v3 instead.


Add a stream client message interface

The clientpublish accepts a pure amqp 1.0 message.
need to create a specific stream message because:

need to add more information like publishingid
in the future implement another codec

closed via https://github.com/rabbitmq/rabbitmq-stream-go-client/pull/47


Getting ac-model and ac-options attributes must be set error even though they are set

Here is my ac-select tag
<ac-select ac-model="selectedColour" ac-options="c.name for c in colours"  ac-change="colourChanged(value)"></ac-select>
Using angular 1.2.1 with requireJS
Full error -
ac-model and ac-options attributes must be set <div class="ac-select-wrapper ng-isolate-scope" ng-keydown="keyHandler($event)" tabindex="999" ac-focus="wrapperFocus" ng-focus="comboFocus = true" ac-model="selectedColour" ac-options="c.name for c in colours" ac-change="colourChanged(value)">

If you're getting the message "ac-options and ac-model attributes must be set", even though you've set the attributes, it's most likely because the scope variable pointed to by the ac-model attribute is undefined when ac-select initialises. E.g. if you have ac-model="myModel", try including the line
$scope.myModel = null;
or
$scope.myModel = [some value];
at the start of your controller.


Allow using various git diff options for comparisons

Instead of having to do funky stuff with soft git resets, this allows the user
to pass a --diff option.  This option can be anything that works with both
git diff-tree and git rev-list.  This option does not work with mercurial
yet.  This is particularly helpful in CI pipelines that rely on PRs.
Effectively, you run git lint --diff 'HEAD ^<target-branch>'
The change basically works by looking at all the commits that are different
instead of just the --last-commit.  It uses the git rev-list command to
determine which commits are different.  It then uses the same modified_lines
function with a slight modification.  modified lines now uses a regex OR
condition for all of the commits instead of just one commit.

Addresses #60 and #110

Thanks @timmartin19 for the PR, I like the idea, but would like to clarify and simplify some things.

With this option --last-commit could be simplified to mean --diff=HEAD^..HEAD.
We should somehow restrict the diff to be only made against HEAD, because otherwise the results are going to be (mostly) meaningless. If you need to diff a range that's not ending in HEAD you actually need to reset the repo so that the results are accurate.
Will this work in a CI environment, I know that the repo is in a weird state in which the HEAD is dettached.
We would need to have an integration test to validate that the listing of the files is working as intended.

@sk- I think you're absolutely right about always comparing against HEAD.  What if it was something like this git lint --diff <commit|branch> and we always compare that commit/branch against the current HEAD?  For example, this PR might use git lint --diff master which would translate to git diff-tree master..HEAD.  In this case, git lint --diff HEAD^ would be equivalent to git lint --last-commit
I don't think a detached HEAD will cause any problems since we aren't making any changes nor committing.  That being said, I'll play with it in a branch in my fork on travis and play with it in Jenkins.

I checked whether it worked with travis.  Do to their use of --depth=50 when cloning, you need to do one of two things:

Tell travis not to use depth when cloning.  In your .travis.yml
git:
depth: false

Explicitly overwrite the configuration before running git lint
git config --replace-all remote.origin.fetch +refs/heads/:refs/remotes/origin/

@sk- Is there anything else you need for this PR?

@timmartin19 Hi Tim, the fact that you still need to wrangle with the git settings in order to be able to run it in Travis makes me doubt about the general usefulness of the PR, as the motivating case was exactly to support CI (hence the mention of git reset).

@sk- That's a quirk of travis as far as I can tell.  We're running it in Jenkins now with no special adjustments and it's working just fine.  Also, this does not break (like the current CI mechanism) when you force push.


[memgraph-2.12 < Storage mode flag ] Add storage mode flag for starting Memgraph

Description
Added storage mode flag for starting Memgraph.
Pull request type
Please check what kind of PR this is:

[x] Fix or improvement of an existing page
[ ] New documentation page, release related

Related PRs and issues
PR this doc page is related to:
https://github.com/memgraph/memgraph/pull/1282
Closes:
(paste the link to the issue it closes)
Checklist:

[ ] Check all content with Grammarly
[ ] Perform a self-review of my code
[ ] Make corresponding changes to the rest of the documentation (consult with the DX team)
[ ] The build passes locally
[ ] My changes generate no new warnings or errors
[ ] Add a corresponding label
[ ] If release-related, add a product and version label
[ ] If release-related, add release note on product PR

non-empty db in on disk will always restart as on-disk - true or false?
the instance in an in-memory analytical storage mode will revert to the default in-memory transactional storage mode - true or false if I change this setting?


CookieAuthenticationHandler, in case using SessionStore, cookieOptions.Expire is not set on renewal

I think I found an issue in Microsoft.AspNetCore.Authentication.Cookies.CookieAuthenticationHandler class, method FinishResponseAsync. There is a line of where cookieOptions.Expire property is set if IsPersistent is true. The problem is that, in case of using a SessionStore, ticket.Properties.IsPersistent is always false, because in that case ticket is assigned a new instance with clean options.
So the cookie send to the browser is now a session cookie and when the browser is closed and reopened, the user must login again.

I'm investigating.

Good catch. A fix is being worked on.

Great. Actually I discovered this problem in my current project which uses Microsoft.Owin.Security.Cookies. I also created an issue at the Katana project, but there seems to be no activity.
After I found the problem, I just thought: lets look it the problem still exists in the aspnet core code :-)

Thanks for reporting the issue, @JaapMosselman !

https://github.com/aspnet/Security/commit/0152691108717bd74cc5f0406e7b745b31c8ca23


Boyfriend Floating

Describe your bug here.
Boyfriend floats no matter what i do..Even if i change it he still floats...Can you please fix this?
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
Only the character..But it wont fix

There is something called character editor and offsets, you know that those exist... right?

There is something called character editor and offsets, you know that those exist... right?

He's saying that even if he changes the character position values, bf still floats

I Figured it out....There was a second bf.chr file in the mods folder


rare texture bug?

There is a bug where the texture instead of duplicating itself simply extends the edge pixels as a result:

is it a bug or did I do something wrong in the configuration?

I have the same one

我有同样的一个，在导入选项卡中启用“重复”的情况下重新导入纹理的精灵

Hi, I have the same problem in godot 4.2, but it seems that there is no "REPEAT" option in the "Import" menu now? Is it just me or has the engine been updated with a new interface?

我有同样的一个，在导入选项卡中启用"重复"的情况下重新导入纹理的精灵

嗨，我在 godot 4.2 中遇到了同样的问题，但现在似乎“导入”菜单中没有“重复”选项？是只有我一个人，还是引擎已经更新了新的界面？

我有同样的一个，在导入选项卡中启用“重复”的情况下重新导入纹理的精灵

Hi, I have the same problem in godot 4.2, but it seems that there is no "REPEAT" option in the "Import" menu now? Is it just me or has the engine been updated with a new interface?

I solved the problem！godot removed the material editing on import in the new version and merged it into the node's familiarity, now you just need to check the node SS2D_Shape_Closed "texture" and you'll find the "repeat"

For Godot 3.x, reimport the texture with repeat enabled.
For Godot 4.x, either use the Texture -> repeat option inherited from CanvasItem or use a CanvasTexture as explained here.


IGNITE-11277: maven checkstyle plugin config

Hello, Maxim.
Thank you for the PR!

Should we remove idea inspection file? At lease, the one to run on TC?
What about other already enabled inspections? SizeReplaceableByIsEmpty, RedundantSuppression, MissingOverrideAnnotation?

Hello, Nikolay.
Thank you for your comment.

After the PR will be merged (if it will) we will get Inspection Suite and Checkstyle working both simultaneously. After we make sure that checkstyle work as expected and community adopted to new build procedure (I expect a day or two) I will create a new issue to disable the Inspection Suite and delete corresponding inspections configuration.
Is it a plan you expect?

The short answer is - there is no analogue of a checkstyle module to previously configured inspections. I've mentioned everything about it in my comment in JIRA. See: IGNITE-11277?focusedCommentId=16771200


[Manual] - The "Comment" screen is closed after adding of a reply to the comment

Commit number: e3e3c42435fb7c1f7d4fee745fcb36133fe69929
Preconditions: Test user is signed in
Steps to reproduce:

Add a post
Open the post and add a comment
Open the comment and add a reply

Actual Result: The "Comment" screen is closed after adding of a reply
Expected Result: The "Comment" screen is opened. The reply is added to the comment

Unable to reproduce on build from commit number 2be778f8f31728dd41a25cd85e5fdfc391969a3f


Feature: list custom sheets only

This pull request implements a requested feature.
Closes #380

@Gisson, thanks for your work here, and I'm sorry it never got merged in.
cheat v2 was causing all sorts of headaches, so I re-implemented v3 from scratch, and in Go versus Python. That being the case, I'm going to close this PR, as it's now moot.
The good news is that cheat v3 now supports this feature via the -p flag. Please upgrade and give it a try.
Thanks again.


CASE: Send busy status report if we receive a sigma1 and we are in the middle of handshake

With #27226,  Unsolicited message handler will never be unregistered and CASEServer can still receive a Sigma1. If we are in the middle of a handshake then do send out Busy status report.
Fixes #27473
Tests

Tested with lighting-app/esp32 and chip-tool. [lightin-app/linux was too quick to reproduce this behaviour]

# Commissioning and access control
./chip-tool pairing onnetwork-long 21 20202021 3840
./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode":2, "subjects": [ 112233, 1213], "targets": null}]' 21 0x0

# Simultaneously sent below two commands from two different terminals
./chip-tool onoff toggle 21 1
./chip-tool onoff toggle 21 1 --commissioner-nodeid 1213

Log on ESP32

I (23613) chip[SC]: Already in the middle of CASE handshake, sending busy status report

Log on chip-tool

[1689917761627] [26247:8748806] [SC] Received error (protocol code 4) during pairing process: src/protocols/secure_channel/CASESession.cpp:1978: CHIP Error 0x000000DB: The Resource is busy and cannot process the request
[1689917761627] [26247:8748806] [SC] Received busy status report with minimum wait time: 500 ms
[1689917761627] [26247:8748806] [IN] SecureSession[0x7f84e94274d0]: Released - Type:2 LSID:44016
[1689917761627] [26247:8748806] [-] src/protocols/secure_channel/CASESession.cpp:1978: CHIP Error 0x000000DB: The Resource is busy and cannot process the request at ../../examples/chip-tool/commands/clusters/ModelCommand.cpp:62

After #28219 got merged, added the SendStatusReport() API on ExchangeContext, so that protocols can use that helper function and to reduce the code duplication.


ListView.builder overflows

Please refer to this thread: https://stackoverflow.com/questions/68789121/listview-builders-builder-items-are-overflowing

It seems you answered your question on SO yourself so you can close the ticket here.

Yeah! But I would like to know the reason behind this. Is this the default behaviour?

It seems like you're not showing all the relevant code.

This is the relevant code I guess because when I only ran this specific code in a new widget, the behaviour was same.

No, it's not all the relevant code. Where is the column visible in your code? Most probably the error lies there since in there you define the available space for the listview.

That's what I told you in the previous reply that the behaviour is same even when the ListView is the root Widget.

I doubt that since "done tasks" is not even in there, so the behaviour for sure changes. But anyway, if you're certain that you don't need to show more code then I can't help further.

Here you go. Please don't mind the extra code.
void main() {
  debugPaintSizeEnabled = true;
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MultiProvider(
      providers: [
        ChangeNotifierProvider(
          create: (context) => AuthProvider(),
        ),
        ChangeNotifierProvider(
          create: (context) => TodoProvider(),
        ),
      ],
      child: Consumer<AuthProvider>(
        builder: (context, authProvider, child) => MaterialApp(
          theme: ThemeData(
            primaryColor: Color(0xFFFFAF49),
            scaffoldBackgroundColor: Color(0xFFF9F9F9),
          ),
          debugShowCheckedModeBanner: false,
          // home: authProvider.isAuthenticated ? HomeScreen() : AuthScreen(),
          home: Scaffold(
            body: SizedBox(
              height: 200,
              child: ListView.builder(
                itemCount: 20,
                itemBuilder: (context, index) {
                  return Padding(
                    padding: const EdgeInsets.only(bottom: 8.0),
                    child: ListTile(
                      title: Text(index.toString()),
                      tileColor: Colors.red,
                    ),
                  );
                },
              ),
            ),
          ),
        ),
      ),
    );
  }
}

Output

Can you please tell me why is it happening now?

Hi @dipanshparmar,  when filing issues in the future please try to fill all are some of the info requested in the issue description This helps to better investigate the issue. There seems to be a similar issue describing this case, You may follow there for further updates.
Closing this issue as a duplicate.
Thanks, @sebastianbuechler for volunteering.

Thanks, @maheshmnj for confirming that it is a bug, and I will make sure to provide all the information while creating an issue next time. Once again Thank you.