aws_launch_configuration.this (deposed #0): ResourceInUse: Cannot delete launch configuration because it is attached to AutoScalingGroup.

Hi,
When I try to add associate_public_ip_address to launch configuration, terraform apply failed with following error:
Error: Error applying plan:

2 error(s) occurred:

* module.zabbix_app_asg.module.launch_configuration.aws_launch_configuration.this (destroy): 1 error(s) occurred:

* aws_launch_configuration.this (deposed #0): 1 error(s) occurred:

* aws_launch_configuration.this (deposed #0): ResourceInUse: Cannot delete launch configuration zabbix-app-lc-20171125225647460700000002 because it is attached to AutoScalingGroup
	status code: 400, request id: 19197d51-d235-11e7-8d7b-19219f15fe4b
* module.bastion_ec2.aws_instance.this: aws_instance.this: diffs didn't match during apply. This is a bug with Terraform and should be reported as a GitHub Issue.

Terraform version
Terraform v0.11.0
+ provider.aws v1.3.1

Error Log
autoscaling_terraform.bug.log
Stemps to reproduce

terraform init
terraform apply
uncomment associate_public_ip_address properties in launch configuration
terraform apply (Error)

Example
TF-Example2.zip

Thanks for opening issues in terraform-aws-modules. There are two different issues in this one:

aws_launch_configuration.this (deposed #0): ResourceInUse: Cannot delete launch configuration zabbix-app-lc-20171125225647460700000002 because it is attached to AutoScalingGroup - this is related to this module and I will work on it during few hours today.
module.bastion_ec2.aws_instance.this: aws_instance.this: diffs didn't match during apply. This is a bug with Terraform and should be reported as a GitHub Issue. - let us track it separately.

I am having the same issue regarding the ResourceInUse problem when trying to change the AMI_ID

https://github.com/terraform-aws-modules/terraform-aws-autoscaling/releases/tag/v2.0.0 - is released. Please read README and report about any issues you can find.

@nodefortytwo - I believe this problem has been also fixed in the release of v2.0.0

works well for me, thanks!

On 28 Nov 2017, at 20:11, Anton Babenko<EMAIL_ADDRESS>wrote:
https://github.com/terraform-aws-modules/terraform-aws-autoscaling/releases/tag/v2.0.0 https://github.com/terraform-aws-modules/terraform-aws-autoscaling/releases/tag/v2.0.0 - is released. Please read README and report about any issues you can find.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/terraform-aws-modules/terraform-aws-autoscaling/issues/8#issuecomment-347594225, or mute the thread https://github.com/notifications/unsubscribe-auth/AP2L3tbFm0eHD7bLSFRCndzUmL5oVsXoks5s7D65gaJpZM4QqtAo.


tf_tree not aligned with trajectory

Hi,
Thank you very much for your fantastic work.
When  I was trying to run googleCartographer for my robot, I found that my tf tree does not align with the trajectory_node_list in RVIZ, unlike what your demo shows.
You may take a look at my screen shot here:
https://drive.google.com/open?id=1aSLKyzCwZJ_hsQWVw-Db-ZLsv6pbJiXF
It confuses me a lot, so I update cartographer_ros into the latest version and post the configuration files online so that you can reproduce my trouble.
1, I uploaded my rosbag here: https://drive.google.com/open?id=16qh_OzVbFOqkddDD5Eb1pdY9Ylg3e3jT
2, I also run rosbag_validate to check my rosbag data. The result is posted here https://gist.github.com/BoomFan/5c75e857e10881a935c982203f18e883
3, My cartographer_ros brach was uploaded here https://github.com/BoomFan/cartographer_ros_for_rover.git
You may run my configuration by roslaunch cartographer_ros rover_offline_no_state_estimator.launch bag_filename:=${HOME}/Downloads/rover_lab_joy_20171205.bag
I know that my imu_frame is not located at the same position as my robot  base_link and it is facing downward so it has a raw angle = 3.1416. Could this be a reason why tf_tree is not aligned with trajectory?  BTW I also noticed that my map got flipped after the first few seconds. Does that also come from a down-facing IMU?
Thanks again for your time.
look forward to your reply.

I'll try to give a quick, partial answer for now and hope that helps you to setup things.
Your validate results for the bag file look good.
Looking at your https://github.com/BoomFan/cartographer_ros_for_rover/blob/master/cartographer_ros/configuration_files/rover_no_state_estimator.lua I'd recommend not to change so many parameters at once.
Yeah, you need to set the transform between base_link and imu_frame correctly. Your map should definitely not flip.
Please disable IMU TRAJECTORY_BUILDER_2D.use_imu_data = false and try to tune the scenario without IMU first, only if this works well try to add IMU again with correct urdf settings.
(Also, for testing you could disable global SLAM MAP_BUILDER.pose_graph.optimize_every_n_nodes = 0 even though I don't think this is the issue here.)

@gaschler
Thanks for your reply!
I tried to turn off the use_imu_data  and I also tried to set MAP_BUILDER.pose_graph.optimize_every_n_nodes = 0, but none of these slove my tf_tree problem.
I'm pretty sure that my urdf file makes sense. So I take a look at this file https://github.com/googlecartographer/cartographer_ros/blob/master/cartographer_ros/cartographer_ros/node.cc and I print out the variables in line 230. I found that *trajectory_state.published_to_tracking is always 0. Do you think that might be a problem? Do you mind pointing out where am I able to fix this issue, please? I tried to go to MapBuilderBridge::GetTrajectoryStates() but I am not sure what I can do over there.

I checked your bag file with (the latest version of) cartographer_rosbag_validate, see below.
The error says that topic "scan" has contradicting information about sensor time stamp and serialization time, by more than a second. Cartographer always uses the sensor time.
Rviz may use the first one and extrapolate wildly, which explains your observation.
I also looked at rqt_bag rover_lab_joy_20171205.bag.
The IMU topic has the same time stamp contradiction.
Also, the sensor data drops many frames between 30--35 seconds which is not ideal.
There no easy way to fix your input data other than recording it again properly, because you wouldn't know how to correct your time stamps (which one is correct).
E1213 17:43:33.715487 147045 rosbag_validate_main.cc:286] frame_id "lidar_link" on topic /scan has serialization time<PHONE_NUMBER>.709794048 but sensor time<PHONE_NUMBER>.816328785 differing by -1.89347 s.
E1213 17:43:33.716337 147045 rosbag_validate_main.cc:286] frame_id "lidar_link" on topic /scan has serialization time<PHONE_NUMBER>.709823381 but sensor time<PHONE_NUMBER>.841436233 differing by -1.86839 s.
E1213 17:43:33.716467 147045 rosbag_validate_main.cc:286] frame_id "lidar_link" on topic /scan has serialization time<PHONE_NUMBER>.709847013 but sensor time<PHONE_NUMBER>.866149514 differing by -1.8437 s.
I1213 17:43:33.969271 147045 rosbag_validate_main.cc:332] Time delta histogram for consecutive messages on topic "/imu/imu" (frame_id: "imu"):
Count: 6327  Min: 0.003908  Max: 0.014986  Mean: 0.010000
[0.003908, 0.005016)	                    	Count: 1 (0.015805%)	Total: 1 (0.015805%)
[0.005016, 0.006123)	                   #	Count: 466 (7.365260%)	Total: 467 (7.381065%)
[0.006123, 0.007231)	                    	Count: 60 (0.948317%)	Total: 527 (8.329382%)
[0.007231, 0.008339)	                    	Count: 12 (0.189663%)	Total: 539 (8.519046%)
[0.008339, 0.009447)	                    	Count: 6 (0.094832%)	Total: 545 (8.613877%)
[0.009447, 0.010555)	    ################	Count: 4991 (78.884148%)	Total: 5536 (87.498024%)
[0.010555, 0.011662)	                  ##	Count: 754 (11.917180%)	Total: 6290 (99.415207%)
[0.011662, 0.012770)	                    	Count: 32 (0.505769%)	Total: 6322 (99.920975%)
[0.012770, 0.013878)	                    	Count: 4 (0.063221%)	Total: 6326 (99.984192%)
[0.013878, 0.014986]	                    	Count: 1 (0.015805%)	Total: 6327 (100.000000%)
I1213 17:43:33.969413 147045 rosbag_validate_main.cc:332] Time delta histogram for consecutive messages on topic "/scan" (frame_id: "lidar_link"):
Count: 2557  Min: 0.019652  Max: 0.030235  Mean: 0.025048
[0.019652, 0.020710)	                    	Count: 3 (0.117325%)	Total: 3 (0.117325%)
[0.020710, 0.021768)	                    	Count: 1 (0.039108%)	Total: 4 (0.156433%)
[0.021768, 0.022827)	                    	Count: 4 (0.156433%)	Total: 8 (0.312867%)
[0.022827, 0.023885)	                    	Count: 16 (0.625733%)	Total: 24 (0.938600%)
[0.023885, 0.024943)	             #######	Count: 952 (37.231129%)	Total: 976 (38.169731%)
[0.024943, 0.026002)	        ############	Count: 1553 (60.735237%)	Total: 2529 (98.904968%)
[0.026002, 0.027060)	                    	Count: 20 (0.782167%)	Total: 2549 (99.687134%)
[0.027060, 0.028118)	                    	Count: 4 (0.156433%)	Total: 2553 (99.843567%)
[0.028118, 0.029177)	                    	Count: 2 (0.078217%)	Total: 2555 (99.921783%)
[0.029177, 0.030235]	                    	Count: 2 (0.078217%)	Total: 2557 (100.000000%)
I1213 17:43:33.969516 147045 rosbag_validate_main.cc:332] Time delta histogram for consecutive messages on topic "/rover/odometry" (frame_id: "odom"):
Count: 1262  Min: 0.025073  Max: 0.071399  Mean: 0.049998
[0.025073, 0.029706)	                    	Count: 3 (0.237718%)	Total: 3 (0.237718%)
[0.029706, 0.034338)	                    	Count: 5 (0.396197%)	Total: 8 (0.633914%)
[0.034338, 0.038971)	                    	Count: 29 (2.297940%)	Total: 37 (2.931854%)
[0.038971, 0.043603)	                  ##	Count: 96 (7.606973%)	Total: 133 (10.538827%)
[0.043603, 0.048236)	               #####	Count: 323 (25.594296%)	Total: 456 (36.133121%)
[0.048236, 0.052869)	             #######	Count: 465 (36.846275%)	Total: 921 (72.979401%)
[0.052869, 0.057501)	                ####	Count: 235 (18.621237%)	Total: 1156 (91.600632%)
[0.057501, 0.062134)	                   #	Count: 67 (5.309033%)	Total: 1223 (96.909668%)
[0.062134, 0.066766)	                    	Count: 31 (2.456418%)	Total: 1254 (99.366089%)
[0.066766, 0.071399]	                    	Count: 8 (0.633914%)	Total: 1262 (100.000000%)

Closing as answered, feel free to reopen if needed.


[Parse] rdar://41154797 Detect eof in non-string-arg recovery loop in #error arg list.

The parser could hang while trying to recover from an unexpected token in the arg list of a pound-diagnostic, and met with and unterminated token. Fix this by noticing eof in the loop.
rdar://41154797

@swift-ci please test


DEV-14263 Add AES256 SSE on bucket objects.

Didn't catch this while testing SSE-S3 changes.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


print out warning when boxing directories that don't exist

if you have
box := packr.NewBox("./foo")

And ./foo doesn't exist, then you run packr.... it just exits cleanly and does nothing.
I think this merits a warning or something, telling me that I'm probably doing something wrong.

I've done this like a dozen times today, where I want to pack the generated docs, only to have deleted and not re-generated them, and it makes it look like there's a bug in packr, that it's not creating the packr file.  Obviously, that's a user error, but it would be nice to be given a warning that I'm being dumb :)


Update Readme regarding features, supported platforms, manifest, help texts, config section....

The https://github.com/esrlabs/northstar#readme is horribly outdated and needs some love.

Work started in doc

Superseded by #426


Feature/new config

We are going to switch to yaml based configuration. This branch is no deprecated.


Fix example

#skip-changelog
:scroll: Description

@marandaneto We already have example/readme.md. All i did is rename the file, as this is how it's documented on https://dart.dev/tools/pub/package-layout#examples. But from the documentation this should have also worked before.
:bulb: Motivation and Context

Closes #84
:green_heart: How did you test it?
Run CI
:pencil: Checklist

[x] I reviewed submitted code
[ ] I added tests to verify changes
[ ] I updated the docs if needed
[ ] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

Running 'pana' locally now yields 10/10 points for the example. (https://pub.dev/help/scoring)


Dice Modification - Future Additions

First of all. To our dear system maker.
Me and all my players love your work.
Some ideas for future options that come to me after seeing the new options for dice modification.

Reading Adversary talent. Could work just like reading the Defense I suppose? Would be a cool addition.
Something far more complex I imagine. Similar system for Social Challanges where targeting a character during an encounter with a Social skill automatically reads that targets opposing skill. Though with how skills operate I imagine that might require quite a bit of setup.

Ty for the kind words!

You can kinda emulate this by creating the Adversary talent and adding an effect on it that upgrades the difficulty of any check they are the target of. The only problem is that this will only apply once since dice pool modifications do not take into account ranks. You can go to the copied effect on the adversary and edit that to include the proper number of upgrades though. Alternatively, you could create multiple Adversary talents with the effect adjusted as needed. I know it's not ideal but hopefully this helps in the meantime.
I've though about this and no solution convinces me as of yet, but I hope to implement something similar at some point in the future.


ColumnRange Chart: datalabel not showing

In the ColumnRange chart of the example project the datalabels do not show up although
.dataLabelEnabledSet(true)
is set properly. Why do the labels not show? Thanks.

It is a bug. I can fix that,wait me for some time!


testing redirects

Docs Build status updates of commit 51cb929:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:bulb:Suggestion

Details

.openpublishing.redirection.json

Line 155, Column 101: [Suggestion-redirect-url-invalid] Can't redirect document ID for redirected file 'voicecommands/launch-a-foreground-app-with-voice-commands-in-cortana.md' because redirect URL '/windows/uwp/design/input/cortana-launch-a-foreground-app-with-voice-commands' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 51cb929:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:bulb:Suggestion

Details

.openpublishing.redirection.json

Line 155, Column 101: [Suggestion-redirect-url-invalid] Can't redirect document ID for redirected file 'voicecommands/launch-a-foreground-app-with-voice-commands-in-cortana.md' because redirect URL '/windows/uwp/design/input/cortana-launch-a-foreground-app-with-voice-commands' is invalid or is in a different docset. Specify a redirect_url in the same docset, or set redirect_document_id to false in .openpublishing.redirection.json.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit d29cf3f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit d29cf3f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Scrollbar with herocard on IE and Firefox

When my webpage is loaded, an event is sent to the backend.
A welcome message in the form of a hero card is shown to the user.
In Google Chrome the card is displayed correctly, but in IE, EDGE and Firefox, a vertical scrollbar appears on the right, and half of the hero card is hidden from view.
This problem occurs since the latest version of the webchat library.

@corinagum can you repro it on latest version?

@compulim able to repro on latest, 0.14.2 on IE, Edge, and Chrome

I believe it has to do with the width of .wc-adaptive-card being 414px instead of something like 350px.


vNext: four copies of the mouse pointer are visible in OpenVR if the mouse has not been moved

Does this affect the legacy HoloToolkit (master) or the Mixed Reality Toolkit (mrtk_release)?
Mixed Reality Toolkit
Describe the bug
At app startup (with spatial mouse enabled) when running on OpenVR, there are four copies of the mouse pointer; one each at roughly the cardinal directions.
Once the mouse is moved, they consolidate into one.
To Reproduce

Open create a scene
Set build platform to Standalone and use the OpenVR SDK
Launch the app in play mode
Note the extra mouse pointers
Move the mouse
Pointers are consolidated

Expected behavior
There to be only one mouse pointer.
Actual behavior
There are four until physically moving the mouse

Pretty sure there only ever is one mouse pointer. Likely the position is moving very quickly between these four points. I'll look into this.

I can't seem to repro with your steps. Is there any additional info you can give me?

it is possible that it is related to the combination of this and #2750. let's revisit this once that PR is complete


Add junit test report in github actions

When a Junit test fails, its hard to identify which test had failed because of the size of the log file.
A github action to publish the Junit test report will be useful.
      - name: Publish Test Report
        uses: mikepenz/action-junit-report@v4
        if: success() || failure() # always run even if the previous step fails
        with:
          report_paths: '**/build/test-results/test/TEST-*.xml'

Junit test report was added to github actions.


Show the experimental running status more prominently;

What would you like to be added:More prominently show the experimental running status

Why is this needed:At present, NNI supports the rendering interval. When the interval is long, the user may not know the running state of the experiment. Because the page is completely static, the position of the running state is not obvious. I hope WebUI can add a dynamic flag to display the experiment's running state.
Without this feature, how does current nni work：normally
Components that may involve changes:Running state
Brief description of your proposal if any:Maybe add a dynamic logo instead of "running“.


why not a simple sqlite rather than a mysql dependency?

just as the title

+1

Now supported sqlite。
mysql is for long-term development in the future


Regarding Data Annotations support in EFCore.

Hello,
Regarding Data Annotations support in EFCore.
Currently the MaxLength attributes are working fine with model decoration, however we saw that ForeignKey by throwing an error like "System.InvalidOperationException"  "composite primary key"
Sample decoration which is not supported in EFCore
[DataMember, Key, Column(Order = 0), ForeignKey("Role")]
public Int32 RoleId { get; set; }
Could you please update us on

In future can we expect all Data Annotations will be supported
Is it a best practice to follow Fluency API when compared to Data Annotations, Could you please share us the benefits in following

Thanks
Naren

@narenkv Column ordering is not currently supported at all, whether using data annotations or not. See issue #2272. This item is currently on our backlog and we don't plan to implement it in the near future. There are several opinions on whether or not it is a good idea and how far to go with it if it is a good idea.
We are unlikely to implement composite key support using data annotations. It has several issues, such as the column order for the table not necessarily being the column order for the key, even though EF6 assumed that it was.
More generally, EF has always supported a subset of data annotations and continues to do so, although the subset has changed slightly. It has also always been the case that data annotations supported only a subset of the configuration that could be done through the fluent API, and this also remains the case in EF Core.
Whether or not using data annotations is best practice or not depends on your design philosophy. If you like them, then feel free to continue using them, but be aware that there may be some types of configuration that you need in your model that cannot be accomplished with data annotations.

Thanks


chore: update to tree-sitter 22.6

This PR closes #4 and updates tree-sitter to the most recent versions. Most of this diff is auto-generated code, and I'll highlight my actual changes with inline remarks.

Thanks for your contribution, I had to fix some changed in the test process but it works with the last version of tree-sitter ! Thanks again


Fix flaky E2E tests

Some E2E tests used week numbers based on current date which caused them to break near the end of the year. Values are now hard-coded and will work regardless of current date.

Okay, this approach does not work with current week browser implementation.


Fix the targets-one Action Models test

We'll have to wait for CableReady v5.0.0 to get rid of the inverse_of error.

@gazayas Hey, just FYI, CableReady released 5.0.0!

Awesome!


Fix Object.create definition

The prototype argument to Object.create is nullable, see spec.

Thanks, @adrianheine!
Can you share some code that exemplifies the issue that this PR solves? I quickly tested Object.create() and Object.create(null) and Flow accepts both already, but maybe I'm missing something.

The spec you linked states "If Type(O) is neither Object nor Null, throw a TypeError exception", so the type annotation we want for that first parameter is
static create(o: Object | null, properties?: any): any;
static create(o?: any, properties?: any): any;
allows the first parameter to be undefined.

I should also note that the libdef is somewhat for show. We special-case Object.create in the type checker in order to implement more of its behavior, since the type declaration language isn't (yet) sophisticated to describe it completely.
That said, happy to learn more about the background for this change.

Hi, thanks for the great feedback :) I suppose this PR is quite useless. The problem I tried to solve can be seen in the following minimal example:
/* @flow weak */
const options = Object.create(null)

function f(opt) {
  for (opt in options) {
    options[opt]
  }
}

Gives me (with 0.20.1):
options.js:2
  2: const options = Object.create(null)
                     ^^^^^^^^^^^^^^^^^^^ Object.create. This type is incompatible with
  2: const options = Object.create(null)
                                   ^^^^ null

Found 1 error

I didn't investigate and thought this issue had a trivial and obvious cause, but I realized that this issue is not too much about passing null to Object.create.

@adrianheine Do you think the right course of action is to close this issue, then?

Sure, I'd like to get my issue triaged, though. Maybe it's handled in an already-open issue?

I think #1272 should cover it.


warning: failed to evaluate const trackerLength

Describe the bug
warning: failed to evaluate const trackerLength at /Users/liaoxinlei/go/pkg/mod/github.com/go-ping/ping@v1.1.0/ping.go:77:2, reflect: call of reflect.Value.Len on zero Value
To Reproduce
Steps to reproduce the behavior:

swag init --parseDependency --parseDepth=6 --exclude=./copy
Generate swagger docs....
Generate general API Info, search dir:./
warning: failed to evaluate const trackerLength at /Users/xxx/go/pkg/mod/github.com/go-ping/ping@v1.1.0/ping.go:77:2, reflect: call of reflect.Value.Len on zero Value

Your swag version
swag version v1.16.4
Your go version
go version go1.23.2 darwin/amd64
Desktop (please complete the following information):

OS: iOS

Ignore it.


Bump moment to 2.9.3

Status
Ready for review
Description of Changes
Moment is affected by CVE2017-18214 (DoS via crafted date string). Not only is it a dev dependency, sunder does not use this functionality and therefore shouldn't be affected. To avoid receiving and ignoring security notifications, version bump of concurrently is non-trivial and requires code changes. Overriding and bumping version of moment to 2.9.3 in package.json appears to be an easy fix.
Testing
npm run test-e2e on all platforms should suffice.

Rebased on top of latest master to include changes from #106 (chained testing targets). Running through the paces on both platforms now....


Figre out NetCDF vz pizzarr axis order and direction.

Currently have to use aperm to get zarr arrays to look the same as NetCDF. Figure out why and make sure it's handled.

Need to build a somewhat large test dataset to validate things between zarr and netcdf.


Check Page Before Open.

Ionic version:  (check one with "x")
[ ] 1.x
[X] 2.x
[X] 3.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[X] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

Hi IONIC TEEEAM !!
Maybe it's a shit, but I will post it!
At my cenario IONIC Side Menu,  I want not reopen the same page if  it's open.
I just put a one check inside at openPage. (See related code).
Maybe its can be used in a  ionic template.
Expected behavior:

Steps to reproduce:

Related code:
if(this.nav.getActive().component !== page.component){
this.nav.setRoot(page.component);
}
insert any relevant code here

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Your system information:
Cordova CLI: 6.5.0
Ionic Framework Version: 3.0.1
Ionic CLI Version: 2.2.2
Ionic App Lib Version: 2.2.1
Ionic App Scripts Version: 1.3.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Linux 4.4
Node Version: v6.10.2
Xcode version: Not installed

Hello! Thanks for opening an issue with us! As this seems like more of a support question I will urge that you ask this question on our forum or on our slack channel. Thanks for using Ionic!


Project License

Amazing work.
Could not find a license. Would you be kind to specify that?
Thanks.

Project now includes a LICENSE file.


Fix link in descriptor.md

Correct digests-and—verification to digests-and-verification.
Signed-off-by: Lei Jitang<EMAIL_ADDRESS>

LGTM, travis is still borked though.

LGTM

travis failure is unrelated


fix: Update software vars at beginning of '--prep'

Software vars '*_repo_path' keys need to be initialized using the
'_update_software_vars' method.

I verified the problem and then verified the fix both with and without an existing install repo in place.  Because the code is clearly 'broken' for a new user, I took the liberty of merging it.


No syntax highligthing at all.

:PluginList
Plugin 'VundleVim/Vundle.vim'
Plugin 'MarcWeber/vim-addon-mw-utils'
Plugin 'tomtom/tlib_vim'
Plugin 'garbas/vim-snipmate'
Plugin 'scrooloose/nerdtree'
Plugin 'mileszs/ack.vim'
Plugin 'kien/ctrlp.vim'
Plugin 'terryma/vim-multiple-cursors'
Plugin 'tpope/vim-fugitive'
Plugin 'bling/vim-airline'
Plugin 'majutsushi/tagbar'
Plugin 'tpope/vim-commentary'
Plugin 'arnaud-lb/vim-php-namespace'
Plugin 'elzr/vim-json'
Plugin 'othree/html5.vim'
Plugin 'hail2u/vim-css3-syntax'
Plugin 'digitaltoad/vim-pug'
Plugin 'posva/vim-vue'
Plugin 'xsbeats/vim-blade'

vim --version
vim --version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Apr 29 2016 11:28:12)

After installing the plugin vim said "Done!" and the a valid vue file is not getting highlighted. I did checked the other issues, my file is properly spelled like "profile.vue".
I did also run the following:
source ~/.vim/bundle/vim-vue/syntax/vue.vim
run ~/.vim/bundle/vim-vue/syntax/vue.vim

But I didn't get any output, not even errors.
Any ideas?

try set ft=vue

Yes with that it works nice. Why is the ftdetect not working?

It may be about cache, I've already experienced this issue with other plugins. It should be working fine with files that have not be opened before

Well It's not, I tried lastnight with a new *.vue file but it didnt work either. Any idea?

You may have a conflicting command somewhere else

I didnt find the conflicting command so I just edited $VIMRUNTIME/scripts.vim and i added:
  " Vue files
  elseif s:line1 =~ '^<template>*'
    set ft=vue

Since all my vue files start with template vim will set the ft automatically.
Cheers.

You can also check for the .vue filetype, like this:
" Vue syntax highligting
autocmd BufNewFile,BufRead *.vue set ft=vue


Replace SQL authentication by Entra ID only authentication

During the deployment of the SQL dedicated pool, sql authentication is used. For security reasons the authentication method should only allow an Entra ID authentication.
DoD

Replace the sql authentication to entra authentication only in the bicep file
Remove sql password from .env file and dependencies encountered while running the script
Remove sql password from keyvault and dependencies of that value

ADF might have to be updated as well.

Failure here in the pipeline was because of not having SQL auth enabled.


Include P2S Address Space for VNet-to-VNet Connections?

"The difference between the connection types is the way the local network gateway is configured. When you create a VNet-to-VNet connection, you do not see the local network gateway address space."
While this may be simpler, the address space for the connected VNet does not include the P2S address space. Is this by design? It prevents a VNet-Integrated Web App from using DNS servers in a different (though connected) VNet. However, a Site-to-Site connection does work in this situation.

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

ID: 1d655e62-511c-5c94-da5f-8ae2fa48927f
Version Independent ID: a1665237-3ff9-6a47-91ac-fba5f2469ba3
Content: Connect an Azure virtual network to another VNet: Portal
Content Source: articles/vpn-gateway/vpn-gateway-howto-vnet-vnet-resource-manager-portal.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@cubikca thanks for the comment. We are actively investigating and will get back to you soon.

@cubikca This is by design. If you would like your Web App to be able to use DNS servers in a different VNET, you can use an App Service Environment.. If you would like us to change this functionality, please leave your feedback Here.

@cubikca We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


put default version&group from provider and consumer into service metadata.

override getVersion and getGroup.

LGTM


Add flatten, flatten_right and flatten_left methods

I think the Either crate is really good, and here are some methods I would love to see:
flatten
I think there should be a flatten method, like for std::Result and std::Option:
impl<L,R> Either<Either<L,R>, Either<L,R>> {
    pub fn flatten(self) -> Either<L,R> {
        match self {
            Left(x) | Right(x) => x
        }
    }
}

As you can see from the implementation, this is the same as into_inner but I think it is good to have this for two reasons:

The terminology "flatten" is often used for flattening such nested structures

One alternative may be to let flatten use any Either<T,T> (and thus skip combine).
flatten_right/flatten_left
Two more propsed functions are flatten_right and flatten_left:
impl<L,R> Either<Either<L,R>, R> {
    pub fn flatten_left(self) -> Either<L,R> {
        match self {
            Left(x) => x,
            Right(x) => Right(x)
        }
    }
}

impl<L,R> Either<L, Either<L,R>> {
    pub fn flatten_right(self) -> Either<L,R> {
        match self {
            Right(x) => Right(x),
            Left(x) => x
        }
    }
}

flatten_left is just flatten on std::Result, but it is nice to have corresponding left and right methods to strengthen the intuition that there is nothing special with the left or the right variant, they are both considered equal.
I am fine with doing the implementation itself but I would be glad about comments, naming suggestions and general suggestions! Do you think this would be useful? Maybe it would be confusing with flatten and into_inner doing the same thing so I am fine with dropping that, but flatten_left and flatten_right seems useful imo.

Made a PR on flatten_left and flatten_right (but not flatten), see #84

As mentioned on #84:

flatten is Either::into_inner
flatten_left is Either::left_or_else(Right)
flatten_right is Either::right_or_else(left)

If you like, we could add these to the documentation as suggested patterns.


Task definition caching does not work if the task definitions come from separate deployments.

Expectation / Proposal
We just moved from defining our own task-definition for prefect-ecs-task, to letting prefect defining them by itself in runtime.
After the change, we seem to have an issue where prefect defines a task_definition per task. Error from aws:
botocore.errorfactory.ClientException: An error occurred (ClientException) when calling the RegisterTaskDefinition operation: Too many concurrent attempts to create a new revision of the specified family.

Task-definition diff is:

taskDefinitionArn , the revision-number is changed
revision , the revision-number is changed
registeredAt , the timestamp

The main think I see I can change in the work_pool-config regarding this, is: Auto Deregister Task Definition (Optional) , we have tried with this both enabled and disabled.
When doing a simple test like, where the same deployment is deployed multiple times, it runs ok, and same task_definition is used, both with and with out Auto Deregister Task Definition (Optional):
#!/usr/bin/env bash

_run_prefect_task() {
    echo "Trigger task: $1"
    poetry run prefect deployment run 'ecs-task-flow/snowflake_access_test'
    echo "Task done: $1"
}

_run_task_in_parallel() {
    CONCURRENT_RUNS="$1"
    for i in $(seq 1 "$CONCURRENT_RUNS"); do
        _run_prefect_task $i &
    done
    echo "Waiting for tasks to complete"
    wait
}

_run_task_in_parallel 200

Traceback / Example

[ ] I would like to help contribute a pull request to resolve this!

In the case where we are being throttled, we have different deployments using the same image/image-tag, and then could also use the same task-definition.
From looking at: prefect_aws/workers/ecs_worker.py#L735 You can see that we cache the task definition to avoid the over-registering of task definitions, but for this user in particular, they have too many different deployments.
We might have a situation, where what is used as cache-key is the deployment-id, so that results in the same task-definition is added to cache multiple times, and then being created multiple times.  Maybe we could use a hash from the task-definition as cache-key, together with some other values from the worker/deployment, but not the deployment-id?

A small example of when this issue presents an issue for us:
from prefect import flow, deploy
import asyncio
from prefect.deployments.deployments import run_deployment

@flow(log_prints=True)
def hello(deployment_index):
    print(f'hello {deployment_index}')

async def main():
    deployments=[]
    for x in range(200):
        deployments.append(
            await hello.to_deployment(
                name=f"deplyment-{x}",
                parameters=dict(
                    deployment_index=x,
                ),
            )
        )
    deployed_deployments = await deploy(
        *deployments,
        image="same image for all deployments",
        work_pool_name="same workpool for all deployments",
        build=False,
    )
    for uuid in deployed_deployments:
        await run_deployment(
            name=uuid,
            timeout=0,
        )

if __name__ == "__main__":
    asyncio.run(main())

Basically, a set of deployments, different parameters, but same image and work_pool, which results in one task_definition revision created per deployment, and we get the ClientException.

I ran into this very same issue yesterday while trying out ECS worker pool deployments.  This is not a problem we see today with our infra block agent deployments.


Basic recommender system

Hi, I haven't done this before. I updated the same branch with the changes on my forked repo. Is the PR updated now?
Thanks!


add new version kafka and apiversions support

One final thing: can you rebase your branch and get squash the last 4 commits into one?

i have do the rebase and squash

@eapache final :eyes: before merging this?


Make project Android agnostic

The plan is to make this library usable outside of Android so that other extensions can be added without having to manage another project.
Since the support annotations are already accessed via reflection there are no downsides. As part of making this a better Java library, the IntRange, FloatRange and Size annotations should be bundled within the library and operate the same way.
Considering this a rebrand of the library (with a new artifact name) the version number will be reset to 1.0.0 and the old library will no longer be supported.

This has been implemented


testing: Add kuttl test suite to operator (PROJQUAY-2622)

Add kuttl testing framework to Github Actions
Update vendor directory

@jonathankingfc this one looks awesome. Would you mind looking into my comments asap ? I would like to add some more e2e tests for https://github.com/quay/quay-operator/pull/635 but I need this in first :-)


Fix: Finalize Fuse Installation and Testing

CHANGELOG

Properly handles fuse status/state to make it easier to client to determine what action to perform. States are either UNSUPPORTED if on an operating system without fuse support, NOT_INSTALLED when fuse is not detected, UNMOUNTED when fuse is installed but the Space drive is not mounted and MOUNTED for when the drive is mounted.
Fixes some bugs with handling opened files in the drive

Hi guys, I'll want to merge this soon. So the updated API can be used for integrations.


Do not crash without YAML-Header

With a YAML lacking the YAML-Header (tree Dashes) yaml-sort just crashes with Traceback, instead of giving an Error-Message, or just being error-tolerant.

I can't reproduce this with my example files, can you please provide symptomatic test cases so that I can use them as a starting point?
The START_OF_DOCUMENT / END_OF_DOCUMENT sucks and would benefit from some re-thinking:
https://github.com/smortex/yaml-sort/blob/c60d1aab94d04291244824620415f964d432e796/lib/yaml/sort/parser.ra#L10-L13

$ cat tmp/a.yaml
a: AAA

$ yaml-sort tmp/a.yaml
---
a: AAA

$ cat tmp/b.yaml
b:
- B
- BB

$ yaml-sort tmp/b.yaml
Traceback (most recent call last):
        11: from /home/cocker/.rvm/gems/ruby-2.7.2/bin/yaml-sort:23:in `<main>'
        10: from /home/cocker/.rvm/gems/ruby-2.7.2/bin/yaml-sort:23:in `load'
         9: from /home/cocker/.rvm/gems/ruby-2.7.2/gems/yaml-sort-1.0.0/exe/yaml-sort:7:in `<top (required)>'
         8: from /home/cocker/.rvm/gems/ruby-2.7.2/gems/yaml-sort-1.0.0/lib/yaml/sort/cli.rb:45:in `execute'
         7: from /home/cocker/.rvm/gems/ruby-2.7.2/gems/yaml-sort-1.0.0/lib/yaml/sort/cli.rb:45:in `each'
         6: from /home/cocker/.rvm/gems/ruby-2.7.2/gems/yaml-sort-1.0.0/lib/yaml/sort/cli.rb:46:in `block in execute'
         5: from /home/cocker/.rvm/gems/ruby-2.7.2/gems/yaml-sort-1.0.0/lib/yaml/sort/cli.rb:55:in `process_document'
         4: from /home/cocker/.rvm/gems/ruby-2.7.2/gems/yaml-sort-1.0.0/lib/yaml/sort/cli.rb:68:in `sort_yaml'
         3: from parser.ra:176:in `parse'
         2: from (eval):3:in `do_parse'
         1: from (eval):3:in `_racc_do_parse_c'
parser.ra:180:in `on_error': undefined method `[]' for nil:NilClass (NoMethodError)

Thanks!
I just released 1.0.1 which should fix this.


Change semantics of replicate to iRODS to copy

Please change Replicate to Copy at locations indicated below.

Yes, I'll make this change.

Should the change also be made to this message?

File larger than 1GB cannot be downloaded directly via HTTP. Please create an iRODS account in your iRODS user zone from your profile page if you have not done so already, and replicate the resource...

OK


How can I change tab by clicking button?

Hi guys!
I'm using this fantastic approach to material, but I'm not sure how I can change active tab by clicking a button inside a tab...
Is this possible?
Thank you

I'm supernoob... sorry for this question...
as easy as "active-tab="activeTab""; activeTab is a variable controlled in my controller xD
Thank you and sorry


tutor portal routes, html, css, js

bleh

Did you want to close and delete this branch in favor of the other one you opened?


Update google-cloud-pubsub to 1.124.2

About this PR
📦 Updates com.google.cloud:google-cloud-pubsub from 1.107.0 to 1.124.2
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
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!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.cloud", artifactId = "google-cloud-pubsub" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.google.cloud", artifactId = "google-cloud-pubsub" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #362.


How to set stroke with on mat-icon.

What are you trying to do?
I'm trying to change the stroke width to 300. I am using the official @angular/material package. I cannot find any documentation on how to change the stroke width as on https://fonts.google.com/icons.
What troubleshooting steps have you tried?
I've tried to change the  contents of the <link>'-tag which imports the css file.
Reproduction
Using angular and material.
Environment
Angular CLI: 14.0.4
Node: 16.14.0
Package Manager: npm 8.3.1
OS: win32 x64

On that fonts.google.com/icons page, they have a tool to give you the corresponding css. On the left hand side you can customize the icons to your specifications, and then if you click on any icon and a panel pops out on the right with the styles.


Build tool support code gen for C targets

Description
I've been working on tools to generate Swift bindings for WinRT.  I consistently get feedback that the right way to do this would be a SwiftPM build tool, so I've been trying to make that work.  I've logged issues for a few Windows-specific bugs, and I assume that kind of thing will get sorted out.  But then I hit a bigger problem.
AFAICT:

SwiftPM build tools cannot generate a C header file to go into a C target
Swift itself does not allow a C function pointer involving a pointer to a struct unless it came from C import

These two things appear to be conspiring to prevent SwiftPM build tools from being used for one of its intended purposes.  I can't generate the C portion of the bindings, because a build tool can't do that.  So I thought I would just get rid of the C side and generate all the vtables in Swift, but the language doesn't allow that.
Note that even if (1) were addressed, there would be potential for another problem:  Generating bindings for WinRT (and similar) would involve two separate parts, one in Swift and one in C.  If the binding generator wanted to scan the existing Swift code to decide what bindings were needed, then the plugin for the C target would need to be able to scan the code in a Swift target, which seems like a violation of how build tool plugins are designed.
I'm not sure what would be the best way to address this problem, but logging this issue seemed like the right step.
Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
Swift Package Manager version/commit hash
No response
Swift & OS version (output of swift --version && uname -a)
No response

cc @compnerd

Noting that the windows tag has been applied to this issue, I would just clarify that even though it arose in my work with WinRT, the issue described here is not Windows-specific.


Ignore .meta files in logging DLL project directory

Ignore .meta files in the logging DLL project director.
This directory doesn't get imported by Unity so it shouldn't have any .meta files.
What is the current behaviour?
.meta files may be accidentally added to the .CSProject logging directory.
What is the new behaviour?
.meta files are ignored in .CSPRoject all all sub-directories.
What issues does this resolve?
None

What PRs does this depend on?

None

Does this introduce a breaking change?

[ ] Yes
[x] No

While you're at it, I noticed anvil-csharp-core ignores anvil-csharp-logging.deps.json, which now exists for the Unity logging DLL too - the internet strongly recommended keeping that file, but I'm not sure it's necessary for Anvil, should it be removed and ignored here as well, or should the anvil-csharp-logging.deps.json be un-ignored?

While you're at it, I noticed anvil-csharp-core ignores anvil-csharp-logging.deps.json, which now exists for the Unity logging DLL too - the internet strongly recommended keeping that file, but I'm not sure it's necessary for Anvil, should it be removed and ignored here as well, or should the anvil-csharp-logging.deps.json be un-ignored?

Done: https://github.com/decline-cookies/anvil-csharp-core/pull/121


Polymorphic deserialization requires type discriminator to be at beginning of the object

Source/destination types
abstract class A
{
    public int Num { get; set; }
}
class B : A
{
}

Source/destination JSON
{
    Num: 1,
    $type: 'B, JsonTest',
}

Expected behavior
Deserializing a polymorphic object should consider the type discriminator where ever it appears in the object.
In the given example, an object of type B should be constructed successfully.
Actual behavior
With the given example, the following exception is thrown:
Newtonsoft.Json.JsonSerializationException: 'Could not create an instance of type A. Type is an interface or abstract class and cannot be instantiated
Steps to reproduce
var settings = new JsonSerializerSettings
{
    TypeNameHandling = TypeNameHandling.Objects
};

var obj = JsonConvert.DeserializeObject<A>(jsonString, settings);

Note:
If this is expected behavior, then it should be documented. I did not find any mention to this limitation in the docs.

https://www.newtonsoft.com/json/help/html/SerializationSettings.htm


Add context flag for subctl deploy-broker

What would you like to be added:
Add context flag for subctl deploy-broker, such as:
subctl deploy-broker --kubeconfig /root/.kube/xxx.config --context yyy
Why is this needed:
There maybe more than one context in kubeconfig file, I want to change to use another context, as follows:
...
contexts:
- context:
    cluster: a
    user: a
  name: a
- context:
    cluster: b
    user: b
  name: b
current-context: a
kind: Config
...

I want to use context b insted of a.

@skitt Thank you very much for your prompt response.

@skitt Thank you very much for your prompt response.

You’re very welcome, it was on my to-do list and your issue prompted me to get it done! (It was a very simple fix.)


complete arg list for MultiPolyMesherIo

We should have all options available in the argument list for the constructor for this object

Should we return the points and cells ?


replace FAILED deployments with helm upgrade --install --force

When using helm upgrade --install, if the first release fails, Helm will respond with an error saying that it cannot upgrade from an unknown state.
With this feature, helm upgrade --install --force automates the same process as helm delete && helm install --replace. It will mark the previous release as DELETED, delete any existing resources inside Kubernetes, then replace it as if it was a fresh install. It will then mark the FAILED release as SUPERSEDED. I did not want to make this the default behaviour of helm upgrade --install because this is a destructive operation that deletes resources in Kubernetes, and the operator should opt into and accept this behaviour.
closes #3353
refs discussion in #3437

Forward note: I'm a little iffy on marking the previous release as SUPERSEDED.

Can this be the default behaviour if there is only 1 release prior and it failed? Seems to be the most common case so far.
Beyond that, I agree with it not being the default behaviour.

Can this be the default behaviour if there is only 1 release prior and it failed? Seems to be the most common case so far.

That is good feedback, thanks @helgi. I'd be a little concerned about the behaviour being inconsistent for users though. In this case, a user can expect helm upgrade --install to "fix" the first failed release, but it will continue to fail on subsequent releases with no feedback on how to fix that. I'd kinda prefer to make it explicitly opt-in as a feature flag, but I'd love to hear any feedback on whether that's important!

Perhaps we can decide at a later date if we should do that based on others' feedback in 2.8.2. How does that sound?

Yeah, I considered the inconsistency and cringed as I wrote that message. The scenario I run into a little too often (for comfort) is engineers throwing together a new helm chart and not running it in minikube but rather putting it directly into the dev CI system (copy pasta basically), which leads to failed first deployment a lot of the time.
The user generally has no idea why it failed and why their future pushes do not fix the issue, and even when they have done the fix before (helm delete --purge) it is forgotten a lot of the time. Basically, first time deploy clumsiness UX issues.
I'm happy with deferring the decision but I did want to bring up the use case

k, addressed all comments. New stuff since the last round of reviews:

the old release finishes in state DELETED instead of state SUPERSEDED, modelling what helm install --replace would do
due to the wonky semantics of this feature flag, pre/post delete and install hooks are run, not pre/post upgrade hooks
m0ar Star Wars references in the tests for @thomastaylor312's enjoyment

Should be good for another round of reviews

Am I write in reading this as --force will only ever cause a delete and redeploy when the first deploy has failed?
so if i have a chart deployed, break it, and then upgrade it, it will be fixed, not recreated?

@bacongobbler I'm also confused regarding this change.
helm upgrade --install

if release v1 failed, release v2 will fail because the operation is considered unsafe
if release v4 succeeded and release v5 failed, release v6 will succeed based off of release v4  ?

helm upgrade --install --force

if release v1 failed, release v2 will succeed because release v1 is deleted first
if release v4 succeeded and release v5 failed, release v6 will succeed based off of release ...  ?
does it delete the pre-existing release?
does it cause downtime?

Is the --force flag safe to use all the time, expecting that it only destroys kubernetes resources when the very first release fails?

helm update --install with the --force flag automates what one would do to "fix" a failed upgrade. --force is just a helm delete && helm install --replace, and it only kicks in when the release failed to deploy. It only causes downtime if your application would go into a failed state. --force just attempts to fix it. If your application would normally upgrade gracefully, there's no downtime.

and no, it kicks in any time a release fails.

is case 2 accurate?
I'm already lost as to whether helm rolls back release versions on failure

We're still on Helm v2.7.0 because the current upgrade-over-failure behavior appears to be safer for our use case than deleting a deployment.
Our releases usually fail due to hooks, but our hooks are idempotent Jobs, so it's usually pretty safe to upgrade right over them.
If I'm understanding the new behavior correctly, I believe it would be possible for a Deployment to be deleted and for no Pods to be available to serve traffic mid-deployment if a hook failed on the previous deployment.

To answer case 2, helm upgrade --install --force will upgrade as normal, so it'll use v4 to upgrade. However, should v6 fail, that's when the --force flag kicks in and I'm not 100% sure I can recall exactly what happens. It's been a little while so I'll have to look through the code again to answer your question. Feel like looking at it together at KubeCon? :)

:+1: yep, I'm curious
looking forward to it

If I'm understanding the new behavior correctly, I believe it would be possible for a Deployment to be deleted and for no Pods to be available to serve traffic mid-release if a hook failed on the previous release.

It seems from https://github.com/kubernetes/helm/issues/3208#issuecomment-390340881 that this might be the case when using upgrade install --force.
This flag is pretty dangerous.


[News] The reply text field hasn't highlighted in red color for starting from character 8001

Environment:
macOS  Version 13.4.1
Google Chrome
Version 117.0.5938.88 (Official Build) (arm64).
Reproducible: always.
Build found:
24/09/23
Preconditions
At least a News is added;
a News includes a User's comment;
The User's comment isn't empty.
Steps to reproduce

Open the site https://www.greencity.social/#/greenCity;
Logged-in as User;
Click on the 'Eco news' tab;
Click on the News that includes a comment;
Click on 'Reply' icon under User's comment;
a) Paste more then 8000 characters;
b) Type more then 8000 characters;

Actual result
a) the reply text field is highlighted in blue color!!
b) the error message “This reply text field shouldn't be more than 8000 characters” under the reply text field is absent!!

Expected result

the system doesn't allow to enter more than 8000 characters in the reply text field;
the reply text field is highlighted in red color starting from character 8001, 'Reply' button is disabled;
the system displays the error message “This reply text field shouldn't be more than 8000 characters” under the reply text field.

Postconditions
User story and test case links
E.g.: "User story #6411
Test case"
Labels to be added
"Bug", Priority ("medium"), Severity ("trivial"), Type ("Functional"), "API" (for back-end bugs).

the system allows to enter more than 8001 characters in the reply text field;

Agree by Viktoriya - the system allows to enter more than 8001 characters in the reply text field


Finishing up Embeddable into R/R^n

I think it is pretty large and can be discussed later.
For example imo "Finite dimensional" can be added, in order to further deduce P184 (Embeddable into Euclidean space).
However, for general spaces, finiteness may(?) be not equal for Lebesgue, inductive and INDUCTIVE.

@yhx-12243 Dimension theory is a vast subject.  Various whole books have been written about it.  It does not seem appropriate to use advanced notions of dimension theory in pi-base, when pi-base does not even have the more basic notions of that subject.
If you want to gradually introduce more dimension theory notions in pi-base, I suggest you first present this in an issue, where this can be discussed and a plan can be developed before doing anything else.  Does that sound reasonable?
It does not matter if we can't assert at the moment all the cases where a space is or is not embeddable into Euclidean space.
So if you don't mind, I will put this PR on hold in Draft mode for now.

I did a separate PR #1099 for S30, S32, which hopefully you can review.
Can you do a separate PR for S196 (long circle)?  If it does not become too large a task, feel free to do more extensive changes to S196, so we can reduce the number of unknown traits for this space.  Up to you.

For S129 (wheel without its hub), you claim it is embeddable into some Euclidean space.  So what would be a specific $\mathbb R^n$ and a specific embedding for that?

In fact there only remains {S75|P184} and {S129|P184} which needs dimension theory.
For these two, we used the characterization in the description: "Second Countable + Metrizable + finite-dimensional", without a explicit embedding.

For S196, I think it may belong to a project that cleaning up the traits of different long rays. Because currently there are still many traits of long ray unresolved.

For S196, I think it may belong to a project that cleaning up the traits of different long rays. Because currently there are still many traits of long ray unresolved.

You are right.  I did not realize there was already #1069.  So let's leave that one alone.

In fact there only remains {S75|P184} and {S129|P184} which needs dimension theory.
For these two, we used the characterization in the description: "Second Countable + Metrizable + finite-dimensional", without a explicit embedding.

I know that's what you did.  But I want to know, if your claim is true, it should not be too hard to exhibit an embedding.  So what would such an embedding be?

@yhx-12243 Also I am curious.  You keep saying "we used ..."  Are you talking about just yourself, or a group of people working on this?

@yhx-12243 Also I am curious. You keep saying "we used ..." Are you talking about just yourself, or a group of people working on this?

Sorry may be my pet phrase (because I usually write this in report and papers maybe)

Please don't do that.  It may be ok in papers, to include the reader.  But it looks pretty bad in conversation.

For S196, I think it may belong to a project that cleaning up the traits of different long rays. Because currently there are still many traits of long ray unresolved.

You are right. I did not realize there was already #1069. So let's leave that one alone.

Sorry that's still open. Will finish it tomorrow.

@yhx-12243 Expanding my earlier comment about S129 (wheel without its hub).
I think this would be a very interesting mathse post.  You could explain why it is embeddable in some Euclidean space $\mathbb R^n$ using dimension theory, and then ask what a particular embedding would be.  I would be very curious to see such embedding, as I cannot easily picture one.
Do you think you can do such a post?

@yhx-12243 You are still planning to do this mathse post as discussed above?


WebGL error: Too many uniforms

Here's an example of a skinned model that works in three.js but not in pixi3D (on iOS < 14):
https://threejs.org/examples/#webgl_animation_skinning_blending
Shaders couldn't compile, reporting too many uniforms...
Looks like three.js automatically reduces number of skinning weights:
https://discourse.threejs.org/t/is-the-limit-of-4-skinning-weights-per-vertex-a-hard-limit-of-webgl
Here's an issue reported on three.js: https://github.com/mrdoob/three.js/issues/7807

Thanks! I'm currently looking into this actually.

First, thanks for reporting these problems :-)
I might have a fix for the issue you are experiencing, please pull latest from develop branch and build it using "npm run build", pixi3d.js will be created in "dist" folder. Please let me know if this fixes the problem.

Tested on a few iOS devices, works well on all of them. Thank you!


fix concurrent piece map panic

Signed-off-by: sunwp<EMAIL_ADDRESS>
Description

Related Issue
fix #1066

Motivation and Context

Screenshots (if appropriate)
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation Update (if none of the other choices apply)

Checklist

[ ] Code compiles correctly.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Codecov Report

Merging #1121 (3dbb48b) into main (d1b8ee6) will decrease coverage by 0.16%.
The diff coverage is 52.94%.

@@            Coverage Diff             @@
##             main    #1121      +/-   ##
==========================================
- Coverage   45.98%   45.81%   -0.17%
==========================================
  Files         130      130
  Lines       10000    10020      +20
==========================================
- Hits         4598     4591       -7
- Misses       4882     4908      +26
- Partials      520      521       +1

Flag
Coverage Δ

unittests
45.81% <52.94%> (-0.17%)
:arrow_down:

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

Impacted Files
Coverage Δ

cdn/supervisor/task/manager.go
25.23% <0.00%> (-1.24%)
:arrow_down:

cdn/supervisor/task/task.go
42.55% <0.00%> (-3.10%)
:arrow_down:

cdn/rpcserver/rpcserver.go
61.58% <50.00%> (+0.37%)
:arrow_up:

cdn/supervisor/progress/manager.go
85.00% <75.00%> (-3.14%)
:arrow_down:

cdn/supervisor/progress/progress.go
90.62% <100.00%> (-0.42%)
:arrow_down:

client/daemon/peer/peertask_conductor.go
57.31% <0.00%> (-0.36%)
:arrow_down:

client/daemon/daemon.go
5.13% <0.00%> (-0.28%)
:arrow_down:

client/config/peerhost.go
35.29% <0.00%> (ø)

client/daemon/peer/piece_broker.go
85.18% <0.00%> (+3.70%)
:arrow_up:


Add FERC1 output table that combines key FERC1 subtables

This PR contains the code needed to create a composite FERC1 output table containing the information from the FERC1 steam, small_gens, hydro, and pumped_storage tables--collectively representing all of the plants reporting to FERC.
This table may have multiple uses, but the main impetus was for mapping FERC records to EIA records via the Master Unit List and FERC-EIA mapping established in the RMI repo.
Besides combining the subtables, this PR also adds new columns (like capacity_factor and in one case opex_fuel_per_mwh) to the subtables where possible so that they may be more accurately matched to EIA records. These columns are only added to subtables when they can be calculated from existing columns.
My main question -- and why this is a draft PR vs a real PR -- is whether this information belongs in the output module or the analysis module. While I originally thought it fit best among the outputs, I recognize that I have added some calculated fields more akin to the analysis. I would love to know what you think is most appropriate!

ADD THIS OUTPUT TO CI TEST


Removed unused ssl_dane struct declaration.

The actually used structure is named ssl_dane_st.
CLA: trivial

Merged to master in 96fc458a9cbeb8e7b30d789ea5919c5dcb9b980e, thank you!


Set packageManager field instead of engines.pnpm

The packageManager field enables using corepack, a feature native to
Node.js since v18.
That way, it's possible to pnpm install the package with engine-strict
and a different version of pnpm.
Closes #307

@otahontas can you review please?
Also, do you want me to add a changeset? The bot complains I didn't add one, but I see all changesets were deleted.

@ianldgs Hey and sorry for not replying, have been off from work for the past month.
Changeset labeled with minor change would be good. It should be quite straightforward to add one with pnpm changeset command.

It seems like maintainers aren't allowed to make changes to this PR, but maybe you can cherry-pick commits https://github.com/otahontas/trpc-rtk-query/commit/f8e6af7fb9621f4d0e7ff389292e1aab70c79633 and https://github.com/otahontas/trpc-rtk-query/commit/65f13a1796cba9ad895b88ea914c81a1e897c439 from the following branch: https://github.com/otahontas/trpc-rtk-query/commits/fix-engines/ ?

Hey @otahontas! Thanks for generating the changeset and fixing the CI. Cherry-picked the commits.

Hey @otahontas! Thanks for generating the changeset and fixing the CI. Cherry-picked the commits.

No problem! Seems that CI is working, so merging this and will make a release soon. Thanks for the fix 💯


Spectator Camera: snap audio using wrong volume setting

The audio volume of the snap sound is influenced by the "environment volume" instead of "UI FX volume"

This seems to be intentional. All audio played using Audio.playSound is  treated as a environment sound.


GCP Instance Implementation

Implements Issue #22

All the resources that have the field fingerprint, I feel none of them are used and as such we might get rid of them, thoughts ?

The doUpdate in InstanceResource uses one. They are/will be needed for doing any updates.


10/24/2018 05:29 : Create Pull Request for branch master -> prTesting1_2018102405

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Contributing and pep8 fixes

@goto40 This PR fixes numerous PEP-8 violations in the tests and brings a new contribution guide in the docs. This should help new contributors get started easier. Please review when you find time.
I'm planing to make flake8 adherence mandatory trough Travis CI.

Very good! I will take my time to read and test your proposal.
At first sight: Do we also need to include the flake command in the .travis.yml file?

At first sight: Do we also need to include the flake command in the .travis.yml file?

Yes, you are right, that is something I was up to do next. I'll need to investigate what is the best way to do it.

I tested the contribution manual, and no errors occurred.

Maybe we could also start to collect architectural entry points... Such as

structure: overall file/module structure (with rough overview about responsibilities)
activity: parsing and model building / scope resolution
...

Do you think something like doxygen could help to link architectural snippets to the code?
You remember the explanation you gave me concerning 'containment' and 'reference' in PR #79. This could be valuable to other contributors.

Thanks for testing. Merging.
Regarding the dev docs, I agree. The overall architecture/processes description and main internal APIs would be helpful, not only for new contributors but for ourself as well as our brains are not the best places to keep all those stuff :)  Although, I wouldn't go into too much of  details (just the high-level overview) as the docs (especially dev docs) tend to become out-of-sync very fast.
OTOH, I'm not that eager to introduce new documenting tools. The project is using mkdocs which is working really good and is very simple to use so IMHO we should use it for all docs parts.


Proper ES6 module support

Is your request related to a specific problem you're having?
I am having problem importing ES6 modules from highlight.js. Although the README mentions about ES6 Modules / import, it does not work in Browser.
I have installed highlight.js using npm install highlight.js. The following are the contents of files in project:
package.json:
{
  "dependencies": {
    "highlight.js": "^11.10.0"
  },
  "type": "module"
}

index.html:
<!DOCTYPE html>

<link rel="stylesheet" href="./node_modules/highlight.js/styles/default.min.css">

<span>Hello World!</span>

script.js:
import hljs from "./node_modules/highlight.js/lib/core.js";
import xml from './node_modules/highlight.js/lib/languages/xml.js';

hljs.registerLanguage('xml', xml);

const highlightedCode = hljs.highlight(
	'Hello World!',
	{ language: 'xml' }
).value;

console.log(highlightedCode);

if (typeof window === 'object') { // check if currently running in browser
	hljs.highlightAll();
}

All the above three files are located inside same directory.
When opening the index.html in Firefox, there is error with following message in console:
Uncaught SyntaxError: The requested module 'http://localhost/node_modules/highlight.js/lib/core.js' doesn't provide an export named: 'default'

However, running node script.js works fine with following output:
<span>Hello World!</span>

It seems both the core.js and xml.js are not ES6 modules at all despite what the documentation says. They are just CommonJS modules. They seem to work in NodeJS despite being imported from ES6 modules.
I tried CDN links and they worked. But I needed local copy of those files. I downloaded those files from CDN and used that. But later, after going through the documentation thoroughly, I found that there is another package @highlightjs/cdn-assets that provide those files. After installing @highlightjs/cdn-assets, I replaced import in script.js with the following code and everything works now:
script.js:
import hljs from<EMAIL_ADDRESS>import xml from<EMAIL_ADDRESS>
hljs.registerLanguage('xml', xml);

const highlightedCode = hljs.highlight(
	'Hello World!',
	{ language: 'xml' }
).value;

console.log(highlightedCode);

hljs.highlightAll();

Although this works, the problem is that @highlightjs/cdn-assets contains generated code, not the original source code. For example, all the language files inside ./node_modules/@highlightjs/cdn-assets/es/languages/ are minified files.
The solution you'd prefer / feature you'd like to see added...

I would like to be able to import ES6 modules directly from hightlight.js package instead of @highlightjs/cdn-assets. Following code should work:import hljs from "./node_modules/highlight.js/lib/core.js";
import xml from './node_modules/highlight.js/lib/languages/xml.js';

The imported file should be original source code, not generated code.

I think any JS library meant for browser should be developed using ES6 modules. It is better to drop support for CommonJS as ES6 module is already supported in Node.
Additional context...
highlight.js version: 11.10.0

It is better to drop support for CommonJS

Version 12 plans to do this, but it's a big change (along with other changes) and I don't have much free time these days.

minified files.

Curious, what's the issue with minified files? We could consider shipping both, we've done it already for things like CSS assets, etc.

contains generated code, not the original source code.

If you want the "raw" ES6 code you can use this repository (and a custom build process)... future versions might ship non-minified but we always plan to ship "cooked" releases because we want to manage some of dependencies and inter-dependencies ourselves, not leave that up to the end user.

Version 12 plans to do this, but it's a big change (along with other changes) and I don't have much free time these days.

I can see that you have started working on version 12 but it has been more than a year since last commit. If you can provide roadmap for version 12, I can help you with the new version.

Curious, what's the issue with minified files? We could consider shipping both, we've done it already for things like CSS assets, etc.

Minified files are not readable. This is a problem when debugging them interactively in the browser.

If you want the "raw" ES6 code you can use this repository (and a custom build process)...

IMO, we should be able to use ES6 source code without having to use build process. Since highlight.js has no dependencies (only devDependencies), this should not be a big deal.

we always plan to ship "cooked" releases

I have no problem with this. We should be able to use hightlight.js in other ways beside ES6 import.


Specify routing for policy version counter document

Closes #99

Codecov Report

Merging #99 (fc61f7b) into main (4c4d641) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #99      +/-   ##
==========================================
+ Coverage   93.55%   93.56%   +0.01%
==========================================
  Files           9        9
  Lines        1071     1073       +2
==========================================
+ Hits         1002     1004       +2
  Misses         55       55
  Partials       14       14

Impacted Files
Coverage Δ

pkg/policy/manager.go
99.53% <100.00%> (+<0.01%)
: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 4c4d641...fc61f7b. Read the comment docs.


help for the program deployment

hi
thanks for this Instructions, it is very very useful for the new mod maker.
i followed the instructions, step by step , everything is ok until Test Mod (page8)
when the game init, i can see the mod initialized. however there is no any setting ui in "Options" screen.
then i move these mod files to "C:\Users\Administrator\AppData\LocalLow\Colossal Order\Cities Skylines II.cache\Mods\mods_subscribed"
and pretend it to be downloaded from Paradox Mods. it works. i can see the name of mod. see the setting ui ,after i quit the game,
i can see the modname.coc.
anyway, i can code and debug my mod now, thanks.

Glad you got it working somehow.  For a new modder, see my Modding Instructions at:
https://github.com/rcav8tr/CS2-Modding-Instructions


[Request] [Question] App Translate

Hello,
Is there any way that you can support translations of the app in other languages?
Thanks

@VeZReVouLiS
Translations are not at ready for now, may or may not in future.
it's not necessary, Please raise a issue if you have anything with latest unc0ver.ipa
else
Please add [Request] [Question] [Help] tags on Title.

@ios11iphone6s this isn't reddit...

@VeZReVouLiS It might happen but it isn't the focus right now.


Settings export / backup doesn't include saved queries  :sob:

Describe the bug
When you export your configuration you'd expect saved queries, notes, shortcuts,etc.. to be included, but you find out they are not when you restore the configuration.
To Reproduce
Steps to reproduce the behavior:

Go to export the app settings
Click on export button and leave all default options

Expected behavior
Saved queries and query history is included in the backup / export.
Application (please complete the following information):

App client [e.g. MySQL]
Installation source: [ Linux Store]

Environment (please complete the following information):

OS name: [Ubuntu]
OS version [22]
DB name  [e.g. MariaDB]

Additional context
Maybe also make encrypting  the backup optional... I don't see the added value of forgetting the password you used and loosing all your hard work of configuring the app.

Additional context Maybe also make encrypting the backup optional... I don't see the added value of forgetting the password you used and loosing all your hard work of configuring the app.

The encryption is needed to secure sensitive data such as hostname, user and password, because otherwise it would be sufficient to open the file with a text editor to obtain its contents.

So?
If the user wants that data protected he can leave a pre-enabled radio button turned on to use the encryption, however if he doesn't need it and the risk of forgetting the password is bigger than the value of the data the encryption is supposed to protect, he can uncheck the button and not use encryption.
I had this exact case, configuring ssh (lets say for homestead) setting settings, adding DBs, seeding test data, etc...
All this took lots of time, but the value of the data is 0, so when I borked the dev setup I had to start over and was thinking of just importing the backup I made and discovered the password was not 123123123 (as I remember using). So I lost several hours of setup configs and lots of test data because I lost the password and had to start doing it by hand all over again.

I think a good compromise would be the ability to uncheck the encryption, and an alert modal about the risks.


Autoscrolling while dragging in SortableContext does not stop scrolling when the container reaches final scroll position

Short (45sec explanation with codesandbox demo)
https://www.loom.com/share/43c9f0e0d77744388b5cb86f06427ec9
Code sandbox with example: https://codesandbox.io/s/dnd-kit-drag-to-sort-exploration-lftzvt?file=/src/App.tsx:752-1120

Yeah I have the same issue

You can reach that by using DragOverlay. I forked and modified your sandbox here: https://codesandbox.io/s/dnd-kit-drag-to-sort-exploration-forked-n33v7p?file=/src/App.tsx

You can reach that by using DragOverlay. I forked and modified your sandbox here: https://codesandbox.io/s/dnd-kit-drag-to-sort-exploration-forked-n33v7p?file=/src/App.tsx

Thank you so much; this was precisely what we were looking for!
Should we close the issue now? Would it help to add a doc comment maybe about this?
I imagine others might encounter the same issue, which might hurt adoption when exploring this library if we don't mention this aspect anywhere.

This works great. I just have one problem with it. My sortableItem runs a web3 method on mount. you can think of it as an API call. therefore, whenever I drag the sortableItem, the drag overlay version of it runs the method again. is there any way to prevent it.
here is a short video demo https://www.loom.com/share/a9a3d9fb99ff402299696aae56888eed

You can create a placeholder, which runs different logic and presents a different UI than the normal one
https://www.loom.com/share/923c7b137a8a468a808852ac822caa64
https://codesandbox.io/s/dnd-kit-drag-to-sort-exploration-forked-hroxjm?file=/src/SortableItem.tsx

You can use modifier to get this job done.

import the following

import {restrictToFirstScrollableAncestor,restrictToVerticalAxis,
//  restrictToParentElement
} from "@dnd-kit/modifiers"

use it on the line <DndContext like this

<DndContext
modifiers={[restrictToVerticalAxis,restrictToFirstScrollableAncestor,
  ]}
***********

The following is your full code in your sandbox.  I modified your code to allow items moving vertically using modifier too but I don't konw how to use sandbox.
Sorry, English is my second language if you don't understand all above.
import { useState } from "react";
import {
DndContext,
closestCenter,
KeyboardSensor,
PointerSensor,
useSensor,
useSensors
} from "@dnd-kit/core";
import {
arrayMove,
SortableContext,
sortableKeyboardCoordinates,
//verticalListSortingStrategy
} from "@dnd-kit/sortable";
import { SortableItem } from "./SortableItem";
// See here!
import {restrictToFirstScrollableAncestor,restrictToVerticalAxis,
} from "@dnd-kit/modifiers"
//
const values = Array.from(new Array(20)).map((i, idx) => idx + 1);
export default function App() {
console.log(values);
const [items, setItems] = useState(values);
const sensors = useSensors(
useSensor(PointerSensor),
useSensor(KeyboardSensor, {
coordinateGetter: sortableKeyboardCoordinates
})
);
return (

<DndContext
// See here!
modifiers={[restrictToVerticalAxis,restrictToFirstScrollableAncestor,
]}
//
sensors={sensors}
collisionDetection={closestCenter}
onDragEnd={(event) => {
const { active, over } = event;
      if (over && active?.id !== over?.id) {
        setItems((items) => {
          const oldIndex = items.indexOf(active.id as number);
          const newIndex = items.indexOf(over.id as number);

          return arrayMove(items, oldIndex, newIndex);
        });
      }
    }}
  >
    <SortableContext items={items} >
      {items.map((id) => (
        <SortableItem key={id} id={id}>

Inner content {id}

        </SortableItem>
      ))}
    </SortableContext>
  </DndContext>

);
}

Thanks @piyapanw
The restrictToParentElement modifier did it for me.


[Feature Request]: Pause/slow down up next display speed

Choose the extension for feature request.
Full Screen Mode
📝 Provide a description of the new feature
Hello, thanks for creating and maintaining this extension!
I have a small suggestion for the up next display on the full screen.
The up next display scroll speed is quite fast and does not have a pause upon reaching the end. This is very apparent on medium length titles, as shown in the video.
My proposal is to add a small pause upon reaching the end of the scroll, and then start to scroll back, similar to the way Spotify does it.
➕ Additional Information
https://github.com/daksh2k/Spicetify-stuff/assets/135397968/4e1c8ba3-20c1-4d01-98ea-94e4c21a2c2e
Have a good day,
Gold

Hi, I wrote the animation logic to be consistent for both short and long titles, felt it had the right speed, and will fine-tune it sometime later if I get time, but I think mostly it's fine. If I increase the stoppage time, on long titles the scrolling speed will increase a lot.  It's just a balance really. So closing this issue currently.


Eslint v9 support

formatting rules will be deprecated in Eslint V9
references:
https://github.com/eslint/eslint/issues/17522
https://github.com/eslint-stylistic/eslint-stylistic

Any thoughts on this?

Discussion also happened in #1872 prior to ESLint announcing that it will be deprecated.
I'm in favor of removing the style rules, but there were some people that disagree, but now that it will be deprecated, we don't have a choice.


on_application_command_error throwing to console even when a handler exists

Summary
application errors will always show in console no matter if they are handled or not
Reproduction Steps

make an on_application_command_error cog listener
make a command raise
observe it in console (not same as ext.commands' on_command_error

Minimal Reproducible Code
from nextcord.ext.commands import Cog

class MyCog(Cog):
    def __init__(self, *_):
        ...

    @Cog.listener()
    async def on_application_command_error(*_):
        ...

def setup(bot):
    bot.add_cog(MyCog(bot))

Expected Results
The error not to be shown to console like ext.commands does.
Actual Results
Error thrown to console no matter what.
Intents
N/A
System Information
nextcord 2.0.0a10
rest is irrelevant
Checklist

[X] I have searched the open issues for duplicates.
[X] I have shown the entire traceback, if possible.
[X] I have removed my token from display, if visible.

Additional Context
No response

This is expected behavior, atleast based on how events vs listeners should work conceptually. This issue actually appears to show that ext.commands is bugged.
Registering an event with @bot.event overrides the event with a new handler, so the previous handler does not get called.
Registering a listener should not override the original handler, it simply adds another method to be called when the event runs. I.e. listen
This form of system allows for multiple listeners on single events, and a prevalent example would be adding an on_ready to every cog.


Stephenfeature

References issue #. Please review this @teammember1, @teammember2.
Types of changes

[ ]  Bugfix (change which fixes an issue)
[x]  New feature (change which adds functionality)
[x]  Refactor (change which changes the codebase without affecting its external behavior)
[ ]  Non-breaking change (fix or feature that would cause existing functionality to work as expected)
[ ]  Breaking change (fix or feature that would cause existing functionality to not work as expected)

Purpose

Allow users option to select all services
Make modal components more readable

Approach

Added button that selects all services on ServicesModal
Styled button so that it matches theme of ServicesModal
Deconstructed props from all modals components
Removed unnecessary console logs

Screenshot(s)

Thanks for adding the select all services functionality! Nice job Stephen


feat: add flake.nix and ipkg-parser.nix

followup of https://github.com/stefan-hoeck/idris2-pack/issues/311
I have added nix builer for all 3 packages

Thanks for doing this. Please note that I'm not a nix user and will not be able to maintain this. I'm therefore wondering if this truly needs to be part of the pack repo or if this would not be better off in its own repo with a link from pack's documentation.
If this is going to stay in the pack repo itself, it will need some documentation in the installation guide plus some CI tests to make sure it works correctly.

I'm not a nix user

yes, I know

link from pack's documentation

wow, thats generous, idris community is different, other people would just close)

it will need some documentation in the installation guide plus some CI tests

can do

In that case I'd suggest to keep this as part of the pack repo for the time being as long as we have proper CI tests and documentation. If the CI starts to fail and no one is around to maintain this, I'll be forced to remove it, but I'd like to have documented nix support for pack.