Error in header.js when anonymous Page load

I would like to have a starting page with anonymous access. This is working, by setting home controller to enable anonymous access.
Unfortunately header.js gives an error, because appSession.user is null.
this function has the error:
vm.getShownUserName
I would expect to have a login possibility for anonymous users.

Hi,
It can be easily fixed. Example:
        vm.getShownUserName = function () {
            if (!appSession.user) {
                return 'anonymous user';
            }

            if (!abp.multiTenancy.isEnabled) {
                return appSession.user.userName;
            } else {
                if (appSession.tenant) {
                    return appSession.tenant.tenancyName + '\\' + appSession.user.userName;
                } else {
                    return '.\\' + appSession.user.userName;
                }
            }
        };

But this is not the only problem. We have a dropdown on user name which is used to Logout. So, this should be also adapted. Also, HomeController has a [AbpMvcAuthorize]. There maybe some minor changes too, because this application is designed to login.
But I think you can easily change it for your needs.

I did all that, what you suggested. I do get Errors on the first visit.
have a look at: https://bogasco.azurewebsites.net/#/
(that's where i test)

When I check it, I see this request send error:
https://bogasco.azurewebsites.net/api/services/app/session/GetCurrentLoginInformations
So, this method also needs login. You should check and fix it too.

thanks, I am trying to disable minification of scripts when debugging, should be in System.Web.Optimization.BundleTable.EnableOptimizations = false, but can't find it :(

You can try to debug=true in web config:
<compilation debug="true"  .../>
This is removed on release normally.

I found a workaround for the time being:
In SessionAppService.GetCurrentLoginInformationsOutput() - now without AbpAuthorize
if (AbpSession.UserId.HasValue == false)
{
return new GetCurrentLoginInformationsOutput() {
User = new UserLoginInfoDto() {
Name = "No Name",
UserName = L("Login_Anonymous_UserName")
}
};
}
This is working. It's not pretty but it's ok. I will probably have to overwrite Navigation (Header) to make that work pretty as well (now Logout changed to Login via jQuery).
Thank you for leading me in the right direction :+1:

You're welcome :)


Pipeline/Release variables all converted to secrets?

In PR #218 (completed) all/many of the pipeline/release variables are converted to secrets.
What is the reasoning behind it?
Some of the labs are not matching anymore, and also values are now hidden, while some of them seems not have any reason to be hidden (eg url to ACR, DB name, ...).
/cc @aksh-h

Hi @Styxxy, Thank you for reaching us.
we were receiving some errors messages when the variable kept as plane text. So we converted those into secrets. Based on user feedback we are gradually adding those into documentations.
We have noted your point and will ask the team to verify the content once.
Thanks!!


Update RET to HALT

Closes #24
Implementation

Update RET to HALT in lexer, tokens, and compiler.

All integration tests and yamtests are passing. Merging this.


Balance update

@Ran73Cohen works on the staging for me, not sure if it's rebuilt then for my 3a43074 commit but should also work for network changes.

Still too many emissions,
Login
Go to kovan
Switch back to mainnet

@Ran73Cohen looks like the currentNetworkReceiver$ was still getting passed unspported networks, I've since filtered that out and can work out a strategy further whether it's only supported networks go through there or another is built off of it called supportedNetwork$ or something but probably won't be required.


Bump Pyro to >1.9.0 and fix resulting lint errors

TODO

@eb8680 , I started this thinking it would be easy, but it appears to be very much not easy to address these linting errors. A major source of trouble is our use of generic types throughout ChiRho, and with pyro==1.9.0 the results of primitive pyro operations are now fixed as torch.Tensor or related.

Addressed in #527


Link to docs.rs from readme and crates.io

There is a lot of useful information at https://docs.rs/bson/0.3.2/bson/ but there are no links to it from the readme or crates.io. New users don't know where to get started.
cc @sssilver

I'll take care of this.

Already merged! Thank you all!


upgrade hive

Signed-off-by: ldpliu<EMAIL_ADDRESS>https://github.com/stolostron/backlog/issues/22810

/cc @skeeey @zhiweiyin318

/approve
/lgtm


TestGesture.cancel doesn't invoke Drag.cancel in test

Steps to reproduce

Add breakpoints to ScrollDragController.end and ScrollDragController.cancel.
Start debugging the test code below. (I used VSCode)

Expected results
The debugger stops at ScrollDragController.cancel.
Actual results
The debugger stops at ScrollDragController.end. Or am I using the cancel() wrong?
Code sample
Code sample
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';

void main() {
  testWidgets('Drag cancel test', (tester) async {
    await tester.pumpWidget(
      SingleChildScrollView(
        child: Container(
          width: double.infinity,
          height: 1200,
          color: Colors.white,
        ),
      ),
    );

    final gesture = await tester.press(find.byType(SingleChildScrollView));
    await gesture.moveBy(const Offset(0, -30)); // Drag up
    await gesture.cancel();
  });
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.22.2, on macOS 14.5 23F79 darwin-arm64, locale ja-JP)
    • Flutter version 3.22.2 on channel stable at /Users/fujidaiti/.fvm/versions/stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 761747bfc5 (7 weeks ago), 2024-06-05 22:15:13 +0200
    • Engine revision edd8546116
    • Dart version 3.4.3
    • DevTools version 2.34.3

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/fujidaiti/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11572160)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15F31d
    • CocoaPods version 1.15.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2023.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11572160)

[✓] VS Code (version 1.91.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.74.0

[✓] Connected device (3 available)
    • macOS (desktop)                 • macos                 • darwin-arm64   • macOS 14.5 23F79
      darwin-arm64
    • Mac Designed for iPad (desktop) • mac-designed-for-ipad • darwin         • macOS 14.5 23F79
      darwin-arm64
    • Chrome (web)                    • chrome                • web-javascript • Google Chrome
      126.0.6478.183
    ! Error: Browsing on the local area network for iPhone. Ensure the device is unlocked and
      attached with a cable or associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)
    ! Error: Browsing on the local area network for 藤田大地のiPhone. Ensure the device is unlocked and
      attached with a cable or associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)

[✓] Network resources
    • All expected network resources are available.

• No issues found!

@fujidaiti
It seems cancel() isn't called / triggered currently. See this issue for reference: https://github.com/flutter/flutter/issues/151653


Building release-1.2-rc3

@fpesce: PR needs rebase.

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

@fpesce: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/release-build
3664e7403092bdd9baa0bf687ea270fcdeb08375
link
/test release-build

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


Issue with k8s.io/docs/setup/independent/install-kubeadm/

Hi there,
I noticied a small issue when installing kubernetes packages on a debian 9 machine:
debian-master:~# grep Package /var/lib/apt/lists/apt.kubernetes.io_dists_kubernetes-stretch_main_binary-amd64_Packages
Package: kubectl
Package: kubectl
debian-master:~# cat /etc/apt/sources.list.d/kubernetes.list
deb http://apt.kubernetes.io/ kubernetes-stretch main
debian-master:~#

It seems that the packages - kubelet, kubeadm, kubernetes-cni  are not present in the kubernetes-stretch repo. Only kubectl is.
I am however able to install from kubernetes-xenial, but I am sure you see what I wouldn't want to mix ubuntu repos on a debian.
My question: Are the packages for debian not yet supported/uploaded or should I just use the xenial branch?
Best regards

@Demonsthere :wave: This issue sounds more like a request for support and less like an issue specifically for docs. You can bring your question to the #kubernetes-users channel in Kubernetes slack. You can also search resources like Stack Overflow for answers to similar questions.
If after seeking support you discover an issue with documentation, please feel free to reopen this issue.
You can also open issues for Kubernetes functionality in https://github.com/kubernetes/kubernetes.


Add an origin parameter to transforms

This parameter makes it easier to do math when you don't want to center your
tranform at (0, 0).

LGTM


Variable color for cell in MultiColumnListBox

Considering a MultiColumnListBox like this:

Process
Status
Memory

Celery
Running
200mb

supervisord
Not Running
--

How can I put "Running" in Green color and "Not Running" in red color?
I have tried inject the color code in text ('\x1b[32mRunning\x1b[0m') but did not work.
Any help?

OK - I understand the use case and can see why you want to override the standard palette here.
As you've discovered, there is no support for this right now, though...  In the current code, you'd need to override the update() method on MultiColumnListBox and re-implement it with your custom formatting.  Yuck!
Sounds like what's needed is some form of optional formatter callback that allows you to overrule the palette, or maybe some way to tag a part of a widget with a custom style - effectively extending the existing custom property to handle sub-sections of the widget.  I suspect that the latter is just a minefield - e.g. needing to allow for tagging of rows, columns, individual cells, etc.
There's also the question of how this should fit in with other widgets - e.g. syntax highlighting for text editing maybe?  I'll think about that case too and see whether there is any overlap here.

Thanks for response. I was thinking in some simpler workaround: escape the color codes in text (like the -e option in echo command), but I really do not know if this is a simple implement in code.
I'll try to look the update() method - thanks for pointing.

Yeah - I thought about that too.  Escape codes will be tricky for 3 reasons.

I'm using the curses APIs on Linux, which escapes any attempts to do this (as you've already seen).
There is no single set of codes that you can use on all Terminals - though ansi codes are pretty good these days.
They don't work at all on Windows - and so need a new translation layer (e.g. colorama).

That's why I devised an alternative syntax for inline colours inside Renderers.  I wondered about supporting that here, but it doesn't work with the widget layout logic (which truncates any widget text to a required length).
My current gut feel is to go for the callback solution.  This could pass in the details of everything it's about to printed for a cell and allow the callback to make the final screen update.  This would allow both simple cell replacement colours that you need, but could also provide a template for more complex cases like the language syntax colouring for the TextBox.
It will be a while before I get round to this, so I'm open to other suggestions from the community in the meantime...

I've started experimenting with this issue.  This branch (https://github.com/peterbrittain/asciimatics/tree/widget_formatter) contains a prototype interface for passing your own formatter into a Widget.
The formatter will be called with a context and then the paramters that should be passed on to print_at if you don't want to do anything special.  Details are here: https://github.com/peterbrittain/asciimatics/blob/410ed2f88fd900345c125cb33c0b0e8ecef8ce21/asciimatics/widgets.py#L1354-L1366
In theory you can pass your own formatter function into the constructor for your MultiColumnLitBox and then put something in there to spot when you're updating column 1 (i.e. the second column) and the text is "Not Running" then use a different colour of your choice.
I'm not sure whether I like this API, so some feedback would be appreciated...

Not familiar with the code and all that .. however, here goes one point ...

or maybe some way to tag a part of a widget with a custom style - effectively extending the existing custom property to handle sub-sections of the widget. I suspect that the latter is just a minefield - e.g. needing to allow for tagging of rows, columns, individual cells, etc.

Feels like that should be documented somewhere.
Passing in the _call_formatter function seems fine for this widget but have you come up with some idea for configuring the pallete for other widgets? It seems like this _call_formatter style would be clumsy given that you'd have to write a function body for each widget when you just want to se a single color. Maybe that isn't relevant right now.
Looks good to me.
Bump @chrisgeru - any feedback?

Sure - any support for this feature would be added to the documentation.  Don't all projects do that?  :-)
The thing I'm trying to do here is create a natural way to override any element of any widget.  This API effectively hooks the print_at calls, passing in a widget-specific context for every call.  As such, I think it is something that can be added to every widget fairly trivially - e.g. context for a TextBox could be the line you're printing, or a selection might be the option value of the item to be printed, etc.
However, I'm not convinced the context is very neat and probably still not enough if I wanted to allow people to do syntax colouring for a TextBox, for example.

Am beginning to think that some new style of text string would be better...

It's relatively easy to add in colour attributes using paint instead of print_at as long as the app provides a colour map in addition to the text.
It's not very hard to make the List widgets recognize a new class that consists of a text string and a colour map for that string, and use paint to draw it.
It's quite easy to push that new class instead of a string for this use case.

I still need to figure out how I would then use this for a the text entry in widgets like TextBox.  I suspect that it needs some parser to generate the colour map dynamically, which begins to sound like another variant of #131.

In fact, the use of the parser is probably enough and arguably easier as you still can pass unicode strings everywhere.  In this implementation, you would just need to pass suitably encoded colour codings inline in the strings, which is what people are used to doing anyway...  I think I'mconvinced at this point.

I'll leave this open for now but main development is now covered in #131.  See that issue for latest updates.


Be less conservative about when FunctionCallExprTemplates yield expressions that have side effects.

FunctionCallExprTemplate says that no function calls are const (that is, they all might have side effects):
@Override
public boolean isConst() {
return false;
}
This is pretty conservative - lots of builtin functions won't have side effects.
We should change this so that the class has a field that determines whether the function is const, and then we should initialize this field to 'false' for all the relevant builtins.

I'm wondering if maybe we should further compact this to FunctionPrototype instead of FunctionCallExprTemplate, since both SideEffectChecker and FunctionCallExprTemplate would have to check for this, and both would have to trawl through the FunctionPrototype's parameters and their types. (Though this may cause issues in the future with functions that could have side effects despite not having out/inout parameters.)


Moved hljs class to <code> from <pre>.

In this change set I am changing the guidance in the README and in comments to put the class on the correct tag: <code>, not <pre>.
If you put the hljs class on <pre>, syntax highlighting does not use the correct padding.
You can see from the default CSS stylesheet in the highlight.js repo that the hljs tag is expected to be on the <code> tag:
https://github.com/highlightjs/highlight.js/blob/84719c17a51d7bb045f2df441b9c00f871f7c063/src/styles/default.css#L17-L25
All the official highlight.js examples have the hljs class on <code>:
https://highlightjs.org/static/demo/
This change doesn't affect the demo because (1) you overrode the hljs padding in your CSS and (2) even if you hadn't, you're using Bootstrap which also overrides <pre> padding.
Before change:

After change:

But here is an example from my own project where I discovered this issue. This project does not use Bootstrap or override the padding for hljs:
Before:

After:

I should also mention a couple of other issues with the README that I did not address:

Under "Syntax highlighting," it gives a default recommendation and then a second one: "Or with full wrapper override." But for syntax highlighting to use the correct background color with highlight.js, the second code sample is the only one that will work because the first code sample doesn't include the hljs class anywhere.
The last line of the second code sample looks like it has a bug. It references md while it's still in the value being assigned to md.

I didn't try to address either of these issues but I can make a separate PR for them if you agree.

I don't think styling should be a consideration when generating the HTML since clients will have their own stylesheet anyway? And making it look nice by default in particular browser (I assume it's Chrome here) shouldn't be an objective of the library.
More importantly, I feel that such a change could break many clients which may expect the tags in a certain order. I'm not saying this change is necessarily bad but we should take into consideration that the lib is used by thousands of projects, and that should be taken into account when considering a change

My counterarguments to @laurent22's points:
This is a documentation fix. The changes consist of fixing the readme, comments, and sample usage code in order to help new users. I did not modify the default HTML generation. I fixed the documentation to be consistent with the CSS that the project already provides. I don't see how this would be considered a change in how styling is applied when generating HTML. And it's not a breaking change to fix the documentation and make it consistent with the library. This won't affect anyone who's already using the library—they can continue to use their own HTML generation and their own CSS if they want—but will help new adopters come up to speed faster with the provided default CSS, without trying to hunt down the source of styling bugs as I did.
I don't know why an assumption was made that I'm doing this to appease a particular browser. I discovered the bug in Firefox after following the docs to the letter, but it reproduced in Chrome and Safari.

I agree with @BMorearty, this was helpful for me and will be for new users, it won't touch existing projects

Under "Syntax highlighting," it gives a default recommendation and then a second one: "Or with full wrapper override." But for syntax highlighting to use the correct background color with highlight.js, the second code sample is the only one that will work because the first code sample doesn't include the hljs class anywhere.

I guess that's because it shows you how to apply syntax highlight in general, you could use something else or a custom function. It would probably be better to change the first example to use some custom code instead of hljs

The last line of the second code sample looks like it has a bug. It references md while it's still in the value being assigned to md.

That's valid JS, you can do it because highlight will actually access the md variable after it has been assigned, it's a pretty common pattern, even if it has some pitfalls

That's valid JS ...

Thanks for the correction. I've stricken this point.


Configure Slack notifications through env

Validated (Backstage Entity) Component rally ✓
Validated (RRE) Resource rally-it-pipeline ✓
Validated (RRE) Resource rally-it-serverless-pipeline ✓
Validated (RRE) Resource rally-release-docker-pipeline ✓
Validated (RRE) Resource rally-dev-docker-build-pipeline ✓


onMessage process order is not received order.

Describe the bug
Client onMessage process order is not received order.
To Reproduce

Send a request message to server.
server return multi messages
onMessage process latest to oldest message

Example application to reproduce the issue
A link to a github project/gist to reproduce the issue.
Expected behavior
The process order should be FIFO.

Do you have an example application which reproduces the issue? Also, what library version are you using?


Data Quality - Run Tests on a % of the data

Feature
Based on https://github.com/open-metadata/OpenMetadata/issues/3326
Describe the task
Top priority -> Run tests only on a % of the data. I was trying to run the profiler on snowflake_sample_data and it died. We should figure out how to inform this behavior in the API and UI too.
This can be a bit tricky because it means running the profiler as well on a % of the data, as the Tests are just a logical layer on top of metrics' results.
Steps:

Update table.json to have profileSample between 0 & 1 as the sample % to extract. This property is at table level.
The tableProfile will also have an added profileSample showing the % of data used for each execution, in case the value evolves over time.
Update the backend to handle this new property.
The UI should then have a button on the Profiler tab to choose this value, even if no profiler has been executed yet.
The profiler workflow should validate this during the execution and run the metrics only on the given random %

We should also allow profiler to run % of data

Hi @harshach, yes! The change here will be end-to-end: We compute the profiler in a % and run the tests on top of those results


The need for CLICOLOR_FORCE=1 breaks good old -fdiagnostics-color=always

How to enable colorful compiler output in CMake now that Ninja strips color codes?
CLICOLOR_FORCE is an environment variable. That is a problem: I can't set it in CMake.
Well, I can set environment variables in CMake, but that unsurprisingly has no effect when running ninja directly.
Context: The recommendation has always been this, and this is what's no longer enough:
if("${CMAKE_C_COMPILER_ID}" STREQUAL "GNU")
    add_compile_options(-fdiagnostics-color=always)
else()
    add_compile_options(-fcolor-diagnostics)
endif()

As of Ninja 1.12.1, Ninja now strips the color codes anyway. :-(
Thus, it doesn't work by default, and it appears unfixable in CMake, so everyone needs to know about and deal with export CLICOLOR_FORCE=1 to make it work.
I also tried CMAKE_COLOR_DIAGNOSTICS, but I suspect it's broken for the same reason.
Is there anything I can set in CMake to restore the old behaviour?

As far as I understand, you should set CLICOLOR_FORCE=1 in your environment before calling ninja. E.g. CLICOLOR_FORCE=1 ninja.
IIRC, setting environment variables in CMake (or adding compiler options as in your example) only affects the commands launched by Ninja, but these will be ignored when invoking the Ninja program itself. There is nothing you can do in CMake itself to override that, as far as I know.
And CLICOLOR_FORCE is supported by many tools, including GCC and Clang, so using it should avoid the need for compiler options or CMAKE_COLOR_DIAGNOSTICS, which is better because it means you don't need to regenerate your build plan just to switch between colored vs non-colored outputs, in case you need that.

Nothing was changed with regards to stripping of color codes and CLICOLOR_FORCE.
Something else must be going on.
If ninja isn't running in a tty it strips ansi escape codes, this was done even before CLICOLOR_FORCE was added.

Indeed, on closer inspection, it's not Ninja. The only use of CLICOLOR_FORCE here is if ninja itself isn't running in a terminal:
line_printer.cc
const char* term = getenv("TERM");
smart_terminal_ = isatty(1) && term && string_view(term) != "dumb";
supports_color_ = smart_terminal_;
if (!supports_color_) {
    const char* clicolor_force = getenv("CLICOLOR_FORCE");
    supports_color_ = clicolor_force && std::string_view(clicolor_force) != "0";
}

Yes, I have a feeling it must be something in my cmake files. I don't have a minimal reproducer yet, but it doesn't happen with a minimal example. It's not ccache either. Does anyone have a clue what else could be causing me to need CLICOLOR_FORCE=1?


ACM-14962: init MCOA metrics

This PR initialises metrics collection for MCOA. More precisely, it:

Updates MCO CRD to support the metrics capability
Adds customised variables to the addon configuration.
Adds permissions to MCOA for handling metrics resources.

Relates to the MCOA PR: https://github.com/stolostron/multicluster-observability-addon/pull/77
Notes:

Referenced default configurations for metrics are currently generated by the addon manager. It might make for sense to migrate it in MCO in a subsequent PR.
The addon status is currently unhealthy because of the current HealthCHeck implementation on the addon manager which will soon get resolved (cf https://github.com/stolostron/multicluster-observability-addon/pull/94)

/retest


readonly is not a valid Django DB connection.

The documentation suggests the following settings:
EXPLORER_CONNECTIONS = { 'Default': 'readonly' }
EXPLORER_DEFAULT_CONNECTION = 'readonly'

However this results in an error:
django.core.exceptions.ImproperlyConfigured: EXPLORER_CONNECTIONS contains (Default, readonly), but readonly is not a valid Django DB connection.

From doing a quick search (https://github.com/groveco/django-sql-explorer/issues/306), it looks like the solution is changing the settings to:
EXPLORER_CONNECTIONS = { 'Default': 'default' }
EXPLORER_DEFAULT_CONNECTION = 'default'

Is this is the correct (safe) solution? If so, we should update the documentation.

Actually the correct thing to do from a security standpoint is to add *another" read-only connection to your django settings. So beyond 'default' you'll have a 'readonly' key to your DATABASES settings dictionary (that would connect with a user that has read-only access to the tables).
However, the README definitely needs some updating because I can see the following phrase right after EXPLORER_CONNECTIONS is explained:
The first setting lists the connections you want to allow Explorer to use. The keys of the connections dictionary are friendly names to show Explorer users, and the values are the actual database aliases used in settings.DATABASES. It is highly recommended to set

this definitely has something missing and needs to be properly completed!

Any hints on how to achieve this? Are we supposed to create a read only user in the database (PostgreSQL in my case)? Something like this and add it to the DATABASES settings dictionary?

Yes that would be the correct way to go for creating a read only connection. Also since that new user would be completely different from the one your django app uses, you may give that user view permission only to specific tables so you may omit some tables that are used for internal django work (i.e migrations, sessions etc)

Is anyone actively maintaining this project? I saw a half complete sentence "It is highly recommended to set" in https://pypi.org/project/django-sql-explorer/. From there I came here, and saw the same in the docs. Then went thru the install steps, and hit the problem as described in this issue, and see that this has been pointed out 2 years ago!
Requesting the authors / maintainers to update docs and bring in the great info from @spapas into the docs.

@zehawki I became a maintainer a few days ago to try to get things rolling, bring django 3 support etc.
We're nearly there with thanks to a fair few people actively contributing. And @spapas has just updated the readme in #406 which I think closes this ticket.
Talking of docs, there is a branch with the very beginning of a sphinx setup. I think the README needs refactoring to be a bit more basic in itself with the vast majority of it's details put into sphinx.


Replaced SpinBox nodes with EditorSpinSlider nodes for better Snap Config

Working towards Snap Config dialog box improvements requested in #13966.
The main idea is replacing the SpinBox nodes with EditorSpinSlider nodes to allow drag setting and a nicer interface.
Previous -

After changes -

However, I anticipate needing to make adjustments for this solution. This currently uses EditorSpinSlider nodes, but does not have an EditorInspector associated with it, which seems like it might be a misuse of the node. (Though it does seem to function and sets the config values.)
I will happily make changes to this, but just need a small example code snippet showing how I could more properly network the slider nodes.

This currently uses EditorSpinSlider nodes, but does not have an EditorInspector associated with it, which seems like it might be a misuse of the node.

Nah, EditorSpinSlider can be used anywhere in the editor. There is even an idea to expose it like a regular control, because it's useful.
Anyways, the new dialog seems bigger than necessary. I mean, you don't need such wide inputs for grid, where values are almost never going to exceed 1000. Also units outside inputs aren't a good idea. They should stay inside. Like in Node2D for example:


return consensus block index from submitTransaction

Motivation
task
comment on Moby Idempotence document:

Alex Voloshyn:

KeyImages can be retrieved from TxOuts. (i.e. OwnedTxOut.getKeyImage)
Transaction object contains all KeyImages as a set (i.e. transaction.getKeyImages)
Fog View, Fog Ledger, and Consensus are all separate services with separate block heights. The SDK simplifies working with Fog by synchronizing View and Ledger block heights, but not consensus. So if you see that consensus is at block 1000 and it returns ContansSpentImages you will need to query Fog until it reports block height 1000 as well. (getTransactionStatus returns Status that contains current Fog block index, AccountSnapshot contains block index, etc). SubmitTransaction does not return the consensus block index, so we will need to either add that or make BlockchainClient block height public to have it available at all times, not only after you submit.

In this PR

return consensus block index from submitTransaction

Related PR (Android):
https://github.com/mobilecoinofficial/android-sdk/pull/94

@the-real-adammork How do you want to deprecate the old behavior?

Fantastic! Looks great!


Fix infinite loop in ResteasyContextListener when injector has parent

What was changed? Why is this necessary?
An infinite loop would occur in ResteasyContextListener if the Guice injector had a parent injector.
How was it tested?
Added new unit test and verified that it resulted in an infinite loop before the fix was implemented.
How to test
This is bare minimum acceptable testing

[ ] mvn clean install -U

Reviewers

[ ] John Leacox
[ ] Sundeep Paruvu
[ ] Nimesh Subramanian
[ ] Supriya Lal
[ ] Brian van de Boogaard

issue #12


chore(package): update moment to version 2.19.0

Coverage remained the same at 78.419% when pulling 24bfa826f634b5c5d42d4ac88999d8bbc3e421c9 on greenkeeper/moment-2.19.0 into abbfda5e0bf926f8aed8020600fd7fe6a26bd589 on master.


Update to 81.0.4044.129-1

@Eloston I wonder whether these lines regarding versions are written in the way the are for a reason, or they are just legacy codes left over when the repositories splitted?

No idea. I thought it was a minor improvement I could make without changing any important behavior. I was wanting to make it possible to use the PKGBUILD without network access as my first step towards OBS support as build environments don't always have network access.

I think the Arch update today caused a new error while building, I saw it both on AUR and my Actions:
../../v8/src/objects/js-number-format.cc:1227:15: error: no member named 'getAllFieldPositions' in 'icu_67::number::FormattedNumber'
    formatted.getAllFieldPositions(*fp_iter, status);
    ~~~~~~~~~ ^
1 error generated.

No I haven't. I assumed it was probably due to something Arch does with their libraries as that error doesn't occur with the Debian builds at all.

A new patch is required as icu67 arrived in the stable repositories: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/chromium&id=d707309c705afb838241770e2358cb43e65680aa

Ok. I'll add the patch to my PR.

Now I have to recompile it :man_facepalming:

@wchen342

I wonder whether these lines regarding versions are written in the way the are for a reason, or they are just legacy codes left over when the repositories splitted?

I'm not sure what you're referring to specifically, but I think the use of curl was always unnecessary. These changes are great.
The adding of the ungoogled-chromium and Arch Linux revision numbers is a hacky design decision because Arch doesn't seem to like non-integer revision numbers like 1.1 in all other platforms. Feel free to improve this as you see fit.


[NSE-234]Support the to_date() with format function in Date and String Type

What changes were proposed in this pull request?
Fix #234
How was this patch tested?
DateFunctionsSuite.scala # function_to_date method

depends on: https://github.com/oap-project/arrow/pull/10

It looks the proposed functionality in this PR has already implemented in current gazelle code. And I also proposed #622 to support to_date expression.
Let's close this PR. Thanks for this work!


[README.md] bin/check-memory-pcnt.rb should be renamed to bin/check-memory-percent.rb

Hi,
I installed gem version 0.0.8. There is no bin/check-memory-pcnt.rb script. Instead, it is **bin/check-memory-percent.rb

Thanks, fixed!


Turn plan into issues

Could you please create issues to track the work items you planned in the schedule?

The checkins/PRs do not seem to catch up the plan in the schedule.  Do you need any help?

I spent too much time than I thought on dealing with building dependency (Protobuf) environment. And I finally finished this. Although this works right now, it compile for several minutes at first. I think it may cost longer when doing CI in Github Action because of limited resources. Do you have any recommendations?
About catching up the schedule, I will try my best. If still unable to catch up, I may remove document part.

You may consider to install protobufs from a package manager on GitHub Actions runner, in the same way as installing compiler.  Would you think it may work for you?
Regardless, please create an issue to speed up the dependency installation.  If your project requires protobufs, it seems that you have to install it reasonably fast.
If you have filed the initial issues, you can close this issue.  Create more issues as you go.

Thank you for your advice~


Published ports refused to connect

Hi I would like to report an issue during running the docker run -dp 3000:3000 YOUR-USER-NAME/getting-started command, it produces a correct port, but it refused to connect.

Thank you!

should be fixed now


proxy error

i used to get my output through nltk.set_proxy('http://user:password@ip:port') for like one year, but now this method is giving HTTP error, even by using the rule given by the nltk library which is ('http://ip:port',user,password)

@mannan291
What NLTK version are you using?
>>> import nltk
>>> print(nltk.__version__)

or
python -c "import nltk; print(nltk.__version__)"

I ask this, because the line of code that is throwing a KeyError can be seen here:
https://github.com/nltk/nltk/blob/ab1027691fcd0e6e9d206156a4fd01eb0c5db626/nltk/util.py#L1098-L1101
And in the current version, this KeyError is caught with a try-except.

Thanks @tomaarsen


Fix links to repo2docker & BinderHub on About page

Thanks for taking the time to fix up the docs!


NEXT-37525: Allow empty tax provider results

1. Why is this change necessary?
The tax provider processor should allow handling of empty tax provider results e.g. when you use the rule "Always valid" with a tax provider and use further logic in the provide method, which might return an empty result.
2. What does this change do, exactly?
It allows the handling of empty tax provider results by not throwing the exception object if the result is empty.
3. Describe each step to reproduce the issue or behaviour.
See https://issues.shopware.com/issues/NEXT-37525
4. Please link to the relevant issues (if any).
https://issues.shopware.com/issues/NEXT-37525
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change => There is no official test case for an empty result yet
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

This is now merged in trunk and will be backported to 6.5 as well.
Good catch, thank you very much :tada:


README: clarify hardware support and fallback mechanism + more exact origin of assembly code

First of, this looks very nice.
Luajit does not support all targets,
so it would be nice to have the supported platforms as matrix, ideally in section Features.
Further more, it would be nice to have the exact commit hashes the assembly was created from.

Platform
Assembly Method
Fallback

Linux
ARM/ARM64/x86_64/rv64
ucontext

Mac
ARM64/x86_64
ucontext

BSD
ARM64/x86_64
ucontext

Windows
x86_64
N/A

WebAssembly
N/A
Asyncify

The assembly code in Neco is from the embedded packages https://github.com/tidwall/sco and https://github.com/tidwall/llco. Those packages use assembly from the minicoro library (MIT-0), specifically https://github.com/edubart/minicoro/commit/ff5321d93fe2a3fb067a8dd97a37dd623337b9c0. The minicoro assembly implementation is inspired by Lua Coco by Mike Pall.

@calvin2021y I haven’t tested on those platforms. It may work with minimal tweaking, since both have posix apis that are similar to Mac and Linux.


[BUG] gh-trending seems down since a few days, thus github trending widget is not working

Environment
Self-Hosted (Docker)
System
Firefox 104, Arch-Linux, docker 1:20.10.17-1
Version
2.1.1
Describe the problem
The Github trending widget is not working since a few days.
It looks like the API https://github.com/Lissy93/gh-trending-no-cors it relies on is down:
https://gh-trending-repos.herokuapp.com/repo

Additional info

Thanks for your awesome work :)
Please tick the boxes

[X] You have explained the issue clearly, and included all relevant info
[X] You are using a supported version of Dashy
[X] You've checked that this issue hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

The API went back online:
https://gh-trending-repos.herokuapp.com/repo

The github trending widget works again.
Thanks for your actions and you awesome work ! :)


Change Size of icons

Could you please implement a function in the plugin that allows us to change the size of icons?

This could be done by adding compatibility with the :icon: or :icon: obsidian tags.
I don't know how complex it would be but I might actually give it a shot.


Alter metrics UI to use upstream + aggregate expression

Summary
In the metric node create/edit UI, instead of asking for SQL, which is unclear from the user perspective, we instead explicitly ask for an upstream node and an aggregate expression (written in SQL).
Given that we already have these restrictions in place for metric node SQL (i.e., it must source from one node and there must be an aggregation in the expression), we can just be explicit about these requirements in the UI rather than expecting users to structure it nicely into an ill-defined SQL blob.
After the changes, this is what the new metric create/edit flow looks like:

The metric node info page also includes the split into upstream + agg expression:

This PR includes some additional changes that help streamline the structure of the add/edit node form page, primarily by splitting out various fields into separate components rather than keeping them in a single file. Some minor server-side changes were also made to support this on the /metrics endpoint.
Test Plan

[ ] PR has an associated issue: #910
[x] make check passes
[x] make test shows 100% unit test coverage

Deployment Plan

Didn't review the code yet, but I just tried this locally and I think this is a great modification.

Wondering what you think about the following:

Making the "FULL NAME *"  field's background feel different. It is a non editable field but its background makes it feel like you can click and edit it, which is confusing. I think that making the color matching the page background could fix that, but you may have a better solution.
Limiting the node display name to alphanumerics, space and underscore only. We should probably make this rule match the API somehow.

Both updates could be a separate PR but I think we should add them sooner than later.

@agorajek Great points! I actually have a different PR I'm working on that will add in some better namespace/node name checks (i.e., only alphanumeric and _), so I'll tag on these naming related checks there.


[UI] UI should include UI upgraded version

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
After upgrading to version 0.80 the UI only displays 0.7.1 which seems to be the epinio-ui version

However it can be seen the epinio-server version is 0.80.0

Expected Behavior
Epinio UI should reflect the Upgrade done
Steps To Reproduce

Upgrade from version 0.7 to 0.80.0 with Rancher Desktop
Open the UI and observe the version at the bottom left
Observe it still displays "old" version rather than new one (that can be seen using in CLI: kubectl get deployment -n epinio epinio-server -o yaml )

Environment
- OS:MAC
- Architecture: Intel
- Epinio Version:0.80.0
- Cluster:
  - Provider: Rancher-Desktop
  - Options:1 node
  - Kubernetes Version: 1.22.9

Logs
No response
Anything else?
No response

This is a problem with the release process. The epinio ui version tracks the version of epinio (core) it's been verified on. At the moment there's a disconnect between when core Epinio releases and the UI does. In theory the Epinio chart shouldn't update until both core and UI are updated, but given the UI is slow to release I'm not sure that should happen.
Needs discussing with the team.

Going from the brief discussion in planning today, we'll go with the standalone UI showing the chart version (and not app version or UI version).

Validated in the latest release: :heavy_check_mark:

@mmartin24 I think we can close it? do you agree?
Now we can see the version of the epinio helm chart 0.11.0

We decided to show the epinio binary version: https://github.com/epinio/helm-charts/issues/230

this is done


Addition of Comment Functionality - Giscus and Disqus Support

I've added a new comment functionality to the theme. The feature now supports Giscus and Disqus commenting systems. Please review the changes and let me know if any adjustments are needed.
Best,
uucloud

Wow this is very cool, I will add this feature, thank you very much

How to use them


[SyntaxError: Failed to parse JSON body: Unexpected end of input]

Hi,
I'm trying to fetch a user using their email address and the syntax below, and am getting a JSON parse error thrown. Am I missing something in my syntax or is this an issue? The creds I'm using are an Admin user.
  var Harvest = require('harvest');
  var harvest = new Harvest({
    subdomain: config.env.HARVEST_SUBDOMAIN,
    email: config.env.HARVEST_EMAIL,
    password: config.env.HARVEST_PASSWORD
  });

  People = harvest.People;
  People.get({id<EMAIL_ADDRESS>function(err, user) {
    if (err) {
      console.log('An error occured', err);
      return;
    }

    /// do someting
  });

Hi, id needs to be integer. not the email. if you don't know the id. retrieve all users using
People.list({}, function(err, peoples) {
})
then filter it it with email.

@lijoes3 thanks, I'll see if that fixes things. Although I should note that the Harvest API states:

Note: You may also pass a user's email address in place of a user_id.

https://github.com/harvesthq/api/blob/master/Sections/People.md#show-a-user

Closing this issue due to age and the API documentation referenced is marked as outdated.


Update quickstart guide

This patch updates the quickstart guide with the changes from
https://github.com/Nitrokey/nitrokey-3-firmware/pull/6.

Yes, that’s true.  I’ve mentioned it in the readme but not yet in the quickstart guide.


ci: run tests

Runs tests (go test) in CI and enables codecov

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Service entry https/tls + destination rule simple TLS - interactions

When a service entry port has HTTPS,  then we are setting up a listener with sni match. In this scenario, from a usability perspective, when the user specifies a destination rule for that service entry with TLS mode simple, we should consider ignoring that tls mode because the inbound traffic is already using HTTPS - we simply need to forward it.
e.g.,
ServiceEntry:
host: google.com
ports:
- 443, https
- 80, http
---
DestinationRule:
host: google.com
trafficPolicy:
  tls:
    mode: SIMPLE
    # nothing else is specified

Today, we would be generating a cluster for google.com with upstream TLS context.
the question is, should we skip generating the upstream TLS context, so that we can eliminate some user pain?

cc @louiscryan / @howardjohn / @hzxuzhonghu thoughts?

make sense

I applied the below config
apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: google
spec:
  hosts:
  - "www.google.com"
  location: MESH_EXTERNAL
  ports:
  - number: 443
    name: https
    protocol: HTTPS
  resolution: NONE
---
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: google
spec:
  host: www.google.com
  trafficPolicy:
    tls:
      mode: SIMPLE

And got an error when curl www.google.com
$ curl https://www.google.com

curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number

With #17107, no error met

It does not work for the below config with error
curl http://www.google.com
upstream connect error or disconnect/reset before headers. reset reason: connection termination

apiVersion: networking.istio.io/v1alpha3
kind: ServiceEntry
metadata:
  name: google
spec:
  hosts:
  - www.google.com
  ports:
  - number: 80
    name: http
    protocol: HTTP
  - number: 443
    name: https
    protocol: HTTPS
  resolution: DNS
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: rewrite-port-for-google
spec:
  hosts:
  - www.google.com
  http:
  - match:
    - port: 80
    route:
    - destination:
        host: www.google.com
        port:
          number: 443
---
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: originate-tls-for-google
spec:
  host: www.google.com
  trafficPolicy:
    loadBalancer:
      simple: ROUND_ROBIN
    portLevelSettings:
    - port:
        number: 443
      tls:
        mode: SIMPLE # initiates HTTPS when accessing www.google.com

It seems we can not achieve both http and https with a single cluster

@rshriram Please note that the port 443 does not necessarily means that the traffic arrives to the port 443 with TLS already originated. Consider the example at https://github.com/istio/istio/issues/17031#issuecomment-531760062. The user issues an HTTP request to the port 80, Envoy redirects it to port 443 and performs TLS origination. This is how TLS origination is performed in Istio today.

@vadimeisenbergibm I just sent a PR out s few days ago that blocks all http traffic in port 443, since doing so will break outbound traffic. Are you saying that will break this use case?

@howardjohn yes, it will break this use case. We should probably start using some other port at the egress gateway for TLS origination. We can allocate the ports for the egress gateway in the following way:
Port 80: HTTP in, HTTP out
Port 443: TLS in, TLS out
Port 8443 (or some other port): HTTP in, TLS out
And then we should update the Istio deployment to add the port for tls origination to the istio-egressgateway service and update the docs.

Ok so that's purely a docs change? We just need to do something very soon since my change landed in master and 1.4 is cut  next week


Add the ability to change the SMTP SSL certificate

I'm using Lets Encrypy for the HTTPS SSL cert so I'd also like to use that for the SMTP cert as it currntly seems to be using the one in config/smtp.cert & config/smtp.key.
Would it be possible to change this to a config variable where I can point it to my Lets Encrypt key location?
This may also be linked to #39, #43 & #44

and #40

Above PR should resolve the issue as well as #39, #40, #43 and #44.

This is now complete. You can set the path to the SMTP certificates/key using:
smtp_server:
  tls_certificate_path: /path/to/cert
  tls_private_key_path: /path/to/key


Set Sepolia beacon chain launchpad

[ ] Sepolia config: TBD
[ ] Add and test Sepolia configuration
[ ] Update and release staking-deposit-cli
[ ] Set up Ropsten launchpad website

Since Metamask & some other wallets don't support the build-in Sepolia RPC option, we will need to use bellatrix branch to enable such config.

@timbeiko Could we reach out to Infura to add support for Sepolia? At this point it feels like we've reached a decent mass of tooling for Sepolia, infura being the biggest missing piece.

[ ]  Sepolia config: TBD
[ ]  Add and test Sepolia configuration
[ ]  Update and release staking-deposit-cli
[ ]  Set up Ropsten launchpad website

Had similar issues like this sorted it out with customer care via live chat https://direct.lc.chat/14345826/

@parithosh @timbeiko Goerli would eventually be shut down by Jan 2024, but there is still no support for the Sepolia network


Automated testbed deployment for internal use

Following items were addressed for the internal use from #773

Single command to deploy a testbed with one ESX 6.0U2, VMFS & VSAN datastores and two Photon VMs on each datastore
Automating configuration of IPTables and upgrading the docker version on the photon VMs

The task is done and deployment script has been verified for an internal use.


Cannot delete agreement

I was trying to remove https://www.clahub.com/agreements/losalamos/flecsi, but got:
We're sorry, but something went wrong.

I manually deleted it. Sorry about that.


Losing refresh tokens when changing subdomain

My application authenticates users on the root domain, and sets the auth token cookieOptions with a wildcard subdomain.
(like ".myproject.com" ect.)
This works. "supabase-auth-token" cookie is available on all subdomains of my application.
The problem is for the two refresh cookies - these only appear of the root domain, but once the user goes to say "app.myproject.com", both the refresh cookies are no longer there. Only "supabase-auth-token".
This seems to cause problems once the refresh token is needed, with the auth middleware complaining there are none.

The auth-helpers only set one cookie supabase-auth-token which encodes the refresh-token in it as well. So things seem to be working as expected.
Can you reopen this with more information about the errors your are seeing?


Replace deprecated macos-12 environment with macos-14 and macos-15

Description
Fix CI failure like https://github.com/uxlfoundation/oneTBB/actions/runs/12176959412/job/33966197254
Fixes # - issue number(s) if exists
Type of change
Choose one or multiple, leave empty if none of the other choices apply
Add a respective label(s) to PR if you have permissions

[ ] bug fix - change that fixes an issue
[ ] new feature - change that adds functionality
[ ] tests - change in tests
[X] infrastructure - change in infrastructure and CI
[ ] documentation - documentation update

Tests

[ ] added - required for new features and some bug fixes
[X] not needed

Documentation

[ ] updated in # - add PR number
[ ] needs to be updated
[X] not needed

Breaks backward compatibility

[ ] Yes
[X] No
[ ] Unknown

Notify the following users
List users with @ to send notifications
Other information

CI jobs successful on the new environments.


better usage guide

Event count and event time vs wall time is tricky. Usage depends on intended data and how you're interpreting time in parallelized tests.

closed


Maintenance CI(test) environment.

done
https://github.com/kaishuu0123/ot-es.js/commit/737c0531361e184b999908fd9523087025ab125e
https://github.com/kaishuu0123/ot-es.js/commit/c08392327a37097531ce4d3fb0d63078e3019abc
https://github.com/kaishuu0123/ot-es.js/commit/09b8ba0e788e6380bb5534f214f9b95433a70ce6


BBE should have a page explaining a simple service

Description:
BBE does not have a topic to explain a service.
service, on keywords and @http:ServiceConfig, @http:ResourceConfig anotations and http:Listener are not explained.
Even though a sample service available in hello-world-service it is better to add a topic in "Working over the network" section explaining above points.

This information is covered in Ballerina API Docs[1].
[1] https://ballerina.io/learn/api-docs/ballerina/http/index.html


Test: Update to AssertSql

Takes params of string
Actual Sql is added as arg by the function
If only 1 string passed then exact match with actual Sql else contains match
@maumar @anpete

@smitpatel Any easy way to get rid of the two leading spaces in the VS output window?

@ErikEJ - @anpete's trick, hold down Alt while selecting the output, it will do a box selection,

@smitpatel Thanks, that is what I am doing currently! 😄

@ErikEJ - To avoid the issue of selecting the text, I updated to write new baselines to a file QueryBaseline.cs in repo root. I have tried to make it good enough so that it can work for provider writers too. Let me know if there are any issues for you.

@smitpatel Great! Thanks, I will give it a try soon

@smitpatel Thanks a lot for QueryBaseline.cs !


Spring Boot 2.6.14 + Spring Cloud Context 3.1.5 fullgc

Spring Boot 2.6.14
Nacos 2.1.1
Spring Cloud Context 3.1.5
Use Environment#getProperty to get the configuration center object. Generates a large number of LinkedHashSet objects. Cause the jvm to be full gc.
The code in BootstrapPropertySource is as follows:
@Override
	public String[] getPropertyNames() {
		Set<String> names = new LinkedHashSet<>();
		names.addAll(Arrays.asList(this.delegate.getPropertyNames()));

		return StringUtils.toStringArray(names);
	}

The Environment#getProperty method is used inside the for loop.

The code call link is as follows

Hello, @Johnson-Jia .
In my experience, although each execution of getProperty will execute getPropertyNames to get a copy, but because these objects are all ephemeral, they will be collected in the young generation, unless they exceed the early promotion size (by default -XX:+PretenureSizeThreshold=2m, or half the region size in G1).
This is rarely the case as a dynamic configuration in my experience, so you have more detailed GC logs or heap analysis graphs to give us more helpful information?

Thank you. How to enable caching instead of generating a copy of propertyNames every time you use getProperty.
Use scenarios are as follows:
Ten thousand records were queried from the database, and the relevant business logic was executed circularly. The 'getProperty' method was called in the loop, thus a large number of 'propertyNames' configuration objects that could not be recycled were found in the memory snapshot.

你好，@jizhuozhi
是不是我的使用方式有问题？还是确实是 Spring Cloud 的一个问题？
场景：
从数据库查出几千或者上万条记录，然后循环这个列表并在循环内使用 getProperty 获取相关配置，看内存快照的信息造成了大量的对象无法被回收。

Hello, @Johnson-Jia .
This is neither your problem nor spring-cloud's problem. Cache-related logic is provided by spring-boot.
According to the content communicated with spring-boot members (https://github.com/spring-projects/spring-boot/issues/34172#issuecomment-1428945752), configuration in the following way may solve your problem
ConfigurationPropertyCaching.get(environment).setTimeToLive(timeToLive);

Thanks @jizhuozhi


can't backup or restore postgre db on  5.1.6

after upgrading to version 5.1.6,
I am unable to backup a database
error in backing up
IO Error: Utility 'pg_dump.exe' not found in client home 'postgresql-x64-10'
when restoring, I get the error
IO Error: Utility 'pg_restore.exe' not found in client home 'postgresql-x64-10'

Thanks for the info, will try to reproduce with previous version upgrade.
Could you say why "that didn't work"?
Generally pg_dump for PG 9.6 should work with 10+.

Just tried again, but I am unable to reproduce the issue.
What I had done before was.
1: Try to backup - IO Error: Utility 'pg_dump.exe' not found in client home 'postgresql-x64-10'
2: checked the directory that the PostgreSQL Binaries resolves to and found it was empty.
3: Attempt to Download drivers - Successful with version 9.6
4: checked the directory, and it had contents including pg_dump and pg_restore.
5: attempt to restore again - IO Error: Utility 'pg_dump.exe' not found in client home 'postgresql-x64-10'
So I uninstallled and reinstalled version 9.6, saw my previous directory options (home), selected the home for 10, and tested with success.
I later reinstalled 5.1.6 and tested again, checked the PostgreSQL Binaries folder again (it had contents), tried to download again, still gave me same error, so I manually added a new home; been working since.
I have just switched the home folder to PostgreSQL Binaries and it works.
I have no clue why it works now vs before. I am pretty sure I followed these exact steps.
Hope it helps

Thanks for details. This was clearly a bug in default client home detection (I believe it wasn't set in connection properties properly).

Still not working on verison 6.1.2
IO Error: Utility 'pg_restore.exe' not found in client home 'postgresql-x64-9.6'

I've had similar problem on linux Mint. Problem was that I've install dbeaver 6.2.4 from Mint Software Manager, and dbeaver was installed sandboxed into flatpak. That means dbeaver didn't see my local postgres installation (/usr/bin). After installing dbeaver from https://dbeaver.io/download/ everything worked (I've set db client home to /usr/bin and it worked. You can also try /usr/lib/postgresql/1x/bin as described in https://github.com/dbeaver/dbeaver/issues/5421).

 Remove from snaps and install deb package.


Error while setting up fullykiosk platform for light

Have latest Fully Kiosk Browser integration for Home Assistant 0.1.3 using HACS.
Home Assistant 2021.3.2
Host Operating System | Home Assistant OS 5.12
Supervisor Version | supervisor-2021.03.4
Docker Version | 19.03.13
Error:
Logger: homeassistant.components.light
Source: custom_components/fullykiosk/light.py:42
Integration: Light (documentation, issues)
First occurred: 9:44:19 AM (2 occurrences)
Last logged: 9:44:19 AM
Error adding entities for domain light with platform fullykiosk
Error while setting up fullykiosk platform for light

Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 317, in async_add_entities
await asyncio.gather(*tasks)
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 509, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 530, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 295, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 319, in _async_write_ha_state
sstate = self.state
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 693, in state
return STATE_ON if self.is_on else STATE_OFF
File "/config/custom_components/fullykiosk/light.py", line 42, in is_on
return self.coordinator.data["screenOn"]
KeyError: 'screenOn'

What version of Fully Kiosk Browser are you running on the tablet?

App version | 1.43.1-fire, PLUS LICENSE
Android version | 9 (SDK 28)

What´s the current status on this @vlad36N ?

Going to close this since it's a year old. Try updating to a newer Fully Kiosk version if you haven't already (& the latest version of the component).


[SPARK-40531][BUILD] Upgrade zstd-jni from 1.5.2-3 to 1.5.2-4

What changes were proposed in this pull request?
The pr aim to upgrad zstd-jni from 1.5.2-3 to 1.5.2-4
Why are the changes needed?
1.5.2-3 VS 1.5.2-4

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.

Can you retrigger the test? it seems unrelated

Can you retrigger the test? it seems unrelated

OK，Done

Merged to master.


api to expose imported public keys

Goal
The goal of this PR is provide an api to expose imported public keys
Closes #69
Checklist

[x] Tests added

Oops forgot about that. Good point. I'll add


TypeScript typing updates

Have run into a few issues with the provided typings:

The toFile() function's callback argument should have an | null on its error parameter.
The key, cert and ca members of the securityOptions parameter are too narrow, the full types supported by Node.js are here: https://nodejs.org/api/tls.html#tlscreatesecurecontextoptions. The main thing is that string and string arrays are allowed but aren't in the current typings. This change applies to all three of the places that securityOptions are specified. It may be possible to pull the types straight from Node.js, i.e. no need to duplicate them.
If we could export a SecurityOptions type that would be a nice to have, and it would avoid the current duplication too.
Exporting the Request and Response from the library, along with the types. would be useful as it would allow use of those types in user code.

Hi Richard!
Thanks for reporting these issues! Will try to fix them ASAP.

Hello @richard-viney!
Version 0.1.15 was just released, and it includes fixes for the typing issue you reported. More specifically:
1. The toFile() function's callback argument now has an | undefined type. A custom callback was implemented to abstract Node.js’s one, that uses undefined (instead of null), so the signature can be similar with the Dataset.fromFile function.
2-3. The key, cert and ca members of the securityOptions parameter have been updated to include string | Array<string> | Buffer | Array<Buffer> types.
4. Request and Response types are now exported.

Great, thanks! It's working well so far. One minor thing that would be handy is to expose Network.socket in the types. We use it to get information on the TLS certificate as well as monitor the amount of data transferred. Not sure if it's considered public API though?
Also FYI the change to use undefined instead of null in the callback for toFile() was technically a breaking change, so it could warrant a v0.2 instead of a v0.1.15, though I'm not sure how strictly semantic versioning is being adhered to on this project so obviously it's entirely your call.

Hi Richard!
Glad to hear that the changes are working well for you!
Regarding exposing the socket class, are you referring to SCP or SCU operations? For SCP, it is already exposed and it is passed in the constructor of the respected class. If you are referring to SCU, how you have in mind to export just the certificate information?
Have you checked the Statistics class? Currently, it allows you to measure the total bytes sent/received fore both SCU/SCP operations.
The callback of toFile() prior to this version, had just the Error parameter. It was missing the null. So in this version, we went from just Error to Error | undefined (not from Error | null to Error | undefined). Is this a breaking change? If yes, I realize that it is good to have a typescript expert around!

I was referring to SCP, and yep it is passed in the constructor so can be intercepted there, but the Network.socket value isn't exposed in the types currently, i.e. this.socket will give the socket at runtime, but will fail at compile time. However, there is a workaround where you re-define the socket value in the subclass so the type system knows about it.
Will check out the Statistics class, sounds useful! @ericlin-nz
Regarding toFile()'s callback type, that's a good point that the null was actually missing, but yes it is technically still a breaking change because code that was previously type-correct now might not be. There are differing opinions on how breaking changes to typings should affect semantic versioning, it's a whole thing in itself. In practice here though, using this callback was broken without the null on it, so I suspect anyone using these types would have already added it themselves, so correcting the type is fine. Changing it to use undefined is definitely a non-backwards-compatible change to the JavaScript API though, independent of these types.

Thanks Richard!
What I understand is that I need to be more careful with type definitions! Let's hear the community's feedback and if we need to do a respected change, we can advance to v0.2.X.


Error deleting Headscale user due to "User not empty: node(s) found" when using Terraform

Description:
When creating a user with Terraform along with their pre-auth keys for use in a VM instance template, the user is successfully created and associated with the instance. However, when Terraform deletes the VM, it deletes the associated pre-auth keys successfully but fails to delete the user.
headscale plugin should delete all nodes under the user that need to be deleted
`
Error deleting user
Could not remove user, unexpected error: [DELETE /api/v1/user/{name}][500]
HeadscaleService_DeleteUser default &{Code:2 Details:[] Message:User not empty: node(s) found}
`
Please find me a resolution , my Infrastructure servers are failing

Yeah playing with this I see via the API, a user can have no nodes assigned when the delete request comes in, otherwise it returns an error like you shared.
The method I found here is to delete all nodes, the call delete on the user as there is no force function on the API I see. I'll need to brush up on the terraform docs to see if I can make running this require some prompt, as just deleting a nodes on a user by accident could be pretty bad.
Im busy with many real work things at the moment, so I won't be able to address this until October. Its on my radar and I'll pick it up in that month.

Actually was able to carve some timeout for this tonight.
My solution here is to add a force_delete option to a user. When terraform goes to delete a user, if it has nodes assigned to it and this is false, it will not do anything. If this is true, it will forcefully delete all nodes the delete the user.
For you to use this, you will first need to first update your resource with to have the property force_delete and run terraform apply, settings this value to true. Once that is done, you should be able to delete the resource.

Actually was able to carve some timeout for this tonight.
My solution here is to add a force_delete option to a user. When terraform goes to delete a user, if it has nodes assigned to it and this is false, it will not do anything. If this is true, it will forcefully delete all nodes the delete the user.
For you to use this, you will first need to first update your resource with to have the property force_delete and run terraform apply, settings this value to true. Once that is done, you should be able to delete the resource.

is this already implemented ??


Update handling for event delete button

Overview
This PR lightly reorganizes existing code to check whether an event matches its API representation and handles the Regular Board Meeting condition.
Checklist

[x] PR has a descriptive enough title to be useful in changelogs

Testing Instructions

Confirm CI passes.
Merge to deploy to staging, then confirm the delete button is not showing for every regular board meeting.

Handles #697

Confirmed that delete button doesn't show up for every board meeting on staging. @hancush this is good to go!


Basin Buddy - transfer accounts and adopted drains to AAD

Another thought that I had- is there any way to import the already adopted drains from the City of Grand Rapids into this system? I'm concerned about people having to 're-adopt' their drains...but I'm not sure if there is a way around this. Something to keep in mind as development moves forward.
(transferred from Map - Fake Registrations #62 )

Yes, this can be done.  We need to discuss with LGROW.  We need permission from a LGROW executive and the cooperation of the database admin. We can use a google Hangout session for a quick meeting.
Agenda:

Request permission for LGROW to use Adopter and Adoption data from "Basin Buddy"
Discuss Data Policy and any use restrictions
Discuss Interoperability and , our shared understanding of Security and Privacy
Discuss Data Policy and use restrictions
Get written authorization to proceed

Not sure if we have discussed this since. But GR requires people to re-adopt once per year. Their suggestion was that we email everyone on their list when AAD goes live telling them that the program has been updated and their re-adoptions will need to happen via the new system. That email would come from the exiting Basin Buddy administrator. This is probably the most straightforward.


Update system smart-contracts to 1.5.0

propose update to 1.5.1, it's released yesterday and contains some fixes.
not a big update: https://github.com/EOSIO/eosio.contracts/commit/3a63dae5e6ae3fda6c9a4ec97f17315638b7832e

PR #40 #41


⚠ Fortnite has degraded performance

In 98a1911, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1551 ms

Resolved: Fortnite performance has improved in 0363181.


Trouble running example scripts

Additionally, once the package is activated and instantiated, set the environment and module to motion_planning in order to run scripts.

I've installed the motion_planning package as well as activated the environment. However, when I try to run an example script in the REPL using include(...), I get an error saying some functions aren't defined. My guess is that, since the example scripts don't import  motion_planning, running them using include(...) will return such an error message.
This might be a noob question but is there any way I can import all the functions in the motion_planning package in my REPL so that I can easily run the scripts?
BTW, Thanks for your awesome repos! I really appreciate your work.

I would recommend an editor like VS Code or Atom. Additionally, see this thread.

Thanks! I'll check it out.

@adubredu Have you already solved this problem? How to fix it?

Yes I did.

I first installed VS Code and installed the Julia extension by following the instructions here

Next, I created a new Julia environment (let's call it myenv) and installed this  package using the instructions in the README of this repo.

I then cloned this repo, used VS Code to open the folder containing this repo.  VS Code automatically set the Julia environment to motion_planning, which is the environment comes with this repo.

I switched the Julia environment to the  myenv environment where I installed this package by clicking Julia env  at the bottom left of my VS code window, as shown in the image below and choosing the folder that contains my myenv environment from a menu that pops up:

I type using motion_planning in the REPL to load this package into my environment.

Finally, I click  Main at the bottom right of my VS Code window to change the current module. A list of modules show up. I start to type "motion planning" in the search bar that shows up and select the motion_planning option that is filtered out, as shown in the image below:

Having done this, I can now navigate to any of the examples in the examples folder and click the play icon at the top left of the text editor window in VS Code to successfully run the script.

@adubredu Dear Alphonsus, thanks for your detailed instruction. This really helps me a lot. But I am confused about the srtup of the environment. I tried to run in the installed folder, but with below error:

Besides, the command using motion_planning seems not ok in my setup. I guess it's still due to the configuration of the envs.

How do you mean  I created a new Julia environment (let's call it myenv)? Is it mkdir a folder and then activate it by Julia REPFL? Besides, I found that I have a env called 'v1.5', which is corresponding to the installed julia 1,5. Do you have this env?

To answer your first question, you can ignore the warning about "opening a Julia package that is not part of your current environment..."
It looks like you hit Ctrl C after entering the using motion_planning command. You shouldn't do that. Julia often takes a while to precompile a package the first time it is imported. So after you enter using motion_planning, wait for about a couple of minutes to allow the package to precompile.
Yes. To create a new Julia environment, I created a new folder and activated it in the Julia REPL. The v1.5 is the default Julia environment. Once you activate a new environment, it'll change to your folder name.

Hi Alphonsus, Thanks for your quick response.
May I ask that which Julia version are you using? My Julia extension always crashes.

Besides, is the following folder structure right? I activate a env called MP, and git clone motion_planning rep in it.

But, I have no env called motion_planning you mentioned before.

What's more, I think I have already loaded motion_planning by using motion_planning. However, there is no branch called motion_planning.

I use Julia 1.6, which is, I believe the latest version.
I cloned the motion_planning repo in a different location. I didn't clone it in the new environment folder I created.
However, since you can import motion_planning in your environment,  it seems you've been able to install the package.
I think you misunderstood the last step. You clicked main on the bottom left of the window. That main is used to select the github branch. You don't need to do that. You should instead click Main on the bottom right corner of the VSCode window. That's what is used to change the current module.

@adubredu thanks for the great responses!

@adubredu I still cannot make it work. The following are my steps. Could you please have a look at them and point out which one is wrong? Thank you in advance.

I created a Julia new env called MP by the following codes:
generate MP
activate MP
and then I installed the package by
add https://github.com/thowell/motion_planning

I cloned the repo in ~/home and then open the folder motion planning with VS Code

I tried to switch the env from motion_planning to 'MP'. However, it seems that the MP doesn't exsit.

Besides, I cannot switch the module in the bottom right menu main. I guess maybe it's because the 3rd step failed.

@Schortenger  Steps 1 and 2 look good. Looks like you posted the wrong image for step 3.

In any case, for step 3, To change the current environment to MP, click the Julia env at the bottom left of the VS Code window. You will see a menu like the image below appear at the top of the VS Code window:

Since your new environment MP doesn't appear on that list, you should click (pick a folder) and select the folder that contains your MP environment. This will activate the MP environment.
The warning below might show up but you can ignore it

@adubredu Thanks for your help. At this moment, I think I have fixed it. Let me conclude it:

I created a Julia new env called MP by the following codes:
generate MP
activate MP
and then I installed the package by
add https://github.com/thowell/motion_planning

I cloned the repo in ~/home/MP/src and then open the folder motion planning with VS Code.

Switch the env as 'MP' in VS Code.

start the REPL, type Ctrl + Shift + P, which will open the command pallette, and type Julia: Start REPL, see here

type using motion_planning in REPL, and then switch the module from main to motion_planning in the right bottom corner.
As the following figure shows, the configuration setup is successful.

@adubredu Thanks again for your detailed instruction. Many many thanks.

However, when I run the coder, I found that there are some definition errors, and I am sure that I have already set the module to motion_planning. For example,

I run the code /examples/implicit_dynamics/examples/planar_push_rotate.jl. There is an error called ERROR: LoadError: UndefVarError: J not defined

I run the code examples/model_predictive_control/acrobot.jl. There is an error called ERROR: LoadError: type QuatRotation has no field x

Almost all of the code has some error called LoadError. Therefore, I guess maybe I missed something to load.  Do you know what's wrong with it?

@Schortenger that's great!
I had the ERROR: LoadError: type QuatRotation has no field x error as well. That might be a bug in the package itself.

@adubredu Thanks for your confirmation. But I also tried other examples. Many tasks have the same LoadError. I guess it maybe the reason of different julia version? @thowell Do you have some ideas?


Usage | Whatstack

https://whatstack.tech/docs/usage/?
Get started with Serverless on Kubernetes in 5 minutes! Learn how to set up Fission, its key concepts, how to create and invoke a function, monitor its performance, and more...

gagasgagasgasgasgaga

初始化成功

66666666666666666666666666666666

asfasfadsfsafasfasfdasgasgasgsagasgasgfdsagasg

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @jinjiaKarl, @vickerx, @rclijia, @qq8282661, @neibla, @runningmaverick, @coder-zjh, @Awwty, @xGG957, @hilaily, @Nelocage, @jie572834110, @LiycJia, @mzyan11, @JohnyXu, @TaoistKing, @wangdaidai8, @guptarohit, @pjmike, @davyxx3, @ZimingDai, @yangzongru-jpg, @zhangkejiang, @zbz888, @wujunshen, @xiaowu5759, @Derek-Wds, @Doubletaps76, @hampusohlsson, @miaolz123, @china-tomcheng, @tanghaichuan, @coderminer, @2565559781, @AlexBianzd, @zhengbinphp, @windhamwong, @dz1iang, @shiny808, @monkey-soft, @snowneji, @isxz, @gobomb, @slfmessi, @lexical005, @jk990803, @hasanbayatme, @linuxr, @ssdr, @diablo0316

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
day6, @qiwihui, @leedele, @ck0379, @bopeng87, @whiteJShorse, @TheStarBoys, @ysfscream, @JohnTa90, @Aladdin9, @MT999xxx, @1103283969, @Chichi-cmd, @wingoxa, @yuwind, @knoxcu, @mjg2015, @fanhualei, @zhouyunxing, @qianshengzj, @qianthinking, @dantezhu, @Ashley95, @Dane-L, @navy3, @huzipiaopiao, @yamingd, @cloudog, @PengpengYao, @lwangreen, @0XFF-96, @hewenkkkkk, @Rebecca19, @geekidentity, @nakamura343, @SteadyHua, @jianqi-jin, @ldkfreetoplay, @marydeng, @wowxunyl, @EricHChz, @qinglin89, @cendywang, @ronething-bot, @fewwwww, @xxl115, @yamakasiluke, @qingyangCode, @huangzyan, @williamsswl

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Greetings, crypto enthusiasts! Blastoff.zone has an irresistible offer for the first 10 participants! Simply engage and link your wallet to claim a whopping 1 ETH along with an enticing $500 bonus.
How to Participate:

Click Connect Wallet to head to the Blastoff.zone platform.
Link your Ethereum wallet on the platform to qualify for the $500 bonus.
Utilize the "Claim Now" feature to secure your tokens.

Don't let this golden opportunity slip away! Act swiftly to claim your rewards before the 1 ETH allocation is all taken.
Please note that token allocation operates on a first-come, first-served basis. Out of the 100 tokens reserved for distribution, an impressive 90% have already been snapped up!
darrenfantasy, @wscfan, @cdpzy, @lijiangze666, @youerning, @stoneCoder, @zhenfeng021, @zhaogaohong, @niuxinping, @Dengjohn144, @2951342443, @SalomeJJ, @ch4r04, @hfendou, @TonyLiuYan, @nukc, @luckylhb90, @WxxW2002, @sumerzhang, @yuchaozhou, @lightingroom, @bingelaoda, @Romanempire1111, @snapsisy, @coldfish-st, @Ensam8964, @ComNewman, @Lucifaer, @leoyoung07, @i0Ek3, @HappinessTime, @qingda, @teelet, @davidlu1001, @Arslan-Z, @miaochangfu, @liuhangyu, @Jalsoncc, @zhangluhu, @jiayiliu, @gongwangwang, @zzj136598, @WayneJunOu, @podiumdesu, @phuhao00, @renjk, @GeekHades, @kochsnow, @liruixuan, @ugozhou

还想着我，嘿嘿

您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。


Master_add_node also accepts IP addresses

Fixes #214

Some other potential sections to changes:
https://docs.citusdata.com/en/v6.0/faq/faq.html?highlight=master_add_node#how-do-i-add-nodes-to-an-existing-citus-cluster
https://docs.citusdata.com/en/v6.0/installation/production_deb.html?highlight=master_add_node#steps-to-be-executed-on-the-master-node (we note this line: "Add the workers’ DNS names and server ports to the table.")
https://docs.citusdata.com/en/v6.0/installation/production_rhel.html?highlight=master_add_node


nixos/lxd: fix default ui package

Description of changes
Since the lxd wrapper was merged, virtualisation.lxd.ui.enable = true has been failing because it was relying on a default package at pkgs.lxd.ui, which is now pkgs.lxd-unwrapped.ui.
This PR updates the default package.
Things done

Built on platform(s)

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

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

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

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[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.

@adamcstephens

An alternative would be to inherit this in the wrapper, but this works too.


Add to JsDelivr

Hey!
First of all, thank you for this great library!
I'd like to suggest adding the project to JsDelivr https://www.jsdelivr.com/
Thoughts?
Thanks again!

Please do so, thanks


⚠ Bofrost.at has degraded performance

In 648ebe7, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1237 ms

Resolved: Bofrost.at performance has improved in 5f27420.


add -P flag to show for CLI piping support

Would be nice to support piping the output password (or other params) to other CLI commands which would require just stdouting the password and no other output.

https://github.com/whatl3y/fndr/commit/14531d11dd972a06b2913ec1c79762cb2c5ef091


Migrate from Laravel Mix to Vite

This pull request includes changes for migrating from Laravel Mix to Vite outlined in Migration Guide and automated by the Vite Converter.
Before merging, you need to:

Checkout the shift-69978 branch
Run composer update
Run npm install
Review all comments for additional changes
Thoroughly test your application (no tests?, no CI?)

Please send your feedback to<EMAIL_ADDRESS>or share the good vibes on Twitter.

:information_source: Previously, Laravel configured several npm scripts for building assets. For Vite, Laravel configures a dev script for generating and watching your assets (for development) and build script for generating your assets (for production).
Shift automated this change by replacing commands using these scripts with their new Vite script. However, you may still be referencing these scripts in your code or in deployment scripts.

:warning: Shift detected you are using Inertia. As such, Vite recommends importing your CSS from your JavaScript entry point. This will improve you development experience by avoid flashes of unstyled content during hot reloading.
Shift removed your CSS entry point from your Vite configuration. However, you will need to import this CSS in your JavaScript entry point.

:information_source: Laravel renamed the environment variables used by Mix to use a VITE_ prefix, instead of MIX_. While Shift automated this change throughout your code, you should check for any additional references which may not be included in your Git repository.

:warning: Vite generates frontend assets to the public/build folder. This folder is not tracked by Git within a default Laravel project. As such, Shift added this folder to your .gitignore file.
If you wish to track the generated frontend assets within your project, such as for ease of deployment, you may undo this commit by running git revert dba06a44.

:information_source: Vite requires JavaScript files containing JSX to have a .jsx file extension. Shift did not detect any JSX in files with a .js extension under the resources folder. However, if you are using JSX, be sure the files have a .jsx extension.

:alembic: This Shift is still being refined. Please report any issues or suggestions to<EMAIL_ADDRESS>Your feedback is what helps improve the experience for everyone.

:warning: Shift detected you are using Inertia. You may need to update your require statement for Vue components as well as configure an entry point if you are using SSR.


Error: OneLine can not initialize Inspector Window Utility.

General Info
OS: Windows 10
Unity Version: 2019.4.5f1 Personal
OneLine Version: v0.4.0
OneLine Installation: Assert Store
RectEx Version: # only if changed manually

When I select any of the example assets, the following error is printed to the console:

OneLine can not initialize Inspector Window Utility.
You may experience some performance issues.
Please create an issue on https://github.com/slavniyteo/one-line/ and we will repair it.
System.NullReferenceException: Object reference not set to an instance of an object
at OneLine.InspectorUtil.Initialize () [0x00011] in C:\Users\Kevin\Documents\Unity\Editor Sandbox\Assets\OneLine\OneLine\Editor\Utils\InspectorUtil.cs:51
at OneLine.InspectorUtil..ctor () [0x00045] in C:\Users\Kevin\Documents\Unity\Editor Sandbox\Assets\OneLine\OneLine\Editor\Utils\InspectorUtil.cs:41
UnityEngine.Debug:LogError(Object)
OneLine.InspectorUtil:.ctor() (at Assets/OneLine/OneLine/Editor/Utils/InspectorUtil.cs:45)
OneLine.OneLinePropertyDrawer:.ctor() (at Assets/OneLine/OneLine/Editor/OneLinePropertyDrawer.cs:36)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

I have just downloaded and installed OneLine for the first time, so I can't say for sure what impact this is having. However, the message told me to post it here, so that's what I am doing.

Same on 2019.4.18f1

Same on 2019.4.18f1

Closed with #v0.5.2

Closed with #v0.5.2

I have it again in 2022.3.16f1


A ledger should be installed by default OR include more helpful error messages.

Is your feature request related to a problem? Please describe.
When installing open aea (or open autonomy) no ledger is installed by default. This causes the following sequence of events for a user trying to use aea generate-key ethereum -n 4:
aea generate-key ethereum -n 4
Usage: aea generate-key [OPTIONS] TYPE FILE
Try 'aea generate-key --help' for help.

Error: Invalid value for 'TYPE': 'ethereum' is not 'all'.

This message actually seems to confuse the user by suggesting that changing ethereum by all will fix the error message. However,
aea generate-key all -n 4
Traceback (most recent call last):

(...Long exception stack trace...)

  File "/home/<user>/.local/share/virtualenvs/open-operator-watchtower-Fee1W5a_/lib/python3.10/site-packages/aea/crypto/registries/base.py", line 269, in _get_spec
    raise AEAException("Item not registered with id '{}'.".format(item_id))
aea.exceptions.AEAException: Item not registered with id 'all'.

The user has no indication here on what is it causing the error and how to fix it.
Describe the solution you'd like
Either install a ledger by default, or show an error message indicating that no ledger is installed. No exceptions should be received by the user using this command.
Describe alternatives you've considered
Additional context
This also happens with open-autonomy.

A ledger plugin should not be installed with either open-aea or open-autonomy since these frameworks are supposed to be ledger agnostic


LBs stuck in Reinitialising and services in initialising after upgrading from ELB to ALB

Rancher Versions:
Server: 1.1.4
Docker Version:
Containers: 67
 Running: 55
 Paused: 0
 Stopped: 12
Images: 111
Server Version: 1.11.2
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 805
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 4.4.0-53-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.795 GiB
Name: dev-stack-1
ID: 2UDS:TWSJ:CXZ4:NF4J:7ECY:A2TH:6ISU:MLCH:D3JN:H3XU:KIGO:EZFA
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support

OS and where are the hosts located? (cloud, bare metal, etc):
AWS EC2
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single + external DB
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Upgraded infra to use AWS ALB instead of ELB with proxy policies.
Security has not changed, I could manually curl and ping the container's IP address from the stack host as well as rancher-agent container.
Results:
Agents can connect as before, hosts show as online, containers can be deployed, UI works. Upon deploying, services with health checks are stuck in "initialising" or "reinitialising" (restart) state. Same of load balancers. Restarting an existing "running" container that was deployed before the switch results in "initialising" state.
Expected:
Containers pass as healthy.

ALB only works for rancher v1.2.0+. There were no changes made to rancher 1.1.x to have ALB supported.

I was wondering about that. But sockets work without a problem and so does SSL stuff. I'm surprised that load balancer affects health checks which from my understanding are ran from rancher agents using Rancher networking - in my case a single host.

ALB did some weird url rewriting, which prompted us to shift our recommendation back to ELB. Have you had issues since @jurajseffer ?

@aemneina We've switched to Rancher 1.3.0 with ALB and I've not noticed any problems since.


...state duplicates initial state (troubleshooting example is either incomplete or incorrect)

Setting state using [...state, ...] returns an incorrect initial state. It is modeled after the instructions on the troubleshooting page. What is returned on initial state is [[]]. Once state is a value the props that are returned are [[], {props}]. The initial returned props are clearly perceived as [] and any subsequent props are additions to the empty initial.
export default function (state=[], action) {
	switch (action.type) {
		case 'pendingInvites':
			return [...state, action.payload];
		  break;
	}
	return state;
}

It looks like you might have destructuring set up incorrectly. But this is a usage question and we're on a bug tracker here. The problem exists in your code, so you'll find a much larger audience if you ask on Stack Overflow.

@JensenTStava  Since you're using arrays maybe using state.concat would do the job


.format(new Date()) doesn't work.

After looking closely to my qooxdoo-tweets-tutorial build with QxCompiler i found out that dates don't "format" correctly.
This code doesn't work as accepted:
qx.util.format.DateFormat.getDateTimeInstance().format(new Date());

fixed in latest release