Javascript Based Loan Calculator

Describe the project you want to add with tech stack
A JavaScript-based loan calculator is a web application that calculates monthly loan payments based on user inputs for loan amount, interest rate, and loan term, providing quick financial estimates.
Expected behavior

Screenshots (optional)

Additional context (optional )

@MohitGupta121 @TusharKesarwani @pranjay-poddar


Install Microk8s on external ssd Windows 10

Heya,
I haven't run inspect because I don't think it applies in this situation.
I have a Windows 10 box I want to use for Microk8s however I'd like it to be installed on run on an external SSD(it's faster), I can't seem to find a way of making the installer use that, any ideas?
Thanks
Marc

@ktsakalozos Heya, thanks a lot for this, I'm sorry for the slow reply, yes I ended up installing VirtualBox to the external drive, then when creating the VM you have to be careful to install it on the right drive and also make sure the VM disk targets that as well since it defaults to C:\ .
I'll do a PR for docs on this at some point since I'm running a cluster for NVIDIA Jetson series bare metal nodes, windows 10 nodes, and even a MacOS node due to the diverse nature of the clients we have to deal with.


[For FAQ?] UDEV Magic

From Project Icestorm homepage:

Notes for Linux: Create a file /etc/udev/rules.d/53-lattice-ftdi.rules with the following line in it to allow uploading bit-streams to a Lattice iCEstick and/or a Lattice iCE40-HX8K Breakout Board as unprivileged user:
ACTION=="add", ATTR{idVendor}=="0403", ATTR{idProduct}=="6010", MODE:="666"

This did not work for me on Debian9. Other tries like setting the device node's ownership/permissions right for my account failed too.
After digging a while, I found Debian's fpga-icestorm_*.deb includes this UDEV rule:
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", MODE="0660", GROUP="plugdev", TAG+="uaccess"

This one worked here and now I can drop sudo for loading the FPGA.

The good Debian.
I can comment this: From the Security Implications of System Groups:
To manage removable drives without root privileges, you have to use the groups cdrom for optical drives. Optical drives can usually be mounted in according to the rules in /etc/fstab, but for other removable drives the group plugdev may be more practical.
And as in the both udev rules, the last one contains the group membership correctly, so for this reason you're able to use udev/pmount without root privileges.
Something you can check is what groups your user belongs to, and if you add yourself to plugdev (I'll probably will not do that if this is a multi user - critical server) you should be able to stick in the original udev rule.
Source:
https://wiki.debian.org/SystemGroups

I could not use the 1st mentioned UDEV rule desoite being in the right group.
TAG+="uaccess" seems to be what makes the difference...

Heh, azonenberg/openfpga had this same issue. According to @cyrozap,
`TAG+="uaccess"` is for systemd compatibility and `MODE="660", GROUP="plugdev"` is for non-systemd systems. This is the same pattern OpenOCD uses for its udev rules.
So the proposed change to the FAQ should be correct.

Ahhhh... systemd stuff... good to have an explanation!
Thanks!

Updated the website.

I feel kinda dumb after actually reading the line, as it clearly says GROUP="plugdev", but maybe it would be helpful to explicitly say next to it that you also need to be in the plugdev group for this to apply?


Update netlify's js-client and semver ranges

Update netlify's js-client and semver floors.

"@iarna/toml": "^2.2.3",
"netlify": "^2.4.0",
"@oclif/dev-cli": "^1.21.1",
"dependency-cruiser": "^4.13.2",

Coverage remained the same at 100.0% when pulling 9ac86ee00853b69fe7204f45b71daab0f3e3255f on deps into 5507344ce781f2eba398df52da1c37d9fbaaeaad on master.


DA v2: Fix Get Query on Chat/Feed Feature

Feature or Bugfix

Bugfix

Detail

If 1 of the dataset, dashboard, or datapipeline modules was disabled, the query to get Feed (i.e. the Chat Feature) would fail with an error similar to error:

[GraphQL error]: Message: Unknown type 'DataPipeline'. Did you mean 'DatasetLink'?, Location: [object Object], Path: undefined
This is due to the fixed inline fragments on the getFeed(...) query that do not exists such as ... on DatasetTable {...}

In this PR we remove the fragments as the label return value is not used in the FeedComments View

Relates

#723

Security
Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

Does this PR introduce or modify any input fields or queries - this includes
fetching data from storage outside the application (e.g. a database, an S3 bucket)?

Is the input sanitized?
What precautions are you taking before deserializing the data you consume?
Is injection prevented by parametrizing queries?
Have you ensured no eval or similar functions are used?

Does this PR introduce any functionality or component that requires authorization?

How have you ensured it respects the existing AuthN/AuthZ mechanisms?
Are you logging failed auth attempts?

Are you using or adding any cryptographic features?

Do you use a standard proven implementations?
Are the used keys controlled by the customer? Where are they stored?

Are you introducing any new policies/roles/users?

Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

With the above changes - the FeedRegistry class is no longer used ... I can clean up the code to remove any reference to this unused class but have left it in for now as it could be used in future enhancements.
What do you think @dlpzx ?


Translate tasks/job/automated-tasks-with-cron-jobs.md into Korean

This is a Feature Request

What would you like to be added

Translate tasks/job/automated-tasks-with-cron-jobs.md into Korean.
Why is this needed
There is no document of tasks/job/automated-tasks-with-cron-jobs.md which is translated into Korean.
Comments

Page to translate: https://kubernetes.io/docs/tasks/job/automated-tasks-with-cron-jobs/
/language ko

/assign


PHP Artisan migrate doesn't seem to handle package migrations

Laravel Version: 5.3.*
PHP Version: >5.6.4
Database Driver & Version: MySQL 5.7.16

Description:
Hey. I've been looking around the existing issue tickets, but I'm failing to find a solution to my problem. I'm probably doing something wrong, but here is my problem:
I just installed the venturecraft/revisionable package to my new Laravel installation, and I noticed that it comes with its own migration. To get it up and running, I ran the migration. Later, I thought to myself "Self, how will fresh installations of my project work if php artisan migrate doesn't run package migrations?" So now I ask this of you. I've thought about copying the migration to my main migrations folder, but this feels hacky and doesn't work for new migrations of new versions of my packages on composer update.
Also, if I ever run php artisan migrate:reset, it complains about the table from the package migration saying "Undefined index: 2013_04_09_062329_create_revisions_table".
Sorry if this has already been resolved. If it has, I haven't found it.
Steps To Reproduce:
composer require venturecraft/revisionable
php artisan migrate --path=vendor/venturecraft/revisionable/src/migrations
php artisan migrate:reset

Laravel already allows options for package developer to include custom migration path. https://laravel.com/docs/5.3/packages#migrations
If the package developer choose not to use this feature, there nothing we can do about it.

Contact the package maintainer and suggest having a Service Provider where he can register the path to the package migrations instead of having to run php artisan migrate --path=vendor/venturecraft/revisionable/src/migrations

Thanks for getting back with my so quickly! Sorry, I'm still pretty new to the framework. THank you for pointing this out, I'll definitely nudge them about it :)
Thank you again.

If you copy the revisions table migration into the folder with the other migrations you should be fine...


Add missing JvmSynthetic annotations to reified methods. Fixes #979

Fixes issue #979 by annotating all reified methods which have a corresponding non-reified signature with @JvmSynthetic
The functions are already supposed to be for Kotlin users only, so I do not think it will cause problems.
Two cases of reified functions remain.

JavalinConfig.getPlugin() in JavalinConfigExt.kt. This one is an extension function which will be available as JavalinConfigExtKt.getPlugin(JavalinConfig) which no one should be using. There is also no conflicting method here.
Context.bodyValidator() in Context.kt. We do not have another method with the same name and signature that should be available. So we do not need to hide this reified method.

Great, thank you @Playacem!


@19Nov DB Models

[x] Create DB-Models for all entities.

These issue completed late because of data scraping and cleaning.


Update: ModuleArt.QuickPictureViewer version 3.0.4

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

/azp run


RuntimeError: The size of tensor a (24) must match the size of tensor b (12) at non-singleton dimension 2

When we run by python inference.py --condition "depth" --video_length 24 --smoother_steps 19 20 --width 512 --height 512, we get the error
Traceback (most recent call last):   File "/root/paddlejob/workspace/lxz/ControlVideo/inference.py", line 129, in <module>     sample = pipe(args.prompt + POS_PROMPT, video_length=args.video_length, frames=pil_annotation,    File "/root/paddlejob/workspace/lxz/miniconda3/envs/controlvideo_py310/lib/python3.10/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context     return func(*args, **kwargs)   File "/root/paddlejob/workspace/lxz/ControlVideo/models/pipeline_controlvideo.py", line 902, in __call__     down_block_res_samples, mid_block_res_sample = self.controlnet(   File "/root/paddlejob/workspace/lxz/miniconda3/envs/controlvideo_py310/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1130, in _call_impl     return forward_call(*input, **kwargs)   File "/root/paddlejob/workspace/lxz/ControlVideo/models/controlnet.py", line 519, in forward     sample += controlnet_cond RuntimeError: The size of tensor a (24) must match the size of tensor b (12) at non-singleton dimension 2
It seems that the depth detector extracts the depth of the size of channel b(12), but the video_length is 24, the size of a(24), so how can solve this problem?

Maybe the length of input video is 12, which is less than video_length. Less video_length could address this problem.

Maybe the length of input video is 12, which is less than video_length. Less video_length could address this problem.

I have solved this problem, because when read video by the function read_video() in models/utils.py, the frame_rate is default to be 2, but when we want to keep all frames of the input video, it may lead this problem. For example, the total number of the input video is 24, and we want to keep all this 24 frames, the frame_rate should not to be 2. I suggest that, you can set the frame_rate in this function read_video() to be frame_rate = len(vr) // video_length.  Then users do not need to modify the value of frame_rate manually to avoid mismatching of its value.

Thanks for your suggestion! I have added it to the code.


python3Packages.django-hcaptcha: init at 0.2.0

Description of changes
Add a new package.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Please rebase this on top of master
Auto-merging pkgs/top-level/python-packages.nix
CONFLICT (content): Merge conflict in pkgs/top-level/python-packages.nix
Automatic merge failed; fix conflicts and then commit the result.

Please rebase this on top of master
Auto-merging pkgs/top-level/python-packages.nix
CONFLICT (content): Merge conflict in pkgs/top-level/python-packages.nix
Automatic merge failed; fix conflicts and then commit the result.

Fixed!

Superseded by 5c71b2335b8ecbb0aa18d0c2dfd1c4c4606f4985


[Bug]-[936]:SAML login fails with invalid request

Is there an existing issue for this?

[X] I have searched the existing issues

Description
While trying to login, the user sees Invalid Request post successful authentication on the IdP.
Keycloak logs contain the error :
"missing_required_destination"
Steps To Reproduce
Trying to reproduce the issue. Will add the steps post reproduction.
Public Sample App
No response
Version
EE Self Hosted

Stats

Stat
Values

Reach
78

Effort (months)
0.25

Estimating the time to fix and test this as one person-week. Please feel free to suggest a change.

Fixed by changing user configurations. Doesn't require a code change.


perturbing according to the covariance between features

The current implementation assumes feature independence and normality.
Can we add a mode that perturbs according to the covariance between the features? This can prevent distorted samples when too features are very correlated (or even the same in the extreme!)

I haven't seen the need for this (I think it's usually better to discretize the data beforehand anyway), but I would welcome a pull request if there are compelling eamples : )


Execute C# scripts from cmd with parameters?

What are you trying to achieve?
I have a C# script, it's saved to a file. When I execute the script from CMD, for example:
TabularEditor.exe "%bim_file_path%" -S "%script_file_path%" -BIM "%bim_file_path%" >> "%output_log_file_path%"
I would like to pass parameters to the script itself. Let's say...I would like to replace date filters in measures and I want to pass the new date to which I'll replace the old ones to. How could I achieve this directly and not indirectly? I thought about creating a "config file" somewhere that can be read from the C# script, "passing parameters" from there, but that seems an ugly workaround.

You can use environment variables. In the command line, you can set a variable before running TabularEditor.exe:
set datefilter=2023-01-28

In your C# script:
string dateFilter = Environment.GetEnvironmentVariable("datefilter");

Awesome, thanks for the quick answer and help!


⚠ Exoticaz has degraded performance

In 05e7be5, Exoticaz ($EZ) experienced degraded performance:

HTTP code: 200
Response time: 2048 ms

Resolved: Exoticaz performance has improved in fa4f1db.


Make decision of uwsgi usage easier

Currently, if one wants to use uwsgi or not, has some significant consequences regarding how sipa has to be started. To make this easier, there should be a start script, which decides based on an environment variable like SIPA_USE_UWSGI, what is run. Also, this “decision” could be passed to sipa to make some things easier, e.g. there does not have to be the monkey-patch when using uwsgi (or the other way around, I always forget).
This could perhaps be combined with the prefix, so keep #176 in mind.

There must be a way to autodetect this.

@sebschrader how about:
try:
    import uwsgi
except ImportError:
    use_uwsgi = False
else:
    del uwsgi
    use_uwsgi = True

?

At first sight, I would have rejected this. Because, what if the uwsgi module is present on sys.path, but then I read the uWSGI documentation of this module and it states

The uWSGI server automagically adds a uwsgi module into your Python apps.

So it should actually work.
What about:
use_uwsgi = 'uwsgi' in sys.modules

@sebschrader  That seems nice, I didn't know about sys.modules.

You should obviously verify that my suggestion actually works.
sys.modules is just a cache of already imported modules, but since the uwsgi does not seem to actually exist on the normal Python path and was automagically inserted as the documentation claims, it should be present.

The variable should be named under_uwsgi or similar BTW.

Closing, since

The dev environment uses uwsgi as well, so the “vanilla way” doesn't even have to be supported anymore
the problem is essentially solved by an if __name__ == '__main__' in sipa.py.


[flow analysis] promote variable in a function expression if not assigned inside it

void g(void Function() x) {}

void f(int? i) {
  int? x;
  if (i == null) return;
  x = i; // here x is not-nullable
  g(() {
    x.isEven; // 🔥 x is nullable
  });
}

Current behavior: on entering the function, x promotion is discarded, so it is not promoted to be not-nullable, because x is assigned outside the function.
If the variable is assigned inside the function, the promotion should be discarded.

https://dart-review.googlesource.com/c/sdk/+/277880

The example above seems sound because there is no demoting assignment to x down-flow from the creation of the closure.
If there were, it would not be sound to assume that x still has the same type when the function is eventually called.


Intervaltree: Replace on Duplicate ID

Rather than having to remove an interval and replace it with one of the same size, it'd be convenient to replace on duplicate interval and ID.
This does require consumers to guarantee uniqueness of an interval ID pair (which they should already be doing)
@dustinhiatt-wf @travissmith-wf

Raven
Number of Findings: 0

@matthinrichsen-wf You able to make these changes?


Sending Linear PCM audio chunks to a cloud service that has whisper deployment for transcription in an efficient way near real time

If we use Linear PCM (LPCM), which doesn't include headers and allows any segment of the audio to be played independently, we can send the audio chunks to the backend. With a method for silence detection, we could split the real-time audio into chunks and send these to OpenAI's Whisper for transcription. This approach could enable near real-time transcription display on the frontend, store the transcription, and perform summarization or other AI tasks.
I'm interested in finding out how to send the minimum amount of bytes with sufficient quality to a cloud-based Whisper deployment for transcription. This transcription could be saved as metadata for the audio recording, and the audio itself backed up to a cloud location. Additionally, generating .srt files with timestamps would allow users to jump to specific audio segments corresponding to the subtitles.

Hey there, sorry we didn't get to this earlier. I'm... Not entirely sure what you're asking here? :)


Update unity to 2017.3.1f1,fc1d3344e6ea

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for your contribution!


Vibrate plugin documentation issue

In documentation you have
 In your iOS, Android, and Windows Phone projects please call:

Xamarin.Forms.Init();//platform specific init
Vibrate.Init();

but in Xamarin Android the Vibrate.Init(); not exists. I saw here
https://github.com/jamesmontemagno/Xamarin.Plugins/blob/master/Vibrate/Refractored.Xam.Vibrate.Android/Vibrate.cs

You are looking in the wrong spot: https://github.com/jamesmontemagno/Xamarin.Plugins/blob/master/Vibrate/Refractored.Xam.Forms.Vibrate.Android/Vibrate.cs

Humm.... why the nuget do not recognize this method?
-----Original Message-----
From: "James Montemagno"<EMAIL_ADDRESS>Sent: 3/5/2015 7:18 PM
To: "jamesmontemagno/Xamarin.Plugins"<EMAIL_ADDRESS>Cc: "Sara Silva"<EMAIL_ADDRESS>Subject: Re: [Xamarin.Plugins] Vibrate plugin documentation issue (#37)
You are looking in the wrong spot: https://github.com/jamesmontemagno/Xamarin.Plugins/blob/master/Vibrate/Refractored.Xam.Forms.Vibrate.Android/Vibrate.cs
—
Reply to this email directly or view it on GitHub.

you changed the API but did not changed the documentation for this reason it was not work... you could say that!

And is CrossVibrate.Current.Vibration and it is not CrossVibrate.Current.Vibrate  :)

I updated it. The API didn't change I just documented it incorrect, thanks for the change. You can always send a pull request for typos as well.
I have also obsoleted the forms version as there is no need for it since there is a general nuget available that I created.

Sure, but I was using the nuget and read the code file on github and I did not have time to see more details.


[Doc] Update the link to IS carbon console in Configuring IS as a SAML 2.0 SSO IdP

Description:
Configuring WSO2 Identity Server as a SAML 2.0 SSO Identity Provider [1]
Step 2: "Sign in to the WSO2 IS Management Console UI (https://localhost:9444/carbon)" the link redirects to https://localhost:9443/carbon
[1] https://docs.wso2.com/display/AM220/Configuring+Identity+Server+as+IDP+for+SSO
Suggested Labels:
Doc

We will not be fixing this as this issue is based on an older version of the product.


Add Tech Events

https://github.com/eventil/awesome-tech-events
https://github.com/eventil/awesome-javascript-conferences
It's a new section for aggregating all tech events with a distinction between conferences and smaller events.
By submitting this pull request I confirm I've read and complied with the below requirements.
Failure to properly do so will just result in the pull request being closed and everyone's time wasted. Please read it twice. Most people miss many things.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title. For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should include a short description about the list project/theme (not the list itself), and should be added at the bottom of the appropriate category.
The list I added

has been around for at least 30 days,
is the result of hard work and is the best I could possibly produce,
is a non-generated Markdown file in a GitHub repo,
is not a duplicate,
includes a succinct description of the project/theme at the top (example),
includes a project logo/illustration (whenever possible) at the top right of the readme (example). (The logo should link to the project website or any relevant website. The logo should be high-DPI, so set it to maximum half the width of the original image.),
only has awesome items with descriptions (Awesome lists are curations of the best, not of everything),
contains the awesome badge on the right side of the list heading,
has a Table of Contents section named Contents as the first section,
has an appropriate license (Meaning something like CC0, NOT a code licence like MIT, BSD, Apache, etc) (If you use a license badge, it should be SVG, not PNG),
has contribution guidelines,
doesn't include a Travis badge,
has been checked for inconsistent formatting, spelling, and grammar:

Each link description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent naming. For example, Node.js, not NodeJS or node.js.

By submitting this pull request I confirm I've read and complied with the below requirements.

You obviously didn't, because these lists basically break every single requirement we have.


Add support for Anchor events

This PR adds support for Anchor events. It enables code like:
class XEvent(Event):
    x: u8
    y: u8

    def __init__(self, x: u8, y: u8):
        self.x = x
        self.y = y

  @instruction
  def init(payer: Signer, x: u8, y: u8):
      e = XEvent(x, y)
      e.x = 100
      e.emit()

I iterated a bit on this (see branch name lol), but settled on using a new DefinedType::Event for events, but then compiling them to a StructSignature (like accounts do) rather than their own ClassSignature (like enums).
They compile almost identically to plain structs. The differences are:

A #[event] macro
A generated __emit__ function in their impl Mutable block. This looks like eg:

fn __emit__(&self) {
    emit!(XEvent {
        x: self.borrow().x,
        y: self.borrow().y
    })
}

See Discord where this approach was originally suggested: https://discordapp.com/channels/1005658120548270224/1033829665493745694/1034555100871524393
Using the DefinedType::Event allows us to restrict the emit() call to only classes that inherit from Event in the compiler.
Closes #1

lgtm!


Update requirements.txt

Update requirements.txt
As we have seen in the past == causes issues when newer versions are made available.

Done


ItemsRepeater: Spec for adding First/LastVisibleIndex and RealizedItems properties to API

Background

ItemsRepeater is a flexible layout control that allows you to easily display collections of items complete with custom layouts, animations, styling, and more. Currently, there is no built-in way to access which items are visible or realized in the viewport of the ItemsRepeater. This inhibits lots of interaction-based UIs and puts lots of extra work on the developer to manually determine which items are visible.
ItemsRepeater does independent scrolling, and requires a buffer area that holds non-visible items and runs layout processes on them before they become visible/scrolled onto. This buffer area size is configurable via the HorizontalCacheLength and VerticalCacheLength properties.
The ListView and GridView controls  have properties to access the indices of their first and last visible items in the form of the FirstVisibleIndex and LastVisibleIndex properties on their respective base panels, ItemsStackPanel and ItemsWrapGrid. These properties allow you to access all currently visible items.
Description

RealizedItems and VisibleItems are properties that give you access to all realized or visible items within an ItemsRepeater. These two properties both return lists of UIElement objects that make up the ItemsRepeater.
Realized items includes all items that are currently visible and all items that are in the cache/buffer area. The size of these buffer areas are configurable via the HorizontalCacheLength and VerticalCacheLength properties
Visible items refers to all items that are visible in the ItemsRepeater, whether they are fully or partially visible.
Examples

/* Example 1: Check if a specific item is visible by the user. If visible, inform the user that they've scrolled to the bottom of the list. */

int repeater_length = repeater.ItemsSource.Count;

foreach (Grid item in repeater.VisibleItems){
  if (repeater.GetElementIndex(item) == repeater_length - 1){
    myTextBlock.Text = "No more elements to display.";
  }
}

/* Example 2: Change the background color of any items that have been seen by the user (i.e. they're visible on the screen). This example applies well to messaging scenarios where the styling is changed for messages that have been read/seen.

By using the RealizedItems property, any item that becomes visible while scrolling will have this changed background color.  */

foreach(StackPanel message in repeater.RealizedItems){
  // each item has a DataTemplate with a StackPanel root element
  message.Background = "Red";
}

API Notes

public IEnumerable<UIElement> RealizedItems { get; }
public IEnumerable<UIElement> VisibleItems { get; }

// RealizedItems and VisibleItems are *unsorted* IEnumerable objects.

API Details

unsealed runtimeclass ItemsRepeater : Windows.UI.Xaml.FrameworkElement
{
    ItemsRepeater();

    // ...
    Windows.Foundation.Collections.IEnumerable<Windows.UI.Xaml.UIElement> RealizedItems { get; }

    Windows.Foundation.Collections.IEnumerable<Windows.UI.Xaml.UIElement> VisibleItems { get; }

    // ...
}

Should the RealizedItems property return an IEnumerable or List? Or should it simply return an object to match the ItemsSource property?

Similiar to what SelectionModel does, I think exposing an IEnumerable<UIElement> would be the best scenario. After all, we we know that the realized items must be UIElements and, we know that it should be a list.
I think the reason why ItemsSource is object is because of the fact that it can accept a broad range of object types. In theory IIterable could be sufficient, but I am not 100% if that would have worked with the projections.

Should the RealizedItems property return an IEnumerable<object> or List<object>? Or should it simply return an object to match the ItemsSource property?
Similiar to what SelectionModel does, I think exposing an IEnumerable<UIElement> would be the best scenario. After all, we we know that the realized items must be UIElements and, we know that it should be a list.
I think the reason why ItemsSource is object is because of the fact that it can accept a broad range of object types. In theory IIterable could be sufficient, but I am not 100% if that would have worked with the projections.
PS: Not entirely sure why but MD seems broken for that comment, so I've added the initial question as code block to differentiate it from my response.

Yes.  Definitely more type safety where possible. ItemsSource is a bit special because it is trying to do the same thing that ItemsControl did for compat reasons and there was not one underlying type we could use there other than object.
One thing to note/question. Should the returned list of realized elements have an order (index order) ? Not guaranteeing an order would be preferred because sorting by index can become a performance issue. I think in most cases the app developer would only care about the set and not the order. If order matters, it can be sorted in the app code. I think it is worth calling that out.

One thing to note/question. Should the returned list of realized elements have an order (index order) ? Not guaranteeing an order would be preferred because sorting by index can become a performance issue. I think in most cases the app developer would only care about the set and not the order. If order matters, it can be sorted in the app code. I think it is worth calling that out.

How would the sorting look like from an App's perspective? Get the index of each realized item and sort via those?
Depending on the layout, the items probably are already sorted, but in general, we would need to sort it to be sure. Since ItemsRepeater is focused on performance, I wouldn't say it's necessary to add the overhead of sorting those. After all in most cases, you are interested in the realized items to update them based on a certain criteria which most likely won't rely on the position in the collection. So, I agree with @ranjeshj, we should call that out that it is not guaranteed the items are in a specific order.

You got here so fast, @chingucoding! :)
Thanks Marcel and @ranjeshj - I agree that type safety should be prioritized. I'll make the change to have it return an IEnumerable. This also makes it much easier to interact with the items inside the list without having to go through the trouble of casting it.
I agree on leaving RealizedItems unsorted.  I think that if you wanted to access the first or last index of the RealizedItems (i.e. needed it to be sorted), you could just use FirstVisibleIndex or LastVisibleIndex to receive the same value, even in non-contiguous scenarios. Can't think of any other common use case where you'd need to know the order of the realized items.

@ranjeshj Bringing this back to life. Any more questions/concerns?

@ranjeshj Bringing this back to life. Any more questions/concerns?

Looks good to me.

@MikeHillberg - would you be able to review this spec? Looks like Ranjesh has approved it, so not totally sure of the next step here. Thanks!


[Improve][Connector-V2] Refactor hdfs file sink connector code structure

Purpose of this pull request
According to pr https://github.com/apache/incubator-seatunnel/pull/2555 , this pr has optimized the hdfs file sink connector on top of it.

Check list

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

@CalvinKirs @EricJoy2048 PTAL.

@CalvinKirs @EricJoy2048 PTAL.

Sorry, some classes are used in hive-connector, I need to refactor hive connector first.

@CalvinKirs @EricJoy2048 PTAL.

Sorry, some classes are used in hive-connector, I need to refactor hive connector first.

This pr is ready. Please review. @EricJoy2048 @CalvinKirs


Setting RenewTickets does not respect existing cache file settings

Setting RenewTickets seems to "forget" cache configuration of the client and revert back to default cache location. Code used:
            var client = new KerberosClient(config, loggerFactory);
            client.CacheInMemory = false;
            client.Cache = new Krb5TicketCache(options.CacheFile);
            client.RenewTickets = true;

after the last line runs, the cache is no longer pointing to what is specified in options.CacheFile.

That's certainly odd. The client.RenewTickets property just sets client.Cache.RenewTickets which is not used at all in Krb5TicketCache. I suspect that line is a red herring. I believe what's happening is KerberosClient.SetupCache() is being called when client.Cache is geted, which is querying the client-wide configuration for it's cache path.
https://github.com/dotnet/Kerberos.NET/blob/ddc0f270988b812dd6cd4dc71cfbbac5d938d21c/Kerberos.NET/Client/KerberosClient.cs#L686-L709
https://github.com/dotnet/Kerberos.NET/blob/ddc0f270988b812dd6cd4dc71cfbbac5d938d21c/Kerberos.NET/Client/KerberosClient.cs#L712-L726

I recently did an overhaul of how the client instantiates the cache. Can you see if this repros for you anymore?


Running as root without --no-sandbox is not supported.

Hi, I have a problem I run sudo make stress and it gives thsi error:
Error: Failed to launch the browser process!
[0110/215548.567156:ERROR:zygote_host_impl_linux.cc(90)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
When I run without sudo it just gives me permission denied.
Can you advise?

@ralfsf007 you shouldn't run it as root. Can you paste the permission denial here?

@ralfsf007 you shouldn't run it as root. Can you paste the permission denial here?

@ralfsf007 you shouldn't run it as root. Can you paste the permission denial here?

@sampaccoud Thank you for your reply. The reqested error:
Traceback (most recent call last):
File "urllib3/connectionpool.py", line 677, in urlopen
File "urllib3/connectionpool.py", line 392, in _make_request
File "http/client.py", line 1252, in request
File "http/client.py", line 1298, in _send_request
File "http/client.py", line 1247, in endheaders
File "http/client.py", line 1026, in _send_output
File "http/client.py", line 966, in send
File "docker/transport/unixconn.py", line 43, in connect
PermissionError: [Errno 13] Permission denied
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "requests/adapters.py", line 449, in send
File "urllib3/connectionpool.py", line 727, in urlopen
File "urllib3/util/retry.py", line 403, in increment
File "urllib3/packages/six.py", line 734, in reraise
File "urllib3/connectionpool.py", line 677, in urlopen
File "urllib3/connectionpool.py", line 392, in _make_request
File "http/client.py", line 1252, in request
File "http/client.py", line 1298, in _send_request
File "http/client.py", line 1247, in endheaders
File "http/client.py", line 1026, in _send_output
File "http/client.py", line 966, in send
File "docker/transport/unixconn.py", line 43, in connect
urllib3.exceptions.ProtocolError: ('Connection aborted.', PermissionError(13, 'P                                                                                ermission denied'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "docker/api/client.py", line 205, in _retrieve_server_version
File "docker/api/daemon.py", line 181, in version
File "docker/utils/decorators.py", line 46, in inner
File "docker/api/client.py", line 228, in _get
File "requests/sessions.py", line 543, in get
File "requests/sessions.py", line 530, in request
File "requests/sessions.py", line 643, in send
File "requests/adapters.py", line 498, in send
requests.exceptions.ConnectionError: ('Connection aborted.', PermissionError(13,                                                                                'Permission denied'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "bin/docker-compose", line 3, in
File "compose/cli/main.py", line 67, in main
File "compose/cli/main.py", line 123, in perform_command
File "compose/cli/command.py", line 69, in project_from_options
File "compose/cli/command.py", line 132, in get_project
File "compose/cli/docker_client.py", line 43, in get_client
File "compose/cli/docker_client.py", line 170, in docker_client
File "docker/api/client.py", line 188, in init
File "docker/api/client.py", line 213, in _retrieve_server_version
docker.errors.DockerException: Error while fetching server API version: ('Connec                                                                                tion aborted.', PermissionError(13, 'Permission denied'))
[58180] Failed to execute script docker-compose
Makefile:47: recipe for target 'stress' failed
make: *** [stress] Error 255

@ralfsf007 you shouldn't run it as root. Can you paste the permission denial here?

@sampaccoud Thank you for your reply. The reqested error:
Traceback (most recent call last):
File "urllib3/connectionpool.py", line 677, in urlopen
File "urllib3/connectionpool.py", line 392, in _make_request
File "http/client.py", line 1252, in request
File "http/client.py", line 1298, in _send_request
File "http/client.py", line 1247, in endheaders
File "http/client.py", line 1026, in _send_output
File "http/client.py", line 966, in send
File "docker/transport/unixconn.py", line 43, in connect
PermissionError: [Errno 13] Permission denied
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "requests/adapters.py", line 449, in send
File "urllib3/connectionpool.py", line 727, in urlopen
File "urllib3/util/retry.py", line 403, in increment
File "urllib3/packages/six.py", line 734, in reraise
File "urllib3/connectionpool.py", line 677, in urlopen
File "urllib3/connectionpool.py", line 392, in _make_request
File "http/client.py", line 1252, in request
File "http/client.py", line 1298, in _send_request
File "http/client.py", line 1247, in endheaders
File "http/client.py", line 1026, in _send_output
File "http/client.py", line 966, in send
File "docker/transport/unixconn.py", line 43, in connect
urllib3.exceptions.ProtocolError: ('Connection aborted.', PermissionError(13, 'P                                                                                ermission denied'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "docker/api/client.py", line 205, in _retrieve_server_version
File "docker/api/daemon.py", line 181, in version
File "docker/utils/decorators.py", line 46, in inner
File "docker/api/client.py", line 228, in _get
File "requests/sessions.py", line 543, in get
File "requests/sessions.py", line 530, in request
File "requests/sessions.py", line 643, in send
File "requests/adapters.py", line 498, in send
requests.exceptions.ConnectionError: ('Connection aborted.', PermissionError(13,                                                                                'Permission denied'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "bin/docker-compose", line 3, in
File "compose/cli/main.py", line 67, in main
File "compose/cli/main.py", line 123, in perform_command
File "compose/cli/command.py", line 69, in project_from_options
File "compose/cli/command.py", line 132, in get_project
File "compose/cli/docker_client.py", line 43, in get_client
File "compose/cli/docker_client.py", line 170, in docker_client
File "docker/api/client.py", line 188, in init
File "docker/api/client.py", line 213, in _retrieve_server_version
docker.errors.DockerException: Error while fetching server API version: ('Connec                                                                                tion aborted.', PermissionError(13, 'Permission denied'))
[58180] Failed to execute script docker-compose
Makefile:47: recipe for target 'stress' failed
make: *** [stress] Error 255

Hello @ralfsf007
As a fast fix you can use the branch proposed in #8.
I'll propose another solution soon to avoid this error.

Hello @ralfsf007
As a fast fix you can use the branch proposed in #8.
I'll propose another solution soon to avoid this error.

@madmatah Hi, thank you that worked.
Mybe you know where I can set timeout time aswell after few users successfully connect I get timeout error: Unable to initialize client K.C.2618 : TimeoutError: Navigation timeout of 30000 ms exceeded

@madmatah Hi, thank you that worked.
Mybe you know where I can set timeout time aswell after few users successfully connect I get timeout error: Unable to initialize client K.C.2618 : TimeoutError: Navigation timeout of 30000 ms exceeded

For the record, if others encounter this problem : we really encourage you not to run this project as root.
Can you run docker ps with your current user ? You should be able to.
If this is not the case, I invite you to follow the instructions here to be able to run docker as a non-root user: https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user
(You probably just have to add your user to the docker group and logout/log back in)
@ralfsf007 : for your question, you should be able to tweak this timeout as explained here by updating the code.

For the record, if others encounter this problem : we really encourage you not to run this project as root.
Can you run docker ps with your current user ? You should be able to.
If this is not the case, I invite you to follow the instructions here to be able to run docker as a non-root user: https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user
(You probably just have to add your user to the docker group and logout/log back in)
@ralfsf007 : for your question, you should be able to tweak this timeout as explained here by updating the code.


Image sharing update

WIP: Still need to get the UI for visualizing the processing images in the thread timeline.
But, it's to the point where we should start discussing the code.

Cleans up image sharing data flow
Adds new ProcessingImagesRedux that tracks state of images before they are done sharing to a thread.
Reverses the order of processing, now we add to IPFS, upload, add to wallet, share to thread

Ah need to update the tests as well, they're failing now

clooooose?!?


Add Custom vision 2.0 Swagger

Adding V2.0 of the Custom Vision Training and Prediction Swagger
This was already approved with private PR#454 by @mcardosos
PR information

[X] The title of the PR is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[X] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[X] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[X] I have read the contribution guidelines.
[X] My spec meets the review criteria:

[X] The spec conforms to the Swagger 2.0 specification.
[X] The spec follows the guidelines described in the Swagger checklist document.
[X] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@AutorestCI rebuild

Automation for azure-libraries-for-java

Automation for azure-sdk-for-node

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go


ida: extractor doesn't calls to recognize extern symbols

When analyzing .lib/COFF files, such as those produced while building a static library, capa doesn't recognize calls to extern symbols. These are calls to routines that will be fixed up by the linker in a subsequent compilation step but aren't available yet. Notably, there is a symbol name associated with the call target. capa should recognize the extern symbol name and emit an API feature for it.
This is probably not super relevant for typical capa workflows, because usually the entire linked executable is available (we don't even really support analyzing non-PE/elf files). However, for systems that use capa to extract features from functions, this is useful.
I'm not certain of the best way to identify extern symbols in IDA, but one way is to walk the segments and collect those of type SEG_XTRN. Any call targets within these sections are extern symbols.
    ... some global setup ...

        extern_ranges = []

        for segstart in idautils.Segments():
            seg = ida_segment.getseg(segstart)

            if not (seg.type == ida_segment.SEG_XTRN):
                continue

            extern_ranges.append(
                (seg.start_ea, seg.end_ea)
            )

    ... extract_insn_api_features ...

        for start, end in extern_ranges:
            if start <= target < end:
                name = ida_name.get_name(target_func.start_ea)
                yield capa.features.insn.API(name), ih.address

viv doesn't support the COFF file format so this isn't relevant there.

call to extern:

extern symbol:

example input file for above:
http.c.zip


Add the documentation links from Links annotations in CSDL to OpenAPI Operations

Given the Links annotation in the CSDL:

We would want to add the external doc. link (from the href property) to the generated OpenAPI doc. in the ExternalDocs property of operations:

just a quick note on the openapi example, it contains a MD extension that shouldn't be here.

just a quick note on the openapi example, it contains a MD extension that shouldn't be here.

FYI @millicentachieng to action on API Doctor


[v2] Deprecations

Few things we should hard deprecate before shipping:

[x] hideDefaultContent() (default-content hard deprecated in v2)

[x] hashTracking (moved to simpla-admin)

[x] webcomponents.js import - too fragile, include as bower/npm dep and tell users to include separately (or from cdnjs if we keep app.simpla.io CDN)

[x] Slim down usageMonitoring and rename to ping or similar - should literally be a 200 okay from the SDK, no need for sessions or elements?

[ ] Use Babel plugins over core-js polyfills? Nicer to have it as part of our transform, rather than separate deps. Also often lighter than polyfills

[x] Can we move the deprecatedConfig to v2-compat layer since it's just for elements?

This looks good, and yes to the two questions.

Cool. And one other thing on webcomponents.js - I'd actually say not include it as a dep at all, and in docs/snippets just link from cdnjs. Those more familiar with WC can always install w/ Bower themselves if they like (it's not available on NPM, and it's js... Srsly google why).

Cool, don't think I've got any issues with that. I'm always keen on polyfills separate - FWIW see this issue on polyfill.io service, though don't think anyone's gonna do it anytime soon, I certainly don't have time for it. Plus that's for v1.

Nice! Well when that gets shipped we just change our docs and snippets to use polyfill.io over cdnjs.
And for the record I still think we should include minor polyfills (eg: promise and fetch) as part of our bundle. They're robust enough not to be an issue, and the extra bundle size is worth the usability improvement of not worrying about those sdk-specific reqs. I tend to think of that kind of thing as similar to including an ES5 build (esp If we do them with babel plugins anyway). WC is a different beast though.

Agreed. And I think that can potentially be mitigated by other builds which are 'pure' - but not worth stressing about right now

Note: this deprecation

Slim down usageMonitoring and rename to ping or similar - should literally be a 200 okay from the SDK, no need for sessions or elements?

Would break the 'use elements' project setup step on the simpla.io dashboard, in that it'd no longer auto-complete when elements have been used. Do we care about this?

The 'use elements' step on the setup screen is now activated when a project has had data fetched from it (or attempted to at least), which is done via the API content fetched service, not no longer the usage monitoring ping, so it'll all still work even without the element information.

Ah, awesome. And I assume that still gets hit when elements request a non-existent UID / 404 content?

Yup - it only gets set on the project on the first call to fetching content, whether the content is there yet or not

👍

Re: Polyfills, for fetch we'll use https://github.com/developit/unfetch rather than babel transform, because 500 bytes (!)

Right so tried removing the polyfills and using the babel transform-runtime but rollup was having some funky errors with it (https://github.com/rollup/rollup-plugin-babel/issues/40). But they're not needed for deprecations anyway, that's an internal optimization, so can leave it for another time correct? Same with using unfetch instead of fetch.

Fixed in https://github.com/simplaio/simpla/commit/e29e22047cd844611653ea70e50c951a3f24b6a5


High memory usage in testworld and berkeley testnets

Gareth reports 120Gb used in berkeley daemon, running in the cloud, leading to an OOM crash.
A testworld seed is using 25Gb, according to kubectl top pod.

I did grab a screenshot from htop for this excessive memory usage. Seems related to the network activity as memory usage grows far less quickly now:

RFC for memory usage improvement- https://github.com/MinaProtocol/mina/pull/14675


hana-cloud-iq-datalake-migration

Single tutorial

This was closed by mistake when I tried to reset the fork.


it can't edit fixer list from inspector

I'm using unity 2022.1.23f1,.The clothes behaviour is working, but I can't edit (change list count or add elements for fixer list). How can I solve this bug?

Hello again @yhh1209 . I've fixed the problem on my Unity newer version (2021.3.10f1), which also had the issue. I believe this will also fix your version, if not, please contact me again. I will commit the changes in the main branch in a moment and If I have the time, I may publish a new release.
About the problem, apparently the newer versions of Unity require the serielizedObject List<> properties to be explicitly updated for a reason that for now I don't understand. Take a look at the image I sent you to see how to fix the issue.

I also leave you a link for the documentation of the class that is giving the problems if you want to check it.
https://docs.unity3d.com/ScriptReference/SerializedObject.html
Please, contact me again if this modification solved your problem in order to close this issue.

@AEspinosaDev Wow, I had the same issue and that worked for me. Thanks :D

Probably the best fabric simulation I've ever seen and even github. Thank you very much

Hello , where can I find the tutorial for this plug in ?


More examples and docs for creating ALERTING RULES

My question is how can I create alert between two metrics?
For example
ALERT
 IF metric_1 > 3 * metric_1
 FOR 5m
 LABELS { severity = "page" }
 ANNOTATIONS {
     summary = "metric_1 > 3 * metric_1",
     description = "metric_1 > 3 * metric_1",
}

any ideas?
in log I see this
msg="Error loading rules, previous rule set restored: error parsing /etc/prometheus/alert.rules: parse error at line 11, char 3: unexpected <IF> in alert statement, expected identifier" source="manager.go:415"

Your alert does not have a name after the ALERT clause.
The syntax is described here: http://prometheus.io/docs/alerting/rules/

@fabxc
time="2016-03-05T03:49:19Z" level=error msg="Error loading rules, previous rule set restored: error parsing /etc/prometheus/alert.rules: parse error at line 11, char 3: unexpected <IF> in alert statement, expected identifier" source="manager.go:415"
Makefile:4: recipe for target 'prometheus' failed


lua: Expose stream info downstreamLocalAddress and downstreamDirectRemoteAddress for Lua filter

Commit Message:
Client IP should be very commonly used and helpful for users.
Expose downstreamLocalAddress and downstreamDirectRemoteAddress help us get client IP in  Lua filters.
Risk Level: Low
Testing: Modify unit test
Docs Changes: updated Lua filter doc
Release Notes: N/A
Signed-off-by: nic-chen<EMAIL_ADDRESS>

Add @nic-chen, sorry, after applying my suggestion here: https://github.com/envoyproxy/envoy/pull/13536#discussion_r506044523 could you merge main?  🙏🏽

@nic-chen, sorry, after applying my suggestion here: #13536 (comment) could you merge main? 🙏🏽

done.

/retest

@nic-chen I think you can do merge master instead of rebasing your branch with the master (so you don't have to do force-pushing).

@dio
OK. thanks for tips.
will pay attention next time.
do I need to do something now ?


Hex color strings allowed as direct props to link component

Is your iteration request related to a problem?
I need to be able to pass hex color strings as a prop to link component
Describe the solution you'd like
be able to pass hex color strings as a prop to link component
Additional context
Nothing

here's the alternative way to pass hex color string into your link component
<Link color href="#" css={{color: "#F96123"}}>THIS</Link>

Hey @jeelmakani the idea behind NextUI and Stitches is to have a system design with predefined colors like primary, secondary, link etc, NextUI provides you with a way to modify those colors (https://nextui.org/docs/theme/customize-theme), that's why is not allowed to pass color strings instead you can use the css property as @Dhananjay-JSR mentioned for setting a custom color that you haven't defined in your theme


feat: Adding Secure Web Proxy to examples

Hey folks.
This PR adds the Secure Web Proxy (SWP/SWG) to the examples.

Moved to PR https://github.com/GoogleCloudPlatform/terraform-google-cloud-functions/pull/46


create fabric +595 crashing with exit code 1

Describe the Bug
fabric 0.14.6
game crashes with exit code 1
even with a new profile with no other mods
Reproduction Steps

use curseforge to install fabric and fabric api
install crate fabric
start launcher
click play
crash with exit code 1

Expected Result
not crash
Screenshots and Videos
No response
Crash Report or Log
https://pastebin.com/xvt0dj2h
Operating System
windows 11
Mod Version
0.4.1
Minecraft Version
1.18.2
Other Mods
No response
Additional Context
No response

#343


Reformated slack API

This PR contains the following changes:

Made the Slack API more readable
Shades simple-json in jar to avoid recoding the SlackMessage for bungeecord.
Only uses 1 runnable to send messages.
This reformat also magically fixes #11

Thanks for the contribution, but SlackMC 2.0 has changed the format of the plugin already, and includes some of the changes you want to merge, like message collection, a unified Bungee and Bukkit sender, and is completely reformated to be more friendly for developers.
Again, I appreciate your hard work, but I won't merge this because of the upcoming release.

Oke :smile:. Can't wait for the 2.0 release thought :+1:.

Me neither! :smile:


appimage-run: Create desktop entry

Description of changes
Adds an appimage-run.desktop file to enable running appimage files in GUI applications like Nautilus.
Thanks @jtojnar for help with the tests!
I'm not sure whether this works as intended or how to test this on my desktop without building master for hours. Installing does not seem to automatically assign the desktop file to the relevant MIME type:
$ nix-env -iA appimage-run -f ~/my\ projects/nixpkgs
installing 'appimage-run'
$ gio mime application/vnd.appimage
No default applications for “application/vnd.appimage”

Do I need to refer to copyDesktopItems? How do I combine that with buildFHSUserEnv?
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/how-to-test-desktop-item-mime-types/24510/10


Feature Request: Return Stream api's

Provide api overloads that return the Stream object directly so it can be wrapped with StreamReader or other processing without having to fill a stream or file first.

@jjxtra  why not use the OpenRead/OpenWrite APIs, they directly provide the Steam.

Return the stream object of what? We already have low level methods, check
out OpenRead et al
On Sun, Apr 17, 2022, 3:33 AM Jeff Johnson @.***> wrote:

Provide api overloads that return the Stream object directly so it can be
wrapped with StreamReader or other processing without having to fill a
stream or file first.
—
Reply to this email directly, view it on GitHub
https://github.com/robinrodricks/FluentFTP/issues/863, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABT3UKTY4TYRDDA4UJYDUMLVFM2LNANCNFSM5TS5WTKQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


narrow tested properties in cli tests

What do people think of this? This is using a tiny crate that I came up with yesterday: unsafe_get. We could also just put this into this project. But it seems generally useful. Should I put it on crates.io?
@matthandlersux @jondistad @data-pup @hallettj

I think it could be useful to have that crate available.

this is really neat, I would endorse that as a separate crate for sure :slightly_smiling_face:


jetbrains.plugins: extend update script for source builds

This updates update_plugins.json to also include source build numbers. This way plugins can no longer break if only either the bin or source versions are updated.
Fixes #366062, but we should also make a backport for #360031 if we plan to backport this PR (which we should).
Also updates the plugins.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

True, but I guess since it's currently still manually updated people can just make sure they match manually as well.
In the next step I want to add automation for source builds as well.

In the next step I want to add automation for source builds as well.

@theCapypara Here are some infomations that you can use:

With the build number, we can prefetch the IntelliJ community and Android plugin source code, prefetching process should also give the updater script the unpacked source code path which will be used in subsequent points
.idea/kotlinc.xml in the IntelliJ code specified the Kotlin version to use, both for compiler (this version or closer should be used to prevent issues like #367486 from happening) and JPS plugin classpath

Prefetch https://cache-redirector.jetbrains.com/maven.pkg.jetbrains.space/kotlin/p/kotlin/kotlin-ide-plugin-dependencies/org/jetbrains/kotlin/kotlin-dist-for-ide/{version}/kotlin-dist-for-ide-{version}.jar for compiler and https://cache-redirector.jetbrains.com/maven.pkg.jetbrains.space/kotlin/p/kotlin/kotlin-ide-plugin-dependencies/org/jetbrains/kotlin/kotlin-jps-plugin-classpath/{version}/kotlin-jps-plugin-classpath-{version}.jar for classpath

Repositories URLs for building Maven root can be found in .idea/jarRepositories.xml in the IntelliJ code
We should be able to reuse the source/build_maven.py file for prerecorded maven artefacts.

The only remaining issues:

jps-bootstrap-repository still required a manual rebuild
Restarter hash for whatever reason changes with the IntelliJ code, I think it's updated less frequently so maybe we can use a prerecorded hash?

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 366290

@leona-ya Hi! Can you review this PR and give feedback on whether we should backport #360031 ? I'm not entirely sure if this would be OK with the backports policy, though it seems Jetbrains IDEs have always been backported in the past?
If we don't want to backport I need to add the IDE builds of the source-built IDEs currently in 24.11 to this PR as well so we can at least backport this PR and fix https://github.com/NixOS/nixpkgs/issues/366062


fix: Dependabot Security Alert Fix for Docusaurus Packages

What does this PR do?
🛑 Please open an issue first to discuss any significant work and flesh out details/direction - we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

This PR addresses security vulnerabilities in the ws package used by Docusaurus dependencies.
Issues Addressed:
Issue #53: ws affected by a DoS when handling a request with many HTTP headers.
Conflicting dependencies<EMAIL_ADDRESS><EMAIL_ADDRESS>and<EMAIL_ADDRESS>Current ws version: 7.5.10
Fixed version: 8.17.1 (not currently compatible with existing dependencies).
Issue #52: ws affected by a DoS vulnerability.
Same conflicting dependencies and fixed version requirements as Issue #53.
Motivation

More

[x] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[ ] Mandatory for new blueprints. Yes, I have added a example to support my blueprint PR
[ ] Mandatory for new blueprints. Yes, I have updated the website/docs or website/blog section for this feature
[x] Yes, I ran pre-commit run -a with this PR. Link for installing pre-commit locally

For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

/hold
fixing the workflow failure issue


Remove tweepy

Streaming API is deprecated in the Twitter API v4.0. https://developer.twitter.com/en/docs/ads/general/overview/versions.html
Also, tweepy is not supporting version 4.0, and it is not managed well.
Because the bot only uses the streaming feature, it might be good to remove tweepy and implement directly.

https://developer.twitter.com/en/docs/basics/authentication/guides/single-user.html
Using Python-OAuth2 library section.

import json
import oauth2

setting = json.load(open('setting.json', 'r'))

def oauth_req(url, http_method="GET", post_body=b"", http_headers=None):
    consumer = oauth2.Consumer(key=setting['tw_consumer_key'], secret=setting['tw_consumer_secret'])
    token = oauth2.Token(key=setting['tw_access_token'], secret=setting['tw_access_secret'])
    client = oauth2.Client(consumer, token)
    resp, content = client.request( url, method=http_method, body=post_body, headers=http_headers )
    return content

#home_timeline = oauth_req( 'https://api.twitter.com/1.1/statuses/home_timeline.json')
url = 'https://api.twitter.com/1.1/statuses/user_timeline.json?screen_name=twitterapi&count=2'
timeline = oauth_req(url)
print(json.loads(timeline))```
Working well, with https://github.com/joestump/python-oauth2


badge="0" not showing

Hi ,
I want to show 0 on badge but it is not showing .. if I use badge="1" then it is showing . What to do ?

Fixed in 2.6.0


Error in creating nonsilence_phones.txt

When running on Samromur V1 the phones
ɪː
ʏ
ɣ
ɲ
arent added to the file  nonsilence_phones.txt. Somethings not right around line 160 in perp_data.sh.
The phones are defentially in the lexicon.

Fixed in develop branch


20818e16 and b0f4d537 has mistype

my model told me that:
evaluation/20818e16.json ['train'][2]['output'] - size(9,8) => (8,8)
evaluation/b0f4d537.json ['train'][0]['output'] - middle line need move 1px righter
seems its true =)

I can confirm that b0f4d537 has been fixed.
ARC-Interactive with the fixed task

However 20818e16 has not been fixed, so this issue cannot be closed yet.

Issuing a fix.

I can confirm the fixes works. Thank you.
task 20818e16 and task b0f4d537


Change default Perl on Windows Images

The Windows runners have two versions of Perl installed. Strawberry Perl should be first in the default path ahead of git-bash Perl because it handles Windows newlines better.
https://github.com/actions/virtual-environments/issues/123
Changes:

Moved Perl installation before Git-Install to change directories order in the Path

/azp run windows2016, windows2019

/azp run windows2019


FLUSHALL ?

Before I could do client.flushall() deleting the entire cache, upgrading to the latest version and the new interface it no longer works and I can't find the FLUSHALL command.

client.flushAll() or client.FLUSHALL() should work


Update triggerfile

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: pgodowski
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [pgodowski]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/test all

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

Test name
Commit
Details
Rerun command

test_ibm-monitoring-grafana-operator
fd8ddd9606184661e8ee136f685454d2e1550ddb
link
/test test ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

test_ibm-monitoring-grafana-operator
514123c775072e0f8fee0fdcd7a42ee3aa650b6f
link
/test test ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

test_ibm-monitoring-grafana-operator
514123c775072e0f8fee0fdcd7a42ee3aa650b6f
link
/test test ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
514123c775072e0f8fee0fdcd7a42ee3aa650b6f
link
/test build ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

test_ibm-monitoring-grafana-operator
514123c775072e0f8fee0fdcd7a42ee3aa650b6f
link
/test test ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
514123c775072e0f8fee0fdcd7a42ee3aa650b6f
link
/test build ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
514123c775072e0f8fee0fdcd7a42ee3aa650b6f
link
/test check ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

test_ibm-monitoring-grafana-operator
514123c775072e0f8fee0fdcd7a42ee3aa650b6f
link
/test test ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
bc8252514b2baf459d0a4d5ae1b0357bc5be371c
link
/test check ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
bc8252514b2baf459d0a4d5ae1b0357bc5be371c
link
/test build ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

check_ibm-monitoring-grafana-operator
bc8252514b2baf459d0a4d5ae1b0357bc5be371c
link
/test check ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
bc8252514b2baf459d0a4d5ae1b0357bc5be371c
link
/test build ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
bc8252514b2baf459d0a4d5ae1b0357bc5be371c
link
/test test ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

build_ibm-monitoring-grafana-operator
bc8252514b2baf459d0a4d5ae1b0357bc5be371c
link
/test build ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
7820b3e785f576f0fea91d9a0b976af1b1dc87cc
link
/test check ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
7820b3e785f576f0fea91d9a0b976af1b1dc87cc
link
/test test ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

check_ibm-monitoring-grafana-operator
7820b3e785f576f0fea91d9a0b976af1b1dc87cc
link
/test check ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
7820b3e785f576f0fea91d9a0b976af1b1dc87cc
link
/test test ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
7820b3e785f576f0fea91d9a0b976af1b1dc87cc
link
/test build ibm-monitoring-grafana-operator

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.

/test all

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: pgodowski
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Rerun command

check_ibm-monitoring-grafana-operator
7820b3e785f576f0fea91d9a0b976af1b1dc87cc
link
/test check ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
7820b3e785f576f0fea91d9a0b976af1b1dc87cc
link
/test build ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
d183ba8d0ef26f294502bb99b2f85ffd2b6eaa02
link
/test test ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

build_ibm-monitoring-grafana-operator
7820b3e785f576f0fea91d9a0b976af1b1dc87cc
link
/test build ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
d183ba8d0ef26f294502bb99b2f85ffd2b6eaa02
link
/test test ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
d183ba8d0ef26f294502bb99b2f85ffd2b6eaa02
link
/test check ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

test_ibm-monitoring-grafana-operator
d183ba8d0ef26f294502bb99b2f85ffd2b6eaa02
link
/test test ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
d183ba8d0ef26f294502bb99b2f85ffd2b6eaa02
link
/test check ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
d183ba8d0ef26f294502bb99b2f85ffd2b6eaa02
link
/test build ibm-monitoring-grafana-operator

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.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: pgodowski
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [pgodowski]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Rerun command

test_ibm-monitoring-grafana-operator
d183ba8d0ef26f294502bb99b2f85ffd2b6eaa02
link
/test test ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
d183ba8d0ef26f294502bb99b2f85ffd2b6eaa02
link
/test check ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
7e87f82bad9665d2cfe466cf1697ef5d118cdf73
link
/test build ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

check_ibm-monitoring-grafana-operator
d183ba8d0ef26f294502bb99b2f85ffd2b6eaa02
link
/test check ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
7e87f82bad9665d2cfe466cf1697ef5d118cdf73
link
/test build ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
7e87f82bad9665d2cfe466cf1697ef5d118cdf73
link
/test test ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

build_ibm-monitoring-grafana-operator
7e87f82bad9665d2cfe466cf1697ef5d118cdf73
link
/test build ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
7e87f82bad9665d2cfe466cf1697ef5d118cdf73
link
/test test ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
7e87f82bad9665d2cfe466cf1697ef5d118cdf73
link
/test check ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

build_ibm-monitoring-grafana-operator
7e87f82bad9665d2cfe466cf1697ef5d118cdf73
link
/test build ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
7e87f82bad9665d2cfe466cf1697ef5d118cdf73
link
/test test ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
19de591950102f1e07b07fa0dd832ba12c8e08dd
link
/test check ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

build_ibm-monitoring-grafana-operator
7e87f82bad9665d2cfe466cf1697ef5d118cdf73
link
/test build ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
19de591950102f1e07b07fa0dd832ba12c8e08dd
link
/test check ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
19de591950102f1e07b07fa0dd832ba12c8e08dd
link
/test test ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

check_ibm-monitoring-grafana-operator
19de591950102f1e07b07fa0dd832ba12c8e08dd
link
/test check ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
19de591950102f1e07b07fa0dd832ba12c8e08dd
link
/test test ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
19de591950102f1e07b07fa0dd832ba12c8e08dd
link
/test build ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

check_ibm-monitoring-grafana-operator
19de591950102f1e07b07fa0dd832ba12c8e08dd
link
/test check ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
19de591950102f1e07b07fa0dd832ba12c8e08dd
link
/test build ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
af9d77041f74a8cf6ce5061bbbd84892681c73ed
link
/test test ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

check_ibm-monitoring-grafana-operator
19de591950102f1e07b07fa0dd832ba12c8e08dd
link
/test check ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
af9d77041f74a8cf6ce5061bbbd84892681c73ed
link
/test test ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
af9d77041f74a8cf6ce5061bbbd84892681c73ed
link
/test build ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

test_ibm-monitoring-grafana-operator
af9d77041f74a8cf6ce5061bbbd84892681c73ed
link
/test test ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
af9d77041f74a8cf6ce5061bbbd84892681c73ed
link
/test build ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
af9d77041f74a8cf6ce5061bbbd84892681c73ed
link
/test check ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

test_ibm-monitoring-grafana-operator
af9d77041f74a8cf6ce5061bbbd84892681c73ed
link
/test test ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
af9d77041f74a8cf6ce5061bbbd84892681c73ed
link
/test build ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
909ae034443ef227501160a7614bb1abf0ea06c4
link
/test check ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

build_ibm-monitoring-grafana-operator
af9d77041f74a8cf6ce5061bbbd84892681c73ed
link
/test build ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
909ae034443ef227501160a7614bb1abf0ea06c4
link
/test check ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
909ae034443ef227501160a7614bb1abf0ea06c4
link
/test test ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

check_ibm-monitoring-grafana-operator
909ae034443ef227501160a7614bb1abf0ea06c4
link
/test check ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
909ae034443ef227501160a7614bb1abf0ea06c4
link
/test test ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
909ae034443ef227501160a7614bb1abf0ea06c4
link
/test build ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

check_ibm-monitoring-grafana-operator
909ae034443ef227501160a7614bb1abf0ea06c4
link
/test check ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
909ae034443ef227501160a7614bb1abf0ea06c4
link
/test build ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
dbc824d0bb069ca45b91383a7b9be848f9056cb7
link
/test test ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

build_ibm-monitoring-grafana-operator
909ae034443ef227501160a7614bb1abf0ea06c4
link
/test build ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
dbc824d0bb069ca45b91383a7b9be848f9056cb7
link
/test test ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
dbc824d0bb069ca45b91383a7b9be848f9056cb7
link
/test check ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

test_ibm-monitoring-grafana-operator
dbc824d0bb069ca45b91383a7b9be848f9056cb7
link
/test test ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
dbc824d0bb069ca45b91383a7b9be848f9056cb7
link
/test check ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
dbc824d0bb069ca45b91383a7b9be848f9056cb7
link
/test build ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

test_ibm-monitoring-grafana-operator
dbc824d0bb069ca45b91383a7b9be848f9056cb7
link
/test test ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
dbc824d0bb069ca45b91383a7b9be848f9056cb7
link
/test build ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
1205cb9d69a883a6660506cfcd3223ee9f8c8881
link
/test check ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

test_ibm-monitoring-grafana-operator
dbc824d0bb069ca45b91383a7b9be848f9056cb7
link
/test test ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
1205cb9d69a883a6660506cfcd3223ee9f8c8881
link
/test check ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
1205cb9d69a883a6660506cfcd3223ee9f8c8881
link
/test build ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

build_ibm-monitoring-grafana-operator
f2db67ff6888268f6aa702236a95b5bdf02ae582
link
/test build ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
f2db67ff6888268f6aa702236a95b5bdf02ae582
link
/test check ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
f2db67ff6888268f6aa702236a95b5bdf02ae582
link
/test test ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

build_ibm-monitoring-grafana-operator
f2db67ff6888268f6aa702236a95b5bdf02ae582
link
/test build ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
f2db67ff6888268f6aa702236a95b5bdf02ae582
link
/test check ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
241d0ea0c601a4705bd5befc560a4274db86d472
link
/test test ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

build_ibm-monitoring-grafana-operator
f2db67ff6888268f6aa702236a95b5bdf02ae582
link
/test build ibm-monitoring-grafana-operator

test_ibm-monitoring-grafana-operator
241d0ea0c601a4705bd5befc560a4274db86d472
link
/test test ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
241d0ea0c601a4705bd5befc560a4274db86d472
link
/test check ibm-monitoring-grafana-operator

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.

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

Test name
Commit
Details
Rerun command

test_ibm-monitoring-grafana-operator
241d0ea0c601a4705bd5befc560a4274db86d472
link
/test test ibm-monitoring-grafana-operator

check_ibm-monitoring-grafana-operator
241d0ea0c601a4705bd5befc560a4274db86d472
link
/test check ibm-monitoring-grafana-operator

build_ibm-monitoring-grafana-operator
241d0ea0c601a4705bd5befc560a4274db86d472
link
/test build ibm-monitoring-grafana-operator

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.


feat: expand footer

Description

Footer decorate more in line with gnav decorate
Footer design more in line with expanded consonant footer

Screenshots & Links:
https://footer-expand--business-website--adobe.hlx3.page/blog/

and I know this will need to be moved into blog proper as well, @kptdobe.


Collapse all the codestyle checks into one script run.

This patch collapses all the maven invocations into one script run,
and removes all superfluous invocations to clean.

Changes Unknown when pulling 119ee11145a9da9941bbe819e738857666570bd2 on feature/collapse_mvn_checks into ** on develop**.


merge package template from arlac77/npm-package-template

package.json

chore(engines): update<EMAIL_ADDRESS>from template

.travis.yml

chore(travis): remove node versions 8.10
chore(travis): add node versions 8.11

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Wrap long breadcrumb trails

When breadcrumbs trails become too long, they should wrap to the next line rather than extending beyond the page.
The current implementation works correctly in FF, but not Chrome.
Example: http://imgur.com/a/uDL9n#MY4Mz
I'm using breadcrumbs inside a dialog window.

Merged into 2.0.1-wip. Thanks!


Breaking change between 2.2.3.RELEASE and 2.2.4.RELEASE+

Describe the bug
There seems to be a breaking change when upgrading from 2.2.3.RELEASE to the latest GA version (2.2.5.RELEASE). Actually, upgrading to 2.2.4.RELEASE is broken too.
The issue is in generated client's URLs. A very basic client like this:
@FeignClient(name = "client", url = "http://localhost:8585", path = "/path")
interface Client {
    @RequestMapping("/") // note this slash here
    fun call(@RequestParam(name = "param") param: String): String
}

is sending requests to http://localhost:8585/path?param=… when using 2.2.3.RELEASE, but in 2.2.4.RELEASE and later the URL is different: http://localhost:8585/path/?param=…. Note that extra slash after path in the second scenario.
Although, such trailing slashes seems to be ignored by most server applications, like the ones authored with Spring Boot, probably not all APIs or servers are so tolerant. The MWE below demonstrates the consequence of such intolerance in WireMock. Some companies are using WireMock for functional, integration and contract testing. Contract tests are just "dumb" stubs / mocks and they expect the exact URL, so upgrading from 2.2.3.RELEASE breaks them.
I guess, the issue was introduced by this commit: https://github.com/spring-cloud/spring-cloud-openfeign/commit/14929cbfee02580a8b0684bb665b7b335f957aa6.
Sample
Please, find the full source code of the minimal working example here: madhead/spring-cloud-openfeign-mwe. Try changing the version of spring-cloud-starter-openfeign in its build.gradle.kts. The test will pass with 2.2.3.RELEASE, but fail with 2.2.4.RELEASE. 2.2.5.RELEASE (latest GA version as of publishing this issue) is affected as well.

Hi @madhead That was just a revert of a commit that introduced a bug while adding a rarely used feature, but let me have a look at it now.

Ok, that indeed, happens. Will fix it.

Have gone through the issue history and the actual situation is that removing the slash was causing this issue. Both urls with and without the trailing slash are permitted as per Uniform Resource Identifier (URI): Generic Syntax, so we should allow the users to decide on whether to add it (by adding @RequestMapping("/")) or not (by just annotating with @RequestMapping, without any arguments, instead).
I recognise that it's a bad situation that there's a breaking change, however, it only affects tests and it is a fix for a breaking change that introduced actual issues, for example, in libraries built on top of this one.

Ok, I understand.


Fix up Github star sync plugin and add to repository

Probably should be cleaned/tested first.
We should increase limits and fetch more data when using an API key
Last time I ran it to get posthog stars, the number didn't match somehow. Not sure why

This is a very nice plugin to use for e.g. open source developers who want to track their projects, and a nice showcase plugin, so it'd be great to get in.
Also missing:

console logs to show status if new stars are added.
support multiple projects

+1 to get this over the line from a customer. CC @yakkomajuri


Modify "genericclioptions.NewContext" to return context based on configuration of experimental mode

Instead of checking for experimental mode and requesting a devfile context at different places in the code, wouldn't it make more sense to put that logic in NewContext so that the same logic doesn't need to be implemented everywhere?
Originally posted by @metacosm in https://github.com/openshift/odo/pull/3069
/kind code-refactoring

@dharmit @metacosm I think my PR https://github.com/openshift/odo/pull/2981 should handle this 🙂

Closing this in favour of #4081

/close


Better hover coloring for inventory

About the PR

Used to only hover if you could wear the item in that slot. This felt really weird for storage and stuff so now it properly takes those into account
Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

no cl no fun

best pr

#11164 related?


[Deployment] Check duplicate hostname

Check duplicate hostname in kubernetes configuration.
Closes #2377.

Coverage increased (+0.01%) to 52.659% when pulling 0e19fc71720794097138fdfc44d63e6653adcb97 on xiongyf/deployment-check-hostname into 1e0c14204b4abba584cfbc4c18e7327c48eb3a9f on master.


Spanish translation

Description
I would like to actively help on the spanish translation for the website if there is a need for it, i have seen that there is a lot of information not translated and having it in spanish would be very helpful for a lot of people that their first language is spanish or self-learners of the CS community
If yes, i would open a new branch so there is no conflicts and progressively start/work on it on my free time

Thank you for your offer to help out, your work would be greatly appreciated!
We use a platform called Crowdin for our translations. The CSFG Project is public so anyone is free to contribute. The translation page of our documentation goes into more detail about Crowdin, the translation pipeline, and some specific notes about translating Field Guide content.
Apologies for the inconvenience but, as we have formalised the translation pipeline, we ask that you please use Crowdin rather than opening a new branch.
Thanks again for your offer to contribute, please add any comments/questions you may have about it to this issue.

Although it is closed, please feel free to comment on this issue with questions

I'm sorry for answering late, sure i will be working on it on my free tiem then, thanks