tries to launch, but quits

Not sure what other requirements are needed, but the installation went without any problems.  It might be the distribution or Window manager (RebornOS with Budgie Desktop).
I've noticed it seems to launch then immediately closes.

Thank you so much for reporting the issue can you please try running it from terminal and provide the output

It could be because a dependency issue . Can you install python-pyqt5 and then try opening it again. Or you can just reinstall the package from AUR. As i have updated the dependencies now

Closing this issue as OP didn't provide more information


Try updating to Nokogiri 1.3.10

When Dependabot did this, it didn't seem to get failures in its PR, but after it was merged (and broke) the auto-build per commit did see the problem. Weird. Gonna see if a draft PR gets a build failure or no.

Sure.
Failing commit: https://github.com/Shopify/yjit-bench/commit/4c717dc2cfecd4c5c4b31520c93458e93f5133ab
Failing build step: https://github.com/Shopify/yjit-bench/actions/runs/3829100596/jobs/6515419985
Error message from bundler:
nokogiri-1.13.10-x86_64-linux requires ruby version < 3.2.dev, >= 2.6, which is
incompatible with the current version, ruby 3.3.0p-1

I doubt it makes a difference, but this was an upgrade from 1.3.6 to 1.3.10, so the problem could date back to any of several different micro versions.

also see upstream bundler PR: https://github.com/rubygems/rubygems/pull/6225


Where's the CATS tab in 2.91?

I can't find it, also, the screenshots no longer apply for Blender versions 2.9 onwards.

Nevermind, I didn't realize I had to press N to view it.

Nevermind, I didn't realize I had to press N to view it.


$set in afterStateUpdated on select with scoped relationship not working in v3

Package
filament/filament
Package Version
3.0.42
Laravel Version
10.22.0
Livewire Version
No response
PHP Version
8.2.9
Problem description
I'm trying to set the property select to the customer's first property when a customer is selected. This worked in v2 but doesn't work in v3.
The issue is the where clause on the property select to scope the options to the selected customer. This isn't updated before the $set is called, so the select doesn't have the correct options.
Select::make('customer_id')
    ->relationship(
        'customer',
        'name',
        modifyQueryUsing: fn (Builder $query) => $query->whereBelongsTo(Filament::getTenant()))
    ->searchable()
    ->afterStateUpdated(function (Set $set, ?string $state) {
        $set('property_id', Customer::find($state)?->properties()->first()?->id);
    })
    ->required()
    ->reactive(),
Select::make('property_id')
    ->relationship('property', 'address_formatted',
        function (Builder $query, Get $get) {
            return $query->where('customer_id', $get('customer_id'));
        }
    )
    ->required(),

Expected behavior
The property select should update when the customer select is updated.
Steps to reproduce
Clone the reproduction repository. Create a new customer and property. Visit /admin/estimates/create and select a customer. The property should change to that customer's first property, but it doesn't. The relevant code is in app/Filament/Resources/EstimateResource.php.
Reproduction repository
https://github.com/eorenstein1/filament-set-reproduction
Relevant log output
No response

Had a similar issue, but was able to fix it by adding a:
->live(debounce: 50)


ERROR: Failed building wheel for insightface

            `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
              you can try to use `exclude_package_data`, or `include-package-data=False` in
              combination with a more fine grained `package-data` configuration.

              You can read more about "package data files" on setuptools documentation page:

              - https://setuptools.pypa.io/en/latest/userguide/datafiles.html

              [^1]: For Python, any directory (with suitable naming) can be imported,
                    even if it does not contain any `.py` files.
                    On the other hand, currently there is no concept of package data
                    directory, all directories are treated like packages.
              ********************************************************************************

      !!
        check.warn(importable)
      creating build/lib.linux-x86_64-cpython-310/insightface/data/images
      copying insightface/data/images/Tom_Hanks_54745.png -> build/lib.linux-x86_64-cpython-310/insightface/data/images
      copying insightface/data/images/mask_black.jpg -> build/lib.linux-x86_64-cpython-310/insightface/data/images
      copying insightface/data/images/mask_blue.jpg -> build/lib.linux-x86_64-cpython-310/insightface/data/images
      copying insightface/data/images/mask_green.jpg -> build/lib.linux-x86_64-cpython-310/insightface/data/images
      copying insightface/data/images/mask_white.jpg -> build/lib.linux-x86_64-cpython-310/insightface/data/images
      copying insightface/data/images/t1.jpg -> build/lib.linux-x86_64-cpython-310/insightface/data/images
      creating build/lib.linux-x86_64-cpython-310/insightface/data/objects
      copying insightface/data/objects/meanshape_68.pkl -> build/lib.linux-x86_64-cpython-310/insightface/data/objects
      creating build/lib.linux-x86_64-cpython-310/insightface/thirdparty/face3d/mesh/cython
      copying insightface/thirdparty/face3d/mesh/cython/mesh_core.cpp -> build/lib.linux-x86_64-cpython-310/insightface/thirdparty/face3d/mesh/cython
      copying insightface/thirdparty/face3d/mesh/cython/mesh_core.h -> build/lib.linux-x86_64-cpython-310/insightface/thirdparty/face3d/mesh/cython
      copying insightface/thirdparty/face3d/mesh/cython/mesh_core_cython.c -> build/lib.linux-x86_64-cpython-310/insightface/thirdparty/face3d/mesh/cython
      copying insightface/thirdparty/face3d/mesh/cython/mesh_core_cython.cpp -> build/lib.linux-x86_64-cpython-310/insightface/thirdparty/face3d/mesh/cython
      copying insightface/thirdparty/face3d/mesh/cython/mesh_core_cython.pyx -> build/lib.linux-x86_64-cpython-310/insightface/thirdparty/face3d/mesh/cython
      copying insightface/thirdparty/face3d/mesh/cython/setup.py -> build/lib.linux-x86_64-cpython-310/insightface/thirdparty/face3d/mesh/cython
      running build_ext
      building 'insightface.thirdparty.face3d.mesh.cython.mesh_core_cython' extension
      creating build/temp.linux-x86_64-cpython-310
      creating build/temp.linux-x86_64-cpython-310/insightface
      creating build/temp.linux-x86_64-cpython-310/insightface/thirdparty
      creating build/temp.linux-x86_64-cpython-310/insightface/thirdparty/face3d
      creating build/temp.linux-x86_64-cpython-310/insightface/thirdparty/face3d/mesh
      creating build/temp.linux-x86_64-cpython-310/insightface/thirdparty/face3d/mesh/cython
      gcc -pthread -B /home/ubuntu/anaconda3/envs/hallo/compiler_compat -Wno-unused-result -Wsign-compare -DNDEBUG -fwrapv -O2 -Wall -fPIC -O2 -isystem /home/ubuntu/anaconda3/envs/hallo/include -fPIC -O2 -isystem /home/ubuntu/anaconda3/envs/hallo/include -fPIC -Iinsightface/thirdparty/face3d/mesh/cython -I/tmp/pip-build-env-jcpgxzhb/overlay/lib/python3.10/site-packages/numpy/core/include -I/home/ubuntu/anaconda3/envs/hallo/include/python3.10 -c insightface/thirdparty/face3d/mesh/cython/mesh_core.cpp -o build/temp.linux-x86_64-cpython-310/insightface/thirdparty/face3d/mesh/cython/mesh_core.o
      gcc: fatal error: cannot execute ‘cc1plus’: execvp: No such file or directory
      compilation terminated.
      error: command '/usr/bin/gcc' failed with exit code 1
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for insightface
Failed to build insightface
ERROR: Could not build wheels for insightface, which is required to install pyproject.toml-based projects

solved
sudo ln -s /usr/lib/gcc/x86_64-linux-gnu/11/cc1plus /usr/bin/cc1plus
ls -l /usr/bin/cc1plus
pip install -r requirements.txt


Add Jaeger integration.

Jaeger is an easy to use request tracer for distributed systems. It's super useful for microservices.

This feature must be added as a part of #85.


@conda-forge-admin, please add user @maresb

Comment:
As you wish, just to make my life slightly easier...

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @maresb in conda-forge/aesara-feedstock#66.


Audit function parameter and return types (2/2)

Ensure that functions in the following modules have the correct types and ensure that all color types can be passed as parameters:

inGamut
luminance
set
setAll
space
toGamut

space.js
I wasn't sure about the types for the to and from methods on Colorspace. If we allow any color type and call getColor in those methods then we introduce a cyclic dependency between the getColor module and the space module. If we're ok having the cyclic dependency and want to allow any color type I can make the appropriate changes.

I wasn't 100% convinced that getColor should be called in setAll but that's what I've gone with for now.

I'm not opposed to calling getColor in set/setAll etc, but currently there are a number of types that are incorrect, some of them a bit tangential to this PR.
First, the type of getColor itself is wrong -- it claims to return a PlainColorObject (or PlainColorObject[]), where in reality if it is passed a Color object, it returns a Color object. That means that every fn which calls getColor and then returns the response (e.g. set, setAll, and toGamut) is also wrong -- they all claim to return a PlainColorObject but often return a Color.

Keep in mind that PlainColorObject is an interface and the Color type implements the PlainColorObject interface.
The types for the getColor function and other functions that return PlainColorObject simply guarantee that the object that is returned conforms to the PlainColorObject interface (space, coords and alpha properties). The object may be a Color, object literal, or some other class that has space, coords and alpha properties.
let x: PlainColorObject = getColor("red"); // returns an object literal
let y: PlainColorObject = getColor(new Color("red")); // returns a Color object
let z: Color = getColor(new Color("red")); // type error

If we want to make additional guarantees about returning the same object if it conforms to the PlainColorObject interface or that we may modify an object in place we can do that in the JSDoc comments.
None of the functions exported in 'colorjs.io/fn' should have types that reference the Color type because the Color class isn't available in colorjs.io/fn.

Honestly, this (that is, keeping the types up-to-date with the codebase) is going to be an ongoing headache unless we're willing to start re-writing the code itself in TypeScript. That's something I'd be willing to consider taking on (potentially with help from @MysteryBlokHed, if he's willing), but I vaguely recall that @LeaVerou was opposed to that direction -- Lea, can you confirm?

I do have some reservations, one of which being that there are many folks who are proficient in color science but only dabble with JS, and a TS codebase is hostile to them. Whereas having the types separately means we can still accept contributions from folks who are not comfortable with TS, and adjust the typings ourselves after.
I’m willing to examine it , but could you elaborate a bit on how TS would help with this issue? I obviously get how it would help us keep types up to date, but not how it would help with the return type issue.

I'm fine merging this as-is, then I have a follow-up PR I can open with a few more proposed changes.

Did you still want me to review https://github.com/lloydk/color.js/pull/1 or should I wait for the follow-up PR?

I'm fine merging this as-is, then I have a follow-up PR I can open with a few more proposed changes.

Did you still want me to review lloydk#1 or should I wait for the follow-up PR?

Probably easier for me to open the PR here and review it then -- thanks!


[stable/verdaccio]: Document pull policy correctly

What this PR does / why we need it:
This MRs fixes the README documentation regarding pull policy.
The default behavior of this chart's pull policy is IfNotPresent, regardless of what the image tag is.

Signed cnfc-cla

@seanknox @viglesiasce Would be great to get your feedback on this.

/assign @mattfarina

If you use an image with tag latest (which is btw not recommended), you should set the pullPolicy to Always as follow:
$ helm install --name my-release \
    --set image.pullPolicy=Always \
    stable/verdaccio

@etiennetremel Thank you very much for the fast response! Yes, I understand overriding the pullPolicy via the command-line.
The use-case we had (using verdaccio-gitlab) was something like the following:
helm install --name my-release \
    --set image.repository=...../verdaccio-gitlab --set image.tag=latest \
    stable/verdaccio

In this case, the image tag is overwritten correctly. However, the pullPolicy is still enforced as ifNotPresent, which does not conform with expected behavior of kubernetes, right? In the current case, the user needs to remember to also override the pullPolicy whenever he wants to use the image latest.
That's why I thought it might make sense not to enforce it here in the chart and let the underlying kubernetes infrastructure take care of the rest.
What do you think?

I'm a bit skeptics about this change since you should let the user choose what they want to do.
Let's see what the approvers suggest. FYI, the imagePullPolicy parameter is created by default during chart bootstrap helm create my-chart.
Default Kubernetes behavior is described here: https://kubernetes.io/docs/concepts/containers/images/#updating-images

@etiennetremel thanks, yes, I am aware of the Kubernetes behavior :-) I had already included the link you provided in my commit message. :-)
I just raised this up because I found that the verdaccio helm chart does not conform to that expected behavior. The README also says it should behave this way but it does not. So if you decide not to take this in, an update to the README would be nice:
https://github.com/helm/charts/blob/master/stable/verdaccio/README.md#configuration

Ha right, README is misleading, IfNotPresent should be default behavior. Thanks for pointing this out.

@etiennetremel you are welcome, thanks for your feedback :-)

@etiennetremel If you guys have corrected this in the README, I guess this can be closed.

Maybe we can make the README.md adjustment in this PR since it is open?

Oh, ok, I thought that it had already been added. I would wait for Erçan then, he should be back in a couple of days and he's the owner of the PR & fork :-)

@etiennetremel @dlouzan @bufferoverflow: Updated the README accordingly and kept the existing pull policy behaviour as you suggested.
Please have a look and let me know what you think.

/ok-to-test

/retest

@mattfarina Fixed the merge conflict. Please take a look.

/lgtm

/approve


Style 403 and 404 pages

Style 404 and 403 error pages

@aleksandraworhacz please resolve conflicts and it's good for merging. Nice work


Error storing data in DB

Apache 7.2
PHP 7.2
MariaDB 10.2
Laravel 5.5.42
gloudemans/shoppingcart 2.5.0
In my CartCotroller I have next
public function __construct()
{
    $this->middleware('auth');
    $this->middleware(function ($request, $next) {
        Cart::restore(Auth::user()->id);
        return $next($request);
    });
}

public function __destruct()
{
    Cart::store(Auth::user()->id);
}

Data is not saving to shoppingcart table. In content field I have only part next

O:29:"Illuminate\Support\Collection":1:{s:8:"

Only this piece of code. No more. As result data not restored from DB

This is possible because Auth::user() is null while controller destructing, maybe. Но это не точно ))

@rariteth No. If try this
public function __destruct()
{
    dd(Auth::user()->id);
    Cart::store(Auth::user()->id);
}

I can see id of my user at the page. So Auth::user() not null while controller destructing

Try this:
\Log::debug(\Auth::user()->id);
to be completely sure

Unfortunately this is big deal to save Cart items and restore every request. Why  cart items is deleted while restoring? I thing is it bug.

\Log::debug(\Auth::user()->id);
return null
Hmm... What can I do with it?

If you testing through dd your session is alive! Its a magic )))
my ugly code maybe helps you - https://pastebin.com/DEzC5xsu

@rariteth I think need to replace all serialize in this repo to json_encode and unserialize to json_decode


Can't install addin

Describe the bug
I wanted to install the ExceLint-addin so I retrieved the manifest.xml file, saved it to the wef directory as instructed, then opened Excel and used the Add-in to attempt to install it. I saw a spinner for quite a while, then saw this message:

To Reproduce
... See above...
Expected behavior
I expected the addin to be installed
Screenshots
Desktop (please complete the following information):

OS: [e.g. iOS] macOS 12.7.4
Browser [e.g. Chrome, Safari] N/A
Version [e.g. Excel 2016, Excel Online] Excel for Mac Version 16.84 (24041420)

Additional context
@dbarowy @emeryberger I peeked into the manifest.xml file and found this snippet:
 <SourceLocation DefaultValue="https://excelint-addin.westus2.cloudapp.azure.com/index.html" />

dig shows the address for excelint-addin.westus2.cloudapp.azure.com to be <IP_ADDRESS>

Could that plugin be revived on azure.com?
Is there a way to make the plugin available elsewhere? Perhaps on github.com?

Many thanks.

Good news...

The ExceLint add-in seems still to work without incident with Excel for Mac (current version)

I was able to build the add-in locally (I needed to use node 16.4.0 to avoid conflicts/outdated packages)

I also created a Dockerfile that builds a container for testing on localhost. This helps people avoid the need to install all kinds of software on their computer to make it work. Would you be interested in a PR?

Finally, any thoughts about making the add-in available from a different server?
Thanks again for this wonderful tool.
Rich Brown
Lyme, NH

Solved with #48. ExceLint add-in is now served from a Github Page from this repo


GenerateMips updated to handle sRGB better

Actually this is not sufficient to address the issue. It is still relying on the previous sample level to do the average which is going to be wrong.


Docs: append anchor tag to headers

Docs should append an anchor tag to each header element in the page body.
Input:
## Installation

Output:

  Installation #

Thank you!


Rename app to Zulip in iOS and Android. Fixes #185

Automated message from Dropbox CLA bot
@borisyankov, it looks like you've already signed the Dropbox CLA. Thanks!


Added EntityFramework.Exceptions

ORM/EntityFramework.Exceptions - EntityFramework.Exceptions
Use typed Exceptions for  Entity Framework Core when your SQL query violates database constraints in SqlServer, MySql, PostgreSQL or SQLite

Probably worthwhile highlighting that this is EntitiyFrameworkCore only

@CZEMacLeod Feel free to send a PR to add support for EF6 :wink:


error when I compile

I have this error then I run "make BOARD=RPI1":
Use make V=1 or set BUILD_VERBOSE in your environment to increase build verbosity.
GEN build/genhdr/qstr.i.last
GEN build/genhdr/qstr.split
GEN build/genhdr/qstrdefs.collected.h
QSTR updated
GEN build/genhdr/qstrdefs.generated.h
mkdir -p build/build/
mkdir -p build/extmod/
mkdir -p build/lib/embed/
mkdir -p build/lib/libc/
mkdir -p build/lib/libm/
mkdir -p build/lib/mp-readline/
mkdir -p build/lib/oofatfs/
mkdir -p build/lib/timeutils/
mkdir -p build/lib/utils/
mkdir -p build/py/
CC ../micropython/py/mpstate.c
In file included from ./mpconfigport.h:2,
                 from ../micropython/py/mpconfig.h:62,
                 from ../micropython/py/mpstate.h:31,
                 from ../micropython/py/mpstate.c:27:
./arm_exceptions.h:34:1: error: FP registers might be clobbered despite 'interrupt' attribute: compile with '-mgeneral-regs                                      -only' [-Werror=attributes]
   34 | extern void __attribute__((interrupt("UNDEF"))) undef_handler(void);
      | ^~~~~~
./arm_exceptions.h:35:1: error: FP registers might be clobbered despite 'interrupt' attribute: compile with '-mgeneral-regs                                      -only' [-Werror=attributes]
   35 | extern void __attribute__((interrupt("SWI"))) svc_handler(void);
      | ^~~~~~
./arm_exceptions.h:36:1: error: FP registers might be clobbered despite 'interrupt' attribute: compile with '-mgeneral-regs                                      -only' [-Werror=attributes]
   36 | extern void __attribute__((interrupt("ABORT"))) abort_handler(void);
      | ^~~~~~
./arm_exceptions.h:37:1: error: FP registers might be clobbered despite 'interrupt' attribute: compile with '-mgeneral-regs                                      -only' [-Werror=attributes]
   37 | extern void __attribute__((interrupt("IRQ"))) irq_handler(void);
      | ^~~~~~
./arm_exceptions.h:38:1: error: FP registers might be clobbered despite 'interrupt' attribute: compile with '-mgeneral-regs                                      -only' [-Werror=attributes]
   38 | extern void __attribute__((interrupt("FIQ"))) fiq_handler(void);
      | ^~~~~~
cc1: all warnings being treated as errors
make: *** [../micropython/py/mkrules.mk:47: build/py/mpstate.o] Error 1

SOLVED
it work only on 32bits OS


Computer Vision Script

@DhanushNehru
Smart Attendance System Using QR code attendance
I hope you will assign this issue to me , As I will Push my project to this repo under hacktoberfest tag.
Thank you.

Hope it would be in a form of script where people can input values and use with a proper readme.md @raj-mistry-01


[Issue]: failed call to hipInit: HIP_ERROR_InvalidDevice

Problem Description
TensorFlow cannot detect GPU
$ python -c "import tensorflow as tf;print(tf.config.list_physical_devices('GPU'))"
2024-04-29 21:45:03.118699: E external/local_xla/xla/stream_executor/plugin_registry.cc:93] Invalid plugin kind specified: DNN
2024-04-29 21:45:03.156327: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-04-29 21:45:04.020735: E external/local_xla/xla/stream_executor/rocm/rocm_driver.cc:261] failed call to hipInit: HIP_ERROR_InvalidDevice
2024-04-29 21:45:04.020751: I external/local_xla/xla/stream_executor/rocm/rocm_diagnostics.cc:111] retrieving ROCM diagnostic information for host: home
2024-04-29 21:45:04.020755: I external/local_xla/xla/stream_executor/rocm/rocm_diagnostics.cc:118] hostname: home
2024-04-29 21:45:04.020782: I external/local_xla/xla/stream_executor/rocm/rocm_diagnostics.cc:141] librocm reported version is: NOT_FOUND: was unable to find librocm.so DSO loaded into this program
2024-04-29 21:45:04.020787: I external/local_xla/xla/stream_executor/rocm/rocm_diagnostics.cc:145] kernel reported version is: UNIMPLEMENTED: kernel reported driver version not implemented
[]
Operating System
Ubuntu 22.04.4 LTS (Jammy Jellyfish)
CPU
Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
GPU
AMD Radeon RX 7900 XTX
ROCm Version
ROCm 6.1.0
ROCm Component
No response
Steps to Reproduce

Follow the steps here o install amdgpu driver and rocm-6.1.0 and hip sdk.
conda create -n TensorFlow python=3.10 -y
conda activate TensorFlow
wget https://repo.radeon.com/rocm/manylinux/rocm-rel-6.1/tensorflow_rocm-2.15.0-cp310-cp310-manylinux2014_x86_64.whl
pip install ./tensorflow_rocm-2.15.0-cp310-cp310-manylinux2014_x86_64.whl
python -c "import tensorflow as tf;print(tf.config.list_physical_devices('GPU'))"

(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
ROCk module version 6.7.0 is loaded
HSA System Attributes
Runtime Version:         1.13
Runtime Ext Version:     1.4
System Timestamp Freq.:  1000.000000MHz
Sig. Max Wait Duration:<PHONE_NUMBER>3709551615 (0xFFFFFFFFFFFFFFFF) (timestamp count)
Machine Model:           LARGE
System Endianness:       LITTLE
Mwaitx:                  DISABLED
DMAbuf Support:          YES
==========
HSA Agents

Agent 1

Name:                    Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
Uuid:                    CPU-XX
Marketing Name:          Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
Vendor Name:             CPU
Feature:                 None specified
Profile:                 FULL_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        0(0x0)
Queue Min Size:          0(0x0)
Queue Max Size:          0(0x0)
Queue Type:              MULTI
Node:                    0
Device Type:             CPU
Cache Info:
L1:                      32768(0x8000) KB
Chip ID:                 0(0x0)
ASIC Revision:           0(0x0)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   4700
BDFID:                   0
Internal Node ID:        0
Compute Unit:            8
SIMDs per CU:            0
Shader Engines:          0
Shader Arrs. per Eng.:   0
WatchPts on Addr. Ranges:1
Features:                None
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: FINE GRAINED
Size:                    65781560(0x3ebbf38) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Recommended Granule:4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
Pool 2
Segment:                 GLOBAL; FLAGS: KERNARG, FINE GRAINED
Size:                    65781560(0x3ebbf38) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Recommended Granule:4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
Pool 3
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    65781560(0x3ebbf38) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Recommended Granule:4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
ISA Info:

Agent 2

Name:                    gfx1100
Uuid:                    GPU-85631fd855c9cea1
Marketing Name:          Radeon RX 7900 XTX
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          64(0x40)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    1
Device Type:             GPU
Cache Info:
L1:                      32(0x20) KB
L2:                      6144(0x1800) KB
L3:                      98304(0x18000) KB
Chip ID:                 29772(0x744c)
ASIC Revision:           0(0x0)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   2482
BDFID:                   768
Internal Node ID:        1
Compute Unit:            96
SIMDs per CU:            2
Shader Engines:          6
Shader Arrs. per Eng.:   2
WatchPts on Addr. Ranges:4
Coherent Host Access:    FALSE
Features:                KERNEL_DISPATCH
Fast F16 Operation:      TRUE
Wavefront Size:          32(0x20)
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Max Waves Per CU:        32(0x20)
Max Work-item Per CU:    1024(0x400)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
Max fbarriers/Workgrp:   32
Packet Processor uCode:: 92
SDMA engine uCode::      20
IOMMU Support::          None
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    25149440(0x17fc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Recommended Granule:2048KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 2
Segment:                 GLOBAL; FLAGS: EXTENDED FINE GRAINED
Size:                    25149440(0x17fc000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Recommended Granule:2048KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 3
Segment:                 GROUP
Size:                    64(0x40) KB
Allocatable:             FALSE
Alloc Granule:           0KB
Alloc Recommended Granule:0KB
Alloc Alignment:         0KB
Accessible by all:       FALSE
ISA Info:
ISA 1
Name:                    amdgcn-amd-amdhsa--gfx1100
Machine Models:          HSA_MACHINE_MODEL_LARGE
Profiles:                HSA_PROFILE_BASE
Default Rounding Mode:   NEAR
Default Rounding Mode:   NEAR
Fast f16:                TRUE
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
FBarrier Max Size:       32
*** Done ***
Additional Information
OS:
NAME="Ubuntu"
VERSION="22.04.4 LTS (Jammy Jellyfish)"
CPU:
model name      : Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
GPU:
Name:                    Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
Marketing Name:          Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
Name:                    gfx1100
Marketing Name:          Radeon RX 7900 XTX
Name:                    amdgcn-amd-amdhsa--gfx1100

If you are willing to try docker, you might want to try latest ROCm tensorflow build from
https://hub.docker.com/r/rocm/tensorflow/tags

docker pull rocm/tensorflow:rocm6.1-py3.9-tf2.15-dev

If you are willing to try docker, you might want to try latest ROCm tensorflow build from
https://hub.docker.com/r/rocm/tensorflow/tags

docker pull rocm/tensorflow:rocm6.1-py3.9-tf2.15-dev

I tried and no help. It shows the same errors.

@Looong01 Internal ticket has been created to fix this issue. Thanks!

Hello @Looong01, please try adding yourself to the render and video groups so that your current user can access your GPU resources:
sudo usermod -a -G render,video $LOGNAME
Then reboot your machine to try again.
Please let me know if this issue still appears afterwards.

@Looong01 This command is already in the installation guide: https://rocm.docs.amd.com/projects/install-on-linux/en/latest/tutorial/quick-start.html


Enable automatic release discussions

Q
A

🐛 Bug fix?
no

🚀 New feature?
no

⚠ Deprecations?
no

❌ BC Break
no

🔗 Related issues
https://github.com/snyk/driftctl/issues/552

❓ Documentation
no

Description
This PR adds a new option to goreleaser so it creates a new GitHub discussion for each new release. This option has been introduced in Goreleaser in v0.163.0.

I'll of course defer to longer-term maintainers, but I think we should start with: why?
Specific issues, PRs, and discussions can already be raised. A potential downside of opening an unfocussed discussion for every release would be for multiple issues to be discussed in one thread. What would the benefit be?


Add Vite template for create fuels

Take the NextJS template as a reference:

https://github.com/FuelLabs/fuels-ts/tree/master/templates/nextjs

One should be able to install it by informing the template option:
npm create fuels -- --template vite

And it should also be made the default template (instead of NextJS), when:
npm create fuels

cc @FuelLabs/devrel

Blocked by:

https://github.com/FuelLabs/fuels-ts/issues/2837


Hello_fpga example

Hi,
I'm using the quick start guide to run hello_fpga but when I launch the command "./hello_fpga", after compiling, I get the following error:
"Error enumerating Accelerators: not found"
Can anyone help me?
Thanks for your help.

Hi!
Can you provide some details on your setup? What hardware are you running on, what driver are you using?
Do you have root access to your platform?
Thanks

Enno

Hi,
I'using a virtual machine with Centos 7.3 (the host OS is Windows server
2012 R2). I installed the OPAE drivers following the guide (v0.9.0). Yes, I
have root access, so I set up my environment variables by root.
Thanks for your help
Il mercoledì 6 dicembre 2017, Enno Lübbers<EMAIL_ADDRESS>ha
scritto:

Hi!
Can you provide some details on your setup? What hardware are you running
on, what driver are you using?
Do you have root access to your platform?
Thanks

Enno

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OPAE/opae-sdk/issues/78#issuecomment-349802026, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Af019-hpIxgk38tDSyT1R8ShQg9i6CoWks5s9xrtgaJpZM4Q4c4U
.

Thanks for the info! What FPGA platform do you have in your system?

I have not a physical platform yet, but I should use an Arria 10 GX FPGA
from Intel/Altera.
Marco Montini
Il domenica 10 dicembre 2017, Enno Lübbers<EMAIL_ADDRESS>ha
scritto:

Thanks for the info! What FPGA platform do you have in your system?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OPAE/opae-sdk/issues/78#issuecomment-350559039, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Af01987oFnn_zfxxtREDc6MFasDwtA3Vks5s_AMFgaJpZM4Q4c4U
.

If you don't have an FPGA platform in your system, it is expected for the software not to find any accelerators (well, to be fair, there aren't any :)).
If you want to run your OPAE application without hardware, you can run it against a simulation of your accelerator in the AFU Simulation Environment (ASE). You'll need to link your application against a different implementation of the OPAE library (libopae-c-ase instead of libopae-c) and run your accelerator RTL through a logic simulator.
Have a look at the ASE user guide for more details on how to use ASE.

Yes, I understood the problem after I sent you the email. I followed step
by step the ASE's guide but I had different warnings when I launched the
command "make" (no errors but 37 warnings). Then I launched the command
"make sim" to run the simulator but I got three errors. I attached 3
screens: one after the command "make" and the others after the command
"make install"(it is the same screen divided in two parts). I'm using
licensed Modelsim-ae 10.5c.
Could you help me? Thanks.
Marco Montini
ᐧ
2017-12-12 19:07 GMT+01:00 Enno Lübbers<EMAIL_ADDRESS>
If you don't have an FPGA platform in your system, it is expected for the
software not to find any accelerators (well, to be fair, there aren't any
:)).
If you want to run your OPAE application without hardware, you can run it
against a simulation of your accelerator in the AFU Simulation Environment
(ASE). You'll need to link your application against a different
implementation of the OPAE library (libopae-c-ase instead of libopae-c)
and run your accelerator RTL through a logic simulator.
Have a look at the ASE user guide
https://opae.github.io/docs/ase_userguide/ase_userguide.html for more
details on how to use ASE.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OPAE/opae-sdk/issues/78#issuecomment-351135424, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Af0190GmefPno-G3qJDC-DVPj2JDTzScks5s_sDQgaJpZM4Q4c4U
.


clock message docs

I'm trying to send MIDI Clock signals and it's not clear from the docs what's going on. There's just one mention of clock and it takes no parameters, so I can't set data to F8/FA/FB/FC. I believe what I'm trying to do is send F8 as I'm trying to synchronize a clock on a remote device (effects unit).
What is going out when you send a Message ('clock')?

Hi and welcome to mido.
Your question would be better suited for the discussions Q&A area.
Issues are not the place for this.
Thanks.


Port to FreeRTOS

FreeRTOS is an operating system that supports many IoT boards. It would be nice to port Soletta to that operating system.
Likely the port will be based on the one for other small OS such as RIOT.

Any plans on this issue?

@ronaldotd started but never had time to finish the basics. You can check with him for his early stage code and continue if you want to do it.

@barbieri Thanks for the prompt reply
I just wanted to check if Soletta would work in a esp8266 running FreeRTOS. Unfortunately I don't have time nor experience on this kind of porting at the moment. I'll keep an eye on it though


new "stable" (v0.4) release?

@i-rinat : you haven't released a new "stable" (v0.4?) release in ~½ year and there has been many changes since then, maybe it would be a good time for one? (if you are uncertain about the stability, release a RC version first)

Let's call it v0.3.7: https://github.com/i-rinat/freshplayerplugin/releases/tag/v0.3.7
I sort of have a tradition to break things when their version changes from 0.3 to 0.4. So, 0.3.7 for now. 😄

Sure that's fine, maybe 0.4-rc wouldn't have been a bad option either


SS_ListDecorator::TotalItems() calling wrong method

SS_ListDecorator::TotalItems() calls $this->list->TotalItems(), but TotalItems() is not defined in the SS_List interface. It should call either $this->list->count(), or just $this->Count() instead.

This has been resolved, and can be closed.

Closed via 7896ce6a90420c82705647fcb5caa62d489abb64


Auto-complete of tmux session target directory

Is it possible to get tab auto-complete of the tmux session directory ie tmux new-session -c ~/work which would suggest directories that match?

Someone will have to modify the tmux completion and submit it upstream.


User ervice

Removed not needed header components
Added Redux state management for authentication
Added Auth logic to hide certain components from users
Added backend user service  to handle login and signup

Things to add on for User Service:

[ ] Integrate MySQL for user management to backend user service
[ ] Firebase to generate JWT tokens
[ ] Build User Profile Page to display all the details and stats
[ ] Store user's attempted questions (to show on dashboard which questions are done before)

and more

LGTM


Delete VM annotations and firmware fields when cloning

Pull Request Test Coverage Report for Build 684

5 of 7 (71.43%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.09%) to 87.066%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/k8s/clone.js
5
7
71.43%

Totals

Change from base Build 861:
-0.09%

Covered Lines:
2081

Relevant Lines:
2284

💛  - Coveralls

Pull Request Test Coverage Report for Build 862

5 of 7 (71.43%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.09%) to 87.066%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/k8s/clone.js
5
7
71.43%

Totals

Change from base Build 861:
-0.09%

Covered Lines:
2081

Relevant Lines:
2284

💛  - Coveralls


dont add filterChainMatch for wildcard hostnames

skip creating a filterChainMatch with a * server_names match since envoy doesnt like it and errors out.

Fixes: https://github.com/envoyproxy/gateway/issues/601
Signed-off-by: Arko Dasgupta<EMAIL_ADDRESS>

cc @chauhanshubham

Codecov Report

Merging #604 (5993d5e) into main (84bf298) will decrease coverage by 0.05%.
The diff coverage is 61.53%.

@@            Coverage Diff             @@
##             main     #604      +/-   ##
==========================================
- Coverage   60.81%   60.75%   -0.06%
==========================================
  Files          47       47
  Lines        5721     5716       -5
==========================================
- Hits         3479     3473       -6
- Misses       2024     2025       +1
  Partials      218      218

Impacted Files
Coverage Δ

internal/gatewayapi/translator.go
84.22% <ø> (-0.12%)
:arrow_down:

internal/xds/translator/listener.go
80.10% <61.53%> (-1.32%)
:arrow_down:

internal/provider/kubernetes/httproute.go
59.25% <0.00%> (-0.83%)
:arrow_down:

internal/provider/kubernetes/gatewayclass.go
73.91% <0.00%> (+0.72%)
:arrow_up:

internal/provider/kubernetes/helpers.go
80.43% <0.00%> (+6.52%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

verified
kubectl get gateway -A -o yaml
apiVersion: v1
items:
- apiVersion: gateway.networking.k8s.io/v1beta1
  kind: Gateway
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"gateway.networking.k8s.io/v1beta1","kind":"Gateway","metadata":{"annotations":{},"name":"eg","namespace":"default"},"spec":{"gatewayClassName":"eg","listeners":[{"name":"https","port":8080,"protocol":"HTTPS","tls":{"certificateRefs":[{"group":"","kind":"Secret","name":"example-cert"}],"mode":"Terminate"}}]}}
    creationTimestamp: "2022-10-19T02:57:45Z"
    generation: 1
    name: eg
    namespace: default
    resourceVersion: "1301"
    uid: 0852e5ef-c64a-4163-98ff-ac2120af885e
  spec:
    gatewayClassName: eg
    listeners:
    - allowedRoutes:
        namespaces:
          from: Same
      name: https
      port: 8080
      protocol: HTTPS
      tls:
        certificateRefs:
        - group: ""
          kind: Secret
          name: example-cert
        mode: Terminate
  status:
    addresses:
    - type: IPAddress
      value: <IP_ADDRESS>
    - type: Hostname
      value: localhost
    conditions:
    - lastTransitionTime: "2022-10-19T03:00:34Z"
      message: The Gateway has been scheduled by Envoy Gateway
      observedGeneration: 1
      reason: Scheduled
      status: "True"
      type: Scheduled
    - lastTransitionTime: "2022-10-19T03:00:35Z"
      message: Address assigned to the Gateway, 1/1 envoy Deployment replicas available
      observedGeneration: 1
      reason: Ready
      status: "True"
      type: Ready
    listeners:
    - attachedRoutes: 1
      conditions:
      - lastTransitionTime: "2022-10-19T03:00:34Z"
        message: Listener is ready
        observedGeneration: 1
        reason: Ready
        status: "True"
        type: Ready
      name: https
      supportedKinds:
      - group: gateway.networking.k8s.io
        kind: HTTPRoute
kind: List
metadata:
  resourceVersion: ""
🐳 ~/go-workspace/src/github.com/envoyproxy/gateway$ curl -v -HHost:www.example.com --resolve "www.example.com:8080:<IP_ADDRESS>" --cacert example.com.crt https://www.example.com:8080/get
* Added www.example.com:8080:<IP_ADDRESS> to DNS cache
* Hostname www.example.com was found in DNS cache
*   Trying <IP_ADDRESS>...
* TCP_NODELAY set
* Connected to www.example.com (<IP_ADDRESS>) port 8080 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: example.com.crt
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server did not agree to a protocol
* Server certificate:
*  subject: CN=www.example.com; O=httpbin organization
*  start date: Oct 18 21:15:36 2022 GMT
*  expire date: Oct 18 21:15:36 2023 GMT
*  common name: www.example.com (matched)
*  issuer: O=example Inc.; CN=example.com
*  SSL certificate verify ok.
> GET /get HTTP/1.1
> Host:www.example.com
> User-Agent: curl/7.64.1
> Accept: */*
>
< HTTP/1.1 200 OK
< content-type: application/json
< x-content-type-options: nosniff
< date: Wed, 19 Oct 2022 03:04:13 GMT
< content-length: 427
< x-envoy-upstream-service-time: 0
< server: envoy
<
{
 "path": "/get",
 "host": "www.example.com",
 "method": "GET",
 "proto": "HTTP/1.1",
 "headers": {
  "Accept": [
   "*/*"
  ],
  "User-Agent": [
   "curl/7.64.1"
  ],
  "X-Envoy-Expected-Rq-Timeout-Ms": [
   "15000"
  ],
  "X-Forwarded-Proto": [
   "https"
  ],
  "X-Request-Id": [
   "76b62191-3e54-4ca5-ae2b-6617d95f3d38"
  ]
 },
 "namespace": "default",
 "ingress": "",
 "service": "",
 "pod": "backend-57cfdc96fb-fsctf"
* Connection #0 to host www.example.com left intact
}* Closing connection 0

@arkodg please test to see if the HTTPS backend is reachable after deleting the secret and comment here.


oha: 1.4.7 -> 1.5.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/oha/versions.
meta.description for oha is: HTTP load generator inspired by rakyll/hey with tui animation
meta.homepage for oha is: https://github.com/hatoo/oha
meta.changelog for oha is: https://github.com/hatoo/oha/blob/v1.5.0/CHANGELOG.md
Updates performed

Rust version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.0 with grep in /nix/store/29vbrnr6yc7r60hjyvxydba9h5s6khv3-oha-1.5.0
found 1.5.0 in filename of file in /nix/store/29vbrnr6yc7r60hjyvxydba9h5s6khv3-oha-1.5.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

oha

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/29vbrnr6yc7r60hjyvxydba9h5s6khv3-oha-1.5.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A oha https://github.com/r-ryantm/nixpkgs/archive/e973c3ee013bcf9aca94499bbc2c476084354f8d.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/e973c3ee013bcf9aca94499bbc2c476084354f8d#oha

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/29vbrnr6yc7r60hjyvxydba9h5s6khv3-oha-1.5.0
ls -la /nix/store/29vbrnr6yc7r60hjyvxydba9h5s6khv3-oha-1.5.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

oha

Maintainer pings
cc @figsoda for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 362807

aarch64-darwin

:white_check_mark: 1 package built:

oha


Make intermediate_files a parameter instead of dumping it in the tool's directory by default

We should default to the CWD of where it's run from, definitely not the application location, which is a nuisance when it's on an image (and generally seems a bad practice for a shared tool, so this moves it in that direction).

The solution applied with TooT-SC works well, so we'll apply it here.


[BUG] Unable to disable security by following documentation

Describe the bug
According to https://docs-beta.opensearch.org/docs/security/configuration/disable/, it should be possible to disable security by setting opensearch_security.disabled: true in opensearch.yml. With 1.0.0-beta1, it was possible to use docker run -p 9200:9200 -e "discovery.type=single-node" -e "opensearch_security.disabled=true" opensearchproject/opensearch:1.0.0-beta1 to start a local OpenSearch node for local testing without security. With 1.0.0-rc1, this doesn't work any more.
[2021-06-08T18:13:20,645][ERROR][o.o.b.OpenSearchUncaughtExceptionHandler] [f4fbee7677c4] uncaught exception in thread [main]
org.opensearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [opensearch_security.disabled] please check that any required plugins are installed, or check the breaking changes documentation for removed settings
	at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:186) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:173) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:99) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:140) ~[opensearch-cli-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.cli.Command.main(Command.java:103) ~[opensearch-cli-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:139) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:105) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
Caused by: java.lang.IllegalArgumentException: unknown setting [opensearch_security.disabled] please check that any required plugins are installed, or check the breaking changes documentation for removed settings
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:557) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:502) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:473) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:444) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.common.settings.SettingsModule.<init>(SettingsModule.java:162) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.node.Node.<init>(Node.java:417) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.node.Node.<init>(Node.java:301) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:240) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.Bootstrap.setup(Bootstrap.java:240) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:406) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:182) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	... 6 more
uncaught exception in thread [main]
java.lang.IllegalArgumentException: unknown setting [opensearch_security.disabled] please check that any required plugins are installed, or check the breaking changes documentation for removed settings
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:557)
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:502)
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:473)
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:444)
	at org.opensearch.common.settings.SettingsModule.<init>(SettingsModule.java:162)
	at org.opensearch.node.Node.<init>(Node.java:417)
	at org.opensearch.node.Node.<init>(Node.java:301)
	at org.opensearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:240)
	at org.opensearch.bootstrap.Bootstrap.setup(Bootstrap.java:240)
	at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:406)
	at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:182)
	at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:173)
	at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:99)
	at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:140)
	at org.opensearch.cli.Command.main(Command.java:103)
	at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:139)
	at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:105)

To Reproduce
Steps to reproduce the behavior:

Try to start a local OpenSearch container with docker run -p 9200:9200 -e "discovery.type=single-node" -e "opensearch_security.disabled=true" opensearchproject/opensearch:1.0.0-rc1.

Expected behavior
The container is successfully started without security enabled.
Plugins
Nothing explicitly change. Output from container startup:
[2021-06-08T18:13:19,659][INFO ][o.o.p.PluginsService     ] [f4fbee7677c4] loaded plugin [opensearch-alerting]
[2021-06-08T18:13:19,659][INFO ][o.o.p.PluginsService     ] [f4fbee7677c4] loaded plugin [opensearch-anomaly-detection]
[2021-06-08T18:13:19,659][INFO ][o.o.p.PluginsService     ] [f4fbee7677c4] loaded plugin [opensearch-asynchronous-search]
[2021-06-08T18:13:19,659][INFO ][o.o.p.PluginsService     ] [f4fbee7677c4] loaded plugin [opensearch-index-management]
[2021-06-08T18:13:19,659][INFO ][o.o.p.PluginsService     ] [f4fbee7677c4] loaded plugin [opensearch-job-scheduler]
[2021-06-08T18:13:19,659][INFO ][o.o.p.PluginsService     ] [f4fbee7677c4] loaded plugin [opensearch-knn]
[2021-06-08T18:13:19,659][INFO ][o.o.p.PluginsService     ] [f4fbee7677c4] loaded plugin [opensearch-notebooks]
[2021-06-08T18:13:19,659][INFO ][o.o.p.PluginsService     ] [f4fbee7677c4] loaded plugin [opensearch-performance-analyzer]
[2021-06-08T18:13:19,660][INFO ][o.o.p.PluginsService     ] [f4fbee7677c4] loaded plugin [opensearch-reports-scheduler]
[2021-06-08T18:13:19,660][INFO ][o.o.p.PluginsService     ] [f4fbee7677c4] loaded plugin [opensearch-security]
[2021-06-08T18:13:19,660][INFO ][o.o.p.PluginsService     ] [f4fbee7677c4] loaded plugin [opensearch-sql]

Host/Environment (please complete the following information):

OS: Ubuntu
Version 20.04

Additional context
A bit separate, but FWIW, having security enabled by default is a difference from the default Elasticsearch containers. We use the default Elasticsearch images in tests and local development and have used them without security up until now.

I've moved this to the security repo, definitely looks like a bug.

@slovdahl Could you please try with opendistro_security.disabled instead of opensearch_security.disabled?

For 1.0.0-beta1, it should be opendistro_security.disabled. For 1.0.0.-rc1, it should be plugins.security.disabled. There is no such settings for opensearch_security.disabled.

I think the doc should say "delete the opensearch_securityplugins.security configuration entries from opensearch.yml"

@slovdahl Could you please try with opendistro_security.disabled instead of opensearch_security.disabled?

Same problem:
$ docker run -p 9200:9200 -e "discovery.type=single-node" -e "opendistro_security.disabled=true" opensearchproject/opensearch:1.0.0-rc1

...

[2021-06-09T05:11:01,621][ERROR][o.o.b.OpenSearchUncaughtExceptionHandler] [082447f12250] uncaught exception in thread [main]
org.opensearch.bootstrap.StartupException: java.lang.IllegalArgumentException: unknown setting [opendistro_security.disabled] did you mean [opendistro_security.audit.enable_rest]?
	at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:186) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:173) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:99) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:140) ~[opensearch-cli-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.cli.Command.main(Command.java:103) ~[opensearch-cli-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:139) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:105) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
Caused by: java.lang.IllegalArgumentException: unknown setting [opendistro_security.disabled] did you mean [opendistro_security.audit.enable_rest]?
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:557) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:502) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:473) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:444) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.common.settings.SettingsModule.<init>(SettingsModule.java:162) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.node.Node.<init>(Node.java:417) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.node.Node.<init>(Node.java:301) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:240) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.Bootstrap.setup(Bootstrap.java:240) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:406) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:182) ~[opensearch-1.0.0-rc1.jar:1.0.0-rc1]
	... 6 more
uncaught exception in thread [main]
java.lang.IllegalArgumentException: unknown setting [opendistro_security.disabled] did you mean [opendistro_security.audit.enable_rest]?
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:557)
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:502)
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:473)
	at org.opensearch.common.settings.AbstractScopedSettings.validate(AbstractScopedSettings.java:444)
	at org.opensearch.common.settings.SettingsModule.<init>(SettingsModule.java:162)
	at org.opensearch.node.Node.<init>(Node.java:417)
	at org.opensearch.node.Node.<init>(Node.java:301)
	at org.opensearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:240)
	at org.opensearch.bootstrap.Bootstrap.setup(Bootstrap.java:240)
	at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:406)
	at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:182)
	at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:173)
	at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:99)
	at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:140)
	at org.opensearch.cli.Command.main(Command.java:103)
	at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:139)
	at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:105)

For 1.0.0-beta1, it should be opendistro_security.disabled. For 1.0.0.-rc1, it should be plugins.security.disabled. There is no setting for opensearch_security.disabled.

Thank you! That did the trick. Is there a reference to this somewhere in the documentation? I couldn't find anything.

@cliu123 Thanks. I can also confirm that docker run -p 9200:9200 -e "discovery.type=single-node" -e "plugins.security.disabled=true" opensearchproject/opensearch:1.0.0-rc1 does indeed work correctly. OpenSearch starts, with security disabled. :rocket: :bow: Thanks a lot for this!
Sub-discussion about the changed security model
As for this comment from @slovdahl:

A bit separate, but FWIW, having security enabled by default is a difference from the default Elasticsearch containers. We use the default Elasticsearch images in tests and local development and have used them without security up until now.

I do agree that this is a big breaking change in terms of drop-in compatibility for OpenSearch 1.0.0 vs ElasticSearch 7.10.

Elasticsearch 7.10 listens on port 9200 with HTTP by default
OpenSearch 1.0.0 listens on port 9200 with HTTPS by default, using a self-signed certificate, and requires authentication

It would be interesting to hear if this has been discussed more in-depth within the project (please refer me to the GitHub issue(s) if this is indeed the case).
I suggest going with either one of the following approaches:

Set plugins.security.disabled=true by default, making the security plugin be opt-in as far as OpenSearch 1.0.0 is concerned (staying closer in spirit to the ES original semantics). The security plugin could then be enabled in a future release (like OS 2.0.0). Or, if this is not considered a good idea/has been discussed already:
Make the docs be super-clear on this topic. It would perhaps make sense to have a sub-section somewhere saying "Switching back to Elasticsearch security semantics" or something.

And to make things clear: I'm not questioning the new security model per se. The default used by Elasticsearch has arguably been a bit odd. What I'm slightly questioning is the fact that this is being introduced in something that I had perceived should be a drop-in replacement for existing Elasticsearch servers, with a minimum amount of fuss for our users. Perhaps this assumption is slightly incorrect?

Thank you! That did the trick. Is there a reference to this somewhere in the documentation? I couldn't find anything.

Docs were fixed in https://github.com/opensearch-project/documentation-website/commit/c4cf6838bf8bfd6264a914d07fa71cb8a6c0a855 and I added https://github.com/opensearch-project/documentation-website/pull/48.

@perlun Thanks for your comments!
Someone please correct me if I am wrong, but security is enabled by default in OpenDistro, so this isn't a breaking change. The equivalent of what you describe is the minimal Elasticsearch artifact, which is also going to also be available as OpenSearch, which won't know anything about the security plugin. There's a discussion on that here.
That said, security and reliability are both so critical that any artifacts without security built-in is 🤯 to me. I'd like to make security a module in some future (as opposed to a plugin, modules cannot be uninstalled) and effectively introduce a breaking change into the minimal artifact as well. We'll want to do that with all the appropriate discussions, deprecation and a major version increments as you rightfully point out.

@dblock Thanks for clearing things out. I do understand your (the project/AWS) perspective a bit better now. :+1:

The equivalent of what you describe is the minimal Elasticsearch artifact, which is also going to also be available as OpenSearch, which won't know anything about the security plugin. There's a discussion on that here.

Thanks, skimmed through that discussion a bit yesterday. I wonder if it makes sense to call both the "minimal Elasticsearch" and the "full, opinionated Elasticsearch + built-in plugins" as the same OpenSearch name though? I guess that's where the -lite, -min, -core etc suffix comes into picture, that definitely makes it clearer. Perhaps this is good enough for time being, given the future vision ("security included, cannot be disabled") you describe in a future major version
(I do think that enforcing HTTPS even for dev environments is perhaps taking it a bit too far though, given the certificate hassles it involves, self-signed certificats et al. But that's a bit of a separate discussion. :slightly_smiling_face:)
Looking at https://hub.docker.com/r/opensearchproject/opensearch, I get the impression that we don't have a Docker image with the "bare", minimal OpenSearch (without security/etc) available yet. Looking forward to see it happen at some point. :pray:

Thanks for your feedback @perlun! The team had decided to call the product "OpenSearch" and "OpenSearch Dashboards". It's definitely confusing that opensearch-project/OpenSearch is just the min engine, but I learned to live with the mental model of OpenSearch (the product with all the plugins) and OpenSearch (the server engine) being two different things 🤣

Closing the issue since the documentation has been corected.


feat: providerArgs option to the push & pull command

fix: #168
add providerArgs option to the push & pull command

Sure!
Just a moment, please.


VSL-142: Added FCLCrypto contract and reused it's validation

Description

Added FCLCrypto.cdc to core contracts and reused it's function for validating signature
Removed MyMultiSig validateSignature function
Updated UI transactions to send also the messageHex which is used for validating signatures, beside parameter called message which is used to validate the content of the message
Demo / Test Result

make test

Closing because not all commits are reflected


[core] support count on files and manifest list name

Purpose

Linked issue: close #1773

Thanks @schnappi17 , LGTM +1, wait for ci


seqtoseq model evaluation part

hello there
I'm working currently on a small chatbot using the SeqToSeq model and the database provided here, but I couldn't figure out the role of the evaluation part more precisely the context vector in the decoder class because in my case the user will have to enter just the question and the response has to be generated by the decoder based on the training hidden states of the encoder
I'm asking if I can tweak the model somehow to be valid with the use case of my web app using the same database, I appreciate any help u could give
`
def answer(question_txt, context_txt, answer_txt_tru):
question = qa_tokenizer.encode_sentences([question_txt], out_length = max_length_inp)
context = cx_tokenizer.encode_sentences([context_txt], out_length = max_length_tar)
question = tf.convert_to_tensor(question)
context = tf.convert_to_tensor(context)
hidden = [tf.zeros((1, units))]
enc_hidden = encoder(question, hidden)
pred = decoder(context, enc_hidden)

start = tf.argmax(pred[0], axis = -1).numpy()[0]
end = tf.argmax(pred[1], axis = -1).numpy()[0]

if start >= len(context_txt.split()):
  start = len(context_txt.split()) - 1
if end >= len(context_txt.split()):
  end = len(context_txt.split()) - 1

# if one word prediction
if end == start:
  end += 1
answer_txt = (' ').join(context_txt.split()[start:end])

print("Question : ", question_txt)
print("Context  : ",context_txt)
print("Pred Answer : ",answer_txt)
print("True Answer : ", answer_txt_tru)
print("======================")

`

The example above will not work because it is for question answering which takes context and question. I dont think the dataset will work for your case. I suggest you use this notebook but you will need another dataset.


Small fixes to docs.

Removes "copy to clipboard" functionality. It's only marginally useful, and it relies on Flash, which is
increasingly deprecated.
Updates theme path for prism syntax highlighting.

@Garbee or @surma: PTAL!

LGTM just looking over the code right now. Will manually run and verify later today that everything works as expected.

@Garbee: OK to merge?

Oh whoops, forgot to go back and test manually. Doing that right now...

Runs fine here. Merging.

No worries, was nothing urgent :) Thanks, @Garbee!


Unexpected value NaN parsing y1 attribute.

null value for Y axis (hole in data) in combination with time series and Chartist.Interpolation.step() produces unexpected behavior:

Hello @WURMiL 👋
Chartist has recently been updated to version 1.0 with some new exciting changes like ESM and TypeScript support. The migration guide can be found right here.
Please let me know if the issue is still relevant to you so we can further investigate it!


Support probing from source namespaces

The probe should be run from the namespace in which the Networktester resource resides. This will ensure the probing is done in a way that takes Networkpolicies into account.

Rather run in restricted namespace mode in relevant namespace. Overhead should be negligible


Increase foldability of various templates

SizeBench revealed heavily non-foldability of certain C++/WinRT templates contributing to increased Windows binary sizes. Some small tweaks dropped the size of test.exe (release, x64) by ~132kb. (5180416 -> 5030400, or 2.8% ... which isn't a super lot, but it's nonzero.
Fixes #1334 and related
Changes
Enable nuspec iteration - Bump the default nuspec version to <IP_ADDRESS> so build_nuget.cmd and iterating with a local nuget source is easier.
Add solution files - Niceness for people who live in Visual Studio.
Fold delegate bases - Forced the layout of the delegate types to be regular by moving the reference count into a base before the non-ABI types. This folds nearly all the AddRef/QueryInterface instances into one. Releases are still unique because they call up into dtors.
Fold "report" in invoke - The invoke helper is a try/catch{report} but the body of "report" is identical on each invoke specialization. Move it to a unique non-inlineable method.
Fold event::add - Make the delegate first, then all the "expand the collection" instances are identical.
Further Work
SizeBench reports the following additional foldability wastage, quoted from the same test.exe:

make_agile_delegate<> - 3.2kb; the agile thunk is unique basically per delegate ::Invoke vtable and offset adjusters.
root_implements::<T1,T2,T3>::query_interface - 4.1kb; again unique per vtable instance, also related to inlining choices
winrt::event::add - 3.2kb; all cost related to inlined use of make_agile_delegate
winrt::impl::runtime_class_name<T1,T2>::get() - 1.4kb; should probably switch to std::wstring_view but this may be a breaking change; currently induces an hstring construction.

Testing
Tested by build_and_test.cmd - all built, all passed

For posterity, switching name_of<> and get_name<> to use std::wstring_view was basically a net wash.  No test code compilation errors that would signal a breaking change, overall binary increased by about 512 bytes.
One area of interest is in GetRuntimeClassName. The inliner is super aggressive about splatting winrt::hstring(anything) inline (and ~hstring) rather than hoisting them out.  In PGO-optimized binaries this ctor is normally de-inlined since it's replicated countless times throughout the code. Making a custom winrt::hstring get_runtime_class_name(std::wstring_view) would likely not really help, as PGO should automatically produce that that when used.

It looks like I can get another 8kb by regularizing the tail of query_interface. Running total after that is ~140kb.
It also looks like the cluster around make_agile_delegate could be connected to a simplification on how delegates are generated. Delegate ctors have a lot of overloads - lambda, function, raw-pointer member, com_ptr member, weak_ref member, shared_ptr member, weak_ptr member.  Under the covers they all route through the lambda form, doing various forms of "lock" and "call method." I wonder if there's a simplification of those to a two-form version.  Unless we were willing to try some stronger type-erasure through a std::function-alike, I'm not sure this can be reduced further.  It's probably another 3.2kb on this test binary, so under 0.5%.

/azp run

Overall looks like goodness. Just a few comments.

One area of interest is in GetRuntimeClassName. The inliner is super aggressive about splatting winrt::hstring(anything) inline (and ~hstring) rather than hoisting them out. In PGO-optimized binaries this ctor is normally de-inlined since it's replicated countless times throughout the code. Making a custom winrt::hstring get_runtime_class_name(std::wstring_view) would likely not really help, as PGO should automatically produce that that when used.

For windows-rs I managed to write a "constexpr" version of hstring so that it can be declared as a compile-time constant. This is mainly used for literals, but it also turns these GetRuntimeClassName into a cheap pointer copy. There are some limitations, so I'm not sure its super practical for cppwinrt to adopt though.

Making the constructor of param::hstring constexpr seems pretty trivial, and it would enable constexpr fast-pass strings.

Making the constructor of param::hstring constexpr seems pretty trivial, and it would enable constexpr fast-pass strings.

I was referring to return values, which has a lot more optimizing value.


Add Mesoscope rig example

Adding mesosocpe_ophys_rig.py and mesoscope_ophys_rig.json to repository

Is this PR still being worked on?

@saskiad I have added what I believe to be all the missing parts I was able to define and track. For the parts missing, I would ask Alex and team to help fill in the gaps especially with respect to how items (e.g. calibrations) get updated and tracked.

Note the mesoscope there is called "429_mesoscope_20220321" which is a slight change of text from before "429-mesoscope-2022321"
I am not sure of the implications. Please tell me how it should be called. This is meant to be MESO.1

Note the mesoscope there is called "429_mesoscope_20220321" which is a slight change of text from before "429-mesoscope-2022321"
I am not sure of the implications. Please tell me how it should be called. This is meant to be MESO.1

It should be dashes.

its 6mm according to the thorlabs website.

From: arielleleon @.>
Sent: Wednesday, November 20, 2024 3:08 PM
To: AllenNeuralDynamics/aind-data-schema @.>
Cc: Alex Cahoon @.>; Mention @.>
Subject: Re: [AllenNeuralDynamics/aind-data-schema] Add Mesoscope rig example (PR #901)
@arielleleon commented on this pull request.

In examples/multiplane_ophys_rig.jsonhttps://github.com/AllenNeuralDynamics/aind-data-schema/pull/901#discussion_r1851098852:

       "manufacturer": {

          "name": "Thorlabs",

          "abbreviation": null,

          "registry": {

             "name": "Research Organization Registry",

             "abbreviation": "ROR"

          },

          "registry_identifier": "04gsnvb07"

       },

       "model": "MVL6WA",

       "path_to_cad": null,

       "port_index": null,

       "additional_settings": {},

       "notes": null,

       "focal_length": "6",

       "focal_length_unit": "millimeter",

Will check with Alex - this may be 6"
—
Reply to this email directly, view it on GitHubhttps://github.com/AllenNeuralDynamics/aind-data-schema/pull/901#discussion_r1851098852, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7SAEYY5FSN7X5NHXBAECKT2BUJAPAVCNFSM6AAAAABGX2N73SVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDINBZHA3TOMRZGU.
You are receiving this because you were mentioned.Message ID: @.***>

its 6mm according to the thorlabs website.
________________________________ From: arielleleon @.> Sent: Wednesday, November 20, 2024 3:08 PM To: AllenNeuralDynamics/aind-data-schema @.> Cc: Alex Cahoon @.>; Mention @.> Subject: Re: [AllenNeuralDynamics/aind-data-schema] Add Mesoscope rig example (PR #901) @arielleleon commented on this pull request.
________________________________ In examples/multiplane_ophys_rig.json<#901 (comment)>:

"manufacturer": {
"name": "Thorlabs", + "abbreviation": null, + "registry": { + "name": "Research Organization Registry", + "abbreviation": "ROR" + }, + "registry_identifier": "04gsnvb07" + }, + "model": "MVL6WA", + "path_to_cad": null, + "port_index": null, + "additional_settings": {}, + "notes": null, + "focal_length": "6", + "focal_length_unit": "millimeter", Will check with Alex - this may be 6" — Reply to this email directly, view it on GitHub<#901 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7SAEYY5FSN7X5NHXBAECKT2BUJAPAVCNFSM6AAAAABGX2N73SVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDINBZHA3TOMRZGU. You are receiving this because you were mentioned.Message ID: @.***>

I think we should remove any metadata for off the shelf parts. It is endless otherwise. I would recommend just storing the part numbers and manufacturer, this is sufficient information.

Agreed, 100%

From: Jerome Lecoq @.>
Sent: Wednesday, November 20, 2024 3:24 PM
To: AllenNeuralDynamics/aind-data-schema @.>
Cc: Alex Cahoon @.>; Mention @.>
Subject: Re: [AllenNeuralDynamics/aind-data-schema] Add Mesoscope rig example (PR #901)
its 6mm according to the thorlabs website.
________________________________ From: arielleleon @.> Sent: Wednesday, November 20, 2024 3:08 PM To: AllenNeuralDynamics/aind-data-schema @.> Cc: Alex Cahoon @.>; Mention @.> Subject: Re: [AllenNeuralDynamics/aind-data-schema] Add Mesoscope rig example (PR #901https://github.com/AllenNeuralDynamics/aind-data-schema/pull/901) @arielleleonhttps://github.com/arielleleon commented on this pull request.
________________________________ In examples/multiplane_ophys_rig.json<#901 (comment)https://github.com/AllenNeuralDynamics/aind-data-schema/pull/901#discussion_r1851098852>:

"manufacturer": {
"name": "Thorlabs", + "abbreviation": null, + "registry": { + "name": "Research Organization Registry", + "abbreviation": "ROR" + }, + "registry_identifier": "04gsnvb07" + }, + "model": "MVL6WA", + "path_to_cad": null, + "port_index": null, + "additional_settings": {}, + "notes": null, + "focal_length": "6", + "focal_length_unit": "millimeter", Will check with Alex - this may be 6" — Reply to this email directly, view it on GitHub<#901 (comment)https://github.com/AllenNeuralDynamics/aind-data-schema/pull/901#discussion_r1851098852>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7SAEYY5FSN7X5NHXBAECKT2BUJAPAVCNFSM6AAAAABGX2N73SVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDINBZHA3TOMRZGU. You are receiving this because you were mentioned.Message ID: @.***>

I think we should remove any metadata for off the shelf parts. It is endless otherwise. I would recommend just storing the part numbers and manufacturer, this is sufficient information.
—
Reply to this email directly, view it on GitHubhttps://github.com/AllenNeuralDynamics/aind-data-schema/pull/901#issuecomment-2489740215, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7SAEY5MJMRDQGDFIWYQ2PD2BUK2RAVCNFSM6AAAAABGX2N73SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBZG42DAMRRGU.
You are receiving this because you were mentioned.Message ID: @.***>


iOS appends question mark to URL when params are empty

On 0.2.1 when executing a GET request with iOS, a question mark is appended to the URL if the params are empty. Depending on your server-side app, this could cause problems. My own solution was to add a dummy param.

I get that too


nazghul 0.7.1

Is there no way to make formula aliases outside of Homebrew core?

Looks like the test is failing.

Yeah, I forgot to update the test after renaming stuff.


Architecture: Architecture Decisions

Section Architecture Decisions (design/decisions.qmd). There might be some overlap with other sections, like the C4 Component Diagram. We've already started with this in the design/decisions/ folder, but we should finish with the major decisions we are making, like:

[x] Why Django
[x] Why Python
[ ] Why Git
[ ] Why DVC? Or other.
[x] Why REST

Any others?

Decisions have been moved to another repo, and these don't need this here.


How to fetch  Art from a deviantArt artist, really I need your help kek

What are the search tokens I'm able to use in DeviantArt.
I'm trying to search a specific artist in grabber w/ DeviantArt as the source to download their art.
artist name is "Akamoriart".
any help please

Grabber uses either the RSS feed or the search field from DeviantArt to perform searches, so you would do it the same way you do there. For RSS the prefix is by:. Like by:username.


Updated public address lookup method to rely on Ceph conf

The updated logic uses ceph.conf file to read the mon host addresses, hence the charm logic can run on any MicroCeph unit.

I would be totally up with updating all mon ips (best case scenario :D). Was concerned how the clients would react to multiple IPs where they expected just one in the relation databag.

maybe we should add new param in the relation databag and deprecate the older one ?


[Add] Create user api

This PR allows creating a user from API.
https://developer.nulab-inc.com/docs/backlog/api/2/add-user/

@biplobice
It corresponded with release1.1.0.
Thank you!


this.remove breaks when using splice on an array

I believe there is an issue when using the remove method for a node. Installed from npm version 0.6.6
If the node is part of an array, and you remove that node from the array, this changes the size of the parent array. Then when the traverse.forEach function tries to walk to the next node of that array, the array size has changed and the the index is invalid.
One possible solution is to index arrays backwards from (length - 1) to 0. That way when you splice out and element, the array size changes but the index will always be valid.
a quick example to illustrate the point: (code and output below)
I will attempt to remove all nodes with the key "tileIdx". You will see that not all are removed if they are in the same parent array. The array index is out of bounds after removing the first element.

Code:
var traverse = require('traverse');
var obj = {     "expanded" : "true",    "folder" : "true",  "key" : "1",    "title" : "Caitlin Havener",    "children" : [  {   "expanded" : "true",    "folder" : "true",  "key" : "2",    "title" : "Sports",     "children" : [  {   "folder" : "true",  "key" : "3",    "title" : "Basketball",     "children" : [  {   "key" : "_2",   "tileIdx" : "54bea3403282a1af40c8ac67" }, {   "key" : "_3",   "tileIdx" : "54bea3403282a1af40c8ac67" } ] },   {   "folder" : "true",  "key" : "6",    "title" : "Football" } ] } ] };
console.log("Before: \n" + JSON.stringify(obj) + "\n\n");
traverse(obj).forEach(function (x) {
console.log("Current Node: " + JSON.stringify(x));
if (x && x.tileIdx)
    this.remove(true);

});
console.log("\nFinal output:\n");
console.log(JSON.stringify(obj));

Would you mind using code formatting to make your question a little more readable?
https://help.github.com/articles/basic-writing-and-formatting-syntax/

I was able to work around this by using a before callback to reverse the order that arrays are traversed.
NOTE: This only works for forEach traversal and NOT map
var traverse = require('traverse');

var obj = {
    tree: [
        { content: "First" },
        { content: "abc" },
        { content: "Second" }
    ]
};

var result = traverse(obj).forEach(function() {
    if (Array.isArray(this.node)) {
        this.before(function() {
            this.keys = this.keys.reverse();
        });
    }
    if (this.node && this.node.content === 'abc') {
        this.remove();
    }
});

console.dir(result.tree);


Update golang.org/x/net -> v0.15.0

Update golang.org/x/net from v0.12.0 -> v0.15.0 to address https://security.snyk.io/vuln/SNYK-GOLANG-GOLANGORGXNETHTML-5816820

Thank you. It's important to understand, though, that the go.mod file of goquery does not define what the applications using goquery will use. That is, the fact that goquery's go.mod does not use the latest version of a dependency does not prevent in any way applications using goquery from updating to the latest dependency (as long as that dependency is version-compatible, of course):
$ go mod init
go: creating new go.mod: module myapp

$ go get github.com/PuerkitoBio/goquery@latest
go: added github.com/PuerkitoBio/goquery v1.8.1
go: added github.com/andybalholm/cascadia v1.3.1
go: added golang.org/x/net v0.7.0

$ go get -u
go: upgraded github.com/andybalholm/cascadia v1.3.1 => v1.3.2
go: upgraded golang.org/x/net v0.7.0 => v0.15.0

$ cat go.mod
module myapp

go 1.21.1

require github.com/PuerkitoBio/goquery v1.8.1

require (
	github.com/andybalholm/cascadia v1.3.2 // indirect
	golang.org/x/net v0.15.0 // indirect
)

Thank you for pointing this out - I was not aware. Good to know!

No problem, yeah it's not something that is widely known or understood about Go modules.


Gracefully handle half created projects

Ignore half created projects when building the project list at
login. Before this change a half created (or half deleted project)
would result in an NPF which would prevent the user from logging in.
Change-Id: Iafdc0c6ec1a3cf4a31c9a534455116f9d268be74

@halatmit @ram8647 @afmckinney This fixes the problem that Ralph was having today.

LGTM
Although I did not test this.


added get community tests

Description
This PR includes the following proposed change(s):

{List all the changes, if possible add the jira ticket #}

Requires
Add 'Requires Attention' label if appropriate.

[ ] Requires an update to the .env file
[ ] Requires adding a file listed in the .gitignore
[ ] Requires an opinion or answer to a question, see comments.
[ ] Requires other attention, see below.

If there are any requirements for the developer to make after this PR is merged please list them here.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation
[ ] Version change

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
For pull requests that are not just a simple fix, please check that the branch works on your local machine.

[ ] Tested by Zach.
[ ] Tested by Brandon.
[ ] Tested by Brady.

Does the change impact or break the Docker build?

[ ] Yes
[x] No

If Yes: Has Docker been updated accordingly?

[ ] Yes
[ ] No

Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] New and existing unit tests pass locally with my changes
[ ] If attention is required by the developer such as updating the .env file, these requirements have been listed.

added the start of the get community unit tests

Since every user is in the Welcome community upon registering, maybe check that the Welcome community is in the 200 response body?

Since every user is in the Welcome community upon registering, maybe check that the Welcome community is in the 200 response body?

Great suggestion.


Deleting Documents & Multi-Tenancy

Is it possible to explicitly specify tenant id when a document is being deleted?
I found how to query documents from all tenants (Where(i => i.AnyTenant()))
It is also possible to store document explicitly specifying tenant id (session.Store with tenantId parameter)
I just can't figure out how to delete a document if I have a session not bound to a tenant.
I tried DeleteWhere<>(i => i.AnyTenant() && i.Id == me.Id) but it does not seem to be working. Did I miss anything or the only option would be to create a new session for a specific tenant and delete from there?

We'll need this for #952 as well. The IDocumentSession needs overloads of Store(), Insert(), Update(), and DeleteWhere that allows you to specify a tenant id

Basically done in a branch.


rollItemMacro has been deprecated in dnd5e 2.2

**I have disabled all other modules: **True
**Module(s) **Combat-Booster
**Conflicting Module(s) **
**Foundry and System version **v10, v11
**OS, Hosting, Browser (if applicable) **
**Short description of bug **rollItemMacro has been deprecated in dnd5e 2.2
**Simple steps to reproduce the bug **
dnd5e: https://github.com/foundryvtt/dnd5e/pull/1655/files
The affected code: https://github.com/theripper93/Combat-Booster/blob/873493dd2254275cf826e663db42b7fcf0835119/scripts/CombatHud.js#L68
Screenshots and/or Console Errors

fixed


Dragging the element and drop on the same element, gives this error.

Most likely something wrong in your implementation. If you still have this problem, could you share some code to give a clue on what could be wrong?


allow running postgres on a diffrent port

@dmethvin-gov to use this you will need to run the following:

cd backend
Bring down the service by running docker-compose down
Wipe the db by running docker system prune && docker images prune && docker volumes prune
Run  docker-compose --env-file .env.development up db
Run  SR_DB_PORT=5433 gradle bootRun --args='--spring.profiles.active=dev'
view site at http://localhost:8080

I think the docker-compose changes are unnecessary.


Make unsafe_cleanup safe, get rid of unsafe_shutdown, initialize devices on-demand

There's no benefit to the shutdown flag, it's better to build new physical device objects on demand.
(Always shutdown, but don't make a fuss about it.)

We cannot make unsafe_cleanup safe, since typically there'll still be live contexts when it's called.


WrapQuery transform should support multiple selections in top-level selectionSet

Currently, the queryWrapper arg for WrapQuery is passed a SelectionSetNode and is expected to return a SelectionNode (well, the docs say any, but it gets added to the selections array here. See docs for WrapQuery here
I am proposing adding support for the query wrapper function to return either a SelectionNode or a SelectionSetNode. Only supporting SelectionNode is limiting because it means you can't expand the top level selection set of a query - i.e. only one level deep or deeper is supported. I'll provide a concrete example of what I want to accomplish to help with the explanation.
Here's a sample query taken from the testcases/docs demonstrating how it works today:
addressByUser(id: "user1") {
  streetAddress
  zip
}

Here's the associated resolver/WrapQuery usage for the addressByUser query:
            addressByUser(parent, { id }, context, info) {
              return delegateToSchema({
                schema: subSchema,
                operation: 'query',
                fieldName: 'userById',
                args: { id },
                context,
                info,
                transforms: [
                  // Wrap document takes a subtree as an AST node
                  new WrapQuery(
                    // path at which to apply wrapping and extracting
                    ['userById'],
                    (subtree: SelectionSetNode) => ({
                      // we create a wrapping AST Field
                      kind: Kind.FIELD,
                      name: {
                        kind: Kind.NAME,
                        // that field is `address`
                        value: 'address',
                      },
                      // Inside the field selection
                      selectionSet: subtree,
                    }),
                    // how to process the data result at path
                    result => result && result.address,
                  ),
                ],

And thus, the resulting downstream query looks like:
userById(id: "user1") {
  address {
    streetAddress
    zip
  }
}

Simple enough. However, imagine there were multiple fields at the top level. So, instead of userById.address.streetAddress and userById.address.zip, we had userById.addressStreetAddress and userById.addressZip. In this case, to support the same query, the downstream request would need to be changed to look something like:
userById(id: "user1") {
  addressStreetAddress
  addressZip
}

In a world where this is supported, the WrapQuery usage might look something like this:
            addressByUser(parent, { id }, context, info) {
              return delegateToSchema({
                schema: subSchema,
                operation: 'query',
                fieldName: 'userById',
                args: { id },
                context,
                info,
                transforms: [
                  new WrapQuery(
                    ['userById'],
                    (subtree: SelectionSetNode) => ({
                      kind: Kind.SELECTION_SET,
                      selectionSet: /* build selectionSet object, includes `addressStreetAddress` and `addressZip` selection/field nodes*/
                    }),
                    // how to process the data result at path
                    result => // ... do stuff with result,
                  ),
                ],
              });
            },
          },

This is a contrived example since the same could probably be accomplished with a couple of transforms/renames, but my usecase is a little more complex and this becomes a necessity. At least, I have yet to come up with a better alternative. This seems like a reasonable request.
I've made the change to graphql-tools locally and will put it up as a PR shortly. Let me know if you have any concerns with this approach.

Fixed in https://github.com/apollographql/graphql-tools/pull/902 - thanks!


no users.json

I am trying to follow the Basics and try out a table. I though that the users.json data would be available. I don't see it anywhere. I can create it, but it should be included.

You can find the users here...
https://github.com/tochoromero/vuejs-smart-table/blob/master/docs/.vuepress/components/data.json
Save it as users.json


Update KlasaConfig snippet to reflect Klasa PR #374

Description of the PR
Updating the config snippet to reflect changes added in Klasa PR #374
Changes Proposed in this Pull Request (List new items in CHANGELOG.MD)

configs -> settings

Semver Classification

[ ] This PR only includes documentation or non-code changes.
[x] This PR fixes a bug and does not change the (intended) framework interface.
[ ] This PR adds methods or properties to the framework interface.
[x] This PR removes or renames methods or properties in the framework interface.

Would you also mind updating Command, and potentially any other snippets effected by that pr?


DON-985: Fix friendly recaptcha verifier

Using 'json' option to guzzle to make it generate proper JSON request header, also telling it not to throw on HTTP error responses

Codecov Report
Attention: Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.

Project coverage is 69.61%. Comparing base (a5a0ca3) to head (a436350).

Files
Patch %
Lines

...Application/Middleware/FriendlyCaptchaVerifier.php
0.00%
6 Missing :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##             develop     #143      +/-   ##
=============================================
- Coverage      69.83%   69.61%   -0.23%
  Complexity       247      247
=============================================
  Files             39       39
  Lines            935      938       +3
=============================================
  Hits             653      653
- Misses           282      285       +3

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


Incompatibility pyjwt 2.0.0+ with djangorestframework-simplejwt <= 4.6.0

Hello, I only have time for a quick message and I could not pin the exact versions where the conflict starts. When upgrading pyjwt from version 1.7.1 to 2.0.0 and above, and the djangorestframework-simplejwt is version 4.6.0 (or below?), authentication will throw a 401 while executing the init of AccessToken in rest_framework_simplejwt.tokens.py

Please take a look at our CHANGELOG for PyJWT support. Due to their instability and not following SemVer, compatibility has been an issue. Utilizing SimpleJWT 4.7.0+ and PyJWT 2+ will work fine and using SimpleJWT 5.1.0+ and any PyJWT version will also work fine


ERROR - Recording error: local variable 'stats_shown' referenced before assignment

I keep getting this error. How can I fix this?

I haven't seen this error before. However it looks like you're on Windows, and I haven't tested the script on Windows yet. It's on the TODO list.
If you find a solution for this or any other Windows-related issues, a pull request would be much appreciated.

i was running into this error too, very easily reproducible if you just clone my #7 branch and try to run it. opened #6 which fixes it

should be fixed by 56988bc


VisualScript gets modified when it shouldn't

Godot version:
3.1.1
Issue description:
There are some instances where VisualScripts are modified (A star appears next to the file name and you have to save it again), even though they shouldn't.

Selecting functions
Canceling the base type selection
More stuff I will add soon

Steps to reproduce:
Create a VisualScript with two functions, save it and select a function.
Create a VisualScript and cancel the change the base type dialog

Also, Undo doesn't revert back the Visual Script to un-edited state.

The two cases mentioned seem fixed in 4.0, so closing.