Fix TableServiceClient.AccountName throwing exception when connecting to Azure Storage Emulator with shortcut

All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[x] Title of the pull request 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 more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

@christothes We are migrating from Microsoft.Azure.Cosmos.Table to this new SDK, and this bug is currently blocking us. Could you review this PR and give me a rough estimation of the time of next release?

@christothes We are migrating from Microsoft.Azure.Cosmos.Table to this new SDK, and this bug is currently blocking us. Could you review this PR and give me a rough estimation of the time of next release?

This should be released the 2nd week of August. But you can grab it from our dev feed tomorrow, if that is too long to wait. Here is today's build, for example.


Switch to sdl2gdx instead Jamepad

Since Jamepad as a direct wrapper of SDL is not maintained any more and is now just a wrapper for sdl2gdx, there's the need to switch over to use sdl2gdx internally in the future.
Why not just use sdl2gdx alone? Because it does not implement AdvancedController interface, but is designed for desktop use only. Thus all extended features won't work on cross-platform projects.
Problem: sdl2gdx is not just a wrapper for SDL, but also comes with the hacks we used here to replace libgdx own controller implementations. That means, just pulling in sdl2gdx will not work because of dublicate classes. Ways to solve this:

jar jar links, which can be also used to strip the unneeded stuff
own fork of the project (best was id GitHub Actions could be used to build the natives) without the unneeded stuff
own fork of the project, changed to implement AdvancedController interface

Switched to own fork of Jamepad. sdl2gdx was not used because of its LGPL license.


handle asdot format and AS env variable

Reopened https://github.com/projectcalico/calico-bgp-daemon/pull/7 as a new PR.
Reflected @gunjan5's comments.
PTAL

Hi, rebased on the master branch.
Does this have any chance to get merged?

@ishidawataru added some comments in the review. Apologize for the delay!

@gunjan5 No worries. Thanks for your review. Reflected your comments. PTAL.

@ishidawataru one last comment then squash it

@gunjan5 Fixed. If this seems fine, I'll squash them.

Done!

@ishidawataru thanks for your contributions! :)


Replace RGBA colors with solid colors

Replacing RGBA colors with solid colors to make sure colors are eligible in every scenario. This update should not break anything unless -rgb colors are used directly in local projects.
Updated components (colors + some cleanup):

InfoBlock
StatusBar
Tag
Tooltip

Preview is available here:http://design-system-pr74.previews.kube001.services.stellar-ops.com/


Dialout and Adding participants working through Direct Routing SBC

[Enter feedback here]
"When dialing out, the Microsoft Audio Conferencing service places the call using online calling capabilities, which requires proper licensing. (Note that dialing out does not route through Direct Routing.) For more information, see Online Meetings with Teams."
"Important : In the case that you would like to add external participants to scheduled meetings, either by dialing out to them or by providing the dial-in number, the audio conferencing license is required. "
Based on the Tests we noticed - DialOut to phone number and the adding a PSTN participants to the existing meeting is connecting via Direct Routing SBC with out Dialin Conferencing license.
Is this an issue ?

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

ID: e26faf8c-529e-b317-5934-cd41cfe8fa24
Version Independent ID: 3ddd5d0a-6dbb-4940-1814-8346e293701b
Content: Plan Direct Routing - Microsoft Teams
Content Source: Teams/direct-routing-plan.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

@dipinn26592 thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


dnf5: 5.1.7 -> 5.1.8, re-enable tests, add man pages

Description of changes
Release notes
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

[ ] 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/)
23.11 Release Notes (or backporting 23.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.

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

Result of nixpkgs-review pr 269512 run on x86_64-linux 1

2 packages built:

dnf5
dnf5.man


[feature] Add DropdownButton2FormField

Please add DropdownButton2FormField which is similar to DropdownButtonFormField as your package substitutes the DropdownButton.

Hello! DropdownButtonFormField2 is already there :)


Popup when hovering or clicking a symbol

Hi,
Thanks for this plugin! I am still very new to this (maplibre) and not a developer so please bear with me :) I was wondering if it would be possible to display an infobox when clicking on a symbol?
I tried to use this example to no avail:
https://maplibre.org/maplibre-gl-js-docs/example/popup-on-hover/
Is it at all possible?
Kind regards

Hello,
For clicking you can use the onLeafClick option but let me know if your having any issues. I didn't add an onLeafHover option but this does sound useful so I will add it soon.
const popup = new maplibregl.Popup({
  closeButton: false,
  closeOnClick: false
});

const spiderfy = new Spiderfy(map, {
  onLeafClick: (f) => {
    // set your popup (clicked feature data is inside `f` object)
    const coordinates = f.geometry.coordinates.slice();
    const description = f.properties.description;
    popup.setLngLat(coordinates).setHTML(description).addTo(map);
  },
   ...
})

Note: You probably want to put closeOnLeafClick option to false if you want to be able to click on the leaves without them disappearing. But this means you have to make your own closing logic by manually closing them using spiderfy.unspiderfyAll()

Wonderful! I will give it a try. And indeed, it would be cool if you could add it too. Thanks so much.

Just added the onLeafHover option. Thanks for the feedback!


BoundTreeView on Wisej: create manual sample to investigate differences to WinForms.

BoundTreeView on Wisej: create manual sample to investigate differences to WinForms.

All issues solved or dependent on Wisej.


More issue fixes

Fixes #218
Fixes #219

Two small comments, other than that looks fine

Looks good.


m64p: persisting config data

mupen64plus was recently added to the bucket but there seems to be a problem as the "mupen64plus-gui.ini" file does not affect the program, i.e. running the program and looking under "Settings > Plugin and Path Selection" shows that "Config Dir Path" is set to $CONFIG_PATH$ despite "mupen64plus-gui.ini" defining it as $APP_PATH$/config.
In this state, "input-profiles.ini", "input-settings.ini", and "mupen64plus.cfg" are saved to "%appdata%\Mupen64Plus" instead of the "config" dir in the program's directory (a directory which "m64p.json" persists).
I have seen that after installing m64p via Scoop, a note message appears saying "Configuration files cannot be persisted, but will be retained during the update", however it should be possible to do:
The "configDirPath" value is stored in the registry (HKEY_CURRENT_USER\Software\mupen64plus\gui) and it to reads $CONFIG_PATH$. Changing this value to $APP_PATH$/config causes the mentioned ini/cfg files to be stored in the persisted "config" dir. Therefore, if the manifest also set this registry value via post_install ("zoom.json" has an example) the configuration files would persist.
Setting the registry value may actually just be a workaround if it turns out that the problem is instead m64p not honouring the "mupen64plus-gui.ini" values.
manifest author: @satorope
m64p dev: @loganmc10

As you say, m64p stores the value of configDirPath in the registry, not in mupen64plus-gui.ini
mupen64plus-gui uses Qt, and it is using QSettings to store this data (https://github.com/m64p/mupen64plus-gui/blob/9cdadb37ab67d1b3bad615312fc792433f324c8c/mainwindow.cpp#L331)
QSettings uses the registry by default on Windows, and ~/.config/mupen64plus on Linux.
Past versions sorted the settings in mupen64plus-gui.ini, which was located in the same folder as mupen64plus-gui. However, the installation directory (where mupen64plus-gui.exe resides) is not always writeable, so it was changed to use the registry in order to make sure the location was always writeable

To my knowledge, Scoop doesn't attempt to backup/save program settings which store to the registry, making persisting such settings not possible. An indirect solution could be to allow m64p to either store its Qt settings to the registry, or as before to "mupen64plus-gui.ini" in the case where the file is present in the program's directory (I assume it's the same format as the Linux file and so may not be too much work to reimplement). This way the program's settings, as well as its Qt settings, would be portable if desired, and too, fix this issue. Alternatively, we could write the "configDirPath" value to the registry as mentioned previously. Which approach depends on @loganmc10's answer I suppose.

I fixed the issue: https://github.com/loganmc10/m64p/commit/4ca0517ceef643dbd8860428d7e436b5b5e16d27
It will attempt to write mupen64plus-gui.ini, and if it is not writeable, it will fall back to using the registry. That change will make it in to the next version of m64p, but I don't have a date for that yet

Great! I assume the Windows version will also attempt to read the ini on program launch if the file is present?

If it's in the same directory as the EXE, yes

Perfect. Thanks @loganmc10!
Assuming the fix works, this issue can be closed once a m64p version greater than "2021.12.29" is released.

@redactedscribe close


Consider not using LCS by default or allow switching it off

Hi,
Hashdiff uses LCS by default when comparing arrays. This algorithm produces a friendlier and easier to read diff for humans, but at high cost O(n2).
Would you consider a patch to either disable LCS or perhaps to allow switching it off via the command line? I'd happy to prepare it.
Thanks.

@nbarrientos Yes, I think an option to toggle LCS (on by default) would be reasonable. I'll be happy to review such a PR! :smile:


TestPutAndDeleteAndLoadJobs failed under github CI environment

Can be reproduced ?
Steps:
Expected behavior:
Actual behavior:
Environment:

Version or commit-id (e.g. v0.1.0 or 8b23a93):
Hardware parameters: Under github CI environment
OS type:
Others:

Configuration file:
Additional context:

Error message from client:
Server log:
Other information: github CI log

In TestPutAndDeleteAndLoadJobs, the test was sleeping for 200ms in order to wait for leadership election.
But the hard-coded 200ms wasn't suitable for CI environment which maybe overloaded.
I would have to change the waiting manner.
By the way, hard-coded 200ms isn't always that applicable.


Correct spelling mistake

This commit correct spelling mistake in amazon-ssm-agent_3.2.582.0.bb. The word "enabsle" was corrected to "enable".

/run

thank you!


Profile HeatMap not updating correctly

I don't know if this is an issue or not. This is the first time I'm posting here. The heat map in our public portfolio does not update to the current day/month.

Steps to Reproduce
Make sure to set your profile heatmap to public.

Go to https://www.freecodecamp.org/yourusername
Scroll down to view the heat map.

Browser and operating system

Browser Name: Google Chrome
Browser Version: Version 67.0.3396.87 (Official Build) (64-bit)
Operating System: macOS High Sierra - version 10.13.1

Screenshot

Right now, it is the month of July, and I have been working on the lessons for the past 2-3 weeks, it does not appear in the heatmap.
If this is an actual issue, I'm willing to take this up. I'm still a beginner, but I am sort of confident and willing to give this a try, if that's okay.
Many Thanks,
Lourdes

I am also having this issue, however my heat map has never worked since I began two weeks ago...

Same issue. I'll be sure to post back if I find anything.

same issue-today

Same issue (using Chrome ver. 63.0.3239.132)

Same issue.  Streak count is accurate, but not showing in the heat map.

Same issue. Streak count is accurate, but not showing in the heat map.
Same issue for me too with my heat map...

Same issue with my "Heat Map", and my "Timeline" sometimes does not appear on the profile page.
Browser and operating system
Browser Name: Google Chrome
Browser Version: Version 70.0.3538.102 (Official Build) (64-bit)
Operating System: macOS Mojave - version 10.14.1

Does anyone know which timezone is used by the streak counter and the heatmap? I just lost a 74 day streak even though I finished a challenge by 15:45PM KST (UTC +0900). The streak shows only 1 day but today's square on the heatmap is colored green, and on the timeline the challenge is recorded as being completed today as well. It seems like the streak counter is using one timezone, while the heatmap and timeline are using a second timezone. Can someone please confirm? It's really demoralizing as I was taking pride in watching the number grow every day and being able to share it with friends, family, and potential employers.
I understand that it may not be a high priority to fix, so at least knowing the rules of the streak would really help me understand and adjust my coding accordingly.
Screenshots: https://imgur.com/a/c47JNv9
Quoted from https://github.com/freeCodeCamp/freeCodeCamp/issues/7925#issuecomment-361716788

I observed how challenges are recorded during the last week and basically saw challenge dates and streak are going by UTC and the heatmap is using EST...

Mine is getting cut off. Today is December 11. It didn't get cut off like this yesterday, or ever in the past that I've noticed.

Mine is getting cut off. Today is December 11. It didn't get cut off like this yesterday, or ever in the past that I've noticed.

At least something is showing up on your heat map, It's been six months since I've seen anything on my heat map... kinda gets discouraging when you can't see your progress at all...

I have no heat on the heat map.
And I Started From June 16th 2018.
My Recent Was On 30th January 2019 but no heat on entire Heat Map.

No Heat On My Profile's Heat Map
https://www.freecodecamp.org/shahayush
I Solved 21Challenges on 30th of January 2019 but there is no heat on heat map.

@raisedadead Any thoughts on this?

@raisedadead Any thoughts on this?

any progress?

@ayushshah2120 Currently we are in the middle of testing a beta site which will hopefully moved to production in the near future, so it could be a while before we have time to work on this issue.

@ayushshah2120 Currently we are in the middle of testing a beta site which will hopefully moved to production in the near future, so it could be a while before we have time to work on this issue.

No Problem Sir. Thank You!

Hi everyone!
Sorry about the delay in getting back on this. Thanks for your patience.
We have had some work go in into this issue a few months back. So this issue is probably fixed or behaving better on the beta, it needs to be tested there.
That does mean that, @RandellDawson you are right, it's going to be a while before we can land the fix in production.
The fastest way to test this would be to copy the data of an affected user from the production (with their permission) and seed it over on the beta site and see the newer heatmap's behaviour.
If it all looks good we could add that as tests.
Action items for anyone interested in overseeing this issue is:

Find a user who has this issue on the production and seek their permission to use their data on the beta.
Once permitted, notify me (@raisedadead) or @bouncey to copy over the user's data.
Confirm the fix, or add more changes as per further investigation.

We definitely want to resolve this issue, which has been bugging us for a really long time now.

Hi everyone!
Sorry about the delay in getting back on this. Thanks for your patience.
We have had some work go in into this issue a few months back. So this issue is probably fixed or behaving better on the beta, it needs to be tested there.
That does mean that, @RandellDawson you are right, it's going to be a while before we can land the fix in production.
The fastest way to test this would be to copy the data of an affected user from the production (with their permission) and seed it over on the beta site and see the newer heatmap's behaviour.
If it all looks good we could add that as tests.
Action items for anyone interested in overseeing this issue is:

Find a user who has this issue on the production and seek their permission to use their data on the beta.
Once permitted, notify me (@raisedadead) or @Bouncey to copy over the user's data.
Confirm the fix, or add more changes as per further investigation.

We definitely want to resolve this issue, which has been bugging us for a really long time now.

It's Okay If You Use my Profile or My Data to work on your issue.

@raisedadead, @Bouncey You have a user now.

is this case is still on going? It happened to me as well but might be with different cause.
I reset my account progress then when restarting there's no heat map progress, though just like others the strike count is working normally.
thank you guys who's working on this, appreciate it very much!

is this case is still on going? It happened to me as well but might be with different cause.
I reset my account progress then when restarting there's no heat map progress, though just like others the strike count is working normally.
thank you guys who's working on this, appreciate it very much!

Actually, I also reset my account a while back and there's no heat map progress and strike counting is normal

This should be resolved on master I think.

what do i do to solve the heatmap with no progress(past and current)?

I just started getting this yesterday (5 November 2019).  My contribution heat map does not reflect my checkins for today.
Here's my heat map showing no check-ins for today

Here's my file where I modified a simple comment just to check heatmap functionality - checked in minutes earlier.

@MalcolmAnderson You would need to contact GitHub for GitHub specific problems.

Thanks Randell.  I have done that.


[Feature]: reverseKeyValue when object has multiple value.

Package Scope

[x] Add to an existing package
[ ] New package

Package name: @toss/utils reverseKeyValue
Overview

below is always correct
expect(reverseKeyValue({ jbee: 'eebj' })).toEqual({ eebj: 'jbee' });

but how about this object which is multiple same value
reverseKeyValue({ jbee: 'eebj',jbee2:'eebj' }) // { "eebj": "jbee2"}

It is not bug,, but people can make human error I think
Describe the solution you'd like

Why don't we put the same values together in an array?
reverseKeyValue({ jbee: 'eebj',jbee2:'eebj' }) // { "eebj": ["jbee","jbee2"]}

Additional context
In the case above, please suggest if it can be handled in another good way👍

안녕하세요 기여를 해보려고 구조를 파악중입니다.
질문이 있어요. 해당 파일의 유닛 테스트는 어떻게 해야할까요?
yarn workspace @toss/utils test:unit 명령어를 쓰니 아무런 반응이 없습니다. 혹시 제가 잘못 사용하고 있는지 궁금합니다.

Thank you for your interest.
I am also Korean, but since the rules of this repository are to communicate in English, I will follow the rules and answer them in English.
Did you install the appropriate package through yarn install?
I run the command you showed me(yarn workspace @toss/utils test:unit), and the test works normally. (From the root path of the project)
https://github.com/toss/slash/assets/69495129/6f2bf8a7-ebd5-475e-936d-7f67504112f7

Thank you for your response and providing the information. Although the exact cause is unknown, it seems that the issue was resolved after upgrading Yarn.
Congratulations on submitting your first open-source PR! I have reviewed your PR at https://github.com/toss/slash/pull/250. I will provide feedback and suggestions for improvement promptly.

Thank you for your response. I appreciate it.
After upgrading yarn and reconfiguring it with yarn berry, the issue has been resolved.
I have submitted my first open source PR. You can find it here: https://github.com/toss/slash/pull/250
I would greatly appreciate any feedback you can provide, and I will make the necessary revisions accordingly.

I agree with this https://github.com/toss/slash/pull/284#discussion_r1253089937

@wooki-kim
I've seen the code of your PR and it works well, but I don't think it's appropriate for the way javascript object works, what do you think? If you agree, I will close this issue

thanks for involving this issue
@wooki-kim @minsoo-web


Ux improve

Not optimized yet.
Solve the issue of asynchronous updating the database.
Future improvement:
Write new Neo4J query with UNWIND features


Add Asterisk Call Data Record to mailboxes component

Description:
This adds the ability to see the call-history from Asterisk as a mailbox component.  There is an associated frontend change as well to allow viewing each mailbox component on its own tab.
The frontend pull request is here: https://github.com/home-assistant/home-assistant-polymer/pull/719
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#4173
Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[x] New dependencies are only imported inside functions that use them ([example][ex-import]).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

I still struggle with the sync/async usage.
Here is what I'm trying to do:
AsteriskData.handle_data() is called by an independent thread from the asterisk_mbox module.  It should send signals to handle data (I believe these should be sent with dispatcher_send since they come from outside the event-loop).
The signals should be picked up from inside the event-loop and processed there.  My understanding is that these signal handlers (_request_messages, _request_cdr and _discover_platform) are executed asynchronously, and so should use async_* functions internally.
I am not sure when the @callback decorator is appropriate or not.  The handle_data function is a callback handler, but is only called from an external thread and not within the event-loop.  Should it have the decorator?  The _request_* and _discover_platform functions are called by the signal handler within the event-loop. Should these have the decorator?

Address comments and look how I do change the code and reopen after all is addressed


SelectableArea error in web html render Error: setState() called after dispose():

Use case
#error video
https://user-images.githubusercontent.com/16702158/225249332-e67ed649-a3a2-47b2-bb95-815a393993fc.mov
Test Code
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',

      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key? key, required this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {

  ScrollController scrollController = ScrollController();
  List<Widget> list = [];

  @override
  void initState() {
    super.initState();

    for(int i = 0; i < 10; i++) {
      list.addAll([
        SelectionArea(
          child: Container(
            color: Colors.grey,
            height: 300,
            child: Text("123213213123123123123123123123123"),
          ),
        ),
        SelectionArea(
          child: Container(
            color: Colors.green,
            height: 300,
            child: Text("123213213123123123123123123123123"),
          ),
        ),
        SelectionArea(
          child: Container(
            color: Colors.lightBlueAccent,
            height: 300,
            child: Text("123213213123123123123123123123123"),
          ),
        ),
        SelectionArea(
          child: Container(
            color: Colors.orange,
            height: 300,
            child: Text("123213213123123123123123123123123"),
          ),
        ),
        SelectionArea(
          child: Container(
            color: Colors.grey,
            height: 300,
            child: Text("123213213123123123123123123123123"),
          ),
        ),
        SelectionArea(
          child: Container(
            color: Colors.green,
            height: 300,
            child: Text("123213213123123123123123123123123"),
          ),
        ),
        SelectionArea(
          child: Container(
            color: Colors.lightBlueAccent,
            height: 300,
            child: Text("123213213123123123123123123123123"),
          ),
        ),
        SelectionArea(
          child: Container(
            color: Colors.orange,
            height: 300,
            child: Text("123213213123123123123123123123123"),
          ),
        ),
        SelectionArea(
          child: Container(
            color: Colors.grey,
            height: 300,
            child: Text("123213213123123123123123123123123"),
          ),
        ),
        SelectionArea(
          child: Container(
            color: Colors.green,
            height: 300,
            child: Text("123213213123123123123123123123123"),
          ),
        ),
        SelectionArea(
          child: Container(
            color: Colors.lightBlueAccent,
            height: 300,
            child: Text("123213213123123123123123123123123"),
          ),
        )
      ]);
    }
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Column(
        mainAxisAlignment: MainAxisAlignment.center,
        children: [
          Expanded(
            child: Container(
              margin: const EdgeInsets.symmetric(horizontal: 10),
              child: ListView(
                controller: scrollController,
                reverse: true,
                children: list,
              ),
            ),
          )
        ],
      ),

      bottomSheet: GestureDetector(
        onTap: () {
          scrollController.animateTo(0, duration: const Duration(milliseconds: 300), curve: Curves.linear);
        },
        child: Container(
          width: 50,
          height: 50,
          color: Colors.orange,
        ),
      ),
    );
  }
}

flutter doctor

Doctor summary (to see all details, run flutter doctor -v):
[!] Flutter (Channel stable, 3.7.0, on macOS 12.6.3 21G419 darwin-x64, locale ko-KR)
! Warning: dart on your path resolves to /usr/local/Cellar/dart/2.17.0/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/toby/Desktop/flutter. Consider adding /Users/toby/Desktop/flutter/bin to the front of your path.
[!] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
✗ cmdline-tools component is missing
Run path/to/sdkmanager --install "cmdline-tools;latest"
See https://developer.android.com/studio/command-line for more details.
✗ Android license status unknown.
Run flutter doctor --android-licenses to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[!] Android Studio
✗ Unable to find bundled Java version.
[✓] IntelliJ IDEA Ultimate Edition (version 2021.3.2)
[✓] VS Code (version 1.76.1)
[✓] Connected device (2 available)
[✓] HTTP Host Availability
! Doctor found issues in 3 categories.

Hello @kokihoon. I cannot reproduce this issue with the latest stable and master versions. Can you try in master or the latest stable and check if you can still reproduce this issue?

i tested flutter version 3.7.7 same issue

I have tried running this on both Windows Chrome and MacOS chrome and I am unable to reproduce it. Can you try adding --web-renderer=html and --web-renderer=canvaskit and see if it reproduces with one or both?

i tried same issue all --web-renderer=canvaskit, --web-renderer=html
could you upload test video?

I'm not sure what you mean about a test video? I tried scrolling right to the bottom of the screen, then right to the top and back and still could not reproduce the error

Can I check the video you tested?

can i check the video you tested??

As you can see, I do not get any errors. Are you running this code in a newly generated project with 3.7.7?
https://user-images.githubusercontent.com/50555895/226262565-380e646f-42e5-457a-b9f4-00d8f30e34c1.mp4

on the lower left orange button. Try pressing it.
ex) scrollcontroller.animateTo(0...);


Out of sync toggle buttons

When starting Clef, it takes a few seconds after I click on the toggle, before it starts (why?). If during this time I click a second time, a second Clef is started (which fails with a port clash error). The second Clef dying, Grid untoggles the button, but one version is still running (logs are still coming). I have to kill all processes from the console before I can geth Grid back into a consistent state.

Haven't dug into the startup delay yet, but the category of double-click bugs should be addressed in the next release by a couple freshly merged commits (https://github.com/ethereum/grid/commit/a428cc19962ee64081aa11bb54e42f0de7a5601a, https://github.com/ethereum/grid-ui/commit/8b87612c01085dea5dc2e8e5fccd2648f3a14ac7). tl;dr - once clicked, buttons are disabled until they shouldn't be.


documentation: Why Use Ortelius

Under Agentless Delivery:
"Ubantu, Redhat, SuSe, Debina" should be "Ubuntu, Redhat, SuSe, Debian"

Fork the ortelius/ortelius-docs repo, install hugo and the markdown plugins for VS Code and you should be set to start making changes.  See setup-for-documenation-updates


HDFS-15383. RBF: Add support for router delegation token without watch

Summary:
This patch is targeting improving router's performance
for delegation tokens related operations.
It achieves the goal by removing watchers from router on
tokens since based on our experience. The huge number of
watches inside Zookeeper is degrading Zookeeper's performance
pretty hard. The current limit is about 1.2-1.5 million.
Specific changes:

Explicitly disable the watcher to tokens by not using
PathChildrenCache or any curator provided cache at all.
Schedule a sync task between router and Zookeeper at
a configurable interval to make routers sync with their
token information through Zookeeper.
For token's change, always make sure to change local cache
first instead of depending on callbacks of the watch event
when using PathChildrenCache.
The above three points are trying to make router token cache
behaves as close as possible to the case when the PathChildrenCache
is used. The below point handles one corner case.
Before token remover(a background thread) removes token from
Zookeeper, one router will first make sure this token hasn't
been renewed by other peers. This happens only when somehow the
sync failed for this token that router local cache doesn't have
the corret renewal date (expiry date)

Test Plan:

Add several unit tests covering all common use cases.
Deployed on two machines and performing all tests.
Pressure testing: create production scale number of tokens (100k)
and monitor the sync latency.

NOTICE
Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)
For more details, please see https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 27s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
0m 33s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
25m 31s
trunk passed

+1 :green_heart:
compile
23m  7s
trunk passed

+1 :green_heart:
checkstyle
3m 10s
trunk passed

+1 :green_heart:
mvnsite
2m 32s
trunk passed

+1 :green_heart:
shadedclient
24m  8s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m 50s
trunk passed

+0 :ok:
spotbugs
1m 31s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
4m  2s
trunk passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 25s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 36s
the patch passed

+1 :green_heart:
compile
22m 19s
the patch passed

+1 :green_heart:
javac
22m 19s
the patch passed

-0 :warning:
checkstyle
3m 11s
root: The patch generated 7 new + 80 unchanged - 0 fixed = 87 total (was 80)

+1 :green_heart:
mvnsite
2m 24s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
15m 57s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
1m 34s
the patch passed

+1 :green_heart:
findbugs
3m 41s
the patch passed

_ Other Tests _

-1 :x:
unit
9m 13s
hadoop-common in the patch passed.

+1 :green_heart:
unit
9m 52s
hadoop-hdfs-rbf in the patch passed.

-1 :x:
asflicense
0m 46s
The patch generated 1 ASF License warnings.

155m 24s

Reason
Tests

Failed junit tests
hadoop.security.TestRaceWhenRelogin

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2047

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 75faf044bd19 4.15.0-91-generic #92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 6288e15118f

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/1/artifact/out/diff-checkstyle-root.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/1/artifact/out/patch-unit-hadoop-common-project_hadoop-common.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/1/testReport/

asflicense
https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/1/artifact/out/patch-asflicense-problems.txt

Max. process+thread count
3232 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs-rbf U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/1/console

versions
git=2.17.1 maven=3.6.0 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

hi~ @fengnanli  Are you still here? I think it's a good work and I hope to see it's done.
Or someone can take over this work, e.g me?

@Cosss7 Thanks for pinging me. I was busy with some other stuff and will start addressing comments soon.

@fengnanli Very brilliant work. Expect work to be done. :heart:

Thanks for the review @Hexiaoqiao ! Have you tested it on your setup?
@goiri Do you mind reviewing this change? Thanks very much!

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
25m 34s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
1m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
21m 58s
trunk passed

+1 :green_heart:
compile
20m 54s
trunk passed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04

+1 :green_heart:
compile
18m  1s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
checkstyle
2m 51s
trunk passed

+1 :green_heart:
mvnsite
2m  5s
trunk passed

+1 :green_heart:
shadedclient
20m 45s
branch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 37s
hadoop-common in trunk failed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04.

-1 :x:
javadoc
0m 33s
hadoop-hdfs-rbf in trunk failed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04.

+1 :green_heart:
javadoc
1m 31s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+0 :ok:
spotbugs
1m 18s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 23s
trunk passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 21s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 22s
the patch passed

+1 :green_heart:
compile
20m 19s
the patch passed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04

+1 :green_heart:
javac
20m 19s
the patch passed

+1 :green_heart:
compile
17m 42s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
javac
17m 42s
the patch passed

-0 :warning:
checkstyle
2m 52s
root: The patch generated 9 new + 80 unchanged - 0 fixed = 89 total (was 80)

+1 :green_heart:
mvnsite
2m 24s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
17m 43s
patch has no errors when building and testing our client artifacts.

-1 :x:
javadoc
0m 36s
hadoop-common in the patch failed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04.

-1 :x:
javadoc
0m 32s
hadoop-hdfs-rbf in the patch failed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04.

+1 :green_heart:
javadoc
1m 33s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
findbugs
3m 50s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
9m 49s
hadoop-common in the patch passed.

-1 :x:
unit
10m  6s
hadoop-hdfs-rbf in the patch passed.

+1 :green_heart:
asflicense
0m 49s
The patch does not generate ASF License warnings.

209m  3s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.federation.store.TestStateStoreMembershipState

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2047

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 7885b472a04f 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 9821b94c946

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_252-8u252-b09-1~18.04-b09

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/2/artifact/out/branch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/2/artifact/out/branch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04.txt

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/2/artifact/out/diff-checkstyle-root.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/2/artifact/out/patch-javadoc-hadoop-common-project_hadoop-common-jdkUbuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04.txt

javadoc
https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/2/artifact/out/patch-javadoc-hadoop-hdfs-project_hadoop-hdfs-rbf-jdkUbuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04.txt

unit
https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/2/artifact/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs-rbf.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/2/testReport/

Max. process+thread count
3240 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs-rbf U: .

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-2047/2/console

versions
git=2.17.1 maven=3.6.0 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

It looks good to me.
@Hexiaoqiao can you provide feedback if you have tested it?

Thanks @fengnanli for your continued works. LGTM, I would like to give +1 from my side.
@goiri I just test this improvement in my test environment but not production cluster. it works fine for me.
Another suggestion, I still think we should consider this as common improvement not only for Router, since it is also effective for KMS and other modules who uses ZK to store DTs. So is it proper to move ZKDelegationTokenSecretManagerImpl class to common sub project? Of course this is not blocked point. cc @goiri @fengnanli @Cosss7 any suggestions?
Thanks @fengnanli again.

Thanks @Hexiaoqiao for the feedback.
I would make the proposed change for KMS in a separate JIRA.
If nobody has any concerns we can go ahead and merge this.

Thanks @goiri @Hexiaoqiao @Cosss7  for the review!
We internally have KMS running for some security projects and if anyone is interested in providing the KMS version, let me know the ticket so I can have them testing the code.

@fengnanli @goiri I agree that we can push this improvement ahead and file another JIRA for other modules.


Refactor dictionary data structure

Coverage increased (+0.4%) to 88.527% when pulling c8b99c32eaf05415e034c57e6b03ef8eecf3dcd3 on wakati-mode into 4d652cad4f1da267ca3257beb11abf63b5ad358e on master.


--exclude is not exluding

BTW. Really helpful tool!  It does exactly what I want. I pushed this all into gemini 1.5 flash and it was able to discuss my project intelligently.
I have tried specifying the --exclude in both the command line and inside the configuration file.  I also also tried both formats in the examples "/tests/" and "tests/*.
{
"suppress_comments": true,
"line_number": true,
"encoding": "cl100k_base",
"filter": ".py,.js",
"exclude": "tests/,prototypes/",
"tokens": true
}
(hals-pen-py3.10) yazoooo@yazoooo-dev:~/PycharmProjects/hals-pen$ code2prompt --output code2prompt.txt --gitignore .gitignore --tokens --path .
Beginning of output
Table of Contents

prototypes/bedrock_anthropic_3.py
prototypes/pyqt6_test_1.py
prototypes/pyqt6_scene_editor_test.py
prototypes/bedrock_anthropic_2.py
prototypes/bedrock_anthropic_1.py
prototypes/openai_api_test_1.py
prototypes/print_fonts.py
prototypes/scrolling_widgets.py
prototypes/openai_api_test_2.py
prototypes/pyqt6_test_2.py
prototypes/conversation_editor.py
tests/init.py
tests/BaseTest.py
tests/ui/init.py
tests/ui/test_plot_node_utils.py
tests/ui/test_project_controller.py
tests/ui/test_project_tree_model.py
tests/persistance/init.py
tests/persistance/test_story_io.py
tests/utils/init.py
tests/utils/test_image_utils.py
tests/story/init.py
tests/story/test_story_nodes.py
tests/story/test_story_project.py
tests/ai/init.py
tests/ai/test_openai_client.py
tests/ai/test_ai_client.py
tests/ai/test_ai_chat_builder.py
tests/ai/test_google_gemini_client.py
hals_pen/init.py
hals_pen/main.py
hals_pen/ui/tab_area.py
hals_pen/ui/project_tab.py
hals_pen/ui/init.py
hals_pen/ui/project_controller.py
hals_pen/ui/navigation_pane.py
hals_pen/ui/project_tree_view.py

The issue is fixed in version 0.6.7
Reinstall using pipx install code2prompt --force


Add examples to windows_security_policy

Signed-off-by: IanMadd<EMAIL_ADDRESS>Updates examples in windows_security_policy and windows_user_privilege resources.
Description
Resource examples were updated in chef/chef-web-docs#2488
This adds those examples to chef/chef
Related Issue

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] All commits have been signed-off for the Developer Certificate of Origin.

Checked the examples with cookstyle locally. They're fine.


FEAT: force_use_ref_model for power users

Fixes: https://github.com/huggingface/trl/issues/1365
This gives more flexibility to users that know what they're doing, by creating a new flag force_use_ref_model in case they want to use a different ref_model that the base model
cc @kashif

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


lower performance compared to tc_aws

Hi, i switched from tc_aws [7.0.2] to thumbor-aws [0.6.0], but i had to revert cause response time increased by ~ 200 ms.
My configuration is very simple and i use loader only (Bucket is get from url).
thumbor-aws conf:
AWS_LOADER_REGION_NAME = "eu-west-1"
AWS_LOADER_BUCKET_NAME = None
AWS_LOADER_ROOT_PATH = ""
AWS_STORAGE_REGION_NAME = ""
AWS_STORAGE_S3_SECRET_ACCESS_KEY = ""
AWS_STORAGE_S3_ACCESS_KEY_ID = ""
AWS_STORAGE_S3_ENDPOINT_URL = ""

tc_aws conf:
TC_AWS_REGION = "eu-west-1"
TC_AWS_ENABLE_HTTP_LOADER = True

Could be probably related to the improvements made on tc_aws by @amanagr https://github.com/amanagr/aws/pull/1 ?
(For whole PR thread: https://github.com/thumbor-community/aws/pull/147).
I will try to investigate further and let you know if i discover something relevant.
Regards, Alberto.

I made further tests and tried to use same approach of tc_aws to re-use s3_client.
I changed s3_client S3Client class to:
class S3Client:
    _client = None
    _instances = {}

    @staticmethod
    def __new__(cls, context):
        key = (context.config.AWS_LOADER_BUCKET_NAME, context.config.AWS_LOADER_REGION_NAME, context.config.AWS_LOADER_S3_ENDPOINT_URL)

        if not cls._instances.get(key):
            cls._instances[key] = super(S3Client, cls).__new__(cls)

        return cls._instances[key]

and checked if  self._client does exist before creating a new one.
As a result performance are now comparable to the tc_aws one!
Mine was only a test, but i can confirm you that the difference in response time is caused by the "multiple" s3 client initialization compared to initialize it just one time (for bucket, region, endpoint).

That fix work only if you do not  put code in an async with context and so do not use aiobotocore > 0.12.
Just for info the PR https://github.com/thumbor/thumbor-aws/pull/19, at the end re-use only the session not the client, and the bigger effort is on creating the whole s3 client.
Currently we have a fast tc_aws but that to re-use aiobotocore s3 client need to use an old (very) version.
And an up to date thumbor-aws that is not usable in production, compared to tc_aws, because increase reponse time of 0.2 sec (and under an high number of request, also memory usage).

Thanks for this heads up

just for info i have mixed tc_aws solutions https://github.com/thumbor/thumbor-aws/pull/19 and https://github.com/thumbor-community/aws/pull/142/commits/b5058e6b9fec7354629acc6d5df423e0310bb0cd in thumbor-aws
(for the second one i had to put _client = None in class definition root and not in class __init__)
This way i have thumbor-aws that use a persistent s3 client and that work using an up to date aiobotocore [2.x].
(i have it running in production without any problem so far)


Dapp CICD

Item Type
Story
Description
Twofold grand story:

Automate frontend deployments
Init e2e testing automation with cypress

Additional Information
If testing fails nothing should be deployed.
Acceptance Criteria

CI+CD pipeline in place

What are the points assigned to this item?
13
Is the issue ready?

[X] This issue is ready

https://github.com/BetaHuhn/deploy-to-vercel-action

done in https://github.com/t3rn/frontend/pull/12, https://github.com/t3rn/frontend/pull/13, and https://github.com/t3rn/frontend/pull/17


Screen record always

I use RtmpDisplay for capture and record the screen, while  frames on screen not updating video packets not wrote. How fix it and send Video packets on server side  always. MediaServer requreis keyframes in 2sec period. Thanks.

https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/issues/63


Kiosk will not build

Describe the bug
I'm trying to build the Kiosk UI as documented at https://membermatters.org/en/latest/GETTING_STARTED.html#kiosk-mode.
To Reproduce
$ cd membermatters/
$ git clone git@github.com:membermatters/MemberMatters.git src
$ cd src/
$ cd frontend/
$ npm install
$ npm run build
$ API_BASE_URL=http://localhost:8000 npm run build:electron

><EMAIL_ADDRESS>build:electron
> quasar build -m electron

 .d88888b.
d88P" "Y88b
888     888
888     888 888  888  8888b.  .d8888b   8888b.  888d888
888     888 888  888     "88b 88K          "88b 888P"
888 Y8b 888 888  888 .d888888 "Y8888b. .d888888 888
Y88b.Y8b88P Y88b 888 888  888      X88 888  888 888
 "Y888888"   "Y88888 "Y888888  88888P' "Y888888 888
       Y8b

 Build mode................ electron
 Pkg quasar................ v2.6.6
 Pkg @quasar/app-webpack... v3.5.1
 Pkg webpack............... v5
 Debugging................. no
 Publishing................ no

 Configured browser support (>= 84.95% of global marketshare):
 · Chrome for Android >= 100
 · Firefox for Android >= 99
 · Android >= 100
 · Chrome >= 91
 · Edge >= 97
 · Firefox >= 90
 · iOS >= 14.0-14.4
 · Opera >= 79
 · Safari >= 14.1

 App • Chaining "Renderer" Webpack config
 App • Extending "Renderer" Webpack config
 App • Cleaned build artifact: "/home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/dist/electron"
 App •  WAIT  • Compiling of "Preload" in progress...
 App •  WAIT  • Compiling of "Main" in progress...
 App •  WAIT  • Compiling of "Renderer" in progress...
(node:82995) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/node_modules/vuex/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
 App •  DONE  • "Preload" compiled with errors • 296ms

 App •  ERROR  •  Preload

Module not found: Can't resolve imported dependency "/home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/src-electron/electron-preload"
Did you forget to install it? You can run: yarn add /home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/src-electron/electron-preload

 App •  COMPILATION FAILED  • Please check the log above for details.

 • Compiling:
 ├── Preload  ███████████████████  92% sealing asset processing TerserPlugin
 ├── Main     ███████████████████  92% sealing asset processing copy-webpack-plugin
 └── Renderer ███                  10% building 0/1 entries 0/0 dependencies 0/0 modules

$ node:internal/process/promises:279
            triggerUncaughtException(err, true /* fromPromise */);
            ^

RpcIpcMessagePortClosedError: Cannot send the message - the message port has been closed for the process 83017.
    at /home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:47:47
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: undefined,
  signal: undefined
}
node:internal/process/promises:279
            triggerUncaughtException(err, true /* fromPromise */);
            ^

RpcIpcMessagePortClosedError: Cannot send the message - the message port has been closed for the process 83011.
    at /home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:47:47
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: undefined,
  signal: undefined
}

Expected behavior
I expect the node/electron Kiosk UI to build.
Screenshots
Desktop (please complete the following information):

OS: Ubuntu
Browser Chrome
Version

Additional context
Ubuntu 22.04
npm 8.5.0
nodejs 16.14.2

We haven't used the kiosk version for over a year now, so it's been a little neglected. I can take a look over the next few days and see what's broken. Looks like it's a dependency issue so hopefully not too big a deal!

That's fair enough, appreciate the insight.
Tbh, the kiosk just looked like something cool to add to the platform, we're quite a way away from needing it for any other reason than tracking how often people attend as we only have one room and so if someone's in the space we can probably see them!
Would be great to be able to play with it though if it is as simple as a dep update.

OK, so I found some more time to play with this and if I create the file frontend/src/electron-preload.js without any content, and then re-run it complains again:
 App •  DONE  • "Main" compiled with errors • 1671ms

 App •  ERROR  •  Main

Module not found: Can't resolve imported dependency "/home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/src-electron/electron-main"
Did you forget to install it? You can run: yarn add /home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/src-electron/electron-main

 App •  COMPILATION FAILED  • Please check the log above for details.

So I symlink src-electron/main-process/electron-main.js to src-electron/electron-main.js, and uncommment the preload line, and now I get the following:
npm --trace run build:electron

><EMAIL_ADDRESS>build:electron
> quasar build -m electron

 .d88888b.
d88P" "Y88b
888     888
888     888 888  888  8888b.  .d8888b   8888b.  888d888
888     888 888  888     "88b 88K          "88b 888P"
888 Y8b 888 888  888 .d888888 "Y8888b. .d888888 888
Y88b.Y8b88P Y88b 888 888  888      X88 888  888 888
 "Y888888"   "Y88888 "Y888888  88888P' "Y888888 888
       Y8b

 Build mode................ electron
 Pkg quasar................ v2.8.3
 Pkg @quasar/app-webpack... v3.6.0
 Pkg webpack............... v5
 Debugging................. no
 Publishing................ no

 Configured browser support (>= 86.52% of global marketshare):
 · Chrome for Android >= 105
 · Firefox for Android >= 104
 · Android >= 105
 · Chrome >= 96
 · Edge >= 102
 · Firefox >= 95
 · iOS >= 15.2-15.3
 · Opera >= 87
 · Safari >= 15.2-15.3

 App • Chaining "Renderer" Webpack config
 App • Extending "Renderer" Webpack config
 App • Cleaned build artifact: "/home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/dist/electron"
 App •  WAIT  • Compiling of "Preload" in progress...
 App •  WAIT  • Compiling of "Main" in progress...
 App •  WAIT  • Compiling of "Renderer" in progress...
(node:26696) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at /home/mmw/Projects/MakeMonmouth/membermatters/src/frontend/node_modules/vuex/package.json.
Update this package.json to use a subpath pattern like "./*".
(Use `node --trace-deprecation ...` to show where the warning was created)
 App •  DONE  • "Preload" compiled with success • 2291ms
 App •  DONE  • "Main" compiled with success • 4915ms
 App •  DONE  • "Renderer" compiled with errors • 31686ms

 App •  ERROR  •  Renderer  in<EMAIL_ADDRESS>
ModuleBuildError: Module build failed (from ./node_modules/css-loader/dist/cjs.js):
    ValidationError: Invalid options object. CSS Loader has been initialized using an options object that does not match the API schema.
     - options.url should be one of these:
       boolean | object { filter? }
       -> Allows to enables/disables `url()`/`image-set()` functions handling.
       -> Read more at https://github.com/webpack-contrib/css-loader#url
       Details:
        * options.url should be a boolean.
        * options.url should be an object:
          object { filter? }

    - validate.js:105 validate
      [frontend]/[schema-utils]/dist/validate.js:105:11

    - NormalModule.js:585 Object.getOptions
      [frontend]/[webpack]/lib/NormalModule.js:585:19

 App •  COMPILATION FAILED  • Please check the log above for details.

Just coming back to this and wondering if you had a chance to look at it?
I'm seeing the same error still when following the commands to build at https://membermatters.org/en/latest/GETTING_STARTED.html#kiosk-mode
If I just run npm run build, then I get a long list of errors starting with:
App •  WAIT  • Compiling of "UI" in progress...
 App •  DONE  • "UI" compiled with errors • 114180ms

 App •  ERROR  •  UI  in src/components/Account/RegistrationCard.vue:179:14

TS2339: Property 'loggedIn' does not exist on type '{ name: string; mixins: { methods: { validateEmail(email: string): boolean; validateNotEmpty(value: string): boolean; validatePassword(value: string): boolean; validateMatchingField(current: string, newField: string): boolean; validateFutureDate(date: string): boolean; validateFutureTime(time: string): boolean; vali...'.
    177 |   },
    178 |   mounted() {
  > 179 |     if (this.loggedIn) this.$router.push({ name: "dashboard" });
        |              ^^^^^^^^
    180 |   },
    181 |   computed: {
    182 |     ...mapGetters("profile", ["loggedIn"]),

This isn't massively urgent, but it would be nice to get this up and running so we can have it on a small screen attached to a Pi or similar by the door.

As mentioned on Discord, the build issue should be fixed now. However, the kiosk mode hasn't been thought about in several years so you may find problems with it, if you do, please open a GitHub issue. 🙂


Safelist entries get removed from sidebar

There seems to be a bug where Safelist entries get removed from the sidebar.
Steps to reproduce:

Create a Safe
Create a second safe
Open Sidebar and switch to first Safe
Refresh page -> Only 1 Safe is now listed in the sidebar

This also affects the production version.
It also is not dependent on the user creating a new Safe, rather, the bug always appears when the page is refresh shortly after switching Safes.
I consider this a critical bug and it should be addressed before the public launch on Wednesday if possible.

I though so, working on it, will continue it at early on monday

This issue was closed by #358


On Tap Returning app crash

The Issue on navigator.pop(context);
This happens on iOS 16 but works fine on iOS17
something very werid

Am also facing similar issue here

Hello guys,
Thanks  for informing
I'll take a look,
Best regards


["Enhancement" request] Local user password length

Detailed Description
In SUSE Rancher 2.6.3-rc1 the minimum password length for local users is 12 characters.
For testing purposes this is a bit too "difficult". (I perfectly understand the security standpoint behind, though.)
Context
Would it be possible to have a check box or other way to override this configuration for testing purposes?

I'm not 100% sure, but i think the restriction is only checked on change not when initially set, so you should be able to get around this by setting it manually at install time

I created a new local user in Users and Authentication. Errored out with a pw too short.
But you are partly right. The initial password for new user must be 12 chars, but you can change it to shorter one later. :)
A short admin password can be set manually during the deployment. Can I also create other users at this stage?

I don't think you should be able to change a user's password to anything less than 12 characters at any point.
I also don't think you should be able to create a user with an invalid password, if that's the case it's probably a bug.
Setting the password at install time I think only works with the default admin.

OK. The UI does not complain if admin sets a short password to an existing user. The password gets corrupted, though, and user can not log in anymore with the old or the new password.

Tested some more.
If admin sets too short password, no error is displayed.
The password does not get changed, though, and the old stays active.

That was https://github.com/rancher/dashboard/pull/4583 .
If you want a shorter password length, it's a setting, set it lower.  /v3/settings/password-min-length

Thanks @vincent99  I'm cool with the solution.
From my standpoint the issue can be closed.


show past polls also in client

I am trying if the "Load History" button actually works (from the UI dialog: "Gridcoin Voting System 1.1")

nothing shown after 17 mins

I can see so far in this dialog only current, ongoing polls: there is 1 poll which is still votable on until 30 Jan 2018

https://github.com/Erkan-Yilmaz/Gridcoin-tasks/issues/138#issuecomment-312846588

IIRC the RPC command for this also fails. Or rather, it returns nothing.

It is a regression. It worked for me at some poibt.

I think this issue is fixed, in staging, right @denravonska? This should be the Qfuture/QtConcurrent bug, right?

It is! :)


Install process loop stuck fails on vcbuildtools.

After following the instructions laid out, my install package just loops on an infinite basis. Currently trying to install on a Windows 10 Home VM. Appears to get stuck at "The install of vcbuildtools was not successful."
I only manage to get as far as cmder being installed. Then it looks like it installs python/a series of python packages but then it enters an continuing loop, restarts, attempts to install the same thing, etc.

I am experiencing the same issue. I already tried Windows 10 and Windows 7.

I am also experiencing this issue on Windows 10

WARNING: Generic MSI Error. This is a local environment error, not an issue with a package or the MSI itself - it could mean a pending reboot is necessary prior to install or something else (like the same version is already installed). Please see MSI log if available. If not, try again adding '--install-arguments="'/l*v c:\vcbuildtools_msi_install.log'"'. Then search the MSI Log for "Return Value 3" and look above that for the error.
ERROR: Running ["C:\Users\Malware\AppData\Local\Temp\vcbuildtools\2015.4\visualcppbuildtools_full.exe" /S ] was not successful. Exit code was '1603'. Exit code indicates the following: Generic MSI Error. This is a local environment error, not an issue with a package or the MSI itself - it could mean a pending reboot is necessary prior to install or something else (like the same version is already installed). Please see MSI log if available. If not, try again adding '--install-arguments="'/l*v c:\vcbuildtools_msi_install.log'"'. Then search the MSI Log for "Return Value 3" and look above that for the error..
The upgrade of vcbuildtools was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\vcbuildtools\tools\chocolateyinstall.ps1'.
See log for details.

If this helps at all this is the warning and error

Experiencing this issue on Windows 10 too

I downloaded the following and it fixed that particular issue: https://www.microsoft.com/en-us/download/details.aspx?id=48159
I then ran into issues with another package stringsifter. I had to manually install it and all of it's dependents.

Hey all,
Thanks for bringing this to our attention. We've updated the vcbuildtools.fireeye package to depend on the 2017 VC build tools package and removed the vcpython27 package from the installation list.
Please give the updates a whirl and let us know if the problem persists.


Shall we bring gravitational potential into flux calculation?

probably no. It seems that something can be done with calculating rho*g


support disk based transactions

In current implementation, some operations like ORDER BY, GROUP BY and also transactions, are executed in heap memory.
This leads to OutOfMemory exceptions when working with big transactions or with big result sets.
When system has low memory, transaction data should be swapped on a disk-based structure, so that the operation can be completed without errors, even with lower performance.

Luigi you propose is the same issue already created issue https://github.com/orientechnologies/orientdb/issues/2022 . Because our transactions right now absolutely disk based.  Also we already discusses this question with you in chat. Why do you call this feature "disk based transactions". It is not true.
Because:

It is misleading.
This issue duplicates two issue, one I mentioned bellow, second one is https://github.com/orientechnologies/orientdb/issues/2874 .

WDYT ?

Duplication of https://github.com/orientechnologies/orientdb/issues/5504


Polymer 2.x update

I needed this component to work with polymer 2.x, so following the upgrade guide, I upgraded your component to a legacy element, then to a class-based element.
Would you be interested in creating new branches for your project so that I can submit PRs to share the updates?
I would propose reorganizing the branches like this:

master -> Polymer 2.x class-based element
polymer-2-legacy -> Polymer 2.x legacy element
polymer-1.x -> The current master branch

Hi!
For the moment I prefer if the master branch is the hybrid (legacy) mode, as it works on both setups (Polymer 1.x and 2.x).
I have already done the hybridation of many of my elements, but I hadn't found time to upgrade this one, so I'm doing it now :)
I'm also created a polymer-2.x branch in order to receive a PR with your class based element, thanks a lot for doing it !

Branch polymer-2.x created :)


How to backup wiki-pages via osfclient?

Hi, I was trying to backup our wiki repository including files and wiki-pages. Is this possible with osfclient? And, if not, are you planning on adding this feature?

I would also find this quite useful! Was also mentioned in #132


ARROW-6110: [Java][Integration] Support LargeList Type and add integration test with C++

Add large list and ensure it works with Integration tests. As noted in the JIRA
ticket this is rather limited as the underlying vector doesn't support int64 addressing
The important downcasts to int32 have been noted for a follow up once vectors with
long addresses are supported

@BryanCutler would you have time to review?

@rymurr looks like this needs a rebase

@rymurr looks like this needs a rebase

Thanks for the reminder @emkornfield, done.

I'm a little swamped right now, but I'll try to review sometime this week

Is this good to merge now? @BryanCutler are you still planning to review this? Would like to get this in 1.0.

Is this good to merge now? @BryanCutler are you still planning to review this? Would like to get this in 1.0.

I'm taking a look now, I'd like to get it in for 1.0 too.

Thanks for working on this @rymurr ! Apologies for taking so long to review.. It looks pretty good, but I saw what looked like inconsistencies in the LargeListVector APIs using ints vs longs to me, and otherwise only minor things to fix up.

Thanks a lot for the thorough review. I have fixed up everything you mentioned. It appears some of the confusion was related to changes for 64-bit allocations that were recently merged and the rest was my ignorance!
I have pushed a change with all your recommended fixes.

Thanks for the quick update @rymurr , it looks pretty good! Only a couple minor things. I see quite a few instances of offsetBuffer.getLong/setLong(i * OFFSET_WIDTH) that I believe need to be cast to long to avoid overflow. Could you take a quick pass and fix those up? I think we will be good to go after that.

Thanks for another thorough review @BryanCutler ! I think that I addressed everything. I may have went over the top w/ the casting but it doesn't hurt :-)

merged to master, thanks @rymurr !


Update o-universo-revelado-com-python.json

Detected error (no speaker). Following the link "Improve this page", and filling the pull request through web.

To enable the "Improve this page" route seems required to admit an \n at the end of the page.

Not so sure that \n make the tests fail
Incorrect serialization order in /home/travis/build/pytube/data/djangocon-eu-2015/category.json

Incorrect serialization order in /home/travis/build/pytube/data/bostonpy/category.json

Incorrect serialization order in /home/travis/build/pytube/data/depy2015/category.json

Incorrect serialization order in /home/travis/build/pytube/data/pythonbrasil-2015/category.json

Incorrect serialization order in /home/travis/build/pytube/data/pythonbrasil-2010/category.json

Incorrect serialization order in /home/travis/build/pytube/data/pythonbrasil-2010/videos/o-universo-revelado-com-python.json

Incorrect serialization order in /home/travis/build/pytube/data/depy2016/category.json

Will try again with my repo up to date


MTL-2247 partial -- adds gitea role

Summary and Scope

adds ansible role for installing and configuring gitea (written by @manderson-hpe, stolen by @jpdavis-prof)

Issue Type

RFE Pull Request

Prerequisites

[x] I have included documentation in my PR (or it is not required)
[x] I have tested this by building an image using this branch HEAD, or this is does not pertain to the node-images pipeline.
[x] I tested this on internal system or this pertains to the node-images pipeline (if yes and not build related, please include results or a description of the test)

Idempotency
Yes
Risks and Mitigations
None

/backport lts/csm-1.5


Feed us section css improvements

Current:-

desired:-

Changes required:-

.feed{
border-radius: 100px;
}
.counter{
color: orange !important;
background-color: #92858552
}

As feed us section in in various pages, please be sure to change the css files for all instances.

Can I work on this issue?

@shriya030 , best of luck.

Lol, @himanshu007-creator  This is a repeat issue of  Which I created !! Its ok Np Great work @shriya030


Configure Renovate

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

Detected Package Files

.github/workflows/release.yml (github-actions)
.github/workflows/verify.yml (github-actions)
package.json (npm)

What to Expect
With your current configuration, Renovate will create 27 Pull Requests:

chore(deps): update dependency @changesets/cli to v2.26.2

Schedule: ["at any time"]
Branch name: renovate/changesets-cli-2.x-lockfile
Merge into: main
Upgrade @changesets/cli to 2.26.2

chore(deps): update dependency @rollup/plugin-typescript to v11.1.2

Schedule: ["at any time"]
Branch name: renovate/rollup-plugin-typescript-11.x-lockfile
Merge into: main
Upgrade @rollup/plugin-typescript to 11.1.2

chore(deps): update dependency @tokens-studio/types to v0.2.5

Schedule: ["at any time"]
Branch name: renovate/tokens-studio-types-0.x-lockfile
Merge into: main
Upgrade @tokens-studio/types to 0.2.5

chore(deps): update dependency @web/dev-server-rollup to v0.5.2

Schedule: ["at any time"]
Branch name: renovate/web-dev-server-rollup-0.x-lockfile
Merge into: main
Upgrade @web/dev-server-rollup to 0.5.2

chore(deps): update dependency browser-style-dictionary to v3.1.1-browser.2

Schedule: ["at any time"]
Branch name: renovate/browser-style-dictionary-3.x-lockfile
Merge into: main
Upgrade browser-style-dictionary to 3.1.1-browser.2

chore(deps): update dependency colorjs.io to v0.4.5

Schedule: ["at any time"]
Branch name: renovate/colorjs.io-0.x-lockfile
Merge into: main
Upgrade colorjs.io to 0.4.5

chore(deps): update dependency @typescript-eslint/eslint-plugin to v5.62.0

Schedule: ["at any time"]
Branch name: renovate/typescript-eslint-eslint-plugin-5.x-lockfile
Merge into: main
Upgrade @typescript-eslint/eslint-plugin to 5.62.0

chore(deps): update dependency @typescript-eslint/parser to v5.62.0

Schedule: ["at any time"]
Branch name: renovate/typescript-eslint-parser-5.x-lockfile
Merge into: main
Upgrade @typescript-eslint/parser to 5.62.0

chore(deps): update dependency @web/dev-server-esbuild to ^0.4.0

Schedule: ["at any time"]
Branch name: renovate/web-dev-server-esbuild-0.x
Merge into: main
Upgrade @web/dev-server-esbuild to ^0.4.0

chore(deps): update dependency @web/test-runner to ^0.17.0

Schedule: ["at any time"]
Branch name: renovate/web-test-runner-0.x
Merge into: main
Upgrade @web/test-runner to ^0.17.0

chore(deps): update dependency @web/test-runner-playwright to ^0.10.0

Schedule: ["at any time"]
Branch name: renovate/web-test-runner-playwright-0.x
Merge into: main
Upgrade @web/test-runner-playwright to ^0.10.0

chore(deps): update dependency eslint to v8.47.0

Schedule: ["at any time"]
Branch name: renovate/eslint-8.x-lockfile
Merge into: main
Upgrade eslint to 8.47.0

chore(deps): update dependency eslint-config-prettier to v8.10.0

Schedule: ["at any time"]
Branch name: renovate/eslint-config-prettier-8.x-lockfile
Merge into: main
Upgrade eslint-config-prettier to 8.10.0

chore(deps): update dependency eslint-plugin-import to v2.28.0

Schedule: ["at any time"]
Branch name: renovate/eslint-plugin-import-2.x-lockfile
Merge into: main
Upgrade eslint-plugin-import to 2.28.0

chore(deps): update dependency glob to v10.3.3

Schedule: ["at any time"]
Branch name: renovate/glob-10.x-lockfile
Merge into: main
Upgrade glob to 10.3.3

chore(deps): update dependency lint-staged to v13.3.0

Schedule: ["at any time"]
Branch name: renovate/lint-staged-13.x-lockfile
Merge into: main
Upgrade lint-staged to 13.3.0

chore(deps): update dependency rollup to v3.28.0

Schedule: ["at any time"]
Branch name: renovate/rollup-3.x-lockfile
Merge into: main
Upgrade rollup to 3.28.0

chore(deps): update actions/checkout action to v3

Schedule: ["at any time"]
Branch name: renovate/actions-checkout-3.x
Merge into: main
Upgrade actions/checkout to v3

chore(deps): update actions/setup-node action to v3

Schedule: ["at any time"]
Branch name: renovate/actions-setup-node-3.x
Merge into: main
Upgrade actions/setup-node to v3

chore(deps): update dependency @rollup/plugin-commonjs to v25

Schedule: ["at any time"]
Branch name: renovate/rollup-plugin-commonjs-25.x
Merge into: main
Upgrade @rollup/plugin-commonjs to ^25.0.0

chore(deps): update dependency @typescript-eslint/eslint-plugin to v6

Schedule: ["at any time"]
Branch name: renovate/typescript-eslint-eslint-plugin-6.x
Merge into: main
Upgrade @typescript-eslint/eslint-plugin to ^6.0.0

chore(deps): update dependency @typescript-eslint/parser to v6

Schedule: ["at any time"]
Branch name: renovate/typescript-eslint-parser-6.x
Merge into: main
Upgrade @typescript-eslint/parser to ^6.0.0

chore(deps): update dependency eslint-config-prettier to v9

Schedule: ["at any time"]
Branch name: renovate/eslint-config-prettier-9.x
Merge into: main
Upgrade eslint-config-prettier to ^9.0.0

chore(deps): update dependency lint-staged to v14

Schedule: ["at any time"]
Branch name: renovate/lint-staged-14.x
Merge into: main
Upgrade lint-staged to ^14.0.0

chore(deps): update dependency prettier to v3

Schedule: ["at any time"]
Branch name: renovate/prettier-3.x
Merge into: main
Upgrade prettier to ^3.0.0

chore(deps): update dependency rimraf to v5

Schedule: ["at any time"]
Branch name: renovate/rimraf-5.x
Merge into: main
Upgrade rimraf to ^5.0.0

chore(deps): update dependency typescript to v5

Schedule: ["at any time"]
Branch name: renovate/typescript-5.x
Merge into: main
Upgrade typescript to ^5.0.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

This PR has been generated by Renovate Bot.

I would rather not adopt renovate bot, for a few reasons:

Pull request spam
Upgrading to new majors likely will cause issues with breaking changes
Just because a dependency is bumped and merged to master, doesn't mean this will translate to what is downloaded by consumers through NPM, because it's not coupled to a release. This is confusing. The alternative is always doing bumps + releases when deps get bumped, but that will cause a bloated changelog with a bloat in the amount of releases we do

We can configure the bot to minimize the amount of PRs it makes and merging into a single PR, as well as limit the changes
That being said, its is noisy with large amounts of deps,and your feedback on dependency changes is completely valid

I'm going to close this for now as I feel like Renovate is more suited for kubernetes and terraform updates


Roadmap

Hey guys-
I am curious what you guys' thoughts are on the future of Anna?  It seems like it would make for a great base for a Microservice framework (haven't seen many in the .NET world).  I'm debating on whether I should fork and create my own based on Anna or contribute here... let me know what you think.

@jbarker7, first of all sorry for the delay in my response.
I agree and I am very open to contributions as well as adding contributors directly to the organisation.
I haven't been using Anna and I have been out of .Net for 4 years now, but since the repository got many contributions I thought it was unfair to keep it under my username so I decide to move it to an org instead.
I still think Anna is the kind of web framework that I'd like to be using, I think the abstractions are quite powerful and there is something about this that I can't find in other frameworks/libs/languages.
Last time I looked we were discussing #9. Please feel free to jump in, fork contribute or create issues with things you think you will like to have. I'm very open to discuss, share ideas, review code, etc.
I'd like to keep it small and simple, but I know there is a lot that can be done to make it more useful.

Sorry, I think after everything I wrote I didn't answer the question, the roadmap is a blank page, there is none.
As I mention before we were discussing #9 few months ago,  is about JSON support for encoding/decoding.


Upgrade grpc to 1.23.0.

This change is

Thank you for these fixes. Much easier to make the next gRPC upgrade after this.


Explain our use of Conventional Commits in CONTRIBUTING.md

Description
This repository uses the Conventional Changelog specification for our commit messages. Explain in the CONTRIBUTING.md file about how we use these commit messages.
Implementation model
The Conventional Changelog specification can be read here: https://www.conventionalcommits.org/en/v1.0.0/ - as a refresher:
<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

The commit types that we use are: feat, fix, refactor, docs, build, chore, perf, style, test. This follows the Angular commit message guidelines.
If possible, we should also define the scopes that this project uses.
Tasks

[ ] Explain our use of Conventional Changelog specification
[ ] Explain the commit types that we use
[ ] Explain the use of commitlint to lint commit messages
[x] (Optional) Switch default merge type for PRs to squash merge-only, to ensure all commit messages match standards

Final task has already done through the GitHub repo settings.

We can update each PR's title with the appropriate conventional commit standards before triggering automerge.


[GDPR] Data removal tool

A logged in user should have the ability to remove their own data (and effectively close their account).
We should likely require a confirmation link to be clicked to prove that the person has access to the email address of the logged in account, otherwise, data removal could become a DoS attack vector.
Anonymous users should have a way to request their data being removed by providing an identifying piece of information like the email address or a phone number. Similar confirmation methods could be used to ensure this feature is not abused with malicious intent.
As the store is required to fulfill any outstanding contracts, orders and financial records should be preserved until they are no longer needed.

When deleting User's account, should we remove user_email  from Order and phone number from order's addresses as well?
I don't find them necessary to keep

Should we keep a track of who deleted which user?

We should not delete any address data as we may still need to contact the user regarding their orders. We have a contractual requirement here but also a legal obligation (the store still needs to be able to accept returns, replacements, refunds and so on).
As for keeping track of who deletes whom:

if the user deletes their own account we don't need to keep track of that as long as we make sure random people can't delete data that belongs to others
if an admin fulfills a right to be forgotten in response to a legitimate request, the company is required to keep this information in an audit log (it's company-level, like accounting, not specific to Saleor, and we don't need to provide such functionality as part of this issue)

During this issue, I'll handle #2000 and #1966 as they seem related to the problems I'm facing.
eg. staff user deleting another's staff user account
I'll introduce another permission 'edit_staff' for this purpose


Issue with IP Blocking and Allowing in global configuration

I configured IP blocking and allowing in Ocelot using SecurityOptions, but it's not working.
{
  "GlobalConfiguration": {
    "BaseUrl": "http://localhost:5000",
    "SecurityOptions": {
      "IPBlockedList": ["<IP_ADDRESS>"]
    }
  }
}

The IP blocking configuration is not working as expected.

Hello, Cavid!
It appears we don't have support for global settings.
You should define the options for each individual route.

Hello @Fabman08,
The absence of global settings support is a significant issue. Here's the current usage of SecurityOptionsCreator:
https://github.com/ThreeMammals/Ocelot/blob/6088515173b70abd52798e544e5ded409680dbdb/src/Ocelot/Configuration/Creator/RoutesCreator.cs#L111
Consequently, the method should accept two arguments, including global settings:
https://github.com/ThreeMammals/Ocelot/blob/6088515173b70abd52798e544e5ded409680dbdb/src/Ocelot/Configuration/Creator/SecurityOptionsCreator.cs#L8
Would you be able to allocate some time to address this?

Hi @raman-m!
Sure, I'll be able to fix the issue this or next week. ☺
@CavidH thank you for reporting this issue! 👍

Thank you very much for your help. We will eagerly await the new version.

Hello, Cavid! It seems we lack support for global settings. The potential solutions could be:

Solely using ocelot.json. Define the options for each route individually.
Utilizing C# coding. Replace the ISecurityOptionsCreator service in the DI container by redeveloping the SecurityOptionsCreator class to consider only the global settings.
https://github.com/ThreeMammals/Ocelot/blob/6088515173b70abd52798e544e5ded409680dbdb/src/Ocelot/DependencyInjection/OcelotBuilder.cs#L141

Which solution would be more convenient for you?

I had thought of the first option, but since I have too many services, it will be difficult to control this

@raman-m just a little question about Global Settings behaviours.
I've found three ways to fix the issue:

Every properties in Route FileSecurityOptions overrides their Global Settings values
eg.

Global:
Allowed: B,C
Blocked: E
ExcludeAllowedFromBlocked: true
Route:
Allowed: A,B,C
Blocked: D,E,F
ExcludeAllowedFromBlocked: false
Final:
Allowed: A,B,C
Blocked: D,E,F
ExcludeAllowedFromBlocked: false

Only the existing properties in Route FileSecurityOptions overrides their Global Settings values
eg.

Global:
Allowed: B,C
Blocked: E
ExcludeAllowedFromBlocked: true
Route:
Allowed: A,B,C
Blocked: null
ExcludeAllowedFromBlocked: null
Final:
Allowed: A,B,C
Blocked: E
ExcludeAllowedFromBlocked: true

The Route FileSecurityOptions values will be merged to Global Settings values
eg.

Global:
Allowed: A,B,C
Blocked: D,E
ExcludeAllowedFromBlocked: true
Route:
Allowed: F,G,H
Blocked: I,K
ExcludeAllowedFromBlocked: false
Final:
Allowed: A,B,C,F,G,H
Blocked: D,E,I,K
ExcludeAllowedFromBlocked: false

Which one is the best?

@Fabman08  Your research is too complicated!

Which one is the best?

It is best to prioritize the route-specific FileSecurityOptions object over the global settings. Therefore, if route settings are defined, all global settings should be disregarded. In practice, if the route object is null, then the global settings should be utilized.

Every properties in Route FileSecurityOptions overrides their Global Settings values

Yes. If route opts are defined, ignore all global ones! We will pay user's attention to this in docs. No merging at all. This will be the simplest solution and single right one, because merging props will be wrong because they will run into conflict in the algorithm. So merging is the source of bugs.


Token expiry refresh is broken

Caught it this morning. I don't know if this is a regression or a bug in the original implementation. Will try to follow up with a an artificial reproducer. Exception:
Uncaught TypeError: Cannot read property 'token_endpoint' of null
    at LoginComponent.componentDidUpdate (webpack-internal:///./src/app/auth/LoginComponent.tsx:33)
    at commitLifeCycles (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:17349)
    at commitAllLifeCycles (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:18736)
    at HTMLUnknownElement.callCallback (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:149)
    at Object.invokeGuardedCallbackDev (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:199)
    at invokeGuardedCallback (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:256)
    at commitRoot (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:18948)
    at eval (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:20418)
    at Object.unstable_runWithPriority (webpack-internal:///./node_modules/scheduler/cjs/scheduler.development.js:255)
    at completeRoot (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:20417)
webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:17117 The above error occurred in the <LoginComponent> component:
    in LoginComponent (created by Context.Consumer)
    in Connect(LoginComponent) (created by Route)
    in Route (created by AppComponent)
    in Switch (created by AppComponent)
    in Router (created by ConnectedRouter)
    in ConnectedRouter (created by Context.Consumer)
    in ConnectedRouterWithContext (created by Context.Consumer)
    in Connect(ConnectedRouterWithContext) (created by AppComponent)
    in ThemeProvider (created by AppComponent)
    in div (created by Context.Consumer)
    in Styled(div) (created by AppComponent)
    in div (created by Context.Consumer)
    in Styled(div) (created by AppComponent)
    in AppComponent (created by Context.Consumer)
    in Connect(AppComponent)
    in Router (created by ConnectedRouter)
    in ConnectedRouter (created by Context.Consumer)
    in ConnectedRouterWithContext (created by Context.Consumer)
    in Connect(ConnectedRouterWithContext)
    in PersistGate
    in Provider

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://fb.me/react-error-boundaries to learn more about error boundaries.

Related #370


benchmark: harmonize colours between plots

rename "pending" line to "awaiting to run" not to conflict with REANA workflow status "pending";
add "queued" or "pending" points at the end of the "waiting to run" line in execution_progress plot if a workflow is not started yet;
use the same colors in execution_status and execution_progress plots for workflow statuses;
histogram plots have only one label so colors harmonization is not applied there, colours are generated automatically, usually blue.

closes #588
How to test:

If you don't have already collected results from previous benchmarks you can get new ones:

$ reana-benchmark launch -w color -n 1-10
$ reana-benchmark collect -w color

OR, you can use this CSV content and save it under color_collected_results.csv:
name,run_number,created,started,ended,status,asked_to_start_date,collected_date
color-3,1,2021-11-16T10:24:12,2021-11-16T10:24:39,,running,2021-11-16T10:24:23,2021-11-16T10:24:47
color-2,1,2021-11-16T10:24:11,2021-11-16T10:24:37,2021-11-16T10:24:44,finished,2021-11-16T10:24:23,2021-11-16T10:24:47
color-1,1,2021-11-16T10:24:11,2021-11-16T10:24:35,2021-11-16T10:24:42,failed,2021-11-16T10:24:23,2021-11-16T10:24:47
color-4,1,2021-11-16T10:24:12,,,queued,2021-11-16T10:24:23,2021-11-16T10:24:47

You can even modify this CSV content. Few notes if you decided to modify content for testing:

running status doesn't have ended value;
pending and queued statuses doesn't have started and ended values;
collected_date is the same for all workflows.

Run reana-benchmark analyze -w color -n 1-10 to get plots.

This PR is modifying the style and colors of the two plots so you can check if colors/labels make sense to you, etc.

Codecov Report

Merging #592 (2b155e8) into master (fdcaa59) will decrease coverage by 5.16%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #592      +/-   ##
==========================================
- Coverage   26.00%   20.83%   -5.17%
==========================================
  Files          17       25       +8
  Lines        1546     1929     +383
==========================================
  Hits          402      402
- Misses       1144     1527     +383

Impacted Files
Coverage Δ

reana/reana_benchmark/__init__.py
0.00% <0.00%> (ø)

reana/reana_benchmark/analyze.py
0.00% <0.00%> (ø)

reana/reana_benchmark/cli.py
0.00% <0.00%> (ø)

reana/reana_benchmark/collect.py
0.00% <0.00%> (ø)

reana/reana_benchmark/config.py
0.00% <0.00%> (ø)

reana/reana_benchmark/start.py
0.00% <0.00%> (ø)

reana/reana_benchmark/submit.py
0.00% <0.00%> (ø)

reana/reana_benchmark/utils.py
0.00% <0.00%> (ø)

execution_progress plot produced by this PR:

execution_status plot produced by this PR:

thought: I think, this PR is doing more stuff than the title ("harmonize colors") says (renaming label and adding statuses points to execution_progress plot). Remainder for me to keep commits/PRs more separated for the future.

For me personally the colors now seems a bit too aggressive. I prefer the ones in the left (e.g. lightblue instead of navy, etc.). Of course it's very personal, it would be interesting to hear what others think.

I don't have preferences with colors, I can try to make them "less aggressive". My only concern is visibility on the execution_progress plot.

Number of workflows is a bit hard to read. Font size could be increased a bit and font-weight could be made bold?

Agree. I can also see that "workflow" can collide with some labels making it even less visible. Will check that too.

Again, very personal, but for me coloring the status labels does not seem necessary

I added it just because it was part of an example I used. I will remove the coloring of status labels because, honestly, no one really asked for it so no point in adding it :)

Not sure about awaiting to run, for me pending makes sense with queued included.

Here is also my initiative that no one asked for :) I can revert it back cause even if change is needed there it deserves a separate PR.

Just a thought: could we increase the dot for failed workflows? So that it wouldn't be lost in a sea of finished ones, WDYT?

Interesting idea, I will try to increase and see how the plot will look like.

You can see that running color is light blue in execution_status and dark blue in execution_progress (other plots uses dark blue too). We could unify these colors across the plots.

Just in case, running workflow status and running line in execution_progress plot are a bit different things but I think it is a good idea to have the same colors for them.

Pending (pending+queued) in execution_progress is orange and Queued in execution_status is violet. I would expect the same color, since it's almost the same thing. WDYT?

I can try to find some colors similar to orange for queued and pending statuses to align them with pending line.

I was actually referring to the white numbers which shows how many workflows falls into certain category in execution_status plot.

Agree. Will make numbers more visible.
Tasks:

[ ] align running line color with running status

[ ] align queued and pending statuses with pending line

[ ] make white numbers on the execution status plot more visible