Aux window: Unable to switch to first editor group from new window

Type: Bug
First of all, thank you for adding floating editor windows! Super useful feature that has already improved my productivity using VS code.
I'm experiencing a weird issue where I am unable to navigate to the first editor group (located in my original window) from a newly opened window. I am able to navigate to any other editor group, but just not the first one.
Steps to repro:

Open vs code window with two editor groups (this is the "original window")
Open new vscode window
From the new window, press ctrl + 1 (workbench.action.focusFirstEditorGroup) to try to go to the first editor group in the original window
Observe that nothing happens (expected to change focus to first editor group in the original window)
From the new window, press ctrl + 2 (workbench.action.focusSecondEditorGroup) and observe that you can change focus to the second editor group as expected

Current workaround if I want to change focus to the first editor group from the new window is I do ctrl + 2 to go to the second editor group, and then I can press ctrl + 1 to focus on the first editor group. If I'm in the original window I have no issue switching between the first and any other editor group in that window
VS Code version: Code - Insiders 1.85.0-insider (54b8f6a80aaad7489b75e9293b8d7a1700bed815, 2023-11-17T10:49:40.914Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Remote OS version: Linux x64 5.15.0-1026-aws
Extensions (13)

Extension
Author (truncated)
Version

remote-containers
ms-
0.324.0

remote-ssh
ms-
0.107.0

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.81.8

vscode-remote-extensionpack
ms-
0.24.0

remote-explorer
ms-
0.4.1

remote-server
ms-
1.5.0

vim
vsc
1.27.0

copilot
Git
1.137.556

copilot-chat
Git
0.11.2023111701

autopep8
ms-
2023.9.13201008

python
ms-
2023.20.0

vscode-pylance
ms-
2023.11.10

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
vscod805:30301674
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30404738
py29gd2263:30784851
vscaac:30438845
vsclangdf:30492506
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30618038
2i9eh265:30646982
showlangstatbar:30737417
pythonfmttext:30716741
fixshowwlkth:30771523
showindicator:30805243
pythongtdpath:30726887
i26e3531:30792625
welcomedialog:30812478
pythonnosmt12:30779711
pythonidxpt:30768918
pythonnoceb:30776497
synctok:30869157
dsvsc013:30777762
dsvsc014:30777825
pythonmhint1:30859868
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30871582
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
aa_t_chat:30882232

Thanks, good catch. Fixing this case is relatively easy, but there are other navigational commands across editor groups that will need special care for when multiple windows are opened: https://github.com/microsoft/vscode/issues/198651


[CT-1046] [Feature] Allow Overrides on Metrics

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
As seen in this documentation, the source resource supports an overrides functionality where the definition can be overridden. This is helpful in package development as it allows customers to override sources that don't perfectly match what their reality looks like.
This functionality should also exist for metrics so that packages which have metrics defined can be overwritten if the definition that the user wants doesn't match that of the package developer.
Describe alternatives you've considered

Not supporting this functionality.
Focusing on enabling/disabling metrics and telling users to disable metrics that don't match their definition and then create new ones.

Who will this benefit?
Anyone using packages that contain metric definitions.
Are you interested in contributing this feature?
Yes
Anything else?
I believe this can be closely tied to #5422

@callum-mcdata Thanks for opening! I'm not conceptually opposed to this. I agree that it will be valuable for packages to define metrics, and users may want to override one or few specific fields.
I know Joe had opened #4157 a few months ago, talking about overrides for models, and I still think it's a reasonable idea. My answer now is the same as my answer then:

The way we've implemented overrides is quite complex under the hood, especially for partial parsing.

@gshank Does this still sound right to you? My sense was that overrides as a pattern introduces a lot of technical complexity behind the scenes.

In the spirit of better support for multi-project namespacing (now its own discussion: https://github.com/dbt-labs/dbt-core/discussions/5244), I've also imagined calling this package_name instead of overrides. The idea is, if you're defining properties for a metric in my_sweet_project like:
version: 2
metrics:
  - name: some_metric
    package_name: cool_installed_package
    description: My slightly different description, with everything else the same

That's equivalent to "overriding" the definition of some_metric from the cool_installed_package package. Only the root project would be able to do this sort of overriding / redefining of objects defined in other packages.

In the meantime, I do see https://github.com/dbt-labs/dbt-core/issues/5422 as another way to get at this same outcome, using a pattern that's both better understood and more widely used. You'd need to disable the some_metric definition coming from the package, and re-enable it yourself in your own project (including all its properties). Less ergonomic, but still possible.

Has there been any more thought around this? I'm interested in the ability to override models, metrics, columns, etc. Basically, I want to create a master project template that has general docs, models, metrics, etc., but each specific project will likely override various parts. I see that the semantic label was recently applied, and I think this concept would be very powerful for creating re-usable master projects that limit redundancy.


invalid ELF header

/home/container/node_modules/bindings/bindings.js:121
        throw e;
        ^
Error: /home/container/node_modules/better-sqlite3/build/Release/better_sqlite3.node: invalid ELF header
    at Object.Module._extensions..node (node:internal/modules/cjs/loader:1179:18)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:999:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at bindings (/home/container/node_modules/bindings/bindings.js:112:48)
    at new Database (/home/container/node_modules/better-sqlite3/lib/database.js:48:64)
    at Database (/home/container/node_modules/better-sqlite3/lib/database.js:11:10)
    at new SqliteDriver (/home/container/node_modules/quick.db/out/drivers/SqliteDriver.js:8:25)
    at new QuickDB (/home/container/node_modules/quick.db/out/index.js:17:28) {
  code: 'ERR_DLOPEN_FAILED'
}
Node.js v17.3.0

I have this error on the hosting

This usually happens if you are using a different architecture (arm, x86) to host the project. To get around this, delete the node_modules folder and run npm i. This will allow you to install all the needed modules in the package.json folder.
This is unlikely a major issue so once you do solve this problem, please close it.

As @pendragons-code said. This is mostly likely the issue.
I wanted to add that node_modules should never be transfered or downloaded to an other machine as It is not recommended to do.
It will also make sure this issue doesn't happen again since you will have to reinstall the dependencies on the target system which will compile the bindings correctly for the current architecture

As @pendragons-code said. This is mostly likely the issue.
I wanted to add that node_modules should never be transfered or downloaded to an other machine as It is not recommended to do.
It will also make sure this issue doesn't happen again since you will have to reinstall the dependencies on the target system which will compile the bindings correctly for the current architecture

/home/container/node_modules/bindings/bindings.js:135
  throw err;
  ^
Error: Could not locate the bindings file. Tried:
 → /home/container/node_modules/better-sqlite3/build/better_sqlite3.node
 → /home/container/node_modules/better-sqlite3/build/Debug/better_sqlite3.node
 → /home/container/node_modules/better-sqlite3/build/Release/better_sqlite3.node
 → /home/container/node_modules/better-sqlite3/out/Debug/better_sqlite3.node
 → /home/container/node_modules/better-sqlite3/Debug/better_sqlite3.node
 → /home/container/node_modules/better-sqlite3/out/Release/better_sqlite3.node
 → /home/container/node_modules/better-sqlite3/Release/better_sqlite3.node
 → /home/container/node_modules/better-sqlite3/build/default/better_sqlite3.node
 → /home/container/node_modules/better-sqlite3/compiled/17.3.0/linux/x64/better_sqlite3.node
 → /home/container/node_modules/better-sqlite3/addon-build/release/install-root/better_sqlite3.node
 → /home/container/node_modules/better-sqlite3/addon-build/debug/install-root/better_sqlite3.node
 → /home/container/node_modules/better-sqlite3/addon-build/default/install-root/better_sqlite3.node
 → /home/container/node_modules/better-sqlite3/lib/binding/node-v102-linux-x64/better_sqlite3.node
    at bindings (/home/container/node_modules/bindings/bindings.js:126:9)
    at new Database (/home/container/node_modules/better-sqlite3/lib/database.js:48:64)
    at Database (/home/container/node_modules/better-sqlite3/lib/database.js:11:10)
    at new SqliteDriver (/home/container/node_modules/quick.db/out/drivers/SqliteDriver.js:8:25)
    at new QuickDB (/home/container/node_modules/quick.db/out/index.js:17:28)
    at new Bot (/home/container/structures/client.js:26:13)
    at Object.<anonymous> (/home/container/index.js:3:16)
    at Module._compile (node:internal/modules/cjs/loader:1097:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1149:10)
    at Module.load (node:internal/modules/cjs/loader:975:32) {
  tries: [
    '/home/container/node_modules/better-sqlite3/build/better_sqlite3.node',
    '/home/container/node_modules/better-sqlite3/build/Debug/better_sqlite3.node',
    '/home/container/node_modules/better-sqlite3/build/Release/better_sqlite3.node',
    '/home/container/node_modules/better-sqlite3/out/Debug/better_sqlite3.node',
    '/home/container/node_modules/better-sqlite3/Debug/better_sqlite3.node',
    '/home/container/node_modules/better-sqlite3/out/Release/better_sqlite3.node',
    '/home/container/node_modules/better-sqlite3/Release/better_sqlite3.node',
    '/home/container/node_modules/better-sqlite3/build/default/better_sqlite3.node',
    '/home/container/node_modules/better-sqlite3/compiled/17.3.0/linux/x64/better_sqlite3.node',
    '/home/container/node_modules/better-sqlite3/addon-build/release/install-root/better_sqlite3.node',
    '/home/container/node_modules/better-sqlite3/addon-build/debug/install-root/better_sqlite3.node',
    '/home/container/node_modules/better-sqlite3/addon-build/default/install-root/better_sqlite3.node',
    '/home/container/node_modules/better-sqlite3/lib/binding/node-v102-linux-x64/better_sqlite3.node'
  ]
}
Node.js v17.3.0

If I don't transfer files from my PC I will get this error

Well I solved this problem by using the correct version on github and compiling the package manually
link


Shape gets highlighted if hovered on loosing focus

🐛 Bug Report
When a Shape is hovered with the mouse, and the napari application looses focus, the Shape will be highlighted. This also emits a highlight event.
💡 Steps to Reproduce
Add a Shapes  layer and hover over a shape.
Then loose the focus from the napari application with for example tabbing out.
The highlight event for the shapes layer will be emitted, and the shape will be visually highlighted.
demonstraion video
💡 Expected Behavior
I would expect this not to happen.
🌎 Environment
napari: 0.1.dev3376+ga6882ad
Platform: Windows-10-10.0.19045-SP0
Python: 3.10.5 (tags/v3.10.5:f377153, Jun 6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)]
Qt: 5.15.2
PyQt5: 5.15.10
NumPy: 1.26.4
SciPy: 1.13.0
Dask: 2024.4.2
VisPy: 0.14.2
magicgui: 0.8.2
superqt: 0.6.4
in-n-out: 0.2.1
app-model: 0.2.6
npe2: 0.7.5
OpenGL:
GL version: 4.6.0 Compatibility Profile Context <IP_ADDRESS>216
MAX_TEXTURE_SIZE: 16384
GL_MAX_3D_TEXTURE_SIZE: 2048
Screens:
screen 1: resolution 1920x1080, scale 1.0
Optional:
numba: 0.59.1
triangle not installed
Settings path:
C:\Users\tomi\AppData\Local\napari.venv_665327481d5ffa929bfcfc10d3499e5b2e1e735a\settings.yaml
Plugins:
napari: 0.1.dev3376+ga6882ad (81 contributions)
napari-console: 0.0.9 (0 contributions)
napari-svg: 0.1.10 (2 contributions)
💡 Additional Context
This issue was discovered together with @melonora.

Thanks for reporting this issue. I can reproduce when using Pan/Zoom mode or the shape drawing modes -- hover a shape in selection mode already does highlight --  and indeed it is a strange behavior!

any resolution on this?

It shows up on the toy example here too: https://napari.org/dev/gallery/nD_shapes.html

Update: I found that 0.5.3 does not have the same issue, so I'm using that for now


[Dashboard] Fix: Nebula send transaction params

PR-Codex overview
This PR enhances the SendTransactionButton component in Chats.tsx by introducing improved transaction handling and validation through the addition of a blockchain chain context and the sendTransaction method.
Detailed summary

Added import for sendTransaction from thirdweb.
Introduced chain variable using useV5DashboardChain.
Updated transaction validation to check for both txData and chain.
Refactored transaction sending logic to use sendTransaction with detailed parameters.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

Merge activity

Dec 15, 6:16 PM EST: The merge label 'hotfix' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


Repeated 503 errors during import

I've been regularly getting 503 errors when importing a process template of late. It occurs at different points in the import process and if you delete the incomplete imported process from the target and retry it may or may not go through successfully. On occasion we have to run process-migrator 5 or 6 times to get it to successfully import on the target. I've uploaded the last log file that had this error and the associated exported process file.
output.zip
Here, I've run the import 3 times over the course of an afternoon with only the final attempt succeeding. In each case its the same source and target...

I'm facing the same issue, random 503 error! and no details are logged in the logs.


gts, dets, recall, ap?

What does gts, dets, recall, and ap mean in voc dataset evaluation?

Feel free to reopen the issue if there is any question.

gts: number of bboxes of this class in your dataset
dets: the detect bboxes used to evaluate
recall: recall，a common metric used in the detection
ap: average precision, a common metric used in the detection

There is too much difference between the number of dets and the number of gts, is it not filtered by the box, such as the confidence threshold, nms? Is the prediction box for calculating recall and precision dets?
@jshilong

gts: number of bboxes of this class in your dataset
dets: the detect bboxes used to evaluate
recall: recall，a common metric used in the detection
ap: average precision, a common metric used in the detection

There is too much difference between the number of dets and the number of gts, is it not filtered by the box, such as the confidence threshold, nms? Is the prediction box for calculating recall and precision dets?
@jshilong


Crashing on Android: TypeError: expected dynamic type int64', but had type double'

I'm successfully running lottie on iOS but have problems with it on Android. App crashes just on the start when I try to show an animation. Stacktrace from the logcat:
AndroidRuntime
E  FATAL EXCEPTION: AsyncTask #1
E  Process: <MY APP PACKAGE NAME>, PID: 15990
E  java.lang.RuntimeException: An error occured while executing doInBackground()
E      at android.os.AsyncTask$3.done(AsyncTask.java:304)
E      at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:355)
E      at java.util.concurrent.FutureTask.setException(FutureTask.java:222)
E      at java.util.concurrent.FutureTask.run(FutureTask.java:242)
E      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
E      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
E      at java.lang.Thread.run(Thread.java:818)
E  Caused by: com.facebook.react.bridge.UnexpectedNativeTypeException: TypeError: expected dynamic type `int64', but had type `double'
E      at com.facebook.react.bridge.ReadableNativeMap.getInt(Native Method)
E      at com.airbnb.android.react.lottie.JSONReadableMap.optInt(JSONReadableMap.java:178)
E      at com.airbnb.lottie.LottieComposition$Factory.fromJsonSync(LottieComposition.java:188)
E      at com.airbnb.lottie.JsonCompositionLoader.doInBackground(JsonCompositionLoader.java:17)
E      at com.airbnb.lottie.JsonCompositionLoader.doInBackground(JsonCompositionLoader.java:7)
E      at android.os.AsyncTask$2.call(AsyncTask.java:292)
E      at java.util.concurrent.FutureTask.run(FutureTask.java:237)
E      ... 3 more

Package.json
"react-native": "0.41.2",
"lottie-react-native": "^1.1.1",

Gradle configuration:
android {
    compileSdkVersion 25
    buildToolsVersion "23.0.1"

    defaultConfig {
        applicationId "..."
        minSdkVersion 16
        targetSdkVersion 22

I had the same issue but managed to fix it by manually changing the "fr" value to an int inside the JSON file.
I changed "fr":29.9700012207031 to "fr":29 in my case.

@NicolasBonduel actually this hack worked out. thanks a lot for a suggestion!
but animation is still not showing up on android whereas it works perfectly on iOS... does it require another hack to make it working?

I've noticed this error as well and am currently working around it by loading assets through the android src instead of the js src (See this thread https://github.com/airbnb/lottie-react-native/issues/78)
As for @NicolasBonduel's suggestion, I tried that as well and, although it avoided the crash, noticed that it didn't allow animations to run properly

My guess is that we're trying to generate the animations with a version of the bodymovin plugin that is not yet supported by Lottie. I will try to work around that by using a previous version.

I actually fixed it by doing like @jdpigeon does here:
https://github.com/airbnb/lottie-react-native/issues/78

Yeah, I did that too. It works but it's just a workaround that results in keeping duplicated assets in two places. Not pretty.

It's definitely a hack, until Lottie is updated.

With the new 1.2.0 version, it doesn't crash anymore, but the animation doesn't seem to be running :/
I got warnings but no errors:

Animation contains merge paths but they are disabled
Composition larger than the screen 900x302 vs 720x1184. Scaling down.

This should be fixed in the latest version.

You can also get this error when you forget to import a package


Simplify CDK ExtraArg processing with jcommander overrides

Description
Simplify CDK ExtraArg processing with jcommander overrides.
Now, given two parameters --s3-region us-east-2 --s3-region us-west-2, jcommander will use the latter one.
Fixed places where parameter values which may have spaces weren't wrapped in quotes.
Removed cdk dependency on yargs
Fixed an issue where List arguments would split on , incorrectly e.g. --setHeader name "value1,value2"
Note: There's two use cases missing from this PR. 1. being able to remove/set an argument to null. 2. correct behavior with extraArgs in RFS for arguments placed in the ENV variables

Category: Bug Fix
Why these changes are required? Currently --setHeader in extraArgs is broken along with special characters in the values.
What is the old behavior before changes and new behavior after changes? CaptureProxy could crash on  startup with otherwise valid arguments.

Issues Resolved
[List any issues this PR will resolve]
Is this a backport? If so, please add backport PR # and/or commits #
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

[x] New functionality includes testing

[x] All tests pass, including unit test, integration test and doctest

[x] New functionality has been documented
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Closing due to error - 2024-09-26 18:55:28,638 -- Report creating failed: {"message":"Token required because branch is protected"}
Tracking in https://github.com/codecov/codecov-action/issues/1580


new CFDE API: server, gateway

Build host for CFDE API:

server in SenNet AWS
gateway

Replicate the Data Distillery configuration.

This is not necessary. Instead of having a separate CFDE API, we will import all HMSN data into the existing Data Distillery and use the Data Distillery API.


configuration problem 0.1.17

so I uninstalled the previous one a week ago after Opnsense upgrade
and seeing now that new version is available I installed again
but, I am not able to configure the integration
no idea why - how can I debug it?
opnsense version: OPNsense 24.1.1-amd64
plugin on opnsense:  os-homeassistant-maxit (installed) | 1.0
in HA:  0.1.17

I’ll need the hass logs

I assume the API key/ Secret are the same, you can resolve fw.local and you've restarted HA since installing the HACS integration?

I assume the API key/ Secret are the same, you can resolve fw.local and you've restarted HA since installing the HACS integration?

all assumptions correct - I use the same credentials as before and they are full rights as I used them for opnsense backup
restarted HA of course
but did not restart Opnsense but that would be too much, right? ;-)

some extras from HA log:
2024-02-12 09:39:29.406 ERROR (SyncWorker_39) [custom_components.opnsense.pyopnsense] Unexpected get_system_info error err=gaierror(-3, 'Try again'), type(err)=<class 'socket.gaierror'>
2024-02-12 09:39:29.407 ERROR (MainThread) [custom_components.opnsense.config_flow] Unexpected err=gaierror(-3, 'Try again'), type(err)=<class 'socket.gaierror'>

That's usually something fundamentally going on with the network and not really related to the integration. Perhaps uncheck the verify ssl box?
https://github.com/travisghansen/hass-opnsense/issues/19

gai stands for getaddrinfo(), so I'd check DNS. Try with IP address first, to confirm.

from HA ssh shell:

but still:

and HA log:
2024-02-12 10:53:13.313 ERROR (MainThread) [custom_components.opnsense.config_flow] Unexpected err=AbortFlow('Flow aborted: already_in_progress'), type(err)=<class 'homeassistant.data_entry_flow.AbortFlow'>

can you do dig fw.local please?

dig fw.local not working from HA

like I suspected. You're having dns resolution issues. The DNS server is <IP_ADDRESS>. Are you using HassOS?

Read this long thread about the problems of using HAOS and its CoreDNS configuration with .local addresses: https://community.home-assistant.io/t/local-dns/178108
So let's concentrate on https://<IP_ADDRESS>. Use that and uncheck ssl cert verification. Then check HA logs and post the error here.

I am seriously lost:
1- my HA is in VM in proxmox, but for last 2 years already
2- this plugin was working fine until... today (I unistalled after last Opnsense upgrade that killed the plugin)
3- my HA network settings:

and from cli on HA:

ping from HA works with both: fw.local and <IP_ADDRESS>

but from the same HA dig and nslookup to fw.local is not working:

trying to add https://<IP_ADDRESS> in plugin config shows this HA error in log:
2024-02-12 12:03:22.528 ERROR (MainThread) [custom_components.opnsense.config_flow] Unexpected err=AbortFlow('Flow aborted: already_in_progress'), type(err)=<class 'homeassistant.data_entry_flow.AbortFlow'>
what am I doing wrong?
I understand that this IP 172... is local IP of one of HA containers and it is not any of my machines ;-)
I am open for anything as long as you have enough patience guys ;-) (and highly appreciated)

To troubleshoot DNS issues you don't use ping, but you use nslookup and dig. And you have name resolution issues in your setup. This is one of the reasons that I dropped HAOS 2y ago and went to container installation on Proxmox. I manage the DNS, not HAOS, that has serious issues in that regard that devs always struggled to acknowledge. ;)

If you had the integration working, why are you configuring it from scratch? You should've disabled it instead of deleting it. So now you simply needed to re-enable it after the update.

Using https://<IP_ADDRESS> is not throwing the gai errors you had, so the problem was indeed the DNS resolution. Now you have another issue: HA can't connect to https://<IP_ADDRESS>. Did you try http instead of https? Enable http on OPNsense and try with http first. If it works, we'll see why https doesn't work.

To troubleshoot DNS issues you don't use ping, but you use nslookup and dig. And you have name resolution issues in your setup. This is one of the reasons that I dropped HAOS 2y ago and went to container installation on Proxmox. I manage the DNS, not HAOS, which has serious issues in that regard that devs always struggled to acknowledge. ;)

I got your point

If you had the integration working, why are you configuring it from scratch? You should've disabled it instead of deleting it. So now you simply needed to re-enable it after the update.

now, only now, I understood why my kids don't like me when I ask them... "WHY DID YOUD DO THAT?" ;-)

Using https://<IP_ADDRESS> is not throwing the gai errors you had, so the problem was indeed the DNS resolution. Now you have another issue: HA can't connect to https://<IP_ADDRESS>. Did you try http instead of https? Enable http on OPNsense and try with http first. If it works, we'll see why https doesn't work.

enabled http instead of https on opnsense but nothing much changed

I think I am having the same issue.
I don't think that it is a DNS issue.
Will try to get logs later.
@homonto can you try to run on HA a curl command to see if you can get data.
curl -k -u API_KEY:API_SECRET https://OPNSENSE_IP_OR_HOSTNAME/api/interfaces/overview/interfacesInfo

using curl with https://fw.local from HA terminal it gave me.... ;-)

@homonto Looks like you can talk to your OPNsense.
Can you check if your home-assistant.log hast the same error like mine?
Here are the logs from home-assistant.log
xmlrpc.client.ProtocolError: <ProtocolError for<EMAIL_ADDRESS>500 Internal Server Error> 2024-02-12 14:55:21.989 ERROR (SyncWorker_30) [custom_components.opnsense.pyopnsense] Unexpected get_telemetry error err=<ProtocolError for<EMAIL_ADDRESS>500 Internal Server Error>, type(err)=<class 'xmlrpc.client.ProtocolError'> 2024-02-12 14:55:21.989 ERROR (MainThread) [custom_components.opnsense] Unexpected error fetching OPNsense OPNsense state data: <ProtocolError for<EMAIL_ADDRESS>500 Internal Server Error> Traceback (most recent call last):   File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 313, in _async_refresh     self.data = await self._async_update_data()                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 269, in _async_update_data     return await self.update_method()            ^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/config/custom_components/opnsense/__init__.py", line 97, in async_update_data     await hass.async_add_executor_job(lambda: data.update())   File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run     result = self.fn(*self.args, **self.kwargs)              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/config/custom_components/opnsense/__init__.py", line 97, in <lambda>     await hass.async_add_executor_job(lambda: data.update())                                               ^^^^^^^^^^^^^   File "/config/custom_components/opnsense/__init__.py", line 316, in update     self._state["telemetry"] = self._get_telemetry()                                ^^^^^^^^^^^^^^^^^^^^^   File "/config/custom_components/opnsense/__init__.py", line 225, in inner     response = func(*args, **kwargs)                ^^^^^^^^^^^^^^^^^^^^^   File "/config/custom_components/opnsense/__init__.py", line 249, in _get_telemetry     return self._client.get_telemetry()            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/config/custom_components/opnsense/pyopnsense/__init__.py", line 101, in inner     raise err   File "/config/custom_components/opnsense/pyopnsense/__init__.py", line 98, in inner     return func(*args, **kwargs)            ^^^^^^^^^^^^^^^^^^^^^   File "/config/custom_components/opnsense/pyopnsense/__init__.py", line 1037, in get_telemetry     data = self._exec_php(script)            ^^^^^^^^^^^^^^^^^^^^^^   File "/config/custom_components/opnsense/pyopnsense/__init__.py", line 88, in inner     response = func(*args, **kwargs)                ^^^^^^^^^^^^^^^^^^^^^   File "/config/custom_components/opnsense/pyopnsense/__init__.py", line 131, in _exec_php     response = self._get_proxy().opnsense.exec_php(script)                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.12/xmlrpc/client.py", line 1122, in __call__     return self.__send(self.__name, args)            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.12/xmlrpc/client.py", line 1461, in __request     response = self.__transport.request(                ^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.12/xmlrpc/client.py", line 1166, in request     return self.single_request(host, handler, request_body, verbose)            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   File "/usr/local/lib/python3.12/xmlrpc/client.py", line 1196, in single_request     raise ProtocolError( xmlrpc.client.ProtocolError: <ProtocolError for<EMAIL_ADDRESS>500 Internal Server Error>

from GUI the only error on HA I have as above:
2024-02-12 13:19:18.444 ERROR (SyncWorker_37) [custom_components.opnsense.pyopnsense] Unexpected get_system_info error err=gaierror(-3, 'Try again'), type(err)=<class 'socket.gaierror'>
2024-02-12 13:19:18.445 ERROR (MainThread) [custom_components.opnsense.config_flow] Unexpected err=gaierror(-3, 'Try again'), type(err)=<class 'socket.gaierror'>

Can you check /config/home-assistant.log

Can you check /config/home-assistant.log

that was from there

Then I guess we don't have the same error ;)
But both can access the API with curl, but not the intergration.
Have to look into it later.

Here are the logs from home-assistant.log

your 500 internal server error is a permission problem for the API key you are using. You need to use a full admin account. OPNsense 24.1 changed granular permissions for some security standard. I solved this creating an hass full admin users and generating the key associated to that one.

using curl with https://fw.local from HA terminal it gave me.... ;-)

you are using curl with -k, that is the skip cert check. I asked you before: did you uncheck that setting when configuring the integration? Also: did you test with http?
You ask for help but don't follow the instructions. :D

I asked you before: did you uncheck that setting when configuring the integration? Also: did you test with http?

yes, and I showed the screen  for it as well - just under your comment ;-)

Sorry, I missed that post. :)
Well, you showed me a screenshot for http, so verify ssl doesn't have effect: the message is "already configured", it means that it finds in HA registry the old setup. And that means it is communicating, because it gets the deviceid from OPNsense and checks if it is already present in HA device registry.
Since opnsense doesn't provide via XMLRPC/REST a unique deviceid, the integration creates one randomly and writes it in OPNsense, in the file /conf/hassid. So what I would do in your case is RENAME that file in OPNsense, so the integration creates a new one, and it shouldn't tell you that it is already configured in HA.
Let me know...;)
PS: you still have the DNS issue...and that is more important than opnsense integration, you need to fix that asap. Then we'll also try to understand why it doesn't work in https.

your 500 internal server error is a permission problem for the API key you are using. You need to use a full admin account. OPNsense 24.1 changed granular permissions for some security standard. I solved this creating an hass full admin users and generating the key associated to that one.

Ok, I created a new user with admin rights, but still the error is the same (500 internal server error)

Sorry, I missed that post. :)

nobody is perfect  and this is not a problem  ;-)

Since opnsense doesn't provide via XMLRPC/REST a unique deviceid, the integration creates one randomly and writes it in OPNsense, in the file /conf/hassid. So what I would do in your case is RENAME that file in OPNsense, so the integration creates a new one, and it shouldn't tell you that it is already configured in HA.

removing this file allowed me to configure under: https://<IP_ADDRESS>

Let me know...;)

done - thank you ;-)

PS: you still have the DNS issue...and that is more important than opnsense integration, you need to fix that asap. Then we'll also try to understand why it doesn't work in https.

as I wrote also somewhere above, I reconfigured on HA /etc/resolv.conf from 172.... to my DNS and since then dig and nslookup from HA works properly:

removing this file allowed me to configure under: https://<IP_ADDRESS>

Good to know. Now try with the hostname, if you fixed DNS. ;)

Ok, I created a new user with admin rights, but still the error is the same (500 internal server error)

500 internal server problem is 99% related to the user/api/key. You can search past issues, I'm pretty confident you should concentrate on that.
Make sure the user is in the admins group. And that in Effective Privileges section of the user page, you see inherit from admins and if you edit those privileges don't check anything, let the user inherit without adding any privilege (all checkboxes unchecked).

This is the OPNsense 24.1 note regarding users/security:

removing this file allowed me to configure under: https://<IP_ADDRESS>

Good to know. Now try with the hostname, if you fixed DNS. ;)

first I tried with fw.local
but ... you know - I would proudly announce it if it worked
so, step by step:
1st try: https://fw.local

2nd, without SSL verification:

however as I showed you, from HA dig fw.local and nslookup work now after changing DNS in resolv.conf

however as I showed you, from HA dig fw.local and nslookup work now after changing DNS in resolv.conf

if it works with IP, the communication issue is not an issue.
if the error is GAI, it means python's getaddrinfo() fails. And it's not a coincidence.
 You will have random issues also in other functionalities with time. Always remember an old System Admin saying: 95% of the time, when something strange happens and you can't find the cause, it's DNS. :)
DNS is the most important service, often overlooked because generally it works, but when it doesn't you can get crazy.
BTW: I remember from 2y ago with HAOS that the dns config files were overwritten when you will update HAOS. So even when fixed manually, you had to do it at every upgrade. HAOS simply sucks in that regard. :)

one more lesson I learned today: when you suggested to delete /conf/hassid and I succeeded configuring, I found out such status...

so, I did NOT delete the integration in the first place when it stopped working (week or so ago) - I disabled it (probably after reading here that patch is on the way).
But today, seeing 0.1.17 announced I could not find it in my HA (disabled and filtered out from lovelace) so I removed it from HACS, installed again and I was trying to configure it again and again... probably enabling it would have been enough... - oh life ;-)
Thing is: until I succeeded with configuration I was not able to see it - filtered out ;-)

Always remember an old System Admin saying: 95% of the time, when something strange happens and you can't find the cause, it's DNS. :)

I am 100% with you from  my experience as well...
if you asked me if it worked before over IP or hostname - no idea - I created certs just few weeks ago - until then I used always IP

@alexdelprete

how do they say: "all's well that ends well!". :)
Glad to have been helpful.


[H] displayed after world name

There is an [H] displayed after one of my world names, and the world name prefix is broken for that world, what does the [H] mean and how can I fix the not displayed prefixes?

Hidden


XML report includes semicolon after PLUGIN_ERROR id and message

When scanning the following test.cfm file:
<cfscript>
  defaultFontColor = "##444444";
</cfscript>

with java -jar CFLint-1.0.0-all.jar -file test.cfm -xml, the XML report contains:
<?xml version="1.0" encoding="UTF-8" ?>
<issues version="1.0.0">
  <issue severity="ERROR" id="PLUGIN_ERROR:" message="PLUGIN_ERROR:" category="CFLint" abbrev="PE">
    <location file="test.cfm" fileName="test.cfm" function="" column="1" line="1" message="" variable="">
      <Expression><![CDATA[]]></Expression>
    </location>
  </issue>
  <issue severity="ERROR" id="PLUGIN_ERROR" message="PLUGIN_ERROR" category="CFLint" abbrev="PE">
    <location file="test.cfm" fileName="test.cfm" function="" column="22" line="2" message="Error in plugin: class java.lang.NullPointerException" variable="class java.lang.NullPointerException">
      <Expression><![CDATA[]]></Expression>
    </location>
  </issue>
</issues>

The first issue incorrectly contains a semicolon : after PLUGIN_ERROR in id and message attributes. The second one is fine. If there are more plugin errors from the same file, then most of them have the erroneous semicolon.
Of course, these errors shouldn't be triggered for the file in the first place, but that's already reported in #240.

fixed.  Thanks!


Knob indicator doesn't adjust when its value prop is modified though a callback

The title should be explicit enough, here are the callback and the visuals
@app.callback(
    Output('knob', 'value'),
    [],
    [],
    [
        Event('radio-choice', 'change')
    ]
)
def knob_reset():
    """reset the knob to 0 when the radio item is toggled"""
    return 0

here's a preview. the knob's value is being set to a certain value with change in boolean switch.
https://user-images.githubusercontent.com/41485085/139593594-32198cf1-6d6f-44c1-9d56-fe7c156ee46f.mov


Release <IP_ADDRESS>3

Release <IP_ADDRESS>3

Codecov Report

Merging #147 into master will decrease coverage by 0.08%.
The diff coverage is 94.78%.

@@            Coverage Diff             @@
##           master     #147      +/-   ##
==========================================
- Coverage   90.31%   90.23%   -0.09%
==========================================
  Files          39       42       +3
  Lines        3262     3470     +208
  Branches       13       13
==========================================
+ Hits         2946     3131     +185
- Misses        303      326      +23
  Partials       13       13

Impacted Files
Coverage Δ

...entFilterRule/MSFT_EXOHostedContentFilterRule.psm1
87.3% <100%> (-0.2%)
:arrow_down:

...ryReviewPolicy/MSFT_SCSupervisoryReviewPolicy.psm1
100% <100%> (ø)

...MSFT_EXOCASMailboxPlan/MSFT_EXOCASMailboxPlan.psm1
85.71% <100%> (-1.08%)
:arrow_down:

...liancePolicy/MSFT_SCRetentionCompliancePolicy.psm1
100% <100%> (+3.57%)
:arrow_up:

...ComplianceRule/MSFT_SCRetentionComplianceRule.psm1
98.14% <100%> (-0.04%)
:arrow_down:

...ControlSettings/MSFT_SPOAccessControlSettings.psm1
95.23% <100%> (-0.15%)
:arrow_down:

...sources/MSFT_SPOSiteDesign/MSFT_SPOSiteDesign.psm1
90.58% <100%> (-0.11%)
:arrow_down:

...Policy/MSFT_EXOHostedOutboundSpamFilterPolicy.psm1
88.67% <100%> (-0.8%)
:arrow_down:

...s/MSFT_SPOStorageEntity/MSFT_SPOStorageEntity.psm1
100% <100%> (ø)
:arrow_up:

...ce365DSC/DSCResources/MSFT_SPOApp/MSFT_SPOApp.psm1
94.11% <100%> (+0.11%)
:arrow_up:

... and 36 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 2cd3ccf...25552ff. Read the comment docs.


deps(gymnasium): update gymnasium version to 0.28.1

Description

Update gymnasium version to 0.28.1

Motivation and Context
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.
You can use the syntax close #15213 if this solves the issue #15213

[x] I have raised an issue to propose this change (required for new features and bug fixes) #39

Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds core functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation (update in the documentation)

Implemented Tasks

[ ] Subtask 1
[ ] Subtask 2
[ ] Subtask 3

Checklist
Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

[x] I have read the CONTRIBUTION guide. (required)
[ ] My change requires a change to the documentation.
[x] I have updated the tests accordingly. (required for a bug fix or a new feature)
[ ] I have updated the documentation accordingly.
[x] I have reformatted the code using make format. (required)
[x] I have checked the code using make lint. (required)
[x] I have ensured make test pass. (required)

It's time to bump the version to 0.3.0 after the PR #16 finishes.

got it


cni config: No networks found

Bug
Environment

Platform: bare-metal

OS: container-linux

Terraform: v0.10.7

Plugins: Provider plugin versions
provider.local: version = "~> 1.0"
provider.null: version = "~> 1.0"
provider.template: version = "~> 1.0"
provider.tls: version = "~> 1.0"
terraform-provider-matchbox v0.2.2

Ref: Git SHA (if applicable)*
ref=1bc25c103654a497bcc0c2486104426f09ea2456

Problem
Temporary Kubernetes control plane API fails to start
Log entries show issues relating to missing cni config
cni.go:189] Unable to update cni config: No networks found in /etc/kubernetes/cni/net.d
kubelet.go:2136] Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

Desired Behavior
bootkube API server starts and cluster is provisioned
Steps to Reproduce
cluster.tf
module "bare-metal-mercury" {
  source = "git::https://github.com/poseidon/typhoon//bare-metal/container-linux/kubernetes?ref=1bc25c103654a497bcc0c2486104426f09ea2456"

  # install
  matchbox_http_endpoint  = "${var.matchbox_http_endpoint}"
  container_linux_channel = "${var.container_linux_channel}"
  container_linux_version = "${var.container_linux_version}"
  ssh_authorized_key      = "${var.ssh_authorized_key}"

  # cluster
  cluster_name    = "${var.cluster_name}"
  k8s_domain_name = "${var.k8s_domain_name}"

  # machines
  controller_names   = "${var.controller_names}"
  controller_macs    = "${var.controller_macs}"
  controller_domains = "${var.controller_domains}"
  worker_names       = "${var.worker_names}"
  worker_macs        = "${var.worker_macs}"
  worker_domains     = "${var.worker_domains}"

  # bootkube assets
  asset_dir = "${var.asset_dir}"

  # Optional
  networking                    = "${var.networking}"
  cached_install                = "${var.cached_install}"
  install_disk                  = "${var.install_disk}"
  container_linux_oem           = "${var.container_linux_oem}"
  pod_cidr                      = "${var.pod_cidr}"
  service_cidr                  = "${var.service_cidr}"
}

terraform.tfvars
matchbox_http_endpoint = "http://matchbox.example.com:8080"
matchbox_rpc_endpoint = "matchbox.example.com:8081"
ssh_authorized_key = "ssh-rsa ..."

cluster_name = "example"
container_linux_version = "1465.6.0"
container_linux_channel = "stable"

# Machines
controller_names = ["m0", "m1"]
controller_domains = ["m0.example.com", "m1.example.com"]
controller_macs = ["MAC1", "MAC2"]
worker_names = ["n0", "n1"]
worker_domains = ["n0.example.com", "n1.example.com"]
worker_macs = ["MAC1", "MAC2"]

# Bootkube
k8s_domain_name = "m0.example.com"
asset_dir = "assets_dir"

# Optional (defaults)
cached_install = "true"
install_disk = "/dev/sda"
#container_linux_oem = ""
networking = "calico"
pod_cidr = "<IP_ADDRESS>/16"
service_cidr = "<IP_ADDRESS>/16"

Run
terraform plan
terraform apply

Resolved this by restarting kubelet service multiple times. Seems like synchronicity issues during the deployment process

To provide a bit of background detail / explanation, its normal for the kubelet to log about the lack of CNI config or CNI plugins during initial bootstrapping. The flannel or calico DaemonSet (depending on your choice) has a sidecar pod called install-cni that is responsible for adding the correct version of the CNI plugins on each node (at /opt/cni/bin which is mounted in the kubelet) and the CNI config in /etc/kubernetes/cni/net.d.
Its actually handy these are decoupled because it means you can kubectl apply to update your flannel or calico to some new version and get the official upstream CNI config and plugins they intend you use.


calico picks virtual-ip (i.e /128) address configured on eth0 for BGP peering and calico-node pod crashes

We have a v6 only k8s cluster (1.21.1) with calico CNI (3.19.1). Our cluster has 3 master nodes for HA purpose (master-0, master-1,master-2).  HA-proxy /keepalived is being used to load-balance the requests being sent to api-server . HA proxy uses VIP as front-end for api-servers.
Is there a way to skip this address (i.e /128 or /32) address ?
Our configuration is shown below :
PodCIDR:  fd00:eccd:81:ffff::/64
Internal network CIDR (Node cidr):  fd00:eccd:81:1111::/64
Nodes:
master-0-ejlnoox-ibd-stack                Ready    control-plane,master   4h15m   v1.21.1   fd00:eccd:81:1111::3           SUSE Linux Enterprise S4
master-1-ejlnoox-ibd-stack                Ready    control-plane,master   4h15m   v1.21.1   fd00:eccd:81:1111::e           SUSE Linux Enterprise S4
master-2-ejlnoox-ibd-stack                Ready    control-plane,master   4h15m   v1.21.1   fd00:eccd:81:1111::4           SUSE Linux Enterprise S4
worker-pool1-ilq0mgem-ejlnoox-ibd-stack   Ready    worker                 4h9m    v1.21.1   fd00:eccd:81:1111::2           SUSE Linux Enterprise S4
VIP address: fd00:eccd:81:1111::123/128
Master 0 Configurations:
eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 2090 qdisc pfifo_fast state UP group default qlen 1000
link/ether fa:16:3e:8d:d4:4a brd ff:ff:ff:ff:ff:ff
inet <IP_ADDRESS>/21 brd <IP_ADDRESS> scope global eth0
valid_lft forever preferred_lft forever
inet6 fd00:eccd:81:1111::123/128 scope global nodad deprecated
valid_lft forever preferred_lft 0sec
inet6 fd00:eccd:81:1111::3/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::f816:3eff:fe8d:d44a/64 scope link
valid_lft forever preferred_lft forever
2021-08-10 06:23:13.886 [INFO][81] monitor-addresses/startup.go 782: Using autodetected IPv6 address fd00:eccd:19:1111::9/128 on matching interface eth0
2021-08-10 06:23:13.886 [INFO][81] monitor-addresses/startup.go 589: Node IPv6 changed, will check for conflicts
2021-08-10 06:23:13.892 [WARNING][81] monitor-addresses/startup.go 1134: Calico node 'master-0-eccd-ci-os-19-jenkins' is already using the IPv6 address fd00:eccd:19:1111::9.
2021-08-10 06:23:13.892 [WARNING][81] monitor-addresses/startup.go 1120: IPv6 address has changed. This could happen if there are multiple nodes with the same name. node="master-2-eccd-ci-os-19-jenkins" original="fd00:eccd:19:1111::c" updated="fd00:eccd:19:1111::9"
2021-08-10 06:23:13.892 [INFO][81] monitor-addresses/startup.go 351: Clearing out-of-date IPv6 address from this node IP="fd00:eccd:19:1111::9/128"
2021-08-10 06:23:13.899 [WARNING][81] monitor-addresses/startup.go 363: Failed to clear node addresses error=update conflict: Node(master-2-eccd-ci-os-19-jenkins)
2021-08-10 06:23:13.899 [WARNING][81] monitor-addresses/startup.go 1340: Terminating

@hanamantagoudvk have you looked at this page at all? https://docs.projectcalico.org/networking/ip-autodetection
This might help configure selection of the correct address.

@caseydavenport i forgot to mention above. We are using auto detection method (i.e interface=eth0). But in this eth0 interface VIP sits along with node address. So calico picks the VIP instead of node address. So i want to propose one thing here, we should one way to skip ip addr along with auto detection method. I see that skip-interface method is there, but skip ip is not present.
Even @fasaxc is ok with this proposal. I can work this fix.

@caseydavenport @fasaxc : Currently calico/node code doesn't guarantee/ensure that nodeAddress it picks under an eth interface is remains same every time. Deterministic way to selecting same ip every time is our requirement. Isn't it possible to pick the ip which is present in  k8s node object ?

Isn't it possible to pick the ip which is present in k8s node object ?

This is an existing feature request, but not implemented yet. If you are using manifests (not operator) you can use the Kubernetes downward API to configure the IP env var with the node IP.

We are using auto detection method (i.e interface=eth0)

Would autodetection mode cidr=A,B,C work for your case?

This is an existing feature request, but not implemented yet. If you are using manifests (not operator) you can use the Kubernetes downward API to configure the IP env var with the node IP.

Yes we do use manifest for the daemonset. But manifest file is generic file , how can we specify ip address of a given node in IP env var ?

@caseydavenport : Downward API seems to be having certain limitations. We want set the IP or IP6 values like shown below.
But downward API currently supports only status.podIP . With dual-stack feature coming into picture now , we should enhance downward API to support status.podIPs

      env:
        - name: IP
  	  valueFrom:
            fieldRef:
              fieldPath: status.podIPs[0]
        - name: IP6
  	  valueFrom:
            fieldRef:
              fieldPath: status.podIPs[1]

@caseydavenport : When i asked couple of folks in community , they say not possible to access indexed values like above. Hence downward API can't be used by us. Is it ok to introduce skip-ip  field ?

Would autodetection mode cidr=A,B,C work for your case?

Let me explain why can't we use cidr=A,B,C auto detection method.
Our k8s cluster deployment is done on VMs (worker nodes) which are managed by openstack.
worker node IPs belong to say cidr A. The VIP configured on eth0 (port where cidr A IP is assigned) should also belong to same cidr A for security purpose. In openstack , security rules are tightly coupled with port concept. By default it only allows IP addresses assigned by opestack itself. If we configure any additional IPs such as VIP , we need to add them to security groups (using allowed-address-pair config) to let the traffic destined for VIP. If we try to configure VIP from say cidr B , openstack doesn't allow it. Hence VIP should also belong to same cidr A.


support for spec 3.6

Spec 2.6 is needed once you try to use spec_wait inside a rails 5 project.

Do you mean RSpec 3.5?

Sorry, I meant RSpec 3.6 iso RSpec 2.6. I will update the above message accordingly.

I am currently adding ruby 2.3 and rspec 3.6 to the forked travis configuration, and I seem to have to fix a few things still. Will come back soon.

I'm confused. I don't see RSpec 3.6 or a prerelease on RubyGems.org. I've opened up #17 if you want to take a look at what I'm doing there.

My bad, so sorry. It is indeed 3.5, I got confused with the dependency declaring < 3.6

close this PR in favour of #17


Force ACT to end encounter

I've been lookin at the test.html overlay for funzies and noticed that it has a inCombat flag for ACT and the game it's self.  The game flag (yes/no) seems to always be correct and even remains in combat during long boss transformations.
Question: Would be be possible to have Cactbot tell ACT when combat ends? I like having a low encounter ends setting for ACT but this splits up a lot of raid fights like Hades EX and the Eden fights.  My current workaround is to have a high second time set and to have an in-game macro that does "/echo end" when clicked. This works but it's a real pain in the butt after a while.

For what it's worth, cactbot does tell ACT when you wipe.  This works in everything HW and onward, I think.  I have my encounter time set to ridiculously high and just depend on that.
The game is not always correct.    There was also a period of time where this also happened in the moogle trial.

I have a personal fork that does this fairly successfully, with a customizable delay so that you have to be out of combat in-game for (x) seconds before ending the encounter, which would mitigate that problem in o5. 5s seems like a good default as dot ticks make you re-enter combat every 3s, and it's leaving my ACT encounters looking very neat.
The UI panel is a big mess though.. 🙃

Ooh, 5 seconds out of game combat is nice, and avoids having to read logs.  Nice thinking!  I was thinking that this should probably be upstreamed to ngld's overlayplugin, as it'd be a nice feature for everybody.  Although I guess this runs into the cn vs intl version issue again there.  Oof.

I guess the best place would for this to be in the FFXIV parser itself.

https://github.com/ngld/OverlayPlugin/pull/134


Working with multiple GPUs on a single machine

Hi,  I have 4 GPUs with a single size of 7GB. When I use 'tmbed embed --use-gpu -f ./ch/test.fasta -e test.h5', it prompts that the GPU is out of memory.
How can 4 GPUs participate in the work simultaneously

Hi. Unfortunately, I do not have any experience with a multi-GPU environment. Assuming you are already using a batch size of 1 to process each sequence individually, splitting the data processing won't help much (I do not think that there is any benefit in splitting the computation of individual layers of the model layers onto multiple GPUs).
One solution that would come to mind is pooling the GPUs' memory into one big chunk of memory. However, I do not know how exactly this would be done; and it might not be possible/feasible without a NVLink connection (or similar) between the GPUs.
Another solution would be to modify the attention mechanism, which due to its squared complexity is the culprit for many out of memory errors. However, this would mean modifying the Huggingface model (T5EncoderModel), i.e., rewriting a modified Pytorch Module that can load the pretrained weights. The calculation of the attention mechanism could then be split into processing each query (residue) individually, rather than all at once. Though, I'd guess that this would increase the runtime by quite a lot.
Finally, you could try to run the T5EncoderModel in 8-bit mode. Though, I do not know how much of an impact that would have on the prediction accuracy. See: https://huggingface.co/docs/transformers/perf_infer_gpu_one
With that being said, before you try any of those solutions, you might want to consider running your sequences in Google Colab (if there are no issues regarding data security). A free account usually gets you a GPU with 16GB of memory and about an hour of runtime.
Regards
Michael

Hi. Thank you for your reply. The final solution is to manually allocate data. I have a total of 20W of data, which is divided into 4 parts on average and assigned separately:
CUDA_VISIBLE_DEVICES=0 nohup python -m tmbed embed --batch-size 1000 -f ~/protein/data0.fasta -e ~/protein/data0.h5 > ~/protein/data0.log 2>&1 &
CUDA_VISIBLE_DEVICES=1 nohup python -m tmbed embed --batch-size 1000 -f ~/protein/data1.fasta -e ~/protein/data1.h5 > ~/protein/data1.log 2>&1 &
......
then
CUDA_VISIBLE_DEVICES=0 nohup python -m tmbed predict --batch-size 5000 -f ~/protein/data0.fasta -e ~/protein/data0.h5 > ~/protein/data0.log 2>&1 &
CUDA_VISIBLE_DEVICES=1 nohup python -m tmbed predict --batch-size 5000 -f ~/protein/data1.fasta -e ~/protein/data1.h5 > ~/protein/data1.log 2>&1 &
Finally, thank you very much for your work.

Ah, then I misunderstood your issue. I thought that the 7 GB memory of a single GPU were not enough to process your sequences with the ProtT5 encoder and you wanted to combine the memory of multiple GPUs to be able to fit those longer sequences. However, based on your solutions, it seems that instead you just wanted to spread the work over all GPUs to speed up the process, i.e., have more compute (not memory).


Helm Chart values not parsed correctly (PodSpec.nodeSelector: got "map", expected "string")

Rancher Server Setup

Rancher version: v2.6.2
Installation option (Docker install/Helm Chart): Helm Chart

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1, Kubernetes v1.19.10

Proxy/Cert Details: Nginx Ingress Controller (came with RKE1 cluster), Rancher-generated TLS certificate (cert-manager installed)

Information about the Cluster

Kubernetes version: v1.21.5
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): VMware vSphere provider

Describe the bug
Unable to deploy Nginx Ingress Controller on downstream cluster (VMware vSphere provider) from Rancher UI (Apps & Marketplace) with controller.nodeSelector set to node-role.kubernetes.io/worker: 'true'.
Deployment with the same values is successful when deploying with helm from CLI:
cat > nginx-controller-load-balancer-service.yaml <<EOF
controller:
  nodeSelector:
    node-role.kubernetes.io/worker: 'true'
EOF

helm install ingress-nginx ingress-nginx/ingress-nginx --namespace ingress-nginx -f nginx-controller-load-balancer-service.yaml --version=4.0.8

Since it works from CLI, this seems to be Rancher issue.
To Reproduce

Add ingress-nginx repository to Rancher (Apps & Marketplace) using this URL (from their docs): https://kubernetes.github.io/ingress-nginx
Try to deploy Nginx Ingress Controller from Rancher UI (Helm Chart version 4.0.8) changing controller.nodeSelector to in values yaml (single change in line 149):

  nodeSelector:
    node-role.kubernetes.io/worker: 'true'

Result
Helm install error:

helm install --namespace=ingress-nginx --timeout=10m0s --values=/home/shell/helm/values-ingress-nginx-4.0.8.yaml --version=4.0.8 --wait=true ingress-nginx /home/shell/helm/ingress-nginx-4.0.8.tgz
Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(Deployment.spec.template.spec.nodeSelector.kubernetes): invalid type for io.k8s.api.core.v1.PodSpec.nodeSelector: got "map", expected "string"

Expected Result
Successful installation.
Additional context
Default selector only works:
  nodeSelector:
    kubernetes.io/os: linux

Keeping default selector works:
  nodeSelector:
    kubernetes.io/os: linux
    node-role.kubernetes.io/worker: 'true'

Does not work:
  nodeSelector:
    node-role.kubernetes.io/worker: true

  nodeSelector:
    node-role.kubernetes.io/worker: 'true'

  nodeSelector:
    node-role.kubernetes.io/worker: "true"

Per @kinarashah's notes, we're allowing duplicate values in through the editor somehow. We should look at the install component first, where there's code to merge new values into the resource class.

not sure who is assigned this issue, but manually testing this is working following the aws out-of-tree documentation

Hey @slickwarren do you mean this was covered by these other issues validation?
https://github.com/rancher/dashboard/issues/9110
https://github.com/rancher/rancher-docs/pull/844

Automation coverage is here https://github.com/rancher/dashboard/pull/9865
Closing as the automation coverage looks right.


Multi dimentional element constraint

Extended the element constraint to accept multiple dimentions, with multiple vars/expressions instead of only 1.
Basically, in NDVarArray's getitem, where the array to be considered is found (based on the constant values in the indices) and flattened, an new index expression is created based on the ones given and the dimentions of the array.
Then, this new expression is given as index to the Element constraint, along with the flattened array.
In addition, if the user writes [x1][x2] instead of [x1,x2], i.e., does not use comma-seperated indexing, an exception is thrown.

Certainly a nice addition, but two things:

We should have a way to print the 2-d element constraint, now if a user prints it he will get something like [0,1,....,8][3 * idx0 + idx1] which might be confusing (not sure how to fix it tho...)
The implementation of get_item really took me a while to understand it, we should add some documentation and/or just completely rewrite it. I can do an effort in rewriting it. If I'm correct, it first checks if we can select a one-dimensional array from the matrix using numpy indexing (if the idx on some dimension are integer) and then proceeds to build a new index using CPMpy expressions to use on the flattened array.

Hmm, I do like the idea of checking it in the __repr__ actually.
But maybe we should look at another representation all together for multi-dimensional elements...
If I take a 2d matrix such as sudoku, this is still not looking very good imho.
    [e, e, e,  2, e, 5,  e, e, e],
    [e, 9, e,  e, e, e,  7, 3, e],
    [e, e, 2,  e, e, 9,  e, 6, e],

    [2, e, e,  e, e, e,  4, e, 9],
    [e, e, e,  e, 7, e,  e, e, e],
    [6, e, 9,  e, e, e,  e, e, 1],

    [e, 8, e,  4, e, e,  1, e, e],
    [e, 6, 3,  e, e, e,  e, 8, e],
    [e, e, e,  6, e, 8,  e, e, e]][idx0, idx1]

I am not sure about the test. It will always be true (unless we change the repr) and also is not really readable for the user, because it actually prints ('[IV0 IV1 IV2 IV3 IV4 IV5 IV6 IV7 IV8 IV9 IV10 IV11][sum([1, 4, 2] * [IV14, '
'IV12, IV13])]')

Ok so we will leave the specialized representation for later (or never), will merge this as is.


Added css file

in this commit i have added css file and made presentation look good with giving the gradient background of making
fonts beautiful

Appreciate your contribution 🔥


Add missing german bad words

The current version had very few German bad words, making it unsuitable for my project.
I collected missing words from different German dictionaries and added them.
(This might be my most disturbing commit ever)

@phoehnel wow fantastic (and yet disturbing) contribution! Merging it 💯


Backporting fix for connecting to the wrong SQLServer host (#1965)

Backport of #1965

Hey. This commit somehow didn't make it to 11.2.2 https://github.com/microsoft/mssql-jdbc/blob/v11.2-servicing/src/main/java/com/microsoft/sqlserver/jdbc/IOBuffer.java

Hey. This commit somehow didn't make it to 11.2.2 https://github.com/microsoft/mssql-jdbc/blob/v11.2-servicing/src/main/java/com/microsoft/sqlserver/jdbc/IOBuffer.java

@mmimica, you're right. Apologies, this is our mistake. Do you need this fix in 11.2.2? This fix will be in the 12.2.2 GA coming in late January.

I'm not going to use preview releases.
At least you should correct the 11.2.2 Changelog.

The 12.2.0 is a GA. So it will be a stable release, not a preview. Again, apologies for the mistake.


Multiplayer projectile #94

closes #94

Not only do I not have 50,000 lines of code added, but I have negative lines....
This makes me sad.


Upgrade ASM to 9.6 to support Java 22

jib 3.4.1 does not support java 22. Please upgrade ASM to 9.6 to support Java 22.
Optionally upgrade ASM to 9.7 to include support for Java 23.

Hi, any progress on this issue?

:(

Any progress?

@estigma88 see https://github.com/GoogleContainerTools/jib/pull/4252


[BUG] setSelectedOption not updating selectedVariant

Describe the bug
When using useProductOptions() hook, when changing the options, the returned selectedVariant doesn't appear to change to reflect
It seems to happen if initialVariantId={null}

This was hopefully fixed here https://github.com/Shopify/hydrogen/pull/1486 and released in 0.24.0 https://github.com/Shopify/hydrogen/releases/tag/%40shopify%2Fhydrogen%400.24.0
Let us know if that doesn't fix it though.


Add separate overview tab for Notes

Thank you for converting Details to Grid View, donation incoming! It looks awesome.
Would it also be possible to add Notes as a separate tab, next to the Overview section? Right now they appear at the top of any game description in the Overview section. Thanks for considering.

Thanks for the donation. Just curious to know what you do with the notes? I actually don't write most of the time.

I play a lot of old school RPGs, so for something like Might and Magic I-V I use it as a journal to write down quest markers and such. For a lot of old games it's mainly tracking progression since I rarely spend more than a month with the same game.

Yea, got it. I like retro games, too. BTW, I like M&M VI, that's my first M&M game to play with. Heroes of M&M is a good series, too.

Done. Will release in v1.2.


Text changes based on feedback

[ ] In the section under "Can you draw...", most of the first paragraph explains what GDD is. Let's keep the first sentence as is, and make the rest of that paragraph hidden unless the viewer clicks on something to expand. "More information on growing degree days" or "What are growing degree days" as a clickable button?

[ ] On x-axis label of the 'you draw it' figure, add Lake Temperature to the label above Growing degree days (make the Lake temperature label bigger than the GDD label).

[ ] In the 'lakes are expected to get warmer in the future' section, split the first bullet into two, as follows:

Scientists agree that the earth will get warmer through the end of the 21st century.

However, the amount of warming depends on actual greenhouse gas emissions and how physical processes such as precipitation and wind speed will change.

[ ] change legend labels on future air temperature projections graph to be "High greenhouse gas emissions (A2)" and "Low greenhouse gas emissions (B1)".

[ ] in future suitability section, change text of first bullet to read:

As  water temperatures get warmer, many lakes that currently can support natural walleye reproduction are unlikely to continue to have the thermal habitat conditions to do so.

[ ] in future suitability section, add a bullet to the beginning:

Water temperature is a critical component of fish habitat.

[ ] in future suitability section, add a bullet to the end:

The predictions shown here are based only on projected changes in water temperature, and do not account for changes in the fish community, water quality, fish management, or angler behavior that may influence walleye and largemouth bass populations.

@gjahansen2 I have gotten feedback that when we have more then 3 bullets, we should just have a paragraph instead. How do you feel about that? Could cut down, or do more paragraphs

Sure, that's fine
On Tue, Aug 30, 2016 at 2:30 PM, Jordan S Read<EMAIL_ADDRESS>wrote:

@gjahansen2 https://github.com/gjahansen2 I have gotten feedback that
when we have more then 3 bullets, we should just have a paragraph instead.
How do you feel about that? Could cut down, or do more paragraphs
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/USGS-VIZLAB/climate-fish-habitat/issues/120#issuecomment-243552528,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASiU6qSW5MMLUIO3quwmWZXOMSV908GQks5qlITfgaJpZM4Jw10y
.

--
Gretchen Hansen
https://gretchenhansen.squarespace.com

I will work on incorporating USGS edits as well

@jread-usgs done, I think.

@gjahansen2 all are taken care of in #122 or moved into new (or existing) issues


BetterTransformer for florence2

Feature request
NotImplementedError: The model type florence2 is not yet supported to be used with BetterTransformer. Feel free to open an issue at https://github.com/huggingface/optimum/issues if you would like this model type to be supported.
Motivation
Florence-2 is a small (compared to other vLLM) and widely used model thus a speed up in inference will be very helpful for everyone
Your contribution
I can help with a PR but I would need some guidance.

+1 to offering to support export own fine-tuned version


Dependecy update. Chart not updated

Updated dependecies of cert-manger, kubernetes and golang image.

I have built and tested a image at https://hub.docker.com/layers/egeback/cert-manager-cpanel-dns-webhook/v0.3.0/images/sha256-3b4ecdfc83cce74700999ad8cd26b96b1da9d2784d73a00b4b9408e5b714a0ae?context=repo.
Helm chart: https://github.com/egeback/helm-charts/pull/30


Add AsyncUnion DStream operation

I am not sure a new API is needed here, it's identical to existing Union semantic wise? starting RDD compute on batch interval is kind of perf tune option, can we use --conf instead?
can we simply override existing UnionDStream and RunJob on UnionRDD since what we need is to start it at batch interval even if previous batch not complete?
UpdateStateByKey does the same thing now. ssc.progressListener.lastCompletedBatch can be used so that if last batch already completes. no need to start a parallel job.

Here we want a general operation that can transform a normal DStream to "AsyncDStream". The operation should be general enough, not limited to "reading from Kafka" or "UpdateStateByKey".
Another reason to add a new operation is that it can combine with other operations. For example, we can begin with an normal kafka direct stream with interval of 1 minute, then transform it to a "AsyncDStream", and then use "Window" operation to transform it to a DStream of 3 minutes batch interval, and finally apply "UpdateByKey". After all these operations, we can achieve the goal that pull from kafka asynchronously in a small batch interval and at the same time "UpdateStateByKey" in a larger interval.
I'd prefer not to change the semantic of "UpdateStateBykey" because it is the standard Spark operation. Changing it may surprise our customer and leads to confusion.

I agree we should have a more generic API. However, UpdateStateByKey is special in that its 2nd stage must be in sync. i.e. the 2nd stage can't start until previous batch completes. otherwise will run into same issue of concurrentJobs. So if one of union's parent is a UpdateStateByKey (in theory), it will hit the issue.
I prefer your Kafka based approach because this approach needs developer to write a different more complex driver program by using a Window at a 1/nth interval of batch interval?
UpdateStateByKey's change is on implementation. what do you refer to by 'semantic change'?

@qintao1976 - I like the idea of generic API for DStream but I am not clear how this PR addresses the problem of batches not starting on-time (and batches getting queued up for execution because of delays)? Is that problem outside the scope of this PR? That is the problem that is addressed in PR #449 in the context of "update state" step. How is this approach of async union better than simply materializing the RDD at the time of creation of CSharpDStream?

@skaarthik , in this PR, the RDD is not materialized when Compute() method of DStream is called. There are two reasons:

Otherwise, it will block streaming UI tab.
We want something "async", just like"Receiver mode". In "Receiver Mode", there are two separate things, the first is to receive data from Kafka and create BlockedRDD to cache the received data, the second step is to process the data. In AsyncDStream, RDDs are queued and materialized in separate threads, this is much like what "Receiver" do.
By the way, renyi think the name of operation "unionAsync" is misleading, and I am considering to change the name.

@qintao1976
I still think we should stick to the original DirectKafkaReceiver or ParallelKafkaDataFetcher:

original design has clear 'receiver' semantic, nothing new invented.
receiver is IO intensive which totally makes sense to run in parallel, not sure yet extending it to generic async has much value.
the approach in question basically requires an extra Window operation which can be confusing to developers and they also needs to understand certain operation like UpdateStateByKey is  not async-able.

Closing it for now. Feel free to reopen if needed.


small typo in demo instruction

❓ Questions and Help
There is a small typo in demo instruction sample command line :
correct launch is done with:
python webcam.py --config-file ../configs/caffe2/e2e_mask_rcnn_R_101_FPN_1x_caffe2.yaml --min-image-size 300 MODEL.DEVICE cpu
and not like written in https://github.com/facebookresearch/maskrcnn-benchmark with :
python webcam.py --config-file ../configs/caffe2/e2e_mask_rcnn_R_101_FPN_1x_caffe2.py --min-image-size 300 MODEL.DEVICE cpu
Thanks for such amazing performance !

Oh, thanks for catching that up, it took me some time to spot the difference :-)
Could you please send a PR fixing the instructions?

Fixed via https://github.com/facebookresearch/maskrcnn-benchmark/pull/20


Bump versions to 0.8.3 (and fix some clippy complaints)

I'll cut the releases after this lands. @dbr is there any reason to think this might have the same issues as #631?

Maybe stating the obvious, but there's a bunch of breaking changes in main since the 0.8 release, so the 0.8.3 release will need to come from a branch rather than merging this!
I've slightly lost track of everything, but I did have a branch set up for this which I think is still good to use:
https://github.com/imgui-rs/imgui-rs/pull/629 (specifically the last three commits of https://github.com/imgui-rs/imgui-rs/commits/patch-v0.8
The changes should fix both the docs.rs build, and using freetype via crates.io (also backports #624 which updated the internally used parking_lot)

@dbr What happened to the authorship on https://github.com/imgui-rs/imgui-rs/commit/5207b29a56f888ee757f92d685344480be04c5cd, btw?

@dbr What happened to the authorship on 5207b29, btw?

Hmm, not sure, sorry about that! I think I may just manually copied the change over to the branch rather than properly cherry-picking the particular commit (which preserves the authored-by metadata)

any reason to not check this in the CI for every push/contribution?

We do run lots of checks on each push/PR, but there's a few complications which means they sometimes miss issues:

The clippy fixes are likely from lints added in newer releases of Rust. We pin the version of clippy used in CI to the MSRV (this is to avoid random new clippy lints causing unrelated failures, like if someone makes a PR with a tweak to some documentation, and the build fails because a newly added lint)
The docs.rs doc-builds happen in their own particular environment, so don't necessarily work exactly same as our CI, and relatedly..
Installing from a .crate file can be slightly different to building a git repo - mainly if the Cargo.toml specifies files to include/exclude (this caused a build to fail only when using the imgui .crate with the freetype feature via crates.io)

:sweat:
Of those I think that:

the pinned clippy thing is better than any alternative I'm aware of
having some kind of "docs.rs CI" would be nice but unlikely to happen (would drastically increase the requirements on doc.rs infrastructure). We already do a test cargo doc build in CI, it just doesn't catch all possible cases
we should probably look into having at least some of the CI checks run on via a .crate file instead of always using the git checkout - but, just not a high priority

Hmm, not sure, sorry about that! I think I may just manually copied the change over to the branch rather than properly cherry-picking the particular commit (which preserves the authored-by metadata)

That's a lot of work, more so than fetching from the remote (it is already merged) or even running curl https://github.com/imgui-rs/imgui-rs/commit/b5376c3fb4e40a45d537a5d4db39e0fa79df84a7.patch | git am :)

We pin the version of clippy used in CI to the MSRV

That explains it. I didn't remember these clippy lints being anything recent but the pinned version is 1.54 which is from quite a while ago :)

(this is to avoid random new clippy lints causing unrelated failures, like if someone makes a PR with a tweak to some documentation, and the build fails because a newly added lint)

That's fair, depending on the project I usually allow the contributor to fix it or - to keep every commit its own isolated change - open a separate PR to address new lints as maintainer. It can be a little hassle at times but it's a way of staying up-to-date with lints. You can also schedule a cron job in the CI which imgui already does (and GitHub recently told me it would get disabled on my imgui fork...).

The docs.rs doc-builds happen in their own particular environment, so don't necessarily work exactly same as our CI, and relatedly..

Fair enough, docs are built on nightly so if you're cross-testing that you'll end up with a lot of noise in your environment. Nightly changes a lot to be really useful for clippy lint checks though, so you don't want that (as required step) in your CI.

Installing from a .crate file can be slightly different to building a git repo - mainly if the Cargo.toml specifies files to include/exclude (this caused a build to fail only when using the imgui .crate with the freetype feature via crates.io)

Always a good idea to test this, it happened on a few occasions that a crate built fine but missed some source files, readme, licenses when packaged and uploaded to crates.io :grimacing:

the pinned clippy thing is better than any alternative I'm aware of

Perhaps bump it more often though? Unless clippy starts recommending things that MSRV-incompatible.

having some kind of "docs.rs CI" would be nice but unlikely to happen (would drastically increase the requirements on doc.rs infrastructure). We already do a test cargo doc build in CI, it just doesn't catch all possible cases

For one you're setting RUSTDOCFLAGS: -D warnings under the clippy job but cargo doc is only ran under the test job, that's not helping... Can't help/comment on the environment issue though.

we should probably look into having at least some of the CI checks run on via a .crate file instead of always using the git checkout - but, just not a high priority

Using an artifact to let people download it too, should be pretty trivial to add? With the artifact you can make sure the crate is tested on a completely clean image.

Might be worth splitting this discussion out elsewhere, but.. with the clippy CI thing it seems like there is a few different levels of "progressiveness":

Don't bother running it in CI. Just use the compiler warnings instead. Compiler will catch the important things.
Run a pinned version. Gives us a set of well-tested lints without much churn
Run latest version of clippy all the time.

I guess there's also a forth option of running latest clippy it in CI with the allow-failures option enabled for it
As mentioned, personally I think the pinned version is a good middleground - while clippy is indeed very noisy, I think there a few lints which are reasonably worthwhile.. while equally I don't think they are too vital as to require constnatly updating clippy (especially as there was a time in the last year or so where lots of new lints were added without sufficient ecosystem-wide testing - there has since been work towards reducing this, https://github.com/rust-lang/rust-clippy/issues/6623 https://github.com/rust-lang/rust-clippy/issues/7666 )
I'd also be in favour of just ditching it from CI - although given the pinned clippy doesn't really add any extra work (and we already run builds with the pinned version to ensure we don't break MSRV), I also don't see much benefit in removing it

Regarding running against a .crate file, I'm not sure even how to do run cargo against a .crate without either unpacking it and running rustc manually, or running a custom registry

Ah, I hadn't really thought much into how to actually do this - I kind of assumed you could just specify it like imgui = { path = "../whatever.crate" } or something, but, it seems not :cry:

Shouldn't the 0.8.3 patches+bump end up on top of https://github.com/imgui-rs/imgui-rs/tree/v0.8.2-patch, or have there not been any breaking changes to main since the last release? It seems our discussion above overshadowed @dbr's comment:

Maybe stating the obvious, but there's a bunch of breaking changes in main since the 0.8 release, so the 0.8.3 release will need to come from a branch rather than merging this!

Personal recommendation: why not name that branch 0.8-stable, do stable development/backporting work on that branch, and tag the actual releases? Then main can proceed pulling in breaking changes.

@thomcc @dbr Where are we at on this? Are there still plans to release 0.8.3 (without the breaking changes from main, see comments above and #629) or is the main focus now on releasing 0.9.0? Or is this frozen until the release process it written in stone via #665?

Yeah, good question. I'm inclined to just release 0.9.0, since I don't think the approach that has worked for the backports in the past has really... worked well at all.

@thomcc Thanks, that'd work for me. If you do that, please also delete stale branches (i.e. those associated with closed PRs) to prevent confusion: https://github.com/imgui-rs/imgui-rs/branches. The relevant commits are tagged anyway.

I'd agree with skipping any further 0.8.x releases - best to make v0.9 and settle on a good system for future patch releases


Buttons overlap on line wrap

v Minor issue.
Whistle Tab overlaps Sheet Music button. See screenshot.
Samsung Galaxy Tab S6 Lite Firefox latest.
It's fine in landscape
(Do you want suggestions here?)
Dave (DaveRo)

Try it now... added flex css to the button groups, should now wrap the buttons

It's OK on my tablet in portrait orientation now.
On my small phone the minimum width is set by the textarea box so that line of buttons doesn't wrap.


Add documentation for the "diagnose" utility of CmdStan

I've attached a chapter on the "diagnose" utility to add to the CmdStan guide, so that the utility is no longer documented. It's in LaTeX, but I added the ".txt" extension so that GitHub would upload it.
To include it in the guide, you'd need to add \include{diagnose} to cmdstan-guide.tex, probably just under the line \include{stansummary}.
I'd make a pull request, but that would seem to require permissions that I don't have, (i.e. git push -u origin feature/issue-578-documentation-for-diagnose-utility just gets me a 403 Forbidden error).
diagnose.tex.txt

totally awesome!
created this branch and added what you sent:
https://github.com/stan-dev/cmdstan/tree/feature/issue-578-documentation-for-diagnose-utility

closing, fixed by https://github.com/stan-dev/cmdstan/pull/579


Replace GRAMMAR_INFORMATIVE by INFORMATIVE_GRAMMAR

Because GRAMMAR_INFORMATIVE starts with GRAMMAR, there are stray ones included in the grammar spec.

I just checked the prospect Grammar page and it looks good.

@ntrel or @thewilsonator, one of you might take a quick look at this. Thanks in advance 😄

Why is this necessary or desired?

Why is this necessary or desired?

To remove blocks like this from the main D grammar:

@thewilsonator, there is a little D program that collects all blocks starting with $(GRAMMAR and adds them to the D Grammar page. The issue is that $(GRAMMAR_INFORMATIVE starts with $(GRAMMAR and is collected as well. I thought about changing the script to do a lookahead and make sure GRAMMAR isn’t followed by another word character, but honestly, I didn’t understand the code, and IMO, it would have required some non-trivial change, as the find operation is in a UFCS chain. So I changed the name of the DDoc macro instead.

Before, the GRAMMAR_INFORMATIVE made D Grammar have stray explanation grammar blocks:

With this change, using INFORMATIVE_GRAMMAR, those aren’t included anymore:

The second block of old is from here, where it is part of an explanation that only makes sense in context:

Surely you can do
-            enum grammarKey = "$(GRAMMAR";
+            enum grammarKey = "$(GRAMMAR";

then.

Surely you can do
-            enum grammarKey = "$(GRAMMAR";
+            enum grammarKey = "$(GRAMMAR";

then.

Is this a joke that I don’t get? Those two lines are exactly the same.

Or is that intended to pick up "$(GRAMMAR_SUMMARY" too?

GRAMMAR_SUMMARY is only used in one place. It’s likely that it’s being picked up, but doesn’t actually do anything when it’s picked up.

Is this a joke that I don’t get?

Nope, that was supposed to be
-            enum grammarKey = "$(GRAMMAR";
+            enum grammarKey = "$(GRAMMAR ";

my bad.

Is this a joke that I don’t get?

Nope, that was supposed to be
-            enum grammarKey = "$(GRAMMAR";
+            enum grammarKey = "$(GRAMMAR ";

my bad.

Most definitely, a space or newline could follow. Possibly also something else. I’ll keep it as-is for now. The Right Thing would be to check for the word ending, but that’s non-trivial.

@ntrel or @thewilsonator, merge?

@thewilsonator, merge?


fail with Julia last release (1.10.3)

Hi,
First of all, many thanks for this Julia Earth4All implementation,
This issue is a feedback concerning installation procedure and Julia compatible version.
As I am new to Julia, I had to install Julia at first,
I downloaded last release (1.10.3) as described in Julialang website but I got some errors during dependencies installation, based on both master branch and E4A tag 0.1.0.
I had to install Julia 1.9.0 as follows (note : macOS system) :

install last Julia version :
curl -fsSL https://install.julialang.org | sh

install specific 1.9.0 Julia version :
juliaup add 1.9.0

and then specify the version when starting Julia REPL :
juliaup +1.9.0

follow E4A procedure in the documentation (instantiate environment and so on)

Did I miss something?
Also I had to install both 1.10 and 1.9, not sure this is the best way to proceed.
Note that it worked based on E4A tag 0.1.0, but failed on main branch
As a suggestion I think this may be useful for new users (and new Julia users like me!) to mention the Julia compatible version on the README file.

Hello!
Probably a problem on our side!
Can you try to delete the Manifest.toml file from the repository and try again using Julia 1.10.3 to activate and instantiate the environment and tell me if it works for you?
Thanks for pointing this out!

Great! I will close the issue and update the repository removing it.
Thanks again!


Let pagination links use the pointer cursor

Thank you @nscyclone!  I'm going to make time this week and next to get some things done for this project, work has been hectic


Grafana: add basic API Server graphs

QPS per resource type/verb:
sum(rate(apiserver_request_count[5m])) by (resource,verb)
Latency percentiles for key resource types:
apiserver_request_latencies_summary{resource=~"gameservers|fleets|pods",verb!~"WATCH|LIST",quantile="0.5"}
Error rates:
sum(rate(apiserver_request_count{code!~"2.."}[5m])) by (code)
Perhaps with a nice drop-down to allow narrowing it down by "resource" for common resource types (fleets, gameservers, pods, etc.)

Perhaps also have a dedicated graph to update conflict rate (HTTP 409):
sum(rate(apiserver_request_count{code="409"}[5m])) by (code,resource)

There is already an API server graph do you want to improve it ?

We have a client view, this issue is about adding server-side view.

Hello @jkowalski , I can start adding these metrics.


🐛 [firestore-bigquery-export] The import script fails when run on multiple threads with millions of records.

[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs for a specific extension in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:

For general technical questions, post a question on StackOverflow
with the firebase tag.
For general Firebase discussion, use the firebase-talk
google group.
To file a bug against the Firebase Extensions platform, or for an issue affecting multiple extensions, please reach out to
Firebase support directly.

 How can we make the problem occur?
This could be a description, log/console output, etc.
Expected result
The script succeeds.
Actual result
An error has occurred on the following documents, please re-run or insert the following query documents manually... {"startAt":{"before":true,"values":[{"referenceValue":"projects/*redacted*/databases/(default)/documents/chats/nishi-chat-token/messages/026e99f6-dd02-42c0-9d14-e5cda422d768/reaction_groups/THUMBS_UP","valueType":"referenceValue"}]},"endAt":{"before":true,"values":[{"referenceValue":"projects/*redacted*/databases/(default)/documents/chats/nishi-chat-token/messages/05a5784c-2818-45cf-84f6-1e214dcc28da/reaction_groups/THUMBS_UP","valueType":"referenceValue"}]}}

Note:

The collection group reaction_groups has around 2.5 million documents.
The script succeeds when I run it on a single thread.

My initial attempt to reproduce this failed, but i had no partitioning. I'm wondering if it's related to https://github.com/firebase/extensions/issues/2092


Switch from std::collections::Hash[Map|Set] to rustc_hash

https://github.com/rust-lang-nursery/rustc-hash

This should be faster

I'd like to take this issue!

I have found the uses of HashMap in ra_analysis, ra_editor, ra_lsp_server, salsa and tools crate. Do we need to replace the usage in tools and in salsa crate though it's going to be replaced?

No, let's use std in salsa (b/c we are getting rid of it anyway) and in tools (runtime performance does not matter here, but one less dep will lead to faster compile times)


Changes to oref0-online

Replace how we get the SSID, use iwgetid instead.
Replace how we the IP of the wlan and bnep interfaces to use the ip command.

Merging to dev for testing there.


Question related to Contiv network isolation

Hey folks,
I know not a whole lot about contiv or what it provides.  One thing that would be helpful for me is isolation of networks within Kubernetes for security reasons.  Essentially I want Kubernetes to mimic bare metal networking in some way and provide eth1/eth2/eth3 (or whatever they may be called) within each of the containers without using net=host mode.  Using net=host mode is workable, but not ideal and it sure would be nice to isolate some types of traffic from others.

@sdake : http://contiv.github.io/
This has all the information about contiv networking. You may want to see various modes in which contiv networking runs. (L2, L3 / BGP , overlay etc)

@sdake k8s needs to support multiple interfaces/ip's per pod. Please see https://github.com/kubernetes/kubernetes/issues/27398

I see in the docs here:
http://contiv.github.io/documents/networking/features.html
L2 is listed as a feature.  What is missing from this list is "are separate interfaces created" or do we just get one to work with (kubernetes context)?  I suppose VLAN over one interface would work.  What I'm looking for is there a way to create multiple network interfaces in the container with netplugin?
TIA!
-steve

@sdake Can you please provide some details of your use case? As far as kubernetes goes, support for multiple interfaces is under discussion. However, based on your exact use case, we may be able to do something.

@jojimt My use case: https://review.openstack.org/#/c/392257/
In essence we are sharing all traffic over one interface now which lacks security.

I could not find a reference to multiple interfaces in the url you provided. It's possible it is hidden somewhere and in that case, it will take me some time to get through it. Could you please elaborate what you mean by "In essence we are sharing all traffic over one interface now which lacks security"? Are you referring to separation of tenant traffic from some kind of control traffic that originates/terminates in the pod?

@sdake is involved in the kolla-k8s project, which is an offshoot of the kolla project. Both projects are for deploying OpenStack services (i.e. Nova Scheduler, Neutron API, etc..) in containers. Typical OpenStack deployments contain several different networks for security and traffic isolation purposes. For example, user/admin facing Nova API endpoints belong to different networks, tenant overlay networks belong to a different network than API networks, etc.. It's preferable for several OpenStack services to include multiple interfaces. @jojimt Can you elaborate on:

However, based on your exact use case, we may be able to do something.

@sdake Looks like CNI does not support multiple interfaces per pod either: https://github.com/containernetworking/cni/issues/114

To elaborate, multiple interfaces bring with it a messy routing problem. With some restrictions, e.g.  the additional interface will be used to forward traffic only to directly connected networks, it is possible limit the complexity and do something in the interim. All of that depends on the use case being addressed.

@sdake what are your thoughts? IMO supporting add'l interfaces for local networking is a step in the right direction.

@danehans the two answers I see that commonly work are vlan on one interface and multiple interfaces directly.  We are using host networking for the dataplane at present and native kubernetes networking for the control plane.  We have the following interface types:
#api_interface: "{{ network_interface }}"
#storage_interface: "{{ network_interface }}"
#cluster_interface: "{{ network_interface }}"
#tunnel_interface: "{{ network_interface }}"
We just need network isolation on the api_interface.
We ideally want QOS on the storage interface and isolation (this is used for ceph traffic which should be second highest priority)
We ideally want QOS and isolation on the cluster interface (this is used for rabbitmq traffic which should be highest priority).
At present we are running all of these over one interface which could lead to a tcpdump security breach.
I'm not sure the best way to solve this problem in Kubernetes environments (I am not a super networking guru).  On bare metal we solve it with separate interfaces.

@jojimt apologies for not getting back to you in a timely manner.

I'm coming from reading contiv docs and capabilities. We have the requirement to deploy network functions as pods. I.e. the termination of Tunnel Protocols and forwarding traffic to a next hop as acting as a routing function. That means the we need at least to interfaces here.

We developed a CNI called Multus to support Multi-homed pod in Kubernetes, which support multi interface in a pod and support different network in a single pod. Hope this could be a best use case for the guys in this forum.

is there any progress for the multi interface use casse?

interest in this use case has ceased, although others may have interest in it.


x11-ssh-askpass window not sized correctly

Issue description
The window opened by x11-ssh-askpass is too small to display its contents.
Steps to reproduce
Run x11-ssh-askpass.
Technical details
My SSH-askpass is from nixpkgs 16.09.1803.40de598, running on NixOS with i3wm.
/nix/store/bpxr2305m7yiadjkh7g9xc3dzcqh5jmy-x11-ssh-askpass-<IP_ADDRESS>.drv
leading to
/nix/store/bs30q10v2gb9cwgdppqiv6h3lj0j3blw-x11-ssh-askpass-<IP_ADDRESS>/libexec/x11-ssh-askpass

Seems to be fixed now.


add UPTP

@weckerleben First stage of verification passed, official domain is uptp.edu.py as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@weckerleben Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Upgrade to 23.10.04

Problem

Upstream upgrade

Solution

Update manifest.toml & tests.toml

PR Status

[x] Code finished and ready to be reviewed/tested
[ ] The fix/enhancement were manually tested (if applicable)

Automatic tests
Automatic tests can be triggered on https://ci-apps-dev.yunohost.org/ after creating the PR, by commenting "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!". (N.B. : for this to work you need to be a member of the Yunohost-Apps organization)

!testme


how to freeze a single weight as it has been added

I want to make some weights in sparse matrix untrainable "after" they are added via self.add_weight.
Is there any way to do so? thanks a lot for your reply.

Just one specific weight in a layer?


Using the Experience Pearl doesn't consume the item

When using the Experience Pearl item, it gives the experience without consuming the item, allowing unlimited experience.
(Disregard the error, that's from something else)

fixed


UnrecognizedURLError

It appears the middleware does not appropriately intercept the url, the ember app attempts to boot, and routing fails.

nvm I had both a build and a serve process running and forgot to restart the serve after I restarted the build