Every time format, a comma is added.

What version of CUE are you using (cue version)?

$ cue version v0.4.2 darwin/amd64

Does this issue reproduce with the latest release?
yes
What did you do?

At first I thought it was a formatting bug in the vscode extension, but it seems to be reproduced in cue fmt, so I'm reporting it.
https://github.com/johnallen3d/vscode-cue-fmt/issues/8
What did you expect to see?
What did you see instead?
I don't want commas to be added after formatting.
❯ cat test.cue
test: {
	test_list: {
		test_list_arr: [
			{
				name: "hoge"
			},
			{
				name: "fuga"
			},
		]
		// list: [
		//   {
		//     name: "hoge"
		//   }
		// ]
	}
	test_list2: {
		create: [
			{}
			// {
			//   name: "hoge"
			// },
			// {
			//   name: "fuga"
			// },
		]
	}
}

❯ cue fmt test.cue

❯ cat test.cue
test: {
	test_list: {
		test_list_arr: [
			{
				name: "hoge"
			},
			{
				name: "fuga"
			},
		]
		// list: [
		//   {
		//     name: "hoge"
		//   }
		// ]
	}
	test_list2: {
		create: [
			{}                        <-------- Removing this object will fix it, but I don't want to remove it.
			// {
			//   name: "hoge"
			// },
			// {
			//   name: "fuga"
			// },,,,,,                <------- this
		]
	}
}

Here's a simple testscript reproducer:
exec cue fmt x.cue
cp x.cue x1.cue
exec cue fmt x.cue
cmp x.cue x1.cue

-- x.cue --
[
	{} //
]

This fails for me as follows:
> exec cue fmt x.cue
> cp x.cue x1.cue
> exec cue fmt x.cue
> cmp x.cue x1.cue
--- x.cue
+++ x1.cue
@@ -1,3 +1,3 @@
 [
-	{} //,,
+	{} //,
 ]

FAIL: /tmp/testscript108976944/x.txtar/script.txt:4: x.cue and x1.cue differ
error running /tmp/x.txtar in /tmp/testscript108976944/x.txtar

testscript: exit 1

I am pretty sure that this is a duplicate of https://github.com/cue-lang/cue/issues/1478, which is a bit older and has been correctly labelled for some time as well.


HOTFIX: fix threading issue in MeteredKeyValueStore

MeteredKeyValueStore wasn't thread safe. Interleaving operations could modify the state, i.e, the key and/or value which could result in incorrect behaviour.

@guozhangwang @mjsax @bbejeck

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/6389/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/6374/
Test PASSed (JDK 8 and Scala 2.12).

merged to trunk and 0.11


References are missing for type bound procedures

For the code below, the following two requests are missing references:
fortls --debug_rootpath . --debug_references --debug_filepath test2.f90 --debug_line 11 --debug_char 12
fortls --debug_rootpath . --debug_references --debug_filepath test2.f90 --debug_line 17 --debug_char 12
The first asks for references of subroutine car, the second for references of dar. The answer has only the subroutine and end subroutine lines. But it should also contain the reference in the type definition mytype, and in my opinion, it should also contain any usage of these type bound procedures (call self%car and call self%dar).
Related to #88.
module mod

type mytype
contains
   procedure, public :: car => car
   procedure, public :: dar
end type mytype

contains

subroutine car(self, i)
   class(mytype) :: self
   integer :: i
   call self%dar(real(i))
end subroutine car

subroutine dar(self, r)
   class(mytype) :: self
   real :: r
   call self%car(int(i))
end subroutine dar

end module mod

As a sidenote: If I ask for definition of type-bound procedure car or dar via
fortls --debug_rootpath . --debug_definition --debug_filepath test2.f90 --debug_line 5 --debug_char 25

fortls --debug_rootpath . --debug_definition --debug_filepath test2.f90 --debug_line 6 --debug_char 25

I get the line themselves. I would rather expect to get the "subroutine car" and "subroutine dar" lines. In fact, currently I do not know what to ask for to jump from the type bound procedure declaration to the definition of the subroutine/function itself, if these have the same name.

Thanks for the report. It looks like symbol differentiation when objects have the same name needs to be improved. I think this will fix the "sidenote" case too.
There is a GoTo Implementation request that I can implement that would allow you to jump straight to subroutine dar from call self%dar statements. However, I am not sure if it is universally implemented in editors since it is part of the newer v3 specification. Other then that there is no way to jump from the procedure, public :: dar line to its implementation since there are two symbols that match the "definition" request, making things ambiguous.
As for call self%dar results in find references requests for subroutine dar. The specification is generally more "symbol" based in which case the symbol referenced by %dar is the type-bound method and not its implementation so generally the find results would not "flow through" that link. Personally, I think this way makes things a little more explicit and doesn't really add unnecessary steps.

Thanks a lot. Works fine. As I just saw emacs has an lsp-goto-implementation function, which does the job. It is often rather confusing to find out which of the many packages within emacs does which job. I have not yet figured out signature help in emacs. All in all, the current state of fortls and emacs already helps a lot in navigating within a big code base. From what I saw, there still seem to be a number of minor issues (completition lists).


Download panel pack in word doc

Is your feature request related to a problem? Please describe.
I'm always frustrated when I download a panel pack in PDF and cannot edit it. The JAC cannot get a licence for everyone so I have to spend hours editing the PDF in word.
Describe the solution you'd like
I would like to be able to download the panel pack in a word document.
Describe alternatives you've considered
Waiting off for panellist app development or keeping PDF. Problem with latter is we cannot get a licence for everyone and although waiting for panellist app would have been ideal we need to do more ground work for this. There is an immediate need for these to be easier to having a word download is a good fix.

@warrensearle there we go :) Will leave to you for estimate and assignee.

Great, thanks @Rebecca-mcknight1991.
Am discussing with @tomlovesgithub now so we'll estimate and get cracking.
Would like to re-iterate that we're treating this as a 'quick fix' whilst we work up a Panelist App and move towards going paperless.

This might be useful: https://phppot.com/javascript/how-to-export-html-to-word-document-with-javascript/

@warrensearle thanks Warren. I'll add the tickets about downloads but this is definitely slower time.


printing out the details of objects

Preliminary Checks

[X] This issue is not a duplicate. Before opening a new issue, please search existing issues.
[X] This issue is not a question, bug report, or anything other than a feature request directly related to this project.

Proposal
how to to print out the details of objects in terminal  in here?
like if I want to print something like this in terminal after I run here:
height ,width, class, distance and confidence, please?
what I am planning is that after the detection I want to send this information via UDP
Use-Case
No response
Anything else?
No response

I got it but why
print(object.label) whenever I print it out I get unknown only???

Use print(object.raw_label) instead.


Duplicate eye surface

Another attempt at making sure our VRSurfaces have the image effects/components copied to them.

I've added a VREye (with a VRSurface child) next to VRViewer in the VRDisplayTracked prefab. If the configuration calls for one eye, it uses this one and doesn't create any new objects at runtime. If the configuration calls for more than one eye (and there is a VREye found in the scene), it duplicates the VReye that is found, which also duplicates the VRSurface and all of its components and image effects that a developer might want on there for their game.
Should probably add in some error checking for if the number of VRViewers or VREyes in the scene exceeds that number of VRViewers or VREyes expected from the DisplayConfig (same for VRSurfaces).

Attempts to solve https://github.com/OSVR/OSVR-Unity/issues/75

This looks good to me on a sight review.

This passed my tests, using a "Particles.unity" scene distributed with Unity's Standard Assets package. The image effects seem to work just fine (depth of field, vignette and chromatic abberation, color correction curves).


Improve documentation on how to replace Scene3D plugin

Following https://github.com/gazebosim/gz-gui/pull/485:

Pointing to SDF code in Migration.md and reference it from the log message 781cecb87e90d3b94b3f362d7034d07e5fbec0e9
Fix format in 781cecb87e90d3b94b3f362d7034d07e5fbec0e9

Fixes https://github.com/gazebosim/gz-gui/issues/484

Can you resolve the conflicts @j-rivero? Otherwise, this looks like it's good to go. And @ahcorde for one more look.

@ahcorde can you give this another look?


Event triggering not recognised as valid syntax

Describe the bug
There is a syntax error at the -> token.
To Reproduce
The minimized test case (test.sv):
module foo(input clk);
  event a;

  always @(posedge clk)
    -> a;
endmodule

Include any options used.
>> verible-verilog-syntax ../test.sv
../test.sv:5:5-6: syntax error at token "->"

Actual behavior:
The valid syntax is rejected
Expected behavior
In SystemVerilog-2017 Standard (LRM), section 15.5.1.
Syntax 15-1
event_trigger ::=
 -> hierarchical_event_identifier ;
| ->> [ delay_or_event_control ] hierarchical_event_identifier ;

Hello,
I am new to how verible development works - I see tgorochowik added this to the release roadmap above.  What does that mean in terms of an ETA for a release?
Also, are there any known workarounds?

Hi @Lightborne it most definitely is! I cannot provide any ETA at this moment though. Would you be interested in looking into this yourself and submitting a PR?

@Lightborne I don't have the issue when decorating the always block in a begin/end. Could that be a workaround?
I have very few event in my codebase, if you can confirm it only fails on naked always block, it would help narrow the issue.
The following two cases passes:
module foo (
    input clk
);
  event a;

  always @(posedge clk) begin
    ->a;
  end
endmodule

module foo(input clk, b);
  event a;

  always @(posedge clk)
    if (b)
      -> a;
endmodule

@corco  - wrapping in begin/end is a good workaround.  Thanks!


Merge SKGLDrawable into the view code

there was not that much code duplication
far more control per platform
surface needs to query the context for the sampls permitted - Fixes #727
renamed SKDrawable in preparateion of the incomming PR and because it was not descriptive anymore

OPS Build status updates of commit a215f55:
:clock10: Preparing: average preparing time is 1 min(s) 50 sec(s)

OPS Build status updates of commit a215f55:
:clock10: Incremental building: average incremental building time is 22 sec(s)

OPS Build status updates of commit a215f55:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

samples/Basic/Android/SkiaSharpSample/SkiaSharpSample.csproj
:white_check_mark:Succeeded

samples/Basic/Xamarin.Forms/SkiaSharpSample.Android/SkiaSharpSample.Android.csproj
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.Android/SKGLSurfaceViewRenderer.cs
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.Android/SKGLTextureViewRenderer.cs
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.Apple/SKCGSurfaceFactory.cs
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.Apple/SKCanvasLayer.cs
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.AppleiOS/SKCanvasView.cs
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.AppleiOS/SKGLLayer.cs
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.AppleiOS/SKGLView.cs
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.Desktop/SKGLControl.cs
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.Mac/SKCanvasView.cs
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.Mac/SKGLLayer.cs
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.Mac/SKGLView.cs
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.Shared/SKGLDrawable.cs
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.Tizen/SKGLSurfaceView.cs
:white_check_mark:Succeeded

source/SkiaSharp.Views/SkiaSharp.Views.UWP/SKSwapChainPanel.cs
:white_check_mark:Succeeded

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


Remove generated zone test files

While testing #9497 i noticed that these generated files were added to version control.
This is to remove them from version control.
I  verified that pytest src/command_modules/azure-cli-network/azure/cli/command_modules/network/tests/latest/ still passes after removing zone*_export.txt files.

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

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[ ] I adhere to the Command Guidelines.

rebased on top of dev so there wasn't merge conflict. Until someone else does a commit :)

@tjprescott all ready for merge :). All checks passed


Manually deploy cluster components on Equinix infra for dev testing

This is to create a dev environment for the Green Reviews WG.
Steps

[ ] Create local kind cluster
[ ] Bootstrap Cluster API on kind cluster
[ ] Add API key to create worker cluster on Equinix infrastructure
[ ] https://github.com/cncf-tags/green-reviews-tooling/issues/5
[ ] Share kubeconfig with other WG contributors to reuse the same clusters
[ ] Document this process on the green-reviews-tooling repository
[ ] Document this in the design doc

Note: Falco can be deployed by the WG contributors in this dev environment to ensure that it can run alongside Kepler without any issues. However, we aim to extract this so that CNCF Project maintainers are responsible for configuring the deployment of the CNCF Project itself.

Adding myself

I am also up for this 👍🏽

I have a question here: can we involve the Falco guys to get Falco deployed manually in the cluster as a first step? We could just give them the kubeconfig and get started while we think more about the pipeline approach. What do you think?

Could we start by asking the Falco team how they would recommend we do the install? Maybe we can install it rather than giving access to the cluster?

Falco maintainers are in the process of creating a new repository (https://github.com/falcosecurity/cncf-green-review-testing) that will store everything needed from their side e.g. Falco deployment manifests,  synthetic workload deployment manifests, benchmark tests, etc. However, Falco maintainers have less availability until mid-December.
It would be better to go with a workaround until then!

They might use Ansible but I'm not sure: https://github.com/falcosecurity/kernel-testing/blob/main/ansible-playbooks/roles/bootstrap/tasks/main.yml

Synthetic workload has been installed we choose https://github.com/GoogleCloudPlatform/microservices-demo/tree/main/helm-chart#readme and we install it manually via helm, here there is a pull request for the 2-lines documentation on how to reproduce it

I think we can close this issue, we have developed manually almost everything except from Falco


Cannot use Hashmap<String, String> for default_headers

I can use a HashMap<&str, &str> for default_headers. But I cannot use HashMap<String, String> . Is there a way to change this?
I guess a follow-up question is why the a HeaderMap requires the keys have a 'static lifetime. This makes inserting headers that are not known at compile-time tricky.
As always -- thanks for making this library!

Thanks for the questions!

I can use a HashMap<&str, &str> for default_headers. But I cannot use HashMap<String, String> . Is there a way to change this?

I believe this is because HeaderName doesn't implement TryFrom<String>, even though it does implement TryFrom<&str> and TryFrom<&String>, which seems a little odd to me and it probably should.

I guess a follow-up question is why the a HeaderMap requires the keys have a 'static lifetime. This makes inserting headers that are not known at compile-time tricky.

This might be a question for the http library, since Isahc just re-exports HeaderMap and other header types from that library. I believe the reason is a balance of header validation at compile time vs. run time. When supplying a &'static str, there's a good chance that the header name is hard-coded so panicking due to invalid headers makes some sense, but for unknown headers panicking isn't appropriate.
By the way, the way to insert unknown header names into a HeaderMap is to first turn your string into a HeaderName using HeaderName::try_from, then giving that to the HeaderMap.

I've opened an upstream issue to add support for this: https://github.com/hyperium/http/pull/479

This is now supported as of http 0.2.5. The following now compiles with the current version of Isahc if you update your transient dependencies via cargo update:
let mut default_headers: HashMap<String, String> = HashMap::new();
default_headers.insert("foo".to_string(), "bar".to_string());

let client = isahc::HttpClient::builder()
    .default_headers(default_headers)
    .build()?;


add Semaphore CI

The icon I want is:

Name: Semaphore CI
URL: https://semaphoreci.com/
Link to icon: https://seeklogo.com/vector-logo/273888/semaphore

Please review pr #327.

@ryuakaa it looks good to me but I'm not a maintainer of this project. :wink:
But so far it seems that reviews by edent are done in a very timely manner.
Thank you for your contribution!

Thank you @alexanderadam and also @edent for reviewing my pr :smile:


Add VERSION_INFO block to Microsoft.WindowsAppRuntime.Bootstrap.dll

Because this native library must match, so to speak, with an installed runtime, it would be greatly helpful if it had a VERSION_INFO block with origin information.

It would also be nice if it disclosed what "Mdd" actually stands for in its description (and if not there, somewhere in the documentation?).

@sredna Microsoft.DynamicDependencies

VERSIONINFO is in the Insights.dll in 1.2. Injecting it into other DLLs is complicated due to the info not known until after they're built so they'll have to wait for vNext

Fixed.


Text input using IME renders outside when having a wrapped editor

VSCode Version: 1.13.0-insider
OS Version: Windows 10 Build 15063

Text input using IME (Chinese and Japanese, Korean not test) are duplicated and do not jump to the next line while typing out of the editor

Steps to Reproduce:
1.set editor.wordWrap on
2.input some text in one line and greater than the width of editor using IME

This still happens! In this screenshot, the word “進行” was entered, and the “行” is displayed on both the current line and the line on which it's supposed to be. Pressing enter to confirm the word in the IME makes the first copy disappear.

VSCode Version:1.5.1
OS Version:Mac os 10.15.7
I met the same problem when i input Chinese use the default IME on MAC OS

Hi thank you for filing this issue. We have recently introduced a setting called editor.experimentalEditContextEnabled which should fix this issue. The setting will be available in the next Insiders. This issue will be closed but feel free to let us know if you see any other issues when this setting is enabled.


AttributeError at /admin/djangocms_blog/post/add/ 'NoneType' object has no attribute 'namespace'

This comes from trying to create a new Post. I have a Config setup and a CMS Page with that Config assigned as the App.
 File "/Users/kayla/dev/client/rebuild/venv/lib/python3.7/site-packages/djangocms_blog/admin.py", line 338, in get_fieldsets     if related and Post.objects.namespace(config.namespace).active_translations().exists(): AttributeError: 'NoneType' object has no attribute 'namespace'
I am on the 1.0.0rc1 beta version. Is this a known issue? Or did I do something wrong?

I got around this by explicitly setting BLOG_USE_RELATED = False in my settings.py even though my Blog Config already had Related Posts unchecked.

@pinksharpii I can't reproduce the original issue.
Apparently it can't load the current configuration, but it should be explicitly asked when creating a new blog post, do you get a selection step like the one below when creating a new post?

The blog post admin URL should be something like https://www.mysite.com/en/admin/djangocms_blog/post/add/?app_config=1

reopening as it's a legitimate issue

I just encountered this same issue - is the short term fix adding the BLOG_USE_RELATED = False setting?

@pdbethke what's the PARLER_LANGUAGES configuration? I suspect that some apphook config instances are not translated in your case
Could you report versions of

Django
django-appdata
aldryn-apphooks-config

we can easily add a check on config on the reported line, but I'd rather understand the root issue which cause config to be None

I have the same issue.
This is my parler setting:

PARLER_LANGUAGES = {
1: (
{'code': 'en-us'},
),
'default': {
'fallbacks': ['en-us'],
}
}

Using BLOG_USE_RELATED = False in settings.py solves it somehow though.


./install-nethunter-termux installation error

EDIT: Says roots is corrupted, how can I fix it?
When I run the ./install-nethunter-termux when it gets ro rootft is cancels and doesn't open up nethunter after installation
--2024-10-14 22:49:57--  https://kali.download/nethunter-images/current/rootfs/kalifs-arm64-full.tar.xz
Resolving kali.download (kali.download)... <IP_ADDRESS>, <IP_ADDRESS>, 2606:4700::6811:feef, ...
Connecting to kali.download (kali.download)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2024-10-14 22:49:58 ERROR 404: Not Found.
Any help would be great!

the server is down, havent find any edited file to work with it, you can always download the tar.gz file from the repo and install it manually with chroot

first dont call idiot, second i modified the file,  so the full version works, only on arm (your phone version)
download using and execute using
wget
https://download2390.mediafire.com/yfgucoxgsgfg7EnC22iS_HkDojVzzkbzIG_X2_pqyIMKJNhErb43K0yNSHmDG_7fIjUWM6z9tf8h7N996qI4cqfv-AfWEDc8LB52sgea61vLmoUrCwxR4ywXpGB8Am2p5_1DX36li9akQVWOZNHq3dt4KPYjFDkP64ekIR_-_4vhBA/w0vcju4re95x3m8/install-nethunter-termux && chmod +x install-nethunter-termux && ./install-nethunter-termux

first dont call idiot, second i modified the file,  so the full version works only on arm (your phone version)
download using and execute using
wget
https://download2390.mediafire.com/yfgucoxgsgfg7EnC22iS_HkDojVzzkbzIG_X2_pqyIMKJNhErb43K0yNSHmDG_7fIjUWM6z9tf8h7N996qI4cqfv-AfWEDc8LB52sgea61vLmoUrCwxR4ywXpGB8Am2p5_1DX36li9akQVWOZNHq3dt4KPYjFDkP64ekIR_-_4vhBA/w0vcju4re95x3m8/install-nethunter-termux && chmod +x install-nethunter-termux && ./install-nethunter-termux

also when starting use
sudo apt update && sudo apt install vncserver vncpasswd

this system has lots of problems,  i would recomend using the original version but i cant find it anywhere

this system has lots of problems, i would recomend using the original version but i cant find it anywhere

Okay thank you for helping me out!!

first dont call idiot, second i modified the file, so the full version works only on arm (your phone version)
download using and execute using
wget https://download1532.mediafire.com/e4arkyw4wdoggjzC1QXVZLBk9CaGyN2clHy-6JWaag-_pkLuAi9ebWJlGGcRs2NSQOinoYWVKXdyMLG3s51bABXsGowJEvER9O6UPQjAaObfYAsB_aq4veLRnOy9UaqUCeSosXwLvdoWgGqAq6IqTtH9RJHXppYNJ6ZvKo9_L2u6Iw/831mgcrfgvkol9p/install-nethunter-termux && chmod +x install-nethunter-termux && ./install-nethunter-termux

THANK YOU! That worked for me

first dont call idiot, second i modified the file, so the full version works only on arm (your phone version)
download using and execute using
wget https://download1532.mediafire.com/e4arkyw4wdoggjzC1QXVZLBk9CaGyN2clHy-6JWaag-_pkLuAi9ebWJlGGcRs2NSQOinoYWVKXdyMLG3s51bABXsGowJEvER9O6UPQjAaObfYAsB_aq4veLRnOy9UaqUCeSosXwLvdoWgGqAq6IqTtH9RJHXppYNJ6ZvKo9_L2u6Iw/831mgcrfgvkol9p/install-nethunter-termux && chmod +x install-nethunter-termux && ./install-nethunter-termux

THANK YOU! That worked for me

it may have some problems, just ask chatgpt it may solve them as theyre some common problems when installing vncserver


Cant get an address of ETC

Hello!
We encountered an issue when attempting to retrieve an Ethereum Classic (ETC) address on the Ethereum Classic network in Trust Wallet. The address returned is identical to the one for the BEP20 network, which is incorrect since these networks operate on different protocols and should generate distinct addresses.

Hello @danilkharlan
You're experiencing transcript error. It sounds like your query would be best dealt with by the support team.
I'll have to refer you to the official support live chat with the ticket ID TRT07638
Please see the link below to our dedicated support line:
Trustwallet Network DApps Support Ticket Requests.
Click on the live chat icon at the bottom corner of the page to initiate chat with a live support agent.

Hello @danilkharlan! Do you mind sharing steps to reproduce?

But have you added Ethereum Classic network in your dapp in the list of supported networks? Have you switched to it?  See docs https://docs.reown.com/appkit/flutter/core/custom-chains
From your steps it feels to me that you connect with Ethereum by default and you just then call getAddress(), therefor you get Ethereum address.
getAddress() is relative to the current selected netowork in your DApp.

selectedChain value is 61 that equal to Etherium clasic network,but I get BEP20 address(

Can you share your code?

showLoader();
final network = SupportedNetwork.getNetworkFor(
assetCode: state.assetNetworkModel!.assetCode,
networkCode: state.assetNetworkModel!.networkCode,
);
if (network != null) {
final res = await getIt().changeNetwork(network);
}
final address = getIt<IReownService>().getWalletAddress();

emitAction(CryptoWithdrawalAction.updateAddress(address, walletType));

@override

Future changeNetwork(SupportedNetwork network) async {
if (!isConnected) return;
try {
 if (_appKitModal.selectedChain?.chainId == network.chainID) return;
  final chain = ReownAppKitModalNetworks.getNetworkById(
      NetworkUtils.eip155, network.chainID ?? '');
  await _appKitModal.selectChain(chain, switchChain: true);
  _appKitModal.launchConnectedWallet();
  final chainId = int.tryParse(network.chainID ?? '0');
  final result = await _appKitModal.request(
    topic: _appKitModal.session!.topic,
    chainId: _appKitModal.selectedChain!.chainId,
    request: SessionRequestParams(
      method: MethodsConstants.walletSwitchEthChain,
      params: [
        {'chainId': '0x${chainId?.toRadixString(16)}'}
      ],
    ),
  );
} catch (e) {
  _streamController.addError(e);
}

}
@override
String getWalletAddress() =>
_appKitModal.session?.getAddress(NetworkUtils.eip155) ?? '';

But are you adding Ethereum Classic to ReownAppKitModalNetworks before initializing AppKitModal?

Here is my init method.Is it correct?
void init({required BuildContext context}) async {
if (_isInitialized) return;
 ReownAppKitModalNetworks.addSupportedNetworks(
    NetworkUtils.eip155,
    ReownConstants.supportedNetworks,
  );

_appKitModal = ReownAppKitModal(
  context: context,
  projectId: ReownConstants.projectId,
  enableAnalytics: true,
  logLevel: LogLevel.debug,
  includedWalletIds: {
    ReownConstants.trustWalletId,
    ReownConstants.metaMaskWalletId,
  },
  metadata: PairingMetadata(
    name: ReownConstants.appName,
    description: 'Mobile app',
    url: """",
    icons: [""""],
    redirect: Redirect(native: """""),
  ),
);

// Set up listeners for modal events
_appKitModal.onModalConnect.subscribe((ModalConnect? event) {
  notifyListeners('onModalConnect');
  _onConnect?.call();
});
_appKitModal.onModalUpdate
    .subscribe((ModalConnect? event) => notifyListeners('onModalUpdate'));
_appKitModal.onModalNetworkChange.subscribe(
    (ModalNetworkChange? event) => notifyListeners('onModalNetworkChange'));
_appKitModal.onModalDisconnect.subscribe(
    (ModalDisconnect? event) => notifyListeners('onModalDisconnect'));
_appKitModal.onModalError
    .subscribe((ModalError? event) => notifyListeners('onModalError'));
_appKitModal.onSessionExpireEvent.subscribe(
    (SessionExpire? event) => notifyListeners('onSessionExpireEvent'));
_appKitModal.onSessionUpdateEvent.subscribe(
    (SessionUpdate? event) => notifyListeners('onSessionUpdateEvent'));
_appKitModal.onSessionEventEvent.subscribe(
    (SessionEvent? event) => notifyListeners('onSessionEventEvent'));
_appKitModal.appKit!.core.relayClient.onRelayClientConnect.subscribe(
    (EventArgs? event) => notifyListeners('onRelayClientConnect'));
_appKitModal.appKit!.core.relayClient.onRelayClientError
    .subscribe((EventArgs? event) => notifyListeners('onRelayClientError'));
_appKitModal.appKit!.core.relayClient.onRelayClientDisconnect.subscribe(
    (EventArgs? event) => notifyListeners('onRelayClientDisconnect'));

try {
  await _appKitModal.init();
  final list = _appKitModal.appKit?.authKeys.storage.getAll() as List<Map>?;
  if (selectedWallet == null) {
    for (final map in list ?? []) {
      final listing = map['listing'];
      if (listing != null) {
        final info = ReownAppKitModalWalletInfo.fromJson(map);
        _appKitModal.selectWallet(info);
        _appKitModal.reconnectRelay();
      }
    }
  }

  _isInitialized = true;
  notifyListeners('isInitialized');
} catch (e) {
  notifyListeners('isInitialized');
}

}

Thanks! Can you explain again the issue? Cause as far as I know Ethereum Classic Ethereum Mainnet uses the same address format. Furthermore, the addresses depending on the network are given by the connected wallet (Trust in this case) and not by AppKit. I'm a bit lost, sorry...

Yes,you are right!
In looks weird,but ETC has different addresses in networks...

In metamask the same addresses,but in trust different
can you handle it?

Sorry, seems to an issue on Trust side. We, as AppKit don't mange neither keys nor addresses. Essentially we just allow secure communication between dapp and wallet but keys (therefor addresses) are always on wallet side. You can try opening an issue to them https://github.com/trustwallet maybe?

ill investigate it and will back soon

Hello @danilkharlan I will close this for now since there are no updates but feel free to reopen if you consider there's still an issue.


Add Jason Swails as a code maintainer for AmberTools

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Is this the right process to get added as a maintainer for a recipe?

This would work but it will also create a new build (or attempt to) innecessarily. We usually prefer using the bot for this. See this command.

Thank you!


keep stat() and list() lastModified upto same resolution

fixes #1632

Quick note (I'm the OP of #1632) I found in my tests that to keep that same behaviour I needed to use:
LastModified.Add(-time.Millisecond * 500).Round(time.Second)

instead of
LastModified.Round(time.Second)

to floor the time, not round it. Not sure if that will solve the tests not completing

No it shouldn't be Round instead it should be Truncate() @jhwz

No it shouldn't be Round instead it should be Truncate() @jhwz

Ah right, that works too

@harshavardhana can't we make Stat() to show more precise time instead of truncating to second ?
I don't think it will break anything since is this a go library and time.Parse(time.RFC3339, "2022-04-16T13:37:01.511096Z") works just fine (time.RFC3339 without Nano)
I think it is just better to keep time precision here rather than losing it (not sure what is the effect for bucket replication here as well)

@harshavardhana can't we make Stat() to show more precise time instead of truncating to second ?
I don't think it will break anything since is this a go library and time.Parse(time.RFC3339, "2022-04-16T13:37:01.511096Z") works just fine (time.RFC3339 without Nano)
I think it is just better to keep time precision here rather than losing it (not sure what is the effect for bucket replication here as well)

The problem is there is no time precision allowed in AWS S3. It's only up to second precision @vadmeste
That's why millisecond values don't make sense.

Tested this with AWS S3 @vadmeste the ListObjects doesn't have the millisecond resolution
AWS_REGION=us-east-1 ./example
2022/04/17 13:34:42 first page results:
Name:           hosts
ListObjectsV2 -> Last modified:  2022-04-17 20:33:17 +0000 UTC
Size:           303
Storage class:  STANDARD

HeadObject() Last Modified:  2022-04-17 20:33:17 +0000 UTC

package main

import (
	"context"
	"fmt"
	"log"

	"github.com/aws/aws-sdk-go-v2/aws"
	"github.com/aws/aws-sdk-go-v2/config"
	"github.com/aws/aws-sdk-go-v2/service/s3"
)

func main() {
	// Load the Shared AWS Configuration (~/.aws/config)
	// cfg, err := config.LoadDefaultConfig(context.TODO(), config.WithSharedConfigProfile("minio"), config.WithEndpointResolverWithOptions(customResolver))
	cfg, err := config.LoadDefaultConfig(context.TODO(), config.WithSharedConfigProfile("s3"))
	if err != nil {
		log.Fatal(err)
	}

	// Create an Amazon S3 service client
	client := s3.NewFromConfig(cfg, func(opts *s3.Options) {
		opts.UsePathStyle = true
	})

	// Get the first page of results for ListObjectsV2 for a bucket
	output, err := client.ListObjectsV2(context.TODO(), &s3.ListObjectsV2Input{
		Bucket: aws.String("vadmeste"),
		Prefix: aws.String("hosts"),
	})
	if err != nil {
		log.Fatal(err)
	}

	log.Println("first page results:")
	for _, item := range output.Contents {
		fmt.Println("Name:          ", *item.Key)
		fmt.Println("ListObjectsV2 -> Last modified: ", *item.LastModified)
		fmt.Println("Size:          ", item.Size)
		fmt.Println("Storage class: ", item.StorageClass)
		fmt.Println("")
	}

	houtput, err := client.HeadObject(context.TODO(), &s3.HeadObjectInput{
		Bucket: aws.String("vadmeste"),
		Key:    aws.String("hosts"),
	})

	fmt.Println("HeadObject() Last Modified: ", *houtput.LastModified)
}

So this PR is valid and we should also perhaps remove millisecond resolution from the MinIO server.
// cc @kannappanr @klauspost

/cc @poornas does this change affect bucket replication ?


Clear dirty SSL error stacks before reading.

In OpenSSL, if there happens to be an error on the stack before
the read begins, that error can cause the read to fail.
"The current thread's error queue must be empty before the TLS/SSL I/O
operation is attempted, or SSL_get_error() will not work reliably."
-- https://www.openssl.org/docs/man1.1.1/man3/SSL_get_error.html
These manifest as difficult-to-debug application errors; handle these
more gracefully and improve the logging around what's going on.
Hopefully fixes #23144 and #24865.
@drfloob

Hi @bdhess . You'll need to sign the CLA before we can take a look at this.

@davidben Hi David, can you please also take a look and advise on how to log OpenSSL errors, if possible? Thanks in advance!

Thanks for making the change so far! The code looks much concise now.
Passing to @yihuazhang for a final review. Hi YIhua, could you please take a final look on this, please?

LGTM

@bdhess It seems the portability test fails: https://source.cloud.google.com/results/invocations/f92d91cc-eeb7-4d11-8230-a5dd78af7954/targets, and the failure seems relevant to this PR.
Would you mind taking a look? Thank you!

@ZhenLian I think I should've explicitly included another OpenSSL header for 1.0.2 backwards compatibility, but I don't have an easy way to test that change besides just kicking off the CI.  Hope this fixes it. :)

All test passed, except "import/copybara" is pending. Merging now...

@bdhess Thanks again for your contributing!


Add error icon and handle pip install errors

Comes from item in #14. Report refers to this line:
https://github.com/napari/napari-plugin-manager/blob/7f90aa83aceb1c093090d8213399ab6f615e1e5b/napari_plugin_manager/qt_plugin_dialog.py#L59

I think this is mostly an outdated comment because we do have some feedback methods to notify of errors now, so no need to have extra ones? Probably just needs to be deleted from the code to avoid confusion.


VEVO videos can't be played

[XCDYouTubeKit] No signature function in player script
[XCDYouTubeKit] Video operation finished with error:
Domain: XCDYouTubeVideoErrorDomain
Code:   150

Thank you for confirming.
I fixed the code(fix regex expression) but the app crashed.

*** Terminating app due to uncaught exception 'NSRangeException', reason: '-[__NSCFString substringWithRange:]: Range {9223372036854775807, 0} out of bounds; string length 1169095'

There are 3 commits that passed by SoneeJohn. Did you implement all of them ?

After fixing the regular expression, I applied 4 commits and it worked fine.
Thank you so much!


Error in ios 9.3

Hi, i use IOS 9.3 and the log not print anithing
let scout = ImageScout()
scout.scoutImageWithURI("http://.../image-scout-logo.png") { error, size, type in
if let unwrappedError = error {
println(unwrappedError.code)
} else {
println("Size: (size)")
println("Type: (type.rawValue)")
}
}

This code snippet is deprecated. Please install 1.0 and try again with the new example.


Consider adding troubleshooting info on setup instructions

Describe the issue or suggestion
Our Setup instructions from the command line don't currently have any troubleshooting information, and we do know that things can go wrong especially when folks try to install the workload via the CLI and have some NuGet.config that is changing the default feeds. The instructions we have currently would fail in that case, and we don't have any info currently to help them diagnose and fix the issue. If @IEvangelist or @bradygaster confirm that it is fine to add troubleshooting info in that setup page, I'd gladly contribute to it.

I'd say go ahead and write the info, we clearly need it and they can then tell us the right place for it.


feat: Store branch and dataset for benchmarks

Store branch and dataset for benchmarks.
This will make it easier to visualize the results of manual benchmark workflow across different branches and datasets.

@generall Please review


Request editor status

Add me and @IronCladDev please (⊙_⊙;)

I'm pretty sure they aren't accepting new editors at this time due to v3 being worked on.

I'm pretty sure they aren't accepting new editors at this time due to v3 being worked on.

I am happy if you add me to the repo, but I meant an entry for us

Isn't that bad. If anyone can create an entry without review some weird entries could be added.

We will obviously be adding some auto moderation and trust factors. So, people with a good trust level will be able to create/edit entries. People with a bad trust level will not be able to contribute to the project until they work that level up.

Done close the issue!

Glad to help!


NG UPDATE NOT WORKING going from angular 17 to angular 18

Command
update
Is this a regression?

[X] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
I have been migrating my projects from angular 17 to angular 18 using the update guide this week. Ever since v18.1.0 was released, the ng update command started to fail. 2 of my projects migrated just fine to version 18.0.6.
The reason for the failure is because of the temporary cli version 18.1.0 that is installed. The error messages is - "No matching version found for<EMAIL_ADDRESS>Seems like this package is missing. Can this be addressed as I can no longer migrate any project to version 18 ? Is there a way to specify which temporary cli version to use? If yes, then I can use this as a workaround for now. Please advise.
Minimal Reproduction
I have been migrating my projects from angular 17 to angular 18 using the update guide this week. Ever since v18.1.0 was released, the ng update command started to fail. 2 of my projects migrated just fine to version 18.0.6.
The reason for the failure is because of the temporary cli version 18.1.0 that is installed. The error messages is - "No matching version found for<EMAIL_ADDRESS>Seems like this package is missing. Can this be addressed as I can no longer migrate any project to version 18 ? Is there a way to specify which temporary cli version to use? If yes, then I can use this as a workaround for now. Please advise.
Exception or Error
No response
Your Environment
angular v 17.3.11

Anything else relevant?
No response

Duplicate of https://github.com/angular/angular-cli/issues/27889


Revert "Prepare SwiftPM for the addition of Result to the stdlib"

Reverts apple/swift-package-manager#1912. The compiler change in https://github.com/apple/swift/pull/21370 is meant to keep existing Result types working by introducing an appropriate name-shadowing rule.

@swift-ci please smoke test

Awesome!


Set the widget as active when opened

This is not a permanent solution, as the tab gets moved to the end.

:+1:


[Bug]: Able to press a button and onclick of that button is executing when the button is in disabled state.

Is there an existing issue for this?

[X] I have searched the existing issues

Description
Able to press a button and onclick of that button is executing when the button is in disabled state. This issue started after recent update.
Steps To Reproduce
1.Create a button
2.Add a function in Onclick of that button
3.Click on the button after disabling it
Public Sample App
No response
Version
Cloud

@Tooluloope can you get this triaged?

@dilippitchika I am looking into this issue, I will push a fix soon.


Changed All Twitter Icons to X Icons

I have changed all the Twitter icons to X Icons with the Updated code and removed conflicts.

Please merge my pull request under gssoc-ext,hacktoberfest

Hey @Bhanuprakash842 please resolve merge conflicts.

@Bhanuprakash842 ?

I will resolve the conflicts now..

Hey @Bhanuprakash842  your changes are not visible and your deploy preview has not been generated by netlify please pass all the checks by netlify.


Make installing for filetransfer scheme optional

Is your feature request related to a problem? Please describe.
I only need files from S3-Buckets and I don't want to install dependencies which handle file-transfers with e.g. google drive.
Describe the solution you'd like
To learn how poetry enables this, please refer to this link. In essence, each subgroup must be specified under dependencies in the pyproject.toml file. I suggest considering the following groups: s3, gc, hf, beaker, and full (which installs all subgroups). Additionally, it’s important to consider a more user-friendly error message if the imported package is not installed. You can use importlib or a try-catch approach to achieve this.
Describe alternatives you've considered
The only alternative i considerd is using a packaged for each file-transfer scheme .
Additional context

Hey @SYDavidBrielbeck we'd be happy to accept a PR for this!

When I have the time I will have a look into it.


Updates to make plugin not send pages for warnings or errors

Cabot philosophy indicates pages should be sent for a critical alerts. This plugin alerts for all service status levels.

As noted comments are stylistic/personal preference. 👍 in general.


Want to embed multiple images into DZI image

I want to embed multiple images into DZI image, something similar to Andrea's work. I obviously do not need lamb or rabbit as a shadow image. Can find seadragon implementation in the following link: http://www.soulsolutions.com.au/silverlight/perumosaic/.
I have written a C# class to embed thumbnail images into a background image, and it works ok, however when i zoom it I am not getting the quality as the example mentioned above.
Any suggestions. I realise tile collection is a good way to embed multiple images ( by making them into a dzi file). But in my project there might be huge collection ranging from (100,000 to 1 million). I feel its impractical to download those many dzi files from server.
Please share your thoughts on how I could do this efficiently.

I'm closing old question threads. I'll just add here that we do now have working collection support (though not yet released or merged into master): #446.


Spark-pi-prometheus does not expose metrics port 8090

Tried this  example without any changes, and I figured out that spark-operator doesn't expose 8090 port on pods\services even if exposeDriverMetrics + exposeExecutorMetrics is set to "true".
$kubectl describe pod spark-pi-driver
Name:                   spark-pi-driver
Namespace:          default
Priority:                 0
PriorityClassName:
Node:                   node3/<IP_ADDRESS>
Start Time:            Thu, 11 Apr 2019 11:49:01 +0300
Labels:                  spark-app-selector=spark-575f1b9b71f74c918fa4d78afc830ad2
spark-role=driver
sparkoperator.k8s.io/app-name=spark-pi
sparkoperator.k8s.io/launched-by-spark-operator=true
version=2.4.0
Annotations:         prometheus.io/path: /metrics
prometheus.io/port: 8090
prometheus.io/scrape: true
Status:                  Running
IP:                 <IP_ADDRESS>
Containers:
spark-kubernetes-driver:
Container ID:  docker://96a8b70f6f5abc5478b5e5c79df784d67319f337e70b20d403be11230ad6a2a6
Image:          gcr.io/spark-operator/spark:v2.4.0-gcs-prometheus
Image ID:      docker-pullable://gcr.io/spark-operator/spark@sha256:9c585c4a794624439a5c957ae2d2cafe2048fee73c47de1ae28cfe03c9c5584f
Ports:         7078/TCP, 7079/TCP, 4040/TCP
Same with services, no 8090 exposed anywhere:
$kubectl get svc | grep spark
spark-pi-1554972540777-driver-svc         ClusterIP      None                    7078/TCP,7079/TCP             20m
spark-pi-ui-svc                           NodePort       <IP_ADDRESS>           4040:30543/TCP                20m
sparkop-metrics                           ClusterIP      <IP_ADDRESS>            10254/TCP                     18h
However, if I jump in pod itself and try some curls to <IP_ADDRESS>:8090 - I will find metrics working.
For now, I can expose 8090 port manually via simple kubernetes svc and scrape metrics without any problems, but just will be happy if spark-operator will expose them itself.
Or did I miss something?

Sure, we can expose the port by patching it through the webhook.

@liyinan926 I am using Sparkoperator to run my Spark applications.
In my SparkApplication, I have exposed REST APIs for some functional need. I am unable to access my REST API port.
Can you please suggest how can I expose port using Sparkoperator framework.

@liyinan926 recently there was a commit at spark that implements custom pod templates for drivers and executors. With this we should be able to omit using webhooks
https://github.com/apache/spark/commit/f6cc354d83c2c9a757f9b507aadd4dbdc5825cca

@rolandjohann pod templating is only available starting Spark 3.0. For Spark 2.4 and earlier, the webhook is still needed.

@liyinan926 is it going to be addressed in the near future?

@liyinan926 How can I expose the port 8090 in the driver and executor pods for my PodMonitor or ServiceMonitor to pick it up?

Hey @liyinan926 could you suggest some example for achieving " expose the port 8090 by patching it through the webhook."

@arijitdey @sahil-sawhney PR #935 will fix this and expose the port.

Thanks a lot, @liyinan926 . In which spark operator version this change would be released?

Thanks a ton @liyinan926 :)


 At the moment, there is no reason to stick with older versions of Go.

Anyways we have to bump up to higher than Go 1.20.
Since the crypto/ecdh package which we need to use in #37 requires Go ^1.20.
https://pkg.go.dev/crypto/ecdh?tab=versions


🚀 Release 2.0.0 is available

hello dominque, nice job, but a puffer probe is always missing, in reality there are 4, hot water, tpo, tpm and tank below, which would be the one that starts the solar pump
Discussed in https://github.com/dominikamann/oekofen-pellematic-compact/discussions/9

Originally posted by dominikamann February  8, 2023
Features:

Enables configuration of the number of heating circuits
Enables configuration of solar/sun support

Warnig:
New configuration options have been added which may cause a break. Please check if your system still works after the update. If not, please delete your device and configure it again.
This discussion was created from the release 🚀 Enables configuration of the number of heating circuits and solar/sun support.

Great ... I will add it. Do you think the names are correct:
L_koll_temp: "Solar Thermal Collector Circuit Temperature"
L_spu: "Solar Thermal Circuit Temperature"
spu_max: "Solar Thermal Circuit Temperature Max"
Please confirm then i will publish a release.
Thanks

Von: lucaferrucci @.>
Gesendet: Donnerstag, 9. Februar 2023 13:24
An: dominikamann/oekofen-pellematic-compact @.>
Cc: Subscribed @.***>
Betreff: [dominikamann/oekofen-pellematic-compact] 🚀 Release 2.0.0 is available (Issue #10)
hello dominque, nice job, but a puffer probe is always missing, in reality there are 4, hot water, tpo, tpm and tank below, which would be the one that starts the solar pump
Discussed in #9https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Fdiscussions%2F9&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=zrizspMIkZum3%2FA%2BJds8XbYd7OZ8kieXdd5HBcbKxKU%3D&reserved=0
Originally posted by dominikamann February 8, 2023
Features:

Enables configuration of the number of heating circuits
Enables configuration of solar/sun support

[grafik]https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F29973737%2F217624206-831311b6-7284-49c9-bc29-8928bd65de6f.png&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=QOj9Za5HJtTSD3T0Lre0BSAa0hjAPjkt%2FAmKCQ3PC8k%3D&reserved=0
Warnig:
New configuration options have been added which may cause a break. Please check if your system still works after the update. If not, please delete your device and configure it again.

This discussion was created from the release 🚀 Enables configuration of the number of heating circuits and solar/sun supporthttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Freleases%2Ftag%2Fv2.0.0&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=g5Z%2B2%2FiRvf8TuF7xRAwrlYfRAjErW%2Ffhyaefpf0SY1k%3D&reserved=0.
—
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Fissues%2F10&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=D9%2BFLJoGfV%2FJB93rQOfxRqa4wPQ2MRVQLGQsHSrUCvk%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHEVZ2NLREBQWCPE43WRRBDWWTOWPANCNFSM6AAAAAAUWPNF4Y&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Ww3MKxblPzlAMKVdgTiYPEJYsSgeuNc%2BaqNh7tEowCI%3D&reserved=0.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

correct name in red, thanks thanks thanks
ps: i am also updating my dashboard thanks to you for the amazing work

Il giorno 9 feb 2023, alle ore 16:47, Dominik Amann @.***> ha scritto:
Great ... I will add it. Do you think the names are correct:
L_koll_temp: "Solar Thermal Collector Circuit Temperature”  (solar panel Temperature)
L_spu: "Solar Thermal Circuit Temperature”  Puffer lower  (lower buffer probe)
spu_max: "Solar Thermal Circuit Temperature Max”  (maximum puffer temperature)
Please confirm then i will publish a release.
Thanks

Von: lucaferrucci @.>
Gesendet: Donnerstag, 9. Februar 2023 13:24
An: dominikamann/oekofen-pellematic-compact @.>
Cc: Subscribed @.***>
Betreff: [dominikamann/oekofen-pellematic-compact] 🚀 Release 2.0.0 is available (Issue #10)
hello dominque, nice job, but a puffer probe is always missing, in reality there are 4, hot water, tpo, tpm and tank below, which would be the one that starts the solar pump
Discussed in #9https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Fdiscussions%2F9&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=zrizspMIkZum3%2FA%2BJds8XbYd7OZ8kieXdd5HBcbKxKU%3D&reserved=0
Originally posted by dominikamann February 8, 2023
Features:

Enables configuration of the number of heating circuits
Enables configuration of solar/sun support

[grafik]https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F29973737%2F217624206-831311b6-7284-49c9-bc29-8928bd65de6f.png&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=QOj9Za5HJtTSD3T0Lre0BSAa0hjAPjkt%2FAmKCQ3PC8k%3D&reserved=0
Warnig:
New configuration options have been added which may cause a break. Please check if your system still works after the update. If not, please delete your device and configure it again.

This discussion was created from the release 🚀 Enables configuration of the number of heating circuits and solar/sun supporthttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Freleases%2Ftag%2Fv2.0.0&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=g5Z%2B2%2FiRvf8TuF7xRAwrlYfRAjErW%2Ffhyaefpf0SY1k%3D&reserved=0.
—
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Fissues%2F10&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=D9%2BFLJoGfV%2FJB93rQOfxRqa4wPQ2MRVQLGQsHSrUCvk%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHEVZ2NLREBQWCPE43WRRBDWWTOWPANCNFSM6AAAAAAUWPNF4Y&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Ww3MKxblPzlAMKVdgTiYPEJYsSgeuNc%2BaqNh7tEowCI%3D&reserved=0.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
—
Reply to this email directly, view it on GitHub https://github.com/dominikamann/oekofen-pellematic-compact/issues/10#issuecomment-1424409265, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2LNND7WJ76426EPO3KPVVLWWUGR7ANCNFSM6AAAAAAUWPNF4Y.
You are receiving this because you authored the thread.

Hi,
it's released. See https://github.com/dominikamann/oekofen-pellematic-compact/releases/tag/v2.0.1
Version: v2.0.1
[https://opengraph.githubassets.com/38d9779f52432064460ae6d2b419fb4d0bfc3e5c37a48de4eadca88d0d4d6887/dominikamann/oekofen-pellematic-compact/releases/tag/v2.0.1]https://github.com/dominikamann/oekofen-pellematic-compact/releases/tag/v2.0.1
Release Implement lower buffer temperature (solar) and fix naming of TPM · dominikamann/oekofen-pellematic-compacthttps://github.com/dominikamann/oekofen-pellematic-compact/releases/tag/v2.0.1
Features: Implement "Solar Thermal Buffer Storage Temperature lower area" & "Solar Thermal Buffer Storage Temperature Max" Fixes: Change "Buffer Storage Temperature lower area" to "Buffer Storag...
github.com
Thank you for using it 🙂

Von: lucaferrucci @.>
Gesendet: Donnerstag, 9. Februar 2023 16:57
An: dominikamann/oekofen-pellematic-compact @.>
Cc: Dominik Amann @.>; Comment @.>
Betreff: Re: [dominikamann/oekofen-pellematic-compact] 🚀 Release 2.0.0 is available (Issue #10)
correct name in red, thanks thanks thanks
ps: i am also updating my dashboard thanks to you for the amazing work

Il giorno 9 feb 2023, alle ore 16:47, Dominik Amann @.***> ha scritto:
Great ... I will add it. Do you think the names are correct:
L_koll_temp: "Solar Thermal Collector Circuit Temperature” (solar panel Temperature)
L_spu: "Solar Thermal Circuit Temperature” Puffer lower (lower buffer probe)
spu_max: "Solar Thermal Circuit Temperature Max” (maximum puffer temperature)
Please confirm then i will publish a release.
Thanks

Von: lucaferrucci @.>
Gesendet: Donnerstag, 9. Februar 2023 13:24
An: dominikamann/oekofen-pellematic-compact @.>
Cc: Subscribed @.***>
Betreff: [dominikamann/oekofen-pellematic-compact] 🚀 Release 2.0.0 is available (Issue #10)
hello dominque, nice job, but a puffer probe is always missing, in reality there are 4, hot water, tpo, tpm and tank below, which would be the one that starts the solar pump
Discussed in #9https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Fdiscussions%2F9&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=zrizspMIkZum3%2FA%2BJds8XbYd7OZ8kieXdd5HBcbKxKU%3D&reserved=0
Originally posted by dominikamann February 8, 2023
Features:

Enables configuration of the number of heating circuits
Enables configuration of solar/sun support

[grafik]https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F29973737%2F217624206-831311b6-7284-49c9-bc29-8928bd65de6f.png&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=QOj9Za5HJtTSD3T0Lre0BSAa0hjAPjkt%2FAmKCQ3PC8k%3D&reserved=0
Warnig:
New configuration options have been added which may cause a break. Please check if your system still works after the update. If not, please delete your device and configure it again.

This discussion was created from the release 🚀 Enables configuration of the number of heating circuits and solar/sun supporthttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Freleases%2Ftag%2Fv2.0.0&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=g5Z%2B2%2FiRvf8TuF7xRAwrlYfRAjErW%2Ffhyaefpf0SY1k%3D&reserved=0.
—
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Fissues%2F10&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=D9%2BFLJoGfV%2FJB93rQOfxRqa4wPQ2MRVQLGQsHSrUCvk%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHEVZ2NLREBQWCPE43WRRBDWWTOWPANCNFSM6AAAAAAUWPNF4Y&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Ww3MKxblPzlAMKVdgTiYPEJYsSgeuNc%2BaqNh7tEowCI%3D&reserved=0.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
—
Reply to this email directly, view it on GitHub https://github.com/dominikamann/oekofen-pellematic-compact/issues/10#issuecomment-1424409265, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2LNND7WJ76426EPO3KPVVLWWUGR7ANCNFSM6AAAAAAUWPNF4Y.
You are receiving this because you authored the thread.

—
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Fissues%2F10%23issuecomment-1424423506&data=05|01||a7dea5fe0f1f42093f6208db0ab653dd|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115550436838259|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=wuhqXQFneiZWTbGY3MxWKtux3caCWbivmbJbRJIg6bc%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHEVZ2P2FINEMOWLAYWVYULWWUHWBANCNFSM6AAAAAAUWPNF4Y&data=05|01||a7dea5fe0f1f42093f6208db0ab653dd|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115550436838259|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=VRwxORjXel7NgZ55k9axG0lG%2F%2Bxgx3hQXs%2BSA%2FUk1O0%3D&reserved=0.
You are receiving this because you commented.Message ID: @.***>

Fantastic, tahnk you very much

Il giorno 9 feb 2023, alle ore 17:19, Dominik Amann @.***> ha scritto:
Hi,
it's released. See https://github.com/dominikamann/oekofen-pellematic-compact/releases/tag/v2.0.1
Version: v2.0.1
[https://opengraph.githubassets.com/38d9779f52432064460ae6d2b419fb4d0bfc3e5c37a48de4eadca88d0d4d6887/dominikamann/oekofen-pellematic-compact/releases/tag/v2.0.1]https://github.com/dominikamann/oekofen-pellematic-compact/releases/tag/v2.0.1
Release Implement lower buffer temperature (solar) and fix naming of TPM · dominikamann/oekofen-pellematic-compacthttps://github.com/dominikamann/oekofen-pellematic-compact/releases/tag/v2.0.1
Features: Implement "Solar Thermal Buffer Storage Temperature lower area" & "Solar Thermal Buffer Storage Temperature Max" Fixes: Change "Buffer Storage Temperature lower area" to "Buffer Storag...
github.com
Thank you for using it 🙂

Von: lucaferrucci @.>
Gesendet: Donnerstag, 9. Februar 2023 16:57
An: dominikamann/oekofen-pellematic-compact @.>
Cc: Dominik Amann @.>; Comment @.>
Betreff: Re: [dominikamann/oekofen-pellematic-compact] 🚀 Release 2.0.0 is available (Issue #10)
correct name in red, thanks thanks thanks
ps: i am also updating my dashboard thanks to you for the amazing work

Il giorno 9 feb 2023, alle ore 16:47, Dominik Amann @.***> ha scritto:
Great ... I will add it. Do you think the names are correct:
L_koll_temp: "Solar Thermal Collector Circuit Temperature” (solar panel Temperature)
L_spu: "Solar Thermal Circuit Temperature” Puffer lower (lower buffer probe)
spu_max: "Solar Thermal Circuit Temperature Max” (maximum puffer temperature)
Please confirm then i will publish a release.
Thanks

Von: lucaferrucci @.>
Gesendet: Donnerstag, 9. Februar 2023 13:24
An: dominikamann/oekofen-pellematic-compact @.>
Cc: Subscribed @.***>
Betreff: [dominikamann/oekofen-pellematic-compact] 🚀 Release 2.0.0 is available (Issue #10)
hello dominque, nice job, but a puffer probe is always missing, in reality there are 4, hot water, tpo, tpm and tank below, which would be the one that starts the solar pump
Discussed in #9https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Fdiscussions%2F9&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=zrizspMIkZum3%2FA%2BJds8XbYd7OZ8kieXdd5HBcbKxKU%3D&reserved=0
Originally posted by dominikamann February 8, 2023
Features:

Enables configuration of the number of heating circuits
Enables configuration of solar/sun support

[grafik]https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F29973737%2F217624206-831311b6-7284-49c9-bc29-8928bd65de6f.png&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=QOj9Za5HJtTSD3T0Lre0BSAa0hjAPjkt%2FAmKCQ3PC8k%3D&reserved=0
Warnig:
New configuration options have been added which may cause a break. Please check if your system still works after the update. If not, please delete your device and configure it again.

This discussion was created from the release 🚀 Enables configuration of the number of heating circuits and solar/sun supporthttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Freleases%2Ftag%2Fv2.0.0&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=g5Z%2B2%2FiRvf8TuF7xRAwrlYfRAjErW%2Ffhyaefpf0SY1k%3D&reserved=0.
—
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Fissues%2F10&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=D9%2BFLJoGfV%2FJB93rQOfxRqa4wPQ2MRVQLGQsHSrUCvk%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHEVZ2NLREBQWCPE43WRRBDWWTOWPANCNFSM6AAAAAAUWPNF4Y&data=05|01||9de2a8465cd948ce37c608db0a988b0c|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115422497387855|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Ww3MKxblPzlAMKVdgTiYPEJYsSgeuNc%2BaqNh7tEowCI%3D&reserved=0.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
—
Reply to this email directly, view it on GitHub https://github.com/dominikamann/oekofen-pellematic-compact/issues/10#issuecomment-1424409265, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2LNND7WJ76426EPO3KPVVLWWUGR7ANCNFSM6AAAAAAUWPNF4Y.
You are receiving this because you authored the thread.

—
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdominikamann%2Foekofen-pellematic-compact%2Fissues%2F10%23issuecomment-1424423506&data=05|01||a7dea5fe0f1f42093f6208db0ab653dd|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115550436838259|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=wuhqXQFneiZWTbGY3MxWKtux3caCWbivmbJbRJIg6bc%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHEVZ2P2FINEMOWLAYWVYULWWUHWBANCNFSM6AAAAAAUWPNF4Y&data=05|01||a7dea5fe0f1f42093f6208db0ab653dd|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638115550436838259|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=VRwxORjXel7NgZ55k9axG0lG%2F%2Bxgx3hQXs%2BSA%2FUk1O0%3D&reserved=0.
You are receiving this because you commented.Message ID: @.***>
—
Reply to this email directly, view it on GitHub https://github.com/dominikamann/oekofen-pellematic-compact/issues/10#issuecomment-1424457588, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2LNND7YNR6RKUWU5KH3763WWUKKXANCNFSM6AAAAAAUWPNF4Y.
You are receiving this because you authored the thread.


[Feature request] Deploy to environment  - next minor/major version

Hi Freddy,
I want to request a new feature in the action "Publish to Environment". Can you build a feature that you can choose to deploy the app in  "Current version", "next minor version", "next major version"?
Just like when you manually upload/install an app in BC?

This feature will be very handy when the customer tests something in a newer version than the production environment.
Thanks a lot!

Sounds like a good idea


Fix prettier import plugin

Fix prettier import plugin import.

[!IMPORTANT]
Once the PR list reduces we should run prettier to fix these issues across the repo and merge.

Just gonna redo this...


LiDAR/Semantic LiDAR sensor does not detect new added vehicle

Hi all,
I followed the official guide to add new vehicle into Carla: https://carla.readthedocs.io/en/latest/tuto_A_add_vehicle/
However, both LiDAR and semantic LiDAR sensor are not able to detect my vehicles.
Here I have my ego-vehicle

yet it is unable to detect anything

Could it be that i am missing some steps?
Thanks!

Figured it out following this part here:
https://carla.readthedocs.io/en/latest/tuto_D_generate_colliders/#raycast-colliders


v1.12 backports 2022-07-14

#20438 -- Update gops to v0.3.25 (@tklauser)
#20460 -- docs: fix a Links documentation style guide error (@Kikiodazie)
#20369 -- daemon: Rename host-reachable services to socket LB (@brb)

@brb - lots of complexity test merge conflicts, may want to double check all the
flags look good.

#20499 -- test: Do not start cilium monitor in K8sServicesTest (@brb)
#20491 -- Add metric on number of requests rejected by DNS Proxy semaphore (@rahulkjoshi)
#19434 -- vtep: VTEP integration pod src identity set to WORLD_ID (@vincentmli)
#20501 -- Update Go to 1.18.4 (@tklauser)

@tklauser - this cherry pick made a conflict with #20438 , this is later commit
so I let this one win. LMK if that's correct.

#20249 -- docs(bpf): fix minor grammar errors in struct padding section (@maxbrunet)
#20415 -- Documentation: Improve cilium-cli and hubble cli installation instructions (@chancez)
#20439 -- docs: Add cluster install/prep guide for AKS-to-AKS clustermesh (@dylandreimerink)
#20447 -- docs: Improve kubeproxy replacement and OKD GSG guide. (@tommyp1ckles)
#20458 -- envoy: Support ca.crt Secrets (@jrajahalme)
#20500 -- test: Remove sockops test cases (@brb)
#20512 -- cilium/cmd, test/runtime: convert test loading invalid policy JSON to unit test (@tklauser)
#20526 -- test: remove nightly test leftovers (@tklauser)
#20383 -- pkg/k8s/version: Also set EndpointSlice when forcing version (@joamaki)
#20537 -- fqdn/dnsproxy: fix test build (@tklauser)
#20549 -- Update cilium-iproute2 (@pchaigno)

Once this PR is merged, you can update the PR labels via:
$ for pr in 20438 20460 20369 20499 20491 19434 20501 20249 20415 20439 20447 20458 20500 20512 20526 20383 20537 20549; do contrib/backporting/set-labels.py $pr done 1.12; done

/test-backport-1.12

/test-backport-1.12

ConformanceAKS (ci-aks-1.12)
ConformanceGKE (ci-gke-1.12)
Currently known flakes - disregarding for merge criteria.

/test-backport-1.12

/test-backport-1.12

/ci-aks-1.12

/test-1.22-5.4

All failures looked like a regression. I bisect the commits from this PR here but the PR didn't fail with the same failures. We can safely merge this one.


AMBARI-25252. Disable directory Indexing at /resources (amagyar) (#2936)

clone of #2936

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5152/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5153/
Test FAILed.
Test FAILured.


帮忙

Description
Overview of your issue here.
Your environment

ROS Distro: [Indigo|Jade|Kinetic]
OS Version: e.g. Ubuntu 16.04
Source or Binary build?
If binary, which release version?
If source, which git commit or tag?

Steps to reproduce
Tell us how to reproduce this issue. Attempt to provide a working demo, perhaps using Docker.
Expected behaviour
Tell us what should happen
Backtrace or Console output
Use gist.github.com to copy-paste the console output or segfault backtrace using gdb.

就是说我能帮忙翻译吗

There is no (readable) issue description


[BUG] Can't install native expo project dependencies

Describe the bug
When running npm install in the native expo project, a "unable to resolve dependency tree" error appears, blocking me from installing the dependencies. This also happens when I try to install reassure dependencies in my own project.
To Reproduce
Steps to reproduce the behavior:

Go to examples/native-expo in your terminal
Run npm install
See error

Expected behavior
Dependencies install successfully
Screenshots

Desktop (please complete the following information):

OS: macOS 13.0.1
NPM version 16.13.0

I'll check with NPM, but it definitely should work with yarn. So you might use it as quick workaround.

@mdjastrzebski got it to work with npm with solution you provided in https://github.com/callstack/react-native-testing-library/issues/1409 :)


Bump to 0.15.2101126099-alpha.

/azp run

/azp run

Force merging to restore build.

Force merging to restore build.


Unpin PyQT version for CI builds

Undo #229 once ContinuumIO/anaconda-issues#1068 has been fixed.
Once the bug in conda has been fixed we should stop pinning the version of pyqt that we use in the CI builds.

Fixed by #278.


Readmi

Modifying our bot is fine, but we don't accept changes of our bot/branding directly unfortunately. If you wish to change things such as the name, we'd prefer you to do this for your own fork.


Resolve: Update container errors

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior:
Updating a container in the manager errors with:
Traceback (most recent call last):
  File "C:\Users\tokejepsen\ayon-core\client\ayon_core\tools\sceneinventory\view.py", line 236, in <lambda>
    lambda: self._update_containers(items, version=-1)
  File "C:\Users\tokejepsen\ayon-core\client\ayon_core\tools\sceneinventory\view.py", line 819, in _update_containers
    update_container(item, item_version)
  File "C:\Users\tokejepsen\ayon-core\client\ayon_core\pipeline\load\utils.py", line 517, in update_container
    return Loader().update(container, context)
  File "C:\Users\tokejepsen\ayon-core\client\ayon_core\hosts\resolve\plugins\load\load_clip.py", line 82, in update
    self.set_item_color(timeline_item, version=context["version"])
  File "C:\Users\tokejepsen\ayon-core\client\ayon_core\hosts\resolve\plugins\load\load_clip.py", line 130, in set_item_color
    version["parent"],
KeyError: 'parent'

Expected Behavior:
No response
Version
1.0.0
What platform you are running on?
Windows
Steps To Reproduce:

Load a clip (EXR) into a timeline in Resolve.
Switch version in the Manager.

Are there any labels you wish to add?

[X] I have added the relevant labels to the bug report.

Relevant log output:
No response
Additional context:
No response

Shouldn't parent key always be present on version data?

The issue is here
Those queries filter fields but we want to pass the full context to the Loader.update calls.
Bug was introduced with #130 indeed.

hey @tokejepsen I believe this had been fixed already. Can you try again please?

hey @tokejepsen I believe this had been fixed already. Can you try again please?

Nice, resolved!


Can't have fastscroll

I didn't find any way to have a fastscroll with your API. I like to use https://github.com/FutureMind/recycler-fast-scroll but I can't mix the two libraries due to the fact that SlimAdapter is hidden (and so I can't override it and make it implements SectionTitleProvider.
Having a public constructor instead of a SlimAdapter.create() method would certainly solve that issue.

thanks for feedback..
hiding the constructor is for forcing to use the fluent calls,  but your case makes sense... i will solve the question or maybe you could fork to contribute your help~

I had similar problem and ended up using recyclerView.Adapter wrapper, and delegated methods like this:
`   private final SlimAdapter slimAdapter;
public MyNewAdapter(SlimAdapter slimAdapter) {
    this.slimAdapter = slimAdapter;
}

@Override
public int getItemViewType(int position) {
    return slimAdapter.getItemViewType(position);
}

@Override
public SlimViewHolder onCreateViewHolder(ViewGroup parent, int viewType) {
    return slimAdapter.onCreateViewHolder(parent, viewType);
}

@Override
public void onBindViewHolder(SlimViewHolder holder, int position) {
    slimAdapter.onBindViewHolder(holder, position);
}

@Override
public int getItemCount() {
    return slimAdapter.getItemCount();
}`

Well, that's a smart and certainly working solution, thanks for sharing it.
However I think SlimAdapter would gain to propose a very simple and documented solution. Could be by allowing to override the SlimAdapter class, providing a abstract SlimAdapterWrapper, or finding another solution (right now I don't have better idea). Not sure of what you prefer to officially include into SlimAdapter.

sorry for reply so late..i am a little too busy in my new project recently...
u could override the SlimAdapter class now to merge with other features, any better idea u found please let me know, sorry again

we have same problem how to solve?


Change the base64 variant from the urlsafe to the standard.

LGTM.

Thx!

I'll merge it once the travis build is complete.


Extension causes high cpu load

Issue Type: Performance
Extension Name: LiveServer
Extension Version: 5.5.1
OS Version: Darwin x64 15.6.0
VSCode version: 1.31.1

:warning: Make sure to attach this file from your home-directory: /Users/OronsW/ritwickdey.LiveServer-unresponsive.cpuprofile.txt :warning:
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

Hello. few questions!!,
When you're getting this issue? after load of vscode or after clicking to Go Live ?
Is this happen every-time ? or random ?
Please reply here https://github.com/ritwickdey/vscode-live-server/issues/278
Duplicate of https://github.com/ritwickdey/vscode-live-server/issues/278

[Note: This issue is closed by a javascript code (written by me).
https://gist.github.com/ritwickdey/36682dabe4a992c57e4562c935bfbbdd ]

Thank You.


Added ajayaa's public key

Please test this.

please test this

Build probably failed due to vRouter issue:
ssh: connect to host <IP_ADDRESS> port 22: No route to host
sed: couldn't flush stdout: Broken pipe
ssh: connect to host <IP_ADDRESS> port 22: No route to host
ssh: connect to host <IP_ADDRESS> port 22: No route to host
sed: couldn't flush stdout: Broken pipe

please test this

Ajaya Agrawal reports to Hari Rao in Jio Cloud.

Build failed as Jenkins tenant was out of quota.

Let's try again.

please test this

Builds passed and merging.


can be graph with edges be analysed like it is done by networkx?

let's say we social relations/ communications graph given by edges and nodes
can it be analyzed for example to predict/recommend connections  or to find similar nodes
thanks

You can learn interactions on the graph. There is no visualization in this package but you can use it with networkx. Not sure what your question is.

"You can learn interactions on the graph."
great, may you help find code example how this can be done with your package?


Cannot minify JavaScript file contains a bare Unicode escape identifier

The following JavaScript source code seems odd, but it is completely legal. (See ECMA-262)
const _\u00bare_unicode_escape_identifier = 42;
console.log(_\u00bare_unicode_escape_identifier);

And, such a source code is generated by Scala.js.
When Hugo tries to minify a source containing a bare Unicode escape identifier, it shows the following error:
Start building sites …
hugo v0.89.4+extended darwin/amd64 BuildDate=unknown
Error: Error building site: MINIFY: failed to transform "index.js" (application/javascript): unexpected \u00BAre_unicode_identifier in var statement on line 3 and column 8
    3:   var _\u00BAre_unicode_identifier = 42;
              ^

Noting that the latest  ESBuild supports minifying source codes with a bare Unicode escape identifier, I think this problem is solved if ESBuild is updated.
What version of Hugo are you using (hugo version)?

$ hugo version
hugo v0.89.4+extended darwin/amd64 BuildDate=unknown

Does this issue reproduce with the latest release?
Yes

Just tried minification using esbuild using js.Build function, it works. But it doesnt work if you are using minify or resources.Minify.
minify or resources.Minify minification function is handled by tdewolff/minify.
If you want to use esbuild to handle minification, you need to set it on js.Build options
{{- $jsOpts := dict "minify" true -}}
{{- $js := resources.Get "js/script.js" | js.Build $jsOpts }}
<script src="{{ $js.Permalink }}"></script>

Hugo Version:
hugo v0.90.0-DEV-75A823A3+extended linux/amd64 BuildDate=2021-11-26T11:59:58+0700

Thanks for clarification.
I will use esbuild to minify, and will open a new Pull Request to tdewolff/minify


Double check the executable name doesn't change for app bundle

Prevents issues with Gatekeeper bug, see https://github.com/electron-userland/electron-packager/issues/323

@cjb @chrisnojima

:thumbsup:


Rebalance tests to prevent travis timeouts

This is a short term fix to address #612.

It moves a couple of tests to the integration batch 2, that seems to be the furthest from timeout.
It also adds a flag to the pytest runs on travis to output the slowest tests in the unit and integration tests, so that we can remove/refactor them periodically.

Hopefully, PyTorch 0.3 should solve a lot of these pain points, and a slightly longer term plan is to run the integration tests as a cron job instead.

@neerajprad do you have a printout of runtimes? i'd feel pretty comfortable removing a few tests right now, even we'll be rethinking test coverage down the line. e.g.
test_elbo_reparameterized_N_is_17
test_elbo_nonreparameterized_N_is_7
test_elbo_nonreparameterized_three_layers_model_permuted

@martinjankowiak - Here are the tests in the different batches.  :)


AMD A6-3400M))))

AMD A6-3400M
Epoch 1 - accuracy: 39.43% (3943/10000) - time: 00:57:37.07 )))

@roma323 You need to reduce batch size, maybe increase number of epoch and adjust learning rate.


Configurable EL gas limit

This PR allows configuration of gas limit in values.env
Only one note: I'm not sure about genesis_aura_posdao.py -- how should it be updated?
Thanks!

Is there a specific reason you'd like to have configurable gas limits?
We deprecated support for PoW/PoS support with this tool. The idea is that all future testnets would start at a post-merge genesis state, this would avoid a lot of complexity related to the merge transition. An older version of the tool can be used for spinning up aura networks of course.

Closing the PR, we can re-open it if needed. Thanks for the PR!


Avoid unnecessary reload after HMR WebSocket connection lost

Clear and concise description of the problem
Currently Vite reloads the page after a successful ping after connection lost.
In a hybrid app, once the app launches another app, the connection lost. When the app switches back, the app reloads. To properly debug routines involve switching to another app, we have to either use production build or comment out location.reload() in vite/dist/client/client.mjs.
Suggested solution
Reconnect WebSocket to check HMR status instead of reload unconditionally.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[x] Read the docs.
[x] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I have same problem #6089

I want to flag an important reason I'd like to be able to deactivate the websocket.
An active websocket blocks the bfcache on the browser. So the bfcaching caching behavior locally is different than the caching behavior in prod, where there is no websocket, at least for me. I therefore couldn't reproduce a certain cache-related bug locally until I realized the Vite websocket was affecting it.
Just leaving this comment here since I didn't see any reference to this caching issue in any of the websocket-related Vite issues, and I'm sure someone will have this problem someday.

@niksy
How this happens is:
When the web socket connection was disconnected, Vite's HMR client starts to ping to http://yourserver/websocket-path.
https://github.com/vitejs/vite/blob/29abeeab9cc147c6d3383c672ded68311304bbaf/packages/vite/src/client/client.ts#L311-L333
When the Vite server starts, Vite will respond to that ping request.
Then, Vite's HMR client reload the page.
https://github.com/vitejs/vite/blob/29abeeab9cc147c6d3383c672ded68311304bbaf/packages/vite/src/client/client.ts#L103-L105
But this has some edge cases. For example, when WebSocket server starts after the HTTP Server (can happen in middleware mode).
Where we need to change is:

Change the ping to use WebSocket instead of HTTP: https://github.com/vitejs/vite/blob/29abeeab9cc147c6d3383c672ded68311304bbaf/packages/vite/src/client/client.ts#L311
Handle that WebSocket connection: https://github.com/vitejs/vite/blob/29abeeab9cc147c6d3383c672ded68311304bbaf/packages/vite/src/node/server/ws.ts#L80

I guess we need to use a different protocol(sec-websocket-protocol) to differentiate the normal connection and the ping connection.

@sapphi-red

Change the ping to use WebSocket instead of HTTP:

Does this mean we need to create our own WebSocket server and reference it in Vite server.hmr.server property?

Could somebody give me any suggestions on how I can prevent the reload?
I use the latest vite 4.5.0 with SSR, createViteServer in middlewareMode and Express.js.
Most of my config is based on the very nice repo vite-typescript-ssr-react.
Honestly, I have not had any issues until we stuck with a security check with one of the 3rd party services. They use Burp Suite to intercept all of the network requests. The app running I believe reverse proxy.
The first thing I noticed is the connection via the app probably because the proxy is always insecure.

This is why, I think, the WebSocket connection fails, and in an attempt to reestablish the connection Vite reloads the web app.
Also to be honest I don't really understand why we need the HMR WebSocket on prod.

@IvanKalinin Vite isn't intended to be run in prod and you shouldn't be doing that.
https://vitejs.dev/guide/ssr.html#:~:text=Then%2C in server,a working setup.

Would love to see this be configurable.
For my situation (a very simple vite server setup w/ some proxies for socketio and our api, nothing else), this diff allowed me to retain HMR functionality but not reload the page:
diff --git a/dist/client/client.mjs b/dist/client/client.mjs
index e944ed731f936d5a35fe8368ce55c0518ade537e..ba56411cce8960a5dd0c47bf9b3bb13a8b8498f6 100644
--- a/dist/client/client.mjs
+++ b/dist/client/client.mjs
@@ -483,7 +483,7 @@ function setupWebSocket(protocol, hostAndPath, onCloseWithoutOpen) {
         notifyListeners('vite:ws:disconnect', { webSocket: socket });
         console.log(`[vite] server connection lost. polling for restart...`);
         await waitForSuccessfulPing(protocol, hostAndPath);
-        location.reload();
+        setupWebSocket(protocol, hostAndPath, onCloseWithoutOpen)
     });
     return socket;
 }

It's not clear if this would break other things but it seems to work just fine for me.

any update on this?

+1
so many issues and pull requests have been created, but they are being closed and rejected, and this error is still being repeated. Why?


Updated logic to keep any previously set custom reply-to email address

fixes PROD-102

after the dmarc changes, replies from members should keep going to the same custom reply-to email address

We'll also need to set sender_email to null when changing sender_reply_to when sender_email is not supported for sending, otherwise we won't be able to clear the replyTo address.
Ideally that check should be auto-correcting every time, so I would try to avoid using feature flag checks / config checks, and when changing sender_reply_to or sender_email actually check if EmailAddressService.getAddress({from: sender_email}) stays the same as sender_email, otherwise set it to null (because that means we cannot send from it).


Wasm VM failed Failed to load Wasm bytecode/Wasm VM failed Failed to load Wasm code

Bug Description
I installed istio and  execute integration test in vmvare virtualmachine , and it works fine, but when execute integration test in kvm virtualmachine(created in openstack), i failed.
failed case path:  telemetry_stats_prometheus_wasm
The eastwestgateway pod failed to start. Looking at the logs of eastwestgateway pod, found some errors:

2022-04-07T05:29:24.754563Z     info    JWT policy is third-party-jwt
2022-04-07T05:29:24.762879Z     info    CA Endpoint istiod.istio-system.svc:15012, provider Citadel
2022-04-07T05:29:24.762953Z     info    Using CA istiod.istio-system.svc:15012 cert with certs: var/run/secrets/istio/root-cert.pem
2022-04-07T05:29:24.763175Z     info    citadelclient   Citadel client using custom root cert: istiod.istio-system.svc:15012
2022-04-07T05:29:24.765153Z     info    Opening status port 15020
2022-04-07T05:29:24.784755Z     info    ads     All caches have been synced up in 36.996382ms, marking server ready
2022-04-07T05:29:24.785059Z     info    sds     SDS server for workload certificates started, listening on "etc/istio/proxy/SDS"
2022-04-07T05:29:24.785293Z     info    xdsproxy        Initializing with upstream address "istiod.istio-system.svc:15012" and cluster "Kubernetes"
2022-04-07T05:29:24.785323Z     info    sds     Starting SDS grpc server
2022-04-07T05:29:24.785800Z     info    Pilot SAN: [istiod.istio-system.svc]
2022-04-07T05:29:24.785819Z     info    starting Http service at <IP_ADDRESS>:15004
2022-04-07T05:29:24.789986Z     info    Pilot SAN: [istiod.istio-system.svc]
2022-04-07T05:29:24.793596Z     info    Starting proxy agent
2022-04-07T05:29:24.793636Z     info    Epoch 0 starting
2022-04-07T05:29:24.793667Z     info    Envoy command: [-c etc/istio/proxy/envoy-rev0.json --restart-epoch 0 --drain-time-s 45 --drain-strategy immediate --parent-shutdown-time-s 60 --local-address-ip-version v4 --file-flush-interval-msec 1000 --disable-hot-restart --log-format %Y-%m-%dT%T.%fZ  %l      envoy %n        %v -l warning --component-log-level misc:error]
2022-04-07T05:29:24.927016Z     info    xdsproxy        connected to upstream XDS server: istiod.istio-system.svc:15012
2022-04-07T05:29:24.955751Z     info    ads     ADS: new connection for node:istio-eastwestgateway-56bd47f7b7-nctt6.istio-system-1
2022-04-07T05:29:24.966251Z     info    ads     ADS: new connection for node:istio-eastwestgateway-56bd47f7b7-nctt6.istio-system-2
2022-04-07T05:29:25.049624Z     info    cache   generated new workload certificate      latency=264.16068ms ttl=23h59m59.950390925s
2022-04-07T05:29:25.049655Z     info    cache   Root cert has changed, start rotating root cert
2022-04-07T05:29:25.049676Z     info    ads     XDS: Incremental Pushing:0 ConnectedEndpoints:2 Version:
2022-04-07T05:29:25.049745Z     info    cache   returned workload trust anchor from cache       ttl=23h59m59.950258676s
2022-04-07T05:29:25.049766Z     info    cache   returned workload trust anchor from cache       ttl=23h59m59.95023602s
2022-04-07T05:29:25.051004Z     info    ads     SDS: PUSH request for node:istio-eastwestgateway-56bd47f7b7-nctt6.istio-system resources:1 size:1.1kB resource:ROOTCA
2022-04-07T05:29:25.051150Z     info    cache   returned workload certificate from cache        ttl=23h59m59.948860345s
2022-04-07T05:29:25.051176Z     info    cache   returned workload trust anchor from cache       ttl=23h59m59.948828986s
2022-04-07T05:29:25.051214Z     info    ads     SDS: PUSH for node:istio-eastwestgateway-56bd47f7b7-nctt6.istio-system resources:1 size:1.1kB resource:ROOTCA
2022-04-07T05:29:25.051296Z     info    ads     SDS: PUSH request for node:istio-eastwestgateway-56bd47f7b7-nctt6.istio-system resources:1 size:4.0kB resource:default
2022-04-07T05:29:25.148602Z     error   envoy wasm      Wasm VM failed Failed to load Wasm bytecode
2022-04-07T05:29:25.148671Z     error   envoy wasm      Wasm VM failed Failed to load Wasm code
2022-04-07T05:29:25.150156Z     critical        envoy wasm      Plugin configured to fail closed failed to load
2022-04-07T05:29:25.185539Z     error   envoy wasm      Wasm VM failed Failed to load Wasm bytecode
2022-04-07T05:29:25.185587Z     error   envoy wasm      Wasm VM failed Failed to load Wasm code
2022-04-07T05:29:25.186706Z     critical        envoy wasm      Plugin configured to fail closed failed to load
2022-04-07T05:29:25.190461Z     warning envoy config    gRPC config for type.googleapis.com/envoy.config.listener.v3.Listener rejected: Error adding/updating listener(s) <IP_ADDRESS>_15012: Unable to create Wasm network filter
<IP_ADDRESS>_15017: Unable to create Wasm network filter
2022-04-07T05:29:26.698892Z     warn    Envoy proxy is NOT ready: config received from XDS server, but was rejected: cds updates: 1 successful, 0 rejected; lds updates: 0 successful, 1 rejected
2022-04-07T05:29:28.697642Z     warn    Envoy proxy is NOT ready: config received from XDS server, but was rejected: cds updates: 1 successful, 0 rejected; lds updates: 0 successful, 1 rejected

Version
[root@nested-istio-node1 istio]#  istioctl version
client version: 1.12.0
control plane version: 1.12-alpha.544d7699245d2a1b127adc08f657e11e2b6594c5
data plane version: 1.12-alpha.544d7699245d2a1b127adc08f657e11e2b6594c5 (3 proxies)

[root@nested-istio-node1 istio]# kubectl version
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.12", GitCommit:"1795ce516f4c5d6456672d5dee34826971d8d617", GitTreeState:"clean", BuildDate:"2022-01-04T05:41:00Z", GoVersion:"go1.15.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.12", GitCommit:"d99e1b8b74e3938f9d50927cc9cf658b23a790ee", GitTreeState:"clean", BuildDate:"2021-12-01T03:10:24Z", GoVersion:"go1.15.15", Compiler:"gc", Platform:"linux/amd64"}

[root@node0 ~]# rpm -qa |grep libvirt
libvirt-lock-sanlock-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-network-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-interface-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-storage-gluster-4.5.0-36.48.el7.3.x86_64
libvirt-libs-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-config-nwfilter-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-storage-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-lxc-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-nodedev-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-storage-iscsi-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-storage-mpath-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-config-network-4.5.0-36.48.el7.3.x86_64
libvirt-client-4.5.0-36.48.el7.3.x86_64
libvirt-bash-completion-4.5.0-36.48.el7.3.x86_64
libvirt-python-4.5.0-1.el7.x86_64
libvirt-daemon-driver-storage-core-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-qemu-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-storage-scsi-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-storage-rbd-4.5.0-36.48.el7.3.x86_64
libvirt-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-nwfilter-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-storage-disk-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-kvm-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-secret-4.5.0-36.48.el7.3.x86_64
libvirt-daemon-driver-storage-logical-4.5.0-36.48.el7.3.x86_64
[root@node0 ~]# rpm -qa |grep qemu
qemu-kvm-block-ssh-4.2.0-29.20.el7.5.x86_64
publish-qemu-event-1.0.2-0.el7.noarch
qemu-img-4.2.0-29.20.el7.5.x86_64
qemu-kvm-core-4.2.0-29.20.el7.5.x86_64
qemu-kvm-block-iscsi-4.2.0-29.20.el7.5.x86_64
libvirt-daemon-driver-qemu-4.5.0-36.48.el7.3.x86_64
qemu-kvm-block-rbd-4.2.0-29.20.el7.5.x86_64
qemu-kvm-4.2.0-29.20.el7.5.x86_64
ipxe-roms-qemu-20170123-1.git4e85b27.el7_4.1.noarch
qemu-kvm-common-4.2.0-29.20.el7.5.x86_64
qemu-kvm-block-curl-4.2.0-29.20.el7.5.x86_64

Additional Information
No response

@bianpengyuan Hi，can you give me some advices? Thank you!

I finally found out that the "adm" cpu ISA was missing in the qemu virtual machine.

@smallcoderhujin Did you get the answer for this issue?

@ingwonsong  Yes, add "abm" cpu isa in nova conf fix this issue


Blue laser trace remains on screen

Even after removing all files/elements/operations, the previous laser trace remains on screen.

#58

Yeah, I'm not sure what to do with that laser trace things. Pressing New will clear it in the next version. But, the overall utility is questionable and I'm not really sure what to do instead or whether to just clear that information a lot. It's just like a thousand lines between various position updates.
I'm not really sure what I should want done there or should do instead.

Changing the selection will now clear that data. There's also a control to perform this action which could be bound to a keypress