Implementing script when having multiple platforms

Hello,
I hope you can help me out.
I have this config file:

{
"bridge": {
"name": "Homebridge",
"username": "CC:21:3E:E4:DE:33",
"port": 51826,
"pin": "031-45-154"
},
"platforms": [{
"platform": "KlikAanKlikUit",
"driver": {
"type": "rpi",
"pin": 11
},
"accessories": [{
"name": "Spotjes zolderkamer",
"type": "Lightbulb",
"dimmable": false,
"address": "M",
"device": 1
},
{
"name": "LED lamp",
"type": "Lightbulb",
"dimmable": true,
"address": 5201,
"device": 2
},
{
"name": "LEDstrip keuken",
"type": "Lightbulb",
"dimmable": true,
"address": 5202,
"device": 3
}
]
}
]
}

Now I want to add this accessory into the config file:

"accessories": [
{
"accessory": "MagicHome",
"name": "LED Strip",
"ip": "<IP_ADDRESS>",
"setup": "RGBWW",
"purewhite": false
}
]

Please, can you help me how to write a working config file for me?
Thanks in advance.

Okay,  I have some questions before I can help you.
What's your hardware that you want to add? Pictures help. Does it have RGB plus a dedicated cold white and a dedicated warm white?
Have you installed the homebridge magichome plugin?
Lastly, homebridge magichome doesn't work perfectly with RGBWW (5 channel) lights. You will need to make some modifications or download my version of flux_led.py and index.js from github to get it to work.
Let me know

On Jul 7, 2017, at 9:54 AM, pjansen75<EMAIL_ADDRESS>wrote:
Hello,
I hope you can help me out.
I have this config file:
{
"bridge": {
"name": "Homebridge",
"username": "CC:21:3E:E4:DE:33",
"port": 51826,
"pin": "031-45-154"
},
"platforms": [{
"platform": "KlikAanKlikUit",
"driver": {
"type": "rpi",
"pin": 11
},
"accessories": [{
"name": "Spotjes zolderkamer",
"type": "Lightbulb",
"dimmable": false,
"address": "M",
"device": 1
},
{
"name": "LED lamp",
"type": "Lightbulb",
"dimmable": true,
"address": 5201,
"device": 2
},
{
"name": "LEDstrip keuken",
"type": "Lightbulb",
"dimmable": true,
"address": 5202,
"device": 3
}
]
}
]
}
Now I want to add this accessory into the config file:
"accessories": [
{
"accessory": "MagicHome",
"name": "LED Strip",
"ip": "<IP_ADDRESS>",
"setup": "RGBWW",
"purewhite": false
}
]
Please, can you help me how to write a working config file for me?
Thanks in advance.
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks for your respons.
See picture of what kind of RGB controller I have, it's an UFO.

In the meantime I managed to make a working config.json file, but I can not change color of the UFO. Then the config will crash and I have to reboot my RaspberryPi3. So, I need to make some modifications you suggest? Maybe, you can help me with that?
Thanks in advance.

This doesn't help me at all. I have no idea what that thing is. There are
too many types of controllers for me to know what you have. Show me the
outputs of the device. Where and how do you plug it in. What kind of LEDs
are you using.  Join me on https://homebridgeteam.slack.com and add me
@lethegrin so we can speak in real time.
On Sat, Jul 8, 2017 at 1:54 AM, pjansen75<EMAIL_ADDRESS>wrote:

Thanks for your respons.
See picture of what kind of RGB controller I have, it's an UFO.
[image: ufo]
https://user-images.githubusercontent.com/29973478/27982976-58645562-63b2-11e7-9ea4-d45c5940dea9.jpg
In the meantime I managed to make a working config.json file, but I can
not change color of the UFO. Then the config will crash and I have to
reboot my RaspberryPi3. So, I need to make some modifications you suggest?
Maybe, you can help me with that?
Thanks in advance.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/steve228uk/homebridge-magichome/issues/19#issuecomment-313836335,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYk1117uH5gIkcGcw22KTlLOGM7tyQmks5sLxmvgaJpZM4OQ-M0
.

It is the same controller as in the discussion of "LEDENET UFO".
I found out that I have to use RGBWWv3 as setup value in the config.json. Then Homekit is stable. I connected a RGB led strip to this controller and it is working with the app "Magic Home" from the Appstore. Everything is working fine then, but I can not change color via Homekit. (Homebridge).
I hope this is enough information? :-)

I don't use this controller but I'm willing to bet it works exactly like
the one I use seeing how you are getting the same problems I had.
*Step One: *
Delete everything in your config.json and replace it with this. Fix the IPs
as neccisary.
{
"bridge": {
"name": "MY COOL HOMEBRIDGE NAME",
"username": "CC:54:3D:E3:CE:30",
"port": 51826,
"pin": "123-45-678"
},
"accessories": [
{
"accessory": "MagicHome",
"name": "Light 1",
"ip": "<IP_ADDRESS>",
"setup": "RGBWW",
"purewhite": true
},
{
"accessory": "MagicHome",
"name": "Light 2",
"ip": "<IP_ADDRESS>",
"setup": "RGBWW",
"purewhite": true
}
]
}
Step Two:
Download my version of magichome here
https://github.com/Lethegrin/homebridge-magichome and extract flux_led.py
and index.js which fixes these lights for RGBWW 5 channel lights. If you
are downloading to a windows based system make sure your line endings don't
get converted to windows line endings. Make sure they are UNIX line endings
for both files. Replace both of these files in your homebridge-magichome
folder on your pie.Use the chmod command on flux_led.py so linux knows it's
an executable.
  That's why I asked for the LED strip type.  A
picture of your actual LIGHTS not the controller would be useful.
Let me know if this works
On Sat, Jul 8, 2017 at 6:25 AM, pjansen75<EMAIL_ADDRESS>wrote:

It is the same controller as in the discussion of "LEDENET UFO".
I found out that I have to use RGBWWv3 as setup value in the config.json.
Then Homekit is stable. I connected a RGB led strip to this controller and
it is working with the app "Magic Home" from the Appstore. Everything is
working fine then, but I can not change color via Homekit. (Homebridge).
I hope this is enough information? :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/steve228uk/homebridge-magichome/issues/19#issuecomment-313847691,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYk1_0K8dyUcS09cAjUkLeVmX-9gSuAks5sL1kxgaJpZM4OQ-M0
.

Hi,
I tried what you asked me, but I get an error after I replaced the two files.

You replaced these files in the homebridge-magichome folder right?  That is
located in /usr/local/lib/node_modules/homebridge_magichome . Sorry, it's
just so hard for me to know whats going on without seeing it directly.
On Sat, Jul 8, 2017 at 7:54 AM, pjansen75<EMAIL_ADDRESS>wrote:

Hi,
I tried what you asked me, but I get an error after I replaced the two
files.
[image: img_1121]
https://user-images.githubusercontent.com/29973478/27985099-f0d5351e-63e4-11e7-812a-47469538a330.JPG
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/steve228uk/homebridge-magichome/issues/19#issuecomment-313851572,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYk1xoW4-T1SdQ9rNojJ33mz9x5p40hks5sL24MgaJpZM4OQ-M0
.

Yes, that's right. I placed it there.
I appreciate your efforts. Thank you.


Python use old version of OpenSSL?

Checklist

[x] I'm asking a question
[ ] I've looked through the README and FAQ for similar questions
[ ] I've searched the bugtracker for similar questions including closed ones

Question

Hello. I used macOS Sierra 10.12.6. I DON'T USE HOMEBREW! I tried to download from Vimeo and got this:
ERROR: Unable to download webpage: <urlopen error [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:590)> (caused by URLError(SSLError(1, u'[SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:590)'),))
It's because OpenSSL version supplied with macOS out of date. So I updated openssl like this:
$ curl -O https://www.openssl.org/source/openssl-1.1.1b.tar.gz

$ tar -zxvf openssl-1.1.1b.tar.gz
$ cd openssl-1.1.1b

$ ./config

$ make

$ sudo make install
After that, I check openssl version:
$ openssl version
OpenSSL 1.1.1b  26 Feb 2019
And check where is it:
$ which openssl
/usr/local/bin/openssl
But error exists anyway. Then I check what version python used:
$ python -c 'import ssl; print(ssl.OPENSSL_VERSION)'
OpenSSL 0.9.8zh 14 Jan 2016
It's old out of date version!
Question: how can I tell the python (and other apps that may use openssl) use the new version?

You must build python agains this openssl version yourself or get it from somewhere.

Sorry, don't understand you. Can you explain more?

Tried a new Python version for macOS (from the official Python website)?

Yes, but same error

what should I do?

Same issue, any help is welcome.


TypeError: init() missing 2 required positional arguments: 'url' and 'message'

The above error is suddenly reported during the model training，Help!!
how to solve this proplem!

Hello @LilySys. Could you follow the issue templete to provide more information, like the mmdet, mmcv, and pytorch version and your environment.


ibeat analytics

ibeat.indiatimes.com is blocked by our list, but following are not blocked,

api.ibeat-analytics.com
ibeat-analytics.com

ibeat analytics belongs to indiatimes (a news site)

https://amp.dev/documentation/guides-and-tutorials/optimize-and-measure/configure-analytics/analytics-vendors/
Transcription (click to expand)
Ibeat Analytics
Type attribute value: ibeatanalytics
Adds support for Ibeat Analytics. More details for adding Ibeat support can be found at Ibeat Integration Support

urlscan.io report
AlienVault report

Thanks @bnainar I think this is ok.  It's not our mission to deplatform companies in legal industries, just intercept their vectors for analytics and shenanigans.  The root domain and the api domain aren't malicious domains, or are they?

just intercept their vectors for analytics and shenanigans
I call blocking:
<IP_ADDRESS> api.ibeat-analytics.com
<IP_ADDRESS> ibeat-analytics.com
right on target and far from deplatforming,in my opinion,of course 😉


[Incremental Imports; performance] Reserve use capacity when deserializing module dep graph

Reserve space in the usesByDef dictionary. May reserve too much.

Can't prove that it pays off; closing.


Device.platform not defined: code breaks after recent change unless one builds new jaxlib not

After pulling the latest version I see an error for any execution (AttributeError: 'jaxlib.xla_extension.CpuDevice' object has no attribute 'platform'.)
I believe that problem is that #1762 relies on very recent changes in the Tensorflow xla_client (adding Device.platform field in https://github.com/tensorflow/tensorflow/commit/72e362bba74a617dfdd326ecae299a6588247e1a), while I had jaxlib version 0.1.32.
Should we at a minimum upgrade the minimum_jax_lib to 0.1.36 (it is 0.1.31)?
How is it guaranteed that a jaxlib with 0.1.36 will include a particular change from xla_client, e.g., if one builds from source?
====
The actual bug is, for np.sin(3.0) produces:
  File "/Users/necula/Source/jax/jax/lax/lax.py", line 166, in sin
    return sin_p.bind(x)
  File "/Users/necula/Source/jax/jax/core.py", line 150, in bind
    return self.impl(*args, **kwargs)
  File "/Users/necula/Source/jax/jax/interpreters/xla.py", line 141, in apply_primitive
    return compiled_fun(*args)
  File "/Users/necula/Source/jax/jax/interpreters/xla.py", line 189, in _execute_compiled_primitive
    input_bufs = [device_put(x, device) for x in args if x is not token]
  File "/Users/necula/Source/jax/jax/interpreters/xla.py", line 189, in <listcomp>
    input_bufs = [device_put(x, device) for x in args if x is not token]
  File "/Users/necula/Source/jax/jax/interpreters/xla.py", line 85, in device_put
    return device_put_handlers[type(x)](x, device)
  File "/Users/necula/Source/jax/jax/interpreters/xla.py", line 94, in _device_put_array
    return xc.Buffer.from_pyval(x, device, backend=xb.get_device_backend(device))
  File "/Users/necula/Source/jax/jax/lib/xla_bridge.py", line 150, in get_device_backend
    platform = device.platform if device else None
AttributeError: 'jaxlib.xla_extension.CpuDevice' object has no attribute 'platform'

BTW, this problem goes away on a recompile from source, presumably also if updating to jaxlib 0.1.36

The remaining questions are:

How is it guaranteed that a jaxlib with 0.1.36 will include a particular change from xla_client, e.g., if one builds from source?

What process we need to have to tell that we need to bump the minimum version?

For the former question, it is simply a question of looking at the TensorFlow git hash in the WORKSPACE file. e.g., right now it is:
https://github.com/google/jax/blob/8547050b09318414190b88d29a2d0914ccc325a3/WORKSPACE#L24
which has git hash 883b5becaced22f7dd9e3c23d9d259f55e087cb5 and which corresponds to https://github.com/tensorflow/tensorflow/commit/883b5becaced22f7dd9e3c23d9d259f55e087cb5
One way to test the latter would be to pin the oldest legal jaxlib version in the travis configuration. We'd then see presubmit errors if a jax PR required a newer jaxlib.


Fix build script to work with VS2019

The main change is to try to find msbuild using the 'Current' version
instead of the '15.0' version.  The MSBuild team has stated that
'Current' will be used going forward to avoid a breaking change to the
path when the version revs.
Also necessary in this change was to drop the /toolsVersion flag from
msbuild.  It was passing 15.0 but that tools version is not recognized in the
current MSBuild.
Lastly, added the UWP.Support component as a required build component.
When the build script picks an instance of VS missing this feature, the build
will fail when trying to import Microsoft.Windows.UI.Xaml.CSharp.Targets.

I submitted this as a possible fix for #605 before waiting for all the tasks in #606 to be completed.  This issue has been filed a few times and is a pain point trying to debug the test framework or make other contributions.

@jimmylewis The changes seem to have broken the build. Can you please take a look

There you go https://dev.azure.com/vstestplatform/TestFx/_build/results?buildId=769


website

i would like to do that :+1:

do it

@necatikartal I've created website gh-page branch http://okulbilisim.github.io/awesome-datascience/
Düde, it's your turn!

Ok, I'll do it as soon as I can! :+1:

you have only 7 days to do it :) my little intern :clock1: :bomb:

it's on the way :+1:

bump

working on it; layout is ready but content and some fixes are still missing.

:bomb:


fix: show deprecation warning in help when using deprecated alias

Show standard deprecation warning in help when using a deprecated alias
@W-14208399@
Fixes https://github.com/oclif/core/issues/800

QA: I see the warning at the top of the help.  Looks good.


About training scripts.

Hi,
Thanks for sharing your code.
I plan to reproduce your results for RL methods in your paper.
However, in my previous experiments, I find it non-trivial to reproduce the results of models like MRT or RL in NMT, where it needs careful tuning of hyper-parameters to make these methods work.
I'm wondering if you can release some of your training scripts to help reproduce the results?

Hi,
thanks a lot for your interest!
Yes, the models are very sensitive to hyper-parameters!
I uploaded example configs for MRT and PG in the configs directory.
You can then select them during training, e.g. python3 -m joeynmt train configs/mrt_cross_domain.yaml
The training procedure is described in the official Joey NMT repository or in greater detail in the documentation.

Hi,
thanks a lot for your interest!
Yes, the models are very sensitive to hyper-parameters!
I uploaded example configs for MRT and PG in the configs directory.
You can then select them during training, e.g. python3 -m joeynmt train configs/mrt_cross_domain.yaml
The training procedure is described in the official Joey NMT repository or in greater detail in the documentation.

Great! Thanks for sharing!


ModuleNotFoundError

ModuleNotFoundError: No module named 'atom3d.datasets.ppi'

Same. Have you fixed this bug?

ModuleNotFoundError: No module named 'atom3d.datasets.ppi'

Same. Have you fixed this bug?

Found the same issue, can you fix it?

https://github.com/drorlab/gvp-pytorch/issues/5 this link maybe helpful


llama build stack fails with image-type docker due to wrong build context

I just installed the package with:
uv python pin 3.10.14
uv init
uv add llama-stack

This installed llama-stack==0.0.36 and its dependencies in .venv.
Then, after activating the virtual environment, I tried to run llama build stack with name my-local-stack, image type docker, and the reference implementations for the remaining options.
The docker build command failed:
+ docker build -t llamastack-my-local-stack -f /tmp/tmp.1BizPTWiy8/Dockerfile /home/carlos/Documents/test-workspace/llaming-around/.venv/lib/python3.10/site-packages
...
Dockerfile:16
--------------------
  14 |     # ENTRYPOINT ["python", "-m", "llama_stack.distribution.server.server"]
  15 |
  16 | >>> ADD .venv/lib/python3.10/site-packages/llama_stack/configs/distributions/docker/my-local-stack-build.yaml ./llamastack-build.yaml
  17 |
--------------------
ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref 5ba41c90-7513-48ee-a463-b1298c362883::zkxo9raxwxt0u06pbwzmhlxob: failed to walk /var/lib/docker/tmp/buildkit-mount3331234773/.venv/lib/python3.10/site-packages/llama_stack/configs/distributions/docker: lstat /var/lib/docker/tmp/buildkit-mount3331234773/.venv/lib/python3.10/site-packages/llama_stack/configs/distributions/docker: no such file or directory

Basically, the *-build.yaml file is not found because the docker builder context is the site-package folder within .venv but the first path in the ADD instruction is relative to the repo directory.
I modified this line:
https://github.com/meta-llama/llama-stack/blob/c8fa26482d5919365152e6bc2273c694847a5e5f/llama_stack/distribution/build_container.sh#L106
so now it reads:
add_to_docker "ADD llama_stack/configs/distributions/docker/$build_name-build.yaml ./llamastack-build.yaml"

It builds the image now!
Is this the correct way to fix the command? I can do a PR if necessary.

I manually tagged it via: docker image tag llamastack/llamastack-local-gpu llamastack-local-gpu

Thanks for raising the issue! This have been fixed in https://github.com/meta-llama/llama-stack/commit/ca7602a64289d272c20f4e702767caecb1fcafcf


Cleanup javadoc issues

coverage: 87.3% (-0.009%) from 87.309%
when pulling 08c197e262b1d8c3a7943d4cf846a075323fedef on hazendaz:pom-cleanup
into 78098db6be1c10b8c741e7f0c28d082680b8982a on mybatis:master.


[X11] Detect XWayland and disable screen capture support.

Adds XWayland detection.
Adds X error handler for capture methods.

Calling XGetImage on XWayland either cause error spam, or crash app, or crash the whole Wayland session.
Fixes #91632
Fixes #88550, at least when running in single window mode (will use app legacy app window color picker), multi window mode is completely unusable on XWayand and was not tested.

Fixes #88550, at least when running in single window mode (will use app legacy app window color picker), multi window mode is completely unusable on XWayand and was not tested.

Tested on XWayland with multi window mode, it seems to fall back to the legacy app window color picker, which seems to be a good compromise.

In windowed mode, the background of the window turns black:

Tested on Wayland with the Wayland display driver, there it looks a bit better:

Thanks!


Missing commandline option

I am opening wireguird via startup and I would like to amend the wish-list either with a commandline option "--hide" to move it straight the task bar or an option in the settings.
Everything else works very nice!

Added an option to start to tray on the new settings window.


Transform one input message into multiple different output messages

Hey Jeff, first of all, thank you for building this amazing tool, it has saved me a lot of time.
Now, onto the question I could not find an answer in the docs, or maybe overlooked. As the title suggest, is it possible to get one input message, process it, and output multiple ones?

Is this something Benthos can do, or is it not a "mundane" enough task? I'd appreciate any ideas you have, thanks!

Hey @nenad, this is definitely a boring task and very much up our street. This requires a two step process, the first is use Bloblang to map your individual messages as an array, then use the unarchive processor with the format json_array in order to break the array out into individual messages, there's an outline of it here: https://www.benthos.dev/docs/guides/bloblang/advanced#message-expansion
In your case it'll look something like this:
pipeline:
  processors:
    - bloblang: |
        let doc_root = this.without("data")
        root = this.data.Resources.map_each($doc_root.merge(this))
    - unarchive:
        format: json_array

Thank you!


SearchGUI produces empty result

Running search_gui <IP_ADDRESS> and get an empty output (0 bytes) .. the tool is shown as successful (green).
stdout
X!Tandem,MSGF,OMSSA
DB: CBDB1_Proteome.fasta sequences: 1458
Spectrums:FileConverter on data 15: out(API:e0ad502b326926d4)
Setting paths
Path configuration completed.
Creating decoy database.
Reindexing: input_database.fasta.

Picked up _JAVA_OPTIONS: -Xmx6g -Xms256m
Picked up _JAVA_OPTIONS: -Xmx6g -Xms256m

stderr
cp: cannot stat â€˜input_database_concatenated_target_decoy.fastaâ€™: No such file or directory

In order to make the tool catch the error: For the cp: the commands in the tool command block should be separated by && or the tool profile should be >=20.09.
But I guess the error is elsewhere.

The original problem seems to be fixed + follow up fix here: https://github.com/galaxyproteomics/tools-galaxyp/pull/572


Tuya Storage decryption

Is it possible to decrypt the Tuya Storage partition?
I am certain it contains the device ID and possibly other information as flashing a Tuya storage partition from one device to another changes said device ID.
It would be great to be able to edit and rebuild this partition in order to repair devices.
Attached my flash.bin (added .txt in order to upload)
flash.bin.txt

It is already supported by the UPK2ESPHome plugin for LTChipTool.  It is included with the binaries in the release section, or can be installed via pip with pip install upk2esphome

Unfortunately I did try this however it did not dump the device ID at all. Device ID looks similar to bf8b7201xxxxxxb69b9ucc.

Look at the source data.

This particular device doesn't have an activated device id in storage (which means it wasn't joined to Smart Life at the time it was dumped).
uuid and authkey are present, which is how it communicated with Tuya's API to generate a device ID.

I see, had no idea that it generated a device ID by talking to the Tuya API. Was not able to find much information on that. Thanks for the information.
Yeah, this was a dump of a downlight before it was setup so it did not contain passwords etc.
Changing the UUID and authkey would therefore generate a different device ID correct?
I will analyse a dump from a configured device.

The UUID and authkey are Tuya secrets per device, they must match, or communication will fail.  The schema that is returned with the device id is attached to the uuid and authkey.  The device id is generated each activation.  The device has no local schema until it has been activated.

Okay I do see the ID after analysing a dump from a configured device.
How would one go about generating a matching UUID and authkey then?
I assume there would be a process when initially developing the device.

That is a secret defined by Tuya and attached to their license, it is not something that can just be generated.  Every device has a unique UUID/authkey combo.  UUID and authkey are only used in communication encryption until a device id is assigned, then it switches to seckey which is attached to the device id.

I signed up to the Tuya cloud and generated a couple of free UUID and authkey pairs.
What would be the best way to update the originals with these?

There is no easy existing way to do this.  All the tools around just read storage data.  You'd need to adapt them for editing, re-encrypted, writing, and crc checks.  No 3rd party firmwares use Tuya's native storage for writing.
CloudCutter somewhat does this by exploit and using Tuya's SDK functions to overwrite that data, but it has limitations (cloudcutter is using smaller data fields and is limited in the size of data the exploit can carry as a payload).

I have managed to decrypt and re-encrypt the Tuya storage partition. Doing a byte to byte comparision before and after shows no differences and it works upon flashing.
However upon modification before re-encryption it seems to crash on bootup. Looking through the bootup log shows the following:
[01-01 18:12:18 TUYA Err][lr:0xa803d] kvs_read fails gw_bi -1
[01-01 18:12:18 TUYA Err][lr:0xac82b] base read fail:-6914
[01-01 18:12:18 TUYA Err][lr:0xad16f] ERR_EXIT is Jumped!
[01-01 18:12:18 TUYA Err][lr:0x65ad5] tuya_iot_wf_soc_dev_init err:ffffe4fe
[01-01 18:12:18 TUYA Err][lr:0x65adf] smart fram init error
[01-01 18:12:18 TUYA Err][lr:0x57fb7] ret:-6914

Interestingly kvs_read fails gw_bi -1 shows up several times even when booting a working flash backup.
base read fail:-6914 always shows even if I edit just a single byte before re-encryption. I even recalculate the checksum and update that too.
After a lot of playing around I believe there is something else in that partition that needs updating.
Here's the Tuya partition and decrypted Tuya partition. Read from offset 0x1EE000.
tuya.bin.txt
decrypted_tuya.bin.txt

In your decrypted_tuya.bin.txt, it appears your gw_bi and user_param_key are colliding.

Yeah, I think that's just how it looks when decrypted. Because that is unmodified, and when re-encrypting and flashing it works fine. Its just as soon as you modify it, the firmware spits out that error.
I tried editing another dump and it was the same issue.
Must be some other checksum in the file/partition?


Don't use bash as your entrypoint

Its doesn't handle signals properly:
https://blog.phusion.nl/2015/01/20/docker-and-the-pid-1-zombie-reaping-problem/

Given we exec runit at the end, I think we're okay.


Bug: utility function jsonify() does not handle datetime after 2.0.0 change

Describe the bug
I originally opened an issue on the surreal/surrealdb repo.
after 2.0.0 SurrealDB no longer eagerly converts a string into a datetime. An implicit d prefix or cast using  is required instead.
Steps to reproduce
      await db.insert("solar_metrics", {
        ...message,
        timestamp: '${message.timestamp.toISOString()}',
        localTimestamp: '${message.localTimestamp.toISOString()}',
      })

...

const fmtMsg = jsonify(message)
      await db.insert("solar_metrics", fmtMsg)
...

Expected behaviour
the jsonify utility should handle the cast to datetime or prefix with d
If I send a raw insert with the d in surrealist, it works. Im just not sure how to do this with the SDK.
SurrealDB version
2.0.4 for macos on aarch64
JavaScript SDK version
1.0.6
Contact Details
No response
Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hey @omencat, this is expected behaviour. In the 1.0.0 version of the SDK and onwards you need to send over actual Date values to SurrealDB, and likewise will you receive values in that format going forwards. As for the jsonify utility, it is there to convert values in their native format to how SurrealDB would represent them in the previously used json protocol.
Hope this helps!


fix(explore): Double divider if no permissions for adding reports

SUMMARY
Fix displaying double divider in actions menu in explore if user doesn't have permissions for managing reports
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before:

After:

TESTING INSTRUCTIONS

Log in as a user without reports permissions
Verify that there is only 1 divider between "Share" and "View query" in actions dropdown in explore

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

CC @kasiazjc

Thanks! LGTM

Thanks! LGTM

Are there any other cases in which double divider can appear (for example cannot edit properties) and are they all covered by this change? @kgabryje

Other cases were covered


Include current src changes in the npm install

Hello Daniel,
we are looking for a way, we could get the latest changes of the ./src/* via npm install. Currently, even if a pull request is accepted for the file in ./src/ folder, we can't get the changes via npm, until they are also copied to root file or to ./dist/ folder as beta.
We can target your plugin directly via github url path in the package.json, so we can get to the up-to-date master branch, but it still only downloads the release or beta file.
This is probably due to the following package.json part:
  "files": [
    "jquery.dataTables.yadcf.js",
    "jquery.dataTables.yadcf.css"
  ],

Could we please somehow add also the latest src file to the package,json, so we can work with the latest changes in our project?
Thanks,
Rado

Hi
Use npm install yadcf@beta for the latest beta version (es5), it should include beta 0.9.4-beta.8
Daniel

Thanks for the hint,
setting "yadcf": "beta" in package.json did the trick. :)
Rado


Apply backend.result_type to arc*, cos*, divide, sin*, sum and tan*

The dtype promotion and compatibility rules:

Match the dtype inference from JAX.
When an integer input becomes a floating-point output, use backend.floatx() for the best attempt.
Make the best effort to support all dtypes for all operators in all backends (although this might introduce some overhead for checking).

Currently, the status of ops applied backend.result_type is as follows:

[x] abs
[x] absolute
[x] add
[x] all
[x] amax
[x] amin
[ ] append
[x] arange
[x] arccos
[x] arccosh
[x] arcsin
[x] arcsinh
[x] arctan
[x] arctan2
[x] arctanh
[x] argmax
[x] argmin
[x] argsort
[ ] array
[ ] average
[x] bincount
[ ] broadcast_to
[x] ceil
[x] clip
[ ] concatenate
[ ] conj
[ ] conjugate
[ ] copy
[x] cos
[x] cosh
[ ] count_nonzero
[ ] cross
[ ] cumprod
[ ] cumsum
[ ] diag
[ ] diagonal
[ ] diff
[ ] digitize
[x] divide
[x] dot
[ ] einsum
[x] empty
[x] equal
[x] exp
[ ] expand_dims
[x] expm1
[x] eye
[ ] flip
[ ] floor
[x] full
[ ] full_like
[x] greater
[x] greater_equal
[ ] hstack
[x] identity
[ ] imag
[ ] interp
[ ] isclose
[ ] isfinite
[ ] isinf
[ ] isnan
[x] less
[x] less_equal
[x] linspace
[x] log
[x] log10
[x] log1p
[x] log2
[x] logaddexp
[x] logical_and
[x] logical_not
[x] logical_or
[x] logspace
[x] matmul
[x] max
[x] maximum
[x] mean
[x] median
[ ] meshgrid
[ ] mgrid
[x] min
[x] minimum
[x] mod
[ ] moveaxis
[x] multiply
[x] nan_to_num
[ ] ndim
[ ] nonzero
[x] not_equal
[x] ones
[ ] ones_like
[ ] outer
[ ] pad
[ ] percentile
[ ] power
[ ] prod
[x] quantile
[ ] ravel
[ ] real
[ ] reciprocal
[ ] repeat
[ ] reshape
[ ] roll
[ ] round
[ ] sign
[x] sin
[x] sinh
[ ] size
[ ] sort
[ ] split
[x] sqrt
[ ] square
[ ] squeeze
[ ] stack
[ ] std
[x] subtract
[x] sum
[ ] swapaxes
[ ] take
[ ] take_along_axis
[x] tan
[x] tanh
[ ] tensordot
[ ] tile
[ ] trace
[ ] transpose
[x] tri
[ ] tril
[ ] triu
[ ] true_divide
[ ] vdot
[ ] vstack
[ ] where
[x] zeros
[ ] zeros_like

Codecov Report
Attention: 143 lines in your changes are missing coverage. Please review.

Comparison is base (e237f08) 78.81% compared to head (77052ea) 56.35%.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #18714       +/-   ##
===========================================
- Coverage   78.81%   56.35%   -22.47%
===========================================
  Files         336      336
  Lines       33591    33859      +268
  Branches     6579     6635       +56
===========================================
- Hits        26476    19081     -7395
- Misses       5540    13329     +7789
+ Partials     1575     1449      -126

Flag
Coverage Δ

keras
56.35% <52.01%> (-22.36%)
:arrow_down:

keras-jax
?

keras-numpy
56.35% <52.01%> (-0.04%)
:arrow_down:

keras-tensorflow
?

keras-torch
?

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

Files
Coverage Δ

keras/backend/numpy/numpy.py
99.20% <100.00%> (+0.13%)
:arrow_up:

keras/ops/numpy.py
95.88% <97.26%> (-0.03%)
:arrow_down:

keras/backend/torch/numpy.py
0.00% <0.00%> (-95.72%)
:arrow_down:

keras/backend/jax/numpy.py
30.34% <0.00%> (-69.18%)
:arrow_down:

keras/backend/tensorflow/numpy.py
30.36% <9.09%> (-66.07%)
:arrow_down:

... and 181 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Elastic Beanstalk deployment is not picking up the configurations from the deployment settings file

Describe the bug
Get this setting Application IAM Role: *** Create new *** after specifying the RoleArn for ApplicationIAMRole in the deployment settings file.
Deployment settings file
{
  "ApplicationName": "AppTest2",
  "RecipeId": "AspNetAppElasticBeanstalkLinux",
  "OptionSettingsConfig": {
    "BeanstalkApplication": {
      "CreateNew": true,
      "ApplicationName": "AppTest2"
    },
    "BeanstalkEnvironment": {
      "EnvironmentName": "EnvTest2"
    },
    "EnvironmentType": "LoadBalanced",
    "LoadBalancerType": "application",
    "ApplicationIAMRole": {
      "CreateNew": false,
      "RoleArn": "arn:aws:iam::xxxxxxxxxxxx:role/Admin"
    },
    "InstanceType": "m4.4xlarge"
  }
}

Expected Behavior
Deploys the application to Elastic Beanstalk with the specified configurations in the deployment settings file
Current Behavior
dotnet aws deploy --apply DeploymentConfigFile.json -d

AWS .NET deployment tool for deploying .NET Core applications to AWS.
Project Home: https://github.com/aws/aws-dotnet-deploy

Configuring AWS Credentials using AWS SDK credential search.
Configuring AWS region using AWS SDK region search to us-west-2.

Configuring Recommendation with: 'ASP.NET Core App to AWS Elastic Beanstalk on Linux'.

Current settings (select number to change its value)
----------------------------------------------------
1. Elastic Beanstalk Application: AppTest2
2. Environment Name:
        Environment Name: AppTest2-dev
3. Environment Type: SingleInstance
4. Application IAM Role: *** Create new ***
5. Service IAM Role: *** Create new ***
6. Environment Variables:

Reproduction Steps
dotnet aws deploy --apply DeploymentConfigFile.json
Possible Solution
No response
Additional Information/Context
The application deploys successfully with the specified Application IAM Role while using Visual Studio Publish to AWS... option
Version used
1.0.3+48ef3bc4ee
Operating System and version
Windows 10

@as14692 As part of releasing the public version of this tooling, we introduced a breaking change in the settings file schema that renamed the OptionSettingsConfig property to Settings. https://github.com/aws/aws-dotnet-deploy/pull/631
Please rename the property in your deployment settings file and try again. We will soon prioritize improving the documentation on how to create the deployment settings file.

Thanks @96malhar! It works for Linux deployment. However when I make the same change in the deployment settings file for AspNetAppElasticBeanstalkWindows recipe as given below, I get the following message
The Option Setting Item BeanstalkEnvironment does not exist as part of the ASP.NET Core App to AWS Elastic Beanstalk on Windows recipe

For more information, please visit our troubleshooting guide https://aws.github.io/aws-dotnet-deploy/troubleshooting-guide/.
If you are still unable to solve this issue and believe this is an issue with the tooling, please cut a ticket https://github.com/aws/aws-dotnet-deploy/issues/new/choose.

Deployment settings file for Windows
{
  "ApplicationName": "AppTest2",
  "RecipeId": "AspNetAppElasticBeanstalkWindows",
  "Settings": {
    "BeanstalkApplication": {
      "CreateNew": true,
      "ApplicationName": "AppTest2"
    },
    "BeanstalkEnvironment": {
      "EnvironmentName": "EnvTest2"
    },
    "EnvironmentType": "LoadBalanced",
    "LoadBalancerType": "application",
    "ApplicationIAMRole": {
      "CreateNew": false,
      "RoleArn": "arn:aws:iam::xxxxxxxxxxxx:role/Admin"
    },
    "InstanceType": "m4.4xlarge"
  }
}

You need to use the EnvironmentName instead of BeanstalkEnvironment whne using AspNetAppElasticBeanstalkWindows
{
  "ApplicationName": "AppTest2",
  "RecipeId": "AspNetAppElasticBeanstalkWindows",
  "Settings": {
    "BeanstalkApplication": {
      "CreateNew": true,
      "ApplicationName": "AppTest2"
    },
    "EnvironmentName": "EnvTest2",
    "EnvironmentType": "LoadBalanced",
    "LoadBalancerType": "application",
    "ApplicationIAMRole": {
      "CreateNew": false,
      "RoleArn": "arn:aws:iam::xxxxxxxxxxxx:role/Admin"
    },
    "InstanceType": "m4.4xlarge"
  }
}

See here for the recipe file

Works, thank you.


[FEATURE] Download all rules from your tenant

Good have feature!
Implementors should have the option to download all cloud rules and perform a test.
Something like this: https://developer.sailpoint.com/discuss/t/download-version-and-update-identitynow-cloud-rules/13593

@drosenbauer  Thank you for sharing your thoughts. It's great to have all the rules consolidated into a single location for users to download and test. Rather than having two separate projects, we can utilize the RDK to download rules from your tenant unified project for all cloud rules lifecycle management. If you are developing new rules, having access to a copy of the existing ones will make it easier for developers to reference them.


ConsulCatalog ignoring prefix option with catalog tags

What version of Traefik are you using (traefik version)?
traefik version
Version:      v1.2.1
Codename:     morbier
Go version:   go1.7.5
Built:        2017-03-27_03:19:40PM
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml...)?
docker + consul k/v + consulcatalog
What did you do?
Try to constrain console catalog auto configuration via tags but prefixed with a custom prefix.

Set the traefik.consulCatalog.prefix kv value in consul to foo.
Set the traefik.consulCatalog.contraints.0 kv value to hello-*
Register a service with the tag foo.tags=hello-foo
Start traefik configured to use the consul k/v as config source

What did you expect to see?
traefik should register the hello-foo service from above
What did you see instead?
traefik filters out saying the hello-* constraint is responsible
Notes
If the same test is run (with the same prefix set in the kv) but with the service being registered with the tag traefik.tags=hello-foo then the service is recognised by traefik as expected. It seems that only the default prefix is honored by traefik.
I should also note that I am brand new to Traefik so could just be configuring things completely wrong, in which case I apologise.

I'll close the issue due to inactivity but feel free to re-open if needed.


Does not bind LDAP user to model with custom guard

Laravel Version: v5.6.39
Adldap2-Laravel Version: v6.0.7
PHP Version: 7.2.8
LDAP Type: OpenLDAP

First of all, thank you for this awesome package!
Description:
We run a project with two separate user tables and auth providers (the Laravel default users for the admin panel, and a 'members' table for frontend users).
We are using the Adldap2 package for authenticating only our frontend users, which are set up with a custom guard frontend in config/auth.php.
Everything went super smooth (we use the DatabaseUserProvider and import users to our DB), also authentication works 👍.
The only problem we have now is, that the LDAP user is not being bound to our Laravel member model. The HasLdapUser trait is set on the model. $user->ldap stays null after a successful auth attempt.
I found out that in the BindsLdapUserModel class, you are checking for a 'guard' property on the event object.
// We'll retrieve the auth guard if available.
if (property_exists($event, 'guard')) {
   $guard = $event->guard;
}

dd($guard) // returns null

Binding actually works if I manually set $guard = 'frontend'; in this file. So now my question is, how does the event even get a guard property? Am I missing something?
Our LoginController is more or less untouched and uses the Laravel default logic. Only thing we do is override the guard method to return our custom guard:
protected function guard() {
   return Auth::guard('frontend');
}

Config
ldap_auth.php
return [

    'connection' => env('LDAP_CONNECTION', 'default'),
    'provider' => Adldap\Laravel\Auth\DatabaseUserProvider::class,
    'model' => RF\Member\Member::class,
    'rules' => [
        Adldap\Laravel\Validation\Rules\DenyTrashed::class,
    ],

    'scopes' => [
    ],

    'identifiers' => [
        'ldap' => [
            'locate_users_by' => 'mail',
            'bind_users_by' => 'dn',
        ],

        'database' => [
            'guid_column' => 'objectguid',
            'username_column' => 'email',
        ],

        'windows' => [
            'locate_users_by' => 'samaccountname',
            'server_key' => 'AUTH_USER',
        ],
    ],

    'passwords' => [
        'sync' => env('LDAP_PASSWORD_SYNC', false),
        'column' => 'password',
    ],

    'login_fallback' => env('LDAP_LOGIN_FALLBACK', false),
    'sync_attributes' => [
        'email' => 'mail',
        'name' => 'cn',
    ],

    'logging' => [
        'enabled' => env('LDAP_LOGGING', true),
        'events' => [
            \Adldap\Laravel\Events\Importing::class                 => \Adldap\Laravel\Listeners\LogImport::class,
            \Adldap\Laravel\Events\Synchronized::class              => \Adldap\Laravel\Listeners\LogSynchronized::class,
            \Adldap\Laravel\Events\Synchronizing::class             => \Adldap\Laravel\Listeners\LogSynchronizing::class,
            \Adldap\Laravel\Events\Authenticated::class             => \Adldap\Laravel\Listeners\LogAuthenticated::class,
            \Adldap\Laravel\Events\Authenticating::class            => \Adldap\Laravel\Listeners\LogAuthentication::class,
            \Adldap\Laravel\Events\AuthenticationFailed::class      => \Adldap\Laravel\Listeners\LogAuthenticationFailure::class,
            \Adldap\Laravel\Events\AuthenticationRejected::class    => \Adldap\Laravel\Listeners\LogAuthenticationRejection::class,
            \Adldap\Laravel\Events\AuthenticationSuccessful::class  => \Adldap\Laravel\Listeners\LogAuthenticationSuccess::class,
            \Adldap\Laravel\Events\DiscoveredWithCredentials::class => \Adldap\Laravel\Listeners\LogDiscovery::class,
            \Adldap\Laravel\Events\AuthenticatedWithWindows::class  => \Adldap\Laravel\Listeners\LogWindowsAuth::class,
            \Adldap\Laravel\Events\AuthenticatedModelTrashed::class => \Adldap\Laravel\Listeners\LogTrashedModel::class,
        ],
    ],
];

Hi, did you manage to solve this? I'm also facing a similar issue right now.

Hi @jschwendener, can you post your config/auth.php file?


Feature Request - ValidatePath option

Summary of the new feature/enhancement
There should be an easy option to validate path parameters.

As a developer I want to validate a path parameter with a keyword to stop using the same validation pattern over and over again.

At the moment I need to use this pattern all the time:
param (
    [ValidateNotNullOrEmpty()]
    [ValidateScript({
        if(-not (Test-Path $_)){
            throw
        }
    })]
    [string]
    $Path
)

I would like to replace it with something like this:
param (
    [ValidatePath()]
    [string]
    $Path
)

There was already a similarly issue #5647 which was bigger in scope than this.
Proposed technical implementation details (optional)
I'v tried my hand at creating this validator #10250

Are you going to handle any PowerShell provider? Or just the FileSystem provider? ValidatePath as a parameter validator should handle any provider, not just files.
I find myself wondering if this should be a validator. Internally if it requires invoking Test-Path again and again, that could be expensive when used at scale, and it's quite specific as far as validators go.
Since it seems from your example, and from the PR the way it is written right now, that your interest is in file/directory validation, I wonder if it would be better to have:

A pair of transformation attributes, [FileInfo()] and [DirectoryInfo()], that can convert a string into a corresponding FileInfo or DirectoryInfo object (these objects support string conversion already, but transformation attributes are necessary if we want these to support PSPath syntax as well).

A property validator, [ValidateProperty('PropertyName','Value')] that would validate that a particular object has a property with a particular value.

The property validator alone would be generally much more useful than ValidatePath, and would allow for something like this:
function Use-Directory {
    [CmdletBinding()]
    param(
        [Parameter(Position=0, Mandatory, ValueFromPipelineByPropertyName)]
        [ValidateProperty('Exists',$true)]
        [System.IO.DirectoryInfo]
        [Alias('FullName')]
        $Directory
    )
}
Get-Item C:\ | Use-Directory

If you wanted PSPath support as well, you could use the proposed [DirectoryInfo()] transformation attribute, and write it like this instead:
function Use-Directory {
    [CmdletBinding()]
    param(
        [Parameter(Position=0, Mandatory, ValueFromPipelineByPropertyName)]
        [ValidateProperty('Exists',$true)]
        [System.IO.DirectoryInfo]
        [DirectoryInfo()]
        [Alias('PSPath')]
        $Directory
    )
}
Get-Item C:\ | Use-Directory

As a developer I want to validate a path parameter with a keyword to stop using the same validation pattern over and over again.

The motivation is not clear because the pattern is as simple as Test-Path.

Correct. However, use of [ValidateScript()] is needlessly syntax-heavy and awkward. PowerShell is an administration tool for computer systems; built-in validation for paths should be provided out of the box, in my opinion. Additionally, having parameter validation for paths run on pre-compiled code is probably likely to give some performance benefits in parameter binding for what seems to be very little cost. 🙂

having parameter validation for paths run on pre-compiled code is probably likely to give some performance benefits in parameter binding for what seems to be very little cost.

The attribute will only slow down. If we want to be fast we should move from string paths to objects with pre-processed paths (like FileInfo)

More than ValidateScript? Really?
That kind of conversion could be done by the validation attribute anyway, couldn't it?

Potential problem with this idea.  If you send an entire pipeline full of paths, doesn't the validation have to succeed on all paths before command can commence?  In many cases that would not be desired to have all the paths checked before work starts, and that just one bad path prevents any of the process.  For single path arguments/pipelines its no big deal.   However, I think the thought process was that you could detect on your own if the path is bad, and display a better error message or take other action, better than just a simple validation.
Additionally, if the paths are validated at the binding of a large/long/slow script, the paths may be invalid by the time the script performs the work, so the script always needs to be prepared for dealing with the exception of a missing path anyway.
Validation of other kinds of inputs makes sense, because they are not moving targets.
So in short, you shouldn't even be using ValidateScript to validate a moving target such as a file path at binding time.  Instead you should be prepared to deal with file path issues using try/catch/finally or trap.
I could see wanting to validate if a path contains any invalid components or syntax, since on some OS's the syntax of a file path is different.
But these are just opinions...

@msftrncs indeed, but the same issue is faced with ValidateScript and Test-Path; it is up to the command implementor to determine if the path is critical or non-critical (whether it should terminate the whole pipeline as a parameter-binding issue).
In most cases where this would be used, the path argument would not be a pipeline parameter and typically critical to the command function. For example, a Write-Log command where it takes data / strings as pipeline input and writes to a single path.

@vexx32 The key difference between ValidateScript and a ValidatePath attribute that internally invokes Test-Path is visibility of the performance hit. I think built-in validators should be very performant and not invoke PowerShell to do their validation.
Also would ValidatePath return true if the item behind the path exists? Or if the path was valid? What about validation against a specific provider, since many functions are written to only work with a limited set (often just one) of providers? What about wildcard validation? There are many validation scenarios, and a single ValidatePath validator does not unambiguously define which one it validates.

Pretty simple to resolve all your concerns there, Kirk. Plenty of validators allow parameters, we can simply leave it up to the command implementer to decide exactly what they're after.
function Write-Thing {
    param(
        [Parameter(Mandatory)]
        [ValidatePath(<# MustExist #> $true, <# ProviderName #> 'FileSystem')]
        [string]
        $Path,

        [Parameter(Mandatory, ValueFromPipeline)]
        [object]
        $InputObject
    )
    process {
        Set-Content -Value $InputObject -Path $Path
    }
}


Multiple 2FA registrations per account

FYI - Related Mastodon feature request:
"Multiple 2FA registrations per account" (TOTP + U2F)
https://github.com/tootsuite/mastodon/issues/10149
Google Accounts is a good example of this flexibility.
With the ongoing decentralization, it is becoming more and more important that users of various systems may have a good level of security while also enabling themselves to recover from login problems on their own, without support/assistance. Multiple 2FA registrations alleviates this, among other practical uses.

I am using devise-two-factor in my project. I display the QR code there and the account holder can connect as many apps/devices as (s)he wants. I myself test usually with Authy and GA in parallel.

This feature would be great for shared accounts. We have an account for our Java User Group which is managed by two people. Unfortunately we can't use 2FA now.

Came here to suggest this -- adding my support. This would be a great feature.


Revert "Update babel-preset-es2015 to version 6.13.0 🚀"

Reverts ParsePlatform/parse-server#2460

Current coverage is 91.87% (diff: 100%)

No coverage report found for master at e4c2e65.

Powered by Codecov. Last update e4c2e65...648d349


Support custom TLS verification for KubeFedCluster and preserve setting from joining kubeconfig

A cluster that has InsecureSkipTLSVerify enabled in kubeconfig, can be joined but will fail due to TLS setting not being preserved on the KubeFedCluster resource.  There are cases where allowing relaxed TLS certificate verification is required.

/kind feature

Resolved by PR #1030


Github action to build helper docker base image

This builds base docker image of a helper using the current IPA code. We will then use this image to create helper node specific images.

I dont have permissions to run this action on main repo hence the failure. @martinthomson @akoshelev what is the best way to unblock? For reference, it does work on my personal repo : https://github.com/richajaindce/raw-ipa/actions/runs/5324489087


Logged errors in Github repo sync need more context

Description:

What issue is being seen?  Describe what should be happening instead of the bug, for example: Cartography should not crash, the expected value isn't returned, the data schema is wrong, etc.

I am seeing error logs that look like
[{'type': 'FORBIDDEN', 'path': ['organization', 'repositories', 'nodes', 93, 'collaborators'], 'locations': [{'line': 43, 'column': 21}], 'message': 'You do not have permission to view repository collaborators.'}]

I have confirmed that my Github PAT does have permission to view repository collaborators and as far as I can tell the sync actually runs to completion so I'm confused here.
In any case,

The log message should make it clear which asset is failing to be retrieved.
Since we don't currently treat this code path as a fatal error, we should consider reducing the log level to warning, or we could make it a fatal error.

To Reproduce:

Steps to reproduce the behavior.  Provide all data and inputs required to reproduce the issue.

Run github sync with a PAT that does have permission to view collaborators on a repo that has external collaborators.
Please complete the following information::

Cartography release version or commit hash [e.g. 0.12.0 or 95e8e11913e2a44a4d4682506d8364a638ceac69]
0.57.0rc1

cc: @ryan-lane

Well, unfortunately, there's a lot to unpack here. It could be a fatal error, or just a warning, depending. Since we're using the graphql API, it could be returning partial (but usable) results, or it could be returning nothing. We're seeing this now because previously, the response would be missing data and we'd raise an exception about the missing data. graphql puts the error message into the 200 response, so I exposed that error as a logged error so we could see why the query was failing.
I think switching it to a warning is fine, but I think in general, if anything is shown, it probably means you're missing some data that the module supports.


Setup instructions with contratospr-api?

This might be already in the works, but would be great to have a guide on how to run this locally with the API. https://github.com/TheIndexingProject/contratospr-api/blob/master/CONTRIBUTING.md#project-setup might be a good place to put it.

We'll need to bring over the contribution guidelines and issue/pr templates from contratospr-api It should be possible to run this project using the production api without having to run it locally, but if you do need to run both things we can point to the project setup section for contratospr-api


WSL apt-get upgrade not working anymore

Your Windows build number:  (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.16299.125]

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)
sudo apt-get upgrade

error message
The following packages will be upgraded:
apport firefox hdparm icu-devtools libavahi-client3 libavahi-common-data libavahi-common3 libicu-dev libicu57 libplymouth4 libssl1.0.0 libtiff5 libvorbis0a libvorbisenc2 libvorbisfile3
libwayland-client0 libwayland-cursor0 libwayland-server0 linux-libc-dev lshw nplan openssl patch plymouth plymouth-theme-ubuntu-text python3-apport python3-distupgrade
python3-problem-report systemd-sysv ubuntu-release-upgrader-core zsh zsh-common
32 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
2 not fully installed or removed.
Need to get 0 B/77.4 MB of archives.
After this operation, 20.5 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up systemd (234-2ubuntu12.3) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
[/usr/lib/tmpfiles.d/tmp.conf:15] Failed to replace specifiers: /tmp/systemd-private-%b-*
[/usr/lib/tmpfiles.d/tmp.conf:16] Failed to replace specifiers: /tmp/systemd-private-%b-/tmp
[/usr/lib/tmpfiles.d/tmp.conf:17] Failed to replace specifiers: /var/tmp/systemd-private-%b-
[/usr/lib/tmpfiles.d/tmp.conf:18] Failed to replace specifiers: /var/tmp/systemd-private-%b-*/tmp
dpkg: error processing package systemd (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

What's wrong / what should be happening instead:

There should be no errors

Try to fix with this commands:
sudo apt-get update –fix-missing
sudo apt-get update
sudo apt-get upgrade

Try to fix with this commands:
sudo apt-get install --fix-missing
sudo apt-get update
sudo apt-get upgrade


fail building ecl 21.2.1-1

When trying to build your ecl package, I got the following error: http://0x0.st/-407.txt. I think mv: can't rename 'libatomic_ops.a': No such file or directory is the critical part, but I'm not sure.
Is there something I'm doing wrong?

I can confirm this is an issue; It fails to build for me with the same error. I was able to successfully compile ecl when I pushed the package to the repo.
I'll see if I can fix this tonight

Just pushed a fix; ecl was able to compile on my machine, let me know if  you are able to compile it

ecl compiles fine now, thanks!


Unable to add other chains

Was giving this a go and trying to play around with some other chains but was unable to add a new chain other than the defaults.
I got a chain.json from the chain-registry repo
Selected this file using file picker in CW IDE
It shows the file selected
IDE still shows Oraichain for queryies and such
I click add new chain
I get error adding chain
No juno chain added

Can you show me the json file you added?  You can check a template in this repo

Did you create a PR for the chain?

At the moment, you need to create a PR submitting your network information. Afterward, we will review and merge it. Below is an example of the network's metadata:
{
"rpc": "https://testnet-rpc.orai.io",
"rest": "https://testnet-lcd.orai.io",
"chainId": "Oraichain-testnet",
"chainName": "Oraichain Foobar",
"stakeCurrency": {
"coinDenom": "ORAI",
"coinMinimalDenom": "orai",
"coinDecimals": 6,
"coinGeckoId": "oraichain-token",
"coinImageUrl": "http://localhost:3000/public/assets/tokens/orai.png"
},
"bip44": {
"coinType": 118
},
"bech32Config": {
"bech32PrefixAccAddr": "orai",
"bech32PrefixAccPub": "oraipub",
"bech32PrefixConsAddr": "oraivalcons",
"bech32PrefixConsPub": "oraivalconspub",
"bech32PrefixValAddr": "oraivaloper",
"bech32PrefixValPub": "oraivaloperpub"
},
"currencies": [
{
"coinDenom": "ORAI",
"coinMinimalDenom": "orai",
"coinDecimals": 6,
"coinGeckoId": "oraichain-token",
"coinImageUrl": "http://localhost:3000/public/assets/tokens/orai.png"
}
],
"feeCurrencies": [
{
"coinDenom": "ORAI",
"coinMinimalDenom": "orai",
"coinDecimals": 6,
"coinGeckoId": "oraichain-token",
"coinImageUrl": "http://localhost:3000/public/assets/tokens/orai.png"
}
],
"gasPriceStep": {
"low": 0,
"average": 0.0025,
"high": 0.004
},
"features": [
"stargate",
"ibc-transfer",
"cosmwasm"
],
"cosmwasmVersion": "0.13.2" // the cosmwasm std your network is using.
}
It follows the same format as that of Keplr so that the webview can work with the extension. We also add a few attributes, which include comments above.
Please append the network information into the config file if you prefer to let your network be included in the IDE permanently. Please note that this requires reviewing & a pull request. The IDE also provides a feature that helps you add and remove custom networks & store them locally.

@kleimanb81 submitting a PR is for adding the chain config permanently. Normally, the devs can add new chains using the "Add new chain" button

Oh really? Ty for letting me know. That's much less work than a pr for each.


Added new TC DeleteBackupOfUserNonSharedRBAC

What this PR does / why we need it:
Added new TC DeleteBackupOfUserNonSharedRBAC and Required Helper Functions
DeleteBackupOfUserNonSharedRBAC - https://portworx.testrail.net/index.php?/cases/view/87561
Which issue(s) this PR fixes (optional)
Closes #PA-1398
Special notes for your reviewer:
This PR doesn't contains 2.5.2 api
logs:
s3:
https://jenkins.pwx.dev.purestorage.com/job/portworx-backup/job/system-tests/job/byoc/job/px-backup-on-demand-system-test-byoc/2406/
Aetos Dashboard: https://aetos.pwx.purestorage.com/resultSet/testSetID/323498
NFS:
https://jenkins.pwx.dev.purestorage.com/job/portworx-backup/job/system-tests/job/basic-system-test/job/px/job/NFS/job/PX-Cloud-Vanilla-NFS/128/
https://aetos.pwx.purestorage.com/resultSet/testSetID/327353

Thanks for the reviews. These changes are now included in PR https://github.com/portworx/torpedo/pull/1669.


Set ActiveSupport::TestCase.test_order to avoid warning

Running the tests shows the following warning:
DEPRECATION WARNING: You did not specify a value for the configuration option `active_support.test_order`. In Rails 5, the default value of this option will change from `:sorted` to `:random`.
To disable this warning and keep the current behavior, you can add the following line to your `config/environments/test.rb`:

  Rails.application.configure do
    config.active_support.test_order = :sorted
  end

Alternatively, you can opt into the future behavior by setting this option to `:random`. (called from test_order at /Users/vladimir/code/foreigner/.bundle/gems/gems/activesupport-4.2.1/lib/active_support/test_case.rb:42)

this PR fixes that by setting the test order to :random (effectively following the second advice in the warning, and opting into the future behavior).

Thanks! I hadn't run the tests for quite a while.


ShouldBeUnique doesn't work with scheduled task "job()"

Hi there,
I found the ShouldBeUnique interface on a job not working if the job gets started by the task scheduler. My intention is to let a job run fairly often but avoid "overtaking", thus not even dispatching the following run if the previous is still running.
To reproduce, create a basic job:
class TestJob implements ShouldQueue, ShouldBeUnique
{
... // sometimes long running job
}

... and schedule it in app/Console/Kernel.php:
class Kernel extends ConsoleKernel
{
    protected function schedule(Schedule $schedule)
    {
        $schedule->job(new TestJob)->everyMinute();
    }
}

If the previous instance is still running, the task scheduler still dispatches the job; a congestion occurs.
If I instead schedule the job as follows, ShouldBeUnique works as intended and documented:
$schedule->call(function () { TestJob::dispatch(); }
		)->name('TestJob')->everyMinute();

If this behavior is intended, then I propose mentioning this in the documentation.
Thank you!

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


Documentation typo for --jpeg-ext EXTENSION

Minor one - the description for the jpeg-ext command uses jpg-ext instead of jpeg-ext
--jpeg-ext EXTENSION
Specify file extension for JPEG files. Photos uses .jpeg for edited images but many images are imported with .jpg or .JPG which can result in multiple different extensions used for JPEG files upon export.  Use --jpg-ext to specify a single extension to use for all exported JPEG images. Valid values are jpeg, jpg, JPEG, JPG; e.g. '--jpg-ext jpg' to use '.jpg' for all JPEGs.

Thanks!  I've fixed this in v0.40.6. I went back & forth on what to call this feature and settled on jpeg-ext as Photos defaults to jpeg but never fixed the docs.


Allow disabling nuitka in pyproject.toml builds.

What does this PR do?
When using pyproject.toml it is sometimes helpful to be able to switch between setuptools-based build and a Nuitka build without modifying the pyproject.toml.
Here, a configuration setting no-nuitka is added, which can be set to true, resulting in a bypass of nuitka during build.
This mechanism also works for the build package, using the --config-setting command line option.
Fixes #1600.
Summary by Sourcery
New Features:

Introduce a configuration setting 'no-nuitka' in pyproject.toml to allow bypassing Nuitka during the build process.

I noticed this one relatively late only, my bad. I rebased it to current develop, after I made the release rebase for 2.5, and am going to check it out now.

Really liking it, would add consistency if all 3 was of doing it, supported it. The name should ideally be the same. It's a pity that the parsing has to be done manually, but I guess, that's how it goes if Nuitka doesn't enter the picture, what else could do it.

I will put this into a hotfix of 2.5 easily, since it seems to have no risk.

I have a suspect, the setting ends up as a Nuitka option on the command line though, which then should be unknown, is that not true?

I am ignore build_with_nuitka in the options parsing from TOML file, then it ought to be good to toggle it on/off without removing the config value from the file.

Can you tell me if this works for you, then I can merge it.

So, 2.5. is delayed due to a regression I will need to fix, taking this in right away therefore.


Produce BIDS Derivatives-compatible outputs

We have a set of outputs of interest from AROMA, including:

Denoised 4D image, in native and standard space (possibly)
Metrics (feature scores)
Component time series
Component maps, in native and standard space (possibly)
Classifications (included with feature scores in "classification_overview.txt")
Figure

We should figure out how best to make those outputs BIDS Derivatives-compatible.
At minimum, I think we can use filenames that are basically BIDS-ish, like what I propose in https://github.com/ME-ICA/tedana/pull/574. This means using entities and suffixes that match BIDS convention, minus the "source entities" from the original files (e.g., sub, ses, run).
I don't know if we want to output the classifications/metrics as a json (as in tedana) or a tsv. A tsv would be easier to read...

I'm currently leaning toward the following outputs:

desc-ICA_decomposition.json
desc-ICA_mixing.tsv
desc-ICA_components.nii.gz
desc-ICAGammaThresholded_components.nii.gz
desc-smoothAROMAnonaggr_bold.nii.gz
AROMAnoiseICs.csv (if we keep them)
desc-AROMA_metrics.tsv (instead of the json)
desc-AROMA_metrics.json (metadata about metrics)
aroma.svg

What about the folder structure? My guess is the users will run it in their data folder, say sub-001/ses-01/func/. We should create a derivatives folder or something right?

Since we're planning to use this as a node in a BIDS App (e.g., fMRIPrep), I think we should dump things into an arbitrarily-named output folder. We can always develop a BIDS App version of the CLI at some point, if there's a demand. It's in the BIDS App version where I think we'd want to try to extract subject and session information, and then develop a folder and filename structure around that.

Since we're planning to use this as a node in a BIDS App (e.g., fMRIPrep), I think we should dump things into an arbitrarily-named output folder.

Yes, it is trivial then to have some manager code that transfers everything to the right position and applies bids-derivatives naming.

I'm currently leaning toward the following outputs:

desc-ICA_decomposition.json
desc-ICA_mixing.tsv
desc-ICA_components.nii.gz
desc-ICAGammaThresholded_components.nii.gz
desc-smoothAROMAnonaggr_bold.nii.gz
AROMAnoiseICs.csv (if we keep them)
desc-AROMA_metrics.tsv (instead of the json)
desc-AROMA_metrics.json (metadata about metrics)
aroma.svg

Yes, don't make it overly complicated - this should do!


Not an issue - Contributing Translations

Hi there, I'd like to contribute with the spanish translations, two versions, traditional spanish ("es") and latin american spanish ("ea" seems to be the code)
Im attaching a TXT file with everything, hope it's complete, I just left out the "Changelog"
translations.txt
Hope it helps and keep up with the great work

Thanks for your contribution! I added the translations to the main branch and created a new release. Can you confirm this zip file works properly with spanish localization? (I haven't tested it yet)
https://github.com/Timmeey86/FS22_UnloadBalesEarly/releases/tag/v<IP_ADDRESS>

Hi, glad you liked it! Unfortunately you have an XML error, an extra "<" on line 82 at the end.
Also, I dont understand why, the description doesnt appear in spanish in the download center

Thanks for pointing that out. I fixed the XML error and replaced the ZIP file in the release (just download it again).
I also removed the Spanish <description> since apparently the mod hub will only ever display German, French or English descriptions and default to English for any other language.
Additional languages are only supported within the game itself

Just to confirm, I tried the Fields of La Mancha map which has a Spanish description, and indeed, only the English text is displayed in the ingame mod hub

Ok, I can confirmed that translations looks OK

Hi @Timmeey86, i have also a full translation for IT (Italian language), please add this too in a next update (here and on modhub) 👍🏻
IT_translation.txt


Auto-Close Sidr on window.resize

If you open Sidr and then resize the browser (make it wider), the body still has it's inline-styles position:absolute, width, and so on.
Please add this to the plugin, so sidr is closed everytime, the browser-window is resized. This will avoid visual bugs.
window.onresize = function(){
jQuery.sidr('close', 'sidr-main'); // "sidr-main" should be replaced to something, that addresses all active Sidr-Containers.
}

Add those things by yourself, there is no need to include it in the plugin


Switching Cloudfront+S3 => Amplify with custom domain requires downtime

Region: eu-west-2
Step: Final Step
Status: Common issue across apps

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
This is not an issue with a specific domain, just one we've encountered during the migration of several static sites from S3 bucket + Cloudfront CDN hosting to AWS Amplify.
AWS Amplify persistently fails on the last step of domain activation when the domain is already associated as a cname on another resource (Cloudfront in our case). The only way to resolve this is to seemingly deactivate the cname(s) in Cloudfront, wait for the deployment to complete, then remove and re-add the domain to the chosen Amplify App.
This is far from ideal as it is commonplace for us to migrate our projects from the old S3+Cloudfront setup to Amplify, but this means we must have downtime in order for the domain to successfully be transferred over.
Additional Information
Route53 is the DNS provider we've been using in all cases.

The best process to follow to minimize downtime here would be:

In your Amplify Console app, open the domain management screen
Type in your root domain (yourdomain.com) and click configure
Click “Exclude root” button
Click “Remove” button next to the “www” sub domain that was automatically added
Click save
What we have now done, is started the process of creating and verifying a domain in Amplify Console, without adding any CNAMEs to the Amplify Console Cloudfront Distribution.
Now follow the instructions for setting up the verification CNAME so that your new custom domain will receive a SSL certificate.
While this process is completing, please check the TTL on the DNS records you are moving to Amplify Console. You want them to be as small as possible so that the change propagates quickly. If you have to change this value, please be sure to wait out at minimum, the original TTL before continuing, to make sure that your new TTL is in effect.
Once that is done and the domain is marked as available, you’re now ready to do the migration.

You will need to do the following in quick succession:

Change the DNS record
Remove the CNAME from your Cloudfront distribution.
Add the CNAME to Amplify Console by going to the domain management page, and clicking “Manage subdomains”
Doing it following this method you should see very little downtime, and will mainly depend on the TTL of the DNS record.

Thanks for the prompt response @swaminator – can you confirm what change you're suggesting is made in "1. Change the DNS record" is in the migration steps at the end?
Surely there's nothing needed on the DNS front at this point if:

You've already verified the domain via the CNAME verification
You've not yet removed the CNAME from Cloudfront (step 2)
You've not yet added the CNAME in Amplify Console (step 3)

Hi @CharlieHawker,
You are correct!
When adding the domain (or at any point after) to Amplify Console, you can add a test sub domain, something you don't use in production/elsewhere. This has 2 benefits:

It lets you test your domain and SSL certificate before cutting over traffice
Because your custom domain uses a single Cloudfront distribution for all sub domains, you can infer the destinations for the other records.

The other option would be to do the last 3 steps in a slightly different order:

Remove the CNAME from your Cloudfront distribution.
Add the CNAME to Amplify Console by going to the domain management page, and clicking “Manage subdomains”
Change the DNS record

The first and second steps can be done immediately after each other (you do not need to wait for the distribution to say Available again), so these two paths should have about the same amount of downtime, but the first one gives you the opportunity to test the site using your custom domain.
Please let me know if you have any other questions!

@anatonie amazing, this helped put the final piece of the puzzle together, thank you 🎉
Not sure if this issue should remain open? I'm reluctant to close as I feel that the issue I was having could be better explained by the web interface - particularly around offering help if there's a resource already linked to the subdomain you're trying to connect to Amplify.

@swaminator i was following same steps as above to move my s3 static website to aws amplify. subdomain is working fine where as actual domain https://example.com not working i am getting site cant be reached error can you able to help me here.
thanks in advance
sam


Uncaught TypeError: this.resultsPaneView.find is not a function

right click on search results
click on Toggle fold results

Error appears.
Atom: 1.16.0 x64
Electron: 1.3.13
OS: Mac OS X 10.11.6
Thrown From: fold-search-results package 1.0.5
Stack Trace
Uncaught TypeError: this.resultsPaneView.find is not a function
At /Users/lacoste/.atom/packages/fold-search-results/lib/ToggleSearchResults.js:57

TypeError: this.resultsPaneView.find is not a function
    at ToggleSearchResults.fold (/packages/fold-search-results/lib/ToggleSearchResults.js:57:46)
    at ToggleSearchResults.toggle (/packages/fold-search-results/lib/ToggleSearchResults.js:90:40)
    at HTMLDivElement.toggle (/packages/fold-search-results/lib/atom-fold-search-results.js:9:13)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/app.asar/src/command-registry.js:259:29)
    at CommandRegistry.handleCommandEvent (/app.asar/src/command-registry.js:3:59)
    at CommandRegistry.module.exports.CommandRegistry.dispatch (/app.asar/src/command-registry.js:160:19)
    at AtomEnvironment.module.exports.AtomEnvironment.dispatchContextMenuCommand (/app.asar/src/atom-environment.js:1185:28)
    at EventEmitter.outerCallback (/app.asar/src/application-delegate.js:325:25)
    at emitThree (events.js:116:13)
    at EventEmitter.emit (events.js:194:7)

Commands
     -2:44 project-find:show (input.hidden-input)
     -2:43.6.0 core:paste (input.hidden-input)
     -2:43.1.0 core:confirm (input.hidden-input)
     -2:39.3.0 atom-minify:close-panel (div.results-view.focusable-panel)
     -2:39.3.0 core:cancel (div.results-view.focusable-panel)
     -2:38.4.0 atom-minify:close-panel (div.results-view.focusable-panel)
     -2:38.4.0 core:cancel (div.results-view.focusable-panel)
     -2:20.9.0 atom-minify:close-panel (div.results-view.focusable-panel)
     -2:20.9.0 core:cancel (div.results-view.focusable-panel)
     -2:20.4.0 core:close (div.results-view.focusable-panel)
     -2:17.7.0 project-find:show (input.hidden-input)
     -2:16.1.0 core:confirm (input.hidden-input)
     -0:10.5.0 fold-search-results:toggle (li.search-result.list-item.selected)

Non-Core Packages
2-dark-syntax 1.1.0
advanced-open-file 0.16.6
atom-minify 0.8.0
atom-wrap-in-tag 0.6.0
autoclose-html 0.23.0
Base16-Chalk-Dark 0.1.0
breezy-dark-ui 0.1.0
busy-signal 1.3.0
change-case 0.6.5
color-picker 2.2.5
custom-title 1.0.1
dead-simple-light-syntax 0.1.0
emmet 2.4.3
erb-helper 1.1.0
file-icons 2.1.3
fold-search-results 1.0.5
git-blame 1.0.1
git-control 0.9.0
git-plus 7.5.0
git-split-diff-hyperclick 0.3.12
git-time-machine 1.5.9
gl-light-syntax 2.2.0
gloom 0.4.13
hyperclick 0.0.40
intentions 1.1.2
linter 2.1.4
linter-ruby 1.2.5
linter-ui-default 1.2.3
steam-pirate-syntax 0.4.0
monokai-one-dark-vivid-syntax 1.4.0
newbound-light-syntax 1.3.0
nucleus-dark-ui 0.11.17
oceanic-next 1.0.0
one-dark-dim-syntax 0.1.0
one-dark-material-syntax 1.0.3
one-dark-vivid-syntax 1.7.1
platformio-ide-terminal 2.5.0
pristine-ui 1.0.15
rails-partials 0.9.2
rails-rspec 0.3.2
rails-transporter 1.6.5
relative-numbers 0.7.1
ruby-test 1.0.1
script 3.14.1
set-syntax 0.3.2
snow-dark-syntax 0.1.1
specs undefined
split-diff 1.3.0
spring-dark-syntax 0.0.4
steam-pirate-syntax 0.4.0
styles undefined
titan-dark-syntax 2.0.0
tree-view-breadcrumb 0.8.1
tree-view-git-branch 0.1.2
two-light-ui 1.1.3
vim-mode-plus 0.89.0
vim-mode-plus-ex-mode 0.9.0
vim-mode-plus-keymaps-for-surround 0.2.1
vivid-syntax 2.1.0
vmp-gutter-annotate-mark 0.3.2

same here

Hi,
I don't plan to fix this myself, I don't have the time, and Atom added buttons that do the exact same job.
If one of you guys wants to do it, PRs are welcome!

cool I didn't notice that!
no need to bother then, If I were you I would deprecate this package and notify users about this native button in the readme.
a final update with a warning notification to remove the package would be a nice idea too to save your users some resources (and save yourself lots of issues here).
Whatever you decide to do, thanks alot for this package 👍

Since Atom core adds this functionality, I see no reason for this package and therefore closing this issue.  +1 to deprecate package, and thanks for making it as it was useful prior to this bug.


A way to update current project template

I don't think this would be feasible, but it would nice to keep up with rust-nix-templater future releases by regenerating the current project.
I'm going to update it manually soon and start using toml files for all my project configuration but wanted to share this pain point.

I implemented this with https://github.com/yusdacra/nix-cargo-integration. Currently what rust-nix-templater does is make a flake using nix-cargo-integration. To get new features and fixes all a user needs to do is nix flake update. The only pain point is that this doesn't apply to CI files, but they aren't updated as frequently as the Nix files so that is probably OK.

Agree, I think when the project becomes tstable this won't be an issue so closing for now


clock speed changes vs. capacitance vs. vreg voltage

Hardware: Raspberry Pico board
Power Supply: Anker PowerPort 6 with only the Raspberry Pico board connected
Test Case: Changing the sys clock from 48MHz USB PLL to 125 MHz SYS PLL
I have noticed that while executing the SDK function clock_configure() the system sometimes halts right at the point where the clock changes from the ring oscillator (intermediate step in the SDK function) to the target source (=SYS PLL) - that is line 98 in https://github.com/raspberrypi/pico-sdk/blob/master/src/rp2_common/hardware_clocks/clocks.c
The clock malfunction then leads to a watchdog reset.
The issue is related to the Anker PowerPort 6 since it neither occurs with an Apple charger nor with a Rocoren USB charger.
Nevertheless do I have some questions regarding this issue:

Does the Pico need additional capacitance on the 5V or 3V3 rail when the buck/boost converter is bypassed (in my case by an LDO)?
Should the VREG voltage be temporarily increased to 1.2V before doing big clock steps in clock_configure() - e.g. from 6 MHz ROSC to 125 MHz PLL?
Should big clock steps be splitted into smaller ones? I'm asking because STM32 devices running at a low voltage e.g. need about 5us at a certain clockspeed before switching to a higher one - to avoid an undervoltage situation.

Based on my tests it seems that splitting the ROSC -> PLL jump into smaller steps, by first using a bigger clock divider, then waiting a couple of cycles, then reducing the divider, then waiting again etc. seems to fix the issue - even with the Anker PowerPort 6.
What I also did was to increase the VREG voltage to 1.2V before doing the sysclock speed change.
What I also observed, though, during this procedure, was increased noise.

I think you should post your questions in the forum as they don't appear to be related to pico-sdk https://forums.raspberrypi.com/viewforum.php?f=144


Error 404 not found on deployment section

When I click on fastapi or onnx lik to check for deployment it gives error 404, but they are checked .

Hello There 👋
Yes, the problem you mentioned is available in pypi and web page, but there is no problem in readme.md on github. There was such a problem because it was broadcast directly through the readme.md file. I will fix this in the next release. Until then, issue may remain open.
Thank you.

I'm closing the issue as the issue you mentioned has been resolved with v0.1.1.
Thank you.


feat(OHIFv3):Add PDF viewer

Support viewing PDF documents.  Has a basic e2e test that checks the basic view capability is working.

@swederik and @sedghi  - Fairly simple PDF viewer.

Some comments for discussion.
One overarching comment, not directly related to this PR, is I'm not sure if we should even be contributing these back to the core repo. We should probably keep the framework as light as possible (only cornerstone + default extension?), and everything else should be an extension that lives in its own repo.
I get its a mono-repo, but I envision there being 100s of extensions, so maybe we should tackle this one early... food for thought.

Great point, and one that I'm specifically trying to address with config-point.  The design of the config-point is to decouple what is getting configured from the configuration that gets puts there, while still allowing the default/basic configuration to be included.  Whether or not pdf and video are included in core I don't really care either way, but I don't want to have to have n^2 modes where each one needs to know/have deep understanding of the modes in order to get them working.
For example, suppose we have a mode without PDF and video, then do we need the same mode + video, the same mode + pdf, the same mode with video + pdf?    Sure, some modes will be orthogonal, like not having a cornerstone 2d mode and a cornerstone 3d mode combined, but even with just that, it would add an extra 4 modes.  What config point allows is to:

Have a basic mode (longitudinal for example)
Add in the default providers
Just load the desired extensions
Extensions register themselves with config-point as to what they provide for things like getSopClassHandler, viewport etc
Modes simply get extended and are have the additional functionality mixed in.

Then, you can have individual theme configs that simply say  add video and add pdf, or do neither.
That vision isn't quite realized in this commit - I didn't want to go quite that far initially, but in static-wado, it is realized that far as you can load third party deployment mechanisms as well as third party custom services (eg custom image conversions) by defining them in the static-wado configuration file.    Adding a new module adds both default configuration to multiple areas and default code.

Great point, and one....

All good points, I think all this really depends on how much modes want to be shared and used. Additionally modes are currently static because the examples ones were designed to be simple, but as you say they may need to be configurable by the client/some external resource, so its good you are thinking about this problem.

@sedghi and @swederik  - I've removed the config point mode configuration from this.  I've left the update to config-point 0.4.3, as the earlier config-point version needs some updating and is committed to v3-stable already.


Is anybody maintaining "Releases"?  🤔

As far as I can see from npm versions https://www.npmjs.com/package/precise-ui there were released lots of stuff since the latest one in https://github.com/zeiss/precise-ui/releases tab.

There wasn't. Now the situation has changed and a (GitHub) release needs to be done to (NPM) release.


SOT-185: Deploy contracts using jayce

Description
Deploy Navori contracts using the jayce tool. The output is logged to the screen. Use the command kurtosis files download to download the output file.
References (if applicable)
jayce tool

@hduoc2003 deploy ionia contract


Add support for switching file group while keeping camera orientation

Is your feature request related to a problem? Please describe.
F3D supports opening multiple files and switching between them. However, when doing that, the camera is always reset.
It would be nice to be able to keep the camera on the same location.
Describe the solution you'd like
Adding either a dedicated interaction or command line option to control this option would be nice

Fixed in https://github.com/f3d-app/f3d/pull/1761


Provide sudoers file example.

To ensure sudo -E commands work, we need to allow SETENV and ideally NOPASSWD.

So you basically want to give some information about how sudo works in the readme?
While these are sudo basics and have nothing to do with kitchen in particular. I don't think it would make sense to document the behaviour of it here. That's what the sudo page is for.
And NOPASSWD is set in the default template anyway.

This needs to be done on the host running docker, not the docker instance created.
I encountered this issue on multiple Ubuntu boxes, and the solution was not completely obvious. This just makes it so people whom encounter issues will have a documented procedure to get it working correctly. I think that is pertains to how this driver functions as it depends on preserving the environment variables to function correctly.

I have validate this step is required on Ubuntu 16.04 hosts as well.

Closing this PR due to inactivity, and I agree with previous comments that this update may not make sense to document here. Please open a new PR if this issue is still relevant. Thanks!


Update data sets on the MGI FTP site

Migrated from rnabio.org proposed improvements page

Use a larger data set that has not been so heavily downsampled

Put the original UHR and HBR instrument data on the FTP site

Put the instrument data for the new hcc1395 data on the FTP site

MGI notes on this data will be here: https://confluence.gsc.wustl.edu/display/CI/Cancer+Informatics+Test+Data

This would indeed be a great addition. I think the original data may be lost but there is a comparable dataset already available in SRA that we could switch over to.


Format the docstring with better indentation

@cmccoy @ehankland I am not sure what style guide this repository is following, but the docstring at the entrance file looks like it could be improved.

LGTM after "softwares" fix.

Thanks for the edits!

Addressed the "softwares" typo. PTAL.


Reducer call inside another Reducer action.

Can you tell me how I call a reducer function inside another reducer function?

Check out https://github.com/infinitered/reduxsauce#default-handler

And how I get a callback from reducer.


[Feature Request] Add Node 22

Now that Node 22 has been released and will be LTS later this year, it would be nice to have support for it in pkg.

Need someone able to do the patch for it, also seems the actual nodejs 20 patches are broken but I have no idea how to fix them

I will have a look - but there are a lot of changes in Node 22 vs 20 and also in the V8 versions

I opened a PR  #45 with an experimental patch, feel free to try ;)


Pt 156569845 check signatures

Check signatures on transactions before applying them to state trees.
Also, move signature verification out of aec_keys and to aetx_sign instead.
https://www.pivotaltracker.com/n/projects/2124891/stories/156569845

Test failed with unrelated known intermittent failure %%% aehttp_integration_SUITE ==> {{badmatch,{error,socket_closed_remotely}}, - I am taking the liberty of restarting CI job.

I am taking the liberty of restarting CI job.

I did - I hope I restarted it in the correct way.


Enable evmts.config.ts

Instead of putting the evmts config in a tsconfig.json file put it in a evmts.config.ts file. The challenge here is we can't read the config file asyncronously and loading this file syncronously being that it's a TS file is not easy. A solution that should work is watching the node_modules/.cache/evmts/config.json with the type server and feeding that into the syncronous type server. Then generate this cached config as a json asyncronously. The other bundlers are async and are easier to implement since they can just read the config directly.
This could cause issues to the type server so we will have to handle the config not be present. This is a dangerous change that should be tested in multiple type servers

Moving to linear


WIP Test-Json should have a -JsonFile parameter #12882. -JsonFile and -Pa…

…th alias added. Includes additional Pester tests.
PR Summary
Add -JsonFile parameter switch and -Path alias.
PR Context
JSON data is often stored in a file. After -SchemaFile was added, it seemed appropriate to have -JsonFile.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[x] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

I made some improvements in my forked project. How can I get the CI tests to run again?

Cannot figure out how to re-integrate, so deleting and trying again.


GeoAreasTile - Improve visuals of the map

The color should be fetched from the current theme (theme.geoAreaSpotFillColor).