fix: filter cached images with host schedtag

这个 PR 实现什么功能/修复什么问题:
改进：通过host_schedtag过滤缓存镜像

是否需要 backport 到之前的 release 分支:

release/3.4

/cc @zexi @yousong @ioito @tb365
/area region

Codecov Report

Merging #8205 into master will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #8205      +/-   ##
=========================================
- Coverage    6.22%   6.17%   -0.05%
=========================================
  Files         759     150     -609
  Lines      117177   20971   -96206
=========================================
- Hits         7289    1296    -5993
+ Misses     109229   19526   -89703
+ Partials      659     149     -510

Flag
Coverage Δ

#aFlag
6.17% <ø> (-0.05%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/multicloud/esxi/guestos.go

pkg/util/samlutils/instance.go

pkg/compute/models/globalvpcs.go

pkg/compute/models/cloudregionresource.go

pkg/util/sysutils/kvm.go

pkg/compute/models/dns_zonevpc.go

pkg/compute/guestdrivers/esxi.go

pkg/compute/models/netinterfaces.go

pkg/compute/models/initdb.go

pkg/multicloud/aws/imageowners.go

... and 598 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b11e472...1c0c66f. Read the comment docs.

/lgtm
/approve


octant capitalization on Mac

For some reason Octant is capitalized with small o in main window caption bar on Mac, see screenshot:

Although some apps like zoom do that as well, I think we should probably fix that.

See if setting a title directly helps: https://www.electronjs.org/docs/api/tray#traysettitletitle-options-macos

I think this is already solved on https://github.com/vmware-tanzu/octant/commit/c9738199daa38d0d4e7277b6b689f54e957549ea


Any chance of JSX support in the new version

I get errors when parsing es6 files with JSX. I desperately want to use sweet.js  with my react project to cut down on boilerplate (the bane of react). I believe this was supported via readtables in a previous release? Any help would be appreciated.

JSX can be supported a soon as we get readtables implemented again. That's being tracked with #535 so closing this issue.


[change the main dataset name]:

Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
the main dataset is named "complex_backscatter" and that seems too long and not fully represnetative of the content. The developer team agrees to change to "slc"
Describe the feature request
rename "complex_backscatter" to "slc" in HDF5

Close this issue as it has been implemented in #74 by @LiangJYu.


@cInclude("sqlite3ext.h") generates invalid Zig

Given a test.zig of
const c = @cImport({
    @cInclude("sqlite3ext.h");
});

pub fn main() void {
    c.sqlite3_libversion();
}

this error is produced on master:
zig run test.zig
/home/bb010g/Documents/test.zig:1:11: error: compiler bug: @cImport generated invalid zig code
const c = @cImport({
          ^
?.c:1:1: note: redefinition of 'sqlite3_module'
TODO: remember C source location to display here
^
?.c:1:1: note: previous definition is here
TODO: remember C source location to display here
^
/home/bb010g/Documents/test.zig:1:11: error: compiler bug: @cImport generated invalid zig code
const c = @cImport({
          ^
?.c:1:1: note: redefinition of 'sqlite3_module'
TODO: remember C source location to display here
^
?.c:1:1: note: previous definition is here
TODO: remember C source location to display here
^
/home/bb010g/Documents/test.zig:1:11: error: compiler bug: @cImport generated invalid zig code
const c = @cImport({
          ^
?.c:1:1: note: redefinition of 'sqlite3_vfs'
TODO: remember C source location to display here
^
?.c:1:1: note: previous definition is here
TODO: remember C source location to display here
^
/home/bb010g/Documents/test.zig:1:11: error: compiler bug: @cImport generated invalid zig code
const c = @cImport({
          ^
?.c:1:1: note: redefinition of 'sqlite3_vfs'
TODO: remember C source location to display here
^
?.c:1:1: note: previous definition is here
TODO: remember C source location to display here
^

Thanks for the report! Here's a workaround if you want it:
Use the command line, zig translate-c sqlite3ext.h to print to stdout the translation of the C code. Then manually fix up the invalid zig.

I'm curious to see what invalid C this generated.

The invalid zig generated was:
pub const sqlite3_module = struct_sqlite3_module;
pub const sqlite3_module = struct_sqlite3_module;

The rest looks good. I'm pretty sure this is some simple thing where translate-c forgot to check a  hash table before emitting a macro, or something like that. Will look into it more later.

Past that, it seems to run into a variant of #624/#679.

I'm working on a small test case. I have it down to 355 lines: https://clbin.com/GMcTt

Here's a reproducer:
typedef struct Bar Bar;
typedef struct Foo Foo;

struct Foo {
    Foo *a;
};

struct Bar {
    Foo *a;
};

translates to
pub const Foo = struct_Foo;
pub const struct_Foo = extern struct {
    a: ?&Foo,
};
pub const Foo = struct_Foo;
pub const struct_Bar = extern struct {
    a: ?&Foo,
};


Questions and proposals about Captive Portal

Where can i set a static redirect URL in the Captive Portal so that the client, after logging in, will be redirected always to for example info.client.com? Is ist possible to introduce a field in Captive Portal to set this?
Thank you for your great work

@gertfriend please use our forum for discussions and questions, it's quite impractical for us to handle multiple questions per issue.
To redirect to a standard page in CP, just download the template and change the redirect here: https://github.com/opnsense/core/blob/master/src/opnsense/scripts/OPNsense/CaptivePortal/htdocs_default/index.html#L89

Thank you for the answer and sorry for the multpost, i will use the forum for the other questions and leave this.


TypeError: "Cannot read properties of undefined (reading '0')" in command "serverinfo"

Reported by .̔̏𝗠𝗲𝗽𝗵𝗶𝘀𝘁𝗼#5558<PHONE_NUMBER>25055775) with bot<PHONE_NUMBER>02710047
TypeError: Cannot read properties of undefined (reading '0')
at ChatInputCommandInteraction.run (/home/container/Commands/Information/serverinfo.js:19:92)
at ChatInputCommandInteraction.interactionCreate (/home/container/Events/interactionCreate.js:79:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

fixed with eb36991


tape -r babel-register equivalent for gulp-tape

I am writing react component test. If I run it manualy with command:
tape -r babel-register tests/counter.component.test.js
It works just fine, but I have hard time getting it to work with gulp. Here is my task:
gulp.task('tape', () => {
  return gulp
  .src(paths.tests)
  .pipe(tape({
    reporter: tapSpec()
  }));
});

As you can see, I'm not handling the actual components files here, so adding pipe with gulp-babel wont help me. What did I miss? Can I pass somewhere require: 'babel-register as an option?

Anyone has an idea on how to do this?

This should be solved as of 0.0.10; see https://github.com/yuanqing/gulp-tape/tree/7754fb0e2956feac10352c4d3d10fa305d2c96f1#tapeoptions


[DS-2604] fix jspui retrieve CC rdf

based on https://github.com/DSpace/DSpace/pull/1506

replaced by #1522


get-nodes reports the wrong port for the controller

This isn't a problem other than causing confusion.  The controller listens on 2050 (legacy) and 2049 (websockets), but is reported as listening on 2151.  Looking at the data structure it looks like zeek-client is just outputting the result handed back to it.
zeek@zeek-test-cluster2:~$ zeek-client --controller zeek-test-cluster1.es.net:2149 get-nodes
{
  "errors": [],
  "results": {
    "agent-zeek-test-cluster1.es.net": {
      "agent-zeek-test-cluster1.es.net": {
        "cluster_role": null,
        "mgmt_role": "AGENT",
        "pid": 324435,
        "state": "RUNNING"
      },
      "controller-zeek-test-cluster1.es.net": {
        "cluster_role": null,
        "mgmt_role": "CONTROLLER",
        "pid": 324434,
        "port": 2151,
        "state": "RUNNING"
      }
    }
  }
}

This looks to be the data sent back to the client from the controller itself.

Looking at this again, I think it's just confusing terminology maybe?  There IS something listening on port 2151, but I think what's happening is that zeek-client is talking to the agent process of the controller node, and that's on 2149.  But then I still don't know what redef'ing Management::Controller::listen_address_websocket does because even if I set that to an IPv6 address, the listener is here:
tcp        0      0 <IP_ADDRESS>:2151            <IP_ADDRESS>:*               LISTEN


Find templates and library sources

[x] find template
[x] try map libraries
[x] define project structure

Template integrated and map box chosen


issue6595/incorrect anchor for constructor with inferred namespace

Description
When a constructor is called without an explicit namespace, relying on the namespace inference, the TypeReferenceAnchor it registers can not be resolved.
closes #6595
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing #6792.


Move dispatcher failed dispatch method from ERROR to WARN log severity

Description
We are running a cluster of validators and when users are hitting the RPC endpoints we get a huge amount of ERROR logs for user-initiated RPC requests. Would like to treat these as WARN instead.
If we could move to DEBUG, would also prefer it over WARN.
Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[ ] Hotfix (change that solves an urgent issue, and requires immediate attention)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Checklist

[ ] I have assigned this PR to myself
[ ] I have added at least 1 reviewer
[ ] I have added the relevant labels
[ ] I have updated the official documentation
[ ] I have added sufficient documentation in code

Testing

[ ] I have tested this code with the official test suite
[ ] I have tested this code manually

Btw can you provide a bit more context? Are you guys running a public chain and you are facing incorrect input being sent by end-users to JSON RPC endpoints?

We have 2 chains ATM, both are being used by internal dev teams. In future, we will have 3 chains, 2 of them publicly available.
Here are examples of ERRORs we get from user RPC:
message:"2023-05-18T07:28:37.670Z [ERROR] polygon.server.dispatcher: failed to dispatch: method=eth_call err=\"execution was reverted\""

message:"2023-05-18T03:44:31.392Z [ERROR] polygon.server.dispatcher: failed to dispatch: method=eth_estimateGas err=\"not enough funds to cover gas costs\""

message:"2023-05-18T06:23:38.646Z [ERROR] polygon.server.dispatcher: failed to dispatch: method=eth_sendRawTransaction err=\"cannot extract signature\""

Each of these can happen many times, depending the (user) client's flow.
I understand that the system can perform RPC actions but I think we can ERROR on those lower in the stack than the dispatcher

I understand that the system can perform RPC actions but I think we can ERROR on those lower in the stack than the dispatcher

We could, although it would require quite of changes (for each endpoint and each function, we would need to add logging there). However, it still wouldn't resolve the original problem and we would still be spammed with a lot of errors, and that problem wouldn't vanish. Because of that, I still find the dispatcher a convenient place because only there we are logging all possible errors.


Containers form all stacks shown in the Stack details

Bug description
When I open some stack's details page, there are all containers from all stacks shown in the containers section.
Expected behavior
I would expect to see only containers in the current stack on the Stack details page.
Steps to reproduce the issue:

Click on Stacks in the left menu
Select some stack
Scroll down to Containers
See all containers from all stacks

Technical details:

Portainer version: 1.23.1
Docker version (managed by Portainer): 19.03.5, build 633a0ea
Platform (windows/linux): linux
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): docker run -p 9000:9000 -v /var/run/docker.sock:/var/run/docker.sock portainer/portainer
Browser: Mozilla Firefox

Additional context
Using LOCAL management

It was caused by bad nginx setting, which ommited query string (part after ?)


Windows compilation warning fixes

as discussed in #40

thanks!

Any reason why that was closed without merging?

Any reason why that was closed without merging?

No good reason. I was too fast. It was merged in https://github.com/pthom/hello_imgui/commit/00b764d244634edb35b5f7ee714458bdb95d2146


Add shortcuts for New Script and New Text File in the script editor

Follow-up to https://github.com/godotengine/godot/pull/48574.
These default to Ctrl + Alt + N and Ctrl + Alt + Shift + N respectively.

Not sure if it's a good idea to add more Alt hotkeys based on https://github.com/godotengine/godot/pull/56695#issuecomment-1010029995 (but maybe there's no conflict in those contexts).

Not sure if it's a good idea to add more Alt hotkeys based on #56695 (comment) (but maybe there's no conflict in those contexts).

Ideally, I'd use Ctrl + N and Ctrl + Shift + N if the script editor is currently focused, but these shortcuts are already used to create new scenes.

I amended this PR to use Ctrl + N and Ctrl + Shift + N. After testing this on master, it seems it works fine as long as the script editor is currently focused.

Thanks!