Request Development, Enhancement: Another option for User Credentials

Can I ask for a development of the node please? Is there a possibility to add the option to insert user credentials (username, password and unit id) into the streamer-node please? (instead of entering them into the node when added to a flow the first time)
Currently the only option to change any of the credentials is for someone with access and the knowledge on how to use Node-Red. I would love have the option to forward any of the credentials via another UI (Home Assistant for example) via input helpers and forwarded to node-red. In this case I can create an admin sight for the end-user to change the password when needed. The credentials would be inserted when node-red start or from another trigger via the websocket.
I would love to contribute myself but can’t do any programming, completely useless.
Thanks for creating this node. Its brilliant and very useful, good job

This looks like a good idea. To be able to insert/inject the user credentials into the node from an external point. Example a helper in home assistant.

Yea. The admin on credentials is the worse when it comes to Home Assistant. Plenty of the integrations don't even have an easy way to change username or passwords. Weird. Typical developers that can't understand how basic, non programming enthusiast... just regular users behave and need. So integration with this limitation makes it not ideal for a setup of HA at your grandparents house. (nightmare)
I thought an additional function in Node-Red would solve with the help of this node. Not an option, was hoping for too much. Have to build a more advanced flow (from my point of view and basic knowledge) to see if I can solve the Easee integration and user credential issue.

@KIDNORswe Is it OK if I add username and password parameters to the doLogin() function?
       node.doLogin = async (_username, _password) => {
        const url = "/accounts/login";
        const response = await fetch(node.RestApipath + url, {
          method: "post",
          body: JSON.stringify({
            userName: _username ?? node.credentials.username,
            password: _password ?? node.credentials.password,
          }),
          headers: {
            Accept: "application/json",
            "Content-Type": "application/json",
          },
        })

Hi @runnane. Thanks for getting back on this. Hope it won't take too much time with a modification of the current node.
If you use the doLogin() function, will it only be for that moment of login that won't change the previous stored data in node.credentials?
I think for the best use and advantage and looking at the purpose of the function + making it better than other integrations or nodes is giving the config a function with the option to change the previous stored credentials in node.credentials.
To make it a little more "safe" and minimise the chances of making any changes by misstake, I reckon it would be best to have an update function that can receive input data and change the current in the config/node.credentials.
Example.
You can have a helper in Home Assistant (HA) that will hold your credential data. There is one that keeps the password hidden. Depending on how the function and trigger in HA to forward this data the to Node-red flow with the Easee node is up to the user creating the function.
In the Node-Red Easee flow you have the option to create an input node with the following:
msg.topic: "change_credentals"; msg.payload = {"change_username": "newusername", "change_password:"newpassword" };

If the message only has "change_password" or only "change_username" it will only change the option that is forwarded.
You have to have the msg.topic in the message or it won't work.

This way the data will be forwarded into the credentials.
However here is where my knowledge is bad... will the password be seen in the log? or can it be hidden? If not there should be a warning that if the user, on their own risk, use this function. They have to be aware that it might be seen in the log. I guess that its only if you are debugging and record longer logs that you will se such a change being pushed through.
What do you think?
Thanks.

@KIDNORswe @runnane
I can't tell if that is possible (the suggestion you made @KIDNORswe) I don't have the knowledge to judge if this is against or OK with the common process in handling user credentials.
The option to be able to change or update the username and/or password from another hub or platform like the Home Assistant would be great. At least for us few that has decided to go with the Easee node and Node-Red instead of the current integration. It will make this node more attractive.
Using Node-Red with other UIs will also benefit from this however in my case, together with the Node-Red add-on in Home Assistent will be very useful. I would setup a function and flow what KIDNORswe is suggesting.
I wish I had the knowledge to create this and contribute. However I cant so the only way I can help is to test it when its available.
Thanks both for taking time for this.


Chip component issue in supporting IE 11 in production mode

Problem description
I am using material-ui-chip in my popup, it is working good in Chrome, but not supporting in IE 11 in production mode . Please let me know whether material-ui-chip supports IE 11 or not.
Steps to reproduce
Versions

Material-UI: ^0.17.1
React: ^15.5.4
Browser: IE 11

We have been porting the component on the v1-beta branch. We reimplemented it from the ground-up. While we haven't tested it, I think that the issue is most likely fixed on that branch. Hence, I'm closing it.
Still, we will accept PR fixes until v1-beta takes over the master branch.

Thanks for your quick reply @oliviertassinari , May I know when you are going to release this with complete testing.

What do you mean by complete testing? It's already fully tested, even on IE11.

I am asking about Master branch.

I am sorry @oliviertassinari , we are hurry in releasing our product, so I am curious to know when Material-UI team is targeting to officially release the fix?

There is no ETA for the release of the v1 branch.


Fix key binding for "Close the current tab"

Change documentation for "Close the current tab" from Ctrl + c to Ctrl + q, because the tab closes with Ctrl + q 🙂

Thanks for the PR!
The documentation is correct. The latest Yazi 0.3 uses Ctrl-c instead of Ctrl-q because it is more in line with conventions and is closer to the Ctrl key. This is a breaking change in v0.3, see https://github.com/sxyazi/yazi/issues/1046


[Jammy] cflinuxsf4 - s3-broker

In order to migrate cflinuxsf4 stack (jammy), we want to test and verify that s3-broker works using the new stack
Acceptance Criteria

Confirm that s3-broker's buildpack supports cflinuxsf4
Deploy s3-broker in development cf using stack cflinuxsf4
Update application manifest to point to cflinuxsf4

Security considerations
None
Resources
https://github.com/cloudfoundry-community/s3-broker
https://github.com/cloud-gov/cg-deploy-s3-broker
https://ci.fr.cloud.gov/teams/main/pipelines/deploy-go-s3-broker
Implementation sketch

[x] Update broker deployment in dev to use cflinuxfs4

[x] In a custom branch, add stack: cflinuxfs4 to the manifest: https://github.com/cloudfoundry-community/s3-broker/blob/master/manifest.yml
[x] Update the pipeline to use a custom source for the dev deployment with your custom branch: https://github.com/cloud-gov/cg-deploy-s3-broker/blob/master/pipeline.yml#L52
[x] Run the push-s3-broker-development job

[x] Confirm that broker still works by running the acceptance-tests-development job

I have verified that the s3-broker runs on cflinuxfs4
\


Better CI

Current CI is extremely slow

was wondering if it is possible to disable default features for bevy and only include the features that the event_priority and mod_scripting crates actually use.
there's a security advisory about stdweb (unmaintained) and time (seg fault possible) crates which are dependencies of bevy_gilrs. this was making my Cargo Checkmate workflow fail and i spent an hour trying to find out why bevy_gilrs was getting included in my Cargo.lock file xD.

Haha, yeah for now I've everything from bevy included to avoid dev-hassle, but closer to the release (very soon) I will go through and make sure not everything is included.
Having said that, once the general API hits, that will touch most bevy crates (although I doubt it will touch bevy_gilrs)


Update initial.js

Fix for the error TypeError: $*.velocity is not a function that occurs when using webpack to require('materialize-css')

Can we have this <3

Related? https://github.com/Dogfalo/materialize/pull/3782

Can you please test if https://github.com/Dogfalo/materialize/pull/3782 solves your problem too? If so I would close this PR


Add the file extension to the path

Hi team,
Hopefully this should be a trivial request for you. I am trying to add a path "suffix" using ReplacePathRegex:
URL: www.example.com/image
Backend: server.local/image.jpg,
where image.jpg is a dynamic/changing filename
I want to add to whatever the URL is the .jpg extension.
Any help to achieve this is greatly appreciated.

ReplacePathRegex: ^/(.*) /$1.jpg did the trick, thanks for your support anyway


[BUG] Concurrent ScheduleMessageAsync throws ServiceBusException

Library name and version
Azure.Messaging.ServiceBus 7.18.1
Describe the bug
When ScheduleMessageAsync() is used in a concurrent operation the sender causes ServiceBusException with reason
 "Cannot allocate more handles. The maximum number of handles is 4999. (QuotaExceeded)."
Expected behavior
Concurrent execution of ScheduleMessage should acknowledge the message and move on.
var sender = serviceBusClient.CreateSender(queueName);
var message = new ServiceBusMessage(JsonSerializer.Serialize(new { id = productId }));
await sender.ScheduleMessageAsync(message, DateTimeOffset.Now.AddSeconds(60), token);
await sender.CloseAsync(token);

Actual behavior
var sender = serviceBusClient.CreateSender(queueName);
var message = new ServiceBusMessage(JsonSerializer.Serialize(new { id = productId }));
await sender.ScheduleMessageAsync(message, DateTimeOffset.Now.AddSeconds(60), token);
// the above line throws ServiceBusException:  Cannot allocate more handles.
// The maximum number of handles is 4999. (QuotaExceeded).
await sender.CloseAsync(token);

The above is not observed when not using ScheduleMessageAsync and instead using SendMessageAsync with ScheduledEnqueueTime property set on ServiceBusMessage.
var sender = serviceBusClient.CreateSender(queueName);
var message = new ServiceBusMessage(JsonSerializer.Serialize(new { id = productId }));
message.ScheduledEnqueueTime = DateTimeOffset.Now.AddSeconds(60);
await sender.SendMessageAsync(message, token);
await sender.CloseAsync(token);

Reproduction Steps
Fully working example of a console app this problem can be reproduced.
using System.Text.Json;
using Azure.Messaging.ServiceBus;
using Microsoft.Extensions.Azure;
using Microsoft.Extensions.DependencyInjection;

// Configure

const string serviceBusConnectionString = "your-connection-string";
const string  queueName = "your-queue";
const string  serviceBusClientName = "any-client-name";

// Register

var serviceProvider = new ServiceCollection()
	.AddLogging()
	.AddAzure(serviceBusConnectionString, serviceBusClientName)
	.BuildServiceProvider();

var serviceBusClientFactory = serviceProvider.GetService<IAzureClientFactory<ServiceBusClient>>();

if (serviceBusClientFactory is null)
{
	Console.WriteLine(@"ServiceBusClientFactory not registered");
	return;
}

var serviceBusClient =  serviceBusClientFactory.CreateClient(serviceBusClientName);

var productIds = new List<int>();
productIds.AddRange(Enumerable.Range(1, 10000));

var parallelOptions = new ParallelOptions { MaxDegreeOfParallelism = 10000 };

Console.WriteLine(@"Starting concurrency simulation ...");

// Simulate concurrency

await Parallel.ForEachAsync(productIds, parallelOptions, async(productId,token) =>
{
	var sender = serviceBusClient.CreateSender(queueName);
	var message = new ServiceBusMessage(JsonSerializer.Serialize(new { id = productId }));

	await sender.ScheduleMessageAsync(message, DateTimeOffset.Now.AddSeconds(60), token);

	/*
		The above line throws ServiceBusException:  Cannot allocate more handles. The maximum number of handles is 4999. (QuotaExceeded).
		Change it to:

		message.ScheduledEnqueueTime = DateTimeOffset.Now.AddSeconds(60);
	 	await sender.SendMessageAsync(message, token);
	*/
	await sender.CloseAsync(token);

	Console.WriteLine(@"Message sent: " + productId);
});

Console.WriteLine(@"Done");

public static class ServiceCollectionExtensions
{
	public static IServiceCollection AddAzure(this IServiceCollection services, string serviceBusConnectionString, string serviceBusClientName)
	{
		services.AddAzureClients(client =>
		{
			client.AddServiceBusClient(serviceBusConnectionString).WithName(serviceBusClientName);
		});

		return services;
	}
}

Environment
Reproduced on:

Azure Functions (Linux) <IP_ADDRESS>

Localhost

dotnet --info
.NET SDK:
 Version:           8.0.100
 Commit:            57efcf1350
 Workload version:  8.0.100-manifests.6c33ef20

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  14.5
 OS Platform: Darwin
 RID:         osx-arm64
 Base Path:   /usr/local/share/dotnet/sdk/8.0.100/

.NET workloads installed:
 Workload version: 8.0.100-manifests.6c33ef20
There are no installed workloads to display.

Host:
  Version:      8.0.0
  Architecture: arm64
  Commit:       5535e31a71

.NET SDKs installed:
  7.0.405 [/usr/local/share/dotnet/sdk]
  8.0.100 [/usr/local/share/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 7.0.15 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 8.0.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 7.0.14 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.15 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 8.0.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  x64   [/usr/local/share/dotnet/x64]
    registered at [/etc/dotnet/install_location_x64]

@JoshLove-msft :  Would you please take a look and offer your thoughts?

The Service Bus service limits the number of concurrent actions for a namespace to 5000. Your sample is attempting to schedule 10k messages in parallel. Please see this doc for detailed limit information.

@JoshLove-msft
Thanks for the info. I understand the limitations.
If you bring parallelism down from 10K to 2K it still throws an exception (just not in an instant).
Is there any logical explanation why this fails in an instant:
await sender.ScheduleMessageAsync(message, DateTimeOffset.Now.AddSeconds(60), token);

and this doesn't ( .... with whatever concurrency you throw at it)
var message = new ServiceBusMessage(JsonSerializer.Serialize(new { id = productId }));
message.ScheduledEnqueueTime = DateTimeOffset.Now.AddSeconds(60);
await sender.SendMessageAsync(message, token);

Isn't the code performing the same thing?
I haven't had a chance to look at the source code but it seems to me that SendMessageAsync closes connections / cleans up resources correctly and ScheduleMessageAsync doesn't.

@JoshLove-msft & @jsquire
I appreciate the help and explanation but I do believe this should be re-opened.

So the code path for Schedule vs Send is slightly different. Scheduling uses the mgmt link whereas sending uses the send link. We are closing up the links as expected for both the send and mgmt links when CloseAsync is called so I would have expected the behavior to be the same. We will need to follow up with the service team to see if it is expected that the quotas would differ between scheduling and sending.

I wasn't able to repro Schedule throwing when using 2k parallel schedules. To provide more context on the difference of send vs schedule, the management link is actually comprised of both a send and receive link, so essentially when you are scheduling a message instead of sending you are using 2 links (aka handles) as opposed to 1. This explains the difference in the behavior that we are observing.


[native_assets_builder] build.dart -> hook/build.dart

https://github.com/dart-lang/native/issues/823

Notes:

Should keep existing toplevel build.dart scripts working by trying both hook/build.dart and build.dart.
Does not migrate the examples yet, so that we don't have to do breaking-change is true in the ci.

Will do this after rolling into Dart.

native_toolchain_c had a this.dartBuildFiles = const ['build.dart'],. Updating that to hook/build.dart would not work for unmigrated scripts, because files listed as dependencies that don't exist will also trigger a rebuild, e.g. it is considered deleting a file. It would also break on any kind of invocation from hook/link.dart. So, I've removed the default value for now. It's not pretty though. Ideas @mosuem?

Updating that to hook/build.dart would not work for unmigrated scripts.

I don't understand what the problem is. A rebuild would be triggered once? That doesn't sound too bad?

Updating that to hook/build.dart would not work for unmigrated scripts.

I don't understand what the problem is. A rebuild would be triggered once? That doesn't sound too bad?

dart run has the old native_assets_builder baked in. So it won't check hook/build.dart from the examples. This will break the dart --enable-experiment=native-assets run ... steps on the CI until we roll this PR actually into the Dart SDK.

coverage: 92.104% (-0.007%) from 92.111%
when pulling 571a542f68b280ff13a0e2614d72059b132c2eca on hook-build-dot-dart
into 7e1e2b73a57507e6cb04b25e93228fc10ef689f8 on main.


Inherited env not cascaded to hook command envs

First time you run it, the system prompts for user input for extra env variables, and these are visible in command env.
The second time you run it, the system no longer prompts for user input, and the variables are missing from command env.
Changing the name of the var will get you back to 1.

My mistake

No I am pretty sure something is wrong with the step of extracting env variables from a previously deployed service

Just to verify, this is on prebuild / postbuild right?

Yeah I observed on postbuild. Looks like you found the issue


perlPackages.MathPlanePath: 127 -> 129

Motivation for this change
This fixes the build failure introduced by c5b0de9c6ba,
which indirectly broke slic3r.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111222 run on x86_64-darwin 1

1 package failed to build and are new build failure:

perl530Packages.MathPlanePath: log was empty

1 package built:

perl532Packages.MathPlanePath

$ nix --experimental-features nix-command build --no-link --keep-going -f /Users/user/.cache/nixpkgs-review/pr-111222/build.nix
error: --- Error -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
nixbuilder for '/nix/store/s0vfw2ni1n9zi289f7bkaprhsfx57cvl-perl5.30.3-Math-BigInt-Lite-0.19.drv' failed with exit code 2; last 10 log lines:
Test Summary Report
-------------------
t/bigintpm.t            (Wstat: 3072 Tests: 4026 Failed: 12)
Failed tests:  2938, 2940, 2942, 2958, 2960, 2962, 3038
3040, 3042, 3058, 3060, 3062
Non-zero exit status: 12
Files=17, Tests=19313, 20 wallclock secs ( 4.61 usr  1.40 sys + 18.29 cusr  1.73 csys = 26.03 CPU)
Result: FAIL
Failed 1/17 test programs. 12/19313 subtests failed.
make: *** [Makefile:866: test_dynamic] Error 255
error: --- Error -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
nix1 dependencies of derivation '/nix/store/1miydvw08n68wv90jnmjw2digrygfd0z-perl5.30.3-Math-PlanePath-129.drv' failed to build

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111222 run on x86_64-darwin 1

1 package failed to build and are new build failure:

perl530Packages.MathPlanePath: log was empty

1 package built:

perl532Packages.MathPlanePath

$ nix --experimental-features nix-command build --no-link --keep-going -f /Users/user/.cache/nixpkgs-review/pr-111222/build.nix
error: --- Error -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
nixbuilder for '/nix/store/s0vfw2ni1n9zi289f7bkaprhsfx57cvl-perl5.30.3-Math-BigInt-Lite-0.19.drv' failed with exit code 2; last 10 log lines:
Test Summary Report
-------------------
t/bigintpm.t            (Wstat: 3072 Tests: 4026 Failed: 12)
Failed tests:  2938, 2940, 2942, 2958, 2960, 2962, 3038
3040, 3042, 3058, 3060, 3062
Non-zero exit status: 12
Files=17, Tests=19313, 20 wallclock secs ( 4.61 usr  1.40 sys + 18.29 cusr  1.73 csys = 26.03 CPU)
Result: FAIL
Failed 1/17 test programs. 12/19313 subtests failed.
make: *** [Makefile:866: test_dynamic] Error 255
error: --- Error -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
nix1 dependencies of derivation '/nix/store/1miydvw08n68wv90jnmjw2digrygfd0z-perl5.30.3-Math-PlanePath-129.drv' failed to build

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111222 run on x86_64-linux 1

1 package failed to build and are new build failure:

perl530Packages.MathPlanePath: log was empty

2 packages built:

perl532Packages.MathPlanePath
slic3r

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 111222 run on x86_64-linux 1

1 package failed to build and are new build failure:

perl530Packages.MathPlanePath: log was empty

2 packages built:

perl532Packages.MathPlanePath
slic3r


Include hidden questions in application PDF export

Is your feature request related to a problem? Please describe.
See https://github.com/civiform/civiform/issues/6277
In discussing that issue with AR, we agreed on the solution of including questions that were hidden from the applicant in the PDF export, clearly labeling them as having been hidden and not applicable for that applicant to avoid confusion.
What priority is this?
High priority to unblock Arkansas.
Associated civic entity
Arkansas
Done when:

[ ] questions that were hidden from the applicant are included in the PDF export
[ ] each question is clearly labeled as having been hidden from the applicant along with a summary of the visibility condition

Discussed on 1/4: Seattle is good with this change for Program Admins. Would need to be careful with wording and design for anything Applicant-facing--there is concern that this would be information-overload or confusing for applicants. Could have a V1 to unblock AR with verbiage to clarify why certain questions/screens are Not Applicable.


Release 0.0.3

Things:

#20
#21
#22
#23
#24
Accessible Abort

https://github.com/austral/austral/releases/tag/v0.0.3


[google_sign_in] Investigating removing Guava dependency

Based on recent discussion, we would prefer not to depend on Guava in general since it's not a finely-scoped dependency. We should investigate how easy it would be to replace the current usage (which from an quick initial check seems to be for some Futures management utilities).

Turns out this was already filed as https://github.com/flutter/flutter/issues/13991


Fix StateManager use in different components

Summary of changes
Changes introduced in this pull request:

While working on the message pool, it seems like i need to integrate the StateManager into the Provider. This led me to see that we were creating a new  StateManager in ChainSyncer and in the RPC. And that seemed wrong.
Creates StateManager in the node startup, and shares it with ChainSyncer, RPC, and Mpool.

Reference issue to close (if applicable)

Closes
Other information and links

came in with #618, I assumed it was intentional to have it separate. @AshantiMutinta want to weigh in on this?
I do think that the state calculation cache should be shared, but the subscriber channel cloned on the RPC side worries me. Since those head change events aren't polled off on the RPC side, the receiver will fill and block the sender. Why is that subscriber field added? It isn't used right now

This should be fine, I think having these two separate was an oversight. Most state operations are just communicating with internal operations. In this way, we can even look into implementing caching mechanisms across the board


Add me please

I would like to be added to the list.
<EMAIL_ADDRESS>Thanks!

Sure - can you let me have your Name, and settings for ShowBoosts, NotifynewPosts and Language?

I'm not sure what ShowBoosts, NotifynewPosts are. I am unfortunately only
fluent in English.
Sam Hetchler
970.430.6688
On Thu, Nov 17, 2022 at 1:34 PM Thomas Lee @.***> wrote:

Sure - can you let me have your Name, and settings for ShowBoosts,
NotifynewPosts and Language?
—
Reply to this email directly, view it on GitHub
https://github.com/doctordns/MastoPosh/issues/6#issuecomment-1319169810,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADFAKV4NJ2VJFJHIG7MEF4LWI2JGJANCNFSM6AAAAAASDUXC4M
.
You are receiving this because you authored the thread.Message ID:
@.***>

I have added added this to the CSV>
Thanks


Workspaces

This feature enables management multiple workspaces on developer machine ie:
~/.rnv (DEFAULT)
~/.myCompanyX
~/.myCompanyY
..
this will then enable support for dedicated private scoped plugins / templates / integrations / keys / sources etc which are only available per specific workspace and allows seamless integration into rnv commands like:
rnv plugin add
rnv template add
etc
Example how to add existing company-wide workspace (github route):
rnv workspace add --git git@github.com:company-x/renative-workspace.git --dest ~/.myCompanyX

Already implemented


ToolBar isn't shown

Hi,
first thanks for this nice package. A toolbar is something that is really missing in this nice software which is Atom.
I've installed your package but the toolbar appears nowhere... I've restarted Atom, but it doesn't change anything.
Is there something to do to make it appear, or is this a bug?
OS: Fedora 20
Thanks for your help!

Have you got the base tool-bar package installed?
https://atom.io/packages/tool-bar

Thanks AlexNewson,
My bad, I missed the tool-bar package, that was the problem! And the real problem was that I didn't read the installation instructions...   :disappointed:


Add Dockerfile for modelmesh-minio-examples image

Add the Dockerfile for the modelmesh-minio-examples image to the modelmesh-serving repo.
From quay.io/cloudservices/minio:RELEASE.2021-06-17T00-10-46Z.hotfix.35a0912ff
EXPOSE 9000
RUN mkdir -p /data1/modelmesh-example-models
COPY sklearn /data1/modelmesh-example-models/sklearn/
COPY lightgbm /data1/modelmesh-example-models/lightgbm/
COPY onnx /data1/modelmesh-example-models/onnx/
COPY pytorch /data1/modelmesh-example-models/pytorch/
COPY xgboost /data1/modelmesh-example-models/xgboost/
COPY tensorflow /data1/modelmesh-example-models/tensorflow/
COPY simple_string /data1/modelmesh-example-models/tensorflow/simple_string/
COPY keras /data1/modelmesh-example-models/keras/
# for ftv image only
COPY fvt /data1/modelmesh-example-models/fvt/
COPY <your files>

And the instructions to build the image, i.e.:
docker build -t <image registry>/<org>/<repo name>:<tag>
docker push <image registry>/<org>/<repo name>:<tag>

Once we have the Dockerfile we should be able to add a Gtihub action to push it whenever it gets updated
Some model files are large and are managed the IBM COS. Maybe we can pull them into the Docker build from their respective sources … i.e. have a build script that copies the large files to a local temp dir before the docker build command starts and then deletes the large temp files once the docker build finished.
The Dockerfile itself could go under a new directory or something called examples (or better)
As a workaround for this current v0.10.0 release I retagged the existing latest image on DockerHub directly.
docker manifest create kserve/modelmesh-minio-examples:v0.10.0 kserve/modelmesh-minio-examples:latest
docker manifest push kserve/modelmesh-minio-examples:v0.10.0

/assign @tedhtchang

UPDATE 2/1/2023: We now have the kserve/modelmesh-minio-examples repository dedicated to maintain and build the ModelMesh MinIO Examples Docker image(s):

https://github.com/kserve/modelmesh-minio-examples/blob/main/Dockerfile

We now have the kserve/modelmesh-minio-examples repository dedicated to maintain and build the ModelMesh MinIO Examples Docker image(s):

https://github.com/kserve/modelmesh-minio-examples/blob/main/Dockerfile


Short solution needed: "How to send HTTP 1.1 request" (curl)

Please help us write most modern and shortest code solution for this issue:
How to send HTTP 1.1 request (technology: curl)
Fast way
Just write the code solution in the comments.
Prefered way

Create pull request with a new code file inside inbox folder.
Don't forget to use comments to make solution explained.
Link to this issue in comments of pull request.

How to send HTTP 1.1 request


Support Visual Studio's MsBuild

Some msbuild projects like sqlproj can only be built using visual studio's msbuild (or another installed msbuild). Allow support for that project style via vswhere and the msbuild installed there.

The primary motivation for this was my usage of sqlproj and dacpacs, as well as having some legacy projects on .NET, not .net core. rules_tsql eliminates the need for dealing with sqlproj files, and I no longer have legacy .net framework projects. Closing as no longer motivated.


CondaStoreServer.log_level doesn't do anything

CondaStoreServer.log_level nominally controls the logger level (see https://conda.store/en/latest/administration.html#conda-store-server-server-app-condastoreserver), but it's never actually used anywhere.
Furthermore, the log level is difficult to set at the command line because --CondaStoreServer.log_level=DEBUG doesn't work. You'd have to use --CondaStoreServer.log_level=10 (where logging.DEBUG == 10).

If this is not used, and it is otherwise not adding anything in terms of user experience (CLI use) would it not be best to remove this altogether?

@costrouc @pierrotsmnrd - What do you think about this?

@costrouc last ping here. Otherwise will just move ahead with removing this altogether.

I think this is a worthwhile issue to look into since this is the primary way that we debug things within a kubernetes deployment on nebari. I'd also say logging/printing in conda-store-server/worker(s) is inconsistent and needs clean up. Traitlets does provide a log attribute to LoggingConfigurable classes but it is not always accessible where you need.

@nkaretnikov can you please take on this issue?

Closed by #940.