Unable to access CUDA on WSL2 via SSH

Version
10.0.22621.819
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu-22.04
Other Software
C:\Users\twenger>nvidia-smi
Mon Nov 21 13:29:49 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 526.98       Driver Version: 526.98       CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name            TCC/WDDM | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ... WDDM  | 00000000:01:00.0  On |                  Off |
| 75%   62C    P2   301W / 450W |   8164MiB / 24564MiB |     97%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

Repro Steps
CUDA is working properly. From Windows command prompt or within WSL, nvidia-smi outputs the expected information (see above).  When I connect to the machine via SSH, however, the command nvidia-smi is not found. This is because the non-local login does not add the required WSL directories to the PATH.
$ echo $PATH
# ... includes, for example, /usr/lib/wsl/lib
$ ssh localhost
$ echo $PATH
# ... does not include, for example, /usr/lib/wsl/lib

I can now add the WSL libraries to the path and run nvidia-smi, but the CUDA driver is not detected.
$ export PATH=/usr/lib/wsl/lib:$PATH
$ nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

Failed to properly shut down NVML: Driver Not Loaded

Expected Behavior
The CUDA driver should be loaded on SSH connection.
Actual Behavior
The CUDA driver is not loaded on SSH login.
Diagnostic Logs
No response

I suspect that starting WSL locally loads some libraries and whatnot that enables the CUDA driver, and these actions are not taking place when connecting remotely. I just want to know what I have to do so that a remote connection via SSH sets up the environment to mimic a local WSL connection.

@iourit

There is an issue when nvidia-smi doesn't work when one instance is launched as Administrator and another as a non-Administrator.

I am not experiencing this. All of my sessions are launched as non-administrator.

Try to shutdown WSL and start the first nvidia-smi instance via SSH.

I have the openssh server running within WSL. If I shutdown WSL, then I won't be able to reach WSL via SSH because the SSH server won't be running.

@iourit

There is an issue when nvidia-smi doesn't work when one instance is launched as Administrator and another as a non-Administrator.

I am not experiencing this. All of my sessions are launched as non-administrator.

Try to shutdown WSL and start the first nvidia-smi instance via SSH.

I have the openssh server running within WSL. If I shutdown WSL, then I won't be able to reach WSL via SSH because the SSH server won't be running.

I meant to say "restart WSL, start the SSH server and start the first nvidia-smi instance via SSH".

You should just re-try restarting WSL. wsl --shutdown; wsl -e sudo nvidia-smi

@iourit
Thanks for the clarification and help!

I meant to say "restart WSL, start the SSH server and start the first nvidia-smi instance via SSH".

I can confirm that this works. To summarize the problem:

Start WSL.
Run nvidia-smi. The CUDA driver is found and all is well.
ssh localhost
Run nvidia-smi: command not found.
export PATH=/usr/lib/wsl/lib:$PATH
Run nvidia-smi. The CUDA driver is not found.

And the workaround:

Shutdown WSL.
Start WSL, but do not execute nvidia-smi
ssh localhost
export PATH=/usr/lib/wsl/lib:$PATH
Run nvidia-smi. The CUDA driver is found and all is well.

Interestingly, now the CUDA driver is loaded fine both locally and in subsequent SSH connections. This is the default behavior that I expected.
Although this is a workaround, this is not a practical long-term solution. A workflow might start locally and then migrate remotely. It is not practical to have to (1) shutdown the WSL server, (2) restart it, (3) login via SSH, (4) execute nvidia-smi, and (5) logout in order to ensure that the CUDA drivers are loaded for both local and remote logins.

Aha, problem solved. Thanks for the following comment @iourit

There is an issue when nvidia-smi doesn't work when one instance is launched as Administrator and another as a non-Administrator.

This actually ended up being my problem after all. WSL is started at log-on via a Task Scheduler script with "Run with highest privileges". Unchecking that box and restarting fixed my problem. Now the drivers are loaded both locally and on remote connections via SSH. Thanks for the hint!

Aha, problem solved. Thanks for the following comment @iourit

There is an issue when nvidia-smi doesn't work when one instance is launched as Administrator and another as a non-Administrator.

This actually ended up being my problem after all. WSL is started at log-on via a Task Scheduler script with "Run with highest privileges". Unchecking that box and restarting fixed my problem. Now the drivers are loaded both locally and on remote connections via SSH. Thanks for the hint!

I am glad it worked. NVIDIA is aware of this issue, but it is not clear at this point if this is the app issue or the OS issue.

This is probably because they load a bunch of extra paths when calling wsl from powershell. Idk i just add manually...


Fix areas where const naming conventions were not correctly followed

Summary
There's probably other areas where this is going on but I just wanted to get the ones that I happened to notice addressed.

@rpetrusha updated access modifiers.

Thank you so much, @alanag13, for making these additional changes. I'll merge your PR now.


Fix several DFP region creation bugs

Fix bugs with computing of addresses of flash regions for different sector-size ranges.
Fix parameter handling bug in PackTargets.populate_targets_from_pack().
Removed unhelpful _info attribute from CmsisPackDevice repr.
Include some memory regions defined in DFPs with a Pname attribute set. This is only a partial fix in that the memory regions will appear in the memory map, where a full fix would include support for core-specific memory maps.
Removed a debug log message for every target loaded from DFPs, which could cause a large spew of log messages.

/morph test


Make documentation consistent

Add "optional." to an optional parameter that was missing it.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: arm-datalake-analytics/catalog/2016-11-01/swagger/catalog.json
Before the PR: Warning(s): 42  Error(s): 4
After the PR: Warning(s): 42  Error(s): 4
Know more about AutoRest Linter Guidelines.
Send feedback and make AutoRest Linter Azure Bot smarter day by day!
Thanks for your co-operation.

 https://github.com/Azure/azure-sdk-for-python/pull/1289

No modification for AutorestCI/azure-sdk-for-ruby

 https://github.com/Azure/azure-sdk-for-node/pull/2218


TypeError [ERR_INVALID_ARG_TYPE]: The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received undefine

Cloned the repository, replaced APP_ID, and APP_CERTIFICATE with my own. The following error is shown when trying to access the /access_token endpoint: http://localhost:8080/access_token?channelName=testchannel:
TypeError [ERR_INVALID_ARG_TYPE]: The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received undefined
    at Function.from (buffer.js:330:9)
    at AccessToken.build (/Users/<omitted>/Agora-Node-TokenServer/node_modules/agora-access-token/src/AccessToken.js:31:21)
    at Function.buildTokenWithAccount (/Users/<omitted>/Agora-Node-TokenServer/node_modules/agora-access-token/src/RtcTokenBuilder.js:70:25)
    at Function.buildTokenWithUid (/Users/<omited>/Agora-Node-TokenServer/node_modules/agora-access-token/src/RtcTokenBuilder.js:40:21)
    at generateAccessToken (/Users/<omitted>/Agora-Node-TokenServer/index.js:47:33)
    at Layer.handle [as handle_request] (/Users/<omitted>/Agora-Node-TokenServer/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/<omitted>/Agora-Node-TokenServer/node_modules/express/lib/router/route.js:137:13)
    at nocache (/Users/<omitted>/Agora-Node-TokenServer/index.js:15:3)
    at Layer.handle [as handle_request] (/Users/<omitted>/Agora-Node-TokenServer/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/<omitted>/Agora-Node-TokenServer/node_modules/express/lib/router/route.js:137:13)

Hi, how did you solve this problem?

Sorry to bother you again but where in that do I put my APP_ID and APP SECRET. because this one had a separate file for that.
Thank you.

Hi. There are some typos in index.js.
You can find the correct version here.

Hi we're sorry this example had some issues before, we've rewritten the server and we hope this should be a much better experience now. Please open a new issue if there's any problem you face, if you tag me I'd be happy to help!


Draco compressed output looks bad in later versions

We have discovered that draco compression looks broken if we don't lock the combination of gltf pipeline and draco3d to 2.1.9 and 1.3.4. Versions after that looks bad and broken, e.g when compressing streamlines exported from Paraview. I have attached outputs and source data. I noted that version 1.3.6 of draco3d contains "Changed quantization defaults" and it seems that gltf pipeline 2.1.10 contains a lot of draco changes.
Command used:
gltf-pipeline -i tmp.gltf -o output.glb -d --draco.compressionLevel 4
example.zip

Try setting the position bits to 14 which was the previous default:
node bin/gltf-pipeline.js -i ~/Downloads/example/tmp.gltf -o ~/Downloads/example/tmp-new.glb -d --draco.compressionLevel 4 --draco.quantizePositionBits 14

--draco.quantizePositionBits 14 seems to fix it, thank you. Care to explain?

Draco works in part by quantizing the space into a grid and clamping positions to that grid, and the position bits determines the resolution of the grid and overall lossiness of the compression. In your model since the vertices are pretty close to one another the default value of 11 bits causes positions to collapse onto one another and look worse. It's a tradeoff of file size vs. quality.


Support for multiple languages at the same time

Hi! Thank you for your script.
Would be useful to have multiple translations in different languages with the same query :)!

Hi,
this workflow was meant to substitute for the discontinued Leo Dict Workflow.
Not sure how you would integrate such functionality and if it even makes sense for a broad range of users. Can you elaborate on how you imagine the workflow of this?!

It's the same funcionality found on this google translate workflow.


Allows parameters to be iterated and observed.

Looks good, but I don't want to play with the docs for this because I've made quite a lot of changes to another PR. So I will update docs for this after both this and that PR have been merged.

@tcr3dr I haven't updated the test or documentation, but basic testing on this functionality indicates that it works as indicated.
A few "semi interesting" things discovered.

The observer is case-sensitive - it will detect change to THR_MIN if you set THR_MIN. Since I thing (?) that ardupilot doesn't care that is a bit of a gotcha
The time taken for the callback to be called seems to be between 1 and 4 seconds after setting.
The result isn't cached. NOt a big deal, but wouldn't it make sense to do so?

Changed this to not be case-sensitive.
Not sure how to address speed issues, at least in the short term.
We now cache parameter results. In practice I expect this to be unnecessary—but semantically if the parameter is unchanged it should not fire again, so better consistent than sorry.

@tcr3dr Those changes sound great. Can you merge this, and I'll update the docs from master?

@hamishwillee Done.

These changes documented in #450


Should higher order singular integral operators be implemented as (normal) derivatives of log|y-x|?

One could then resolve the fundamental solution as A*log|y-x| + B, take the normal derivative wrt y, and this would be ∂A * log|y-x| + A * ∂(log|y-x|) + ∂B. If CauchyWeight(1) were ∂(log|y-x|), then this would be simplest. (Otherwise some other combinations and re-sampling would be required.)

CauchyWeight should always be 1/(-2piim(x-z)) to avoid confusion.  I could see adding an order to LogWeight.
Sent from my iPhone

On 1 Dec 2015, at 12:58 AM, Richard Mikael Slevinsky<EMAIL_ADDRESS>wrote:
One could then resolve the fundamental solution as A*log|y-x| + B, take the normal derivative wrt y, and this would be ∂A * log|y-x| + A * ∂(log|y-x|) + ∂B. If CauchyWeight(1) were ∂(log|y-x|), then this would be simplest. (Otherwise some other combinations and re-sampling would be required.)
—
Reply to this email directly or view it on GitHub.

LogWeight subsequently appeared in ApproxFun for logarithmic endpoint weights. It could be SingularWeight/DiagonalSingularity... and CauchyWeight a type alias.


whereis rknn-toolkit-1.7.0-docker.tar.gz??

You can get from here
baidu cloud: https://eyun.baidu.com/s/3dHiqukh
fetch code: rknn

This link is no longer valid, where can we download this old version docker(1.7.0)?

You can get from here baidu cloud: https://eyun.baidu.com/s/3dHiqukh fetch code: rknn


Several shader preprocessor parser fixes and improvements

Fixes several small issues with the shader preprocessor.

Add support for line continuation ("\" + "\n"). The official docs (https://docs.godotengine.org/en/latest/tutorials/shaders/shader_reference/shader_preprocessor.html) show a code snippet where it's supported, but it actually doesn't work because I forgot to code it. With this PR it's now supported in most places and this snippet now works:

// Multiline replacement using backslashes for continuation:
#define SAMPLE(param1, param2, param3, param4) long_function_call( \
        param1, \
        param2, \
        param3, \
        param4 \
)

Parser will now raise an error if there are extra non-whitespace characters after #else, #endif or #undef XYZ. Added consume_empty_line() for this to make the intent clear. Previously this was valid:

#endif some junk that is ignored
#undef SOMETHING gga8ha5e978 hs5sv5

Fix an #include throwing off error line numbers by one in the editor end error messages. Also fixes some other line number offset errors.
#undef no longer causes an error when used on a non-existing macro. This is similar to other preprocessors.

Technically you could say that this PR breaks compatibility, but in practice I don't think anyone will notice because anything that breaks was wrong and didn't do anything to begin with.

The changes seem fine to me, but I can't really comment on the code itself as I am pretty unfamiliar with the preprocessor.

Looks great. For some reason, the following code does not parse properly:
shader_type spatial;

vec3 long_function_call(vec3 param1)
{
 param1 += vec3(0, 0, 1);
 return param1;
}

#define SAMPLE(param1) long_function_call( \
    param1 \
)

void fragment() {
	ALBEDO = SAMPLE(vec3(1.0, 0.0, 0.0));
}

(It should be correct according to the ShaderToy)

@Chaosus
Looks like that macro argument expansion never supported very complex arguments (with commas or parentheses) to begin with, I guess you are just the first one to notice it and report the issue. I fixed that now and updated the PR.
Previously it simply used String.split(",") to split the arguments, which caused it to see three arguments as SAMPLE(vec3(1.0, 1.0, 0.0)) turned into

vec3(1.0
1.0
0.0

instead of the correct single argument vec3(1.0, 1.0, 0.0). I replaced the code with better parsing, should work properly now.

Thanks!


Update Spec with info about recommended power name to number mapping

@matrixbot: ok to test

@sbts: thank you!


New version current master

It would be great if you could create a new release (v1.0.4) from the current master that includes the changes related to phpstan

Thanks, released!


Removal of ff() and fw()

I've been using the $typefaces map for a while now in my project and created a simple enough mixin that was using ff() and fw() directly, that helped me quite a bit and noticed that recently it got removed.
Any reasons behind it? I know it was not "officially" documented, but I was wondering if there's any plan around it or if I should prepare for full removal, at the moment I've decided to just include the typography sass file directly.
Thanks for your time and the effort to support this library.

Great question. I didn't notice other people were using ff and fw, since they weren't documented officially. So, I removed them. I'd curious, what mixin did you create for your persional use?
I wanted to improve fw, and that improvement is going to come soon, but had some hiccups during the dev process, and I thought I could remove them first, since nobody was using them (I presumed, sorry!).

sorry for the late reply: so at the moment the mixin is as simple as this:
@mixin font($type, $weight: 'regular') {
  @include ff($type);
  @include fw($type, $weight);
}

which works and does what I need.
I do like the idea of having the $typefaces map, IMO it's useful, although somehow some part seems to be cryptic to me, e.g. font-size-ratio, but overall it's really nice to have.
The mixin I've got makes things a bit more easy for final dev that won't have to worry about weights or exact names for the font families to use.

$font-size-ratio was for a trial thing I was running. I have thoughts about it still, so I'm going to leave this hanging for a while until I sort out my thoughts. In the meantime, if you want the typefaces may back, mind sending in a pull request?


Griddle doesn't refresh when item is added / removed / edited during search

When a user has entered a search term in the search box and they add or remove an item to/from the results prop, or edit a record, the change doesn't show up until the user performs another search.

@emorling https://github.com/kaivi/riek


sms verification

After running timelineExporter.py i got a verification sms. How to handle it?
first run:
Traceback (most recent call last):
File "timelineExporter.py", line 11, in
tr.login()
File "../trapi/api.py", line 83, in login
self.register_new_device()
File "../trapi/api.py", line 50, in register_new_device
self.signing_key.get_verifying_key().to_string("uncompressed")
TypeError: to_string() takes 1 positional argument but 2 were given
next run:
Traceback (most recent call last):
File "timelineExporter.py", line 11, in
tr.login()
File "../trapi/api.py", line 83, in login
self.register_new_device()
File "../trapi/api.py", line 46, in register_new_device
processId = r.json()["processId"]
KeyError: 'processId'

Obviously you did a mistake. I got the same error after I entered the wrong phone number in environment.py. Check the docs if you did all steps correctly, afterwards an sms will be sent and the command line asks you to "Enter your token".


[cloud] - issues connecting via cli

What's your CLI version?
0.85.53
Description & steps to reproduce
INFO[2023-12-21T16:34:17+01:00] Loading cloud instance 02a311f602d04a72a97d007cac0a0c5b
INFO[2023-12-21T16:34:17+01:00] Successfully Loaded API Key...
INFO[2023-12-21T16:34:18+01:00] Adding new context 'cloud-02a311f602d04a72a97d007cac0a0c5b'
INFO[2023-12-21T16:34:18+01:00] Context successfully added
INFO[2023-12-21T16:34:18+01:00] Switching context...
INFO[2023-12-21T16:34:19+01:00] Upgrading currently Kurtosis Portal version '0.0.4' to '0.0.7'
INFO[2023-12-21T16:34:26+01:00] Kurtosis Portal started successfully on PID 18441
INFO[2023-12-21T16:34:26+01:00] Context set to 'cloud-02a311f602d04a72a97d007cac0a0c5b', Kurtosis engine will now be restarted
INFO[2023-12-21T16:34:26+01:00] No Kurtosis engine was found; attempting to start one...
WARN[2023-12-21T16:34:35+01:00] The context was successfully set to 'cloud-02a311f602d04a72a97d007cac0a0c5b' but Kurtosis failed to start an engine in this new context. A new engine should be started manually with 'kurtosis engine restart'. The error was:
An error occurred starting the engine with the engine existence guarantor
 --- at /root/project/cli/cli/helpers/engine_manager/engine_manager.go:202 (EngineManager.StartEngineIdempotentlyWithDefaultVersion) ---
Caused by: An error occurred guaranteeing that a Kurtosis engine is running
 --- at /root/project/cli/cli/helpers/engine_manager/engine_manager.go:362 (EngineManager.startEngineWithGuarantor) ---
Caused by: An error occurred launching the engine server container
 --- at /root/project/cli/cli/helpers/engine_manager/engine_existence_guarantor.go:196 (engineExistenceGuarantor.VisitStopped) ---
Caused by: An error occurred launching the engine server container with default version tag '0.85.53'
 --- at /root/project/engine/launcher/engine_server_launcher/engine_server_launcher.go:70 (EngineServerLauncher.LaunchWithDefaultVersion) ---
Caused by: An error occurred launching the engine server container with environment variables 'map[SERIALIZED_ARGS:{"grpcListenPortNum":9710,"logLevelStr":"info","imageVersionTag":"0.85.53","metricsUserId":"2d01bb50fd304dea5d8356b294190f28ead3452cf91cfd3c7a80b2823e00dce7","didUserAcceptSendingMetrics":false,"kurtosisBackendType":"kubernetes","kurtosisBackendConfig":{"StorageClass":"hostpath"},"onBastionHost":true,"poolSize":0,"enclaveEnvVars":"{\"AWS_ACCESS_KEY_ID\": \"AKIATYNZLDGVKKJ6INJ3\", \"AWS_SECRET_ACCESS_KEY\": \"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\", \"AWS_BUCKET_REGION\": \"us-east-1\", \"AWS_BUCKET_NAME\": \"kurtosis-cloud\", \"AWS_BUCKET_USER_FOLDER\": \"cloud-user-7a5a4c805eeb4dc0887a1192418babdd\"}","is_ci":false,"cloud_user_id":"7a5a4c805eeb4dc0887a1192418babdd","cloud_instance_id":"02a311f602d04a72a97d007cac0a0c5b"}]'
 --- at /root/project/engine/launcher/engine_server_launcher/engine_server_launcher.go:129 (EngineServerLauncher.LaunchWithCustomVersion) ---
Caused by: An error occurred creating the engine using image 'kurtosistech/engine' with tag '0.85.53'
 --- at /root/project/container-engine-lib/lib/backend_impls/metrics_reporting/metrics_reporting_kurtosis_backend.go:63 (MetricsReportingKurtosisBackend.CreateEngine) ---
Caused by: An error occurred creating engine using image 'kurtosistech/engine:0.85.53', grpc port number '9710' and environment variables 'map[SERIALIZED_ARGS:{"grpcListenPortNum":9710,"logLevelStr":"info","imageVersionTag":"0.85.53","metricsUserId":"2d01bb50fd304dea5d8356b294190f28ead3452cf91cfd3c7a80b2823e00dce7","didUserAcceptSendingMetrics":false,"kurtosisBackendType":"kubernetes","kurtosisBackendConfig":{"StorageClass":"hostpath"},"onBastionHost":true,"poolSize":0,"enclaveEnvVars":"{\"AWS_ACCESS_KEY_ID\": \"AKIATYNZLDGVKKJ6INJ3\", \"AWS_SECRET_ACCESS_KEY\": \"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\", \"AWS_BUCKET_REGION\": \"us-east-1\", \"AWS_BUCKET_NAME\": \"kurtosis-cloud\", \"AWS_BUCKET_USER_FOLDER\": \"cloud-user-7a5a4c805eeb4dc0887a1192418babdd\"}","is_ci":false,"cloud_user_id":"7a5a4c805eeb4dc0887a1192418babdd","cloud_instance_id":"02a311f602d04a72a97d007cac0a0c5b"}]'
 --- at /root/project/container-engine-lib/lib/backend_impls/kubernetes/kubernetes_kurtosis_backend/kubernetes_kurtosis_backend.go:147 (KubernetesKurtosisBackend.CreateEngine) ---
Caused by: An error occurred creating the engine pod
 --- at /root/project/container-engine-lib/lib/backend_impls/kubernetes/kubernetes_kurtosis_backend/engine_functions/create_engine.go:133 (CreateEngine) ---
Caused by: An error occurred while creating the pod with name 'kurtosis-engine-122f347a140242b7bd71da90d15867e2' in namespace 'kurtosis-engine-122f347a140242b7bd71da90d15867e2' with image 'kurtosistech/engine:0.85.53'
 --- at /root/project/container-engine-lib/lib/backend_impls/kubernetes/kubernetes_kurtosis_backend/engine_functions/create_engine.go:441 (createEnginePod) ---
Caused by: An error occurred waiting for pod 'kurtosis-engine-122f347a140242b7bd71da90d15867e2' to become available
 --- at /root/project/container-engine-lib/lib/backend_impls/kubernetes/kubernetes_manager/kubernetes_manager.go:1157 (KubernetesManager.CreatePod) ---
Caused by: Pod 'kurtosis-engine-122f347a140242b7bd71da90d15867e2' failed before availability with the following state:
>>>>>>>>>>>>>>>>>>>>>>>>>> Pod kurtosis-engine-122f347a140242b7bd71da90d15867e2 <<<<<<<<<<<<<<<<<<<<<<<<<<
Container Statuses: - kurtosis-engine-container (docker.io/kurtosistech/engine:0.85.53): TERMINATED with exit code 1 -

-------------------- Container kurtosis-engine-container Logs --------------------
2023-12-21T16:34:33.347426913+01:00 ERRO[2023-12-21T15:34:33Z][main.go:main] An error occurred when running the main function
2023-12-21T16:34:33.347455479+01:00 The remote backend config '/run/engine/remote_backend_config.json' cannot be found
2023-12-21T16:34:33.347461625+01:00  --- at /home/circleci/project/engine/server/engine/main.go:161 (runMain) ---
2023-12-21T16:34:33.347466863+01:00 Caused by: open /run/engine/remote_backend_config.json: no such file or directory

------------------ End Container kurtosis-engine-container Logs ---------------------
>>>>>>>>>>>>>>>>>>>>>>>> End Pod kurtosis-engine-122f347a140242b7bd71da90d15867e2 <<<<<<<<<<<<<<<<<<<<<<<<<<<
 --- at /root/project/container-engine-lib/lib/backend_impls/kubernetes/kubernetes_manager/kubernetes_manager.go:1861 (KubernetesManager.waitForPodAvailability) ---

Desired behavior
Be able to connect.
What is the severity of this bug?
Critical; I am blocked and Kurtosis is unusable for me because of this bug.
What area of the product does this pertain to?
Frontend: the Graphical User Interface, including the Enclave Manager

@barnabasbusa I think you may have switched your kurtosis cluster and need to switch it back. To confirm this is the case first run this command:
kurtosis cluster get

if it says docker then my hypothesis is wrong and this is not the issue. If it does not, but rather something regarding kubernetes, then switch over to k8s:
kurtosis cluster set docker

Background:
When connecting to you cloud instance, the kurtosis CLI needs to be configured to connect to a docker based backend (for now).

this has been since fixed. I was able to connect to the cluster, and update the engine.
I should be able to bump the engine without needing to connect to it via cli though.


Update cairo to the latest one

Currently we are using 2 months old compiler version. We want to use the latest one

Great! Waiting for this one! Do you guys have any ETA? Thank you so much


⚠ Bofrost.fr has degraded performance

In aea1c02, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 2695 ms

Resolved: Bofrost.fr performance has improved in 4d044e8.


Dapr dashboard doesn't show local app-only components

In what area(s)?
/area runtime
What version of Dapr?
1.5.1
Expected Behavior
I have installed Dapr using the slim option dapr init -s because I want to be very specific about what services are available to various applications I'm working on. For example, we don't have Zipkin in our Kubernetes cluster so I don't want that just "globally available" during local development.
I have an application set up with exactly one component - a file-based secret store. I also have a configuration specified to disable tracing. I'll show these in the repro below.
I am able to start my application using the dapr command line and it starts fine. It runs and I can access the app. I don't get the errors saying Zipkin is unavailable so I can tell the config is working.
However, when I do dapr dashboard and look at the components tab, I don't see my secret store component. I don't see any components. If I view the configuration tab, I see the one at ~/.dapr/config.yaml rather than the one for my app.
There are no namespaces available in the "scope" dropdown in the top right corner. "All" is the only option.
I am able to find my running application in the dashboard. The associated components and config are not there.
I expect to be able to at least find the components and config for running apps when browsing the dashboard.
Actual Behavior
The local components and configuration are not shown in the dashboard.
Steps to Reproduce the Problem

Using .NET 6:
dapr uninstall --all
dapr install -s
mkdir DaprRepro
cd DaprRepro
dotnet new web
mkdir components
echo "{}" > secrets.json

Create the file config.yml and put it in the DaprRepro folder. Make it like this:
apiVersion: dapr.io/v1alpha1
kind: Configuration
metadata:
  name: dapr-config
spec:
  tracing:
    samplingRate: "0"

In the components folder, create keystore.yml and save this:
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: key-store
spec:
  type: secretstores.local.file
  version: v1
  metadata:
    - name: secretsFile
      value: secrets.json

Now run the app.
dapr run `
  --app-id "daprrepro" `
  --app-port "4801" `
  --components-path "./components" `
  --config "./config.yml" `
  -- `
  dotnet run `
  --urls "http://localhost:4801"

If you look in dapr dashboard now, you'll see the app but no components. The config is also wrong and doesn't show the correct sample rate.
Release Note
RELEASE NOTE: FIX Local application components and configuration now show in the dashboard.

Additionally whenever I start a dapr process with a components folder with a space in the name, then the dapr application is not shown.
E.g. when I run
dapr run --app-id myapp --components-path "Local Components"
then the app "myapp" is not shown in the running dapr apps.
When I run
dapr run --app-id myapp --components-path "LocalComponents"
then the app "myapp" appears in the list with running dapr apps.
dapr --version
CLI version: 1.7.1
Runtime version: 1.7.2

any solutions now?...

For anyone else having this issue right now: The problem is with dapr cli parsing the command line. It is fixed in the main branch for dapr cli but that's not yet released.
https://github.com/dapr/cli/pull/1244
The problem appears as soon as any "flag" parameter is used when starting dapr for example "--app-ssl". As the CLI parses the command line into key value pairs this results in everything after that not getting recognized (including app-id) as it's off by one step. A workaround for me was to use another "flag" parameter like "--enable-app-health-check" to make it trip again resulting it to be back in the correct order for the following arguments.


[Bug]: different default values across visualizations

Description
Different default values in input, sliders are different in timeseries and bar chart fixed
Issues Resolved
Bug #896

Raised external PR #1111
so closing this PR


Config error

Hi I found this code very helpful for on of my project !
I was getting module not found(Tried different methods to install but was unsuccessful!) error while authenticating the credentials using dotenv/env.py.
Hence I used config method to authenticate (saved the credentials in a file called config.py).
I am getting the error as shown in attached screen shot ..

Secondly: Is there a way to mention date range to pull tweets rather than specifying the number of tweets to pull?
appreciate your quick response on this
Thank you so much !

Hi I found this code very helpful for on of my project !
I was getting module not found(Tried different methods to install but was unsuccessful!) error while authenticating the credentials using dotenv/env.py.
Hence I used config method to authenticate (saved the credentials in a file called config.py).
I am getting the error as shown in attached screen shot ..
Secondly: Is there a way to mention date range to pull tweets rather than specifying the number of tweets to pull?
appreciate your quick response on this
Thank you so much !

For the first question, have you installed the required package using pip? https://pypi.org/project/python-decouple/
And for the second question, the user_timeline method does not support since and until date parameters (and user timelines are limited to the most recent 3200 Tweets posted)**. Also, the API has been updated constantly, so maybe you can refer to this StackOverflow post for more info.
Hope that helps and apologies for the late reply!

Hi I found this code very helpful for on of my project !
I was getting module not found(Tried different methods to install but was unsuccessful!) error while authenticating the credentials using dotenv/env.py.
Hence I used config method to authenticate (saved the credentials in a file called config.py).
I am getting the error as shown in attached screen shot ..
Secondly: Is there a way to mention date range to pull tweets rather than specifying the number of tweets to pull?
appreciate your quick response on this
Thank you so much !

For the first question, have you installed the required package using pip? https://pypi.org/project/python-decouple/
And for the second question, the user_timeline method does not support since and until date parameters (and user timelines are limited to the most recent 3200 Tweets posted). Also, the API has been updated constantly, so maybe you can refer to this StackOverflow post for more info.
Hope that helps and apologies for the late reply!

Hi @mdrhmn. Yes I have installed all the package mentioned in the code and I am still getting the same error(NameError: name 'config' is not defined)...
Am I missing something ? . Can you please assist on this?

Hi @mdrhmn. Yes I have installed all the package mentioned in the code and I am still getting the same error(NameError: name 'config' is not defined)...
Am I missing something ? . Can you please assist on this?

 If you run the command pip freeze, do the list of Python packages that you installed can be seen?

Hello @mdrhmn Thank you for responding back... Not very sure about virtual environment. But when i run pip freeze I see all the packages I installed ... Is there direct way of authenticating credentials and run the entire code ? I have seen many similar codes which authenticate twitter credentials and pull the tweets(single user). However, I am unsure about using it in the above code.
Thanks again for looking into it !

Hello @mdrhmn Thank you for responding back... Not very sure about virtual environment. But when i run pip freeze I see all the packages I installed ... Is there direct way of authenticating credentials and run the entire code ? I have seen many similar codes which authenticate twitter credentials and pull the tweets(single user). However, I am unsure about using it in the above code.
Thanks again for looking into it !

Yes, you can actually directly paste the API credentials instead of using config, provided you do not push the code in any public repositories (hence why I coded mine using environment variables which is the best practice). You can refer to the following example, where you simply replace 'CONSUMER_KEY' with the string value of your API keys.
consumer_key = 'CONSUMER_KEY'...


DBZ-5117 Add mandatory database.server.id into Redis test profile

https://issues.redhat.com/browse/DBZ-5117

Thanks @vjuranek !

@vjuranek Is this needed for 1.9 too?

@jpechane not needed, in 1.9 these tests work.


Handle array and function arguments list comments

[Current coverage][cc-pull] is 99.19%

Merging [#36][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.39%

@@             master        #36   diff @@
==========================================
  Files            81         81
  Lines           497        499     +2
  Methods          78         78
  Messages          0          0
  Branches        105        105
==========================================
  Hits            495        495
- Misses            2          4     +2
  Partials          0          0

Powered by Codecov. Last updated by [58e577a...179c2e2][cc-compare]
[cc-base-branch]: https://codecov.io/gh/dmitriiabramov/esfmt/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/dmitriiabramov/esfmt/compare/58e577a1302ce662a813550c14aa8a8552f93285...179c2e2c7fc7841cf8b2fdf7e55e42a0ea9cc6c9
[cc-pull]: https://codecov.io/gh/dmitriiabramov/esfmt/pull/36?src=pr


Move entry_point flag onto entry functions for cw721-base

Makes the contract multitestable and in line with other contract structures.

Was writing this up elsewhere, but realize it's only needed here. Reason we need to do this:
Cargo uses feature unification during dependency compilation. During feature unification, cargo determines the union (set theory edition) of all the features set for a given crate and compiles one version of that library with those features enabled. The top level crate or workspace then is linked against this unified library.
From the docs:

A consequence of this is that features should be additive. That is, enabling a feature should not disable functionality.

As it is currently the case the enabling the library feature removes methods this confuses cargo and results in it being impossible to both use cw721 messages in your contract and use it's execute methods in a test.

Closed with #76


GitHub Workflow: Use new setup-godot-cpp github action from godot-cpp submodule.

Follow up of #68.
Do not merge this PR until godotengine/godot-cpp#1656 is merged.
This PR exists as a proof of concept until then, because it needs to modify the submodule version and remote to be testable.
Let's see if it runs!
Readme will be adjusted later. Not sure yet what to do with it, since it uses the 'run' action which I don't think is appropriate from this point on. Perhaps we'll just link the workflow and explain the parts separately?

Sorry for the repeated pushes... Somehow, I got stuck with git issues regarding the submodule. I simply don't understand those things...
Anyway, the PR is updated to use the latest godot-cpp commit now. It should still run through. But we still shouldn't merge because that would upgrade the repo to godot 4.x. Should merge until the change is cherry-picked to 4.3 at least.


Expression interpolation in injectGlobal

emotion version: 7.2.0
react version: 15.6.1

import { injectGlobal } from 'emotion'

const headerElements = {
  h1: 4,
  h2: 3,
  h3: 2,
  h4: 1,
}

const makeStyleString = (element, rems) => `${element} { font-size: ${rems}rem; }`
const styles = Object.keys(headerElements).map(x => makeStyleString(x, headerElements[x]))
const stylesBlock = styles.join('\n')

injectGlobal`
  ${stylesBlock}
`

I'm attempting to set up some global styles using injectGlobal: above is a very basic example.
I was expected the following block of styles:
h1 { font-size: 4rem; }
h2 { font-size: 3rem; }
h3 { font-size: 2rem; }
h4 { font-size: 1rem; }

But no styles were output.
This is trivial using preprocessors like Stylus:
headerElements = {
  h1: 4,
  h2: 3,
  h3: 2,
  h4: 1,
}

for element, rems in headerElements
  element
    font-size: rems rem

Of course, manual interpolation works just fine:
injectGlobal`
  h1 { font-size: ${headerElements.h1}; }
  h2 ...
`

...but this quickly gets tedious.
What am I missing here?!!!

For what it's worth, I'm currently using something like this:
import { css, injectGlobal } from 'emotion'

const headerElements = {
  h1: 4,
  h2: 3,
  h3: 2,
  h4: 1,
}

const styles = Object.keys(headerElements).reduce((accumulator, key) => {
  accumulator[key] = css`font-size: ${headerElements[key]}rem`
  return accumulator
}, {})

injectGlobal`
  h1 {
    ${styles.h1};
  }
  h2 {
    ${styles.h2};
  }
  h3 {
    ${styles.h3};
  }
  h4 {
    ${styles.h4};
  }
`

As expected, it generates classes for each style and also applies them to the elements:
.css-xxtg95{font-size:4rem;}
.css-hj4e5e{font-size:3rem;}
.css-1oic13s{font-size:2rem;}
.css-1h3rrcl{font-size:1rem;}
h1{font-size:4rem;}
h2{font-size:3rem;}
h3{font-size:2rem;}
h4{font-size:1rem;}

I'd just like to be able to do this in cases where I don't need a class generated for each style.

Just out of curiousity does this work?
const styles = Object.keys(headerElements).reduce((accumulator, key) => {
  accumulator[key] = css`${key} { font-size: ${headerElements[key]}rem }`
  return accumulator
}, {})

@tkh44 , thanks for the input.
Including the element in the argument to css produces the same output as my current solution. That is, it first generates css classes and then applies the styles to the elements:
.css-xxtg95{font-size:4rem;}
.css-hj4e5e{font-size:3rem;}
.css-1oic13s{font-size:2rem;}
.css-1h3rrcl{font-size:1rem;}
h1{font-size:4rem;}
h2{font-size:3rem;}
h3{font-size:2rem;}
h4{font-size:1rem;}

For styles that I'm certain I won't be applying elsewhere, your solution does save some keystrokes. What is mystifying to me – though probably quite obvious to you – is why passing even a simple string won't work, e.g.:
const styles = 'h1{font-size:4rem;}h2{font-size:3rem;}h3{font-size:2rem;}h4{font-size:1rem;}'

injectGlobal`
  ${styles}
`

...produces the styles but does NOT apply them to elements:
.css-yazff5h1{font-size:4rem;}
.css-d24qd6h2{font-size:3rem;}
.css-1k98u62h3{font-size:2rem;}
.css-ualo1th4{font-size:1rem;}

I'm trying for the opposite!
Honestly, generating the styles independently and then explicitly applying them to elements in injectGlobal isn't much extra work and the 'extra' classes don't add that much bloat. I just thought I might be missing something obvious (aside from my clear misunderstanding of how emotion works...grin).

The reason is that we compile the string styles down to objects. https://medium.com/@tkh44/emotion-7-7ef119c45869. CMD+F "How does it work?"
I'm not sure there is a good solution for injectGlobal, sorry.

Ok, thanks for the help.


any future plan to update this library?

Hi Benjamin,
any future plan to update this library?

Hi!
Sorry, there is no plan, time and hardware available for updates at the moment. You're welcome to work on it.


[Bug] Font resolving problems

Version
latest from site
Operating System
MacOS
Device
Macbook Pro 13
Browser & Version
Version 79.0.3945.88
Steps to reproduce

Download .zip from site
Unpack
Install package.json
Run

What is actually happening?
Can't resolve './fonts/nucleo-icons.eot' in 'paper-kit-react-master/src/assets/scss'

Solution
You need to edit 'src/assets/scss/paper-kit/_nucleo-icons.scss'
And add additional '../' to each path to font
Additional comments

Hello there, @Olegt0rr ,
Thank you for your interest in working with our products.
I've just made a quick test by following your exact steps:

Download .zip from site
Unpack
Install package.json
Run
On a MacBook PRO 15, and I did not have any issues.
Please make sure you have the latest version of NodeJS installed on your machine (v12.14.1 LTS - the Current version 13.6.0 always comes with new features, but also with bugs).

Best,
Manu

I have the same issue, Node 12 LTS. It was fixed like @Olegt0rr described


Recognize mismatched keys in record decryption and add private key MSB check

Motivation
We first recall the DPC's record encryption framework.
The blockchain contains encrypted records. A user, who has the viewing key, can decrypt records that belong to him/her. Note that the blockchain has everyone's records, so a user cannot decrypt most of the records on the blockchain. As a result, most of the times, the decryption result is wrong, because they are encrypted under another user's public key.
Recognize mismatched keys in record decryption. To enable this user to recognize ciphertexts that do not belong to him/her, so that the user can simply ignore the decryption result instead of trying to interpret the incorrect result, we commit to the public key in the ciphertext.
Now, each ciphertext additionally includes a commitment of the public key. The randomness of the commitment comes from the sponge (which absorbs the DH result). Now, a person who decrypts the ciphertext, performs the following steps:

given the encryption randomness rG and the private key, the person computes xrG (aka, the DH result).
the person creates a sponge and lets the sponge absorb xrG.
the person squeezes from the sponge and obtain the commitment randomness R.
given the public key commitment C and the public key xG, the person checks if C is a commitment of xG, under randomness R.
If so, the person decrypts the ciphertext, by squeezing more elements from the sponge and using them like in the counter mode. Otherwise, the person is sure that this ciphertext is not under the public key xG, and can skip it.

We use commitment rather than other cryptographic primitives for three reasons:

commitment provides hiding, so the transaction does not reveal who is the receiver (who can decrypt the record).
commitment provides binding, so even if the encryptor is malicious, it cannot commit to more than one users' public keys.
recall that the commitment is checked in the inner circuit, so therefore, we can be sure that the encryptor commits the right public key, exactly as the one used in the encryption.

This change increases the transaction sizes and number of constraints in the system, but not to a significant degree.
Add the private key MSB check. Now the ECIES Poseidon has an additional requirement about the private key: the private key must be, not just in the scalar field of the Edwards curve, but also within the capacity of the scalar field of Edwards curve. The same check is also enforced during allocation.
Test Plan
The code passes all the existing tests (except the genesis and transaction size tests, which would be fixed in another PR) after parameter resampling.
Related PRs
The fixing of the private key MSB check is a followup of #347.

It seems running the testnet1/inner_snark.sh script causes the following error now:
thread 'main' panicked at 'assertion failed: input.len() <= WINDOW_SIZE * NUM_WINDOWS', /snarkVM/gadgets/src/algorithms/crh/bhp.rs:92:9
stack backtrace:
   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::panicking::panic
   3: <snarkvm_gadgets::algorithms::crh::bhp::BHPCRHGadget<G,F,GG,_,_> as snarkvm_gadgets::traits::algorithms::crh::CRHGadget<snarkvm_algorithms::crh::bhp::BHPCRH<G,_,_>,F>>::check_evaluation_gadget_on_bits
   4: snarkvm_gadgets::traits::algorithms::crh::CRHGadget::check_evaluation_gadget
   5: snarkvm_dpc::circuits::inner_circuit::execute_inner_circuit
   6: snarkvm_algorithms::snark::groth16::generator::generate_random_parameters
   7: <snarkvm_algorithms::snark::groth16::snark::Groth16<E,V> as snarkvm_algorithms::traits::snark::SNARK>::setup
   8: inner_snark::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Let me handle it. Will get back soon.

@weikengchen it is very strange that the Transaction serialized size has regressed from 1278 to 1342 in the PR (despite the PR we just merged to master with the sizes working correctly)

Pushed a fix. Follow up on this:

Yes, the tx size and block size increases are expected, because now the ciphertext includes an additional field element that commits the public key being used for encryption.

And yes, thanks for catching that. The ToBitsBEGadget is now correctly implemented for Blake2s. Indeed, the ToBitsBEGadget for UInt8 and [UInt8] are also missing. So, this PR adds them as well.

Ready for a follow-up review. It seems that we do not need to sample the parameters again.


fix: remove default wait timeout of 500ms

Description

500ms of timeout duration is too short while waiting for ePaper display refreshes to complete. This commit will force the driver to wait only for the busy pin by default. Implementors can specify custom timeout duration if required based on their needs.
Motivation and Context

How Has This Been Tested?

Tested using SSD1681 ePaper display with resolution of 200x200.
Screenshots
Types of changes

[ ] Improvement (non-breaking change that improves a feature, code or algorithm)
[x] Bug fix (non-breaking change which fixes an issue with code or algorithm)
[ ] New feature (non-breaking change which adds functionality to code)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Config and build (change in the configuration and build system, has no impact on code or features)
[ ] Dependencies (update dependencies and changes associated, has no impact on code or features)
[ ] Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
[ ] Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

[x] My code follows the code style of this project (only if there are changes in source code).
[ ] My changes require an update to the documentation (there are changes that require the docs website to be updated).
[ ] I have updated the documentation accordingly (the changes require an update on the docs in this repo).
[x] I have read the CONTRIBUTING document.
[x] I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
[ ] I have added new tests to cover my changes.

Tested this one - image is drawn on display, still some issue with coordinates.
https://discord.com/channels/478725473862549535/1310919806072913951/1316105123507998763


Memory leak caused by HealthCheckHandler function

Hi @kimdre,
When I deployed and handled a high volume of commits to git within a time frame, I noticed that the agent memory usage increased abnormally.

`
After checking the code, I found that the HealthCheckHandler() function includes a segment that checks the Docker socket connection via the VerifySocketConnection() function. In this function, the httpClient instance is created but not closed after use.
httpClient := NewHttpClient()
When I added code to ensure the httpClient is released after use.
defer httpClient.CloseIdleConnections()
httpClient := NewHttpClient()

err = VerifySocketRead(httpClient, apiVersion)
if err != nil {
  return err
}

defer httpClient.CloseIdleConnections() //close http client

It worked. Memory usage is now stable, with no further unexpected increases.
Please check this again.

Thank you for noticing this. :)

The fix is released with v0.12.2

You're welcome. Thanks for your app, it's a great gitops CD.


[Fix][UI Next][V1.0.0-Alpha] Add direct and type  into the custom par…

Purpose of the pull request
This pull request adds direct and type into the custom parameters  in shell.
Releated issues
close #9073

Codecov Report

Merging #9081 (5276881) into dev (bf1f959) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #9081      +/-   ##
============================================
- Coverage     39.80%   39.76%   -0.04%
+ Complexity     4264     4262       -2
============================================
  Files           808      808
  Lines         32545    32545
  Branches       3646     3646
============================================
- Hits          12953    12941      -12
- Misses        18365    18378      +13
+ Partials       1227     1226       -1

Impacted Files
Coverage Δ

...er/master/processor/queue/TaskResponseService.java
49.43% <0.00%> (-13.49%)
:arrow_down:

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 bf1f959...5276881. Read the comment docs.


feat: revert react-components bundle and keep things simple

What's the problem this solves? :sweat_smile: because it does not seem simpler ^^

The rendering automation of emails wasn't working. I spent a day trying to come up with an automated solution and couldn't find one. So this pull request was born, there is no automation creating the templates, just automation pushing them to aws.

How did we generate the email previously?

It worked on a subset of the components we had. Somewhere during the iterations of the components we introduced a rule that makes the bundled code throw an exception when loading it to inline the css styles.


Update to 1.7.5

1.7.5
-----

Changes:
 - New: ForeignKeyAutocompleteAdmin, Add autocomplete for inline model admins
 - Improvement: graph_models, Rewrite modelviz module from method to class based processor
 - Improvement: db fields, make MAX_UNIQUE_QUERY_ATTEMPTS configurable per field and via settings
 - Improvement: runserver_plus, Added nopin option to disable pin
 - Fix: graph_models, Support PyDot 1.2.0 and higher
 - Fix: shell_plus, Fix that aliases from SHELL_PLUS_MODEL_ALIASES were not applied
 - Removed: validate_templatetags, remove support for pre django-1.5 style {% url %} tags
 - Cleanup: removing support for end-of-life Python 3.2
 - Docs: simplify installation instructions
 - Docs: fix example for NOTEBOOK_ARGUMENTS
 - Docs: Remove extraneous '}' characters from shell_plus docs

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Make termination more "RPC friendly"

Currently we fetch termination events from the earliest available block.
The issue is that this can sometimes lead to RPC timeouts, or even errors if the RPC doesn't support big ranges.
All such instances of "from_block=earliest" should be handled.

To address such issues and prevent their recurrence, we decided to apply a universal approach that can be utilized by future implementations as well.
We plan to add a custom filtering method to the ledger on https://github.com/valory-xyz/open-aea which will handle performing the event filtering in batches.


dry run support for managed cluster

What happened:
when i do a kubectl dry run command to the k8s cluster managed by clusternet ，there goes an error: dry run is not supported;
I think  maybe this is a problem  caused by remote-dialer.clientDial.newConnect ? or rejected by aggregated apiserver ?  the response time is very short，such as 1ms/2ms，so it probably happened  in the clusternet-hub side；
Is there a plan to support dry-run method？

What you expected to happen:
user can use  dry run command  to cluster managed  by clusternet
How to reproduce it (as minimally and precisely as possible):
1、register  a cluster by  deploy clusternet-agent；
2、make a proxy kubeconfig  to access  the cluster   through clusternet-hub；
3、 kubectl create  ns  test  --kubeconfig=proxyconfig  --dry-run=server -v=9
Anything else we need to know?:
Environment:

Clusternet version: v0.10

Kubernetes version (use kubectl version): v1.20.10

I had the same problem, and solved it with this https://github.com/yeqiugt/apiserver/commit/f256a01128ff7b68b84a829c25e4466bda1a3301, can i create a pr to fix it? @dixudx

Sure. Please go ahead. @yeqiugt

i create a pr https://github.com/clusternet/apiserver/pull/1 in clusternet/apiserver, and then, the go.mod in clusternet/clusternet also need to be edit

@yeqiugt Please help bump go.mod in clusternet/clusternet.


Group 0

Hi,
When I turn on and off group 0 all other groups keep their status.
Is this a normal behaviour? My idea when I turn on/off group 0 all other groups 1 2 3 4 will get this status.

Have you been to the Hardware setup in Domoticz to set the new "updates"
MQTT topic? If not set, they will not update.
Le mer. 29 mai 2019 à 10:15, poudenes<EMAIL_ADDRESS>a écrit :

Hi,
When I turn on and off group 0 all other groups keep their status.
Is this a normal behaviour? My idea when I turn on/off group 0 all other
groups 1 2 3 4 will get this status.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/galinette2000/espmilighthub-domoticz/issues/7?email_source=notifications&email_token=ACXIPYPVIEPYA6G4YK2UCODPXY3SFA5CNFSM4HQKGEZ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GWNJG3Q,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACXIPYJBAX5NPDNN7OQXZUTPXY3SFANCNFSM4HQKGEZQ
.

Also, there is a lag of a few seconds before update, because I wait for the
hub MQTT response for updating.
Le mer. 29 mai 2019 à 09:34, Etienne Sandré-Chardonnal <
<EMAIL_ADDRESS>a écrit :

Have you been to the Hardware setup in Domoticz to set the new "updates"
MQTT topic? If not set, they will not update.
Le mer. 29 mai 2019 à 10:15, poudenes<EMAIL_ADDRESS>a écrit :

Hi,
When I turn on and off group 0 all other groups keep their status.
Is this a normal behaviour? My idea when I turn on/off group 0 all other
groups 1 2 3 4 will get this status.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/galinette2000/espmilighthub-domoticz/issues/7?email_source=notifications&email_token=ACXIPYPVIEPYA6G4YK2UCODPXY3SFA5CNFSM4HQKGEZ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GWNJG3Q,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACXIPYJBAX5NPDNN7OQXZUTPXY3SFANCNFSM4HQKGEZQ
.

Have you been to the Hardware setup in Domoticz to set the new "updates" MQTT topic? If not set, they will not update. Le mer. 29 mai 2019 à 10:15, poudenes<EMAIL_ADDRESS>a écrit :
…

You mean the new updates with MQTT Pattern?
mqtt_topic_pattern: milight/:device_id/:device_type/:group_id
mqtt_state_topic_pattern: milight/states/:device_id/:device_type/:group_id

There is a new, third MQTT pattern parameter in v0.0.9, with "updates"
instead of "states" (as in hub MQTT settings), it is necessary for updating
bulbs from group ALL.
Le mer. 29 mai 2019 à 10:53, poudenes<EMAIL_ADDRESS>a écrit :

Have you been to the Hardware setup in Domoticz to set the new "updates"
MQTT topic? If not set, they will not update. Le mer. 29 mai 2019 à 10:15,
poudenes<EMAIL_ADDRESS>a écrit :
… <#m_-5592924997172180490_>
You mean the new updates with MQTT Pattern?
mqtt_topic_pattern: milight/:device_id/:device_type/:group_id
mqtt_state_topic_pattern: milight/states/:device_id/:device_type/:group_id
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/galinette2000/espmilighthub-domoticz/issues/7?email_source=notifications&email_token=ACXIPYKC2WLEQCUGBH5SYUTPXY76PA5CNFSM4HQKGEZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWOUSEY#issuecomment-496847123,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACXIPYITAIA2LELX47BN3JLPXY76PANCNFSM4HQKGEZQ
.

Do you have the MQTT line?
I can't find it on the site.... :)

Issue solved. Update the plugin to 0.0.9 :D


Flutter AutoComplete populate future list from API and restrict to choose only exist value

i am using AutoComplete i want to call  future list and if i input wrong value which not exist on leave focus i want to validate it also.
below is piece of code butt i want to call list from future and restrict on leave focus if input value not exist.
one more thing i want to show progress indicator while loading data

  static const List<User> _userOptions = <User>[
    User(name: 'Alice', email: 'alice@example.com'),
    User(name: 'Bob', email: 'bob@example.com'),
    User(name: 'Charlie', email: 'charlie123@gmail.com'),
  ];

  static String _displayStringForOption(User option) => option.name;

  @override
  Widget build(BuildContext context) {
    return Autocomplete<User>(
      displayStringForOption: _displayStringForOption,
      optionsBuilder: (TextEditingValue textEditingValue) {
        if (textEditingValue.text == '') {
          return const Iterable<User>.empty();
        }
        return
          _userOptions.where((User option) {
          return option
              .toString()
              .contains(textEditingValue.text.toLowerCase());
        });
      },
      onSelected: (User selection) {
        debugPrint('You just selected ${_displayStringForOption(selection)}');
      },
    );
  }
}

@immutable
class User {
  const User({
    required this.email,
    required this.name,
  });

  final String email;
  final String name;

  @override
  String toString() {
    return '$name, $email';
  }

  @override
  bool operator ==(Object other) {
    if (other.runtimeType != runtimeType) {
      return false;
    }
    return other is User && other.name == name && other.email == email;
  }

  @override
  int get hashCode => hashValues(email, name);
}

@abdulrehmananwar
From your issue description, you are looking for:

call future list and if i input wrong value which not exist on leave focus i want to validate
show progress indicator while loading data

I believe for such solutions, support channels like StackOverflow is the correct platform, so please ask the same there as you can find solutions for both.
Also, checkout this video and see if it helps https://www.youtube.com/watch?v=gDryje6oPrk
You can also search for community packages that uses AutoComplete feature which offers both the points you are looking for.
Closing from here, as the solution you are looking for in AutoComplete can be found on support channels or in community third party plugins.
If you disagree, write in comments and I'll reopen.


Set default working directory to /

runc/runtime-spec doesn't allow empty working dir
Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

LGTM

LGTM

Would this cause problems with unit tests? Go's convention is to chdir into the directory containing the running test, so that test data can be loaded relative to the test path.

When 'go test' runs a test binary, it does so from within the corresponding package's source code directory. Depending on the test, it may be necessary to do the same when invoking a generated test binary directly.

Source: https://golang.org/cmd/go/#hdr-Description_of_testing_flags

This shouldn't affect go tests. This is for the path specified in runc config.

On Apr 1, 2017, at 10:32 AM, Jonathan Yu<EMAIL_ADDRESS>wrote:
Would this cause problems with unit tests? Go's convention is to chdir into the directory containing the running test, so that test data can be loaded relative to the test path.
When 'go test' runs a test binary, it does so from within the corresponding package's source code directory. Depending on the test, it may be necessary to do the same when invoking a generated test binary directly.
Source: https://golang.org/cmd/go/#hdr-Description_of_testing_flags
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


Fix epub opening when the document is a directory with the .epub extension

Sometimes EPUB documents are directories with the .epub extension. It seems, those are valid documents and they can be opened in Books.app

Dear @outpunk! Thank you so much for contributing to this project :) I wish I had more time to keep polishing it but I am glad there are people like you! Thanks again.
After quick check the changes look legit, the only concern I have is making EPUBParsable protocol public. Is this something you would like to collaborate on? I am not that strong on keeping it internal to the module but would like to hear more on why is this exactly happening. I haven't had chance to compile the code and run against the test suit but will do that as soon as I can. Maybe it would be nice to include an additional test for your changes (unwrapping directories that end .epub) so we can cover even more cases :)
Have a great day!

@witekbobrowski I'm out of time for now, but I'll be glad to improve the PR a bit later.

This have been hanging here for a long time now... Let's merge it! Thank you for contributing.


Upmerge v1.19.x

Let's see if tests are happy.

Known failure https://github.com/grpc/grpc/issues/18477

Since there are podspec changes adding @muxi as reviewer.


Cannot add site without creating a site type before

Affected Version of Concrete CMS
9.x
Description
When using a multi site configuration we are not able to add a site without adding a new site type beforehand. (v9.0.2)
As described in the documentation in section "Create a New Site" at "step 3." the default site type should be selected when adding a site without creating a new site type before:

If you have created a Site Type before then it will give you an option to choose the Site type in which you want to add this site. If you don’t have any Site Types created then it will automatically be assigned to Default Site Type.

Also we are not able to choose the new site type when adding a new site as also stated in the quote.
Instead the new site type is automatically preset.
We want the second site to use the same site type like the default site.
How to reproduce

Try to add a new site without adding a site type beforehand
It does not work

But it should work as stated in the documentation.
Possible Solution
Workaround

Create a new site type
Create new site which will be automatically assigned to the new site type
Change "siteTypeID" in table "Sites" for the new site to "1" (the default site type)

Not sure if this is a valid workaround though, but we tested it and cannot see any sideeffects.
Additional Context
Note:
When not changing the site type to the default site type via database, we are not able to add pages to the sitemap of the new site. "Permission denied."
A user reported the same problem in the forum here, second and third post.
Our described workaround also fixes the problem mentioned in the forum post, that there are no page types.

Agreed - that's not clear. There is currently a limitation of multi-site that does require you create a site type yourself prior to creating your first multi-site site through the Dashboard (which would actually be the second site in a Concrete install.) You cannot use the Default Site Type for anything other than the first site that is created when you install Concrete.
I have updated the documentation to make this clearer.

Thanks for your explanation, that makes sense.
Thank you for updating the docs as well!

Maybe it could be useful to add a note in the docs as well, that a new multi site has no page types by default.
So adding a new page would require the user to add a page type (/index.php/dashboard/pages/types/) beforehand with a valid option to select the page path / page location via sitemap for example.


Race condition within pID get

There is a race condition when getting the process ID right away after the cluster starts. It seems .onClusterTopology() conflicts with cluster.Get().
To Reproduce

Create a localhost cluster (only one node) with default Consul
Get process ID (i.e. c.Get("abc", "hello"))
run code with race detection

Test code:

import (
	"fmt"

	"github.com/asynkron/protoactor-go/actor"
	"github.com/asynkron/protoactor-go/cluster"
	"github.com/asynkron/protoactor-go/cluster/clusterproviders/consul"
	"github.com/asynkron/protoactor-go/cluster/identitylookup/disthash"
	"github.com/asynkron/protoactor-go/remote"
)

type HelloRequest struct {
	Name string
}

func main() {
	c := startNode()

	fmt.Print("\nBoot other nodes and press Enter\n")
	pid := c.Get("abc", "hello")
	fmt.Printf("Got pid %v", pid)
	res, _ := c.Request("abc", "hello", HelloRequest{Name: "Roger"})
	fmt.Printf("Got response %v", res)

	fmt.Println()
	c.Shutdown(true)
}

func startNode() *cluster.Cluster {
	system := actor.NewActorSystem()

	provider, _ := consul.New()
	lookup := disthash.New()
	config := remote.Configure("localhost", 0)
	clusterConfig := cluster.Configure("my-cluster", provider, lookup, config)
	c := cluster.New(system, clusterConfig)
	c.StartMember()

	return c
}

Cmd to run:
go run -race main.go
Output:
WARNING: DATA RACE
Read at 0x00c000710098 by main goroutine:
  github.com/asynkron/protoactor-go/cluster/identitylookup/disthash.(*Manager).Get()
      /..../go/pkg/mod/github.com/asynkron/protoactor-go@v0.0.0-20240822202345-3c0e61ca19c9/cluster/identitylookup/disthash/manager.go:75 +0x44
  github.com/asynkron/protoactor-go/cluster/identitylookup/disthash.(*IdentityLookup).Get()

  Previous write at 0x00c000710098 by goroutine 39:
  github.com/asynkron/protoactor-go/cluster/identitylookup/disthash.(*Manager).onClusterTopology()
      /..../go/pkg/mod/github.com/asynkron/protoactor-go@v0.0.0-20240822202345-3c0e61ca19c9/cluster/identitylookup/disthash/manager.go:69 +0x464
  github.com/asynkron/protoactor-go/cluster/identitylookup/disthash.(*Manager).Start.func2()

Env:
MacOS Monterey v12.7.6
MacBook Pro mid 2015
Go v1.23.0
Expected behavior
Process ID creation or retrieval should not lead to race conditions to avoid data inconsistency.

Do you have any thoughts or updates? I did not dive deep in the code, but I suppose we must sync rdv, before retrieval if an async getter is used, i.e.
pm.rdv = clustering.NewRendezvous() -> 	ownerAddress := pm.rdv.GetByClusterIdentity(identity)
BTW: I noticed that the last commit was quite a time ago, and I wanted to check if the project is still actively maintained.


integrate with OpenZeppelin Relay

Review notes
This is a massive PR for which I'm very sorry. Some notes and motivation below.
Database schema
Marcin is working on bigger schema changes so I wanted to keep mine to minimum. mined_in_block is incorrect for OZ (we don't know block numbers) so I renamed it to transaction_id. status is needed to retry transactions safely (without causing duplicates).
Reorgs
We no longer care about reorgs. Reorg handling should be "outsourced" to OZ Relay. As such, I removed "retrigger_stale_identities" part of the ethereum subscriber, and removed simulate_eth_reorg integration test (impossible to test with OZ).
Split into read and write providers
"Ethereum" module has been split into two parts: read & write (further split into dev version and OZ version). read + write_dev should represent the old provider stack without any changes (except for moving the code around).
To do

[x] don't retry transactions that OZ already knows about
[x] remove tx-sitter module
[x] set much longer validUntil field
[x] SIGTERM works while mining
[x] set MaybeSubmitted status when calling OZ API, and Finished when mined.
[x] proper feature flags
[x] code cleanup

Deployment

Create production OZ Defender account & provide keys in ENV vars
Change owner (manager) of the production contract
Switch to OZ provider (--features oz-provider)

Codecov Report

Merging #357 (5806061) into main (eb42564) will decrease coverage by 4.11%.
The diff coverage is 45.66%.

:exclamation: Current head 5806061 differs from pull request most recent head 1f65a96. Consider uploading reports for the commit 1f65a96 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@            Coverage Diff             @@
##             main     #357      +/-   ##
==========================================
- Coverage   44.85%   40.75%   -4.11%
==========================================
  Files          23       27       +4
  Lines        6064     6677     +613
==========================================
+ Hits         2720     2721       +1
- Misses       3344     3956     +612

Flag
Coverage Δ

test
40.75% <45.66%> (-4.11%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/app.rs
48.03% <ø> (+0.46%)
:arrow_up:

src/ethereum/read/rpc_logger.rs
100.00% <ø> (ø)

src/ethereum/read/transport.rs
50.00% <ø> (ø)

src/ethereum/write_dev/estimator.rs
68.25% <0.00%> (ø)

src/ethereum/write_dev/gas_oracle_logger.rs
96.87% <ø> (ø)

src/ethereum/write_dev/min_gas_fees.rs
95.83% <ø> (ø)

src/ethereum/write_oz/mod.rs
0.00% <0.00%> (ø)

src/ethereum/write_oz/openzeppelin.rs
0.00% <0.00%> (ø)

src/lib.rs
41.63% <ø> (ø)

src/identity_committer.rs
59.49% <20.00%> (+1.26%)
:arrow_up:

... and 20 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 eb42564...1f65a96. Read the comment docs.

Lint errors to be fixed by: https://github.com/worldcoin/signup-sequencer/pull/367

@kustosz or anyone: "I reeeeeally want to believe this works." - if you have any ideas how to provide automated tests (or anything that would increase our confidence in this), please please let me know.
OZ Relay doesn't work with your local chain, and E2E tests with sending transactions to Polygon Mumbai uses gas that is very slow to top up...


python3.pkgs.umap-learn: 0.5.2 -> unstable-2022-04-11 [fixes build]

Description of changes

Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Cherry-picking commits has been considered however the history of the project is not so clean, so it was messy to get those fixes.

Looks like the issue has been addressed already.


Nihdev 465 update rebuild metadata dag for soft assays

Two changes here:

Change how the assaytype invocation works such that the request to the assay classifier and the assertion are not coupled
Create a new DAG that takes a list of uuids that can be either primary or processed and spawns the appropriate DAG for that primary or processed dataset.

@sunset666 - let me know what you think about moving the rebuild_metadata in this direction. I have no clue whether this will work or not but would like to test it on devel if you feel that this is the path we want to take moving forward.


Incorrect Data Factory functions

There's a table that states there's a function called 'AddMonths' which is not available in ADF

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 963b81d6-a8d3-eee7-d47c-a8945bc4fc8b
Version Independent ID: d9eb8ed4-0773-1e82-296f-d2cd0ce0d402
Content: Data Factory Functions and System Variables - Azure Data Factory
Content Source: articles/data-factory/v1/data-factory-functions-variables.md
Service: data-factory
Sub-service: v1
GitHub Login: @dcstwh
Microsoft Alias: weetok

@ricardoventagium
Thanks for your feedback! We will investigate and update as appropriate.


ReplyError: ERR Error running script (call to f_9681e2eb0f886df26fa948812dbd55b6263256c4): @user_script:157: user_script:157: too many results to unpack

Versions
redis<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>I'm getting the following error when running a limiter under heavy load without highWater config set:
{
  "command": {
    "name": "evalsha",
    "args": [
      "9681e2eb0f886df26fa948812dbd55b6263256c4",
      "8",
      "b_my-limiter_settings",
      "b_my-limiter_job_weights",
      "b_my-limiter_job_expirations",
      "b_my-limiter_job_clients",
      "b_my-limiter_client_running",
      "b_my-limiter_client_num_queued",
      "b_my-limiter_client_last_registered",
      "b_my-limiter_client_last_seen",
      "1584463898439",
      "pakqh4wntyn",
      "0",
      "2.19.5",
      "maxConcurrent",
      "5",
      "minTime",
      "250",
      "highWater",
      "",
      "strategy",
      "1",
      "penalty",
      "",
      "reservoir",
      "40",
      "reservoirRefreshInterval",
      "",
      "reservoirRefreshAmount",
      "",
      "reservoirIncreaseInterval",
      "1000",
      "reservoirIncreaseAmount",
      "2",
      "reservoirIncreaseMaximum",
      "40",
      "id",
      "my-limiter",
      "version",
      "2.19.5",
      "groupTimeout",
      "",
      "clientTimeout",
      "10000"
    ]
  },
  "msg": "Unhandled Promise Rejection",
  "stack": "ReplyError: ERR Error running script (call to f_9681e2eb0f886df26fa948812dbd55b6263256c4): @user_script:157: user_script:157: too many results to unpack \n    at parseError (/app/server/node_modules/redis-parser/lib/parser.js:179:12)\n    at parseType (/app/server/node_modules/redis-parser/lib/parser.js:302:14)",
  "type": "Error"
}

^ I am getting this same exact error too

same

FYI I think this can happen if you don't set a timeout on your limiters. We create limiters in AWS Lambda and eventually ran into this because the limiters never expired.


[ODS-4252] Upgrade Load Tools Project to netcore 3.1

In general the tests where we are using .Result as a suffix should be converted to async Task as the type from void.

Still getting errors when I run the application, in this case I am running the BulkLoadClient using the statemet Initialize-MinimalTemplate -samplePath ..\Ed-Fi-Standard\ -noExtensions -noValidation


MM-32421: categorize incident channel when a new incident member joins

Summary
See issue description for details
Ticket Link
Fixes: https://github.com/mattermost/mattermost-server/issues/17318
JIRA: https://mattermost.atlassian.net/browse/MM-32421
Checklist

[x] Initiate discussion of create/update incident sidebar category
[x] Create PR to expose API endpoint in the plugin RPC interface for mattermost-server => PR
[x] Create PR to expose API endpoint in the plugin RPC interface for mattermost-plugin-api
[x] Unit tests updated
[ ] E2E tests

Hello @madhavhugar,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Hi @madhavhugar, we merged your mattermost-server PR last Friday. Can we help you in any way to continue the work on this?

Most of the conflicts here look to be related to my generalize terminology PR. @madhavhugar, if it's ok with you, I'd love to help here by porting your changes over and pushing an update to your branch. Any objections?

@lieut-data that would be great thank you, feel free to push updates to the branch

@madhavhugar & @agarciamontoro, I've resolved the merge conflicts, and made two additional changes:

Tweaked the category to be Playbook Runs and the settings text to read Add the channel to a sidebar category
Changed the business logic to create channel, then run, then add members, so that the logic works for the reporter as well (previously, the channel's hook would fire before it was known to be a run, and the categorization would be skipped)

Really excited to see this merged!

/update-branch

@agarciamontoro and @lieut-data
I am facing problems running cypress tests on my system. I am unable to effectively debug the error happening in the ci environment, not sure if this was related to my changes
Would appreciate it if you guys could take a look :)

This one is on me, @madhavhugar -- we've had some flakiness in our Cypress e2e tests in the past few weeks, and our versions is fairly old. I have a PR to upgrade Cypress pending that fixes a few other things.
I'll own figuring out what's going on with your PR here :)

Hah, this one was /actually/ my part, having "fixed" the playbook automation to now allow the reporter and owner users to show up as events in the timeline. I've pushed a change that should wrap things up :)

I've tested this locally and it looked good -- @agarciamontoro, did you want to take a second look?


Revert "Fix bug in locality LB normalization (#12532)"

This reverts commit 3e184f3fa3a18d314824b8e5b12289822c41adb8.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: duderino
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
If they are not already assigned, you can assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/pkg/networking/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
549aa68d7d6f60ff85874e47c03283257096cb42
link
/test istio-integ-k8s-tests

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

@duderino: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
549aa68d7d6f60ff85874e47c03283257096cb42
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
549aa68d7d6f60ff85874e47c03283257096cb42
link
/test istio-pilot-multicluster-e2e

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


Version number in source code on main not updated to v0.14.1.

ReleaseProcess.md specifies updating the source code on main with the latest release number. For the v0.14.1 this step was skipped (sources on main still on 0.14.0).

Since release of 0.14.1 required cherry-pick of some fixes from main --> release\0.14 branch, and there were some more fixes in main present at that time that were not cherry-picked to the release branch, both the branches had effectively "diverged" in terms of the code base. In such a case, should we still be tagging main with 0.14.1?

Yes, main should always be updated to the latest release version. Release branching diverging is absolutely normal.

#3357


Added npm shrinkwrap file

why do we need that?

Instructions for regenerating the shrinkwrap file -
After altering the package.json and changing version

have npm in path
cd activemq-artemis/artemis-website
npm cache clean; rm -rf ./node_modules/ ./node npm-shrinkwrap.json
npm install --save-dev
npm shrinkwrap --dev

the new npm-shrinkwrap.json should be written

Can you add some information on the hacking guide? in specific how to upgrade the gitbook and generate this file?

Have update the hacking guide now


Issue#35: check if the title in GuaranteedAnalysis is minimal

Adding a Boolean field to the GuaranteedAnalysis class to check if the title has minimum, minimal, etc in it.
Issue #35

Please rebase on main and update the tests.

Done


How to use configs\sana_config\512ms\Sana_600M_img512.yaml

The following goes out of memory on 15.9 GB
configs\sana_config\512ms\Sana_1600M_img512.yaml --model_path Efficient-Large-Model\Sana_1600M_512px\checkpoints\Sana_1600M_512px.pth

Hardware requirement
9GB VRAM is required for 0.6B model and 12GB VRAM for 1.6B model.

What GPU are you using? There maybe misaligned here. Besides, the safe guard google/shieldgemma-2b will occupy more GPU memory which is not part of Sana, if you are using app/app_sana.py, refer to: https://github.com/NVlabs/Sana/blob/82ebd2706879b9725d2af903601a64c0e38bfed5/app/app_sana.py#L198.

Thank you @lawrence-cj , Appreciate yours and your team work on releasing this model for us.
I commented the safety checker code and it's fixed.

@lawrence-cj can we remove safety checker to reduce vram
so this model uses least vram?
ShieldGemma-2B ?
which model you recommend for least VRAM?


Support id as string

should we?

@devlucky/kakapo-core

Yes, that's why I suggested https://github.com/devlucky/Kakapo.js/issues/24.
And basically allow the user to specify the type of id (we can go with autoincrement as default behaviour)

I would say that Int will be the default and Storable will use the current implementation (Int). Then We can create a simple protocol CustomStorable or StringStorable or whatever
that has a default implementation that convert the Int to String and add a computed property:
var id: String {
    get {
       return String(id) // the Int id
    }
}

Unfortunately we might need special handling in the Serializer to avoid using the Int in the JSON so maybe it should be the other way around

@devlucky/swift-core let's discuss before deciding if it should be in the Milestone... looks like we are not sure if we want this (cc/ @zzarcon )


Replace "data-val-" on TextBoxFor not working

What I am trying to achieve is to replace the default error message with a database driven error message.  I created this same method to make all of my text, labels, static text, etc dynamic and it all works great.  When I try to use the .Data() or .HtmlAttributes() it will not overwrite the data-val- objects.  Model["validation.name.required"] translates to "Name is required." instead of "The Name field is required."
You can recreate it this way:
This works using standard TextBoxFor -
Html.TextBoxFor(x => x.Name, new { data_val_required = Model["validation.name.required"], @class="form-control" }), Html.ValidationMessageFor(x => x.Name)
Output:
<input name="Name" class="form-control" id="Name" type="text" value="" data-val-required="Name is required." data-val="true" data-val-length-max="50" data-val-length="The field Name must be a string with a maximum length of 50.">
This does not work -
@:@form.FormGroup().TextBoxFor(x => x.Name).Data(new { val_required = Model["validation.Name.required"]}).Placeholder(Model["placeholder.Name"]).ShowValidationMessage(true).Label().LabelText(Model["label.Name"])
Nor does this -
@:@form.FormGroup().TextBoxFor(x => x.Name).HtmlAttributes(new { data_val_required = Model["validation.Name.required"]}).Placeholder(Model["placeholder.Name"]).ShowValidationMessage(true).Label().LabelText(Model["label.Name"])
Output for both that do not work is the same:
<input name="Name" class="form-control input-validation-error" id="Name" type="text" placeholder="Enter your name, please" value="" data-val-required="The Name field is required." data-val="true" data-val-length-max="50" data-val-length="The field Name must be a string with a maximum length of 50.">

This should be fixed. Please get latest and let me know if it worked fine for you.

Works as expected now.  Thanks for the insanely fast fix and update as usual! =D


Updated versions

Hi,
Take a look at this 2 and let me know what you think.
https://github.com/EaDesgin/magento2-pdf-generator2
https://github.com/EaDesgin/magento2-mobiledetect
Thanks,

Hi there,
thanks for your contribution. The modules you mentioned look great. Please give me some time to review them and add them to the list! I might apply some minor PR's.
Greetings David

Hey, I just added your Extension! Thanks again for contributing.


Enable UndefinedBehaviorSanitizer and rename "asan" build to "sanitized"

Hmmm, this is taking way too long. I may just have to run this locally from time to time.


[Request] More customizable props

Thanks for this great library, it helped me a lot when I am trying to implement a screen.
But it could be more convenient if we can add more customizable props. At this moment I want to style the search box inside the Dropdown ( placeholder & input style, custom search & close icon... ).
Hope to hear from you soon.

Thank you!
I will add props for input search.

Wow...thanks for quick response. I will check it right now

I believe it would be great if you included a select all button in the multi select dropdown.


[ART-3634] Numerically sort OCP versions for setting symlinks

set_client_latest must run in order (from lower releases to higher) ... and that stopped happening since 4.10, because it is not sorting the versions properly.
def ocp4Versions = ["4.10", "4.9", "4.8", "4.7", "4.6"]

ocp4Versions.sort(false)
=> [4.10, 4.6, 4.7, 4.8, 4.9]

ocp4Versions.sort {
  def _, minor = it.tokenize(".")
  minor
}
=> [4.6, 4.7, 4.8, 4.9, 4.10]

/lgtm


Uncaught Error: EPERM: operation not permitted, lstat '~/Desktop\New folder'

[Enter steps to reproduce:]

...
...

Atom: 1.47.0 x64
Electron: 5.0.13
OS: Microsoft Windows 10 Home
Thrown From: Atom Core
Stack Trace
Uncaught Error: EPERM: operation not permitted, lstat 'C:\Users\roco_\Desktop\New folder'
At fs.js:122

Error: EPERM: operation not permitted, lstat 'C:\Users\roco_\Desktop\New folder'
    at Proxy.realpathSync (fs.js:1512:7)
    at Proxy.fs.realpathSync (electron/js2c/asar.js:300:40)
    at ~/AppData/Local/atom/app-1.47.0/resources/app/static/<embedded>:11:813938
    at Array.map (<anonymous>)
    at Object.startTask (~/AppData/Local/atom/app-1.47.0/resources/app/static/<embedded>:11:813929)
    at Object.startLoadPathsTask (~/AppData/Local/atom/app-1.47.0/resources/app/static/<embedded>:11:189147)
    at ~/AppData/Local/atom/app-1.47.0/resources/app/static/<embedded>:11:187111
    at processTicksAndRejections (internal/process/task_queues.js:79:9)

Commands
     -0:33 application:open-folder (input.hidden-input)

Non-Core Packages
atom-beautify 0.33.4
atom-html-preview 0.2.6
atom-ide-ui 0.13.0
atom-ternjs 0.20.0
autoclose-html 0.23.0
csslint 1.2.0
emmet 2.4.3
kite 0.184.0
language-ejs 0.4.0
linter 2.3.1
linter-eslint 8.5.5
linter-ui-default 1.8.1
pigments 0.40.2
Sublime-Style-Column-Selection 1.7.5

Thanks for contributing!
We noticed that this looks like a duplicate of https://github.com/atom/atom/issues/19433 so you can subscribe there for updates if you'd like.   If you have specific steps to reproduce, please let us know in https://github.com/atom/atom/issues/19433.

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.

Thanks for contributing!
We noticed that this looks like a duplicate of https://github.com/atom/atom/issues/19433 so you can subscribe there for updates if you'd like.   If you have specific steps to reproduce, please let us know in https://github.com/atom/atom/issues/19433.

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


⚠ Bofrost.be has degraded performance

In 5ec7df3, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1248 ms

Resolved: Bofrost.be performance has improved in 6f10465 after 19 minutes.


Update create-new-operations-offer.md

Added link.

@v-trloc : Thanks for your contribution! The author(s) have been notified to review your proposed change. @navits09

Hi @v-trloc - This pull request was opened in the public repository. Would you submit this update in the private repo?
In the private repo, content benefits from automated validations, a content staging environment, and comprehensive PR reviews. Also, you can sign off directly in your PR (in the public repo, you can't sign off in your own PR), and many PRs qualify for auto-merge.
To edit an article in the private repo from within the documentation, after you select Edit on an article page,  add “-pr” to the repo name in the URL.
SpineEdit is a MicrosoftDocs-approved Chrome extension that opens the edit option in the private repo, if there is one and if you have access to it.
We'll close this PR. Thanks!

Related links in the internal Microsoft Docs contributor guide:
Public vs. private repos | Move a commit to a different repo (public -> private) | GitHub for content reviews
Quick reference for contributing to the docs | Make changes to a Docs article | PR review quality criteria


Honor MaxUnvailable for inplace upgrades

What this PR does / why we need it:
Hypershift nodepool controller should have additional logic to handle correctly MaxUnavaibale, which is hard coded to 1 at the moment. Added logic to honor MaxUnavailable in inplace upgrades and unit tests for the changes.
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[x] This change includes unit tests.

/ok-to-test

@raisaat are you able to convert this from draft to a normal PR?

@yuqi-zhang converted it to a normal PR

Tried to see if that fixes the CI failures. This is independent of https://github.com/openshift/hypershift/pull/1691

/test e2e-aws-nested

Ok, updated, and added this commit:
Add an annotation to pass maxUnavailable between nodepool controller to
HCCO via machineset, like we do for other nodepool configs.

The nodepool controller will take an int or percent value and convert it
to a number of nodes maxUnavailable to pass via the annotation. We
should definitely convert this to a better interface in the future, but
for now, this is the easiest way to do so.

Also, when an inplace nodepool is created, it does not create an inPlace
management spec but instead creates a replace management type, will fix
that in a future PR.

The maxUnavailable value test is covered via previous tests. We should
eventually also beef up our e2e for actual upgrade testing.

I've tested this to work with percentages, as well as default (no value)

PTAL if you get a chance @enxebre , thanks!

Updated based on comments above (except the one question)

failed to create infra: cannot tag NAT gateway EIP: InvalidElasticIpID.NotFound: The elasticIp ID 'eipalloc-048e2483d1ecee578' does not exist

/test e2e-aws

/test e2e-aws

@raisaat @yuqi-zhang Thanks! I dropped some minor comments, if we can fix them and squash commits then let's merge.

if we can fix them and squash commits then let's merge.

I can definitely squash all of my commits. Raisaat no longer works at Red Hat, which is why I took over the PR and then preserved the original commit. Would you be ok with this being 2 commits? (Raisaat's work and then the rest) or would you prefer I squash into one commit

Rebased, squashed, added a unit test, and added a comment above

/label tide/merge-method-squash
/lgtm
/approve


Add a benchmark tool for executable libraries.

Mash up the new benchmark C header and iree_hal_executable_loader_t with some command line goo to benchmark executables. Would be good for the codegen crew to use for microbenchmarks.

TODO: see about adding a .h/.c benchmark generator for calling into the executables based on their dispatch usage. May not be worth it.


Improve error message for survey-text plugin

Just helped troubleshoot a situation where the parameter for the survey-text plugin was set as question instead of questions, but the error message generated was not helpful. We should provide a better error message (and generalize this beyond this particular plugin probably!).

my $0.02: could be especially helpful for simulation-related functionality as I constantly find myself forgetting the names of the parameters. Possible error/warning messages could include:
"Argument FOO provided in trial definition but not used"
"Trial received simulation string BAR but BAR was not defined. Defaulting to DEFAULT behaviour." (warning)
"FUZ simulation string defined but not used anywhere." (warning)


updated task card UI

Changes card design
-changed color of card for better readability
-makes the font size bigger
-gives spaces to the text in card(padding)

hey @pratikagr can you attach some screenshots?

hey @pratikagr can you attach some screenshots?

@pratikagr Hey remove that hello task card from the top of listview builder and set the initial route to splashscreen.id from home_screen.dart.

done

-Height is dynamic
-font size is decreased
-what topic?


Add more field

Add push

Add shake

Add loops

Update rotation add mode rotation

It seems that some important classes have been deleted, it doesn't work.

I just added the fields above (I just updated the description), can you tell me what error you got?

and i think you can add editor to preview editor to reduce testing time

我刚刚添加了上面的字段（我刚刚更新了描述），你能告诉我你遇到了什么错误吗？

UIDOTween and SingleTween are missing.

我认为你可以将编辑器添加到预览编辑器中以减少测试时间

I tried to add this feature one year ago, but i got stuck in some problems.  In the end, i gave up. : (

i forgot commit scripts file