Possible bug? Acrylic can not be enabled for Ubuntu profiles

Hi,
I don't know if this is a bug or a known limitation (I tried googling but couldn't find anything). Anyway, I'll try to keep this short and simple. I am trying to enable acrylic for my Ubuntu profile:

But when I save my changes the acryclic switch is reset to off:

Acryclic does seem to work just fine for Powershell and CMD. This happens on both of my computers. I am using the Windows Terminal Preview from the Microsoft Store. If anyone knows what is causing this issue then please let me know :)

What is the version you're using? Please fill the template to provide the necessary information.

Yea, the specific version number would help here. But we have been seeing a good number of these "I change a setting and it didn't apply" issues - see #9855, #9864. There's something weird about layering and the SUI, that's for sure.

We've managed to track down a minimal repro of this. We're now tracking this in #9962. Thanks for the help!
/dup #9962

Sorry for not following up! The exact version I am using right now is 1.8.1032.0, however the version I was using when reporting the bug above was Windows Terminal Preview installed from Windows Store the same day as I reported the bug. However it seems the issue is gone now and I can apply the acrylic effect to Ubuntu. I don't know if it's because the app has been updated, or if it's because there are some specific factors that affects this. Let me know if there's anything else I can help with :)

It also happen to me, but after I deleted acrylic-related settings in specific ubuntu profiles it works.


Show chapter for internal link suggestions

Short description

This pr changes the internal link suggestions to show the full path to an object translation instead of just its title.
As a sideeffect, the title will be shown in the backend language instead of the object translation's language.
I did not change the general search input feature, because there it is not ambiguous which object is which after performing the search.
Proposed changes

Add  a path to the JSON objects returned by search_content_ajax
Display the path instead of the title in the internal link suggestions

Side effects

/
Resolved issues

Fixes: #1752

Pull Request Review Guidelines

Sorry for the delay..
The path should now be displayed in the current language.

Yes, I agree. The issue we had before is fixed now. Thank you a lot!

Hey @david-venhoff Since we are adding your change to today's release, I'll take the liberty of merging your PR. Nevertheless, many many thanks for your work and best regards from the conference in Dortmund! :)

Thanks you! :)


Introduce a release script

What
Add a script for preparing the library for a release. I've got something similar (though less solid) on my preparing my legacy buildpack for a release: https://github.com/heroku/heroku-buildpack-ruby/blob/a1dc09a93fc81a73482d6db0ecb02298001d5af4/Rakefile#L70-L104.
While this isn't a buildpack, the preparation and updating are similar experiences.
Why
Releasing is a chore. Automation improves quality and reduces toil.
Worst case, this is a throwaway experiment:  I want to explore automating our processes using Rust to serve as an opportunity for me to learn and to inform future efforts in scripting and automation.
Best case, it helps us move towards more automation: For example, we could move this logic into a GitHub action. That would allow one fewer review step for the release process.
Demo
$ cargo run -p prepare
    Finished dev [unoptimized + debuginfo] target(s) in 0.37s
     Running `target/debug/prepare`
# Preparing libcnb.rs for release

 - Found project root at /Users/rschneeman/Documents/projects/work/libcnb.rs

## Detecting semver from CHANGELOG.md

- Semver change is: Major

## Updating Cargo.toml /Users/rschneeman/Documents/projects/work/libcnb.rs/Cargo.toml

- Last release was version: '0.11.3'
- Updated version: '1.0.0'

## Updating CHANGELOG.md /Users/rschneeman/Documents/projects/work/libcnb.rs/CHANGELOG.md

- Done

Features
Detect SemVer value from CHANGELOG.md
The script parses the CHANGELOG.md as an AST and knows if the next feature should be a major/minor/patch bump based on the presence/absence of Changed/Added/Fixed sections.
Update the Cargo.toml
Once we know the semver change, the script can read in the old version from Cargo.toml, apply the SemVer update to that version and write the new version back to Cargo.toml. This process uses toml_edit which preserves formatting including whitespace, ordering, and comments.
Updating the CHANGELOG.md
Finally the changelog needs to move the elements under ## [Unreleased] to a new section with the version and date. The version was determined previously and the date is grabbed via crono.
Draft comments
I'm looking for feedback on the overall idea as well as implementation-specific bits. The intent here is to be explorative so, go wild. That being said, I would like to actually ship some automation, so while it will be valuable to think about the best possible ways forward, I'm also looking for guidance on where "good enough" lies.
Ultimately I want scripting and automation to be high-quality and robust (both to the user and maintainer), but I'm mindful that it should be pragmatic as well.

Closing because this is a stale PR. Feel free to re-open at any time if this is still relevant at this point in time.

Btw I found https://github.com/crate-ci/cargo-release which would avoid the need to write our own custom tooling.


(Re)introduce Property.replace

Fixes #27227
This PR reintroduces update() method pulled from 8.6 release under a new name.
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test PRF, BD

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test RfN

I've triggered the following builds for you. Click here to see all build failures.

ReadyForNightly build

The merge queue build has started. Click here to see all failures if any.


Shadow DOM: DOMException: Failed to execute 'attachShadow'

Version
2.6.14
Reproduction link
https://gist.github.com/praveenpuglia/0832da687ed5a5d7a0907046c9ef1813
Steps to reproduce
I want to set, or select shadow DOM, but gives an error: DOMException: Failed to execute 'attachShadow' on 'Element': This element does not support attachShadow
What is expected?
I want to create show dom.
What is actually happening?
gives an error: DOMException: Failed to execute 'attachShadow'

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.


Weather fetcher using API

Prerequisites

[X] I am a GSSoC-22 Participant
[X] I checked to make sure that this issue has not already been filed

Description
It is a python automation project using API . It tells us the weather of a given place.
Tech Stack
Python

@srinjoy-26 go for it, Good Luck 👍

issue resolved with #197


fix: not to be deleted a container created with --rm when detaching

In the current implementation, detaching from a container started with
nerdctl run --rm ... unexpectedly removes it.
The behaviour before this modification is as follows.
> nerdctl run --rm -it --detach-keys=ctrl-a,ctrl-b --name test alpine
/ # INFO[0002] read detach keys

> nerdctl ps
CONTAINER ID    IMAGE    COMMAND    CREATED    STATUS    PORTS    NAMES

When the same operation is performed in the Docker CLI, the container will
not be deleted.
This issue is reported in the following:

https://github.com/containerd/nerdctl/issues/3568

Therefore, this commit resolves this behaviour of a container not being
deleted on detachment.
Note that the behaviour after this modification is as follows.
> nerdctl run --rm -it --detach-keys=ctrl-a,ctrl-b --name test alpine
/ # INFO[0010] read detach keys

> nerdctl ps
CONTAINER ID    IMAGE                                        COMMAND      CREATED           STATUS    PORTS    NAMES
46f4c829e5cc    docker.io/library/alpine:latest              "/bin/sh"    15 seconds ago    Up                 test

This PR has also been modified to remove a container when detaching and
attaching a container started with the --rm option.
The detailed behaviour is as follows.
> nerdctl attach test

/ # exit

> nerdctl ps -a
CONTAINER ID    IMAGE    COMMAND    CREATED    STATUS    PORTS    NAMES

Hi, @apostasie @djdongjin @AkihiroSuda
Could you review this PR when you have time ?

Thanks for the ping @haytok
I don't think that works yet.
If you detach, then attach, then exit, the container is not removed (it should).
Run and detach
nerdctl run --rm -ti --name foo debian
root@c9951514746b:/# INFO[0001] read detach keys

then attach and CTRL+D.
nerdctl attach foo
root@c9951514746b:/#
exit

nerdctl ps -a | grep foo <- container should have been removed.

Thanks for comments !!!
I have checked the behaviour of apostasie's comments and I'm able to reproduce the behaviour with this modification applied.
Details

(24-10-31 14:57:30) <0> [~/workspace/nerdctl]
dev-dsk-haytok % n run --rm -ti --name foo debian
root@aedd1bb7ab0a:/# INFO[0001] read detach keys

(24-10-31 14:57:36) <0> [~/workspace/nerdctl]
dev-dsk-haytok % n ps
CONTAINER ID    IMAGE                              COMMAND    CREATED          STATUS    PORTS    NAMES
aedd1bb7ab0a    docker.io/library/debian:latest    "bash"     3 seconds ago    Up                 foo

(24-10-31 14:57:38) <0> [~/workspace/nerdctl]
dev-dsk-haytok % n attach foo

root@aedd1bb7ab0a:/# exit
exit

(24-10-31 14:57:51) <0> [~/workspace/nerdctl]
dev-dsk-haytok % n ps
CONTAINER ID    IMAGE    COMMAND    CREATED    STATUS    PORTS    NAMES

(24-10-31 14:57:52) <0> [~/workspace/nerdctl]
dev-dsk-haytok % n ps -a
CONTAINER ID    IMAGE                              COMMAND    CREATED           STATUS                      PORTS    NAMES
aedd1bb7ab0a    docker.io/library/debian:latest    "bash"     18 seconds ago    Exited (0) 2 seconds ago             foo

There is indeed a problem with the current implementation, so I have modified it so that the container is also deleted when detaching with ctrl+D to an attached container.
Thanks for quieck review :)

As a result of this modification, it appears that the following process is not being executed when detach is performed after attach in the above-mentioned operation check, resulting in a stopped state where the container is deleted.
- https://github.com/containerd/nerdctl/blob/main/cmd/nerdctl/container/container_run.go#L452C1-L464C4
Additional investigation will be done tomorrow ...

Hi, reviewers and maintainers
After applying this fix, when detach and attach a container that has activated the --rm option, the container is not deleted and stopped.
Applying the following fix solves this problem, but I'm not sure if this is a proper implementation...
I would appreciate advice if there is any other good implementation 🙏
Details

dev-dsk-haytokb % gd pkg/cmd/container/attach.go
diff --git a/pkg/cmd/container/attach.go b/pkg/cmd/container/attach.go
index fbbddafc..c35daa1d 100644
--- a/pkg/cmd/container/attach.go
+++ b/pkg/cmd/container/attach.go
@@ -37,6 +37,8 @@ import (
 func Attach(ctx context.Context, client *containerd.Client, req string, options types.ContainerAttachOptions) error {
        // Find the container.
        var container containerd.Container
+       var cStatus containerd.Status
        walker := &containerwalker.ContainerWalker{
                Client: client,
                OnFound: func(ctx context.Context, found containerwalker.Found) error {
@@ -54,6 +56,15 @@ func Attach(ctx context.Context, client *containerd.Client, req string, options
                return fmt.Errorf("more than one containers are found given the string: %s", req)
        }

+       defer func() {
+               if cStatus.Status == containerd.Stopped {
+                       if err = RemoveContainer(ctx, container, options.GOptions, true, true, client); err != nil {
+                               return
+                       }
+               }
+       }()
        // Attach to the container.
        var task containerd.Task
        detachC := make(chan struct{})
@@ -114,6 +125,7 @@ func Attach(ctx context.Context, client *containerd.Client, req string, options
        if err != nil {
                return fmt.Errorf("failed to init an async wait for the container to exit: %w", err)
        }
        select {
        // io.Wait() would return when either 1) the user detaches from the container OR 2) the container is about to exit.
        //
@@ -129,6 +141,11 @@ func Attach(ctx context.Context, client *containerd.Client, req string, options
                }
                io.Wait()
        case status := <-statusC:
+               cStatus, err = task.Status(ctx)
+               if err != nil {
+                       return err
+               }
                code, _, err := status.Result()
                if err != nil {
                        return err

I thought it would be nice to have a flag from the attach command process to determine if the container has run the --rm option, but now I have not been able to confirm this in the current implementation.

@haytok it would be easier to comment on the code, so, suggesting you modify your PR to incorporate all your changes and we can talk from there.
From a glimpse at it, I wonder if your change would also impact containers not started with --rm?

Hi @apostasie
Thanks for comments !!!
I have fixed to remove a container when detaching and attaching a container started with the --rm option.


crystalball has numpy incompatability in 0.2.0

Crash while running the crystalball cab in 0.2.0
Looks like a numpy problem.
# INFO:    Build complete: /home/tim/.singularity/quay.io-stimela2-crystalball:cc0.2.0.simg
2024-12-12 01:03:39 STIMELA.white_belt.predict-model INFO: (singularity build) exited with code 0 after
0:01:16
### running /usr/bin/singularity exec --containall --pwd /home/tim/git/molteno/physics/imaging/meerkat --bind
/home/tim/git/molteno/physics/imaging/meerkat:/home/tim/git/molteno/physics/imaging/meerkat:rw
/home/tim/.singularity/quay.io-stimela2-crystalball:cc0.2.0.simg crystalball --field 2 --output-column
MODEL_DATA --sky-model sky_models/J0408-6545_L.txt --num-sources 53 --memory-fraction 0.1
ms-orig/mt0_b_j0159.ms
# /usr/lib/python3/dist-packages/scipy/__init__.py:146: UserWarning: A NumPy version >=1.17.3 and <1.25.0 is
required for this version of SciPy (detected version 2.0.2
#   warnings.warn(f"A NumPy version >={np_minversion} and <{np_maxversion}"
#
# A module that was compiled using NumPy 1.x cannot be run in
# NumPy 2.0.2 as it may crash. To support both 1.x and 2.x
# versions of NumPy, modules must be compiled with NumPy 2.0.
# Some module may need to rebuild instead e.g. with 'pybind11>=2.12'.
#
# If you are a user of the module, the easiest solution will be to
# downgrade to 'numpy<2' or try to upgrade the affected module.
# We expect that some modules will need time to support NumPy 2.
#
# Traceback (most recent call last):  File "/usr/local/bin/crystalball", line 5, in <module>
#     from crystalball.crystalball import predict
#   File "/usr/local/lib/python3.10/dist-packages/crystalball/crystalball.py", line 8, in <module>
#     from dask.array import PerformanceWarning
#   File "/usr/local/lib/python3.10/dist-packages/dask/array/__init__.py", line 56, in <module>
#     from dask.array import backends, fft, lib, linalg, ma, overlap, random
#   File "/usr/local/lib/python3.10/dist-packages/dask/array/backends.py", line 8, in <module>
#     from dask.array.core import Array
#   File "/usr/local/lib/python3.10/dist-packages/dask/array/core.py", line 32, in <module>
#     from dask.array.chunk_types import is_valid_array_chunk, is_valid_chunk_type
#   File "/usr/local/lib/python3.10/dist-packages/dask/array/chunk_types.py", line 131, in <module>
#     import scipy.sparse
#   File "/usr/lib/python3/dist-packages/scipy/sparse/__init__.py", line 267, in <module>
#     from ._csr import *
#   File "/usr/lib/python3/dist-packages/scipy/sparse/_csr.py", line 10, in <module>
#     from ._sparsetools import (csr_tocsc, csr_tobsr, csr_count_blocks,
# AttributeError: _ARRAY_API not found
# Traceback (most recent call last):
#   File "/usr/local/bin/crystalball", line 5, in <module>
#     from crystalball.crystalball import predict
#   File "/usr/local/lib/python3.10/dist-packages/crystalball/crystalball.py", line 8, in <module>
#     from dask.array import PerformanceWarning
#   File "/usr/local/lib/python3.10/dist-packages/dask/array/__init__.py", line 56, in <module>
#     from dask.array import backends, fft, lib, linalg, ma, overlap, random
#   File "/usr/local/lib/python3.10/dist-packages/dask/array/fft.py", line 11, in <module>
#     import scipy.fftpack
#   File "/usr/lib/python3/dist-packages/scipy/fftpack/__init__.py", line 94, in <module>
#     from ._basic import *
#   File "/usr/lib/python3/dist-packages/scipy/fftpack/_basic.py", line 8, in <module>
#     from scipy.fft import _pocketfft
#   File "/usr/lib/python3/dist-packages/scipy/fft/__init__.py", line 90, in <module>
#     from ._fftlog import fht, ifht, fhtoffset
#   File "/usr/lib/python3/dist-packages/scipy/fft/_fftlog.py", line 11, in <module>
#     from ..special import loggamma, poch
#   File "/usr/lib/python3/dist-packages/scipy/special/__init__.py", line 649, in <module>
#     from . import _ufuncs
#   File "_ufuncs.pyx", line 1, in init scipy.special._ufuncs
# ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got
88 from PyObject
2024-12-12 01:03:40 STIMELA.white_belt.predict-model ERROR: step 'white_belt.predict-model' has failed,
aborting the recipe

Probably belongs upstream.

I pushed a new image, can you try again?

Will do. PS. Have begun looking at crystalball.  It may benefit from pyproject.toml, and improved dependencies

MODEL_DATA --sky-model sky_models/J0408-6545_L.txt --num-sources 53 --memory-fraction 0.1
ms-orig/mt0_b_j0159.ms
# Traceback (most recent call last):
#   File "/usr/local/bin/crystalball", line 8, in <module>
#     sys.exit(predict())
#   File "/usr/local/lib/python3.10/dist-packages/crystalball/crystalball.py", line 155, in predict
#     return _predict(args)
#   File "<decorator-gen-1>", line 2, in _predict
#   File "/usr/local/lib/python3.10/dist-packages/africanus/util/requirements.py", line 159, in _wrapper
#     raise MissingPackageException(msg)
# africanus.util.requirements.MissingPackageException: _predict requires installation of the following
packages: ['daskms'].
# cannot import name '_execute_task' from 'dask.core' (/usr/local/lib/python3.10/dist-packages/dask/core.py)
2024-12-12

Grrr, this new pip is really broken, isn't it? OK, try now...

I checked quay.io and new image is there. Deleted .simg, but error persists.
/home/tim/.singularity/quay.io-stimela2-crystalball:cc0.2.0.simg crystalball --field 2 --output-column
MODEL_DATA --sky-model sky_models/J0408-6545_L.txt --num-sources 53 --memory-fraction 0.1
ms-orig/mt0_b_j0159.ms
# Traceback (most recent call last):
#   File "/usr/local/bin/crystalball", line 8, in <module>
#     sys.exit(predict())
#   File "/usr/local/lib/python3.10/dist-packages/crystalball/crystalball.py", line 155, in predict
#     return _predict(args)
#   File "<decorator-gen-1>", line 2, in _predict
#   File "/usr/local/lib/python3.10/dist-packages/africanus/util/requirements.py", line 159, in _wrapper
#     raise MissingPackageException(msg)
# africanus.util.requirements.MissingPackageException: _predict requires installation of the following
packages: ['daskms'].
# cannot import name '_execute_task' from 'dask.core' (/usr/local/lib/python3.10/dist-packages/dask/core.py)
2024-12-12 02:47:31 STIMELA.white_belt.predict-model ERROR: step 'white_belt.predict-model' has failed,
aborting the recipe

@tmolteno I think adding
cabs:
  crystalball:
    image:
      version: cc0.1.3

might be a workaround for you in the meantime?

I think it might be because my pyproject.toml didn't depend on codex-africanus[dask]
This is now fixed in the PR on https://github.com/caracal-pipeline/crystalball/pull/64

Is the above running with crystallball 0.3.0 or master branch? I wager it's 0.3.0 which is an ancient vintage (2020)

The original error in the first post was with an install from master on python3.10. The 0.3.0 release didn't install at all (https://github.com/caracal-pipeline/crystalball/issues/65).
@tmolteno I've pushed a 0.4.1 image now (a.k.a. latest), see if that runs?

Meh, I've seen this breakage elsewhere. regions moved that function into a sub-module as of 0.6 (I think). OK I'm out of workarounds now, sorry, @sjperkins needed.

Actually I see this is already fixed on crystalball master, we just need a new release. I declare 0.4.1 officially broken. :)
@tmolteno, how's the latest master image acting?

@tmolteno I pushed a new master image with @sjperkins's latest fixes. Please try again.

More errors. This looks like the numpy 2.0 requirement. I have an end-to-end testcase using TART data that works using the pyproject.toml from my branch.
# INFO:    Creating SIF file...
# INFO:    Build complete: /home/tim/.singularity/quay.io-stimela2-crystalball:cc0.2.0.simg
2024-12-12 17:42:32 STIMELA.white_belt.predict-model INFO: (singularity build) exited with code 0 after 0:01:19
### running /usr/bin/singularity exec --containall --pwd /home/tim/git/molteno/physics/imaging/meerkat --bind
/home/tim/git/molteno/physics/imaging/meerkat:/home/tim/git/molteno/physics/imaging/meerkat:rw
/home/tim/.singularity/quay.io-stimela2-crystalball:cc0.2.0.simg crystalball --field 2 --output-column MODEL_DATA --sky-model
sky_models/J0408-6545_L.txt --num-sources 53 --memory-fraction 0.1 ms-orig/mt0_b_j0159.ms
# /usr/lib/python3/dist-packages/scipy/__init__.py:146: UserWarning: A NumPy version >=1.17.3 and <1.25.0 is required for this version of
SciPy (detected version 2.0.2
#   warnings.warn(f"A NumPy version >={np_minversion} and <{np_maxversion}"
#
# A module that was compiled using NumPy 1.x cannot be run in
# NumPy 2.0.2 as it may crash. To support both 1.x and 2.x
# versions of NumPy, modules must be compiled with NumPy 2.0.
# Some module may need to rebuild instead e.g. with 'pybind11>=2.12'.
#
# If you are a user of the module, the easiest solution will be to
# downgrade to 'numpy<2' or try to upgrade the affected module.
# We expect that some modules will need time to support NumPy 2.
#
# Traceback (most recent call last):  File "/usr/local/bin/crystalball", line 5, in <module>
#     from crystalball.crystalball import predict
#   File "/usr/local/lib/python3.10/dist-packages/crystalball/crystalball.py", line 8, in <module>
#     from dask.array import PerformanceWarning
#   File "/usr/local/lib/python3.10/dist-packages/dask/array/__init__.py", line 56, in <module>
#     from dask.array import backends, fft, lib, linalg, ma, overlap, random
#   File "/usr/local/lib/python3.10/dist-packages/dask/array/backends.py", line 8, in <module>
#     from dask.array.core import Array
#   File "/usr/local/lib/python3.10/dist-packages/dask/array/core.py", line 32, in <module>
#     from dask.array.chunk_types import is_valid_array_chunk, is_valid_chunk_type
#   File "/usr/local/lib/python3.10/dist-packages/dask/array/chunk_types.py", line 131, in <module>
#     import scipy.sparse
#   File "/usr/lib/python3/dist-packages/scipy/sparse/__init__.py", line 267, in <module>
#     from ._csr import *
#   File "/usr/lib/python3/dist-packages/scipy/sparse/_csr.py", line 10, in <module>
#     from ._sparsetools import (csr_tocsc, csr_tobsr, csr_count_blocks,
# AttributeError: _ARRAY_API not found
# Traceback (most recent call last):
#   File "/usr/local/bin/crystalball", line 5, in <module>
#     from crystalball.crystalball import predict
#   File "/usr/local/lib/python3.10/dist-packages/crystalball/crystalball.py", line 8, in <module>
#     from dask.array import PerformanceWarning
#   File "/usr/local/lib/python3.10/dist-packages/dask/array/__init__.py", line 56, in <module>
#     from dask.array import backends, fft, lib, linalg, ma, overlap, random
#   File "/usr/local/lib/python3.10/dist-packages/dask/array/fft.py", line 11, in <module>
#     import scipy.fftpack
#   File "/usr/lib/python3/dist-packages/scipy/fftpack/__init__.py", line 94, in <module>
#     from ._basic import *
#   File "/usr/lib/python3/dist-packages/scipy/fftpack/_basic.py", line 8, in <module>
#     from scipy.fft import _pocketfft
#   File "/usr/lib/python3/dist-packages/scipy/fft/__init__.py", line 90, in <module>
#     from ._fftlog import fht, ifht, fhtoffset
#   File "/usr/lib/python3/dist-packages/scipy/fft/_fftlog.py", line 11, in <module>
#     from ..special import loggamma, poch
#   File "/usr/lib/python3/dist-packages/scipy/special/__init__.py", line 649, in <module>
#     from . import _ufuncs
#   File "_ufuncs.pyx", line 1, in init scipy.special._ufuncs
# ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject
2024-12-12 17:42:33 STIMELA.white_belt.predict-model ERROR: step 'white_belt.predict-model' has failed, aborting the recipe

The end-to-end test (including measurement set) is in
https://github.com/tmolteno/crystalball/tree/master/test_data

More errors. This looks like the numpy 2.0 requirement. I have an end-to-end testcase using TART data that works using the pyproject.toml from my branch.

It's like playing whack-a-mole... tests may run in your environment, but a pip install inside a clean image results in breakage. OK, I've added pip install - U scipy to the image and pushed, try again.
@sjperkins we may need to add an explicit "scipy higher than" requirement. The current install pulls in numpy>=2 but leaves scipy at some older incompatible version.

Why are we installing scipy at all? A fresh install of 0.4.2 in a virtualenv doesn't show scipy in pip freeze.
Could it be that scipy is baked into the image somehow?

Good question -- it might be pre-installed in the base image. Let me check.
Looks like dask imports scipy if available:  https://github.com/dask/dask/blob/main/dask/array/chunk_types.py

Sounds like the package will need a venv to operate? Can we use a default cult_cargo venv for each cab? This might keep the system from polluting the python namespace?

As a rule I think all of our applications should be installed in venvs

It's a good guideline to impose to keep users out of our hair, but seems like a regression if i can't operate outside a venv at all!

It's a good guideline to impose to keep users out of our hair, but seems like a regression if i can't operate outside a venv at all!

Perhaps, but isolation as provided by containers, snaps, flatpaks and python virtual environments is designed to circumvent these dependency issues.

Which is exactly why I'm trying to come up with a clean Dockerfile. Venv inside container seems like adding another layer of complexity to the process which can bite us down the road.

I suspect what happened in this case is that a system scipy was installed, built against an older version of numpy. When numpy > 2, was installed any call to scipy was going to break because the system numpy had been replaced. A virtualenv would prevent this.

Finally! @tmolteno I believe I have pushed working images. At least your test runs. Lessons learned:

Dask is sneaky! It will attempt to import scipy and cause kak if it gets hold of a system scipy that clashes with a newly-installed numpy. Since scipy is not in any dependencies in this case, there's nothing pip can do to avoid this. (Solved by stripping scipy out of the base image.)

Something similar going on with matplotlib, solved by an explicit "pip install -U matplotlib". I'm still investigating why matplotlib is installed to begin with, since it's not a dependency and not in the base image.

I'm still investigating why matplotlib is installed to begin with, since it's not a dependency and not in the base image.

Possibly the kernsuite base:
https://github.com/caracal-pipeline/cult-cargo/blob/0aa0fe574dc57514d32c2acf5e423f325170461a/cultcargo/images/base-cult/Dockerfile#L1-L5

Yep probably. Basing off kern seemed like a good idea at the time...

Yep probably. Basing off kern seemed like a good idea at the time...

I suspect most of the dask based apps could run off ubuntu-24.04. Could multiple base images be supported?

Could multiple base images be supported?

Absolutely. The builder script will look for a per-package Dockerfile under cultcargo/images/package. Most of these just happen to symlink to https://github.com/caracal-pipeline/cult-cargo/blob/master/cultcargo/images/Dockerfile.generic.pip, which is meant to be a generic Dockerfile for pip installable packages. If something less than generic is required, we put a specific Dockerfile in rather.

OK, I pushed new images for crystalball and tricolour based off the standard "slim" containers. At least invoking the command seems to work -- @tmolteno would you please test further?
Slim is not so slim anymore once pip and git is installed, but it did reduce the crystalball image by almost 50%. Only 10% simming for tricolour though.


[lc_ctrl] Transition to SCRAP not possible once the transition counter is maxed out

Description
Looking at the RTL, it seems that all transitions are rejected once the transition counter is maxed out.
Would it make sense to still allow transition to SCRAP in this case?

Lets close this, as we won't have that in integrated_dev for now and the other one has been closed.


Update docs marked for review by RE

Review on a number of AWS alerts
Updated the "Contacting RE" section to include PagerDuty path
Deprecated AWS (Mongo, RabbitMQ)-cluster network issue workaround

I accidentally entangled this by a applying a broken rebase : / close and trying again


SLING-2707 Support of chunked file upload into Sling

Feature enhance with details at https://cwiki.apache.org/confluence/display/SLING/Chunked+File+Upload+Support

Extension to [SlingPostServlet|http://sling.apache.org/site/manipulating-content-the-slingpostservlet-servletspost.html]
Chunk upload is supported in "modify"operation of [SlingPostServlet|http://sling.apache.org/site/manipulating-content-the-slingpostservlet-servletspost.html](ie. In default operation) . No new operation introduced for it
Chunks are saved in temporary location identified by upload id
Chunk processing

First/Intermediate chunks: Chunk is saved in temporary location in jcr. Ignores all upload semantics (@TypeHint, etc) and request parameters.
Last chunk: Stitches all chunks. Process all upload semantics and request parameters and creates jcr node structure at the right location.

@shashank-itbhu  - the Jira issue has been resolved, can you please close the pull request?

With the upcoming migration to git this repository will be deleted. If the pull request contains data that should be re-submitted I suggest that you save the changes locally and resubmit them after the migration, which will likely happen on Monday the 9th of October.


Handle soundchecks on import

If files like "S 01 (Check) My Soul.mp3" are found, they should be automatically added to the import even though the phish.net API response will not include them. The title should be everything after "(Check) " and the song should be "Soundcheck".

Now that the library is up to date with circulated sources, it's extremely rare to get the soundcheck at the same time as the show content, so this feature would rarely be used.


Test Fail when using NPM pack

First off, thanks for creating this shareable config.
I'm behind a firewall and need the ability pack packages so that other developers can download the package without going outside the network.  Executed npm pack in the command line and received a test failure.  Details are below:
npm pack

<EMAIL_ADDRESS>prepublish /Users/cjohn/Documents/Projects/Servicing/src/main/webapp/spa/node_modules/eslint-config-angular
npm test

<EMAIL_ADDRESS>test /Users/cjohn/Documents/Projects/Servicing/src/main/webapp/spa/node_modules/eslint-config-angular
gulp test

sh: gulp: command not found
npm ERR! Test failed.  See above for more details.
npm ERR! addLocalDirectory Could not pack /Users/cjohn/Documents/Projects/Servicing/src/main/webapp/spa/node_modules/eslint-config-angular to /Users/cjohn/.npm/eslint-config-angular/0.5.0/package.tgz
npm ERR! addLocal Could not install /Users/cjohn/Documents/Projects/Servicing/src/main/webapp/spa/node_modules/eslint-config-angular
npm ERR! Darwin 14.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "pack"
npm ERR! node v4.4.5
npm ERR! npm  v2.15.5
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>prepublish: npm test
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepublish script 'npm test'.
npm ERR! This is most likely a problem with the eslint-config-angular package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm test
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs eslint-config-angular
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls eslint-config-angular
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:

Hi. Have you ran npm install before running npm pack?


Load data into manifests from disk

This opens the door to modding support, easier tools for game designers, and is frankly better code organization.

[ ]  We need to load all manifests and have their resources created before we start the gameplay logic. This is probably not trivial as it is not clear if this should logic should reside in the app or lib and how exactly we want to implement it.
[ ] We need to move the other manifests to the new system (e.g. recipes and units).
[ ] We should apply more data validation, e.g. checking for hash collisions, checking that IDs to external manifests (e.g. item IDs in recipes) are valid, etc.
[ ] We probably need another resource that can map back from ID to the string identifiers if needed. This would be useful to make our UI more readable again before we have proper localization tools.
[ ] Remove the hard-coded definitions.

From #521.


Typings install fails

Performing an 'npm install' on a fresh copy of the project I get the following error:
typings ERR! message Unable to read typings for "jasmine". You should check the path is correct
typings ERR! caused by https://raw.githubusercontent.com/angular/DefinitelyTyped/4b36b94d5910aa8a4d20bdcd5bd1f9ae6ad18d3c/jasmine/jasmine.d.ts responded with 404, expected it to equal 200

Hi Zachallen,
I've been unwatching this project for a while.
I'll put some updates very soon as I'm working on a talk around this matter.
Keep you posted if still interested!
Grtz

Hi @zachallen project updated

Hi @zachallen project updated, can you please check if it's ok on your side now?

Hi @samvloeberghs, everything works correctly.


.search.dropdown cannot move cursor

After I've selected an item from dropdown list, i cannot delete that item pressing 'delete' key and cannot navigate the text of the item using right\left keys.

I'm not sure what happened there, but it appears there's some regression with 1.x keyboard shortcuts

Fixed in patch today.

Jack, the fix don't work.
Checked it on my meteor project and on SUI.com

Seems to be fine at semantic-ui.com at http://semantic-ui.com/modules/dropdown.html#search-selection
Clear cache?

Cleared. Still serving 1.12.1 on sui.com. You sure everything's fine with sui.com link to master repo?

But anyway, I have 1.12.2 in my meteor app and the fix doesnt seem to work. I'll make a fiddle once the versioning confusion is sorted.

well, maybe this needs reopening.
still aint working.http://jsfiddle.net/pybxztu2/1/

Delete key and arrow keys seem to be fine in your fiddle?

Is it a question or a statement?
In the fiddle the keys delete, left, right aint working after I've selected an item from dropdown list.

The bug I fixed was left/right arrows not working during selection.
This is expected behavior. After making a selection it adjusts the underlayed text content. This could contain other non string values like images or labels and is unselectable. It is not part of the current input.
http://beta.semantic-ui.com/modules/dropdown.html#search-selection


Rec Complex transformers adding ore to stone clumps on surface

Including  vanilla iron.

I experimented with transformers yesterday and learned that they're pretty easy. They're also pretty neat. I added a stone clump on the surface that had some iron and copper ore. I may work on this more tonight.

This is no longer an issue, as we have annother gate on iron now.


Adding BsonArray constructor that allocates an ArrayList with known capacity

This probably does not need much additional explanations. I could not find a way in the current BsonArray implementation to specify the capacity.
From https://dzone.com/articles/performance-evaluation-of-java-arraylist

It is clear from the from the results (considering the add operation of ArrayList) that if the required maximum capacity of the ArrayList is known, we can get the optimal performance (both average latency and throughput) by specifying the initial capacity to the required capacity.

In doing so, we can get 24% to 34% improvement in average latency and 30% to 50% improvement in throughput.

JAVA-3613

Sorry for leaving this un-merged for so long.  We lost track of it after the initial review.  I applied the requested changed myself and merged: https://github.com/mongodb/mongo-java-driver/commit/55ca500447d2d0126f36e2fa16ba0061113785b6 and https://github.com/mongodb/mongo-java-driver/commit/82e40ed6929c2b0e7dcd65f3615e10b183275b1e


Revise license line

At least the released binary and the logo is not MIT

@chrisdias can advise on VSCode license

Relevant: https://github.com/Microsoft/vscode/issues/60#issuecomment-161792005

Since nobody's commented in opposition to this, and since I think this PR is more accurate than the description in master, I'm going to merge this.
If @chrisdias, @pasero or anyone else feels this is in error, please @ me in a followup and we'll go from there. Thank you!


[smart-file-system] Tag error on Packagist

Hi @TomasVotruba
I got the same error of #1810 but for package smart-file-system.
I think, it's because of the tag created for the issue #1813
Can you create an other tag for it ?
Thank you so much :heart_eyes:

Hi, I tried and it works:

It's probably related to OS/Composer. Try:

clearning composer cache
removing vendor and composer.lock
try composer update

It's work for me, thanks :smile:


Done some changes

Added some new css changes

This branch has conflicts that must be resolved
Use the web editor or the  to resolve conflicts.
Conflicting files
assets/style.css
pls PR to the specific branch


Bug in "Sum of N terms of GP calculator" when r=1

Describe the bug
In sum of n terms of GP calculator When common ratio ==1 the sum comes out to 0
Possible solution
Modify the javascript code for when r==1 || The formula of GP sum when r==1 is ( no. of terms *  common ratio)
Screenshots

Please assign me this issue i will start working on it as soon as i m assigned to it !!

Go ahead
Deadline 28 March,2021 (11:59 PM IST)


Crystal installation failing on travis.

Suddenly builds started to fail because of failing crystal installation on Travis.
Relevant Logs
Installing Crystal
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /tmp/tmp.4f8XoP5XRu --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d//apt.postgresql.org.gpg --keyserver keys.gnupg.net --recv-keys 09617FD37CC06B54
gpg: requesting key 7CC06B54 from hkp server keys.gnupg.net
?: keys.gnupg.net: Host not found
gpgkeys: HTTP fetch error 7: couldn't connect: Success
gpg: no valid OpenPGP data found.

WARNING: The following packages cannot be authenticated!
  crystal
E: There are problems and -y was used without --force-yes
Installing Shards

$ crystal --version
/home/travis/build.sh: line 45: crystal: command not found
$ crystal deps --version
/home/travis/build.sh: line 45: crystal: command not found

$ crystal deps
/home/travis/build.sh: line 45: crystal: command not found

More here.

I can confirm the same

Closing as a duplicate of https://github.com/travis-ci/travis-ci/issues/5461


Remove ppc64le support

Travis is failing to download source tarballs from github, failing our feedstock build.
This is a known issue (https://github.com/conda-forge/conda-forge.github.io/issues/1521) with no current solution.
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

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

How would I switch over the builds?

It's just:
provider:
  linux_ppc64le: azure

I'd try this if there is no other URL available.


#147 monthly task

used tag 1-1.22-bullseye which pointing to the latest release for go

Hi @samruddhikhandale ,
Can you help review this PR and approve the same?

@bamurtaugh would you be able to help approve as part of Community PR Approvals? Thanks!


Laptop enters suspend even when in use

Describe the bug
Laptop enters suspend even when in use, about every 5 minutes. Whether media is playing or I'm using the keyboard/mouse does not appear to matter, it will still suspend.
Steps To Reproduce
I do not know how to reproduce it. Heres my logind config:
services = {
  logind.extraConfig = ''
    HandlePowerKey=suspend-then-hibernate
    HandlePowerKeyLongPress=poweroff
    HandleLidSwitch=suspend-then-hibernate
    HandleLidSwitchExternalPower=suspend-then-hibernate
    HandleLidSwitchDocked=suspend-then-hibernate
    HoldoffTimeoutSec=5s
    IdleAction=suspend
    IdleActionSec=300s
  '';
};
systemd = {
  sleep.extraConfig = "HibernateDelaySec=1h";
};

I also have thermald and powerManagement enabled.
Expected behavior
Laptop does not suspend when used, and will only suspend after being idle for x time.
Screenshots
N/A
Additional context
Framework 13 AMD 7040 series.
The suspensions appear to happen every 5 minutes which would align with the IdleActionSec of 300s (5 minutes) but I'm using the system, like watching videos or whatever and it will still proceed to suspend.
In trying to test battery saving methods, I did run powertop (calibrate and autotune) and I noticed this issue after the fact but I believe powertop settings don't stay across boots so I don't think that caused it? DPMS does not seem to have any effect.
Already tried asking around in 2 Discord servers and on Reddit, along with many searches but haven't had any luck.
Notify maintainers
Not sure who to notify.

Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.9.2-zen1, NixOS, 24.05 (Uakari), 24.05.20240605.0b8e7a1`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - channels(root): `"nixos-23.05"`
 - nixpkgs: `/nix/store/axfhzzkixwwdmxlrma7k8f65214acvml-source`

Add a :+1: reaction to issues you find important.

The same started happening here as well a few days ago on unstable - displays turn off after 60 secs, even when watching a movie.
The only thing to prevent this is to wiggle the mouse or press keys on the keyboard.
There were no changes the any power management/screensaver settings here, neither in my NixOS configuration, nor interactively in my Plasma 6.0.5 session.
Still trying to figure out where this is coming from.

Ive done a little more digging into journalctl and it appears that systemd.logind is the one starting the suspensions with
systemd-logind[1041]: System idle. Will suspend now.

This appears to be an issue of my WM not managing idle state or something similar. Since this appears to be unrelated to NixOS, other than the logind configuration option, I will close this.

Sorry for necrobumping, I had a similar issue to that of eliasp when using Firefox. In my case, the solution was to downgrade Firefox, it seems that newer versions (I don't know from which exactly, but it definitely doesn't happen with versions <=121.0) or a newer version of a dependency (of those newer firefox versions) causes the browser to not signal to the OS/DE when a video is playing.

There are other reports of this on gnome-settings-daemon: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/771 (Repeated suspend loop on resume). I've been experiencing this problem for a while on my nvidia machine, and I do have nvidia power management enabled.
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/611 (Suspend in multiseat not working correctly: One seat causes the entire installation to go into suspend mode).


Bump version

Fixes example for PEP-8 conventions.

Coverage remained the same at 52.381% when pulling 1990af8c8447b62f566a0fafa8ba5e8693dbac22 on develop into 9952d18113e7b95b123af198095320037040ffea on master.


Finlaymath

What you have tested it on?
When was it tested?
What did you do?
Why did you do it?
Does it compile????????
Are you sure it works??????

Finlaymath has been the working branch for all of build season and has been verified to work so i am merging it in to master so it is less confusing to find the code if we need it next year


Update StockVisualEnhancements.netkan

Fixes current SpaceDock download. I'm hoping to persuade @Nhawks1717 to switch to a more CKAN-friendly distribution method soon as right now the EVE files are bundled.

Basically a duplicate of #3779 . #3779 also removes the Kopernicus recommendation. As SVE has zero interaction with Kopernicus, removing this recommendation makes sense.

Kopernicus


fix mock behavior

Fix for https://github.com/uber-go/cadence-client/issues/259
We only try to call mock if we know a mock was setup for it.
This means if the mock call fails (panic), it is the expected behavior to fail.
So we don't need to catch the panic. This also remove the needs to print those panic message since it is already print out by testify.

Coverage increased (+0.008%) to 69.332% when pulling ecaf326c633f8ed6bea02ed2030430e8a27d102b on yiminc:fix_mock into 907a7e677b9c065b8b69b1ae02b2366cb4c426ed on uber-go:master.

Coverage increased (+0.07%) to 69.332% when pulling 6152ddc28197e10c74c18eec80cec34e95e6c311 on yiminc:fix_mock into 407655ec5ae4a1ed65fefb93c70651aafd6ee2fc on uber-go:master.


Add routes to view available minigames

REST-style routes to retrieve minigame value

Closing – team decided that we do not need to expose these endpoints


These two pages appear to have the titles mixed up

Swap titles so they match the page content and filenames

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

#label:"aq-pr-triaged"

#sign-off

@steved0x: I'm sorry - only the author of this article, @shashban, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


fix: unintended version of espree loaded

close #238
This PR fixes an issue where an older version of espree could be loaded unintentionally by the user.

Hmm. It seems that the compatibility issue with older versions of ESLint is difficult.


Can I use component inside Swiper?

I am trying to use Swiper to wrap a list of components with the coverflow effect but it doesn't work. It seems that the children of Swiper can only be <div>. Thanks for any help.
const params = {
effect: 'coverflow',
grabCursor: true,
centeredSlides: true,
slidesPerView: 'auto',
coverflowEffect: {
rotate: 50,
stretch: 0,
depth: 100,
modifier: 1,
slideShadows: true
},
pagination: {
el: '.swiper-pagination'
},
shouldSwiperUpdate: true,
rebuildOnUpdate: true
}
<Swiper {...params}><Item /><Item /><Item /></Swiper>

Hi @billyyyyy , you can wrap component inside Swiper.
In your case, you're using composite component  (a component comprised of other components),  so you need to provide props className within Item component for Swiper to add swiper-slide class name to each slide.
For more detail you can check a demo I made here.


NTR: beta-pinacene synthase activity

Please let me know of any questions.
Thanks,
Bob Dodson
Name: beta-pinacene synthase activity
Ontology: function
Synonyms:
Definition: Catalysis of the cyclization of geranylgeranyl pyrophosphate (GGPP) to yield the monocyclic diterpene beta-pinacene.
CHEBI:139494
Child of: GO:0010333 terpene synthase activity
References:
PMID:28696553 Mechanisms of the Diterpene Cyclases Beta-Pinacene Synthase from Dictyostelium discoideum and Hydropyrene Synthase from Streptomyces clavuligerus.

Is this
EC <IP_ADDRESS>
(+)-beta-pinene synthase (EC <IP_ADDRESS>, (+)-pinene cyclase, cyclase III) is an enzyme with systematic name geranyl-diphosphate diphosphate-lyase ((+)-beta-pinene-forming).[1][2] This enzyme catalyses the following chemical reaction
geranyl diphosphate ⇌(+)-beta-pinene + diphosphate

@hdrabkin
This does not appear to be EC <IP_ADDRESS> (+)-beta-pinene synthase, although it is certainly confusingly close in name.
The enzyme in question here has only been recently described, and I used the name given by the authors: "beta-pinacene synthase". They do not provide an EC number. I also previously requested the addition of the the new compound "beta-pinacene" at CHEBI, and they approved and assigned it as CHEBI:139494.
Please let me know if you have further questions.
Thanks,
Bob

@rjdodson , so you have  a suggested is_a parent

@hdrabkin:  apologies, I forgot to add a suggested parent.
Going back and checking my notes, I see that I had meant to add as a suggested parent:
GO:0010333 terpene synthase activity
In the paper, the authors describe this as a cyclase reaction, and in this case it is described as a cyclization reaction of the linear terpene geranylgeranyl pyrophosphate (GGPP) to beta-pinene (a monocyclic diterpene). So I would suggest GO:0010333 terpene synthase activity as parent, which is a child of GO:0016838.
Sorry I forgot to add this previously. Thanks and let me know if you have further questions.
Bob

Thanks Bob; I saw it finally in the orginal text. Coffee not kickeing in yet

GO:0106101
done


Build Darwin ARM64 release

When I run the command
fyne-cross darwin -arch amd64,arm64 -app-id $(APPID) -icon $(ICON) -output $(NAME)
I end with two build for AMD64 even it creates two separated dist folders. Also if I only use the ARM64 it still build AMD64. I'm probably missing something but I don't get any error or warning during the build.

Thanks for reporting. Could you please provide some info about your env like OS, fyne-cross version and the command output with the -debug flag enabled?

OS - MacOS 11.4
Go - 1.16.5
Fyne - 2.03
Fyne-Cross - 1.1.0
Command
[i] Target: darwin/arm64 command.Context{Volume:volume.Volume{binDirHost:"/Users/facorreia/Projects/catch-my-file/fyne-cross/bin", cacheDirHost:"/Users/facorreia/Library/Caches/fyne-cross", distDirHost:"/Users/facorreia/Projects/catch-my-file/fyne-cross/dist", tmpDirHost:"/Users/facorreia/Projects/catch-my-file/fyne-cross/tmp", workDirHost:"/Users/facorreia/Projects/catch-my-file"}, Architecture:"arm64", Env:[]string{"CGO_LDFLAGS=-fuse-ld=lld", "GOOS=darwin", "GOARCH=arm64", "CC=oa64-clang", "CGO_CFLAGS=-mmacosx-version-min=11.1", "CGO_LDFLAGS=-mmacosx-version-min=11.1"}, ID:"darwin-arm64", LdFlags:[]string(nil), OS:"darwin", Tags:[]string(nil), AppBuild:"1", AppID:"com.github.fabiodcorreia.catch-my-file", AppVersion:"1.0", CacheEnabled:true, DockerImage:"fyneio/fyne-cross:1.1-darwin", Icon:"assets/icon/icon-512.png", Name:"CatchMyFile", Package:".", Release:false, StripDebug:true, Debug:true, Pull:false, Category:"", Certificate:"", Developer:"", Keystore:"", KeystorePass:"", KeyPass:"", Password:"", Profile:""}


Get Codenvy Project Setup for angularjs-portal

Adds in codenvy files
Adds in codenvy intructions to README.md

#tothecloud!

if it works, :+1:


Question on connecting to pins

Thank you for maintaining this Plug-in and the new updates.
I am sorry for this beginner’s question.
The connection: GND <---> SENSOR <---> PIN does not work for me.
It only works if I connect:
3.3V <---> SENSOR <---> PIN
or
GND <—> SENSOR <---> PIN <---> Resistor <---> 3.3V
Which way is correct?

And Is
GND <—> SENSOR <---> PIN <--->  3.3V
with no resistor improper on the Pi?
Thanks so much

Hi,
GND <---> SENSOR <---> PIN is the only working configuration since in the latest plugin vesion exept if you disable pullUp with config parameter "pullUp":false. As I think it's not your case, just check 2 things :

You have the latest plugin version : sudo npm update -g homebridge-gpio-device
Your sensor is a normally open contact

Never try GND <—> SENSOR <---> PIN <---> 3.3V as it will short circuit when sensor contact is closed => GND <—> PIN <---> 3.3V.
Best way is even GND <---> SENSOR <---> 1k resistor <---> PIN to protect circuit as presented by @migabc here : here(https://github.com/dubocr/homebridge-gpio-device/issues/44#issuecomment-471603336). (Just remove the 10k resistor).

I updated and it is working great. Thank you so much. Awesome Plug-in.

Great, that's perfect.
You're welcome. Thank you for your feedback.


remove unused files from operator.

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

@morvencao: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
9d786c7d94b9db64edaf0ec434efef6d6e40fa17
link
/test release-notes_istio

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

/test release-notes_istio

@shamsher31 Yes, they are.


Add com.snowplowanalytics.snowplow/web_page/jsonschema/1-0-1 (closes #1222)

Closes #1222

Both id and tabId are generated using the uuid pacakge which produces valid UUIDs.
tabId is the identifier of the current tab the event was sent from. More info on the JS repository.

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

@paulboocock As Emiel is off this week I had a look at this. The page_view context is taken during the creation of the events-this-run table which is then referred back to when building the page-view model. See related BigQuery sql for web
The coalesce would need to happen here:
SELECT
        a.contexts_com_snowplowanalytics_snowplow_web_page_1_0_0[SAFE_OFFSET(0)].id AS page_view_id,
        a.* EXCEPT(contexts_com_snowplowanalytics_snowplow_web_page_1_0_0)

    FROM
      {{.input_schema}}.events a

To create the automatic coalescing there is already a procedure called combine_context_versions in the sql runner model that is used when referencing other context fields so the groundwork is there I think. I would also point out that the dbt web is also impacted as currently the 1_0_0 page_view_context schema is hard_coded but, as you mentioned we could leverage the combine_column_versions macro there. The EXCEPT bit needs further handling in case we want to limit superfluous columns and the integration tests would also need rework so that needs to be taken into consideration.
Not THAT quick to solve but is doable as much as I can see it from this.

Just to elaborate on Agnes' answer, the combine_context_versions procedure for SQL runner creates a new table to include the context fields in a coalesced manner, so we will need to revamp the events_this_run logic as Agnes outlined. I think we'd need to also have an intermediary events_this_run table which doesn't yet include the page_view_id. We'd need to call it something else, however, so we'd have to first create a events_this_run_temp table, which we could define as follows:
CREATE OR REPLACE TABLE {{.scratch_schema}}.events_this_run_temp{{.entropy}}
AS(
  -- Without downstream joins, it's safe to dedupe by picking the first event_id found.
  SELECT
    ARRAY_AGG(e ORDER BY e.collector_tstamp LIMIT 1)[OFFSET(0)].*
  FROM (
    SELECT
        a.* EXCEPT(contexts_com_snowplowanalytics_snowplow_web_page_1_0_0, contexts_com_snowplowanalytics_snowplow_web_page_1_0_1)

    FROM
      {{.input_schema}}.events a
    INNER JOIN
      {{.scratch_schema}}.base_sessions_to_include{{.entropy}} b
    ON a.domain_sessionid = b.session_id
    WHERE
      a.collector_tstamp >= LOWER_LIMIT
      AND a.collector_tstamp <= UPPER_LIMIT

      {{if eq (or .derived_tstamp_partitioned false) true}}

        AND a.derived_tstamp >= LOWER_LIMIT
        AND a.derived_tstamp <= UPPER_LIMIT

      {{end}}

  ) e
  GROUP BY
    e.event_id
);

Then we'd also need to introduce a different combine_context_versions procedure specifically for the web page context, to not take the page_view_id from the events_this_run table. It would look something like this:
CREATE OR REPLACE PROCEDURE {{.output_schema}}.combine_context_versions_web_page (columns_prefix STRING)
BEGIN
  DECLARE COLUMN_COALESCE STRING;

  SET COLUMN_COALESCE = (
    -- Flatten results of nested query into comma separated list of coalesces
    SELECT ARRAY_TO_STRING(
      ARRAY_AGG(CONCAT('COALESCE(', ARRAY_TO_STRING(paths, ', '), ', NULL) AS ',  field_name)), ', ')
    FROM(
      -- Get field names and their corresponding paths
      SELECT
        SPLIT(field_path, '.')[SAFE_OFFSET(1)] AS field_name,
        ARRAY_AGG(CONCAT(column_name, '[SAFE_OFFSET(0)].', SPLIT(field_path, '.')[SAFE_OFFSET(1)]) ORDER BY column_name DESC) AS paths

      FROM {{.scratch_schema}}.INFORMATION_SCHEMA.COLUMN_FIELD_PATHS
      WHERE table_name = 'events_this_run_temp{{.entropy}}'
      AND column_name LIKE CONCAT(columns_prefix, '%')
      AND ARRAY_LENGTH(SPLIT(field_path, '.')) = 2 -- Only first-order fields
      AND data_type NOT LIKE 'STRUCT%' -- No structs
      AND data_type NOT LIKE 'ARRAY%' -- No arrays
      GROUP BY 1
    )
  );

  IF COLUMN_COALESCE IS NULL THEN
    RAISE USING MESSAGE = 'ERROR: Cannot combine context versions: No eligible top-level columns found.';

  END IF;

  -- Create scratch table with extracted data:
  EXECUTE IMMEDIATE CONCAT("""CREATE OR REPLACE TABLE {{.scratch_schema}}.""",
                            columns_prefix,
                            """{{.entropy}} AS( SELECT event_id, """,
                            COLUMN_COALESCE,
                            """ FROM {{.scratch_schema}}.events_this_run_temp{{.entropy}})""");
END;

.We would also need to introduce a new step before the events_this_run step but after the events_this_run_temp step to call the procedure to create the page view context table, but that should be a quick one, probably something like this:
CALL {{.output_schema}}.combine_context_versions_web_page('contexts_com_snowplowanalytics_snowplow_web_page_1');

We'd need to change the events_this_run step to something like this:
CREATE OR REPLACE TABLE {{.scratch_schema}}.events_this_run{{.entropy}}
AS(
    SELECT
        wpc.id as page_view_id,
        a.*

    FROM
      {{.scratch_schema}}.events_this_run_temp a
   INNER JOIN {{.scratch_schema}}.contexts_com_snowplowanalytics_snowplow_web_page_1{{.entropy}} wpc
    ON a.event_id = wpc.event_id
);

I think if we did that then we should be fine, although I might have missed something. Up to you whether you consider that a lot of work or not, but I think we're adding two steps and a new stored procedure to ensure things continue to run smoothly on SQL runner if we introduce this change.

So your response makes me realise this is not the right time to introduce 1-0-1 until we've done the above to the models first. However, it's also clear this will have a significant impact on older data models which we won't be updating but know are out in the wild.
I think theres two choices:

Update dbt models to be ready for a 1-0-1 and block this feature being released until then - also knowing this will have consequence for people on older models when they update their tracker. Meaning it should perhaps be a tracker v4 feature.
Create a new schema/entity and store the tab id there. This is safe, the only downside I see is that it makes the payload bigger. Sort of a shame for one extra uuid.

So to move this forward, lets go with option 2.
I think we dependencies on 1-0-0 of the webPage schema are too great at the moment to justify this optional schema.

Wondering if this could be a good time to introduce a browser_context schema similar to the mobile_context that we track on the mobile trackers? We were talking about deprecating some of the atomic event fields and maybe a browser context could also cover the resolution, viewport, browser language, cookies flag, document charset, or even the page offsets set by page ping (that probably fits the web_page context better)?
It's just an idea, might not be worth it, just thinking if we should go more general to avoid having to introduce other tiny entities in the future.

Sounds like a good idea to me! Could maybe make it a toggle in v4, either track the atomic fields, or the browser_context?

Included in #1250


Remove fix for Firefox bug#592221

A workaround for Firefox bug#592221 has been inplemented in main.js. Remove the code as soon as Firefox has fixed the bug. However the developers do not seem to perceive the bug as a bug.
Status report can be found here:
https://bugzilla.mozilla.org/show_bug.cgi?id=592221

Close issues with workaround


ConnectionError: exception while running queryset on elasticsearch

Hi, I followed the same steps mentioned in given readme.md file
Here is my model:
from django.db import models
from django_elasticsearch.models import EsIndexable

class Product(EsIndexable, models.Model):
    product_name = models.CharField(max_length=100)
    slug = models.SlugField(max_length=100)

After this as per mentioned in steps I did this in python shell
>>> q = Product.es.search('sample')
>>> q

and I got this error in shell
ConnectionError: ConnectionError(<urllib3.connection.HTTPConnection
object at 0x10828e250>: Failed to establish a new connection: [Errno
61] Connection refused) caused by:
NewConnectionError(<urllib3.connection.HTTPConnection object at
0x10828e250>: Failed to establish a new connection: [Errno 61]
Connection refused)

What is that I'm missing and how do I proceed now, so that I should get resultant array

It looks like either Elasticsearch is not running or not reachable, see https://www.elastic.co/guide/en/elasticsearch/reference/2.0/setup.html.


Format-specific timer options

Ideally before VGC 2015 rules are announced we should be able to replicate to an extent the in-game timer. Although lag definitely sucks I'm sure we can provide some slight leeway for that server-side somehow. We could also have some form of confirmation sent from the server that it received the moves.
On a tangent from that, we will look into interest in removing the option to cancel a move in VGC, If it's a popular opinion/desire then look into working on that as well and implementing if it's not that invasive.

We should be refactoring timer code from rooms.js to simulator.js... this is on my to-do list.

blah blah discussion about moving simulator bits of PS into a node stream blah blah
I guess it would be better to wait for that refactor than to go about this, maybe

Well, "simulator bits" here refers to battle-engine.js. simulator.js is reasonably isolated from that.

^how did that just happen

^how did that just happen

can someone help me out here. I do see the room.js file, but I couldn't find the simulator.js file. And I think simply copy & paste is not a solution here.

@asingh04 simulator.js was renamed to room-battle.js

I guess this is done now? @Zarel

In VGC, we must call BattleSide#chooseDefault() (or whatever it's called now) when the turn timer expires instead of forfeiting.
Though maybe we should still autoforfeit if a player is AFK for 3+ decisions?

chooseDefault just chooses the first move; I was under the impression that VGC chooses a random move?

It chooses the first move, and likewise for switches. The only disagreement is in Team Preview, where the current algorithm involves team order swap for GUI convenience, whereas in VGC it's lineal.

?

I don't understand how the team preview distance affects chooseDefault?

Not sure what you mean by "distance", but the issue I mentioned only happens when the user has sent only a part of his team order decision by the time their turn ends. Supporting that circumnstance is not critical at this point, so chooseDefault() should work just fine.

Oh, I understand now.

Fixed in 73f7c998823 and 9bc83e897b, among other follow-up commits.


Installing NixOS in a container with a non-NixOS host is painful

Recently I installed NixOS into a systemd-nspawn container on a Debian host. I found this was quite painful.
I was using Debian stretch (testing), but backported systemd and systemd-container 226 from sid (unstable) due to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792882 - anyone wanting to install NixOS under systemd-nspawn should make sure systemd-nspawn is working first with some simpler system (e.g. by debootstraping jessie (stable))
Links to not-very-useful documentation:

https://nixos.org/wiki/Install_NixOS_on_Linode - way too many steps
https://nixos.org/wiki/How_to_install_NixOS_from_linux - gave the download and unsquash instructions, but then gives unnecessary commands to edit init to start bash instead of systemd and chroot manually.
https://nixos.org/wiki/Install_NixOS_as_OpenVZ_guest - links to obsolete tarballs and refers to commands that no longer exist.
https://nixos.org/wiki/NixOS:Containers - has a useful configure.nix to disable grub, but all the commands require a working nix host

Steps to reproduce:

Create /etc/static/os-release on the host because Nix ships absolute symlinks, which is a bug. Per os-release(5), if /etc/os-release is a symlink, it must be relative. While NixOS doesn't use /usr/lib/os-release, the same principle applies (and there are multiple symlinks to follow - all need to be relative). This bug is obscured when the host is also NixOS because it also contains a (wrong!) /etc/static/os-release.
Download http://nixos.org/releases/nixos/latest-iso-minimal-x86_64-linux
Extract the squashfs from the ISO.
Then extract the contents from the squashfs. It would be awesome if a runnable NixOS system could be available from a tarball (which does not require tools that probably weren't installed) instead of requiring these steps; the only tarballs I found were 4 years old on the OpenVZ page.
Use systemd-nspawn to start the contents of the squashfs, and bind-mount the path you want to install the real NixOS system to /mnt. Entering it in any other way will clobber the hosts's UTS and mount namespaces - nixos-install doesn't form its own until far too late.
When systemd bails out, press enter to use the rescue shell, that is enough.
Copy /etc/resolv.conf from outside the container to inside it.
Create /mnt/etc/nixos/configuration.nix with boot.isContainer = true;
Run nixos-install. Note that if /mnt/ is not a mount point, nixos-install will bail out for no good reason, there should probably be a --force if people want to mv it later.
Leave the squashfs container, you're done with it.
Create sbin/init in the real container as a relative symlink to ../nix/var/nix/profiles/system/init. If you were fancy, you could do some sort of menu that lets you choose a profile.
Create /etc/profile.local containing if [ "$TERM" = vt102 ]; then TERM=xterm; fi to fix systemd's braindead agetty settings.
Start your new NixOS container with systemctl -bD $container_path (or machinectl start $machine_name or systemctl start systemd-nspawn@$machine_name if it's in /var/lib/machines) and enjoy!

Looks useful for the first step: https://hydra.nixos.org/job/nixos/release-14.12/nixos.system_tarball_pc.x86_64-linux

The instructions at https://nixos.org/wiki/How_to_install_NixOS_from_linux don't work. The chroot command fails to execute (No such file or directory), not sure why.

As of this writing, this has gotten pretty simple (although it's still a few steps away from plug-and-play). Many thanks to those who came before me; here's what I learned from them and a little trial-and-error:
Pick your build from this list. Choose the last successful job, copy the URL of its build product, and use it below.
url=https://hydra.nixos.org/build/62686007/download/1/nixos-system-x86_64-linux.tar.xz
name=my-nixos
path=/var/lib/machines/$name
sudo machinectl pull-tar --verify=no $url $name
sudo mkdir $path/etc
sudo touch $path/etc/os-release
sudo mkdir $path/sbin
sudo ln -s /init $path/sbin/init

As with every nspawn container, you can configure it by creating an /etc/systemd/nspawn/$name.nspawn (see man page). Here's mine—this is the simplest way to get internet access from inside the container:
[Files]
Bind=/home

[Network]
Private=no
VirtualEthernet=no

Now you're ready to run:
sudo machinectl start $name
sudo machinectl shell $name
sudo machinectl stop $name

Before you run your first nixos-rebuild, if your host is running an sshd, you may want to add services.openssh.enable = false; to your configuration.nix to prevent a port conflict.
Tested on Arch Linux, but I don't see why it wouldn't work on other systemd distros.

Oh, so not being able to downloading stuff from hydra was fixed, yay! That indeed makes things much easier already.
I tried it with building my own containerTarball, but I only fixed /etc/os-release and couldn't figure out the /init part. Have to test this soon!

I created a PR for the os-release issue at #35364 , @rhendric could you please take a look? I hoped this could take the /etc/os-release part away from the nspawn setup, but I'm not sure anymore.

The nspawn code searching for the init system, which does not check /init but /sbin/init, can be found at https://github.com/systemd/systemd/blob/476f65f98a60b070bfec85842f220f0d37819f7f/src/nspawn/nspawn.c#L2477

We might be able to work around needing to modify the init part of the tarball by adding this to the Exec section:
[Exec]
Boot=no
Parameters=/init

The /init link itself is created at: https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/profiles/docker-container.nix#L25
Using the storeContents attribute, we could either:
a) change the link from /init to /sbin/init
b) add the /sbin/init link on top for both docker and lxc, or only the lxc image.
c) if the [Exec] workaround works, leave it as is, and document the remaining required setup e.g. in the https://nixos.wiki

Is there any way Hydra could automatically push this image to the Docker Hub?

The [Exec] workaround works! So now if #35364 will be merged, we're down to no modifications required anymore!

Hm, not quite. It seems that using Boot=no does remove the need for /sbin/init (it also removes the need for /etc/os-release, so #35364 isn't even necessary), but it replaces it with a need for a /usr directory (see nspawn.c), which I had to manually create.
(Sorry for taking so long to get around to this; I tried a few times earlier but my free time always seemed to intersect with Hydra being down.)

That is really strange, it worked for me as described in #36364. But I see from the code it shouldn't have. @rhendric can you elaborate what happened on your system?
We probably should create our own base as an replacement for profile/docker.nix using /sbin/init instead of /init, or change it in the docker thing, so that we can boot=yes and land in this check: https://github.com/systemd/systemd/blob/2e10cc5649193eef5117fa5186869fbb74b0481e/src/basic/stat-util.c#L148

I thought maybe it's because I tried on NixOS which currently ships the somewhat outdated systemd v214, but no, that code is also in there. Why did it work for me, then? :thinking:

Transcript:
$ name=nixos-test-charlie
$ path=/var/lib/machines/$name
$ sudo machinectl pull-tar -q --verify=no https://hydra.nixos.org/build/71761700/download/1/nixos-system-x86_64-linux.tar.xz $name
Content too large.
$ printf %s '[Exec]
> Boot=no
> Parameters=/init
> ' | sudo tee /etc/systemd/nspawn/$name.nspawn
[Exec]
Boot=no
Parameters=/init
$ sudo machinectl start $name
Job for<EMAIL_ADDRESS>failed because the control process exited with error code.
See "systemctl status<EMAIL_ADDRESS>and "journalctl -xe" for details.
$ systemctl status<EMAIL_ADDRESS>| cat
●<EMAIL_ADDRESS>- Container nixos-test-charlie
   Loaded: loaded<EMAIL_ADDRESS>disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2018-03-23 12:48:53 EDT; 1min 20s ago
     Docs: man:systemd-nspawn(1)
  Process: 22908 ExecStart=/usr/bin/systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --network-veth -U --settings=override --machine=nixos-test-charlie (code=exited, status=1/FAILURE)
 Main PID: 22908 (code=exited, status=1/FAILURE)
   Status: "Terminating..."

Mar 23 12:48:53 adam systemd[1]: Starting Container nixos-test-charlie...
 Refusing.
Mar 23 12:48:53 adam systemd[1]<EMAIL_ADDRESS>Main process exited, code=exited, status=1/FAILURE
Mar 23 12:48:53 adam systemd[1]<EMAIL_ADDRESS>Failed with result 'exit-code'.
Mar 23 12:48:53 adam systemd[1]: Failed to start Container nixos-test-charlie.
$

My host OS is Arch Linux on x86_64, in case it matters.

For reference, https://github.com/erikarvstedt/extra-container project removed this pain for me. I was able to launch NixOS container on Ubuntu 17.10. I've documented 2 main problems in https://github.com/erikarvstedt/extra-container/issues/1, of which one is NixOS problem (the check for /etc/static/os-release), and one is extra-container problem (registers service units in wrong directory, which exists only in NixOS).

Given the age of this, I'm going to close this. If this is still an issue, please feel free to open and add more up to date context.


[feature] project fields in moon.yml should be optional

Is your feature request related to a problem? Please describe.
Currently when defining a project field, all of its fields need to be filled but this is cumbersome and sometimes not applicable, as such all fields should be optional.
For example not all projects have channels, and there might only be one owner (the organization that the repo belongs to) and therefore it just becomes repetitive.
Describe the solution you'd like
All fields should be optional.
Describe alternatives you've considered
N/A
Additional context
N/A

This has landed in v0.22!


Use gdal-config

On debian squeeze (and Ubuntu), the gdal lib name is not gdal but gdal1.8.0, the build instructions do not work.
This pull request propose to use gdal-config to build the lib by default, this implies to remove the libraries param in setup as it is passed in the command line.
Tested on debian squeeze and ubuntu lucid.

Thanks!


Payload size incorrect

The generated payload size is currently set to the number of bytes in the image, and doesn't include the size of the header and palette data. This means that the Surface::load_packed function misses off the last few bytes of the image.
I've raised an issue rather than fix it because I'm not sure which is the 'right' approach - if the payload size should include everything then we can fix it here, otherwise we'll need to fix it in Surface.

I think this might have been fixed as part of @ali1234's refactor...

I think this was fixed a long time ago (can't quite remember if it was in the tool or the API in the end), but somehow I never got around to closing the issue :-)


docker run applications mapping the project output

We can run docker on a project and build inside of the container directly. Not sure about cross OS building

See https://github.com/dotnet/tye for the future of this project


throw java.lang.InstantiationException instead of returning null

Hi,
jPopulator catches every java.lang.InstantiationException and returns null if the instantiation fails. I would prefer that my tests fail when the test data is incomplete. Therefore, I would be great, to be able to switch the behavior at InstantiationExceptions.
Best regards
Kermit the Frog

Hi,
Sorry for the late reply.
Could you please give an example of when the instantiation fails? I would like to see how jPopulator returns null.
What do you mean by "switch the behavior at InstantiationException"? Would it be throwing an exception or making this behavior configurable (to let the user choose between returning null or throwing an exception) ?
Regards
Mahmoud

Hello,
I was thinking of making the behaviour configurable in this way:
Populator populator = PopulatorBuilder.aNewPopulator()
   .silentMode(true) // or may be another method name
   .build();

This would (silently) swallow exceptions and return null when the instantiation fails. If silent mode is set to false, the populator will throw a runtime exception instead of returning null.
The second option is to update the Populator API to throw an exception:
public interface Populator {
    <T> T populateBean(final Class<T> type, final String... excludedFields) throws BeanPopulationException;
}

The client code will be able to catch the exception and know that bean population failed.
Would love to hear your thoughts.
Kind regards
Mahmoud

Hello Mahmoud
sorry for not replying to your first message. I'm on holiday for two weeks.
Thanks for thinking about my suggestion. Both options are ok for me. You should choose the one you prefer.
Kind regards,
kermit-the-frog
Am 21. Dezember 2015 23:36:07 MEZ, schrieb Mahmoud Ben Hassine<EMAIL_ADDRESS>
Hello,
I was thinking of making the behaviour configurable in this way:
Populator populator = PopulatorBuilder.aNewPopulator()
  .silentMode(true) // or may be another method name
  .build();

This would (silently) swallow exceptions and return null when the
instantiation fails. If silent mode is set to false, the populator will
throw a runtime exception instead of returning null.
The second option is to update the Populator API to throw an exception:
public interface Populator {
<T> T populateBean(final Class<T> type, final String... excludedFields)
throws BeanPopulationException;
}

The client code will be able to catch the exception and know that bean
population failed.
Would love to hear your thoughts.
Kind regards
Mahmoud

Reply to this email directly or view it on GitHub:
https://github.com/benas/random-beans/issues/39#issuecomment-166443033

Ok that's fine.
I'll go for adding an exception clearly in the API.
Have a nice holyday :smile:

Hello @kermit-the-frog
I've added the BeanPopulationException in the Populator API.
This exception will be thrown whenever a bean can not be populated.
You can catch this exception and make your test fail as requested.
Kind regards
Mahmoud

Sorry for the late response. Thanks for the Exception. The implementation as a runtime exception is perfect. The only thing that could be better is the message of the exception. It's hard to discover which field in which class causes the exception. Especially if you have serveral fields of the the same type in your classes.

Hi,

Thanks for the Exception. The implementation as a runtime exception is perfect.

Great! glad to hear that.

The only thing that could be better is the message of the exception. It's hard to discover which field in which class causes the exception. Especially if you have serveral fields of the the same type in your classes.

Sure! Please open a separate issue with all these details and I'll plan it for next release. Thanks
Regards
Mahmoud


Git push with --no-verify by default

I'm sure this was already asked before but I couldn't find any references.
Is there a way to use the Push function on VSCode but having it execute with the --no-verify flag command automatically (by default)?
Would be nice if there was a setting

Setting the git.allowNoVerifyCommit setting to true will enable a set of new commands in the "Commit" menu that use the --no-verify argument.


Customizable animation duration

I'd like to increase the animation duration, which is currently hardcoded to 1000ms. Can WaveSlider take in an animationSpec?

I think animationSpec is overkill. How about just adding another parameter called animationDuration? Or, replacing animationDirection parameter with a velocity parameter which specifies speed and direction?

Yea just the duration sounds good because you'll never want to use any non-linear easing spec.

It seems the current animation duration is 2000ms.
1000ms is the animation duration of wave height when it is changed.
Did you mean the animation duration of wave height?

Whoops I must have misread. The wave height animation duration of 1s is fine IMO.


[Store] No Documents Found Message should be displayed in Documentation tab when docs are not available

An info message should be displayed in doc page, when docs are not available.
Old UI

New UI

This is fixed


"react-native run-android " in the cmd meet with "cannot download the gradle" problem

info Fetching system and libraries information...
System:
OS: Windows 10 10.0.18362
CPU: (6) x64 Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz
Memory: 5.00 GB / 15.86 GB
Binaries:
Node: 12.18.0 - D:\dev\rn\install\node.EXE
Yarn: 1.17.3 - ~\AppData\Roaming\npm\yarn.CMD
npm: 6.14.4 - D:\dev\rn\install\npm.CMD
Watchman: Not Found
SDKs:
Android SDK:
API Levels: 10, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28
Build Tools: 23.0.1, 23.0.2, 23.0.3, 24.0.0, 24.0.2, 25.0.0, 25.0.2, 26.0.2, 27.0.2, 27.0.3, 28.0.0, 28.0.1, 28.0.2, 28.0.3
System Images: android-25 | Google APIs Intel x86 Atom, android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
Android NDK: 19.0.5232133
IDEs:
Android Studio: Not Found
Languages:
Java: Not Found
Python: 3.6.3
npmPackages:
@react-native-community/cli: Not Found
react: 16.11.0 => 16.11.0
react-native: 0.62.2 => 0.62.2
npmGlobalPackages:
react-native: Not Found

Your stacktrace says you are behind a proxy
Your info says you don't have Java JDK installed

Hi @zhangyang520 you can run npx react-native doctor on the root of your RN project to check for environment issues.
For future, environment issues Stack Overflow would be the more appropriate place to ask this. Thanks!


Receive Configuration Error when combining the Secrets and deployment into one file.

I had to apply the Secrets and Deployment files separately to fix the error.

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

ID: 301b44e3-4be7-6364-01b4-c2a55ff9b14a
Version Independent ID: 62569967-65c6-ece6-2d1e-689a73dd59ca
Content: Kubernetes on Azure - Cluster Autoscaler
Content Source: articles/aks/autoscaler.md
Service: container-service
GitHub Login: @sakthivetrivel
Microsoft Alias: sakthivetrivel

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


Add API endpoint and cli cmd to shut down daemon

[ ] Add api endpoint for nimona daemon to shut itself down
[ ] Add cli command to stop the daemon

We might want to move starting the daemon to nimona daemon start instead of just nimona daemon so we can add ways to configure the daemon.

We might want to move starting the daemon to nimona daemon start instead of just nimona daemon so we can add ways to configure the daemon.

This is currently implemented in #165 so it might be nice to wait for it to get merged.

Done in #170


Update package version

3.0.1-alpha.5 (2023-10-25)
Bug Fixes

frontend: refetch the task data (515485c)

:tada: This PR is included in version 1.1.0-alpha.13 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0-alpha.13 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.0.1-alpha.6 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0-alpha.11 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:


change ufw port for glance to 9393 from 9293.

Wrong Glance haproxy https port being opened up in ufw. Changed it from 9293 to 9393.

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

The commit message has some typos, but otherwise this is right.

Corrected the typos.


Create .babelrc

Hello @szhigunov. Why do you need to add a .babelrc file? The babel config is already in the package.json here.

Its a necessary part to add support react-native. React-native inspect all
deps and assumes that we need to use babel presets in applications, so
better way is to move babel config from package.json. That problem is also
touches in issue 102.
On Oct 26, 2016 18:38, "Guillaume Plique"<EMAIL_ADDRESS>wrote:

Hello @szhigunov https://github.com/szhigunov. Why do you need to add a
.babelrc file? The babel config is already in the package.json here
https://github.com/Yomguithereal/baobab-react/blob/master/package.json#L50-L56
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Yomguithereal/baobab-react/pull/119#issuecomment-256385650,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHGCPkQeleatA5H8pR_u6Sp6f5Q71rENks5q33PbgaJpZM4KhIMl
.

Thanks @szhigunov. Your PR is already merged and released in v2.1.2.

Already using in our application! Thanks
On Oct 28, 2016 12:19, "Guillaume Plique"<EMAIL_ADDRESS>wrote:

Thanks @szhigunov https://github.com/szhigunov. Your PR is already
merged and released in v2.1.2.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Yomguithereal/baobab-react/pull/119#issuecomment-256874776,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHGCPiNLbvPIEiMXKXoPLnaWcAXTIoj7ks5q4b4HgaJpZM4KhIMl
.


wsl --install : Don't work with System context

Windows Version
19045.3930
WSL Version
2.0.14
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
Ubuntu
Other Software
No response
Repro Steps
I want to deply WSL 2 to Intune but when testing on my local machine I can't install WSL with system context  (C:\pstools\PsExec.exe /s cmd) .
the Script:
####### Install the latest version of Ubuntu ######
Write-Log -Message "Starting Install WSL..."
wsl --install
########## Update WSL to the latest version ##########
Write-Log -Message "Starting Update WSL to the latest version..."
wsl --update --web-download
########## Set default version 2 ##########
Write-Log -Message "Starting Set default version 2..."
wsl --set-default-version 2
########## Install Ubuntu distribution ##########
Write-Log -Message "Starting Install Ubuntu distribution..."
wsl --install -d Ubuntu --no-launch
command for testing:
%WINDIR%\System32\windowsPowershell\v1.0\Powershell.exe -ExecutionPolicy Bypass -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -File Install_WSL.ps1
Expected Behavior
It should install WSL and update to latest version and set version 2 and instal Ubuntu distribution.
Actual Behavior
It gives the output:
COMMENTAIRES : Starting Install WSL...
o p y r i g h t   ( c )   M i c r o s o f t   C o r p o r a t i o n .
COMMENTAIRES : Starting Set default version 2...

    ]   [ C o m m a n d L i n e ]

Diagnostic Logs
No response

Any updates on this? Using Intune to distribute wsl and found out that it currently doesn't want to install in System context. Any reason why this limitation exists?
Our users don't have admin permissions (which they should not have in a corporate environment).

Try to use the WSL MSI directly with Intune (Windows MSI app) from from https://github.com/microsoft/WSL/releases
Anyway, wsl --install will download and install this msi.

You could try to deploy WSL2 to non-admin users through Intune using the WSL2 MSI [1] and the Intune [2] "Windows LOB apps" feature.
The required feature [3] VirtualMachinePlatform, could also be deployed as a dependency. using Intune.
[1] https://github.com/microsoft/WSL/releases
[2] https://learn.microsoft.com/en-us/microsoft-365/solutions/apps-type-lob?view=o365-worldwide
[3] https://learn.microsoft.com/nl-nl/windows/client-management/client-tools/add-remove-hide-features?pivots=windows-11#use-windows-powershell-to-disable-specific-features


Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
No applicable update found.
Brief description of your issue
Pull request https://github.com/microsoft/winget-pkgs/pull/151990 appears to have removed all references to the x64 package. The 32-bit package will not install on a 64-bit operating system.
Steps to reproduce

Install the Tenable.NessusAgent package via winget (winget install Tenable.NessusAgent)
The package fails to install

Actual behavior
The package fails to install on x64 devices
Expected behavior
Winget should select the correct package version for the architecture but the manifest no longer contains the x64 package
Environment
Windows Package Manager v1.7.11261
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19045.4291
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.11261.0

Winget Directories
-----------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled

Screenshots and Logs
No response

@markpconroyscp Can you show me a screenshot of the error please?

@vikingnope PSB

I think I have found a fix, please give me a few minutes to create a PR

@markpconroyscp Can you try again now and let me know please?

@vikingnope All working! Thank you for your prompt assistance :)


deprecated extension

Extension eg2.vscode-npm-script is deprecated:

Functionality is now supported by vscode directly:

https://code.visualstudio.com/updates/v1_23#_npm-script-running

Repoman Generation Results
Repoman pushed changes to remotes for the following projects:
Project: todo-nodejs-mongo-aca
Remote: azure-samples-staging
Branch: pr/2145
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-aca -b pr/2145

View Changes | Compare Changes

Project: todo-nodejs-mongo-aks
Remote: azure-samples-staging
Branch: pr/2145
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-aks -b pr/2145

View Changes | Compare Changes

Project: todo-nodejs-mongo-swa-func
Remote: azure-samples-staging
Branch: pr/2145
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-swa-func -b pr/2145

View Changes | Compare Changes

Project: todo-nodejs-mongo
Remote: azure-samples-staging
Branch: pr/2145
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo -b pr/2145

View Changes | Compare Changes

Project: todo-nodejs-mongo-terraform
Remote: azure-samples-staging
Branch: pr/2145
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-terraform -b pr/2145

View Changes | Compare Changes

Repoman Generation Results
Repoman pushed changes to remotes for the following projects:
Project: todo-nodejs-mongo-aca
Remote: azure-samples-staging
Branch: pr/2145
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-aca -b pr/2145

View Changes | Compare Changes

Project: todo-nodejs-mongo-aks
Remote: azure-samples-staging
Branch: pr/2145
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-aks -b pr/2145

View Changes | Compare Changes

Project: todo-nodejs-mongo-swa-func
Remote: azure-samples-staging
Branch: pr/2145
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-swa-func -b pr/2145

View Changes | Compare Changes

Project: todo-nodejs-mongo
Remote: azure-samples-staging
Branch: pr/2145
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo -b pr/2145

View Changes | Compare Changes

Project: todo-nodejs-mongo-terraform
Remote: azure-samples-staging
Branch: pr/2145
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-terraform -b pr/2145

View Changes | Compare Changes


grunt doesn't build www_root

This is probably not necessary, but a config option would be nice

Fixed in https://github.com/C-Bouthoorn/Epsilon/commit/9df0fb93910d810ba7d84db84733030ca318772d


KeyError during the process (MERSCOPE)

Hello Quentin,
I'm trying to use snakemake baysor to analyze our MERSCOPE datasets with the default config file. I have received the following error. Could you give me some advice to solve the problem?
$ snakemake --config data_path=/home/MERSCOPE/S2R3 --configfile=config/merscope/baysor_vizgen.yaml --cores 1 --use-conda
Building DAG of jobs...
Using shell: /usr/bin/bash
Provided cores: 1 (use --cores to define parallelism)
Rules claiming more threads will be scaled down.
Job stats:
job               count

aggregate             1
all                   1
explorer              1
image_write           1
report                1
resolve_baysor        1
total                 6
Select jobs to execute...
[Mon Sep 30 23:44:23 2024]
rule resolve_baysor:
reason: Missing output files: /home/MERSCOPE/raw_dat/S2R3.zarr/.sopa_cache/baysor_boundaries_done
resources: tmpdir=/tmp
KeyError: 'CR2d20505a1-64'
Reading transcript-segmentation outputs:   7%|█████████▍                                                                                | 2/29 [00:15<03:30,  7.81s/it]
[Mon Sep 30 23:48:25 2024]
Error in rule resolve_baysor:
jobid: 2

Hello @ykashima2, which version of Baysor are you using? I'm improving support for baysor 0.7.0, so it will fix many issues related to Baysor in the future

Hi Quentin, Thank you for the reply. I'm using baysor 0.7.0.

Alright, it makes sense then. I'll let you know when sopa 2.0.0 is released, it will fix this!

Hi @bednarsky, thanks for your kind words, I really appreciate :)
The version 2.0.0 is almost ready, but I'm still adding some tests to make sure it's stable. Also, the new version will use a new feature from the SpatialData library that has not been released yet. So, I will release Sopa 2 when I finish my tests + when the next version of SpatialData is released.
TL;DR: let's say something like early/mid-November!
Meanwhile, I'll see if it's easy/quick to cherry-pick my fixes for Baysor on master; I'll let you know.

Okay @bednarsky I cherry-picked the change and merged it on master, can you git pull and let me know if it's fixed?

Amazing, fixed the issue! Thank you so much! World record time to fix via writing an issue!

Nice haha, thanks! I'm closing the issue then


Change to use UGF.Assets package

Create branch from main
issue-28-change-to-use-ugf.assets-package