Add jobs and scripts for precompilation

Add jobs for building and releasing precompiled packages

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:fd1e91d9c47db49e1f697b49990b32938d8b8e22

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:dd0035ccffa80b9956b8bb8e5dabb4e8cd57fdf9

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:c014df375f40b40bbe64eb4375d67b08a5fd1e66

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:f8799b932221fcc9db4a83639fc67d42e850fd21

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:96f2fd20244cbffa294fa56d9c50dccb95eda730

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:1bd658cb2d654f7fd09add28c9afa3578b369695

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:7315159f6714929143049b96a8acb602068da12a

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:b4aaaa1093c69b2dfc5ab958ac4f3c542a77b43d

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:2722881d216ecbb4e2e884a5f4e8056cb4e51e0c

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:57237a08c90fa5cf079f41fb5ff7c7ab1ed7c6b1

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:40b1cfd7fd143a88d056f5776a5080c73fc4459b

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:bb6e09188b2baef26dda6527b2a5e87a81b7f292

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:5db9d1338748dad57d9bbd342e980a6f2c76f712

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:1b74046e2173a377eb57edb267abc664d3bf9091

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:f059a80129a175c0b4e2d520bb686ef202d8a65b

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:f196d8f4809429df291e0a1634e4b9b870626d8e

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:a2d08be0febfe3e2acc93eacfec81091c23e6cfb

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:5cc867d568244c00e4faa3fe4cc5ab47d19da1cb

Your development orb has been published. It will expire in 30 days.
You can preview what this will look like on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=dev:5cc867d568244c00e4faa3fe4cc5ab47d19da1cb

Your orb has been published to the CircleCI Orb Registry.
You can view your published orb on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/membraneframework/elixir?version=1.4.0


JSONAPI Meta object should be at same level as Data, not inside it

The JSONAPI spec at https://jsonapi.org/format/#document-meta shows the META object at the same level as the DATA object:
{
  "meta": {  //META IS OUTSIDE DATA
    "copyright": "Copyright 2015 Example Corp.",
    "authors": [
      "Yehuda Katz",
      "Steve Klabnik",
      "Dan Gebhardt",
      "Tyler Kellen"
    ]
  },
  "data": {
     //...
  }
}

However Laravel JSONAPI seems to place the META object INSIDE the DATA object:
"data": {
        "type": "users",
        "id": "1",
        "attributes": {
            "firstName": "User",
            "lastName": "One",
            "email"<EMAIL_ADDRESS>        },
        "relationships": {
            "profile": {
                "links": {
                    "related": "http://host.docker.internal/api/users/1/profile",
                    "self": "http://host.docker.internal/api/users/1/relationships/profile"
                }
            }
        },
        "links": {
            "self": "http://host.docker.internal/api/users/1"
        },
        "meta": {  // META IS INSIDE DATA
            "roles": [
                "super-admin"
            ]
        }
    },

While not a crisis, we're using some other stuff that populates some META info, and it put's it OUTSIDE the data object. So we end up with two META objects for the resource. Would it be possible to address this somehow? We can work around it, but the workaround involves manually manipulating the response body before sending and is a bit 'hacky'.

So no, it's actually both.
The top-level document can have meta, but also a resource object in the data top-level member can have meta within it.
So it depends where you are returning the meta from in your implementation as to where it will be in the resource object, or at the top-level document. Can you provide details of where you are returning this from?

This distinction is:

Document level (top-level) meta is about the document as a whole - link
Resource object meta is about that specific resource - link

https://jsonapi.org/format/#document-resource-objects OK - we're all good. When we searched the spec on Meta the link to the resource meta did not show up for some reason. Anyway, sorry for the false alarm and as always thanks for the quick response. Closing this based on the spec being adhered to.
We lost our lead frontend developer and I have been feeling that gap in addition to my day job. We have a replacement starting on 6/19 and once things settle down a bit, I'll try to find some time to respond to your questions regarding doc improvements from some of the other issues.

Hey - no worries, don't worry about creating this issue, all good!
Yeah that sounds stressful. I've actually started the v4 rewrite, and making good progress - so there's still a lot to do. But once I've finished writing it, I'm going to have to go through all the docs and update them - so a good point to incorporate any feedback you have on the docs. Ideally send me any ideas via Slack - link on the homepage.

Hi, sorry to respond to this closed thread, but I'm actually wondering if it's possible to add stuff to the top-level meta object using Laravel JSON API?
Is there a method for that?
Thanks in advance!


Keras Sequential using RNN not working on M1 Max GPU

Click to expand!
Issue Type
Bug
Source
source
Tensorflow Version
2.8.0
Custom Code
No
OS Platform and Distribution
MaxOS 12.3.1
Mobile device
No response
Python version
3.9
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
M1 Max 26 cores GPU
Current Behaviour?
If using a Sequential model, I use a SimpleRNN layer, there is no way to use the GPU as device (no problem with the same code on Colab, every runtime works).
The same code using:
with tf.device("/device:CPU:0"):
  ...

works fine, but takes a while
Standalone code to reproduce the issue
from tensorflow import keras
(X_train, y_train), (X_test, y_test) = keras.datasets.imdb.load_data(num_words=10000)
(X_valid, X_test) = X_test[:12500], X_test[12500:]
(y_valid, y_test) = y_test[:12500], y_test[12500:]
word_index = keras.datasets.imdb.get_word_index()
X_train_trim = keras.preprocessing.sequence.pad_sequences(X_train, maxlen=500)
X_test_trim = keras.preprocessing.sequence.pad_sequences(X_test, maxlen=500)
X_valid_trim = keras.preprocessing.sequence.pad_sequences(X_valid, maxlen=500)
model = keras.models.Sequential()
model.add(keras.layers.Embedding(input_dim=10000, output_dim=10))
model.add(keras.layers.SimpleRNN(32))
model.add(keras.layers.Dense(1, "sigmoid"))

model.compile(loss='binary_crossentropy', optimizer="adam", metrics=["accuracy"])

history = model.fit(X_train_trim, y_train,epochs=10, batch_size=128, validation_data=(X_valid_trim, y_valid))

Relevant log output
Metal device set to: Apple M1 Max
systemMemory: 32.00 GB
maxCacheSize: 10.67 GB
2022-05-12 14:36:06.487099: I tensorflow/core/common_runtime/pluggable_device/pluggable_device_factory.cc:305] Could not identify NUMA node of platform GPU ID 0, defaulting to 0. Your kernel may not have been built with NUMA support.
2022-05-12 14:36:06.487233: I tensorflow/core/common_runtime/pluggable_device/pluggable_device_factory.cc:271] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 0 MB memory) -> physical PluggableDevice (device: 0, name: METAL, pci bus id: <undefined>)
2022-05-12 14:36:07.054786: W tensorflow/core/platform/profile_utils/cpu_utils.cc:128] Failed to get CPU frequency: 0 Hz
Epoch 1/10
2022-05-12 14:36:07.290001: I tensorflow/core/grappler/optimizers/custom_graph_optimizer_registry.cc:113] Plugin optimizer for device_type GPU is enabled.
  1/196 [..............................] - ETA: 5:01:59 - loss: 0.6936 - accuracy: 0.5469

The same code using:
with tf.device("/device:CPU:0"):
    history = model.fit(X_train_trim, y_train,epochs=10, batch_size=128, validation_data=(X_valid_trim, y_valid))

Works fine, so I think it's something related to the hardware

@AlbertoSinigaglia Thank you for the update!
Please move this issue to closed status if it is resolved ?
Thank you!

@AlbertoSinigaglia Thank you for clarifying the confusion.
Could you please try with the latest  tf-nightly and let us know if the issue still persists ?
Thank you!

How should I install it?
pip install tf-nightly

returns:
ERROR: Could not find a version that satisfies the requirement tf-nightly (from versions: none)
ERROR: No matching distribution found for tf-nightly

and also the whl are not working:
pip install tf_nightly-2.10.0.dev20220512-cp39-cp39-macosx_10_14_x86_64.whl
ERROR: tf_nightly-2.10.0.dev20220512-cp39-cp39-macosx_10_14_x86_64.whl is not a supported wheel on this platform.

By the way, it's literally only SimpleRNN that is causing problem, also the same code without the embedding layer works fine, and same for the same code using LSTM instead of SimpleRNN

Tried many other thing, the only solution for the moment is to uninstall tensorflow-metal (I tried all the versions, all have the same issue), but it means that everything runs on the CPU (even though for the project I'm doing, the performances are more or less the same, for some reason)

@AlbertoSinigaglia,
Looks like tensorflow-metal or Tensorflow on M1 chip has limited support for GPU.
Could you check this link. Thanks!

I got same issue, TensorFlow-metal==0.4.0 TensorFlow-macos==2.8.0 python3.9 M1 max. After fit() function, only shows 2022-06-14 13:47:18.695745: W tensorflow/core/platform/profile_utils/cpu_utils.cc:128] Failed to get CPU frequency: 0 Hz Epoch 1/15 2022-06-14 13:47:19.146313: I tensorflow/core/grappler/optimizers/custom_graph_optimizer_registry.cc:113] Plugin optimizer for device_type GPU is enabled. and I can see cpu% is 300 gpu% is 100 , but no progress bar no matter how long I wait. However, if I don't use RNN, for example, only has dense layer in my model, everything works well.


What does the output model mean after each script

Hi, thanks for your ama~~~zing job!
I'd like to reproduce the 10+10 experiment according to Table 2 in your paper, which means i am running the scripts as follow:
(Base 10)
python tools/train_net.py --num-gpus 1 --config-file ./configs/PascalVOC-Detection/iOD/base_10.yaml SOLVER.IMS_PER_BATCH 1 SOLVER.BASE_LR 0.005
(10 + 10)
python tools/train_net.py --num-gpus 1 --config-file ./configs/PascalVOC-Detection/iOD/10_p_10.yaml SOLVER.IMS_PER_BATCH 1 SOLVER.BASE_LR 0.005
(10 + 10 _ ft)
python tools/train_net.py --num-gpus 1 --config-file ./configs/PascalVOC-Detection/iOD/ft_10_p_10.yaml SOLVER.IMS_PER_BATCH 1 SOLVER.BASE_LR 0.005
(because of limited devices, I set --num-gpus and bs to 1. )
According to my understanding, the Base 10 script conducts the First 10 class training, refer to the 3-th line of table. The trained model can only detect the first 10 class.
However, the 10+10 script output a model that can only detect the last 10 class object, is it not the final model after continual learning?
And, what does the 10+10_ft do, though i am running this script.
Look forward to your reply！

In one word, I don't know clearly what does the above three scripts mean or how can I reproduce the results in Table 2. Thanks for any advice!


Different USB behavior

If I connect the MX chip directly to the computer, I see the window and can drag the .bin file over to it, and it updates. However, if I connect the usb to the docking station, the window does not appear, and I am not sure how to access the device. However, I was able to provision the MX chip connected to the docking station, and get telemetry data, but not sure why the  behavior is different with regards to updating the firmware. Probably a known issue with docking stations?

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

ID: e8e7c7d8-9e2e-a23b-35e6-489650473909
Version Independent ID: 5861e5ab-fb35-02a6-c848-6d8680501901
Content: Connect a DevKit device to your Azure IoT Central application
Content Source: articles/iot-central/howto-connect-devkit.md
Service: iot-central
GitHub Login: @dominicbetts
Microsoft Alias: dobett

@PeterTurcan Thanks for the feedback! We are currently investigating and will update you shortly.

@PeterTurcan Sorry for the delayed response. Would you please open an issue here: https://github.com/Azure/iot-central-firmware/issues

@PeterTurcan Any updates?

Since we haven't heard back from you, we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Add support for THB-splines

To do:

[ ] Cite the paper used for the optics research in the README.
[ ] Create an object which can slot into SplineGrid.control_points, with the required data to compute the full control point grid from the data from the several hierarchies, and implement this computation into a dedicated evaluate! method.
[ ] Add tests.

Adding a refinement algorithm either in the core code or in the docs as an example can be done either for this issue or for a follow up issue.

C:\Users\bart1\Documents\Optics\Research_optics\mitsuba_caustic_design\THB_splines\THB-splines.ipynb


The Expected parameters for 'change-password' were not supplied

I've been using Chauffeur on my 7.2.8 websites and its been working great, however, I've just used it in  a 7.3.0-RC site and cant seem to update the default password.
It creates the default SQL CE database fine, but when I run the command "user change-password 0 default newpass" I get the error "The Expected parameters for 'change-password' were not supplied. Format Expected: change-password   "
Chauffeur 0.6.3 installed via nuget
Any ideas?

Ah sorry, I forgot to update the documentation after I refactored the way it worked. Chauffeur now uses the IUserService rather than the membership provider. I'll get the doco (and error message) fixed tonight but the new structure is:
umbraco> user change-password <username> <new password>

You no longer need to provide the old password. It also works off the username (eg: admin).

Thanks Arron,
I should have run the help command as it was updated there. Thanks going to be much more useful being able to use the username instead.
I'm still getting my head around Git, so thought it was a good opportunity to try out a pull request to fix the change. Let me know if my pull request with the change is done right.

Yep it was all good, it's merged and just going through the CI pipeline at the moment, so you'll see release 0.6.4 up on NuGet shortly (if it's not already). You can also cross-link GitHub issues with PR's by tagging them, such as #32 which is now merged :smile:

Great. Thanks for the tip!


Win32 panic slice bounds out of range

This issue is noticed with intelliJ Go plugin 0.10.1164, while try to debug whole package (instead of single go file), windows dlv.exe panic saying
panic: runtime error: slice bounds out of range
goroutine 34 [running]:
github.com/derekparker/delve/dwarf/frame.parseFDE(0xc0824080c0, 0xb9ddf0)
C:/BuildAgent/work/gopath/src/github.com/derekparker/delve/dwarf/frame/parser.go:74 +0x406
github.com/derekparker/delve/dwarf/frame.Parse(0xc082724000, 0x592a4, 0x59400, 0x355fe0, 0xdbb860, 0x0, 0x0, 0x0)
C:/BuildAgent/work/gopath/src/github.com/derekparker/delve/dwarf/frame/parser.go:33 +0x1c8
github.com/derekparker/delve/proc.(*Process).parseDebugFrame(0xc082082540, 0xc0820f2230, 0xc0820ea980)
C:/BuildAgent/work/gopath/src/github.com/derekparker/delve/proc/proc_windows.go:174 +0x4df
created by github.com/derekparker/delve/proc.(*Process).LoadInformation
C:/BuildAgent/work/gopath/src/github.com/derekparker/delve/proc/proc.go:154 +0x112
Same exact source code works well on Mac version of dlv.exe and go plugin.

What version of Delve are you using (dlv version)?
Delve Debugger
Version: 0.11.0-alpha
Build: 63a660820e7beef3b4870922e25897887392b188

What version of Go are you using? (go version)?
go version go1.6 windows/386

What operating system and processor architecture are you using?
Win32  64bit OS but golang exe and target exe is 32bit

What did you do?
C:/Go\bin\go.exe build -o C:\Users\leewi\AppData\Local\Temp\clm-adls0go -gcflags "-N -l" git.company.com/clm-adls
C:\Users\leewi.IntelliJIdea15\config\plugins\Go\lib\dlv\windows\dlv.exe --listen=localhost:50958 --headless=true exec C:\Users\leewi\AppData\Local\Temp\clm-adls0go --
panic: runtime error: slice bounds out of range
...

What did you expect to see?
No panic and be able to debug

What did you see instead?
Panic and stopped debugger

It would help to see your executable file C:\Users\leewi\AppData\Local\Temp\clm-adls0go. It would be even better if you can provide instructions on how to build C:\Users\leewi\AppData\Local\Temp\clm-adls0go. Thank you.
Alex

One possible explanation for that panic would be a FDE in debug_frame containing no instructions.

go version go1.6 windows/386

Looks like this is on 32-bit Go.  Pretty sure Delve doesn't support 32-bit Go installations on any platform.

Ah, didn't catch that. Closing as duplicate of #20. Thanks, @lukehoban.

Looks like this is on 32-bit Go.

Shouldn't Delve recognize this situation and stop debugging with a nice error message, instead of confusing us all?
Alex


Contain code that will be rejected by future version of Rust

I get
warning: the following packages contain code that will be rejected by a future version of Rust: console_log v0.2.0

When compiling my project https://github.com/erwanvivien/gifski on branch wasm32 using
RUSTFLAGS="-C target-feature=+atomics,+bulk-memory,+mutable-globals" cargo build --target=wasm32-unknown-unknown --release -Z build-std=panic_abort,std

I don't know if it's normal?

🤔 I'll need to look into that.

I don't see this warning when building locally with cargo build --release. Additionally when running the command provided, I get an error indicating that the -Z flag is only supported on nightly. I'm not using nightly and don't have time to try and chase this down. If you (or anyone else) want's to take a crack at figuring out what's causing this, pull requests are welcome. Having said that, it does not seem like a serious issue and should be safe to ignore.

You were right, I found the log and it's very simple bug:
$ cargo report future-incompatibilities --id 1
The following warnings were discovered during the build. These warnings are an
indication that the packages contain code that will become an error in a
future release of Rust. These warnings typically cover changes to close
soundness problems, unintended or undocumented behavior, or critical problems
that cannot be fixed in a backwards-compatible fashion, and are not expected
to be in wide use.

Each warning should contain a link for more information on what the warning
means and how to resolve it.

To solve this problem, you can try the following approaches:

- If the issue is not solved by updating the dependencies, a fix has to be
implemented by those dependencies. You can help with that by notifying the
maintainers of this problem (e.g. by creating a bug report) or by proposing a
fix to the maintainers (e.g. by creating a pull request):

  -<EMAIL_ADDRESS>  - Repository: https://github.com/iamcodemaker/console_log
  - Detailed warning command: `cargo report future-incompatibilities --id 1 --package<EMAIL_ADDRESS>
- If waiting for an upstream fix is not an option, you can use the `[patch]`
section in `Cargo.toml` to use your own version of the dependency. For more
information, see:
https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#the-patch-section

The package `console_log v0.2.1` currently triggers the following future incompatibility lints:
> warning: trailing semicolon in macro used in expression position
>   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/console_log-0.2.1/src/style.rs:19:83
>    |
> 19 |                 concat!("color: white; padding: 0 3px; background: ", $color, ";");
>    |                                                                                ^
> ...
> 24 |             trace: bg_color!("gray"),
>    |                    ----------------- in this macro invocation
>    |
>    = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
>    = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
>    = note: `#[allow(semicolon_in_expressions_from_macros)]` on by default
>    = note: this warning originates in the macro `bg_color` (in Nightly builds, run with -Z macro-backtrace for more info)
>
> warning: trailing semicolon in macro used in expression position
>   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/console_log-0.2.1/src/style.rs:19:83
>    |
> 19 |                 concat!("color: white; padding: 0 3px; background: ", $color, ";");
>    |                                                                                ^
> ...
> 25 |             debug: bg_color!("blue"),
>    |                    ----------------- in this macro invocation
>    |
>    = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
>    = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
>    = note: `#[allow(semicolon_in_expressions_from_macros)]` on by default
>    = note: this warning originates in the macro `bg_color` (in Nightly builds, run with -Z macro-backtrace for more info)
>
> warning: trailing semicolon in macro used in expression position
>   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/console_log-0.2.1/src/style.rs:19:83
>    |
> 19 |                 concat!("color: white; padding: 0 3px; background: ", $color, ";");
>    |                                                                                ^
> ...
> 26 |             info: bg_color!("green"),
>    |                   ------------------ in this macro invocation
>    |
>    = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
>    = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
>    = note: `#[allow(semicolon_in_expressions_from_macros)]` on by default
>    = note: this warning originates in the macro `bg_color` (in Nightly builds, run with -Z macro-backtrace for more info)
>
> warning: trailing semicolon in macro used in expression position
>   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/console_log-0.2.1/src/style.rs:19:83
>    |
> 19 |                 concat!("color: white; padding: 0 3px; background: ", $color, ";");
>    |                                                                                ^
> ...
> 27 |             warn: bg_color!("orange"),
>    |                   ------------------- in this macro invocation
>    |
>    = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
>    = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
>    = note: `#[allow(semicolon_in_expressions_from_macros)]` on by default
>    = note: this warning originates in the macro `bg_color` (in Nightly builds, run with -Z macro-backtrace for more info)
>
> warning: trailing semicolon in macro used in expression position
>   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/console_log-0.2.1/src/style.rs:19:83
>    |
> 19 |                 concat!("color: white; padding: 0 3px; background: ", $color, ";");
>    |                                                                                ^
> ...
> 28 |             error: bg_color!("darkred"),
>    |                    -------------------- in this macro invocation
>    |
>    = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
>    = note: for more information, see issue #79813 <https://github.com/rust-lang/rust/issues/79813>
>    = note: `#[allow(semicolon_in_expressions_from_macros)]` on by default
>    = note: this warning originates in the macro `bg_color` (in Nightly builds, run with -Z macro-backtrace for more info)
>


Can I pass a value to control the amplitude of the curve?

@liutian0117 You can adjust amplitude by using the .power() modifier


DRF & ninja support

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.58%. Comparing base (30a2975) to head (195f08a).

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #4   +/-   ##
=======================================
  Coverage   89.58%   89.58%
=======================================
  Files           4        4
  Lines          96       96
=======================================
  Hits           86       86
  Misses         10       10

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


Is SchemaExtension isolated (thread/coroutine-safe) ?

I encountered a bug where self.execution_context in the extension hook is not properly isolated between different requests/coroutines.

resolver must be async (sync seems ok, but probably because it is single threaded)
extension must be an instance passed to Schema (with extension class it works just fine)

Here is a repo with a reproducible example - https://github.com/kindermax/strawberry-extension-thread-safe
https://github.com/strawberry-graphql/strawberry/issues/2781 is probably related.

@kindermax the repo doesn't seem to be public 😊

Oh, my mistake, I've just made it public)

I'm instantiating extensions because I want to pass some data to the extension constructor, so basically what I need is an extension factory. Maybe it is described somewhere in docs but I didn't find one.

When I saw https://strawberry.rocks/docs/extensions/mask-errors and https://strawberry.rocks/docs/extensions/max-aliases-limiter#maxaliaseslimiter I thought that it is fine to instantiate extensions but probably this is not true, and these extensions are basically extension factories and maybe should be pointed in docs)

we definitely need to make the docs better and maybe put a warning when you pass an instance


feat: use dependency plugin instead of package goal

Uses the dependency plugin to gather the required information.
This introduces less build time overhead for each module and acquires
the same information. This also makes the action more stable since it
does not require the package goal to work but rather just gathers
dependency information.

Has been tested over here: https://github.com/camunda/camunda-bpm-platform/pull/3413

Ah, I wasn't aware 👍
I can do that 🙂


cleaned up TypeScript in coders.ts

Please add a meaningful description for your change here
This fixes 22 problems caught by eslint in coders.ts. The file should be clean and any free now. Let me know if I've misunderstood the intention of any of the types... I'm just looking at this code for the first time. There are probably some unknown types that could be narrower.
@robertwb
@pabloem

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

R: @damccorm

This should be ready now. I had to update a few types after resolving a merge conflict.

@pabloem or @robertwb would you mind taking a look/merging?


Role Assignment Fails in Dependency Pipeline due to an existing name

Description
Role Assignment task fails in the dependency pipeline due to a role that already exists.
Exception: /home/runner/work/_temp/c15652b3-bd86-4903-88d8-0e6578b5b1de.ps1:33
Line |
  33 |    throw $res['Exception']
     |    ~~~~~~~~~~~~~~~~~~~~~~~
     | 19:29:44 - The deployment '-20211129T1911425766Z' failed with
     | error(s). Showing 1 out of 1 error(s). Status Message: The
     | role assignment already exists. (Code:RoleAssignmentExists)
     | CorrelationId: 240d7e6a-2bee-4a3d-acb6-233ccd0b290d

The reason is that the latest module update for role assignments, we decoupled the location property from the role assignment GUID as it is not a dependency. Where a deployment might happen on a specific location, but then another location is introduced or being tested which causes issues and doesn't make the deployment idempotent.
Steps to reproduce

Deploy the dependency pipeline

Solution

Remove the role assignment from the principal ID: cf33fea8-b30f-424f-ab73-c48d99e0b222. This can be done via CLI or portal but requires permissions
Rerun the dependency pipeline.

Possible side effects

If other resources are deployed that require the user assigned managed identity to have the permissions and they are deployed before it in the dependency pipeline, that might fail the first time, until the identity has a role assigned to it

Thanks for tracking the issue @ahmadabdalla.
The roleassignment has been deleted and redeployed successfully through the dependency pipeline.
Closing the issue.


KeyError: 'graphql'

Describe the bug
tried scraping location posts and unable to get the posts owner_id.
When running code, a KeyError :'graphql'  occurs in line 135 of structures.py
~/anaconda3/lib/python3.7/site-packages/instaloader/structures.py in _obtain_metadata(self)
    133         if not self._full_metadata_dict:
    134             pic_json = self._context.get_json("www.instagram.com/p/{0}/".format(self.shortcode), params={})
--> 135             self._full_metadata_dict = pic_json['entry_data']['PostPage'][0]['graphql']['shortcode_media']
    136             self._rhx_gis_str = pic_json.get('rhx_gis')
    137             if self.shortcode != self._full_metadata_dict['shortcode']:

To Reproduce
Steps to reproduce the behavior:
loader = instaloader.Instaloader()
loader.login(USER, PASSWORD)
info = loader.get_location_posts(215634585)

for things in info:
    print(things.owner_id)

Expected behavior
return owner_id
Error messages and tracebacks
KeyError: 'graphql'
Instaloader version
instaloader 4.2.10
Additional context
Add any other context about the problem here.
(please also see https://instaloader.github.io/contributing.html for how to report a bug)

i wait the fix

Thanks for reporting. I'm closing this in favor of #433, which seems to describe the same bug.


Artifacts when resizing the subpasses example

Hello there,
when playing around with the samples, I noticed an issue within the "subpasses" sample. This issue is only triggered when resizing the window while the program is running. It basically becomes a giant artifact which it never recovers from.

At first I thought, that it had to do with my gpu drivers but it seems to affect both Nvidia aswell as AMD gpu's.
I hope this helps to some extent!
Best regards!

See https://github.com/KhronosGroup/Vulkan-Samples/issues/455. That sample is missing proper synchronization. We'll fix this.


Trailing in Nginx conf.

The trailing in the Nginx configuration should be removed, in order to make it function
location /irc/ {
	proxy_pass http://localhost:9000/;
	proxy_http_version 1.1;
	proxy_set_header Connection "upgrade";
	proxy_set_header Upgrade $http_upgrade;
	proxy_set_header X-Forwarded-For $remote_addr;

	# by default nginx times out connections in one minute
	proxy_read_timeout 1d;
}

I had to edit it to this, to make it work
location / {
	proxy_pass http://localhost:9000/;
	proxy_http_version 1.1;
	proxy_set_header Connection "upgrade";
	proxy_set_header Upgrade $http_upgrade;
	proxy_set_header X-Forwarded-For $remote_addr;

	# by default nginx times out connections in one minute
	proxy_read_timeout 1d;
}

s/trailing/directory path/
The Lounge is supposed to support being proxied behind a /path/ URL, so it seems #27 was subsequently broken?

What was the problem you were experiencing? Does adding
rewrite ^/irc/(.*) /$1 break;

fix the issue?

@xPaw I was getting a 502 and it was impossible to reach the server. I used this config to fix it
server {

     server_name lounge.xxxxxxx.eu;
     return 301 https://lounge.xxxxxxx.eu$request_uri;

     location / {
     	proxy_pass http://<IP_ADDRESS>:9000/;
     	proxy_http_version 1.1;
     	proxy_set_header Connection "upgrade";
     	proxy_set_header Upgrade $http_upgrade;
     	proxy_set_header X-Forwarded-For $remote_addr;

     	# by default nginx times out connections in one minute
     	proxy_read_timeout 1d;
     }

@xPaw I will try you soultion as well to see if it works and then report back, but for now everything is working

@notaduck any update on this?
Feel free to edit the wiki if you think it needs to change. Closing this just now.


Should aws_X_clock_get_ticks() return an error code?

Reading the kernel docs, it doesn't seem like these functions can ever fail the way we're using them.
In code we're writing that calls aws_X_clock_get_ticks(), it can be very difficult to handle situations where the clock returned a theoretical error code, so we're not bothering with thorough error handling.
Perhaps the signature should simply be:
AWS_COMMON_API uint64_t aws_X_clock_get_ticks(void);

I tend to agree. @bdonlan thoughts?


Review changes requested in docs PR #10411

Summary
Changes requested in https://github.com/dotnet/docs/pull/10411.
Remove all snippet tags.
In the C# code:

add a using System.Globalization statement.
change Globalization.CultureInfo.InvariantCulture to CultureInfo.InvariantCulture

In the VB code:

Change Imports System.Windows to Imports System.Windows.Forms.
(Note from v-thepet: Visual Studio says Imports System.Windows.Forms is unnecessary.)
Change Inherits Forms.Form to Inherits Form
Remove the <STAThreadAttribute> line; it's the default for VB.

Fixes dotnet/docs#Issue_Number (if available)
See https://mseng.visualstudio.com/TechnicalContent/_queries/edit/1409982/?triage=true

@rpetrusha @BillWagner - Ready for review - see comment above that Visual Studio says Import System.Windows.Forms is unnecessary in the VB sample.

Thanks for making the additional changes, @v-thepet. I'll merge and rebuild dotnet/docs#10411.


Disable corepack when we run npm

This would unblock https://github.com/DefinitelyTyped/DefinitelyTyped/pull/67120, but I actually think these two uses could just be pacote +<EMAIL_ADDRESS>or something.

I don't know how we can use untar.js since it's not labelled Blazing Fast.

We wouldn't actually need the tar lib as pacote can extract. But this code unfortunately has to be synchronous because it's called from tslint anyhow

Forgot the changeset, oops


Notification module cannot find capture with custom reference

follow up for https://github.com/commercetools/commercetools-adyen-integration/issues/975
We added the custom reference for the refund. To match them to a single/specific capture, we added custom reference values for every capture. This is working fine now (match a specific refund to a specific capture).
But the notification module now has a problem, it cannot find the correct capture (because of the custom reference field instead of the merchant reference).
Perhaps you need to enter a fallback to find the correct payment in the notification module if the custom reference field has been used?

Hi @LSshopmacher
Thank you for the issue. I can confirm this is a bug.
We will check it and come up with the solution as soon as possible.

Hi,
we have the same issue. The custom reference will be set in adyen but the payment will not be set to payed. The notification module reports: "Payment with merchantReference: customReference was not found"

@baumwolli Thanks for the report. It is an known issue for us, and we are going to fix it in coming weeks

@baumwolli We have already provided a fix in the latest release
https://github.com/commercetools/commercetools-adyen-integration/releases/tag/v10.1.1
Please feel free to let us know if you have further question.

Dear reporter, we would like to notify you that the Adyen x CommerceTools integration has changed ownership. From July 1st 2023, Adyen has taken over support / maintenance tasks for this integration from CommerceTools. Thank you for your product feedback. We will take your suggestion into consideration and prioritize accordingly. If you are experiencing any ongoing issues with this integration please contact Adyen Support and we will make sure you will get the answers you need to get going.

Dear reporter, we would like to notify you that the Adyen x CommerceTools integration has changed ownership. From July 1st 2023, Adyen has taken over support / maintenance tasks for this integration from CommerceTools. Thank you for your product feedback. We will take your suggestion into consideration and prioritize accordingly. If you are experiencing any ongoing issues with this integration please contact Adyen Support and we will make sure you will get the answers you need to get going.


Security: Profile picture filtering

When uploading a profile picture for companies or participants, there is no filter in place for file formats. This means that various file types like PHP, PHP5, and Python (PY) scripts, can be uploaded. It should only allows file formats such as JPG, JPEG, and PNG.

Closed in #404


Create REQUIREMENTS.md

create REQUIREMENT.md file.

Issue No: #21
create requirement.md file

thanks for the clarification. text replaced.


Add Content Overview In Readme.md

Having at least a description of the theme of each directory would help. Right now there are just the core-assumptions and use-cases directories.

I am actually in the process of completely restructuring this repo.  As part of that work I will be adding descriptions of each of the directories and how to use them plus generating the top level readme and the architecture document.

@jmwright - my plan is to migrate material over to the architecture yaml files and then retire the old content from the repo.  Assuming this is done in concert with the production docs about the yaml file formats and the final architecture documentation, would you feel this issue is being addressed enough to close it?

Yep. I think this has a good direction set already.


Upgrade Plugins

xsbt-web-plugin, sbt-release, sbt-mima-plugin, sbt-site, sbt-twirl, sbt-coursier, sbt-jmh

If you are using sbt-ensime from ~/.sbt/0.13/plugins/plugins.sbt for sbt-ensime, it will want to be updated to the current release to work with the new coursier release. Current version is 1.12.9

Failure was timeout.
[error]   ! Repeat a simple request
[error]    java.util.concurrent.TimeoutException: Timed out after 10000 milliseconds (ClientRouteTestBattery.scala:50)

lol, we seem to be reproducing this a lot in release-0.15.x, except on the branch where I'm expressly trying to reproduce it.


fix publish_time not set error when broker entry metadata enable without AppendBrokerTimestampMetadataInterceptor

Fixes #11013
Motivation
fix publish_time not set error when broker entry metadata enable without AppendBrokerTimestampMetadataInterceptor
Modifications
check whether BrokerTimestamp exist by BrokerEntryMetadata.hasBrokerTimestamp() first before we get it from  BrokerEntryMetadata.getBrokerTimestamp()
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: ( no)
The schema: ( no )
The default values of configurations: ( no)
The wire protocol: ( no)
The rest endpoints: ( no)
The admin cli options: ( no)
Anything that affects deployment: (no)

After discussing with @aloyszhang , we need to find why the required publish_time field is missed first.

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

ResourceGroupConfigListenerTest

/pulsarbot run-failure-checks

/pulsarbot run-failure-checks

@lhotari Hi could you help look at this test failure?
Error:  Tests run: 14, Failures: 1, Errors: 0, Skipped: 13, Time elapsed: 57.774 s <<< FAILURE! - in org.apache.pulsar.broker.resourcegroup.ResourceGroupConfigListenerTest
Error:  testResourceGroupAttachToNamespace(org.apache.pulsar.broker.resourcegroup.ResourceGroupConfigListenerTest)  Time elapsed: 10.167 s  <<< FAILURE!
org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a lambda expression in org.apache.pulsar.broker.resourcegroup.ResourceGroupConfigListenerTest expected object to not be null within 10 seconds.

I see your PR (https://github.com/apache/pulsar/pull/11048) fixed the flaky test, but it still failed for multiple times.

/pulsarbot run-failure-checks

@BewareMyPower @hangc0276 PTAL

@BewareMyPower  I have added a new method named getEntryTimestamp which will return the brokerEntryTimestamp if BrokerEntryMetadata is enabled or otherwise return the publishTime. And then using this entryTimestamp for expiry checking.

/pulsarbot run-failure-checks

@hangc0276 Could you also take a look?

cc @hangc0276

@sijie @codelipenghui PTAL

/pulsarbot run-failure-checks

@hangc0276

@hangc0276 PTAL


Don't provide spelling suggestion for module

Fixes #22800

Seems reasonable, but down the line it'd be awesome if we could give suggestions for module names based on what we've already seen.


Max Call Stack Exceeded w/ recursive circular reference via property access

TypeScript Version:  3.8.0-dev.20191024

Search Terms:
Max call stack exceeded, getEffectiveTypeArguments, getTypeFromLiteralTypeNode
Code
type Mxs = Mx<'list', Mxs['p1']>;

interface Mx<T, K> {
  p1: T;
  p2: K;
}

Expected behavior:
~Ideally, it would work 😉 but if it won't,~ a circular reference error.
Actual behavior:
RangeError: Maximum call stack size exceeded
I've not included the stacktrace, b/c it changes depending on everything from the number of lines in the file to the property names.
Playground Link: https://www.typescriptlang.org/play/?ts=3.8.0-dev.20191024#code/C4TwDgpgBAsgHgZygXlnAPAcgDYEsHCYA0aCA2pmAIyYC6AfANwCwAUG7gHbAQBOAZgEMAxtHjoAKiQDS9KAG82UKNQBcUCS1bKwAJnXStAXyA
Related Issues:
#25379
#17049

Regression in 3.7

Here's a couple of times around the loop:
    at Object.getObjectFlags (/home/nathansa/ts/built/local/tsserver.js:14073:28)
    at isGenericMappedType (/home/nathansa/ts/built/local/tsserver.js:41205:26)
    at isStringIndexSignatureOnlyType (/home/nathansa/ts/built/local/tsserver.js:45640:57)
    at getIndexedAccessTypeOrUndefined (/home/nathansa/ts/built/local/tsserver.js:43871:17)
    at getIndexedAccessType (/home/nathansa/ts/built/local/tsserver.js:43862:20)
    at getTypeFromIndexedAccessTypeNode (/home/nathansa/ts/built/local/tsserver.js:43925:32)
    at getTypeFromTypeNode (/home/nathansa/ts/built/local/tsserver.js:44458:28)
    at Object.map (/home/nathansa/ts/built/local/tsserver.js:388:29)
    at getEffectiveTypeArguments (/home/nathansa/ts/built/local/tsserver.js:58669:48)
    at getTypeArguments (/home/nathansa/ts/built/local/tsserver.js:42472:109)
    at resolveTypeReferenceMembers (/home/nathansa/ts/built/local/tsserver.js:40612:33)
    at resolveStructuredTypeMembers (/home/nathansa/ts/built/local/tsserver.js:41211:25)
    at getPropertiesOfObjectType (/home/nathansa/ts/built/local/tsserver.js:41238:24)
    at getPropertiesOfType (/home/nathansa/ts/built/local/tsserver.js:41302:17)
    at isStringIndexSignatureOnlyType (/home/nathansa/ts/built/local/tsserver.js:45640:86)
    at getIndexedAccessTypeOrUndefined (/home/nathansa/ts/built/local/tsserver.js:43871:17)
    at getIndexedAccessType (/home/nathansa/ts/built/local/tsserver.js:43862:20)
    at getTypeFromIndexedAccessTypeNode (/home/nathansa/ts/built/local/tsserver.js:43925:32)
    at getTypeFromTypeNode (/home/nathansa/ts/built/local/tsserver.js:44458:28)
    at Object.map (/home/nathansa/ts/built/local/tsserver.js:388:29)
    at getEffectiveTypeArguments (/home/nathansa/ts/built/local/tsserver.js:58669:48)
    at getTypeArguments (/home/nathansa/ts/built/local/tsserver.js:42472:109)
    at resolveTypeReferenceMembers (/home/nathansa/ts/built/local/tsserver.js:40612:33)
    at resolveStructuredTypeMembers (/home/nathansa/ts/built/local/tsserver.js:41211:25)
    at getPropertiesOfObjectType (/home/nathansa/ts/built/local/tsserver.js:41238:24)
    at getPropertiesOfType (/home/nathansa/ts/built/local/tsserver.js:41302:17)
    at isStringIndexSignatureOnlyType (/home/nathansa/ts/built/local/tsserver.js:45640:86)


fix: new alert should have force_screenshot be true

SUMMARY
Superset will do force_refresh query when generating chart screenshot for a given alert. We also had db migration to set all chart alerts' force_refresh attribute be true.
But when user create new chart alert, its force_refresh is false. This PR is to fix this issue, and set force_refresh default be true when creating new chart alert.
TESTING INSTRUCTIONS
CI and manual test:

create a new alert
check its force_refresh value from report_scedule table.

ADDITIONAL INFORMATION

[x] Has associated issue: #17853
[ ] 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

ping @betodealmeida and @eschutho for code review. thanks!


PERF-#4743: avoid partition.length() in the parquet dispatcher

Signed-off-by: Myachev<EMAIL_ADDRESS>
What do these changes do?

[x] commit message follows format outlined here
[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #4743
[x] tests added and passing
[x] module layout described at docs/development/architecture.rst is up-to-date
[x] added (Issue Number: PR title (PR Number)) and github username to release notes for next major release

I'm curious about the performance implications here. Is there a way you could check quickly @anmyachev ?

This is part of the change required for asynchronous execution. The performance difference should not be visible now.
Without knowing that this is needed for asynchronous execution, these changes can be considered as refactoring, since there is no immediate impact on performance. I can change the first commit category (to REFACTOR) if it's better.

We should label things PERF if they're the PR which helps performance. If they're building the base they could be FEAT or REFACTOR, but not PERF.

We should label things PERF if they're the PR which helps performance. If they're building the base they could be FEAT or REFACTOR, but not PERF.

Apparently yes, I was wrong about that. Convert to draft.

not actual


add a db command that lets the user query each db table.

most important is the ability to view current workspaces
./celerystalk db [workspaces] [services] [vhosts] [-w workspace]

done


Continue supporting factory builders on Laravel 8

Summary
This PR adds support for model factory builders provided by laravel/legacy-factories package.
Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist

[ ] Existing tests have been adapted and/or new tests have been added
[ ] Add a CHANGELOG.md entry
[ ] Update the README.md
[x] Code style has been fixed via composer fix-style

Either the laravel/legacy-factories should be added as dev dependency or the psalm baseline should be updated.

Okay, I dont know what I watched but this is already implemented, sorry


fix: add missing h5 weight adjustment

I'm not sure if this was deliberate or not, but I prefer to have my header weights the same

Ah, I seem to have missed that. LGTM


Sentinl for Kibana 6.5 fails starting up with error "Cannot find module later/later"

System Details
Versions

Type
Version

Kibana
6.5

Elasticsearch
6.5

Server OS
CentOS

Browser
Opera

Original Install Method

[x] Release pkg link
[ ] Gulp
[ ] Source
Other:

Bug Details
I want to update my old SENTINL Installation (old version 6.3) to 6.5 and I have changed the packages (directories containing sentinl). After that I want to start my Kibana installation but it breaks down with the error (see server output)
Expected Behavior
Kibana is starting up,
Kibana logs and/or server output (attached if relevant)
Dec 07 10:10:59 server kibana[14774]: FATAL  Error: Cannot find module 'later/later'
Dec 07 10:10:59 server systemd[1]: kibana.service: main process exited, code=exited, status=1/FAILURE
Dec 07 10:10:59 server systemd[1]: Unit kibana.service entered failed state.
Dec 07 10:10:59 server systemd[1]: kibana.service failed.

...I have changed the packages (directories containing sentinl)

Did you install Sentinl like this?
./bin/kibana-plugin install sentinl.zip

Did you notice any error during or after the installation? Please try to reinstall Sentinl using the command above, the later package must be there.

I´ve reinstalled sentinl, now it works.

@Grashee can we close this issue too? https://github.com/sirensolutions/sentinl/issues/635

@sergibondarenko No the #635 issue is a new problem I have


The function GetPublicCompanies always throws the error index out of range [1] with length 1

Dear Team,
I was trying to list of all US public companies registered with the US Securities and Exchange Commission. We aimed to achieve this by using the API GetPublicCompanies API. Regrettably, this approach has consistently resulted in errors during our attempts.
Furthermore, I have made an attempt to troubleshoot the code locally by implementing certain modifications. Unfortunately, these adjustments did not yield the desired successful execution.
import (
	"context"
	"encoding/csv"
	"fmt"
	"net/http"

	"github.com/piquette/edgr/core"
)

func main() {
      headers :=  map[string]string{"User-Agent": "Steampipe/v0.x"}
	req, err := http.NewRequest("GET", "https://api.iextrading.com/1.0/ref-data/symbols?format=csv", nil)
	if err != nil {
		return []core.Company{}, err
	}

	for k, v := range headers {
		req.Header.Set(k, v)
	}

	resp, err := http.DefaultClient.Do(req)
	if err != nil {
		return []core.Company{}, err
	}
	defer resp.Body.Close()

	r := csv.NewReader(resp.Body)
	r.FieldsPerRecord = -1
	table, _ := r.ReadAll()
	result := []core.Company{}
	for _, row := range table {
		if len(row) < 2 {
			fmt.Sprint("ROW =====>>>>>", row)
			continue
		}
		sym := row[0]
		nme := row[1]
		if len(sym) > 5 || nme == "" {
			continue
		}
		result = append(result, core.Company{
			Symbol: sym,
			Name:   nme,
		})
	}
}

Could you please check it out and let us know I am doing anything wrong or it is a bug from SDK side?
Thanks!

Dear team, Is there any update on this issue?


Update 2016

Updated source code (-lssl => -lcrypto)
Updated README => README.md
Code style fixes

Hey mate!
Please review & merge the improvements I implemented :-)


Preview mode broken

@tobifroe when @Schille switched the domains yesterday and put the page live, I think he accidentally broke the preview mode. When previewing at the moment we get the content from Unikube but the styling is all blueshoe. For the live page it's fine though.

I fixed that already.
(wagtail configuration required a fix)


solved issue #436

PR Description 📜
New game
Fixes # <436>

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added entries for my game in main README.md
[x] I have added README.md in my folder
[ ] I have added working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @ePSA-eJya ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@ePSA-eJya Plz mention * in place of a number in main README file.

@ePSA-eJya Plz mention * in place of a number in main README file.
done

I have completed it. Please review and merge the pr.

Thank you  @ePSA-eJya , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Support for Llama 3

Feature Description
Llama 3 support
The Solution
Allow for llama 3 support
Considered Alternatives
na
Additional Context
No response
Related Features to This Feature Request

[ ] Metal support
[ ] CUDA support
[ ] Grammar

Are you willing to resolve this issue by submitting a Pull Request?
No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.

Llama 3 is already supported in version 3 beta


Python binding installation issues on OSX. Symbol not found: __ZTIN13IlmThread_2_04TaskE

Hello there,
I'm trying to get the OpenEXR Python bindings to work in my Python environment on OSX. So far, I've tried to install OpenEXR using Macports (i.e., sudo port install openexr which installs the C++ headers and libraries), and then use pip to install the Python bindings (i.e., pip install openexr). This installation procedure seems to work. However, when I try to import OpenEXR, I get the following error message:
ImportError: dlopen(/Users/mike/Library/Enthought/Canopy_64bit/User/lib/python2.7/site-packages/OpenEXR.so, 2): Symbol not found: __ZTIN13IlmThread_2_04TaskE
  Referenced from: /Users/mike/Library/Enthought/Canopy_64bit/User/lib/python2.7/site-packages/OpenEXR.so
  Expected in: flat namespace
 in /Users/mike/Library/Enthought/Canopy_64bit/User/lib/python2.7/site-packages/OpenEXR.so

Is what I'm doing a supported scenario? What is the recommended way of getting the OpenEXR Python bindings working on OSX?

Update: I get similar errors (i.e., "symbol not found; expected in flat namespace"), regardless of whether or not I use sudo port install openexr to install the OpenEXR C++ libraries, or if I build the C++ libraries myself. I've tried to build the C++ libraries with clang and gcc. I've also tried to build and install the Python bindings myself, by running setup.py build, and making sure to specify the CC and CXX environment variables to match the compiler used to build the C++ libraries.
In case anyone is reading this and running into similar issues, I can confirm that based on my experiments, it seems as though these Python bindings don't work on OSX. Or at the very least, it is not clear to me how to get them working.

Same trouble here, tried multiple ways of getting them to work..

I also have similar problems with macOS(10.10.5)
I think that this problem did not occur with openexr 1.7.0.
I'm trying backdating but I am in conflict with ImageMagick.
I can not change the environment for a while, but I will report it when I have made any progress.
People with similar problems may try backdating.
Old OpenEXR source is here.
http://www.openexr.com/downloads.html

I have the same problem with Python 2.7 on OSX 10.13.4.... I used brew install openexr and pip install openexr...Let me know if you find any solutions.

I really a trouble question, I try many meas to address this undefined symbol issue, but it does't work. Is there you anyone found any solutions. Thanks

On Ubuntu 16.04 with miniconda I was able to do the following:
conda install -c conda-forge openexr
which installs openexr 2.3.0
I cloned https://github.com/jamesbowman/openexrpython
I then manually modified the following lines of https://github.com/jamesbowman/openexrpython/blob/master/setup.py
include_dirs=['/path/to/miniconda/include/OpenEXR'],
library_dirs=['/path/to/miniconda/lib'],
and ran python setup.py install

HI @jbartolozzi，thanks for your reply.  it sounds good  solutions. I followed your step, and it still does't work. Steps are as follows. I indeed installed with miniconda inside openexr 2.3.0 since i found the error are different.  I wonder if  there are any other mistakes. Thanks
1、modify the set.py manually
include_dirs=['/raid/home/wangjian/miniconda2/include/OpenEXR'],
library_dirs=['/raid/home/wangjian/miniconda2/lib'],
2、python setup.py install
running install
running build
running build_py
running build_ext
building 'OpenEXR' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/raid/home/wangjian/miniconda2/include/OpenEXR -I/usr/include/python3.5m -I/raid/home/wangjian/tools/venv/include/python3.5m -c OpenEXR.cpp -o build/temp.linux-x86_64-3.5/OpenEXR.o -g -DVERSION="1.3.2"
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
x86_64-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.5/OpenEXR.o -L/raid/home/wangjian/miniconda2/lib -lIex -lHalf -lImath -lIlmImf -lz -o build/lib.linux-x86_64-3.5/OpenEXR.cpython-35m-x86_64-linux-gnu.so
running install_lib
copying build/lib.linux-x86_64-3.5/OpenEXR.cpython-35m-x86_64-linux-gnu.so -> /raid/home/wangjian/tools/venv/lib/python3.5/site-packages
byte-compiling /raid/home/wangjian/tools/venv/lib/python3.5/site-packages/Imath.py to Imath.cpython-35.pyc
running install_egg_info
Removing /raid/home/wangjian/tools/venv/lib/python3.5/site-packages/OpenEXR-1.3.2.egg-info
Writing /raid/home/wangjian/tools/venv/lib/python3.5/site-packages/OpenEXR-1.3.2.egg-info
3、check the installation
(venv) wangjian@dgx-1:~/miniconda2/lib$ pip list | grep OpenEXR
OpenEXR                 1.3.2
4、 check the final result， there is still the undefined symbol problem. But I notice that the printing information is different with the installation from pip directly

import OpenEXR
Traceback (most recent call last):
File "", line 1, in
ImportError: python3.5/site-packages/OpenEXR.cpython-35m-x86_64-linux-gnu.so: undefined symbol: _ZNK7Imf_2_314TypedAttributeISsE12writeValueToERNS_7OStreamEi

if if use the command 'pip install OpenEXR;, the error info is：
ImportError: python3.5/site-packages/OpenEXR.cpython-35m-x86_64-linux-gnu.so: undefined symbol: _ZNK7Imf_2_214TypedAttributeISsE12writeValueToERNS_7OStreamEi

FWIW, using the gcc demangler, we can find out that the missing symbol in question is:
Imf_2_3::TypedAttribute<std::string>::writeValueTo(Imf_2_3::OStream&, int) const

Running into some similar issue today.
Package IlmBase was not found in the pkg-config search path.
Perhaps you should add the directory containing `IlmBase.pc'
to the PKG_CONFIG_PATH environment variable
Package 'IlmBase', required by 'OpenEXR', not found
gyp: Call to 'PKG_CONFIG_PATH="/usr/lib/pkgconfig:/usr/local/Homebrew/Library/Homebrew/os/mac/pkgconfig/10.14:/Users/rchen/.gvm/pkgsets/go1.16.3/global/overlay/lib/pkgconfig:/Users/rchen/.gvm/pkgsets/go1.16/global/overlay/lib/pkgconfig::/usr/local/lib/pkgconfig:/usr/lib/pkgconfig" pkg-config --cflags-only-I vips-cpp vips glib-2.0 | sed s\/-I//g' returned exit status 0 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/Users/rchen/mup/build-meetup/node_modules/node-gyp/lib/configure.js:345:16)
gyp ERR! stack     at ChildProcess.emit (events.js:315:20)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
gyp ERR! System Darwin 18.7.0
gyp ERR! command "/Users/rchen/.nvm/versions/node/v14.16.0/bin/node" "/Users/rchen/mup/build-meetup/node_modules/.bin/node-gyp" "rebuild"
gyp ERR! cwd /Users/rchen/mup/build-meetup/node_modules/sharp

@chenrui333 The homebrew org is here - https://github.com/Homebrew ~ I'm not sure how to report an issue to the homebrew team, but it seems like an issue with their formula for OpenEXR?


example client fails with doozer 0.8

python examples/client.py
Traceback (most recent call last):
File "examples/client.py", line 6, in
import doozer
File "examples/../doozer/init.py", line 1, in
from client import connect
File "examples/../doozer/client.py", line 9, in
from msg_pb2 import Response
File "examples/../doozer/msg_pb2.py", line 285, in
DESCRIPTOR.message_types_by_name['Request'] = _REQUEST
AttributeError: 'FileDescriptor' object has no attribute 'message_types_by_name'
after starting the following i checked the source for the default ips.
doozerd -timeout 5 -l <IP_ADDRESS>:8046 -w <IP_ADDRESS>:8006 2>/dev/null &
doozerd -timeout 5 -l <IP_ADDRESS>:8042 -w <IP_ADDRESS>:8002 -a <IP_ADDRESS>:8046 2>/dev/null &
doozerd -timeout 5 -l <IP_ADDRESS>:8043 -w <IP_ADDRESS>:8003 -a <IP_ADDRESS>:8046 2> /dev/null &

after googling a bit.. it was the default installed protobuf libray which was causing problems..
installing a new version fixed my problems.
pip install<EMAIL_ADDRESS>--upgrade

Thanks for documenting the issue nevertheless!


StringsOpt can not start with dashes

If you want to supply additional options to pass to another program the syntax is limited.
Assuming that the option --args takes in these arguments and no one-character-alternative has been set, the = is required.
Meaning the following:
fails: --arg --wait
fails: --arg -w
works: --arg=--wait
works: --arg=-w

I can understand the reason for this but still feel this bahaviour to be inconsistent.

Hm - seems to me you missed the "--" seperator?
From README in Section https://github.com/jawher/mow.cli#spec-strings
...
The -- operator can be used to automatically treat everything following it as arguments. In other words, placing a -- in the spec string automatically inserts a -- in the same position in the program call arguments. This lets you write programs such as the POSIX time utility for example:
x.Spec = "-lp [-- CMD [ARG...]]"

// Allows parsing of the following shell command:
//   $ app -p ps -aux

The thing is that -- is not the correct solution. It's not an argument but a parameter, as you can see in the example I provided.  FILES...

Arguments:
  FILES                the source files that will be added to the editor

Options:
      --editor         executable of the editor (env $EDITOR) (default "vi")
      --arg            arguments for the editor (default ["{}"])

(removed some options, but you should get the gist) The issue is with --arg which allows passing arguments for the editor.

Moritz @mpldr
I am sorry, I do not get what you expect.
Shouldn't it
br --editor FILES... [-- ARG...]

so let you call
br --editor file1.txt file2.txt -- -w

Just as I would expect it from documentation?

No, a call would be something like:
`br --editor sed --arg=-ie --arg 's/1/2/g' --arg {} *.txt

Ah, ok, got it.
Will it work already if you use parenthesis?
br --editor vim --arg "{}" --arg "+%s/1/2/g" --arg "+x" *.txt

while *.txt will become automatically
br --editor vim --arg "{}" --arg "+%s/1/2/g" --arg "+x" file1.txt file2.txt filea.txt

if the files exist on command call.

The problem is not the vim version, it just served for illustration. The interesting part is the --arg=-ie for sed. Not the Shell-Side expansion of globbing patterns.

Yes got all from previous posts
I just wonder and ask if the Parenthesis will already help to function StingOpts
So I ask for the sequence
--arg "{}" --arg "+%s/1/2/g" --arg "+x"

only if that will work and StingOpts detect this correctly also without a equal sign =

Because of how (most) shells work, unfortunately this does not change anything. The quotation marks (I guess by parenthesis you mean them) are only used by the shell to call the process and determine where an argument starts. The quotation marks themselves are not added to the process's arguments. An easy way to try it out would be to run:
package main
import "os"
import "fmt"
func main() { fmt.Println(os.Args) } // the quotation marks would be printed here as well

Ok, got that also - for sorry
I just look if something will allow the parser to catch the second value after --arg as a string value and not a new argument.
Maybe that will be stayed safe thru the shell?
--arg '"-ie"' --arg '"+%s/1/2/g"' --arg '"+x"'

Its not the solution - just as a test if the parser currently would recognize those correctly

here is what it looks like to the program: [/tmp/go-build861777601/b001/exe/main --arg "-ie" --arg "+%s/1/2/g" --arg "+x"]
and the actual program tells me:
> ./bulkrename --editor sed --arg '"-ie"' --arg 's/6/4/g' *
sed: -e expression #1, char 1: unknown command: `"'

Well, thanks for feedback.
Did I get it correctly, that even the params do not work for the forwarded sed, this time the values are correctly attached to the --arg param of the mow.cli app?
So if you would drop the (") inside your golang mow.cli app then the call for sed will work?
If so, the parser needs a to identifiy - as string after an argument

I mean… technically it would be possible to remove this, but I am not a fan of special behaviour and this might very well cause some issues. While there might not be a "correct" answer on this, there might be a "best solution"… (I mean… I documented this behaviour with my program but just wanted to bring it up)


docs fix collapse flags

To collapse input use #collapse, #collapse_show instead of #collapse_input, #collapse_input show.
Change information in docs.
#410

Many thanks - merged through CLI due to conflicts.


Extension causes high cpu load

Issue Type: Performance
Extension Name: jupyter
Extension Version: 2020.11.372831992
OS Version: Windows_NT x64 10.0.19041
VSCode version: 1.51.1

:warning: Make sure to attach this file from your home-directory:
:warning:c:\Users\zuhay\AppData\Local\Temp\ms-toolsai.jupyter-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

@Zuhayer-Bin-Javed, we need the file noted to be able to investigate this problem.
c:\Users\zuhay\AppData\Local\Temp\ms-toolsai.jupyter-unresponsive.cpuprofile.txt


Epic: SCSS utility classes aligned with design system

Description
This epic covers the creation of design system-based utility classes in our SCSS library. The goal is to develop a consistent, scalable, and maintainable set of utility classes that adhere to the design system's core principles, such as spacing, typography, colors, and other design tokens.
Atomic CSS Approach
We will use an Atomic CSS methodology to create single-purpose utility classes. Each class will be responsible for a single styling property, ensuring maximum reusability and flexibility. This approach will simplify the development process and promote consistency across the application.
Key Objectives

Define a comprehensive set of utility classes for common design system properties (e.g., margins, padding, typography).
Ensure that the utility classes are consistent with the design tokens used throughout the design system.

Deliverables

Utility classes covering design system tokens like spacing, typography, and colors.

Utility class examples:

Bootstrap
Bulma
Tailwind

Linked tasks:

[x] #2432
[x] #2453
[x] #2460
[x] #2461
[x] #2463
[x] #2464
[x] #2466

This epic was successfully accomplished


callback execution hell gives many errors at runtime

Summary
I have a callback that get called from a websocket from my browser and I'm using a #[wasm_bindgen] function in an impl that I am calling to retrieve the result inside the Rust environment
my js:
const p = create_peer( );

socket.on( async ( message ) => {

  await p.on_message(  message )

} );

my rust
impl Peer {

  ...

  on_message ( &self ) {

    self.clone().member = some_value;
    ...
    something.await;
    ...

  }

  ...

}

pub fn create_peer() {

  let peer = Peer::new()

  peer.some_function_that_sends_message_to_web_socket();

}

basically my impl self is referenced into many methods and many operation get triggered asynchronously both on js and rust side.
This is resulting in many errors unreachable or already borrowed or recursive use of object, I would say I'm kinda facing some sort of callback execution hell.
So my question is how can I make sure both environments keeps running the tasks in a manner I don't trigger a function make use of an already borrowed element. How can I keep both environments in sync because all of these errors always show on runtime which make them really hard to debug?
Thanks
ps:if you need more code please tell me.

Hi, I'm not associated with this project but I'm writing similar code. I'm interested in the error you're running into because I want to know if I'll end up with the same problem.
I did a trivial test of a recursive call and didn't run into any errors. I also peeked at the code the macro generates and didn't spot any locking or anything fancy. But I may well have missed something.
Do you have an example I can run that will fail with the error you're getting? (Ideally you'd reduce it to as little code as necessary to get to the error). I'm interested in taking a look.
Unrelatedly self.clone().member = value looks fishy. You're creating a duplicate of self, mutating it, and then throwing it away.

This doesn't really look like a wasm-bindgen problem to me, but just a borrowing issue with the Rust language itself.
I'm happy to take a look if you could provide a minimal self-contained example.


Code may not work properly after running for 50 days straight

The timers are based on the millis() and micros() functions from arduino, but reading the description of the millis() function on the arduino reference page:
"Returns the number of milliseconds passed since the Arduino board began running the current program. This number will overflow (go back to zero), after approximately 50 days." (reference
I found that after 50 days this function will go back to zero, and the code may malfunction.

The library should work as expected after overflow. What is the malfunctiom?


使用谷歌搜索一直报错，是否需要升级什么版本？Can not find chromedriver for currently installed chrome version

Can not find chromedriver for currently installed chrome version

[17:28:22]  driver = webdriver.Chrome(chrome_path, chrome_options=chrome_options)
[17:28:22]  TypeError
[17:28:22]  :
[17:28:22]  init() got an unexpected keyword argument 'chrome_options'
[17:28:22]  stopped

I resolved this issue by downloading chromedriver and adding it to PATH.
Then I commented utils.py lin 72-79
def resolve_dependencies(driver=str):
    if "chrome" in driver:
        print("Checking Google Chrome and chromedriver ...")
        #driver_path = chromedriver_autoinstaller.install()
        #if not driver_path:
        #    return False
        print("OK.")
    return True

same issue, gennaromellone's tip didn't work for me.

chromedriver

Works for me !!!
For anyone who cant find histroy version of Chrome or Chromedriver, here is the link: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html


Using flow, OrderedMap#merge cannot be called with a KeyedSeq

What happened
In immutable 4.0.0-rc.7 (and flow 0.57.1), I’m getting this flow error when trying to merge a KeyedSeq into an OrderedMap:
Error: src/model/transaction/removeRangeFromContentState.js:72
 72:   blockMap = blockMap.merge(newBlocks).filter(block => !!block);
                  ^^^^^^^^^^^^^^^^^^^^^^^^^ rest parameter array of call of method `merge`. Has some incompatible type argument with
938:     ...collections: (Iterable<[K_, V_]> | PlainObjInput<K_, V_>)[]
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ array type. See: node_modules/immutable/dist/immutable.js.flow:938
  Type argument `T` is incompatible:
     72:   blockMap = blockMap.merge(newBlocks).filter(block => !!block);
                                     ^^^^^^^^^ KeyedSeq. This type is incompatible with
    938:     ...collections: (Iterable<[K_, V_]> | PlainObjInput<K_, V_>)[]
                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ union: type application of identifier `Iterable` | type application of polymorphic type: PlainObjInput. See: node_modules/immutable/dist/immutable.js.flow:938
      Member 1:
      938:     ...collections: (Iterable<[K_, V_]> | PlainObjInput<K_, V_>)[]
                                ^^^^^^^^^^^^^^^^^^ type application of identifier `Iterable`. See: node_modules/immutable/dist/immutable.js.flow:938

I had expected KeyedSeq to be a part of Iterable<[K_, V_]>, but it seems that isn’t the case?
How to reproduce
var newBlocks = blockMap
    .toSeq()
    .skipUntil((_, k) => k === startKey)
    .takeUntil((_, k) => k === endKey)
    .concat(Immutable.Map([[endKey, null]]))
    .map((_, k) => { return k === startKey ? modifiedStart : null; });

  blockMap = blockMap.merge(newBlocks).filter(block => !!block);

Full source here: https://github.com/facebook/draft-js/blob/master/src/model/transaction/removeRangeFromContentState.js#L68

Thanks for the report. I'd also have expected KeyedSeq to match Iterable<[K_, V_]> - I'll try out a flow test for this

Hmm, I just put that exact reproduction case into a flow test (with some mocked values) and saw flow pass. I'm putting up a PR for a simpler test case which is also passing.
Do you mind testing out the master build ("immutable": "facebook/immutable-js#npm") just to see if this issue was fixed on master since the last RC was released? I've been steadily improving flow types, so it's possible this was fixed

Running npm install immutable@facebook/immutable-js#npm removed that flow error, so it looks like this issue has been resolved. Thanks for the help!

Awesome, thanks for the confirmation! I'll get a build on npm so you can rely on that


feat!: Add primary name server to outputs in modules/zones. Bump AWS provider version to 4

Description
One more output has been added in zones module in this PR: primary_name_server.
Motivation and Context
This new output could be useful if SOA record modification is required in dependent modules.
Breaking Changes
No breaking changes
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

Thank you for for your review. I've updated the version of aws provider at zones module.

This PR is included in version 4.0.0 :tada:


Combine with built in integration

I currently use the built in Fronius integration and it works well.
Occasionally though there may be an issue with something in the chain and my HA data is lost.
Examples are, Fronius data logger loses connection, Home assistant is off for a while etc.
Because the inverter stores data, when connection is restored Solar.web catches up this missing data.
A great feature IMHO, would be to combine the two. The Fronius integration for fast updating and local operation, and your integration for filling in missing data from solar.web.
Would it be possible to have you plug-in check for existing data and only add solar.web if missing?
Perhaps it already does, as I have not yet tried both integrations together and your documentation implies to run one or the other only?

Hi, prior to creating this repo I approached the existing repo owners suggesting the two be combined. They preferred keeping it separate. Happy for you to raise it again with them.

I had the same thought, yes it would be perfect if they were combined. I suspected they may not want to change theirs, so thought I'd ask if you would consider changing yours to only update any missing data?
This way the existing one is installed to get live data, and your integration if installed as well only adds missing data.

I don't know how that would work. Happy to review a PR if you've got a workable solution.

Hi 👋!

They preferred keeping it separate.

If I remember correctly, my suggestion was to keep the communication libs ([pyfronius](https://github.com/nielstron/pyfronius) and your [python-fronius-web](https://github.com/drc38/python-fronius-web)) separate as they used a very different tech stack (httpx vs aiohttp, pydantic vs custom parser). I still think this is a good idea so each can individually be updated, tested and be used in other projects.
I do not have any objections to import and use both libraries in the HA core Fronius integration.
That said, the local SolarAPI pyfronius uses does provide historical data as well, however using this endpoint is not implemented currently.

I'd be happy if it was incorporated into the core HA fronius integration using @farmio's approach, this repo could then be sunset.

Great! @JCalvi are you planning on working on this? I'd be happy to do reviews or answer questions along the way (if I can 🙃).

Hi @farmio, no I was just hoping to see some merging of these two projects.
Happy to help test, but coding it was not in my plans.


Update README: Public CDN URLs

As detailed in #174, add a quick entry to the readme to explain how to use jsdelivr.com to serve Epoch.

@rsandor Sent in a pull request with the addition.

@srinath-v - When you made the PR you could have added Fixes #184;  in the title along with the description of the change. If done that way it will automatically close the associated ticket when the PR is merged :).

@rsandor Still quite new to all this. Will keep in mind.


Add pre-commit hook for bsrefmt. Run refmt over codebase.

This PR is purely a formatting PR. It adds a yarn refmt script that runs the bsrefmt CLI over the whole codebase, and a husky pre-commit hook to do the same. There are no actual code changes included in this PR. @kitten the main motivation for this PR is just to get wonka to a state where it works with refmt so the code is a bit more readable and so that we have nice editor integration with Jared's reason-language-server. If you don't want to include this change, no worries. I've just found myself disabling editor settings when working on wonka tests previously so I didn't end up with a bunch of formatting changes in the diff. But since we have a formatter in Reason, we might as well use it!

Coverage remained the same at 72.83% when pulling 4be36ace5af2c88d1c8e517b902429a5e96f5ac4 on parkerziegler:task/add-refmt into 6be9f26afbbc46a58324b3f7d42909f16f65cbdb on kitten:master.

Dang I hadn't heard about the formatting drama. But thanks for merging it, I think it'll at least give us a standard pattern across editor setups (even if it's one we don't like). I'll work more on docs / tests this weekend!


support test owners

Describe the bug
When we add an owner in meta on a custom generic test, owner doesn't appears in slack alert
To Reproduce
Steps to reproduce the behavior:

Create a custom generic test in DBT with a meta

run the test and run a monitor to send an alert in a slack channel

See owner missing in alert

Expected behavior
We expected to have the tag for owners as it appears for subscribers
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

edr Version: 0.6.7
dbt package Version: 0.9.2

Additional context
Add any other context about the problem here.

Hi @kimLalilo,
Starting in edr v0.6.10, we also support getting the owners from the test's meta field.
Please upgrade by running pip install --upgrade elementary-data.
Thanks.


Conversion of JS to use relative paths

Hi,
I'm going through a bunch of ComfyUI nodes and resolving some things here and there, as well as examining source.  A thing I noticed is that your imports are all absolute pathed.  I'd suggest adopting relative pathing so that comfyui doesn't have to be at / folder for a given project/company/website.
Most other nodes do follow that pattern already.  Otherwise, looking sharp.  Thanks for your help!

Hi,
Thanks for reaching out.
At a glance, that seems trivial to change, but I won't be coding before 6th of April.
If you already fixed the problem on your end, I suggest that you send a pull request;  I should review it next weekend.
Best Regards

https://github.com/bmad4ever/comfyui_bmad_nodes/pull/11
As mentioned, test before pulling

merged #11 .


Lustre not mounting correctly

I am using the following lustre parameters in the config.yml file and all compute nodes are using
OpenLogic:CentOS-HPC:7_9-gen2:latest
lustre:
rbh_sku: "Standard_D8d_v4"
mds_sku: "Standard_D8d_v4"
oss_sku: "Standard_D32d_v4"
oss_count: 2
version: "2.12.4"
hsm_max_requests: 8
# optional to use existing storage for the archive
mdt_device: "/dev/sdb"
ost_device: "/dev/sdb"
hsm:
# if not included it will use the azhop storage account that is created
storage_account: #existing_storage_account_name
storage_container: #only_used_with_existing_storage_account
On HB120rs_v2 compute node, I do not see lustre mounted?
[garvct@ip-0A001004 ~]$ df -h
Filesystem               Size  Used Avail Use% Mounted on
devtmpfs                 225G     0  225G   0% /dev
tmpfs                    225G     0  225G   0% /dev/shm
tmpfs                    225G   25M  225G   1% /run
tmpfs                    225G     0  225G   0% /sys/fs/cgroup
/dev/sda2                 30G   20G   10G  66% /
/dev/sda1                494M  166M  329M  34% /boot
/dev/sda15               495M   12M  484M   3% /boot/efi
/dev/sdb1                473G   73M  449G   1% /mnt/resource
<IP_ADDRESS>:/home-nxkogxwk  4.0T     0  4.0T   0% /anfhome
on ood lustre is mounted, but are the permissions correct?
[garvct@ondemand ~]$ df -h
Filesystem               Size  Used Avail Use% Mounted on
devtmpfs                 3.9G     0  3.9G   0% /dev
tmpfs                    3.9G     0  3.9G   0% /dev/shm
tmpfs                    3.9G   81M  3.8G   3% /run
tmpfs                    3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/sda2                 30G  3.6G   26G  13% /
/dev/sda1                494M   72M  422M  15% /boot
/dev/sda15               495M   12M  484M   3% /boot/efi
/dev/sdb1                 16G   60M   15G   1% /mnt/resource
<IP_ADDRESS>:/home-nxkogxwk  4.0T     0  4.0T   0% /anfhome
<IP_ADDRESS>@tcp:/LustreFS   2.4T  2.5M  2.3T   1% /lustre
tmpfs                    783M     0  783M   0% /run/user/0
tmpfs                    783M     0  783M   0% /run/user/10001
drwxr-xr-x.   3 root root 4096 Jul 24 16:18 lustre

I see this error in the jetpack logs
modprobe: FATAL: Module lustre not found.
Unable to mount lustre

lustre client is not installed on image.
[garvct@ip-0A001004 scripts]$ rpm -qa | grep -i lustre
[garvct@ip-0A001004 scripts]$

Resolved: Need a Custom image with lustre clients preinstalled.


Fixed speechOutput so it does not overwrite itself

speechOutput string was overwriting itself so Alexa would not say 'I'm sorry, I currently do not know  ...' when a bad input was given.
I added two concatenations to fix the problem.
Thanks

Thanks for submitting this PR, which applies to a previous version of the skill.  I checked and the latest version does not have this issue.


Add repo collaborators API

Adds API for this

Coverage decreased (-1.6%) to 88.073% when pulling 28f157f2afdd7bc6413f06565b445e809269bf0c on andersklenke:add-repo-collaborators-api into 973fc9b0a137f3ee1fdac9b26c3bece6a854b66a on edgurgel:master.

Coverage increased (+0.1%) to 89.862% when pulling a1f111c4408a85e81968dc5ec06841c87cdbf34a on andersklenke:add-repo-collaborators-api into 973fc9b0a137f3ee1fdac9b26c3bece6a854b66a on edgurgel:master.

I have added tests for all the endpoints.

Coverage increased (+0.1%) to 89.862% when pulling da9af6df90ddb6a381566cf98dfc13ace4097790 on andersklenke:add-repo-collaborators-api into 973fc9b0a137f3ee1fdac9b26c3bece6a854b66a on edgurgel:master.

Nice! Thank you @andersklenke


Path of a removed lib/ver.

Log:
$ haxelib version
3.2.0-rc.3

$ haxelib list h3d
h3d: git [dev:/Users/ak/Developer/Haxe/libs/h3d/git]
$ haxelib remove h3d git
Library h3d version git removed

$ haxelib path h3d
Library h3d version dev is not installed
fzzr:bin ak$ haxelib list h3d
h3d: [dev:/Users/ak/Developer/Haxe/libs/h3d/git]

$ cd /Users/ak/Developer/Haxe/libs/h3d/
$ ls -GFAC
.DS_Store  .current   .dev
$ cat .current
dev
$ cat .dev
/Users/ak/Developer/Haxe/libs/h3d/git

After haxelib remove h3d git a git directory really was deleted. But not removed record about it in the .dev (devPath).
Anyway I try to remove current version but no getting exception about it impossible (Main.hx#L1125).
If we can remove the current version and when the library not contain other versions => maybe we have to delete this library fully (in my case: /Users/ak/Developer/Haxe/libs/h3d) ?

This is somewhat related to #263, but that issue is quite heavy, so let's fix this for now by checking whether the path we're removing is the same that specified in .dev and remove the .dev file if so.
Removing the whole library folder when last version is removed makes sense too, i'll make another issue for that.

Or rather, forbid removing version if its path is specified in .dev (which will be true for vcs checkouts), so the behaviour is consistent.


How much data do i need to train a melGAN from scratch?

Hello.
How much data do i need to train a melGAN from scratch? Will 3 hours be enough to generate speech?

I tried with 1 hour of speech to train from scratch with mb-melgan.
The quality is not so good but not so bad.
(In the case of PWG, it works well with only 1 hour of data).
So I think 3 hours of data is worthwhile to train from scratch.

@kan-bayashi Thanks. You have already helped me many times. Could you give me your contacts? I would like to ask you a few more questions regarding speech synthesis, possibly for a fee if you are not interested in answering them. I will delete this post after your reply.


add sha256 support

By default OpenSSL generate a deprecated sha1 CSR. Just need to add -sha256 to the 'Generate CSR' command.

@Sispheor don't hesitate to submit a PR :)

@Sispheor Done in last release


Proxy hit error in headless setup

Hi,
thanks for providing this proxy solution!
I am having trouble setting it up though. My frontend is a static build with Astro JS.
The pirsch php proxy is on a separate server together with the CMS.
My frontend is in staging level on let's say "stage.xyz.de". This is also the host i added in the pirsch dashboard.
The content url is "content.xyz.de". This is where i load the scripts from which works fine.
I created a client in the dashboard, added id and secret to the config.php and "stage.xyz.de" as the host.
Now when i load the page i get an console error alongside a 400 bad request from "hit" as well as "session" requests saying:
"Identification code not found for domain. Make sure you're sending requests from the configured domain or subdomain. Identification codes and domains are cached for up to 5 minutes."
I know there is a separate Id code in the dashboard. I've tried adding it via the data-code-attribute to the script tag but that did not help.
Any hint or help much appreciated,
thanks
np

Hi,
did you set up the data-endpoint attribute correctly? The proxy doesn't use the identification code, as it directly makes use of the API. The error message however looks like it has been directly sent to pirsch.io. Can you check your browser network tab to see if that's the case?
<script defer type="text/javascript"
    src="/custom/path/pirsch.min.js"
    id="pirschjs"
    data-endpoint="/custom/path/hit.php"></script>

Hey,
thanks for getting back.
As for the data-endpoint i was under the impression that i only have to set it up if i use a custom path. Since i have the proxy inside a folder pirsch in the docroot i felt like that is the default.
As for the request itself. It looks like it targets the api as expected:
:authority: api.pirsch.io
:method: GET
:path: /hit?nc=1724139002250&code=zO ...
:scheme: https
accept: */*
accept-encoding: gzip, deflate, br, zstd
accept-language: de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7
cache-control: no-cache
origin: https://stage. ...
pragma: no-cache
priority: u=1, i
referer: https://stage. ...
sec-ch-ua: "Not)A;Brand";v="99", "Google Chrome";v="127", "Chromium";v="127"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "macOS"
sec-fetch-dest: empty
sec-fetch-mode: cors
sec-fetch-site: cross-site
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36

Okay, in that case, you need to add the data-endpoint attribute. Our JavaScript endpoint will look for the identification code that is missing from your request. The proxy directly uses the API, where the identification code isn't required (auth is handled by the client access key or id + secret).
The entire point of the proxy is that all requests are first-party. Right now you're only hosting the script files yourself.

Ok. Got it. The error is gone. Now i got a CORS-Problem but i guess that is a problem in my setup out of this scope?
Script tags look like this now. For the error see screenshots attached.
<script defer type="text/javascript" src="https://content.xyz.de/pirsch/pirsch.min.js" id="pirschjs" data-endpoint="https://content.xyz.de/pirsch/hit.php"></script>
<script defer type="text/javascript" src="https://content.xyz.de/pirsch/pirsch-sessions.min.js" id="pirschsessionsjs" data-endpoint="https://content.xyz.de/pirsch/session.php"></script>

I don't really get why the overview states "CORS Error" while the detailed view says "200" but i guess i have to figure that out with hosting.

Yup, you can try setting the CORS headers on the proxy:
header("Access-Control-Allow-Origin: *");
header("Access-Control-Allow-Headers: *");

Through htaccess might also be an option.

Another step.
I've set the headers. CORS is fine now.
The requests seem to work as expected. I still don't get any data in my dashboard though :(
I've checked the Client ID, Secret and Host. I also added the data-code attribute to the scripts. Hostname (also in the dashboard) is stage.xyz.de as that is my frontend url.
I've also tried setting up a second website in the dashboard with content.xyz.de as the host, added a new client there and used the settings for the config.php. Also no hits / page views in the dashboard.
Any idea what could be the problem?
My frontend is protected by htaccess / passwd but that cannot be a problem i guess since the content-server is communicating with the api 🤔

The requests could get stuck in the bot filter. Is your proxy behind a load balancer or another proxy (Cloudflare?). In that case, you might need to configure an HTTP header to extract the real visitor IP address from, or otherwise, our service only receives your server's/proxy IP address, which will be filtered.
The PHP SDK and proxy are a bit outdated and don't support this out of the box. I need to update it. It would still be good to know if that's the cause of your problem :)

Yes, I think that would be the better option for now. The Go proxy supports configuring a header.
Just for context: the PHP proxy currently only accepts the remote IP. If a proxy or load balancer is involved, the remote IP will be that of the proxy/LB instead of the actual visitor IP address. It's possible to get around this by extracting the visitor IP out of a header set by the proxy/LB (like X-Forwarded-For for example).

I've released version 2 of the proxy, although it doesn't support setting the headers right now...
Can we close this issue for now?

Yes. Sorry for the delay.

I just got info that we can get the original IP just like you expected via X-Forwarded-For.
Hosting says: X-Forwarded-For is a comma seperated list of addresses where the first one is the original visitor ip.
Can you give a hint on how to actually pass this address to the script then?

I just got info that we can get the original IP just like you expected via X-Forwarded-For.
Hosting says: X-Forwarded-For is a comma seperated list of addresses where the first one is the original visitor ip.
Can you give a hint on how to actually pass this address to the script then?

Well, that's the issue with the PHP proxy currently. It only supports the remote IP address:
https://github.com/pirsch-analytics/pirsch-php-proxy/blob/master/p/proxy.php#L67
As you can see, I've started implementing header support but didn't finish yet. I guess I should do that right now to get it out of the way. I'll let you know when it's ready, probably later today :)

Alright, could you give it a shot?
https://github.com/pirsch-analytics/pirsch-php-proxy/releases/tag/v2.1.0
You need to update the configuration to include the header:
return (object) array(
    'ipHeader' => array('X-Forwarded-For'),
    'clients' => array(
        (object) array(
            'secret' => 'your-client-secret'
        )
    )
);

I've deployed 2.1.0 on the server at content.xyz.de/p
config updated looks like this:
return (object) array(
  'ipHeader' => array('X-Forwarded-For'),
  'clients' => array(
    (object) array(
      'id' => 'KUr...',
      'secret' => 'jFy...',
      'hostname' => 'content.xyz.de'
    )
  )
);

Script in the frontend head looks like this:
<script defer type="text/javascript"
      src="https://content.xyz.de/p/p/p.js.php"
      id="pianjs"
      data-hit-endpoint="https://content.xyz.de/p/p/pv.php"
      data-event-endpoint="https://content.xyz.de/p/p/e.php"
      data-session-endpoint="https://content.xyz.de/p/p/s.php"></script>

When i visit the frontend i see one related request:

Nothing in the Dashboard yet. Am i missing something?

Hmm, looks good to me. It might take a few seconds before the page view appears on the dashboard though.
If it doesn't, could you add a php file with the following code to see if it spits out your real IP address?
<?php

function parseXForwardedForHeader($value) {
    if (!isset($value)) {
        return '';
    }

    $parts = explode(',', $value);

    if (count($parts) > 0) {
        return cleanIP(trim($parts[0]));
    }

    return '';
}

function cleanIP($ip) {
    if (str_contains($ip, ':')) {
        $parts = explode(':', $ip, 1);
        return $parts[0];
    }

    return $ip;
}

echo parseXForwardedForHeader($_SERVER['HTTP_X_FORWARDED_FOR']);

Perfect! It should track then. Are you behind a proxy or VPN or something? Could you send me a link to<EMAIL_ADDRESS>so that I can have a look?

Just in case somebody else stumbles across this issue.
Stats work fine via the 2.1.0 proxy. Last issues were related to some special circumstances with the hosting.

Awesome! Thank you for your patience :)