Results Missing

Provider: MTGJson
Search by text doesn't return all result :
Example : "text = Faerie" doesn't return "Willow Priestess" from HML.

sample good result : https://scryfall.com/search?q=o%3Afaerie


Startup script fails to handle & character in password (and possibly other fields)

Configuring a container with a password that contains the & character fails.
If my password was foobarpass&word, then the config.ini.php contained:
password = foobarpassPIWIK_MYSQL_PASSWORDword

well yeah thats actually a bug - you'll have trouble with many unescaped special chars the bash tries to interpret - you could try to escape those chars with \

this bug exists because I'm using a Environment Variable which I process with sed
sed -i "s/PIWIK_MYSQL_PASSWORD/$PIWIK_MYSQL_PASSWORD/g" /piwik/config/config.ini.php

If somebody got a better/safer Idea to replace this, it would be possible to support special characters in the password.
Meanwhile be carefull with the passwords


arch: sparc: Force 8-byte alignment for structs

This commit adds the -mfaster-structs flag for the SPARC
architecture, which forces all structs to have an 8-byte alignment.
This is a temporary workaround for the alignment-related test failure
reported in the GitHub issue zephyrproject-rtos/zephyr#48992, and
should be reverted once the root cause is identified and fixed.
Signed-off-by: Stephanos Ioannidis<EMAIL_ADDRESS>NOTE: This is a hotfix for the issue reported in #48992.

It seems our codebase really dislikes -mfaster-structs ... will need to look for another workaround.


change install dir preferences

priorities: /opt/homebrew/share then /usr/local/share then /usr/share/ramalama
Co-Authored-By: boredsquirrel<EMAIL_ADDRESS>Signed-off-by: Eric Curtin<EMAIL_ADDRESS>

I fixed your PR here @boredsquirrel
https://github.com/containers/ramalama/pull/182


Skipping optimization due to error while loading function libraries: Invalid argument

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Ubuntu 18.04 docker image
TensorFlow installed from (source or binary):
pip install tensorflow-gpu=2.0
TensorFlow version (use command below):
GIT_VERSION: v2.0.0-rc2-26-g64c3d38 VERSION: 2.0.0
Python version:
3.7.3
CUDA/cuDNN version:
CUDA: 10.0, cuDNN: <IP_ADDRESS>-1
GPU model and memory:
Tesla P100 16GB

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with: 1. TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)" 2. TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
Describe the current behavior
When training LSTMs using the tf.keras API I get a warning:
W tensorflow/core/grappler/optimizers/implementation_selector.cc:310] Skipping optimization due to error while loading function libraries: Invalid argument: Functions '__inference___backward_cudnn_lstm_with_fallback_2111_2291_specialized_for_StatefulPartitionedCall_at___inference_distributed_function_2921' and '__inference___backward_cudnn_lstm_with_fallback_2111_2291' both implement 'lstm_9ed5de36-e395-476d-91c9-2cd0a6da489a' but their signatures do not match.

Describe the expected behavior
Should probably not give any warnings
Code to reproduce the issue
import tensorflow as tf

batch_size = 16
num_batches = 4
num_timesteps = 100
num_features = 40
num_targets = 2

model = tf.keras.Sequential()
model.add(tf.keras.layers.LSTM(2, input_shape=(None, num_features), return_sequences=True))
model.compile(optimizer='adam', loss='mse')
model.summary()

X = tf.random.normal((batch_size * num_batches, num_timesteps, num_features))
y = tf.random.normal((batch_size * num_batches, num_timesteps, num_targets))

model.fit(X, y)

Other info / logs
python reproduce.py
2019-11-28 10:07:13.562280: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcuda.so.1
2019-11-28 10:07:13.988578: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:13.999849: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1618] Found device 0 with properties:
name: Tesla P100-PCIE-16GB major: 6 minor: 0 memoryClockRate(GHz): 1.3285
pciBusID: 0000:13:00.0
2019-11-28 10:07:13.999984: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.061208: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1618] Found device 1 with properties:
name: Tesla P100-PCIE-16GB major: 6 minor: 0 memoryClockRate(GHz): 1.3285
pciBusID: 0000:1b:00.0
2019-11-28 10:07:14.061465: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0
2019-11-28 10:07:14.062923: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0
2019-11-28 10:07:14.064178: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10.0
2019-11-28 10:07:14.064527: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10.0
2019-11-28 10:07:14.066268: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10.0
2019-11-28 10:07:14.067651: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10.0
2019-11-28 10:07:14.071730: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2019-11-28 10:07:14.071863: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.072508: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.073136: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.073750: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.074320: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1746] Adding visible gpu devices: 0, 1
2019-11-28 10:07:14.074596: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 AVX512F FMA
2019-11-28 10:07:14.084185: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2019-11-28 10:07:14.087023: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x5618f79346f0 executing computations on platform Host. Devices:
2019-11-28 10:07:14.087055: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): Host, Default Version
2019-11-28 10:07:14.233596: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.235446: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.237594: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x5618f7996f10 executing computations on platform CUDA. Devices:
2019-11-28 10:07:14.237621: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (0): Tesla P100-PCIE-16GB, Compute Capability 6.0
2019-11-28 10:07:14.237630: I tensorflow/compiler/xla/service/service.cc:175]   StreamExecutor device (1): Tesla P100-PCIE-16GB, Compute Capability 6.0
2019-11-28 10:07:14.237933: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.238529: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1618] Found device 0 with properties:
name: Tesla P100-PCIE-16GB major: 6 minor: 0 memoryClockRate(GHz): 1.3285
pciBusID: 0000:13:00.0
2019-11-28 10:07:14.238608: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.239161: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1618] Found device 1 with properties:
name: Tesla P100-PCIE-16GB major: 6 minor: 0 memoryClockRate(GHz): 1.3285
pciBusID: 0000:1b:00.0
2019-11-28 10:07:14.239197: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0
2019-11-28 10:07:14.239214: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10.0
2019-11-28 10:07:14.239226: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcufft.so.10.0
2019-11-28 10:07:14.239241: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcurand.so.10.0
2019-11-28 10:07:14.239257: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusolver.so.10.0
2019-11-28 10:07:14.239272: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcusparse.so.10.0
2019-11-28 10:07:14.239288: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
2019-11-28 10:07:14.239349: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.239942: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.240527: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.241117: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.241680: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1746] Adding visible gpu devices: 0, 1
2019-11-28 10:07:14.241720: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.0
2019-11-28 10:07:14.243465: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1159] Device interconnect StreamExecutor with strength 1 edge matrix:
2019-11-28 10:07:14.243489: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1165]      0 1
2019-11-28 10:07:14.243502: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1178] 0:   N N
2019-11-28 10:07:14.243514: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1178] 1:   N N
2019-11-28 10:07:14.243666: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.244276: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.244873: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.245455: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1304] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 15216 MB memory) -> physical GPU (device: 0, name: Tesla P100-PCIE-16GB, pci bus id: 0000:13:00.0, compute capability: 6.0)
2019-11-28 10:07:14.245932: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:1006] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2019-11-28 10:07:14.246534: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1304] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:1 with 15216 MB memory) -> physical GPU (device: 1, name: Tesla P100-PCIE-16GB, pci bus id: 0000:1b:00.0, compute capability: 6.0)
Model: "sequential"
_________________________________________________________________
Layer (type)                 Output Shape              Param #
=================================================================
lstm (LSTM)                  (None, None, 2)           344
=================================================================
Total params: 344
Trainable params: 344
Non-trainable params: 0
_________________________________________________________________
Train on 64 samples
2019-11-28 10:07:16.655379: W tensorflow/core/grappler/optimizers/implementation_selector.cc:310] Skipping optimization due to error while loading function libraries: Invalid argument: Functions '__inference___backward_cudnn_lstm_with_fallback_2111_2291_specialized_for_StatefulPartitionedCall_at___inference_distributed_function_2921' and '__inference___backward_cudnn_lstm_with_fallback_2111_2291' both implement 'lstm_9ed5de36-e395-476d-91c9-2cd0a6da489a' but their signatures do not match.
2019-11-28 10:07:16.787844: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudnn.so.7
64/64 [==============================] - 3s 40ms/sample - loss: 1.0611

Seems to be discussed in #30263, which is closed. Apparently because the warning can be disregarded. I still think that it should be removed, so keeping this open for now.

@torjush ,
When tried running the given code, i did not face any warnings. Please find the gist of colab.Thanks!

After carefully rereading the comments of #30263, I see that there is indeed a fix for this coming in the next release, ref: https://github.com/tensorflow/tensorflow/issues/30263#issuecomment-548053368. Closing this issue.

I met the same problem as you in version 2.0.0, is there any solution other than upgrading the version?


make build fails to build due to shortcode reference

Problem description
make build fails to build due to shortcode reference
Error: Error building site: "/tmp/hugo_cache/modules/filecache/modules/pkg/mod/github.com/pulumi/pulumi-hugo/themes/default@v0.0.0-20220318004743-dbc39a077f17/content/blog/aws-eks-managed-nodes-fargate/index.md:36:1": failed to render shortcode "tweet": failed to process shortcode: template: _internal/shortcodes/tweet.html:6:82: executing "_internal/shortcodes/tweet.html" at <index .Params 0>: error calling index: value has type int; should be string
Total in 60070 ms
Makefile:44: recipe for target 'build' failed
make: *** [build] Error 255

Affected product version(s)
master @ 09cef630a976fb68b838d7981620cc449056e816

Hey @tomweston! Quick question: Which version of Hugo are you on? There was an update to the Twitter API, and therefore an update to the shortcode, upstream. We adopted the update, which would leave the error message that you're finding there if you're on a Hugo version before 0.89.0. I bumped up to 0.92.0 and built cleanly.

Thanks @nimbinatus I was using hugo v0.86.0+extended linux/amd64 which was >= 0.81 as referenced in the README.
Updating Hugo to 0.92.0 fixed it.
Ill raise a PR to change the README to the correct version

Ah, thanks for catching that in the readme, and thanks for the PR!


Rendering broken on a mac

OSVR-RenderManager commit 29df705a6060af04bce3ffd5d4498c4759dc98b3 was overzealous in its removal of state changes.  The change apparently works on all but macs.

Fixed in pull request https://github.com/sensics/OSVR-RenderManager/pull/377 along with a number of other bugs.


serialization: remove windows-specific layers+base rootfs

The rootfs.type field previously allowed a type of layers+base to
signify that there the layers must be applied to a base image. This was
required to support windows containers in Docker initially but has since
been replaced with a more compatible mechanism. It has no relevence for
OCI.
Signed-off-by: Stephen J Day<EMAIL_ADDRESS>Closes #186.
@opencontainers/image-spec-maintainers PTAL

Tagging @jstarks for a look / FYI

LGTM

LGTM


Remove Event Hubs logic from ReactorSession. Fix NullPointerException

This mitigates the cognitive burden in the large PR: https://github.com/Azure/azure-sdk-for-java/pull/5346.

Split Event Hubs related knowledge from ReactorSession
Fix NullPointerException that occurred in CustomIOHandler
Fix NullPointerException in SessionHandler

/check-enforcer evaluate


MacOS client loses all its settings on update

SInce Client 0.31.0 When we updated to 0.32.0 and 0.33.0 all the configurations settings in the advanced settings box are lost.  You have to fill out all the fields.  Before the interface name and port were automatically filled in.  Now all the fields are just blank.

hello @jadk9000, can you clarify how did you install NetBird on your macOS peers? We extensively test each release and we can't replicate this issue.
I've tried both manual install (via package download) and via homebrew (which if you run the automated install script, will automatically choose brew as the install method, if present) and on updates between versions, settings are kept.
With this in mind, let us know how you installed the client to understand if there's something else that might be causing this behaviour on your end.

Internal
Hi Marco,
Finaly found the solution.
We had disabled Wiretrustee UG at start up to troubleshoot some other errors.  Re-enableing fixes the issue.
Thanks
Jad
From: Marco Garcês @.>
Date: Friday, 29 November 2024 at 12:02
To: netbirdio/netbird @.>
Cc: Jad Kanji @.>, Mention @.>
Subject: Re: [netbirdio/netbird] MacOS client loses all its settings on update (Issue #2949)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
hello @jadk9000https://github.com/jadk9000, can you clarify how did you install NetBird on your macOS peers? We extensively test each release and we can't replicate this issue.
I've tried both manual install (via package download) and via homebrew (which if you run the automated install script, will automatically choose brew as the install method, if present) and on updates between versions, settings are kept.
With this in mind, let us know how you installed the client to understand if there's something else that might be causing this behaviour on your end.
—
Reply to this email directly, view it on GitHubhttps://github.com/netbirdio/netbird/issues/2949#issuecomment-2507674917, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AYZTZGE6CGH3BDJBF5EQPRL2DBJT5AVCNFSM6AAAAABSNUI2T2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBXGY3TIOJRG4.
You are receiving this because you were mentioned.Message ID: @.***>


Fix behavior of Parameter set_to when entering context with current value

The Parameter.set_to method is very useful and we use it often. However, a minor annoyance is that the parameter value may not be returned when exiting the context manager, if the set_to method is created with the current value of the parameter. For example:
p = qc.Parameter("foo", set_cmd=None, get_cmd=None)
p(42)

# ... lots of code ...

with p.set_to(42):
	p(123)

p()  # expected 42 but is 123

This often happens in notebooks during long measurement sessions, where parameters are modified all over the place.
This is caused by the changes introduced in #1749, where set_to was made to do nothing if the context manager is created with the parameter's current value, in order to reduce communication to the instrument. However, I think this is unnecessary with the new cache feature.
With the changes proposed in this PR, the above code works as expected. Do you think this makes sense? This would also get rid of usage of the old get_latest method.
Another related idea that comes to mind, would be to allow "saving" the parameter
value by calling set_to() with no arguments, like this:
original_value = p()
with p.set_to():
	p(some_other_value)

assert p() == original_value

What do you think of this? It might look a bit confusing to new users, perhaps there could be a separate method with a more descriptive name, like keep_value or store or save or something similar.
@astafan8

To me it seems like
with p.set_to(42):
	p(123) <- trying to set within a set to context should raise

Should simply be an error:
As the set_to context means within this block the value of this parameter is whatever it is set to and nothing else

There could be a usecase for what you descibe but that context manager should imho be called something else

I come across such situations where the parameter is modified inside the context very often when messing around with experiments. Typically I'll have a jupyter cell with something like
with ExitStack() as stack:
    #stack.enter_context(param1.set_to(some_value1))
    stack.enter_context(param2.set_to(some_value2))
    #stack.enter_context(param3.set_to(some_value3))

    do_ndim_sweep(
        #param1,
        param2,
        param3,
        some_values
    )

I may have many lines with set_to and many different sweep parameters that I'm commenting in and out while trying to figure out why something doesn't work. Often this results in sweeping over some parameter which is also set using a context manager, but I think that should be fine. The sweep function might also temporarily alter some parameter values using more context managers (for example to calibrate something). Maybe this is slight abuse of the context manager, but at least for me it would be quite considerably less useful if the value couldn't be changed inside.
I also think it would be quite complicated to implement this behavior, if it would need to modify the set method of the parameter.

Maybe there could be another context manager, like "lock" or "freeze" that would temporarily prevent modifications to the parameter. But for me the current use case is important.

In my oppinion set_to impliezes freeze so I would much rather add a new context mananger for you use case with a better name
Making the parameter temorarily non settable is very easy you will just need to change the _settable flag on it

Thinking about it a bit more, I could come up with reasonable use cases for all four combinations of entering the context with/without changing the value and preventing/allowing it to change inside.
Maybe set_to could be extended so that it can be called without any value (same as entering with the current value), and with a kwarg freeze (maybe with the default value of True), which would prevent changing. This way we don't need four different context managers for all cases. The common feature in all of these is that the parameter value gets returned to its original value after exiting (which is not the case with the current implementation).

hey @mgunyho , we had an offline discussion with @jenshnielsen and we decided to suggest the following:

improve the behavior of set_to such that inside the context it is not possible to set the parameter to any different value - this is justified by the care about users, even when they fiddle around with code of the measurement, qcodes still should be there to prevent unnoticed mistakes - i hope you'll agree that it's easier for the user to think that inside the set_to context the value of the parameter is NOT supposed to change.
in order to enable your use case of allowing users to change the value of the "set-to" parameter, let's indeed introduce a flag - we suggest that flag to be called allow_changes that is set to False by default -- so set_to(new_value, allow_changes: bool = False) - would you agree?
the use case of only reverting the current value of the parameter can be nicely achieved via with p.set_to(p.cache()): ... - is that good enough?

Hi

it's easier for the user to think that inside the set_to context the value of the parameter is NOT supposed to change

That's fair enough, although at least we have not automatically assumed so in our use until now.

we suggest that flag to be called allow_changes

I would prefer the name freeze or lock, because it's less typing, but still quite well understandable in my opinion. But in either case the flag is a good idea, and it's ok that the default value is to not allow changes.

with p.set_to(p.cache()):

I would prefer the version with no args. This version might be hard to read if the variable name is long. Also consider the case I discussed above, with ExitStack(). Then, if I want to add a new set_to statement by duplicating an existing line, I would have to change the variable name in two places, and this can be prone to errors.
I worked a bit on implementing this functionality, and have now pushed it to this branch. Should I add those changes to this PR or create a new one? The flag is now called freeze, but I can rename it. I've also implemented the no-args version, but that can be left out if you really think that it's not good.

I would prefer the version with no args. This version might be hard to read if the variable name is long. Also consider the case I discussed above, with ExitStack(). Then, if I want to add a new set_to statement by duplicating an existing line, I would have to change the variable name in two places, and this can be prone to errors.

This is fair. Then let's take the middle ground of having a new context manager called .reset_at_exit(allow_changes=False) (the same flag is included)?

I worked a bit on implementing this functionality, and have now pushed it to this branch. Should I add those changes to this PR or create a new one?

Thank you! that's great! i think it's more convenient to use this pull-request, just push those changes to the branch that is attached to this PR (or re-target this PR to that other branch, if that's more convenient)

The flag is now called freeze, but I can rename it.

yes, please, allow_changes (it is more descriptive of what happens) :)

I've also implemented the no-args version, but that can be left out if you really think that it's not good.

yeah, with p.set_to(): it's less readable/intuitive of what is going on. So, instead of having the no-args version, let's go for another context manager - .reset_at_exit(allow_changes=True).

Alright, I'll update this branch.
For our use case, where we may want to set a parameter temporarily for the duration of a sweep, but it might be altered during the sweep to e.g. do some calibration, having two different context managers would then require having twice as many lines, which is again susceptible to typos. But maybe that's quite rare even in our case, we'll have to see.
Do you think reset_at_exit is the best possible name for the method? For a new user not familiar with the with statement, it might be unclear that something is being exited at the end of the block. How about something like keep_value?

I've updated the PR description.
Some TODOs/questions:

Are the tests extensive enough? In particular, there's no test for reset_at_exit when the parameter cache is not initialized, but I'm not sure how to clear the parameter cache.
These features should be mentioned in the documentation/example notebooks, I haven't done that yet. If you have any particular spot in mind where these could be mentioned, let me know.
Should the _original_value be set only when entering the context? Now, it is in principle possible to get some weird behavior if the parameter value is changed between creating and entering the context manager (although this is very much of a fringe case):p = qc.Parameter("foo", set_cmd=None, get_cmd=None)
p(3)
ctx = p.set_to(5)

p(123)
with ctx:
    assert p() == 5

assert p() == 3  # although someone may assume that p() == 123 here

The same goes for _parameter_was_settable.

Another small thing that came to mind: if parameter B is a delegate of A, and I enter a context where I make B not settable, it is still possible to modify the value of A and thus the value of B. But maybe that's a problem for another PR (if it's a problem at all). At first thought it feels like trying to implement something like this could be quite complicated in general for multiple nested DelegateParameters.

Do you think reset_at_exit is the best possible name for the method? For a new user not familiar with the with statement, it might be unclear that something is being exited at the end of the block. How about something like keep_value?

well, users that are "not familiar with the with statement" but are using python should take their time to get familiar with one of the most fantastic features of python - the context managers and the with statement :) next, of course reset_at_exit is likely not the best possible name, however it is very explicit in expressing the behavior that the user should expect - the value of the parameter will be reset at the exit of the context manager. the keep_value option doe snot explicitly mention that the parameter's value will be reset once the context is exited, moreover, "keep value" may confuse users to think that inside the context they should not change the value of the parameter which is opposite from your feature request, and is definitely possible with allow_changes=True. So, keep_value is not better than reset_at_exit. I don't have any other splendid ideas, so we might as well just stick with reset_at_exit?

These features should be mentioned in the documentation/example notebooks, I haven't done that yet. If you have any particular spot in mind where these could be mentioned, let me know.

great question! I think that for this PR it is good enough make sure that set_to and reset_at_exit have clear docstrings explaining the behavior and usage.

Should the _original_value be set only when entering the context? Now, it is in principle possible to get some weird behavior if the parameter value is changed between creating and entering the context manager (although this is very much of a fringe case):

I think this is a great test case! indeed, the "original_value" should be taken at the moment the context is entered, and NOT at the moment the context manager is initiated. So please feel free to add this exact test, and modify the implementation to capture the original value at the enter of the context manager.

Another small thing that came to mind: if parameter B is a delegate of A, and I enter a context where I make B not settable, it is still possible to modify the value of A and thus the value of B. But maybe that's a problem for another PR (if it's a problem at all). At first thought it feels like trying to implement something like this could be quite complicated in general for multiple nested DelegateParameters.

Again, great call! However, let's keep this for another PR, this needs a bit of thinking, and let's not pollute the discussion inside this particular PR.

I've added the changes about entering the context.
You're correct, the with statement is important, and the more people learn about it the better (although from my experience it takes a while before beginners understand its usefulness).
How about restore_at_exit? "Reset" could imply something like resetting to the initial value of the parameter.

How about restore_at_exit?

yes, that's probably better. my english is not that good so i had to google differences in meanings of the words.

Alright, to me this is now good to merge. Let me know if there's something to change.


Makefile: Add build tags for build integration target

Looks like it is missed during 589ab2cd9c0ac907dd9dd67f351c3c65c0565d32 and build_integration target failing with following.
[1/2] STEP 5/5: RUN make build_integration
GOOS=linux   go test ./test/integration/ --ldflags="-X github.com/code-ready/crc/pkg/crc/version.crcVersion=2.9.0 -X github.com/code-ready/crc/pkg/crc/version.ocpVersion=4.11.3 -X github.com/code-ready/crc/pkg/crc/version.okdVersion=4.11.0-0.okd-2022-08-20-022919 -X github.com/code-ready/crc/pkg/crc/version.podmanVersion=4.2.0 -X github.com/code-ready/crc/pkg/crc/version.commitSha=589ab2cd" -c -o out/linux-amd64/integration.test
vendor/github.com/mtrmac/gpgme/data.go:4:11: fatal error: gpgme.h: No such file or directory
 // #include <gpgme.h>
           ^~~~~~~~~
compilation terminated.

Looks like it is missed during https://github.com/code-ready/crc/commit/589ab2cd9c0ac907dd9dd67f351c3c65c0565d32 and build_integration target failing with following.

the commit id you wanted to refer to is not correct i think

Looks like it is missed during 589ab2c and build_integration target failing with following.

the commit id you wanted to refer to is not correct i think

@anjannath Ah yes, updated it.

Approved, but would like to understand what caused this 'missing' as it seems builds and tests didn't catch this.

@gbraad This target in the makefile only run during the building e2e containerize images and our build/test didn't catch it, we may add another CI targeted for same.

Ouch.
This is likely to happen again


Added JSONRPC 2.0 spec

This is a JSONRPC spec that describes the pubsub API (for its use with libjson-rpc-cpp)

I haven't figured out what the subscribe and unsubscribe methods should be mapped. What's the network payload in both cases? Is there any example of clients or of network traffic I can use? Thanks.

Hi @esteve, did it sorted or you still have any questions? Can we move this PR forward?

@akru there's still the question of how to represent subscribe and unsubscribe. Do you have example traffic of those methods?

Hi @esteve ! For subscribe it's:
{
"name": "pubsub_subscribe",
"params": {
"topic_name": "String"
},
"returns": ()
}
I have no unsubscribe method description, because it generates automatically by jsonrpsee lib.
I believe the subscribe method will open a WS connection and will call unsubscribe on connection close.


first build

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:15: avoid_noarch: noarch: python packages should be avoided
ERROR: clone/recipe/meta.yaml:40: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: clone/recipe/meta.yaml:40: missing_dev_url: The recipe is missing a dev_url
WARNING: clone/recipe/meta.yaml:40: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:40: missing_license_family: The recipe is missing the about/license_family key.
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:15: avoid_noarch: noarch: python packages should be avoided
ERROR: clone/recipe/meta.yaml:34: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: clone/recipe/meta.yaml:40: missing_license_family: The recipe is missing the about/license_family key.
WARNING: clone/recipe/meta.yaml:40: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:40: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: clone/recipe/meta.yaml:40: missing_dev_url: The recipe is missing a dev_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:15: avoid_noarch: noarch: python packages should be avoided
WARNING: clone/recipe/meta.yaml:22: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:35: missing_pip_check: For pypi packages, pip check should be present in the test commands
WARNING: clone/recipe/meta.yaml:41: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:41: missing_license_family: The recipe is missing the about/license_family key.
ERROR: clone/recipe/meta.yaml:41: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: clone/recipe/meta.yaml:41: missing_dev_url: The recipe is missing a dev_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:15: avoid_noarch: noarch: python packages should be avoided
WARNING: clone/recipe/meta.yaml:22: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:41: missing_dev_url: The recipe is missing a dev_url
ERROR: clone/recipe/meta.yaml:41: missing_documentation: The recipe is missing a doc_url or doc_source_url
WARNING: clone/recipe/meta.yaml:41: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:41: missing_license_family: The recipe is missing the about/license_family key.
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:15: avoid_noarch: noarch: python packages should be avoided
WARNING: clone/recipe/meta.yaml:22: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:42: missing_license_family: The recipe is missing the about/license_family key.
ERROR: clone/recipe/meta.yaml:42: missing_documentation: The recipe is missing a doc_url or doc_source_url
WARNING: clone/recipe/meta.yaml:42: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:42: missing_dev_url: The recipe is missing a dev_url
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:15: avoid_noarch: noarch: python packages should be avoided
ERROR: clone/recipe/meta.yaml:43: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: clone/recipe/meta.yaml:43: missing_license_family: The recipe is missing the about/license_family key.
ERROR: clone/recipe/meta.yaml:43: missing_dev_url: The recipe is missing a dev_url
WARNING: clone/recipe/meta.yaml:43: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:15: avoid_noarch: noarch: python packages should be avoided
WARNING: clone/recipe/meta.yaml:22: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
ERROR: clone/recipe/meta.yaml:43: missing_dev_url: The recipe is missing a dev_url
ERROR: clone/recipe/meta.yaml:43: missing_documentation: The recipe is missing a doc_url or doc_source_url
WARNING: clone/recipe/meta.yaml:43: missing_description: The recipe is missing a description
ERROR: clone/recipe/meta.yaml:43: missing_license_family: The recipe is missing the about/license_family key.
Errors were found


Allow posting to several channels

Allow posting to several channels by doing:
set : slack_channel_updated, %w[#deploy #deploy-production]

Also significantly reduces code in all the tasks by using a lambda.
Haven't tried it locally, just edited it on github.

Interesting. I like it. Will try to get this merged in soon.

@phallstrom awsome, fixed a syntax error and rebased. Will use it in our deployment to try it out.

No idea why the build fails. I use ruby 2.2 locally and all works. I'd try to merge #39 first and rebase this PR to get new build.

Had to tweak the implementation a bit due to some other commits that modified similar sections, but this is in place (soon to be released). Via a555c81f200b65693a995c0c50c734211c3259d7


rest api on jolnir explorer

Describe the feature request
Please add rest api on jolnir explorer

Great project

Great project

good projectors

Great project


Do not qualify <fenv.h> names that might be macros.

This fixes a build failure for GNU/Linux on powerpc, as described at https://bugzilla.redhat.com/show_bug.cgi?id=1262444
This is the same problem described at https://svn.boost.org/trac/boost/ticket/6767

Do you know if the issue https://svn.boost.org/trac/boost/ticket/11756 is also related to this one?

Is there any plan to merge this for 1.61 again ?

I thought  I merged this into develop in early november.
On Fri, Dec 18, 2015 at 8:37 AM, Damien Buhl<EMAIL_ADDRESS>wrote:

Is there any plan to merge this for 1.61 again ?
—
Reply to this email directly or view it on GitHub
https://github.com/boostorg/test/pull/88#issuecomment-165780316.

--
Gennadiy Rozental

I reverted it to maintain the scope of 1.60. Now that 1.60 is released, I merged the change to develop.

Thanks. We use the patch succesfully on top of 1.59.0 on ppc603e-poky-linux, armv7a-vfp-neon-poky-linux-gnueabi and x86_64 linux without any problem. Hope 1.61.0 will have it. :smile:


v2 Issue

While using script it will randomly not hit skill checks. Sometimes not putting any input in at all and then breaking the script further or randomly doing the skill check early (Fairly Uncommon).

Seems to be fixed


The Smooth stone slab (strata 1) you craft is not the same as the one you get back after mining it

It's not the only slab and strata variant problem with recipes but Hiracho is already aware of most of them

Already fixed as a part of #358


compilation error

Dear all, i try to compile the "light" example .
plateformio.ini is :
[env:adafruit_qtpy_esp32c3]
platform =<EMAIL_ADDRESS>board = adafruit_qtpy_esp32c3
framework = arduino
build_unflags = -std=gnu++11
build_flags = -std=gnu++17
board_build.partitions = min_spiffs.csv
imported lib matter in the directory lib/matter
compilation is working but not linking :

<EMAIL_ADDRESS>D:\WIFIPOWER\Matter\Matter/src/main.cpp:93: undefined reference to esp_matter::attribute::get_val(unsigned int*, esp_matter_attr_val_t*)'<EMAIL_ADDRESS>.pio\build\adafruit_qtpy_esp32c3\src\main.cpp.o: in function set_onoff_attribute_value(esp_matter_attr_val_t*)':
D:\WIFIPOWER\Matter\Matter/src/main.cpp:99: undefined reference to `esp_matter::attribute::update(unsigned short, unsigned long, unsigned long, esp_matter_attr_val_t*)'
collect2.exe: error: ld returned 1 exit status
[.pio\build\adafruit_qtpy_esp32c3\firmware.elf] Error 1

any advice please ?
thanks

Hi, I tested it today and can confirm same problem. I'm looking at this.

Actually, I did not look at this error correctly and I had different but quite similar error. I fixed this in 1.0.0-beta.3-branch, could you confirm if that works?

Not realy better :
Regards
Phil
De : Jakub Dybczak @.>
Envoyé : lundi 20 mars 2023 22:27
À : jakubdybczak/esp32-arduino-matter @.>
Cc : phil31 @.>; Author @.>
Objet : Re: [jakubdybczak/esp32-arduino-matter] compilation error (Issue #22)
Actually, I did not look at this error correctly and I had different but quite similar error. I fixed this in 1.0.0-beta.3-branch https://github.com/jakubdybczak/esp32-arduino-matter/tree/1.0.0-beta.3-branch , could you confirm if that works?
—
Reply to this email directly, view it on GitHub https://github.com/jakubdybczak/esp32-arduino-matter/issues/22#issuecomment-1476957376 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJOE2RRGVBR4IKZGJ7CSITW5DDQ5ANCNFSM6AAAAAAWAIS7JI .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/ACJOE2QN2HPHTAE3S5ZN7D3W5DDQ5A5CNFSM6AAAAAAWAIS7JKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSYBCKMA.gif Message ID: @.*** @.***> >

I just tried and compiled successfully light example with this config:
[env:esp32dev]
platform =<EMAIL_ADDRESS>board = adafruit_qtpy_esp32c3
board_build.mcu = esp32c3
framework = arduino
build_unflags = -std=gnu++11
build_flags = -std=gnu++17
board_build.partitions = min_spiffs.csv
lib_deps = https://github.com/jakubdybczak/esp32-arduino-matter.git#1.0.0-beta.3-branch
monitor_speed = 115200

Could you send your project so I can debug it?

Not working on my side, the only difference is that i import the matter lib directly in lib directory because i don’t have GIT on my PC.
You can download the project here : https://transfert.free.fr/thDsAIY
Thanks, regards
De : Jakub Dybczak @.>
Envoyé : mardi 21 mars 2023 08:57
À : jakubdybczak/esp32-arduino-matter @.>
Cc : phil31 @.>; Author @.>
Objet : Re: [jakubdybczak/esp32-arduino-matter] compilation error (Issue #22)
I just tried and compiled successfully light example with this config:
[env:esp32dev]
platform = @.*** @.***>
board = adafruit_qtpy_esp32c3
board_build.mcu = esp32c3
framework = arduino
build_unflags = -std=gnu++11
build_flags = -std=gnu++17
board_build.partitions = min_spiffs.csv
lib_deps = https://github.com/jakubdybczak/esp32-arduino-matter.git#1.0.0-beta.3-branch
monitor_speed = 115200
Could you send your project so I can debug it?
—
Reply to this email directly, view it on GitHub https://github.com/jakubdybczak/esp32-arduino-matter/issues/22#issuecomment-1477406094 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJOE2XA5IOZCTZZRS63EGLW5FNOHANCNFSM6AAAAAAWAIS7JI .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/ACJOE2RXR7ATZCU3AADP6SDW5FNOHA5CNFSM6AAAAAAWAIS7JKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSYB5WY4.gif Message ID: @.*** @.***> >

I will look at this on weekend

The problem is with your project structure, you copied src folder from this library to lib/matter folder. Proper structure is
.
Tip: you can go to lib folder, clear the stuff here and type git clone --depth 1 --branch 1.0.0-beta.3-branch https://github.com/jakubdybczak/esp32-arduino-matter and that will be enough ;)

Thanks Jakub, regards
De : Jakub Dybczak @.>
Envoyé : samedi 25 mars 2023 12:02
À : jakubdybczak/esp32-arduino-matter @.>
Cc : phil31 @.>; Author @.>
Objet : Re: [jakubdybczak/esp32-arduino-matter] compilation error (Issue #22)
The problem is with your project structure, you copied src folder from this library to lib/matter folder. Proper structure is
https://user-images.githubusercontent.com/37028087/227713272-a77c71f3-fa60-429b-9b99-94efa5833834.png .
Tip: you can go to lib folder, clear the stuff here and type git clone --depth 1 --branch 1.0.0-beta.3-branch https://github.com/jakubdybczak/esp32-arduino-matter and that will be enough ;)
—
Reply to this email directly, view it on GitHub https://github.com/jakubdybczak/esp32-arduino-matter/issues/22#issuecomment-1483795404 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ACJOE2WETGRCLVW6FRNCUZTW53GEDANCNFSM6AAAAAAWAIS7JI .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/ACJOE2Q3PUJ4OFQQCAIHN4DW53GEDA5CNFSM6AAAAAAWAIS7JKWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTSYODV4Y.gif Message ID: @.*** @.***> >


[Bug]: bluetooth-cli-tools doesnt work on windows 11

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name
extras/bluetooth-cli-tools
Expected/Current Behaviour
These tools don't seem to support windows 11 (they hang with no output when run in windows terminal)
Does scoop have a way to add a warning or filter out a tool based on OS version?
Steps to Reproduce
> scoop install extras/bluetooth-cli-tools
Updating Scoop...
Updating 'extras' bucket...
Updating 'java' bucket...
Updating 'main' bucket...
Updating 'sysinternals' bucket...
Scoop was updated successfully!
Installing 'bluetooth-cli-tools' (<IP_ADDRESS>) [64bit] from extras bucket
BluetoothCLTools-<IP_ADDRESS>.exe (3.2 MB) [======================================================================] 100%
Checking hash of BluetoothCLTools-<IP_ADDRESS>.exe ... ok.
Extracting BluetoothCLTools-<IP_ADDRESS>.exe ... done.
Linking ~\scoop\apps\bluetooth-cli-tools\current => ~\scoop\apps\bluetooth-cli-tools\<IP_ADDRESS>
Creating shim for 'btdiscovery'.
Creating shim for 'btftp'.
Creating shim for 'btinfo'.
Creating shim for 'btobex'.
Creating shim for 'btpair'.
Creating shim for 'btcom'.
Creating shim for 'btconfig'.
'bluetooth-cli-tools' (<IP_ADDRESS>) was installed successfully!

Possible Solution
filter based on OS, or add a warning after install if running windows 11?
Scoop and Buckets Version
> scoop --version
Current Scoop version:
v0.3.1 - Released at 2022-11-15

'extras' bucket:
df02f9c4a (HEAD -> master, origin/master, origin/HEAD) saber: Update to version 0.14.8

'java' bucket:
9edd4930 (HEAD -> master, origin/master, origin/HEAD) liberica8-jre: Update to version 8u382-6

'main' bucket:
38993078d (HEAD -> master, origin/master, origin/HEAD) quarkus-cli: Update to version 3.2.1

'sysinternals' bucket:
cdb0f98 (HEAD -> main, origin/main, origin/HEAD) chore: Add ARM64 arch to several tools

Scoop Config
> scoop config

last_update                     : 7/19/2023 4:40:36 PM
cat_style                       : plain
aria2-warning-enabled           : True
aria2-max-connection-per-server : 2
alias                           : @{u=scoop-u; alias-v=scoop-alias-v; cache-rm-all=scoop-cache-rm-all;
                                  cache-show-all=scoop-cache-show-all; cleanup-all=scoop-cleanup-all; i=scoop-i;
                                  info-v=scoop-info-v; search-info=scoop-search-info; update-all=scoop-update-all;
                                  info-all=scoop-info-all}
show_update_log                 : False
aria2-enabled                   : False
scoop_repo                      : https://github.com/ScoopInstaller/Scoop
scoop_branch                    : master

PowerShell Version
> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.3.5
PSEdition                      Core
GitCommitId                    7.3.5
OS                             Microsoft Windows 10.0.22621
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Additional Softwares
No response

It is slow, but it works.
~
❯ scoop install bluetooth-cli-tools
Installing 'bluetooth-cli-tools' (<IP_ADDRESS>) [64bit] from extras bucket
Loading BluetoothCLTools-<IP_ADDRESS>.exe from cache
Checking hash of BluetoothCLTools-<IP_ADDRESS>.exe ... ok.
Extracting BluetoothCLTools-<IP_ADDRESS>.exe ... done.
Linking ~\scoop\apps\bluetooth-cli-tools\current => ~\scoop\apps\bluetooth-cli-tools\<IP_ADDRESS>
Creating shim for 'btdiscovery'.
Creating shim for 'btftp'.
Creating shim for 'btinfo'.
Creating shim for 'btobex'.
Creating shim for 'btpair'.
Creating shim for 'btcom'.
Creating shim for 'btconfig'.
'bluetooth-cli-tools' (<IP_ADDRESS>) was installed successfully!
~
❯ btinfo -c
False
~ took 21s
❯ btconfig -c 1
~ took 21s
❯ btinfo -c
True
~ took 21s
❯ btdiscovery
(**:**:**:**:**:**)     humorce's iPhone        Smartphone
~ took 27s
❯ btpair -n "humorce's iPhone" -p0000
### A window pop up on both phone and PC then connected to phone with manually operation.
~ took 49s
❯ btobex -n "humorce's iPhone" sc.png
System Error.  Code: 10049.
The requested address is not valid in its context
### Following the usage example of its, fails

I am not progressing test btobex, btftp and btcom, this may be limited by the iPhone or something what. It may be better to use in cmd.exe.

Temporarily closed, feel free to reopen this issue.
Reasons:

Cannot reproduce.
No response and additional information


[release-2.5] Reduce caching time for translations (#1761)

Avoid sending content on revalidation
https://github.com/stolostron/backlog/issues/23479

/cc @jamestalton


fix: Fix IDb-automerge storage adapter

Motivation / Background

This Pull Request ...
Details

Additional information

Current dependencies on/for this PR:

main

PR #5252   👈

This stack of pull requests is managed by Graphite.


IAM policy resource late initialization does not complete for Description field

Describe the bug
Hello team, we recognised that iam-controller does not sync properly iam-policy resource and causing constant reconciliation with message "Late initialization did not complete, requeuing with delay of 5 seconds", full log attached bellow.
Steps to reproduce
Deploy iam policy with iam-controller, check resource status.
Expected outcome
IAM policy resource state synced.
Environment

EKS: 1.21
AWS service targeted: AWS::IAM::Policy
Controller: iam-controller:v0.0.21

iam-controller.log

Hi @vshunkov could you provide an example of a resource that's triggering this error message?

Hi @A-Hilaly, here you are policy.txt

Apologies on delayed response... Still digging out from hurricane...
Can you please paste the results of kubectl describe? Thanks!
On Wed, Sep 28, 2022, 3:20 AM vshunkov @.***> wrote:

Hi @A-Hilaly https://github.com/A-Hilaly, here you are policy.txt
https://github.com/aws-controllers-k8s/community/files/9662408/policy.txt
—
Reply to this email directly, view it on GitHub
https://github.com/aws-controllers-k8s/community/issues/1490#issuecomment-1260491349,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACAWP2LFLPYMRFMKKPDKEDWAPWULANCNFSM6AAAAAAQW4HVLI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi @jaypipes,
I hope none of your loved ones got hurt. Here is describe output.
Regards,
Vladimir.

@vshunkov OK, there's at least a couple bugs that I've found. The first is that the delta comparison for Tags is incorrectly returning a difference between lists that contain identical structs but are ordered differently. The fix for this bug will avoid the repeated lines in the controller log that look like this:
2022-09-27T14:37:23.536Z	INFO	ackrt	desired resource state has changed	{"account": "XXXXXXXXXX", "role": "", "region": "eu-west-1", "kind": "Policy", "namespace": "default", "name": "iamp-d-demo-test-eu-west-1", "is_adopted": false, "generation": 6, "diff": [{"Path":{"Parts":["Spec","Tags"]} ...

The controller isn't actually calling any AWS APIs for changing tags, but it's annoying to have the controller logs show there is a difference in tags when there actually isn't :) I will work on this bug in a separate issue.
The second bug seems to be that the fields of a Policy that are late-initialized (which are Spec.Path and Spec.Description) are not properly returning a non-error value for some reason.
I suspect that this is probably the Spec.Description field which is late-initialized and I wrote this in the generator.yaml file for the IAM controller after finding out that the Description field is, well, a bit weird:
      Description:
        # You might be wondering why description is late-initialized, since
        # there isn't a default server-side value for description.
        #
        # The CreatePolicy API call accepts a Description field in the input
        # and the documentation (and API model) say that a Description field is
        # included in the returned response from CreatePolicy, however the
        # Description returned from the CreatePolicy API call is always
        # missing/nil which means the SetResource code sets the
        # Spec.Description to nil. When the next time the GetPolicy API call is
        # made in the next reconciliation loop, GetPolicy returns the
        # description that was originally set in the CreatePolicy API call and
        # a Delta difference is discovered erroneously (because the SetResource
        # call after CreatePolicy incorrectly set the description to nil). So,
        # we set the late initialize property of the Description field here to
        # override the Spec.Description to the original value we set in the
        # CreatePolicy *input* shape.
        late_initialize: {}

@vshunkov May I ask that you add a Description to your Policy resource and see if that ends up allowing the late initialization to complete properly? If so, then it's a bug in how I implemented late initialization for the Description field...

OK, awesome. You can use that as a workaround in the meantime while I fix the IAM controller's late initialization of the Description field. I've also created a new issue (#1503) for the tag comparison bug.

Related #1772

This is now fixed in iam-controller v1.3.6 - the controller now correctly handles the Description field for Roles and Policies, preventing an infinite requeue caused by missing Description field in Create calls. cc @vshunkov


charliecloud: 0.12 -> 0.18

Motivation for this change
An important bug has been fixed https://github.com/hpc/charliecloud/pull/826/files
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

@ofborg build charliecloud

@ofborg eval

Many thanks for your help @danieldk !

Thanks for packaging Charliecloud!! Very much appreciate your efforts. And please do let us know if upstream can do anything to make you work easier.


update eye script to gate with CI in a PR

:tada: This PR is included in version 2.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


unable to proceed in a filterable prompt after breaking out of the input field

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
pnpm
If applicable, what version of Node.js are you using?
18
Amplify CLI Version
10.5.1
What operating system are you using?
mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
n/a
Amplify Categories
Not applicable
Amplify Commands
Not applicable
Describe the bug
Similar to https://github.com/aws-amplify/amplify-cli/issues/11521, I encountered this using the API category. In a filterable prompt, type a few characters such as "hello", move the cursor to the left a few spaces, then hit backspace. From here you will be able to continue to hit backspace and move the cursor into the prompt's question and you must ctrl+c out of the flow.
Expected behavior
you are unable to move out of the input field
Reproduction steps

amplify init -y
amplify add api > REST API
follow the prompts until you get to "Restrict API Access"
select "Yes"
filter with "hello"
move the cursor to the left
press backspace a few times
observe you have broken out of the input field and are unable to proceed

✔ Restrict API access? (Y/n) · yes
✖ Restrict access by: ·               lu
🛑 There was an error adding the API resource

GraphQL schema(s)

# Put schemas below this line

Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response

Was able to reproduce this, marking as bug. We can click the right arrow to jump back to the filter input.


update dotnet-sdk to 2.0.3

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[ ] Named the cask according to the token reference.
[ ] brew cask install {{cask_file}} worked successfully.
[ ] brew cask uninstall {{cask_file}} worked successfully.
[ ] Checked there are no open pull requests for the same cask.
[ ] Checked the cask was not already refused in closed issues.
[ ] Checked the cask is submitted to the correct repo.

Version 2.0.3 of .net core was released Nov 11th 2017. https://github.com/dotnet/core/blob/master/release-notes/2.0/2.0.3.md

Thanks for the PR!


Add the traefik to the VelaUX addon and provide dynamic proxy capability for system service

Currently, we use the Nginx to proxy the API and dex services, it must static configuration. We will integrate more system service that has access endpoint, the static configuration is painful.
Traefik is a modern and cloud-native proxy server, that has dynamic configuration capability, at the same time it is lightweight and easy to use.

done


Elevated PowerShell window is left open after installation

What You Are Seeing?
Boxstarter opened an elevated PowerShell window to install a script. After the script installation the window was left open.
This might be confusing for users less familiar with Windows in general ("Did it already finish? Or doing something in the background? Can I close this?"). This might also be considered a security issue: scripts can take a long time to run, users may leave the computer unattended and the elevated console might be used by someone else.
What is Expected?
The window should pause at the end to allow reading the console output, but then exit without giving users a chance to use the console (something similar to https://github.com/chocolatey/boxstarter/blob/262f07e81d8f1dc3a20ac7530f35d241bd9b3c80/Boxstarter.Bootstrapper/Cleanup-Boxstarter.ps1#L38).
How Did You Get This To Happen? (Steps to Reproduce)
Run a script without Admin privilege in Windows 10 (mine is 10.0.17134.228).

PR #340 was merged.


Tf 0.7.1

Merging in tensorflow 0.7.1
This will change a lot of functionality.

Can one of the admins verify this patch?

My apologies. This was an accidental request.


Partial error message from code executor

take a max subset of the output to do not run out of token.

#2060

@microsoft-github-policy-service agree

Hi can I close the pull request or u have any requirements/ sudgestion for further implementation, in case let me know

Hi, I think this kind of capability might be better suited to the new transform_messages capability - https://microsoft.github.io/autogen/docs/reference/agentchat/contrib/capabilities/transform_messages#transformmessages


Switch to udx-native

This PR replaces the networking layer with https://github.com/mafintosh/libudx.

@kasperisager pushed my changes to origin/udx. can we update this PR to point to that?

GitHub only allows changing the target branch, not the source branch. I can open a new PR though.

@kasperisager really! can you make a new PR then?

Superseded by #83.


⚠ SceneTime has degraded performance

In d271bb6, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1586 ms

Resolved: SceneTime performance has improved in 1b8b934.


SVN link in Readme is dead

New link is:
git clone https://chromium.googlesource.com/breakpad/breakpad

Actually, the aforementioned git repo is missing things like the lss third_party headers -- turns out you have to use depot_tools to fetch them all.


Table elements onClick

Description
Adds onClick prop to JTable, TableRow, and TableCell
Updated stories to demonstrate cancelling events to stop propagation to containing elements.
@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.


Add support for more OpenEXR attributes

As reported in:
https://github.com/darbyjohnston/DJV/issues/251
Currently we are only showing the standard OpenEXR attributes, we should expand this to include any attributes that have types we can parse, such as strings, floats, vectors, etc.

I've added support for all of the OpenEXR predefined attributes and also any other attributes with standard types like string, int, float, M44f, etc.


Add minor improvements for readability

Hey buddy,
I added the changes we discussed and did some additional renamings.
Cheers

We might want to think about supporting different logging patterns or at least try to detect the datasource url a little more flexible as not everyone is using the default spring boot logging format ( https://docs.spring.io/spring-boot/docs/2.1.13.RELEASE/reference/html/boot-features-logging.html#boot-features-logging-format ).
Thoughts?

I removed it as we are mit bound to a particular log pattern. Thats why I
created the other remark. 😄
Yusuf Uğur ÖZBEK @.***> schrieb am Sa., 11. Sept. 2021,
11:26:

I am trying to find the message on GitHub, but couldn't. I think that's a
brilliant idea. From a PO perspective, we shouldn't make an effort until
our end customers request that. From a developer's perspective, let's do
that. I propose to create an issue about it and if it gets rate or thumbs
up we can do that. Therefore, could you please create an issue about it? I
don't want to do that since it is your idea.

From: Ben Roth @.***>
Sent: Friday, September 10, 2021 17:25
To: yusufugurozbek/testcontainers-port-updater
Cc: Subscribed
Subject: Re: [yusufugurozbek/testcontainers-port-updater] Add minor
improvements for readability (#39)
We might want to think about supporting different logging patterns or at
least try to detect the datasource url a little more flexible as not
everyone is using the default spring boot logging format (
https://docs.spring.io/spring-boot/docs/2.1.13.RELEASE/reference/html/boot-features-logging.html#boot-features-logging-format
).
Thoughts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<
https://github.com/yusufugurozbek/testcontainers-port-updater/pull/39#issuecomment-916989928>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/AFL7SDBYIXR3RPBJ2WBUBNDUBIPQJANCNFSM5DZOVNTQ

.
Triage notifications on the go with GitHub Mobile for iOS<
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android<
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/yusufugurozbek/testcontainers-port-updater/pull/39#issuecomment-917374891,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAESHGHDU52WRXZGNHAMT2LUBMOEJANCNFSM5DZOVNTQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


support more file types

The Issue
I tried opening this content (included screenshot)  and after the download was completed, this is how the screen appeared(please check screen)
Steps to reproduce

In the mobile app, look for the community post that has a broken cup
Download and after the download is completed, the screen appears white

Expected behaviour
It should have opened the content as it does on PC: seems to me like the android app does not seem to support text/html as the desktop app
Actual behaviour
Instead the screen appears white, and does not include the full video description
System Configuration

Device: Note 8 Samsung
Android version: 8.0.

Anything Else

https://cdn.discordapp.com/attachments/439055085616496640/441960963302752267/Screenshot_20180504-192359_LBRY_Browser.jpg
https://cdn.discordapp.com/attachments/439055085616496640/441961042998722571/Screenshot_20180504-192341_LBRY_Browser.jpg
Screenshots

We can try to add support for images and text/html to display in-app.

Added in-app view support for the following content types:

image/*
text/*


TODO: Rename index cache YAML fields: type => backend, config => backend_config

https://github.com/thanos-io/thanos/pull/2532 has introduced new cache config for caching bucket. In this PR, we use backend and backend_config YAML fields for selecting type of cache (memcached only for now), and its configuration.
This is different than what is used by index cache, where we use type and config. We would like to rename these to backend and backend_config as well at some point.

This is to be done after #2532  gets merged, right?
I would like to fix this if it's ok.

This is to be done after #2532 gets merged, right?

Yes.

I would like to fix this if it's ok.

That would be great! Thanks.

We also need to update docs to reflect renaming.

We can close this now :)

Closing as a result of the discussion on Slack https://cloud-native.slack.com/archives/CL25937SP/p1589816009201600.
Let us know if this is still desired.


Example in ReadMe uses invalid coin

cdv rpc coinrecords --by id e16dbc782f500aa24891886779067792b3305cff8b873ae1e77273ad0b7e6c05
The coin listed above is not valid; it produces an empty result.
0x6ce8fa56321d954f54ba27e58f4a025eb1081d2e1f38fc089a2e72927bcde0d1
This one works^

Thank you for the comment, this was fixed in https://github.com/Chia-Network/chia-dev-tools/pull/16


Stop PinchZoom when page scaled by pinch

On touch devices the OpenLayers PinchZoom interaction changes the zoom/resolution of the map. This works well unless the user gets into the following situation of 'no escape':

User visits a page with an OpenLayers map, on say a mobile device
The user uses the pinch gesture to scale the page (not the map) so that now only the map is now visible on the page
The user tries to pinch again to scale the page back to normal, but as only the map is visible and any pinch gesture changes the zoom/resolution on the map and not the page, the user gets stuck in the map and cannot get back to the page

The above can be seen in the https://openlayers.org/en/latest/examples/pinch-zoom.html example.
One option is to disable the map PinchZoom interaction whenever the user uses the pinch gesture to scale the page. You may have a better solution?
How do we detect the above situation and prevent it from happening?
Thank you.

That is opposite problem to #13495.  If the page must be able to zoom https://stackoverflow.com/a/995967/10118270 might help with the detection.

This works on Android with Chrome - disable the interaction if the map size exceeds more than half the visual viewport https://codesandbox.io/s/pinch-zoom-forked-r7lk4r?file=/main.js

Many thanks. This looks like a something that I can work with.


ADReplicationSite: Integration tests is missing for this resource

We should add integration tests for this resource.

Cool thank you!


Weird behaviour in a series of if-else branches

Aim
I have a series of nested if-else blocks. In each branch I assign a value to a variable based on the branch condition.
Expected Behavior
I would expect only of the branches to execute as it is the case in if-else conditions.
Bug
I'm experiencing something with I'm struggling to get my head around.
I've to the following function:
global UPPERCASEOFFSET: u8 = 65;
global LOWERCASEOFFSET: u8 = 71;
global DIGITOFFSET: u8 = 4;

pub fn get_char_for_index(index: u8) -> Option<u8> {
  let mut ascii_index = Option::none();

  if index >= 0 & index <= 25 {
    std::println(index);
    // A-Z
    ascii_index = Option::some(index + UPPERCASEOFFSET);
  } else {
    if index >= 26 & index <= 51 {
      // a-z
      ascii_index = Option::some(index + LOWERCASEOFFSET);
    } else {
      if index >= 52 & index <= 61 {
        // 0-9
        std::println(">>>>>>>>>>>>>>>>>>>>>>>>");
        ascii_index = Option::some(index - DIGITOFFSET);
      } else {
        if index == 62 {
          ascii_index = Option::some(43);
        } else {
          if index == 63 {
            ascii_index = Option::some(47);
          }
        }
      }
    }
  };

  ascii_index
}

#[test]
fn test_get_char_for_index() {
  let value: [u8] = [0, 10, 25, 26, 35, 51, 52, 55, 61, 62, 63];
  let expected: [u8] = [65, 75, 90, 97, 106, 122, 48, 51, 57, 43, 47];

  for i in 0..11 {
    let result = Option::unwrap(get_char_for_index(value[i]));
    assert(result == expected[i]);
  }

  let result = get_char_for_index(64);
  assert(Option::is_none(result));
}

The test passes which is cool. However, when I call this function from another context I get some weird behaviour.
I'm sharing the console output which shows the logs:
[base64] Testing encode::test_encode_with_trailing_equal... 0x10
0x14
0x09
0x11
0x00
Failed assertion: 'attempt to subtract with overflow'
error: Assertion failed: 'attempt to subtract with overflow'
   ┌─ /Users/ppoliani/code/apocentre/zk/noir/noir-libs/base64/src/classic.nr:23:36
   │
23 │         ascii_index = Option::some(index - DIGITOFFSET);
   │                                    -------------------

The function is called with the following u8 integers
[16, 20, 9, 17, 0]
It crashes on the last value (which is 0). As you can see in the logs though, when the value is 0, it enters the first if (index >= 0 & index <= 25) but for some reason it then end ups entering the nested statement where the panic happens.
What is interesting though is that the println is not even executed within that branch.
I'm not sure if it's a bug or I'm doing something fundamentally wrong.
To Reproduce

The code for the circuit is here.

Run the tests in the root base64 folder.
nargo test  --show-output  --package base64  --silence-warnings test_encode_with_trailing_equal
Installation Method
Binary
Nargo Version
nargo 0.19.2 (git version hash: 47f0130c0d154f1b70eb23f376783beb3f23ad72)
Additional Context
No response
Would you like to submit a PR for this Issue?
No
Support Needs
No response

Hi @ppoliani, this looks to be a duplicate of #3493 which was fixed in https://github.com/noir-lang/noir/pull/3494.
You can fix this issue by updating to 0.19.3 or above.

Hi @ppoliani, this looks to be a duplicate of #3493 which was fixed in #3494.
You can fix this issue by updating to 0.19.3 or above.

Oh thank @TomAFrench. I can confirm it works now. Sorry, I missed https://github.com/noir-lang/noir/issues/3493.


tuf.api.exceptions.DownloadLengthMismatchError: Downloaded x bytes exceeding the maximum allowed length of y

tuf.api.exceptions.DownloadLengthMismatchError: Downloaded 21755631 bytes exceeding the maximum allowed length of 21755616

how can we fix this issue? pls help
Originally posted by @mdhuzaifapatel in https://github.com/dennisvang/tufup-example/issues/3#issuecomment-1728942285

@mdhuzaifapatel Typically this happens if your file is modified, somewhere along the line, after adding it to your tuf repository.
It is difficult to help without more detailed information, as there are many possible causes. It could be due to your own actions, or perhaps your server configuration is causing the issue.
For example, if your server is serving the .tar.gz files with Content-Encoding: gzip, the files will be decoded automatically upon download, which is not what you want.
Another possibility is that you are working with stale metadata. During the testing phase, it often helps to start with a clean slate.


Split Datastore issue

I've recently wiped my database. Now, every time i try to add a command for me, or use something, I'm receiving a error of No Permissions. I was wondering why, then I decided to add a permission for me, and seems that LuckPerms didn't re-registered me to the database. Look: http://prntscr.com/d05su5
In my database, the user and uuid tables are empty.
Running:
SpongeForge 1.10.2-6.0.0-BETA-1851
LuckPerms build 45 from Jenkins
LuckPerms in database (MySQL) mode

Did you wipe the database whilst the user was online?

No, I wiped with the server offline. I've tried reconnect/restart, but no effect too.

Is the uuid table still empty?

Yes

Then that's your problem.
It's working fine for me. I dropped all of my tables before testing.

I'm running a modpack, I didn't erased the playerdata or something like it... Can you explain what exactly is wrong? I'm blind 😥

Player data shouldn't effect it. LuckPerms relies on the uuid table only for it's lookups.
Any exceptions in console? My guess is that the server can't write to MySQL.

Hmmm, true, i've recently restarted my MySQL server, let me try restart again the server.

Nope. Didn't work. Looking in the logs, everything seems to work fine, no errors/stacktraces, and LuckPerms can connect to the database...

Can you try testing with H2 instead? The core behaviour is exactly the same. It will just narrow down whether it's an issue with your MySQL server or LuckPerms.

Okay, brb

[LP] User could not be found.

Using H2...

Can you pastebin your startup log please?

Here: http://frani.magitechserver.cf/fml-server-latest.log

Strange.
Can you try on a clean Sponge installation? I cannot reproduce at all. I've tried on both SpongeForge and SpongeVanilla, using clean H2 setups.

Tried a clean Sponge installation, worked... I'm wondering why it's bugging only with my server :/

I guess just try out different things.
Take a copy of your old server and try removing bits.
Remove some mods, remove other plugins, reset the world, etc etc. I have no clue why you're having issues. 😢

I also hit this problem. I have managed to reproduce it once.
From a fresh install, change all the storage methods to yaml and split storage all at the same time. Luckperms will not recognise a player exists with /perms user  info.
storage-method="yaml"
split-storage {
  enabled=true
  methods {
    user="yaml"
    group="yaml"
    track="yaml"
    uuid="yaml"
    log="yaml"
  }
}

However when I changed from H2 to yaml storage method, then restarted, and then to split storage, it worked okay.
So perhaps it's something to do with changing storage methods and splitting all at once?

Shouldn't be. Is it specifically an issue with split storage? @Eufranio were you using split storage, or one option?

Yes, I was. I thought change the split was neccessary to change the database type...

Alright, perfect.
I'll look into that. :)
p.s. No it's not necessary.

You could add a comment in this section, like
DON'T MODIFY IF YOU DON'T KNOW WHAT YOU ARE DOING

It did previously have that message, funnily enough. I removed it because I considered it stable enough to use. 😉
https://github.com/lucko/LuckPerms/commit/3fd62a80e27c3aa240f65723d714c6b32be6a3ba

Thanks, i'll test it right now!

FIXED!

I haven't fixed the split storage issue yet. :)

Ahhh, okay, it's fixed here because i disabled split storage. Nice work


Request for newer version of FMS

mom6 apparently requires more recent version of FMS. The latest release from GFDL is xanadu (although mom6-examples refers to a FMS @ f2e2c86, which is the latest on the master branch)

When we go to MOM6, we should fork FMS into a separate repository under GEOS-ESM.    We could still include it underneath GMAO_Shared if that is desired.

When we go to MOM6, we should fork FMS into a separate repository under GEOS-ESM. We could still include it underneath GMAO_Shared if that is desired.

If we do this, we need to be careful, or mindful at least. Xanadu is a few months behind the master of FMS. Not a big problem as it looks like 99% of the changes since then are Ed Hartnett adding Autotools.
What's more exciting is that it would require careful, but not impossible, CMake update from @tclune and myself as a pure clone of FMS into GEOS would pull the real source code out of the current GFDL_fms/shared directory to directly into GFDL_fms.

Hmm. Actually, it might be worth the effort. It looks like the test with the JEDI FMS I did a while back has quite a few differences with Xanadu. I think they forked off of the dev/master of GFDL. From staring at the changes, some were by @aerorahul  and others seem to be bug fixes either from GFDL or JCSDA.

I suppose the "correct" thing would be to fork from NOAA-GFDL and then make a branch and, if nothing else. put the MAPL_MODE changes into that.
There do seem to be a good chunk of changes on the JCSDA version that seem worthy bug fixes and I'm wondering if @aerorahul or Dan Holdaway could tell us if those are things we'll need to fix for GEOS as well? If so, we'd probably want to pull those edits into our branch (the ones that aren't on master).

Yes - fork of NOAA-GFDL can/must proceed in advance of other changes.
@aerorahul (on travel this week) has already looked into issues with integrating MOM6 within our cmake infrastructure.    I don't think it was completed before he left town, and it may be in the way of Santha's work.   I'll try to catch up with him today.  (His GitHub account request preceded our establishment of a process and thus he was missed until just now.)

If possible, please look at jcsda fork of fms and branch dev/master-ecbuild.
We have used this branch with both mom6 and standalone FV3.
I did not finish mom6 integration into our geos cmake.
If you are interested in seeing how the JEDI builds mom6 with FMS and other mom6 dependencies, see aerorahul/mom6-bundle

@aerorahul - we certainly want to get your branch pushed onto the GEOS-ESM fork of fms.     But I think our fork should be directly from GFDL.      I anticipate a bit of a mess in the future when high level apps try to determine just where to get libraries like FMS from ...

Well, going off of NOAA-GFDL/FMS/master, I at least have something that can build the library itself; I'm trying the model now. I'll probably do some baby steps. First the minimal change off of master and if all is zero-diff, commit. Then perhaps branch

I should say commit and push of course.
Eventually I'll need to consult @tclune on how to manage the external. For now I'm just sort of hard-coding in changes into this clone and getting things working first.

And one plus of forking off of GFDL's stock repo master is I can make another fork, where I disable those annoying !DEC$ MESSAGE and make a pull request to have them removed in master!

@tclune the changes in the jcsda fork are strictly in the CMakeLists.txt. So, no issue on forking directly from NOAA-GFDL.
We can eventually reconcile. Also, when building JEDI interfaces with GEOS, we will use the FMS library compiled with GEOS, rather than the jcsda fork.

Well this is exciting. I committed and pushed some changes to my fork of FMS and guess what? It has a .travis-ci.yml file!
It is failing at present, though I'm not sure if it ever passed. Still, I think I have an inkling of what it's mad about and I'll fix that soon.

Okay. I have some results. I can build and run the model with both a minimally-different-from-master branch and one which has all the extra changes from JCSDA. If I compare that to our current FMS the answers are...sort of zero-diff?
If I compare a 1-day run of stock GEOSgcm master (v10.3.1 or Jason-3_1) to the new FMS I get zero diff except for:
Comparing NC4 fvcore_internal_checkpoint using nccmp...
Failure!
Checking for data differences
Variable Group Count          Sum      AbsSum          Min         Max       Range         Mean      StdDev
U        /     15954 -2.89844e-13 1.35394e-11 -1.42109e-14 1.42109e-14 2.84217e-14 -1.81675e-17 1.44738e-15
V        /     11219 -7.91107e-14 8.93166e-12 -2.13163e-14 1.77636e-14 3.90799e-14 -7.05149e-18 1.48342e-15
Checking for metadata differences

Comparing NC4 moist_import_checkpoint using nccmp...
Failure!
Checking for data differences
Variable Group Count         Sum      AbsSum         Min         Max Range        Mean StdDev
OMEGA    /         1 3.72529e-09 3.72529e-09 3.72529e-09 3.72529e-09     0 3.72529e-09      0
Checking for metadata differences

Comparing NC4 turb_import_checkpoint using nccmp...
Failure!
Checking for data differences
Variable Group Count         Sum      AbsSum         Min         Max Range        Mean StdDev
OMEGA    /         1 3.72529e-09 3.72529e-09 3.72529e-09 3.72529e-09     0 3.72529e-09      0
Checking for metadata differences

Nothing else is different. As for the "stock" HISTORY, everything is identical except one file of geosgcm_prog:
Comparing geosgcm_prog.20000415_0000z...
Success!
Comparing geosgcm_prog.20000415_0600z...
Success!
Comparing geosgcm_prog.20000415_1200z...
Failure!
Checking for data differences
Variable Group Count         Sum      AbsSum          Min         Max       Range        Mean      StdDev
OMEGA    /        13 8.73115e-10 1.51922e-08 -1.86265e-09 2.32831e-09 4.19095e-09 6.71627e-11 1.38192e-09
Comparing geosgcm_prog.20000415_1800z...
Success!

This said, the two branches I made are zero-diff to each other. So they are consistent.

All,
I have a new branch of GEOSgcm with the latest Xanadu FMS. The branch is feature/xanadu-fms. In this branch, FMS is now a new subrepository parallel to GMAO_Shared. I'll wait for @atrayano to test it out, but it seems to build and run for me.

I suppose this is now closed as we have moved to use FMS 2019.01.01
Is that correct @aerorahul, et al?

@mathomp4 if FMS 2019.01.01 is the default FMS, then I think this can be closed.

I like closing things.


[UPDATE] logic of check for asset amount on send

Please update the logic for the amount check of assets.
Currently: Checks after each input, leading to annoying UX when inserting . or erasing everything.
Wanted: check once when user leaves input label
https://github.com/user-attachments/assets/f46766ab-003b-43b9-a795-8e73895eda99

QA done.


Quick edit doesn't close using keyboard shortcut without a CSS file.

If you delete your CSS file from the file tree and try to close quick edit using the keyboard shortcut CMD + e the inline widget opens back up.
STR:

open brackets
delete all CSS files
open quick edit on an element using CMD + E
try to close quick edit using CMD + E

It looks like this

Its because there is no focus on inlineWidget when no css/less is present in the project. I feel it would be good to have focus on 'X' in inline widget.


Document types of available channels

It's hard to discover the types of channels (triggers) available to force. It would be great to include them in the docs.

this is done at least for MVP in plugins section


Homebridge will not show up in ios using version 2.0

Problem/Motivation
I had homebridge working on my Rapi3 but after updating to homebridge 2.0 I can no longer get it to show up on HomeKit on my ios devices. The HomeKit scan will also not recognize the HomeKit Code
Expected behavior
I would expect that when the ios scanner is used on the displayed code it would recognize it and then the accessories would appear in the Home app
Actual behavior
The HomeKit scanner does not detect the displayed code and no accessories appear in the app when the code is manually entered
Steps to reproduce
Using this configuration:
{
"log_level": "info",
"avahi_interfaces": "eth0,wlan0",
"avahi_hostname": "",
"avahi_domainname": "local",
"enable_ipv6": false,
"packages": [],
"init_commands": [],
"plugins": [
"homebridge-mqtt-temperature",
"homebridge-mqtt-switch-tasmota",
"homebridge-radiothermostat",
"homebridge-chamberlain"
]
}
Produces these logs:
Logs
[cont-init.d] 50-config.sh: executing...
[cont-init.d] 50-config.sh: exited 0.
[cont-init.d] 60-ipv6-hotfix.sh: executing...
patching file /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/eventedhttp.js
[cont-init.d] 60-ipv6-hotfix.sh: exited 0.
[cont-init.d] 80-user-packages.sh: executing...
[cont-init.d] 80-user-packages.sh: exited 0.
[cont-init.d] 81-user-scripts.sh: executing...
[cont-init.d] 81-user-scripts.sh: exited 0.
[cont-init.d] 82-user-plugins.sh: executing...

<EMAIL_ADDRESS>added 73 packages in 26.125s

<EMAIL_ADDRESS>added 73 packages in 10.864s

<EMAIL_ADDRESS>added 54 packages in 19.116s

<EMAIL_ADDRESS>added 6 packages in 4.435s
[cont-init.d] 82-user-plugins.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
starting version 3.2.2
[services.d] done.
Found user 'avahi' (UID 86) and group 'avahi' (GID 86).
Successfully dropped root privileges.
avahi-daemon 0.6.32 starting up.
WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Successfully called chroot().
Successfully dropped remaining capabilities.
No service file found in /etc/avahi/services.
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Joining mDNS multicast group on interface hassio.IPv4 with address <IP_ADDRESS>.
New relevant interface hassio.IPv4 for mDNS.
Joining mDNS multicast group on interface wlan0.IPv4 with address <IP_ADDRESS>.
New relevant interface wlan0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address <IP_ADDRESS>.
New relevant interface eth0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for <IP_ADDRESS> on hassio.IPv4.
Registering new address record for <IP_ADDRESS> on wlan0.IPv4.
Registering new address record for <IP_ADDRESS> on eth0.IPv4.
Server startup complete. Host name is hassio.local. Local service cookie is<PHONE_NUMBER>.
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=node
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!

Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 841-81-145 │
└────────────┘

[10/23/2017, 6:44:30 PM] Homebridge is running on port 51826.
[10/23/2017, 6:44:30 PM] [HomeAssistant] Received event: {"event_type": "state_changed", "data": {"entity_id": "sun.sun", "old_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-10-24T11:25:56+00:00", "next_dusk": "2017-10-23T23:06:06+00:00", "next_midnight": "2017-10-24T05:15:13+00:00", "next_noon": "2017-10-24T17:15:18+00:00", "next_rising": "2017-10-24T11:54:47+00:00", "next_setting": "2017-10-24T22:35:50+00:00", "elevation": -2.29, "azimuth": 255.81, "friendly_name": "Sun"}, "last_changed": "2017-10-23T22:37:20.575769+00:00", "last_updated": "2017-10-23T22:43:30.554935+00:00"}, "new_state": {"entity_id": "sun.sun", "state": "below_horizon", "attributes": {"next_dawn": "2017-10-24T11:25:56+00:00", "next_dusk": "2017-10-23T23:06:06+00:00", "next_midnight": "2017-10-24T05:15:13+00:00", "next_noon": "2017-10-24T17:15:18+00:00", "next_rising": "2017-10-24T11:54:47+00:00", "next_setting": "2017-10-24T22:35:50+00:00", "elevation": -2.48, "azimuth": 255.98, "friendly_name": "Sun"}, "last_changed": "2017-10-23T22:37:20.575769+00:00", "last_updated": "2017-10-23T22:44:30.555779+00:00"}}, "origin": "LOCAL", "time_fired": "2017-10-23T22:44:30.555925+00:00"}
Proposed changes

Home Assistant._hap._tcp.local.
HAP
hassio.local:51826
<IP_ADDRESS>:51826
<IP_ADDRESS>:51826
2601:408:400:e18c:674b:cb30:b7c8:73a6:51826
2601:408:400:e18c:622c:fa83:df1d:f19:51826
c# = 23
ci = 2
ff = 0
id = AA:BB:CC:DD:EE:FF
md = Home Assistant
pv = 1.0
s# = 1
sf = 0

That all looks good @kbloxsom.
Have you tried: https://github.com/hassio-addons/addon-homebridge#my-ios-app-cannot-find-homebridgehome-assistant ?

That seems to have solved it. Thanks!


Fixes #128 Send only last log lines to log window

I might consider a small change to the log window to make it more appealing.
We can always decide to drop it.


Provide signed updates on the website and through auto-update

It would be great if you could provide signed updates on the website and through the auto-update functionality. There are a few different ways you can do this, but I highly recommend using GPG signatures. This will require some key management on your end. Please let me know if you'd like to chat about how to best implement this.

@runasand thanks for opening this issue - sorry for the delay in responding!


Lib is hardcoded to C:

in cuda_setup/main.py
CUDA_SHARED_LIB_NAME: str = "libcuda.so" if not IS_WINDOWS_PLATFORM else "C:\\Windows\\System32\\nvcuda.dll"
Should probably use something like f"{os.environ['windir']}\\System32\\nvcuda.dll" so it works on all letters.

I wasn't the one who coded that, but I can certainly change it! I've been meaning to re-order the runtime search paths anyway. It doesn't make sense to search PATH before searching CUDA_PATH since PATH can potentially contain multiple runtimes and none of them have to be relevant to the current task.


fix: Harden violation scanning against NullPointerException

Fix #314
Hardens violation scanning against NPEs by filtering out any AnalyzerMessages that don't have primary locations. If one were to somehow slip through anyway, ScannedViolation is now adapted to provide better error messages.

Thanks @slarse

Thanks @slarse


Flutter project cannot run on iOS simulator, but can run on real device.

Both flutter run --debug and Run in Xcode shows the same error.
ld: targeted OS version does not support use of thread local variables in l1862 for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Please add the output of flutter doctor -v.

[✓] Flutter (Channel master, v0.10.2-pre.30, on Mac OS X 10.14 18A391, locale en-HK)
• Flutter version 0.10.2-pre.30 at /Users/edwardwong/flutter
• Framework revision b63ced55b4 (4 hours ago), 2018-10-22 19:20:17 -0700
• Engine revision 4c79e423dc
• Dart version 2.1.0-dev.7.1.flutter-45f9462398
[✓] Android toolchain - develop for Android devices (Android SDK 28.0.3)
• Android SDK at /Users/edwardwong/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-28, build-tools 28.0.3
• ANDROID_HOME = /Users/edwardwong/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
• All Android licenses accepted.
[✓] iOS toolchain - develop for iOS devices (Xcode 10.0)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 10.0, Build version 10A255
• ios-deploy 1.9.2
• CocoaPods version 1.5.3
[✓] Android Studio
• Android Studio at /Applications/Android Studio 3.3 Preview.app/Contents
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
[✓] Android Studio (version 3.2)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 29.0.2
• Dart plugin version 181.5540.11
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
[✓] IntelliJ IDEA Ultimate Edition (version 2018.2.5)
• IntelliJ at /Applications/IntelliJ IDEA.app
• Flutter plugin version 29.1.3
• Dart plugin version 182.4999
[!] VS Code (version 1.28.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension not installed; install from
https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (2 available)
• Edward’s iPhoneX • 8c0a6d19b6856c4e927e583deeeedc710c651506 • ios • iOS 12.0.1
• iPhone XS Max    • C2F247F8-F6BC-433F-AED4-69CD1F2B3A9A     • ios • iOS 12.0 (simulator)
! Doctor found issues in 1 category.

The issue if fixed by changing the Deployment Target from 8.0 to 9.0 in Xcode. It is a weird one.

The issue if fixed by changing the Deployment Target from 8.0 to 9.0 in Xcode. It is a weird one.

still got this error on 10.0 in Xcode

The issue if fixed by changing the Deployment Target from 8.0 to 9.0 in Xcode. It is a weird one.

still got this error on 10.0 in Xcode


Animation problem with blit

Hello, I'm new to GitHub (and somewhat to python). I'm not sure but I report what seems to be an issue for me. I am using Python 3.5.1 32bits Qt 4.8.7, PyQt4 (API v2) 4.11.4 on windows,  with the spyder I-python console 2.3.8, comming from the Anaconda installation which I have downloaded some days ago.
I have exactly the sames installations on my desktop computer and my leptop, and I have tried to run the attached python code taken from the Pyplot animation examples. On the desktop computer (native 32bit), it runs without problem, but on the leptop (native 64 bit), the animation does not work, unless I set the "blit" option to False in the animation.funcAnimation function (and then, the animation is somewhat slow). Attached is the code.
double_pendulum_animation.txt

You need to change the matplotlib backend to run animations, with
%matplotlib qt5

in an IPython console.
Sorry for the (very) late response.


Develop

contact / reach us : fixed
backstrech : fixed
.contact class is not responding , thus making a big gap between heading and envelope
nor its media query
Mohit : don't close any request without approval of the TITIKSHA _ TEAM as you did earlier

It's Approved dear !
We have decided to keep plain background in Gallery,
So it will be corrected in next PR

it's not we..... it's without mbj36