Sucess : background green

Hello
First, excuse my bad english... :)
So... I want update one line and if it's a success, ... this line appear in green (3 or 4 seconds...).
Actually, it's red (error) or yellow (warning or success ??)..
Nothing in documentation can help me, my bad if it's explain...
So, how do I make this ? Thank you

Good morning,
Ok there was no answer... I just tweaked part of the Tabledit code by changing: warningClass: "warning" to warningClass: "success"
This is not ideal...


MemoryStore fails to read data involving persisted nested triples

Current Behavior
Trying to create a MemoryStore from a datafile containing a nested Triple fails.
Expected Behavior
A MemoryStore can be created from a datafile containing a nested Triple.
Steps To Reproduce
Create MemoryStore with persist=true.
Add a statement involving a nested Triple.
Shutdown MemoryStore.
Create MemoryStore from datafile.
Exception in thread "main" java.lang.ClassCastException: class org.eclipse.rdf4j.model.impl.SimpleTriple cannot be cast to class org.eclipse.rdf4j.sail.memory.model.MemResource (org.eclipse.rdf4j.model.impl.SimpleTriple and org.eclipse.rdf4j.sail.memory.model.MemResource are in unnamed module of loader 'app')
2024-01-03T13:28:27.689776800Z 	at org.eclipse.rdf4j.sail.memory.FileIO.readStatement(FileIO.java:256)
2024-01-03T13:28:27.689938600Z 	at org.eclipse.rdf4j.sail.memory.FileIO.read(FileIO.java:183)
2024-01-03T13:28:27.689956200Z 	at org.eclipse.rdf4j.sail.memory.MemoryStore.initializeInternal(MemoryStore.java:289)
2024-01-03T13:28:27.689972100Z 	at org.eclipse.rdf4j.sail.helpers.AbstractSail.init(AbstractSail.java:183)
2024-01-03T13:28:27.689990100Z 	at org.eclipse.rdf4j.repository.sail.SailRepository.initializeInternal(SailRepository.java:158)
Version
4.3.8
Are you interested in contributing a solution yourself?
None
Anything else?
The root cause of this is line
https://github.com/eclipse-rdf4j/rdf4j/blob/d8bdc75592e3e53938a8dc4354c76df194e751c1/core/sail/memory/src/main/java/org/eclipse/rdf4j/sail/memory/FileIO.java#L323
where SimpleValueFactory is used to convert an encoded triple IRI to a nested Triple. This will then cause a class cast exception on line
https://github.com/eclipse-rdf4j/rdf4j/blob/d8bdc75592e3e53938a8dc4354c76df194e751c1/core/sail/memory/src/main/java/org/eclipse/rdf4j/sail/memory/FileIO.java#L256
RDFStarUtil should contain methods that take the ValueFactory to use so that the MemoryStore can pass in its ValueFactory.

@pulquero Thanks for figuring out this bug! It should be fixed in 4.3.9.
Btw. I noticed that you don't have a name in your Github profile. We like to credit people for bug reports and fixes in the release notes on rdf4j.org, if you add a name to your Github profile then we will use that when we credit you in the release notes.


Support PubSub handle type

Support PubSub handle type

Support PubSub handle type

great abstraction👍

Improved configuration information @gitsrc

After merging, I want to build a tag version for standard version dependencies


Change font in history page to Roboto

Purpose

The purpose of this PR is to fix #254
Goals

Changing the fonts in history page to "Roboto".
Approach

I made a "section" tag in history/index.html file and inside it I put a "class" as "HistoryPageParagraph". After that, I went to the assets/css/custom.css and put the class in the bottom in "for History Page" comment and I put the "font-family: roboto;" in that class.
Screenshots

Preview Link
Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[ ] I have read and understood the development best practices guidelines
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Related PRs

Test environment

Learning

What is my problem ?


"Not authorized" error after adding user to collaborators

I added a collaborator to a project but when accessing the project's URL, he is getting a "Not authorized" error page. The collaborator can succesfuly login in Strider.

Setting the user as an admin fixes the issue though this is not idea.

The collaboration roles need to be straightened out. There's a related issue floating around.

Yep seems to be a duplicate of: https://github.com/Strider-CD/strider/issues/750 , closing.


refactor: liquidation logic

Security Checklist

[ ] 1. Re-Entrancy
[ ] 2. Arithmetic Over/Under Flows
[ ] 3. Unexpected Ether
[ ] 4. Delegatecall
[ ] 5. Default Visibilities
[ ] 6. Entropy Illusion
[ ] 7. External Contract Referencing
[ ] 8. Short Address/Parameter Attack (off chain)
[ ] 9. Unchecked CALL Return Values
[ ] 10. Race Conditions / Front Running
[ ] 11. Denial Of Service (DOS)
[ ] 12. Block Timestamp Manipulation
[ ] 13. Constructors with Care
[ ] 14. Uninitialized Storage Pointers
[ ] 15. Floating Points and Precision
[ ] 16. Tx.Origin Authentication
[ ] 17. Address.isContract Re-Entrancy via Constructor

⚠ NOTES ⚠
Make sure to think about each of these exploits in this PR.

mainly follow items in improve list
```

liquidationAsset vs debtAsset, liquidationAssetReserve vs debtReserve
a. if we really want to allow non-borrowed asset for liquidation, we should always use liquidationAsset instead of debtAsset OR debtReserve

baseCollateral naming is very confusing, we can remove it and keep only maxCollateralToLiquidate

collateralAmount naming is very confusing, can it be renamed as actualCollateralToLiquidate

collateralDiscountedPrice is very confusing, can it be renamed as
actualLiquidationAmount

erc721 liquidation shouldn’t read decimals ⇒ to keep consistency because other places we didn’t use

doesn’t respect CEI(check effects interaction)

for item 1 not change yet , for me both are ok  but prefer `debtAsset` from Aave a little bit more easy to understand than `liquidationAsset` , but I'm ok if we all agree to change @WalidOfNow @GopherJ

@yrong the issue is that we support liquidation using non-borrowed assets

@yrong the issue is that we support liquidation using non-borrowed assets

@GopherJ so you mean in some cases debt asset to be in liquidation may not borrowed directly by the user, so better to use liquidationAsset to replace, right?


guzzlehttp/psr7 v2.0 API change breaks part of the library

Hello,
With the new PSR7 library released a few days ago, some API has changed and it broke the StreamCommand that I was using. Is there any plan to upgrade the API in order to support the latest version of PSR7?
For your reference
https://github.com/guzzle/psr7/blob/c0dcda9f54d145bd4d062a6d15f54931a67732f9/README.md#upgrading-from-function-api
Thanks

Using version ^2.5 for intervention/image
./composer.json has been updated
Running composer update intervention/image
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - intervention/image[2.5.0, ..., 2.5.1] require guzzlehttp/psr7 ~1.1 -> found guzzlehttp/psr7[1.1.0, ..., 1.x-dev] but the package is fixed to 2.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - Root composer.json requires intervention/image ^2.5 -> satisfiable by intervention/image[2.5.0, 2.5.1].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

I'm facing issues with guzzlehttp/psr7 on a new Laravel project. Related?

I think this will fix it #1094

For those who face this issue as well when running composer require intervention/image on a Laravel 8 install.
Run:
composer require intervention/image:"master"
This will get the master branch with fix indicated above in #1094

I think this will fix it #1094

why not draft a new released

There are 2 issues here. Updating the dependency to ^2.0 will solve @bilogic's issue
In my case, I get an error saying the stream_for() function doesn't exist.
For example, if you inspect StreamCommand.php
You'll see this:
$this->setOutput(\GuzzleHttp\Psr7\stream_for(
    $image->encode($format, $quality)->getEncoded()
));

That's because it has been replaced with Utils::streamFor in v2.0.
Switching to this works but I am sure it'll break the package for people not using the latest version.
$this->setOutput(\GuzzleHttp\Psr7\Utils::streamFor(
    $image->encode($format, $quality)->getEncoded()
));

run
composer require intervention/image -w

@Cynically my apologies if I hijacked your issue. To others, my issue has since been resolved with the use of composer require intervention/image -W. There might be other solutions, but this was what worked for me. Thank you.

This issue is preventing users from uploading avatars in the Flarum software when they make a new installation or update all their dependencies since it automatically makes the PSR7 package jump to ^2.0 and cause the stream_for error https://github.com/flarum/core/issues/2966
We are currently suggesting users require version ^1.1 of PSR7 package manually as a workaround, but a fix here would be appreciated.

Facing this issue in my application as well. Image uploads are broken now. Laravel throws the following error:
Call to undefined function GuzzleHttp\Psr7\stream_for()


publish<EMAIL_ADDRESS>

Requested by: @flub
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Targets

[ ] crates
[ ] pypi
[ ] github

This is missing a proper changelog


Zen Mode Maximize

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.84.0 (d037ac076cee195194f93ce6fe2bdfe2969cc82d)
OS Version: Linux Mint 21.2 (5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux)

Issue Description
When creating two groups, enabling Zen Mode (ctrl+k z), and maximizing the group (ctrl+k ctrl+m), I observed that the active group is not centered but left margin placed. This behavior is not as expected.
Environment

VS Code Version: 1.84.0 (d037ac076cee195194f93ce6fe2bdfe2969cc82d)
OS Version: Linux Mint 21.2 (5.15.0-88-generic #98-Ubuntu SMP Mon Oct 2 15:18:56 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux)

Steps to Reproduce

Open VS Code and create two groups.
Toggle on Zen Mode using ctrl+k z.
Maximize the group using ctrl+k ctrl+m.

Actual Behavior
The active group is left margin placed, as shown in the provided image:

Expected Behavior
The active group should be centered, as shown in the expected image:

https://github.com/microsoft/vscode/blob/f713a2942254ad0698ab30e280946776a997d5e7/src/vs/workbench/browser/layout.ts#L1601-L1604
@bpasero we look at the number of groups on the editor group service and in this case I believe we need to know if a single editor group is maximized, but I only see an event on the service, no property to read. how should we read this info?

https://github.com/microsoft/vscode/blob/f713a2942254ad0698ab30e280946776a997d5e7/src/vs/workbench/browser/layout.ts#L1601-L1604
@bpasero we look at the number of groups on the editor group service and in this case I believe we need to know if a single editor group is maximized, but I only see an event on the service, no property to read. how should we read this info?

I bad understand how vscode work, but i found in editor.contribution.ts:
MenuRegistry.appendMenuItem(MenuId.EditorTitle, { command: { id: TOGGLE_MAXIMIZE_EDITOR_GROUP, title: localize('maximizeGroup', "Maximize Group") }, group: '8_group_operations', order: 5, when: ContextKeyExpr.and(EditorPartMaximizedEditorGroupContext.negate(), EditorPartMultipleEditorGroupsContext) });
MenuRegistry.appendMenuItem(MenuId.EditorTitle, { command: { id: TOGGLE_MAXIMIZE_EDITOR_GROUP, title: localize('unmaximizeGroup', "Unmaximize Group") }, group: '8_group_operations', order: 5, when: EditorPartMaximizedEditorGroupContext });

Also in contextkeys.ts:
// Editor Part Context Keys
export const EditorPartMultipleEditorGroupsContext = new RawContextKey<boolean>('editorPartMultipleEditorGroups', false, localize('editorPartMultipleEditorGroups', "Whether there are multiple editor groups opened in an editor part"));
export const EditorPartSingleEditorGroupsContext = EditorPartMultipleEditorGroupsContext.toNegated();
export const EditorPartMaximizedEditorGroupContext = new RawContextKey<boolean>('editorPartMaximizedEditorGroup', false, localize('editorPartEditorGroupMaximized', "Editor Part has a maximized group"));
export const IsAuxiliaryEditorPartContext = new RawContextKey<boolean>('isAuxiliaryEditorPart', false, localize('isAuxiliaryEditorPart', "Editor Part is in an auxiliary window"));

Can it help?

We did not expose if the editor part was maximized or not before as it wasn't used anywhere, but it makes sense to expose it for this. Created the PR #201229 to support centered layout with maximized groups

verification steps:

Open a single editors (groups)
Run workbench.action.toggleCenteredLayout
Open a second editor (group) to the side => As there are more then 2 groups, centred layout is not applied
Run workbench.action.toggleMaximizeEditorGroup => Only one group is visible and centred layout is applied

Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting \closedWith someCommitSha, or directly add the insiders-released label if you know this has already been releaased


Failed to install DPythonModular on Ubuntu 14.04 with shogun-4.1.0

i have Ubuntu 14.04
swig 2.0.11
python 2.7.6
numpy 1:1.8.1
gcc 4.8.2
i ran cmake .. -DPythonModular=On -DPYTHON_INCLUDE_DIR=/usr/include/python2.7 -DPYTHON_LIBRARY=/usr/lib/python2.7/config/libpython2.7.so
then i ran make
[  0%] Generating /root/shogun-4.1.0/src/shogun/base/class_list.cpp
[  0%] Built target class_list
[  1%] Generating version header
[  1%] Built target version
Scanning dependencies of target libshogun
[  1%] Building CXX object src/shogun/CMakeFiles/libshogun.dir/base/class_list.cpp.o
[ 86%] Built target libshogun
Linking CXX shared library libshogun.so
[ 86%] Built target shogun
[ 86%] copying SWIG files
[ 86%] Built target python_modular_src
[ 86%] Building CXX object src/interfaces/python_modular/CMakeFiles/_python_modular.dir/modshogunPYTHON_wrap.cxx.o
/root/shogun-4.1.0/build/src/interfaces/python_modular/modshogunPYTHON_wrap.cxx:155:21: fatal error: Python.h: No such file or directory
include <Python.h>
                 ^

compilation terminated.
make[2]: *** [src/interfaces/python_modular/CMakeFiles/_python_modular.dir/modshogunPYTHON_wrap.cxx.o] Error 1
make[1]: *** [src/interfaces/python_modular/CMakeFiles/_python_modular.dir/all] Error 2
make: *** [all] Error 2

oh this is rather interesting! could you please provide the full cmake output as well (when you ran it the first time). thnks

i follow this https://github.com/shogun-toolbox/shogun/wiki/QUICKSTART
$ cd "$HOME/shogun-4.1.0"
$ mkdir build
$ cd build
$ cmake -DCMAKE_INSTALL_PREFIX="$HOME/shogun-install" ..
$ make -j5 all
$ make install

wait i thought you ran:
cmake .. -DPythonModular=On -DPYTHON_INCLUDE_DIR=/usr/include/python2.7 -DPYTHON_LIBRARY=/usr/lib/python2.7/config/libpython2.7.so (see your first message).
but anyhow i would need the full output of what you get on your screen after running cmake.

oh i see like this？
root@cory-virtual-machine:~/shogun-4.1.0/build# cmake .. -DPythonModular=On -DPYTHON_INCLUDE_DIR=/usr/include/python2.7 -DPYTHON_LIBRARY=/usr/lib/python2.7/config/libpython2.7.so
-- Using system's malloc
-- Could NOT find MOSEK (missing:  MOSEK_DIR MOSEK_INCLUDE_DIR MOSEK_LIBRARY)
-- A library with BLAS API found.
-- A library with LAPACK API found.
-- Could NOT find GLPK (missing:  GLPK_LIBRARY GLPK_INCLUDE_DIR GLPK_PROPER_VERSION_FOUND)
-- Could NOT find CPLEX (missing:  CPLEX_LIBRARY CPLEX_INCLUDE_DIR)
-- Could NOT find Eigen3 (missing:  EIGEN_INCLUDE_DIR) (Required is at least version "3.1.2")
-- Could NOT find OPENCL (missing:  OPENCL_LIBRARY OPENCL_INCLUDE_DIR)
-- Could NOT find ViennaCL (missing:  VIENNACL_INCLUDE_DIR OPENCL_INCLUDE_DIRS OPENCL_LIBRARIES) (Required is at least version "1.5.0")
-- checking for one of the modules 'libColPack>=1.0.9;ColPack>=1.0.9'
-- Could NOT find NLOPT (missing:  NLOPT_LIBRARY NLOPT_INCLUDE_DIR)
-- Could NOT find LPSOLVE (missing:  LPSOLVE_LIBRARIES LPSOLVE_INCLUDE_DIR)
-- Could NOT find ColPack (missing:  COLPACK_LIBRARIES COLPACK_LIBRARY_DIR COLPACK_INCLUDE_DIR)
-- Could NOT find ARPREC (missing:  ARPREC_LIBRARIES ARPREC_INCLUDE_DIR)
-- Could NOT find Doxygen (missing:  DOXYGEN_EXECUTABLE) (Required is at least version "1.8.6")
-- checking for one of the modules 'libjson>=0.11;json>=0.11;json-c>=0.11'
-- Could NOT find HDF5 (missing:  HDF5_LIBRARIES HDF5_INCLUDE_DIRS)
-- Could NOT find CURL (missing:  CURL_LIBRARY CURL_INCLUDE_DIR)
-- Could NOT find BZip2 (missing:  BZIP2_LIBRARIES BZIP2_INCLUDE_DIR)
-- Could NOT find LibLZMA (missing:  LIBLZMA_INCLUDE_DIR LIBLZMA_LIBRARY LIBLZMA_HAS_AUTO_DECODER LIBLZMA_HAS_EASY_ENCODER LIBLZMA_HAS_LZMA_PRESET)
-- Could NOT find SNAPPY (missing:  SNAPPY_LIBRARIES SNAPPY_INCLUDE_DIR)
-- Lzo includes and libraries NOT found.
-- Spinlock support found
-- Could NOT find PROTOBUF (missing:  PROTOBUF_LIBRARY PROTOBUF_INCLUDE_DIR)
-- Supported backend(s) for linear algebra NOT FOUND/NOT ENABLED
-- ===================================================================================================================
-- Summary of Configuration Variables
-- The following OPTIONAL packages have been found:

CCache
GDB
OpenMP
BLAS
LAPACK
Atlas
LibXml2
ZLIB
Spinlock
Threads

-- The following REQUIRED packages have been found:

SWIG (required version >= 2.0.4)
PythonLibs
PythonInterp
NumPy

-- The following OPTIONAL packages have not been found:

Mosek
GLPK
CPLEX
ARPACK
Eigen3 (required version >= 3.1.2)
ViennaCL (required version >= 1.5.0)
NLopt
LpSolve
ColPack
ARPREC
Doxygen (required version >= 1.8.6)
HDF5
CURL
BZip2
LibLZMA
SNAPPY
LZO
Protobuf

-- The following REQUIRED packages have not been found:

OpenCL

-- ===================================================================================================================
-- Enabled Integration
--   OpenCV Integration is OFF 	 - enable with -DOpenCV=ON
-- ===================================================================================================================
-- Enabled Interfaces
--   libshogun is ON
--   python modular is ON
--   octave modular is OFF 	 - enable with -DOctaveModular=ON
--   java modular is OFF 	 - enable with -DJavaModular=ON
--   perl modular is OFF 	 - enable with -DPerlModular=ON
--   ruby modular is OFF 	 - enable with -DRubyModular=ON
--   csharp modular is OFF 	 - enable with -DCSharpModular=ON
--   R modular is OFF 		 - enable with -DRModular=ON
--   lua modular is OFF 	 - enable with -DLuaModular=ON
-- Enabled legacy interfaces
--   cmdline static is OFF 	 - enable with -DCmdLineStatic=ON
--   python static is OFF 	 - enable with -DPythonStatic=ON
--   octave static is OFF 	 - enable with -DOctaveStatic=ON
--   matlab static is OFF 	 - enable with -DMatlabStatic=ON
--   R static is OFF 		 - enable with -DRStatic=ON
-- ===================================================================================================================
-- To compile shogun type
--   make
-- To install shogun to /root/shogun-install type
--   make install
-- or to install to a custom directory
--   make install DESTDIR=/my/special/path
--   (or rerun cmake with -DCMAKE_INSTALL_PREFIX=/my/special/path) to just change the prefix
-- ===================================================================================================================
-- Configuring done
-- Generating done
-- Build files have been written to: /root/shogun-4.1.0/build

yep this is the one!
i suppose you are using all the default packages of ubuntu. in that case could you please just do the following:
rm -rf build
mkdir build
cmake -DPythonModular=ON ..

ok i did,but i have error:

root@cory-virtual-machine:~/shogun-4.1.0# cmake -DPythonModular=ON ..
CMake Error: The source directory "/root" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
root@cory-virtual-machine:~/shogun-4.1.0# cd build
root@cory-virtual-machine:~/shogun-4.1.0/build# cmake -DPythonModular=ON ..
-- The C compiler identification is GNU 4.8.4
-- The CXX compiler identification is GNU 4.8.4
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found CCache: /usr/bin/ccache
-- Found SWIG: /usr/bin/swig2.0 (found suitable version "2.0.11", minimum required is "2.0.4")
-- Performing Test HAS_CXX11_FLAG
-- Performing Test HAS_CXX11_FLAG - Success
-- Checking C++11 support for "func"
-- Checking C++11 support for "func": works
-- Checking C++11 support for "atomic"
-- Checking C++11 support for "atomic": works
-- Checking C++11 support for "auto"
-- Checking C++11 support for "auto": works
-- Checking C++11 support for "auto_ret_type"
-- Checking C++11 support for "auto_ret_type": works
-- Checking C++11 support for "class_override_final"
-- Checking C++11 support for "class_override_final": not supported
-- Checking C++11 support for "constexpr"
-- Checking C++11 support for "constexpr": works
-- Checking C++11 support for "cstdint"
-- Checking C++11 support for "cstdint": works
-- Checking C++11 support for "decltype"
-- Checking C++11 support for "decltype": works
-- Checking C++11 support for "initializer_list"
-- Checking C++11 support for "initializer_list": works
-- Checking C++11 support for "lambda"
-- Checking C++11 support for "lambda": works
-- Checking C++11 support for "long_long"
-- Checking C++11 support for "long_long": works
-- Checking C++11 support for "nullptr"
-- Checking C++11 support for "nullptr": works
-- Checking C++11 support for "regex"
-- Checking C++11 support for "regex": not supported
-- Checking C++11 support for "rvalue-references"
-- Checking C++11 support for "rvalue-references": works
-- Checking C++11 support for "sizeof_member"
-- Checking C++11 support for "sizeof_member": works
-- Checking C++11 support for "static_assert"
-- Checking C++11 support for "static_assert": works
-- Checking C++11 support for "variadic_templates"
-- Checking C++11 support for "variadic_templates": works
-- Looking for C++ include unordered_map
-- Looking for C++ include unordered_map - found
-- Using system's malloc
-- Looking for isfinite
-- Looking for isfinite - not found
-- Looking for isinf
-- Looking for isinf - found
-- Looking for isnan
-- Looking for isnan - found
-- Looking for signgam
-- Looking for signgam - found
-- Looking for fdopen
-- Looking for fdopen - found
-- Looking for log2
-- Looking for log2 - found
-- Looking for powl
-- Looking for powl - found
-- Looking for lgammal
-- Looking for lgammal - found
-- Looking for sqrtl
-- Looking for sqrtl - found
-- Looking for finite
-- Looking for finite - found
-- Looking for isfinite
-- Looking for isfinite - not found
-- Looking for isinf
-- Looking for isinf - found
-- Looking for isnan
-- Looking for isnan - found
-- Performing Test HAVE_STD_ISINF
-- Performing Test HAVE_STD_ISINF - Success
-- Performing Test HAVE_STD_ISFINITE
-- Performing Test HAVE_STD_ISFINITE - Success
-- Performing Test HAVE_STD_ISNAN
-- Performing Test HAVE_STD_ISNAN - Success
-- Looking for xmmintrin.h
-- Looking for xmmintrin.h - found
-- Looking for emmintrin.h
-- Looking for emmintrin.h - found
-- Looking for arc4random
-- Looking for arc4random - not found
-- Found GDB: /usr/bin/gdb
-- Could NOT find MOSEK (missing:  MOSEK_DIR MOSEK_INCLUDE_DIR MOSEK_LIBRARY)
-- Looking for include file pthread.h
-- Looking for include file pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Try OpenMP C flag = [-fopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Success
-- Try OpenMP CXX flag = [-fopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Success
-- Found OpenMP: -fopenmp
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.26")
-- Looking for dgemm
-- Looking for dgemm - found
-- A library with BLAS API found.
-- Looking for cheev_
-- Looking for cheev_ - found
-- A library with LAPACK API found.
-- Looking for clapack_dpotrf in /usr/lib/atlas-base/liblapack_atlas.so.3
-- Looking for clapack_dpotrf in /usr/lib/atlas-base/liblapack_atlas.so.3 - found
-- Found ATLAS: /usr/lib/atlas-base/liblapack_atlas.so.3;/usr/lib/atlas-base/libcblas.so.3;/usr/lib/atlas-base/libf77blas.so.3;/usr/lib/atlas-base/libatlas.so.3;/usr/lib/liblapack.so.3
-- Could NOT find GLPK (missing:  GLPK_LIBRARY GLPK_INCLUDE_DIR GLPK_PROPER_VERSION_FOUND)
-- Could NOT find CPLEX (missing:  CPLEX_LIBRARY CPLEX_INCLUDE_DIR)
-- Could NOT find Eigen3 (missing:  EIGEN_INCLUDE_DIR) (Required is at least version "3.1.2")
-- Could NOT find OPENCL (missing:  OPENCL_LIBRARY OPENCL_INCLUDE_DIR)
-- Could NOT find ViennaCL (missing:  VIENNACL_INCLUDE_DIR OPENCL_INCLUDE_DIRS OPENCL_LIBRARIES) (Required is at least version "1.5.0")
-- checking for one of the modules 'libColPack>=1.0.9;ColPack>=1.0.9'
-- Could NOT find NLOPT (missing:  NLOPT_LIBRARY NLOPT_INCLUDE_DIR)
-- Could NOT find LPSOLVE (missing:  LPSOLVE_LIBRARIES LPSOLVE_INCLUDE_DIR)
-- Could NOT find ColPack (missing:  COLPACK_LIBRARIES COLPACK_LIBRARY_DIR COLPACK_INCLUDE_DIR)
-- Could NOT find ARPREC (missing:  ARPREC_LIBRARIES ARPREC_INCLUDE_DIR)
-- Could NOT find Doxygen (missing:  DOXYGEN_EXECUTABLE) (Required is at least version "1.8.6")
-- Found PythonInterp: /usr/bin/python (found version "2.7.6")
-- checking for one of the modules 'libjson>=0.11;json>=0.11;json-c>=0.11'
-- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.1")
-- Could NOT find HDF5 (missing:  HDF5_LIBRARIES HDF5_INCLUDE_DIRS)
-- Could NOT find CURL (missing:  CURL_LIBRARY CURL_INCLUDE_DIR)
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.8")
-- Could NOT find BZip2 (missing:  BZIP2_LIBRARIES BZIP2_INCLUDE_DIR)
-- Could NOT find LibLZMA (missing:  LIBLZMA_INCLUDE_DIR LIBLZMA_LIBRARY LIBLZMA_HAS_AUTO_DECODER LIBLZMA_HAS_EASY_ENCODER LIBLZMA_HAS_LZMA_PRESET)
-- Could NOT find SNAPPY (missing:  SNAPPY_LIBRARIES SNAPPY_INCLUDE_DIR)
-- Lzo includes and libraries NOT found.
-- Spinlock support found
-- Could NOT find PROTOBUF (missing:  PROTOBUF_LIBRARY PROTOBUF_INCLUDE_DIR)
-- Supported backend(s) for linear algebra NOT FOUND/NOT ENABLED
CMake Error at /usr/local/share/cmake-3.2/Modules/FindPackageHandleStandardArgs.cmake:138 (message):
Could NOT find PythonLibs (missing: PYTHON_LIBRARIES PYTHON_INCLUDE_DIRS)
Call Stack (most recent call first):
/usr/local/share/cmake-3.2/Modules/FindPackageHandleStandardArgs.cmake:374 (_FPHSA_FAILURE_MESSAGE)
cmake/FindPythonLibs.cmake:190 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:904 (FIND_PACKAGE)
-- Configuring incomplete, errors occurred!
See also "/root/shogun-4.1.0/build/CMakeFiles/CMakeOutput.log".
See also "/root/shogun-4.1.0/build/CMakeFiles/CMakeError.log".

@Corllll oh ok great! lemme look into it and get back to...

＠vigsterkr thanks to your help,and answer quickly.

Check your python setup

@karlnapf  what's your mean?

@vigsterkr @karlnapf ok i got that thanks.

Ill close this for now. If any problems, let us know!


Verify Container Registry Move

Motivation
With the new release kubernetes moved the container registry service from k8s.gcr.io to registry.k8s.io (see here). We have to make sure, that this is already done on our side and we won't have any negative effects upgrading.
Todo

[x]  Verify that we already use the correct registry or are at least prepared to do so after the upgrade
[x] Document what to do, if there is still a todo throughout the upgrade process

Outcome

We are confident in the upgrade not breaking our running kubernetes environments.

technical hints

Biggest effort should be around retagger
Search through the repositories if we use k8s.gcr.io still somewhere
Prometheus has a metric for registries

I think we're good, I mostly checked the repos and created some PR's where I think we could do a small change 🙂.
According to the metrics in Prometheus, we should be also good.
Closing it for now.


Building Graph: std::bad_alloc

I'm trying to run your code using another dataset tokenized/bin as in your CNN/DM repo.
I'm running it using 32Go RAM & Nvidia 1080.
It looks memory related so I tried to set small values for some parameters and still got the issue.
## Command
python run_summarization.py --mode train --data_path ./data/train.bin --vocab_path ./data/vocab  --log_root ./ --exp_name cnndm_summ --batch_size 4 --vocab_size 25000 --max_enc_steps 200 --max_dec_steps 100
## Output
[...]
INFO:tensorflow:Adding attention_decoder timestep 80 of 100
INFO:tensorflow:Adding attention_decoder timestep 81 of 100
INFO:tensorflow:Adding attention_decoder timestep 82 of 100
INFO:tensorflow:Adding attention_decoder timestep 83 of 100
INFO:tensorflow:Adding attention_decoder timestep 84 of 100
INFO:tensorflow:Adding attention_decoder timestep 85 of 100
INFO:tensorflow:Adding attention_decoder timestep 86 of 100
INFO:tensorflow:Adding attention_decoder timestep 87 of 100
INFO:tensorflow:Adding attention_decoder timestep 88 of 100
INFO:tensorflow:Adding attention_decoder timestep 89 of 100
INFO:tensorflow:Adding attention_decoder timestep 90 of 100
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
max_size of vocab was specified as 25000; we now have 25000 words. Stopping reading.
Finished constructing vocabulary of 25000 total words. Last word added: pencils
creating model...
Writing word embedding metadata file to ./cnndm_summ/train/vocab_metadata.tsv...

If you have any clue/advice
Thx for releasing the code, paper & blog post btw

Hi @pltrdy, I've never seen this std::bad_alloc error before. After googling the error, the advice does seem memory related. Sorry not be of more help!

The issue was on my side (the dataset).
Closing the issue. thx for fast answer tho.

@pltrdy Hi! I have the same problem. Could you please tell me what was the cause in your case?


License??

What is the licensing model of the project??

The nuget page says MIT. However, it would be great if there would be a LICENSE file in the repo, too.

Could you please add the license to the repo ?
Otherwise, Great work, thanks.

The license has been added to the repo


Invalid Syntax

Getting this error on running !python setup.py develop in jupyter notebook. How to resolve this ?
File "setup.py", line 62
VERSION_INFO = ', '.join([x if x.isdigit() else f'"{x}"' for x in SHORT_VERSION.split('.')])
^
SyntaxError: invalid syntax

Hi, probably you have an old version of python. Try upgrading to the latest version of python or use !python3 setup.py develop. F-string literals have been added to python since python 3.6


refactor(typescript): upgrade to TS 4.1, simplify and generalize types

What
Upgrades to the latest version of TypeScript: 4.1. I think this will be breaking changes. I mean it isn't a change to the code, but the TS updates might require some slight modifications to user code if they were using the ParametricSelector or Selector types directly.
Changes

types no longer suffer "death from a thousand overloads"
createSelector can accept any number of selectors

the limit is only in the depth of recursion TS allows, which is 50 levels as of now
why this arbitrary number? I dunno ask the TS guys

removed ParametricSelector as the base Selector type is now smart enough to "encompass" this role

CI/Build Chores

updated Travis targets to still maintained versions of node
fixed broken build scripts
updated TypeScript testing strategy to use https://github.com/microsoft/dtslint

created /types folder and moved tests there
added symlink to test folder (easiest way to setup new test)

Wow, thanks for putting this together!
The biggest issue atm is that @ellbee , the primary maintainer for Reselect, has been mostly inactive for a while.  Tim Dorr and I have commit rights to the repo as owners of the reduxjs GH org, but we don't have publish rights on NPM.  So, even if we merge this, we don't currently have a way to publish a new build.
I'm going to try reaching out to @ellbee and seeing if we can get added as publishers.

Wow, thanks for putting this together!
The biggest issue atm is that @ellbee , the primary maintainer for Reselect, has been mostly inactive for a while.  Tim Dorr and I have commit rights to the repo as owners of the reduxjs GH org, but we don't have publish rights on NPM.  So, even if we merge this, we don't currently have a way to publish a new build.
I'm going to try reaching out to @ellbee and seeing if we can get added as publishers.

As for backwards compatibility: I'd suggest keeping existing types with their names as they are and deprecating them.
In addition to that, I'd keep the old type definition in a second file and use typesVersions to have TS choose the new one only for TS >=4.1

I'm embarrassed to admit that I had no idea that could be done. I've never written package typings before so that thought never crossed my mind. I will absolutely do this though!

As for backwards compatibility: I'd suggest keeping existing types with their names as they are and deprecating them.
In addition to that, I'd keep the old type definition in a second file and use typesVersions to have TS choose the new one only for TS >=4.1

I'm embarrassed to admit that I had no idea that could be done. I've never written package typings before so that thought never crossed my mind. I will absolutely do this though!

Just as an update, I plan to get around to updating this with the suggestions this weekend. I'm sorry I didn't reply/update this sooner, it's been a busy week at work.
I am very thankful for the reviews though. I also plan to answer those and make corrections in my code as soon as I am able.

Hey, wanted to follow up on this.
I'd like to split the work in this PR into a couple different PRs if at all possible.
First, per #482 , I definitely want to modernize the CI setup, including switching from TravisCI to Github Actions and dropping old versions of Node.  However, I think that should be its own PR.
From there, yes, I do want to update any dependencies and actual TS typings.
Not sure if it'd be easier to close this PR and then create two new ones?

Also: my other concern atm is that it looks like some of the changes in here are probably enough to justify a Reselect 5.0 release.  However, if we do a 5.0, it seems like there are also a number of other functionality changes that should be considered as well, such as #401 , and even rewriting the code itself in TS.
Meanwhile, there's open PRs like #465 , which seems small but useful, and could be put out in a new 4.x release.
Given that, can we figure out a way to scope the changes so that we can have a 4.x release soon with some additional bits of cleanup, and then do a larger effort to work towards a 5.x?

Given that, can we figure out a way to scope the changes so that we can have a 4.x release soon with some additional bits of cleanup, and then do a larger effort to work towards a 5.x?

Sure. I really like that idea. We can do a 4.x PR that is only non-breaking upgrades. A non-exhaustive list:

CI upgrade from Travis -> GHA
#465
...whatever else looks good to pull into a 4.x release.

Then I can start a 5.0 release w/:

the 4.1 type updates I did here
some incarnation of #401?

I would love to include #401 (well some variant of it) in the 5.0 release PR, but I'm not sure there is a consensus on the names for the new API. I have read through all the posts and related issues (that took a while BTW 😆) and think it's a great idea. I'm of the opinion it shouldn't be called createKeySelector (which I think @josepot agrees with). It should still behave the same as the idea you proposed and will allow for things like shared selectors. Heck, it might even enable things with can't think of right now. I really like that idea!
My personal opinion is that it should be called createDynamicSelector AND that it should still be able to accept the state. The "dynamic selector" moniker would just let people know that it won't be considered for caching purposes. This is a slightly less "leaky" way to name it. What do you think @josepot?
I have no problem making both of these PRs. Or I can contribute to them if you'd rather control that process. Just let me know.

@eXamadeus yep, sounds good. Let's do the build updates first. In fact, let's split this up into separate PRs for :

CI changes
Dependency updates
Any minor fixes we feel are appropriate for a 4.x release.

I think it's worth having a larger planning discussion around what 5.x should include. There's a bunch of open PRs that I could see conflicting. I think it's also important to analyze what weaknesses Reselect currently has and what use cases it doesn't convert well atm, and look at other alternatives in the ecosystem for comparison.
Related to all this, I've been looking at https://github.com/dai-shi/proxy-memoize as a possible better alternative to Reselect that we could start recommending.  Discussion thread for that topic is at https://github.com/reduxjs/react-redux/issues/1653.
However, I'm also interested in improving Reselect itself too. If we're going to do so, I want to have a plan laid out.
I'll try to create a discussion thread tonight or tomorrow.

@markerikson Sounds good, I'll have them up tonight or tomorrow (at least the CI one for sure).
Question about the dependency updates: which updates does reselect want to entertain? If we decided to just assume TS 3.9+ support we can drop the testing libraries completely. If that's the route we want to go, that's probably the easiest one. Also, do you want to do a generic upgrade of other dependencies while were at it? Or just remove the testing libraries and update to say 3.9+ is supported?
Either way, I can create the CI PR and a "minor fixes" PR that follows that w/ #465 in it.

Yeah, I still want to do this in phases.  There were several open "update deps" PRs I closed today.  Like, this is apparently still on Babel 6 (!).
I think we can certainly ignore TS < 3.5, and it's probably not unreasonable to go 3.9+.  Of course, as we just saw, 3.1+ appears to be an issue :)

I think we can certainly ignore TS < 3.5, and it's probably not unreasonable to go 3.9+. Of course, as we just saw, 3.1+ appears to be an issue :)

Yeah, it's only two of the tests that are broken (sort of). The actual library in production is already affected by this, so it's not like removing the tests would cause a breaking change. It's basically just acknowledging that the types work as expected for 2.9 and 3.0, but don't behave correctly for 3.1+. Maybe we should make a bug fix for that in 4.x?
The new typings for TS 4.1+ do actually work for this tested scenario, so the test is brought back for TS 4.1+. If you're alright with it, we can just make this PR only do the type upgrade to TS 3.9+ with no breaking changes (so we can keep this as reselect v4)? I am still planning to make that other PR that will be for the 5.0 release w/ TS 4.1+ typings.
Of course, both of these would require the work done in #483 to use the new CI changes. Let me know if you want me to repurpose this PR or create another one for the "reselect v4 type updates (TS 3.9+)".

Hah, I'm kinda getting lost on what's where now :)
Yeah, let's try things in this order:

Turn off the couple failing tests in the GH Actions PR, as the failing tests are not due to the GH Actions switch, and get that merged in
Update any other dependencies and build tooling
Figure out if there's a reasonable fix to the types that could be made in a 4.x release
Hold off on a larger rewrite of the types, because this will be affected by any noticeable changes to the API that might be involved in a v5

@eXamadeus: so, it turns out that this bug was already reported by @nickmccurdy two years ago :)
https://github.com/reduxjs/reselect/issues/420

Whoops sorry, I reviewed this without reading the discussion first. I'm now following the repo so if there are new PRs I should be able to review them. Let me know if any other help is needed.

Hey @nickmccurdy this is still the best one to review the type changes I suppose. But @markerikson brings up a good point that these type changes need to wait until a v5 release.
Here's a list of things I'm planning on doing now:

[ ] Turn off the couple failing tests in the GH Actions PR (#483), as the failing tests are not due to the GH Actions switch, and get that merged in
[ ] Retarget (recreate?) this PR to v5.0.0 branch. @markerikson I think these types will be best to get in before the API changes, since they should be:

easier to modify
shouldn't conflict with the changes suggested in #401
might actually help the changes in #401 be easier to implement

[ ] Figure out any type changes that can be in 4.x and make a PR for those. Ones that seem likely:

#465
Seeing if I can find a fix for #420

For the deps PRs, I can do those too. Looks like #461 and #381 look like good candidates there. I would think the babel upgrade (#381) should probably go first, then #461 can go on top of that. Would you like me to pull those together in a deps PR as well? Or is that something you guys want to do?

@eXamadeus Yep, please go ahead and do a deps PR as well if you have time.
I really appreciate your effort and contributions here!

I'm going to make issues to track the "bullet points" I made earlier and I'll edit the comment to link to them.

FYI, we do already have an "upgrade Babel" PR at #381 , which Andarist just rebased.  However, it now conflicts with the removal of the Travis file.
Not sure what the best option is for resolving that atm.

FYI, we do already have an "upgrade Babel" PR at #381 , which Andarist just rebased. However, it now conflicts with the removal of the Travis file.
Not sure what the best option is for resolving that atm.

I'll comment on that PR, but he just made the same "changes" we just made to the node versions essentially. It looks like just deleting the .travis.yml file in his PR will resolve the conflict and should "just work"™.

Good call! Just did that via the web UI and I see the GH actions kicking in now.

Whoops, I should have made a branch on my fork. When I updated my master branch it purged this PR of the code.
The latest commit here for reference is 66fcf9000bc173ca1f168656d2611e8448ecc188. You can see the changes, as they originally were, @ https://github.com/reduxjs/reselect/pull/487.


No exceptions are raised when there is a socket error

Hi,
While doing doing some more testing I've discovered something wrong about exception handling, look at this snippet that is trying to connect to a MongoDB server that is not actually running:
use BSON::Document;
use MongoDB::Client;
use MongoDB::Database;
use MongoDB::Collection;
# Native MongoDB driver
my MongoDB::Client $client;
my MongoDB::Database $db;
my MongoDB::Collection $col;

try {
  $client .= new(:uri("mongodb://<IP_ADDRESS>:27017"));
  $db = $client.database('Test');
  $col = $db.collection('test');
  CATCH {
    default {
      say "Mongo exception: ",.^name, '→ ', .Str;
    }
  }
}

No exception are raised , you get only log in MongoDB.log telling you that the server is down.
2024-07-12 07:20 UTC

39.881059 [E][7][Wire][121]: <IP_ADDRESS>:27017: Failed to resolve host name '<IP_ADDRESS>' with family 2.
Error: nodename nor servname provided, or not known
39.881729 [W][7][Monitor][422]: no response from server <IP_ADDRESS>:27017
39.883154 [I][7][Server][168]: Server status of <IP_ADDRESS>:27017 is ST-Unknown
39.889115 [I][7][Client][595]: Client '6F44E7DDB4DE902F8A6523F9DDB480ECA1137272' topology is TT-Single

So how can one detect a socket error in that case as there is no exception to catch ?

I don't know if that was according to the protocol of MongoDB, I'll have to look that up.

isn't it possible to catch Failed to resolve host name '<IP_ADDRESS>' with family 2. Error: nodename nor servname provided, or not known and similar network errors ?
I've tried to modified wire.rakumod to trigger a fatal-message but my main program is not getting the exception so maybe it's just an issue related to propagating the exception to the calling code ? One of the main use case would be detecting disconnection from socket pool and then trigger reconnection of the pool. As of now it seems to get stuck when you get "Not connected !" exception which seems to happen not very often but after a huge amount of request in a replicaset.

I haven't yet found the developer docs about a driver's behavior in case of unavailable servers.
There is, however, another way to find out if servers aren't running. There is the timeoutMS option. This one replaces several other options. The option has not yet been implemented in this driver, so I must implement it. I can imagine the behavior after the implemention being something like an empty doc returned with the ok field set to 0.


Need a proper cpp code to download the large file from S3 bucket

Hi,
I have tried the getobject.cpp code but in that i am not able to download the file. It just copy the contents from the file and display it on the terminal.
I have tried the demo code of transfer manager but its download is failing.
Please guide me in this how to proceed to download the any file from AWS S3 bucket using only cpp code.
Thanks in advance.

Hi @AkshayGawande1994 ,
So I'm closing this as it is not really SDK related but rather a C++ question of "how to save a stream as a file"... but basically you'd want to do something like:
Aws::String filename = "something.txt"
auto &retrieved_file = outcome.GetResult().GetBody();
    std::ofstream output_file(filename.c_str(), std::ios::out |std::ios::binary);
    output_file << retrieved_file.rdbuf();


Hashicorp Vault Integration

What happens?
We need to have the ability to pull secrets and inject them into the templating engine. We need to decide on what the best approach for this is.
What were you expecting to happen?
We determine a way to integrate Hashicorp Vault in a way that will allow adding other secrets management solutions in the future.

I'd like to understand this requirement better.
Is this like saying that some of the parameters are not coming from the parameter git repo, but actually from a secret store?
That would probably mean that we need to turn the parameter source into an array of potentially different sources. Also it escapes me how secrets will be merged with normal parameters and then used by the templating engine.

Yeah nobody said it's going to be easy to solve. ;-)
We need the ability to inject secrets from Hashicorp Vault, because that's the best place to store them. We can't put them in github.
I've been doing some research and it might be best to write a helm plugin, which does exactly that. This would allow for supporting different secret backends in the future and also make it independent from the eunomia code base.
A lot of the more advanced and flexible features might require us to restrict them to a templating engine that can support it. I'm right now thinking that helm is the answer for a lot of these problems. The variable hierarchy has a similar potential solution.

Please hold off on working on this item. A solution will soon be available.

Please hold off on working on this item. A solution will soon be available.
What exactly do you mean? Can you provide more details?

@seanmalloy I can't share the information in public. Talk to me in person.

I'm wondring why would you need to tie in secrets injection into the gitops/operator / templating at all.
There's quite a few projects around now that can do this at the Deployment/PodSpec level (check out some of the tools avialable from the bankvaults project).
Non-vault solutions tend to focus around tools like SealedSecrets from bitnami.

I don't care how we support it at the end, we just need to provide the capability. I'm thinking this is more a case of "here are some ways to solve this" in our docs.

Did anything come of this @Smiley73 ? I did not find any further reference.

@fabstu the eunomia project has not decided on the best way to implement this feature. Please feel free to share any ideas or recommendations you have. Thanks!

@seanmalloy Difficult! I don't have much of an idea either. Just wondered whether anything came of the prior discussion : )

@fabstu our current workaround is to use vault init containers for the pods that need the secrets.
We have some ideas for v1alpha2 to be able to inject secrets before the k8s resources are modified. Unfortunately the the v0.2.x release of Eunomia is still a bit out. (We could use some help squashing bugs to make faster progress ;-) ).

Thanks for the info @Smiley73.
I don't habe the time to spare, but I think having different template files is an interesting way to do things compared to flux.


Replace custom version code with semver

Right now there is a lot of custom version code, while it just looks like semantic versioning. In which case it would be better to simply use the semver package. The biggest reason is to lower the maintenance, even though the versioning code is simple enough that we might just want to not-fix this issue. However, right now we keep the versions stored as string, and have to parse it each time we want to interact with it, which is not super ideal. But again, it's cheap enough that this might as wel be neglectable. But be aware of dead of a thousand cuts.

I would like the original SemVer variable to be parsed from a string variable, this way I can add it to the buildscript to inject that string (being the git describe version string)

Since this issue was made, we did start using a minimal version of semver, specifically restricted for our purposes.
Because the problem with semver libraries (eg https://github.com/blang/semver), is that they can contain way too much data, and especially data which we cannot really easily serialize over the wire, using the Sia protocol. If you check https://github.com/blang/semver/blob/master/semver.go#L24-L30, that's really a nightmare to serialize over the Sia protocol, and also way too much data for what it is.
So I see 2 roads:

either we stick with our custom one-file version module, which might be good enough for our specialized purposes;
we wrap around a library (eg github.com/blang/semver) handicapping it to fit our needs (eg in the serialization department);

If we stick with our custom one-line version module (which is newer than this issue), we have to:

Make a MustVersionFromString function, which wraps around VersionFromString and panics in case of an error, this would allow us to have a string variable injected as you want. This one is easy enough as the biggest chunk of work is already done (parsing from strings);
In case we want to get the build version from git describe, which gets the versions, we would need to really be disciplined in using versioning that fits within our supported scheme. Right now if I do git describe I get "v0.1.0-1-g805e96d", which is illegal in the current scheme. v0.1.0-g805e96d would be legal, as for now I only allow 1 pre-release tag (limited to 8 bytes);

The good thing about our custom one-line version module is that it is really perfect to wire over the sia protocol, as the output string is a fixed size. If you check the ProtocolVersion struct for yourself, you can see that the only thing it has to serialize is one uint32 and an array ([8]byte). In case you think it will be needed to allow for greater versions than 255.255.255, we can also go for an uint64 instead of an uint32. We also still have 8 bits available, so in theory we could even support a 4th number after the patch number, as in <IP_ADDRESS>, but dunno that becomes a bit much. I have a feeling that a major+minior+patch version AND a commit 8-byte commit hash, should be sufficient to represent versions, but perhaps I'm missing something here.

A bit unrelated, I am not a too big fan of the wiring protocol of Sia and how it (de)serializes stuff, directly from struct fields, with no real structure. Meaning that everything really has to be static in size, AFAIK.
Personally I would ratter go for a structured encoding format for our wiring protocol, such as bencoding, which is still minimalistic, but at least we would have some sane structure, instead of just raw struct data.

Please let me know your opinions on these 2 (slightly related) topics, and I'll take it from there @robvanmieghem. The first part of my comment is obviously the important one for this issue.

@GlenDC I agree with the wiring protocol being structured more would be a very good thing.
For the version string, having v0.1.0-g805e96d instead of v0.1.0-1-g805e96d is fine, we do need to 'cut out the the number of commits away from tag' in the publish script then.

Or we have a seperate buildversion where we just use the entire git describe string and a protocolversion that only takes the vx.y.z string.

I think I would prefer you first suggestion. Although in theory I don't think it is ever needed to start comparing remote with local versions, more specific than the patch level. But perhaps that's something we can address later when we take more control over the wiring protocol. For now I would go for you first suggestion, as I don't think it's too important at this point.
Which build scripts do you want to inject it at? I can add that code as well as part of the PR I'll make than.


Trouble with screen lay out

Please provide context so the developer knows why this happens; how to reproduce it.

Direct after staring the program
Outlook voor Androidhttps://aka.ms/AAb9ysg downloaden

From: RavenMacDaddy @.>
Sent: Monday, May 23, 2022 6:59:56 PM
To: martinet101/WingetUI @.>
Cc: aadvanraamt @.>; Author @.>
Subject: Re: [martinet101/WingetUI] Trouble with screen lay out (Issue #19)
Please provide context so the developer knows why this happens; how to reproduce it.
—
Reply to this email directly, view it on GitHubhttps://github.com/martinet101/WingetUI/issues/19#issuecomment-1134922450, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFPOFJK5GMGH6BZMSIAIBCDVLO2QZANCNFSM5WV4B4ZQ.
You are receiving this because you authored the thread.Message ID: @.***>

Hello the problem is gone when i rezize the box then it works fine

Van: Martí Climent @.>
Verzonden: woensdag 25 mei 2022 13:28
Aan: martinet101/WingetUI @.>
CC: aadvanraamt @.>; Author @.>
Onderwerp: Re: [martinet101/WingetUI] Trouble with screen lay out (Issue #19)
Closed #19https://github.com/martinet101/WingetUI/issues/19 as completed.
—
Reply to this email directly, view it on GitHubhttps://github.com/martinet101/WingetUI/issues/19#event-6676934977, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFPOFJISVMN6D5J5IJ74YI3VLYFFNANCNFSM5WV4B4ZQ.
You are receiving this because you authored the thread.Message ID: @.***>


BI-3868 Changing govuk-frontend to version 3.5.0

Noticed in the cdn there's 3.6 available there, have you considered using that? Not a big deal but it might be better.

Good spot, I'll change to 3.6


Do not generate #include guards in Cython C files

Typical Cython-generated C files have an #include section which looks like this:
/* ... */
#define __PYX_HAVE__sage__ext__interpreters__wrapper_rr
#define __PYX_HAVE_API__sage__ext__interpreters__wrapper_rr
#include "string.h"
#include "stdio.h"
/* ... */

This patch removes those first two lines. They serve no purpose and in fact block an interesting use-case: a Cython file calling code implemented in C which in turns calls the original Cython file (see the added test case).

This is an unpleasant issue that I've run into recently as well. The problem is that Cython needs to forward declare everything so that there aren't any ODR violations. Handling any static variable declarations will be a bit tricky as well since there isn't a method for forward-declaring static variables that works in both C and C++ (see http://stackoverflow.com/a/936589/1935144). I think it's still possible to make all of this work properly by restructuring the ifdef guards in both the module and the autogenerated headers, but it's not an easy problem.

Note that this breaks existing tests.

I know it breaks tests, so this PR isn't ready to merge. However, I would really like to know the purpose of those tests and to see a more "real-world" example which shows the need of those #include guards.

I honestly don't remember how the API stuff is used in the wild, which is
why I'm hesitant to change it for fear of breaking people.
On Tue, Feb 2, 2016 at 12:37 AM, jdemeyer<EMAIL_ADDRESS>wrote:

I know it breaks tests, so this PR isn't ready to merge. However, I would
really like to know the purpose of those tests and to see a more
"real-world" example which shows the need of those #include guards.
—
Reply to this email directly or view it on GitHub
https://github.com/cython/cython/pull/474#issuecomment-178445070.

I forgot why I needed this, so let's close it.


download failed with timeout error

while downloading sources using krs_alpha.repos using vcs command
surender@xhdsurender41:~/krs_ws$ vcs import src --recursive < krs_alpha.repos
.....E
=== src/acceleration/acceleration_firmware (git) ===
HEAD is now at 913fe05 Add CHANGELOG.rst
=== src/acceleration/acceleration_firmware_kv260 (zip) ===
Invocation of command 'import' on client 'zip' failed: timeout: The read operation timed out (/usr/lib/python3.8/ssl.py:1099)
=== src/acceleration/ament_vitis (git) ===
HEAD is now at 219c04a Add CHANGELOG
=== src/acceleration/colcon-acceleration (git) ===
HEAD is now at 9ff8ca2 0.2.0
=== src/acceleration/ros2acceleration (git) ===
HEAD is now at a6a1a85 0.2.0 CHANGELOG updates
=== src/acceleration/vitis_common (git) ===
HEAD is now at 8805009 Add utilities library

@surender009,
For context, I presume your ask is related to instructions at https://xilinx.github.io/KRS/sphinx/build/html/docs/install.html. Note that acceleration_firmware_kv260 is being fetched directly from GitHub's releases. See the following line in the krs_alpha.repos file:
  acceleration/acceleration_firmware_kv260:
    type: zip
    url: https://github.com/ros-acceleration/acceleration_firmware_kv260/releases/download/v0.6.0/acceleration_firmware_kv260.zip

This is a 1.6 GB file so we might be encountering some issues due to the size itself. Tests I went through to try and reproduce your issues:

❌  I indeed obtained the same result you did with vcs. Further looking into it, there seems to be a wider issue with operations timing out with big files with Python-based clients, so I believe this is not specific to us. I did a bit of further testing:
✅ Downloading it from the browser: typing https://github.com/ros-acceleration/acceleration_firmware_kv260/releases/download/v0.6.0/acceleration_firmware_kv260.zip in your browser. I succeed downloading it. You just then need to unzip it and place it under src in your workspace
✅ wgeting it

wget https://github.com/ros-acceleration/acceleration_firmware_kv260/releases/download/v0.6.0/acceleration_firmware_kv260.zip
--2021-11-16 08:53:02--  https://github.com/ros-acceleration/acceleration_firmware_kv260/releases/download/v0.6.0/acceleration_firmware_kv260.zip
Resolviendo github.com (github.com)... <IP_ADDRESS>
Conectando con github.com (github.com)[<IP_ADDRESS>]:443... conectado.
Petición HTTP enviada, esperando respuesta... 302 Found
Localización: https://objects.githubusercontent.com/github-production-release-asset-2e65be/376909513/ba0e1de1-53b4-4aad-a6fd-a2f5a7c57218?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211116%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211116T075302Z&X-Amz-Expires=300&X-Amz-Signature=04baac28924a42852d2cf6dc600116db32519b0d190c40ba7142169817de9ed0&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=376909513&response-content-disposition=attachment%3B%20filename%3Dacceleration_firmware_kv260.zip&response-content-type=application%2Foctet-stream [siguiendo]
--2021-11-16 08:53:02--  https://objects.githubusercontent.com/github-production-release-asset-2e65be/376909513/ba0e1de1-53b4-4aad-a6fd-a2f5a7c57218?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211116%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211116T075302Z&X-Amz-Expires=300&X-Amz-Signature=04baac28924a42852d2cf6dc600116db32519b0d190c40ba7142169817de9ed0&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=376909513&response-content-disposition=attachment%3B%20filename%3Dacceleration_firmware_kv260.zip&response-content-type=application%2Foctet-stream
Resolviendo objects.githubusercontent.com (objects.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Conectando con objects.githubusercontent.com (objects.githubusercontent.com)[<IP_ADDRESS>]:443... conectado.
Petición HTTP enviada, esperando respuesta... 200 OK
Longitud:<PHONE_NUMBER> (1,6G) [application/octet-stream]
Grabando a: “acceleration_firmware_kv260.zip”

acceleration_firmware_kv 100%[================================>]   1,62G  73,8MB/s    en 22s

2021-11-16 08:53:57 (73,7 MB/s) - “acceleration_firmware_kv260.zip” guardado [1735682989/1735682989]

Short answer to unblock you, please fetch it from any of the other avenues and drop it into your workspace.

Further looking into this to isolate potential issues:
vcs functionality validation  - fetching it from a local resource ✅
This does not seem to be the issue. The following validation was performed:
mkdir src
cat << 'EOF' > krs_alpha.repos
repositories:
  acceleration/acceleration_firmware:
    type: git
    url: https://github.com/ros-acceleration/acceleration_firmware
    version: 0.4.0
  acceleration/acceleration_firmware_kv260:
    type: zip
    url: file:///Users/xilinx/Downloads/acceleration_firmware_kv260.zip/acceleration_firmware_kv260.zip
  acceleration/colcon-acceleration:
    type: git
    url: https://github.com/ros-acceleration/colcon-acceleration
    version: 0.2.0
  acceleration/ros2acceleration:
    type: git
    url: https://github.com/ros-acceleration/ros2acceleration
    version: 0.2.0
  acceleration/ament_vitis:
    type: git
    url: https://github.com/ros-acceleration/ament_vitis
    version: 0.5.0
  acceleration/vitis_common:
    type: git
    url: https://github.com/ros-acceleration/vitis_common
    version: 0.1.0
EOF

vcs import src --recursive < krs_alpha.repos
......
=== src/acceleration/acceleration_firmware (git) ===

HEAD está ahora en 913fe05 Add CHANGELOG.rst

=== src/acceleration/acceleration_firmware_kv260 (zip) ===
Downloaded zipfile from 'file:///Users/xilinx/Downloads/acceleration_firmware_kv260.zip' and unpacked it
=== src/acceleration/ament_vitis (git) ===

HEAD está ahora en 219c04a Add CHANGELOG

=== src/acceleration/colcon-acceleration (git) ===

HEAD está ahora en 9ff8ca2 0.2.0

=== src/acceleration/ros2acceleration (git) ===

HEAD está ahora en a6a1a85 0.2.0 CHANGELOG updates

=== src/acceleration/vitis_common (git) ===

HEAD está ahora en 8805009 Add utilities library

vcs functionality validation - fetching it from another server
Droped the file acceleration_firmware_kv260.zip in a different server and tried fetching it from there. Particularly, placed it at http://<IP_ADDRESS>/acceleration_firmware_kv260.zip:
cat << 'EOF' > krs_alpha.repos
repositories:
  acceleration/acceleration_firmware:
    type: git
    url: https://github.com/ros-acceleration/acceleration_firmware
    version: 0.4.0
  acceleration/acceleration_firmware_kv260:
    type: zip
    url: http://<IP_ADDRESS>/acceleration_firmware_kv260.zip
  acceleration/colcon-acceleration:
    type: git
    url: https://github.com/ros-acceleration/colcon-acceleration
    version: 0.2.0
  acceleration/ros2acceleration:
    type: git
    url: https://github.com/ros-acceleration/ros2acceleration
    version: 0.2.0
  acceleration/ament_vitis:
    type: git
    url: https://github.com/ros-acceleration/ament_vitis
    version: 0.5.0
  acceleration/vitis_common:
    type: git
    url: https://github.com/ros-acceleration/vitis_common
    version: 0.1.0
EOF

vcs import src --recursive < krs_alpha.repos
......
=== src/acceleration/acceleration_firmware (git) ===

HEAD está ahora en 913fe05 Add CHANGELOG.rst

=== src/acceleration/acceleration_firmware_kv260 (zip) ===
Downloaded zipfile from 'http://<IP_ADDRESS>/acceleration_firmware_kv260.zip' and unpacked it
=== src/acceleration/ament_vitis (git) ===

HEAD está ahora en 219c04a Add CHANGELOG

=== src/acceleration/colcon-acceleration (git) ===

HEAD está ahora en 9ff8ca2 0.2.0

=== src/acceleration/ros2acceleration (git) ===

HEAD está ahora en a6a1a85 0.2.0 CHANGELOG updates

=== src/acceleration/vitis_common (git) ===

HEAD está ahora en 8805009 Add utilities library

Which succeeded.

With https://github.com/ros-acceleration/acceleration_firmware_kv260/issues/1#issuecomment-970002827 I believe it becomes clear that the problem's that GitHub's server is interrupting the download.
@jasvinderkhurana and @giuliocorradi, given the previous limitation, can we look for an alternative path whereto deposit firmware releases? We can continue doing public releases at https://github.com/ros-acceleration/acceleration_firmware_kv260/releases (and though it's pretty straightforward to realize the problem in here) it might be worth providing a clean hurdle-less experience.
@jasvinderkhurana and @surender009, I'd be great if you could help with the following (ask): once you figure out where firmware files can be deposited elsewhere (e.g. in a Xilinx-owned server), can you file a Pull Request against KRS to update documentation accordingly?

@surender009  @vmayoral  could you please try vcs import --retry 10 to check if the problem disappears before changing things?

@surender009 @vmayoral could you please try vcs import --retry 10 to check if the problem disappears before changing things?

vcs import src --recursive --retry 10 < krs_alpha.repos
.....E
=== src/acceleration/acceleration_firmware (git) ===

HEAD is now at 913fe05 Add CHANGELOG.rst

=== src/acceleration/acceleration_firmware_kv260 (zip) ===
Invocation of command 'import' on client 'zip' failed: timeout: The read operation timed out (/usr/lib/python3.8/ssl.py:1099)
=== src/acceleration/ament_vitis (git) ===

HEAD is now at 219c04a Add CHANGELOG

=== src/acceleration/colcon-acceleration (git) ===

HEAD is now at 9ff8ca2 0.2.0

=== src/acceleration/ros2acceleration (git) ===

HEAD is now at a6a1a85 0.2.0 CHANGELOG updates

=== src/acceleration/vitis_common (git) ===

HEAD is now at 8805009 Add utilities library

Fails with GitHub's servers. They're probably just blocking it. They have an LFS service so likely this is an encouragement to use it 😄. See https://git-lfs.github.com/.

@vmayoral @giuliocorradi , I think we should find a place to host large files in xilinx servers, to give users a seamless experience.

ping @giuliocorradi, we need a resolution on this. Currently, it's not possible to install KRS from the documentation since the  acceleration_firmware_kv260 package will fail due to GitHub's restrictions. We need either a server wherein we can host the releases or an alternative service for large files.

ping @giuliocorradi and @jasvinderkhurana, do we have a solution for this already in a public server?

@vmayoral, currently no progress, but I am discussing with vivado team, for how to they host big files. I will update as soon as I get to know the complete process

Thanks for the update @jasvinderkhurana

@vmayoral , I have got the kv260 and zcu102 uploaded on Xilinx server, below are the links

https://www.xilinx.com/bin/public/openDownload?filename=acceleration_firmware_kv260.zip
https://www.xilinx.com/bin/public/openDownload?filename=acceleration_firmware_zcu102.zip

But currently the download speed from this server is very low. I am checking with concerned team and will update once it is fixed.

Thanks @jasvinderkhurana,
I gave it a try:
time wget https://www.xilinx.com/bin/public/openDownload?filename=acceleration_firmware_kv260.zip
--2021-12-07 07:41:11--  https://www.xilinx.com/bin/public/openDownload?filename=acceleration_firmware_kv260.zip
Resolviendo www.xilinx.com (www.xilinx.com)... <IP_ADDRESS>
Conectando con www.xilinx.com (www.xilinx.com)[<IP_ADDRESS>]:443... conectado.
Petición HTTP enviada, esperando respuesta... 302 Moved Temporarily
Localización: https://xilinx-ax-dl.entitlenow.com/dl/ul/2021/12/03/R210492402/acceleration_firmware_kv260.zip?hash=A5I6v3UuqBArDYcdXB9svg&expires=1638880872&filename=acceleration_firmware_kv260.zip [siguiendo]
--2021-12-07 07:41:12--  https://xilinx-ax-dl.entitlenow.com/dl/ul/2021/12/03/R210492402/acceleration_firmware_kv260.zip?hash=A5I6v3UuqBArDYcdXB9svg&expires=1638880872&filename=acceleration_firmware_kv260.zip
Resolviendo xilinx-ax-dl.entitlenow.com (xilinx-ax-dl.entitlenow.com)... <IP_ADDRESS>
Conectando con xilinx-ax-dl.entitlenow.com (xilinx-ax-dl.entitlenow.com)[<IP_ADDRESS>]:443... conectado.
Petición HTTP enviada, esperando respuesta... 200 OK
Longitud:<PHONE_NUMBER> (1,6G) [application/zip]
Grabando a: “openDownload?filename=acceleration_firmware_kv260.zip”

openDownload?filename=acceleration_firmware_kv260 100%[===========================================================================================================>]   1,62G  20,2MB/s    en 84s

2021-12-07 07:42:39 (19,8 MB/s) - “openDownload?filename=acceleration_firmware_kv260.zip” guardado [1735682989/1735682989]

real	1m28.246s
user	0m3.200s
sys	0m8.552s

It's not too bad I'd say, but if we can improve it, +1!

@vmayoral , yes it is better now. But earlier I was getting 60 KB/s only. So we can go ahead with the changes.  I will make the changes in KRS with new links.

All right, thanks!
Please paste in here the link to the PR with the changes and let's close with that this ticket.

Ping @jasvinderkhurana, can we get the link in here of the firmware for completeness? Thanks!

Closing this ticket due to inactivity.

Here are the firmware links. which I provided earlier in the ticket:
https://www.xilinx.com/bin/public/openDownload?filename=acceleration_firmware_kv260.zip
https://www.xilinx.com/bin/public/openDownload?filename=acceleration_firmware_zcu102.zip

Thanks @jasvinderkhurana!


feature: Added scope parameter for advertisingId

:tada: This PR is included in version 0.18.0-next.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Forbidding method calls of Object.create(null)

https://flowtype.org/try/#0PTAEAEDMBsHsHcBQiDGsB2BnALqAhgFygDeAvqALygDyARgFYCmK2AdCgE6N7aMAU6AK7RoASgDciPK2ywAytg4BLdAHM+E0KBChMAC1jCAJqFqNQSkY1V5oU1nGiVQAckcvx2sPsPQTZ0GhrW0QgA
// @flow

const a: {} = Object.create(null);
a.toString();  // should be illegal
a.lol = 'lol'; // should be legal

I know there is an issue about assigning properties on object with null prototype but didn't find any about forbidding calls of Object.prototype methods.

I am suffering this problem too, and some other problems derived from the same situation.

This does not seem to be fixed in v0.56.
The following should error but does not:
/* @flow */
const a = Object.create(null);
a.toString();

See https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVBjOA7AzgFzAEMwBeMAeQCMArAUw3wDoMAnOo-OgCmwFcYMAJQBuVESb44AZXysAltgDm3UUA


Investigate why auth0 doesn't let me use one-week expiration

I've tried several times to fix the token expiration at one week rather than one day.   But, it seems like a login is required daily, which I think is inconvenient and not warranted by the pretty limited value of the assets being protected on the server.

First of all, it's possible I am misusing auth0.  I have a native app and an API that are not (I think) formally linked to each other.   It's the native app that logs in.  The dashboard for that app has an expiration for the id_token but not the access_token.   The id_token expiration is 1 day, which I don't think I ever tried to change.
The API has an expiration which seems to apply to the access_token.   It is currently 1 day but I'm sure I set it to one week at some point.
I can certainly set both expirations to one week and then see what happens.  If it nominally fixes the problem, I can put off worrying about whether things are actually secure or not, but I should keep this open in some fashion until I reach a comfortable level of understanding.

I set both the id token expiration for the app and the access token expiration for the API to one week.  It appears both values held.  I am going to retitle this issue to focus on making sure I understand the relationship between app login and access token verification in APIs and am not misusing auth0 in a way that will compromise security.


useAsyncData can‘t watch slug

Environment

Operating System: Darwin
Node Version:     v16.14.0
Nuxt Version:     3.0.0-rc.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules, experimental, unocss, colorMode
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-wp5lsq-fyzsuf?file=pages/[slug].vue
Describe the bug
useAsyncData cannot update data correctly when watch slugs
Additional context
No response
Logs
No response

I found that I can get the slug to update the useAsyncDate by wrapping the route param into a computed()
May be a workaround but it does seem to work based on a few test and trials I did.
import { useRoute } from 'vue-router'
const route = useRoute()
const idOrSlug = computed(() => route.params.idOrSlug)
const { data: libraryVideo } = await useAsyncData(() => libraryVideoStore.fetchBySlugOrId(idOrSlug.value), { watch: [idOrSlug] })

In my case, on Nuxt 2 Bridge,watch: [route] resulted in an infinite loop (RangeError: Maximum call stack size exceeded).
Could find much on this issue and ended up using the flag workaround: https://stackoverflow.com/a/75952272/2771889

I found that I can get the slug to update the useAsyncDate by wrapping the route param into a computed()
May be a workaround but it does seem to work based on a few test and trials I did.
import { useRoute } from 'vue-router'
const route = useRoute()
const idOrSlug = computed(() => route.params.idOrSlug)
const { data: libraryVideo } = await useAsyncData(() => libraryVideoStore.fetchBySlugOrId(idOrSlug.value), { watch: [idOrSlug] })

I also noticed that things behave differently if I import the vue-router manually or if I just try to use the one that get's auto imported. So I included it here.

It seems that the auto-imported useRoute is not being updated in time, but the original useRoute in vue-router is functioning correctly.

Don’t use the one from vue-router. It’s not in sync with the suspended route and you’ll get flickering or issues with suspense.


Merge master into meshmap

Description
This PR fixes #1628

Couple conflicts - https://github.com/layer5io/meshery/pull/1629/conflicts

@vineethvanga18 will you pick up the remainder of this?


Longhorn: commit the orchestrator code for longhorn

You need to merge the two commits into one. Commit addressed the review is not functionally different from the original commit.
Also, since we're using the environment variables now, we need to provide examples for how to set those env in the kubectl yaml file in the commit message.


Batch subscribe list functionality contains error

Describe the bug
Unable to batch subscribe a list of emails because and ID check is looking for a non-existent class member.
https://github.com/Jhut89/Mailchimp-API-3.0-PHP/blob/master/src/Resources/Lists.php#L54
This line should be a check like:
$this->throwIfNot("id", $this->list_id);
Expected behavior
Batch subscribe request should fail only when no list ID ahas been provided.
Additional context
Will fix in a new release.

PR: https://github.com/Jhut89/Mailchimp-API-3.0-PHP/pull/65

Fixed in 3.1.1


Backport v20.0.1

What
back port the v20.0.1 to main
Why
the gh bot pr to do the same backport has fallen behind main and would have a conflict - https://github.com/stellar/soroban-tools/pull/1119 , doing it here as a rebase on top of latest main instead.
Known limitations

ok, I'll merge, I saw conflict on cargo.lock when I rebased main locally and assumed that would have popped up when merging main into release/v20.0.1, but didn't verify that


Fix mix-fast plugin

The mix command for listing all available actions has been changed from mix --help to mix help. The mix-fast plugin was using the old command and did not return any results, which prevented the plugin to work.
For the record, invoking the old mix --help returns the following output:
$ mix --help
Mix is a build tool for Elixir

Usage: mix [task]

Examples:

    mix             - Invokes the default task (mix run) in a project
    mix new PATH    - Creates a new Elixir project at the given path
    mix help        - Lists all available tasks
    mix help TASK   - Prints documentation for a given task

The --help and --version flags can be given instead of a task for usage and versioning information.

While invoking mix help returns:
$ mix help
mix                           # Runs the default task (current: "mix run")
mix app.start                 # Starts all registered apps
mix app.tree                  # Prints the application tree
mix arc.g                     # For Arc definition generation code
mix archive                   # Lists installed archives
mix archive.build             # Archives this project into a .ez file
mix archive.install           # Installs an archive locally
mix archive.uninstall         # Uninstalls archives
mix clean                     # Deletes generated application files
mix cmd                       # Executes the given command
mix compile                   # Compiles source files
mix credo                     # Run code analysis (use `--help` for options)
mix credo.gen.check           # Generate a new custom check for Credo
mix credo.gen.config          # Generate a new config for Credo
mix deps                      # Lists dependencies and their status
mix deps.clean                # Deletes the given dependencies' files
mix deps.compile              # Compiles dependencies
mix deps.get                  # Gets all out of date dependencies
mix deps.tree                 # Prints the dependency tree
mix deps.unlock               # Unlocks the given dependencies
mix deps.update               # Updates the given dependencies
mix dialyzer                  # Runs dialyzer with default or project-defined flags.
mix do                        # Executes the tasks separated by comma
mix docs                      # Generate documentation for the project
mix ecto                      # Prints Ecto help information
mix ecto.create               # Creates the repository storage
mix ecto.drop                 # Drops the repository storage
mix ecto.dump                 # Dumps the repository database structure
mix ecto.gen.migration        # Generates a new migration for the repo
mix ecto.gen.repo             # Generates a new repository
mix ecto.load                 # Loads previously dumped database structure
mix ecto.migrate              # Runs the repository migrations
mix ecto.migrations           # Displays the repository migration status
mix ecto.rollback             # Rolls back the repository migrations
mix escript                   # Lists installed escripts
mix escript.build             # Builds an escript for the project
mix escript.install           # Installs an escript locally
mix escript.uninstall         # Uninstalls escripts
mix format                    # Formats the given files/patterns
mix gettext.extract           # Extracts translations from source code
mix gettext.merge             # Merge template files into translation files
mix help                      # Prints help information for tasks
mix hex                       # Prints Hex help information
mix hex.audit                 # Shows retired Hex deps for the current project
mix hex.build                 # Builds a new package version locally
mix hex.config                # Reads, updates or deletes local Hex config
mix hex.docs                  # Fetches or opens documentation of a package
mix hex.info                  # Prints Hex information
mix hex.organization          # Manages Hex.pm organizations
mix hex.outdated              # Shows outdated Hex deps for the current project
mix hex.owner                 # Manages Hex package ownership
mix hex.publish               # Publishes a new package version
mix hex.repo                  # Manages Hex repositories
mix hex.retire                # Retires a package version
mix hex.search                # Searches for package names
mix hex.user                  # Manages your Hex user account
mix kinesis.tail              # tails a stream
mix loadconfig                # Loads and persists the given configuration
mix local                     # Lists local tasks
mix local.hex                 # Installs Hex locally
mix local.public_keys         # Manages public keys
mix local.rebar               # Installs Rebar locally
mix new                       # Creates a new Elixir project
mix phoenix.gen.html          # Generates controller, model and views for an HTML based resource
mix phoenix.server            # Starts applications and their servers
mix phx.digest                # Digests and compresses static files
mix phx.digest.clean          # Removes old versions of static assets.
mix phx.gen.channel           # Generates a Phoenix channel
mix phx.gen.context           # Generates a context with functions around an Ecto schema
mix phx.gen.embedded          # Generates an embedded Ecto schema file
mix phx.gen.html              # Generates controller, views, and context for an HTML resource
mix phx.gen.json              # Generates controller, views, and context for a JSON resource
mix phx.gen.presence          # Generates a Presence tracker
mix phx.gen.schema            # Generates an Ecto schema and migration file
mix phx.gen.secret            # Generates a secret
mix phx.routes                # Prints all routes
mix phx.server                # Starts applications and their servers
mix profile.cprof             # Profiles the given file or expression with cprof
mix profile.eprof             # Profiles the given file or expression with eprof
mix profile.fprof             # Profiles the given file or expression with fprof
mix release                   # Build a release for the current mix application
mix release.clean             # Clean up any release-related files
mix release.init              # initialize a new release configuration
mix run                       # Starts and runs the current application
mix test                      # Runs a project's tests
mix xref                      # Performs cross reference checks
iex -S mix                    # Starts IEx and runs the default task

Thanks!


Fix dotfiles

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@527e301). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #3   +/-   ##
=========================================
  Coverage          ?   71.32%
=========================================
  Files             ?       42
  Lines             ?     1639
  Branches          ?        0
=========================================
  Hits              ?     1169
  Misses            ?      470
  Partials          ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 527e301...633318c. Read the comment docs.


Volumes are not created when pool-claim is smaller than storage-class replica

Description
Volume does not get created for application when number of pools created is smaller than the number of replicas in storageclass.
Steps to reproduce

Use three noded openshift cluster with 1 master and 2 compute nodes.(i.e; master is not schedulable)
Apply openebs operator yaml from master branch of repo openebs/openebs.
Deploy percona application using openebs-cstor-sparce( storage class).

Expected Behavior

The volume should get provisioned for the corresponding pvc of percona application.
The volume creation should fail with error notenough pools present or similar. This should be visible when describing the pvc.

Current Behavior

Volume was not created and the error received was waiting for a volume to be created, either by external provisioner "openebs.io/provisioner-iscsi" or manually created by system administrator

Your Environment

kubectl get nodes:

kubectl get nodes
NAME               STATUS    ROLES          AGE       VERSION
opens1.mayacb.in   Ready     infra,master   5d        v1.10.0+b81c8f8
opens2.mayacb.in   Ready     compute        2d        v1.10.0+b81c8f8
opens3.mayacb.in   Ready     compute        2d        v1.10.0+b81c8f8

kubectl get pods -n openebs:

kubectl get po -n openebs
NAME                                         READY     STATUS    RESTARTS   AGE
cstor-sparse-pool-l0nf-7c97b5c744-zqkqz      2/2       Running   0          3h
cstor-sparse-pool-mef2-69dddb667c-6fd6c      2/2       Running   0          3h
maya-apiserver-67686ccd48-b976r              1/1       Running   0          3h
openebs-ndm-mbtlq                            1/1       Running   0          3h
openebs-ndm-qvxrm                            1/1       Running   0          3h
openebs-provisioner-67c4cbd8c6-v496b         1/1       Running   1          3h
openebs-snapshot-operator-644c567cf6-5l7vn   2/2       Running   1          3h

*kubectl get pods -n openebs:
NAME                                         READY     STATUS    RESTARTS   AGE
cstor-sparse-pool-l0nf-7c97b5c744-zqkqz      2/2       Running   0          3h
cstor-sparse-pool-mef2-69dddb667c-6fd6c      2/2       Running   0          3h
maya-apiserver-67686ccd48-b976r              1/1       Running   0          3h
openebs-ndm-mbtlq                            1/1       Running   0          3h
openebs-ndm-qvxrm                            1/1       Running   0          3h
openebs-provisioner-67c4cbd8c6-v496b         1/1       Running   1          3h
openebs-snapshot-operator-644c567cf6-5l7vn   2/2       Running   1          3h

kubectl get pv:

No resources found.

kubectl get pvc -n app-percona-ns:

kubectl get pvc -n app-percona-ns
NAME                  STATUS    VOLUME    CAPACITY   ACCESS MODES   STORAGECLASS           AGE
percona-mysql-claim   Pending                                       openebs-cstor-sparse   1h

kubectl describe pvc percona-mysql-claim -n app-percona-ns:

Name:          percona-mysql-claim
Namespace:     app-percona-ns
StorageClass:  openebs-cstor-sparse
Status:        Pending
Volume:
Labels:        <none>
Annotations:   kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"v1","kind":"PersistentVolumeClaim","metadata":{"annotations":{},"name":"percona-mysql-claim","namespace":"app-percona-ns"},"spec":{"acce...
               volume.beta.kubernetes.io/storage-provisioner=openebs.io/provisioner-iscsi
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
Events:
  Type     Reason                Age                From                                                                                Message
  ----     ------                ----               ----                                                                                -------
  Normal   Provisioning          6m (x12 over 1h)   openebs.io/provisioner-iscsi_openebs-provisioner-67c4cbd8c6-v496b_edf9f69c-f2f7-11e8-9954-0a580a820037  External provisioner is provisioning volume for claim "app-percona-ns/percona-mysql-claim"
  Warning  ProvisioningFailed    6m (x12 over 1h)   openebs.io/provisioner-iscsi_openebs-provisioner-67c4cbd8c6-v496b_edf9f69c-f2f7-11e8-9954-0a580a820037  failed to provision volume with StorageClass "openebs-cstor-sparse": Post http://<IP_ADDRESS>:5656/latest/volumes/: EOF
  Normal   ExternalProvisioning  4m (x416 over 1h)  persistentvolume-controller                                                                             waiting for a volume to be created, either by external provisioner "openebs.io/provisioner-iscsi" or manually created by system administrator

Logs of openebs-provisioner:

W1128 12:05:55.202920       1 controller.go:750] Retrying syncing claim "app-percona-ns/percona-mysql-claim" because failures 11 < threshold 15
E1128 12:05:55.203065       1 controller.go:765] error syncing claim "app-percona-ns/percona-mysql-claim": failed to provision volume with StorageClass "openebs-cstor-sparse": Post http://<IP_ADDRESS>:5656/latest/volumes/: EOF
I1128 12:05:55.203149       1 event.go:221] Event(v1.ObjectReference{Kind:"PersistentVolumeClaim", Namespace:"app-percona-ns", Name:"percona-mysql-claim", UID:"347dbf78-f2f8-11e8-8a4a-005056ba22b1", APIVersion:"v1", ResourceVersion:"479938", FieldPath:""}): type: 'Warning' reason: 'ProvisioningFailed' failed to provision volume with StorageClass "openebs-cstor-sparse": Post http://<IP_ADDRESS>:5656/latest/volumes/: EOF
W1128 12:07:06.534553       1 reflector.go:270] github.com/kubernetes-incubator/external-storage/lib/controller/controller.go:667: watch of *v1.PersistentVolumeClaim ended with: The resourceVersion for the provided watch is too old.
W1128 12:13:58.525219       1 reflector.go:270] github.com/kubernetes-incubator/external-storage/lib/controller/controller.go:670: watch of *v1.PersistentVolume ended with: The resourceVersion for the provided watch is too old.
W1128 12:14:14.478549       1 reflector.go:270] github.com/kubernetes-incubator/external-storage/lib/controller/controller.go:673: watch of *v1.StorageClass ended with: The resourceVersion for the provided watch is too old.

Logs of Maya-api-server:

nodes qualified for pool:only 0 node could be allotted but required is 1
E1128 13:47:01.483153       7 runner.go:112] Error syncing 'cstor-sparse-pool': aborting storagepool create operation as no node qualified: not enough nodes qualified for pool:only 0 node could be allotted but required is 1
2018/11/28 13:47:21.112022 [DEBUG] http: Request /latest/meta-data/instance-id (GET)
2018/11/28 13:47:21.112123 [DEBUG] http: Request /latest/meta-data/instance-id (117.124µs)
2018/11/28 13:47:21.113117 [DEBUG] http: Request /latest/meta-data/instance-id (GET)
2018/11/28 13:47:21.113182 [DEBUG] http: Request /latest/meta-data/instance-id (64.211µs)
I1128 13:47:31.445254       7 handler.go:172] Converging storagepoolclaim cstor-sparse-pool to desired state:current pool count is 2,desired pool count is 3
I1128 13:47:31.445354       7 storagepool_create.go:44] Storagepool resync event received for storagepoolclaim cstor-sparse-pool
I1128 13:47:31.456683       7 storagepool_create.go:60] Lease acquired successfully on storagepoolclaim cstor-sparse-pool
W1128 13:47:31.460417       7 storagepool_create.go:176] invalid or 0 min pool specified, defaulting to 1
I1128 13:47:31.491929       7 spc_lease.go:123] Lease removed successfully on storagepoolclaim
E1128 13:47:31.491996       7 handler.go:90] Storagepool cstor-sparse-pool could not be synced:aborting storagepool create operation as no node qualified: not enough nodes qualified for pool:only 0 node could be allotted but required is 1
E1128 13:47:31.492057       7 runner.go:112] Error syncing 'cstor-sparse-pool': aborting storagepool create operation as no node qualified: not enough nodes qualified for pool:only 0 node could be allotted but required is 1

Kernel (from uname -a):
Install tools:
Others:

I landed here from Google via "not enough pools available to create replicas".  My issue is very similar and I have 3 node setup 1 master + 2 workers.  I ended up changing both my storage classes (openebs-jiva-default and openebs-cstor-sparse) to use 2 replicas instead of 3.

thanks @silasb ... this is expected. However, was the error message clear enough?

Yes, but it took me a second to realize that my storage class determined the number of replicas present.  Maybe the default should be 2 nodes as I'm sure a lot of people, including me, are testing EBS on their homelab.

@silasb OpenEBS recommends 3 nodes as high availability of storage is considered important. In case of 2 nodes, if one node experiences any problem, data will be available as ReadOnly. I am cc-ing @kmova @ranjithwingrider to see if something can be done in this regard.


[Feature] Support Kibana Dashboards

place holder item for now *

Duplicates https://github.com/elastic/terraform-provider-elasticstack/issues/650


Authenticated client: ValueError: Expecting value: line 1 column 1

Hello,
When I'm trying to connect to GDAX with the authenticated client I get this traceback:
  File "gdax_test.py", line 10, in <module>
    auth_client.get_products()
  File "/root/git/test/env/lib/python3.4/site-packages/gdax/public_client.py", line 50, in get_products
    return r.json()
  File "/root/git/test/env/lib/python3.4/site-packages/requests/models.py", line 866, in json
    return complexjson.loads(self.text, **kwargs)
  File "/usr/lib/python3.4/json/__init__.py", line 318, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python3.4/json/decoder.py", line 343, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.4/json/decoder.py", line 361, in raw_decode
    raise ValueError(errmsg("Expecting value", s, err.value)) from None
ValueError: Expecting value: line 1 column 1 (char 0)

The code is very simple :
import gdax

passphrase = "X"
base64 = "Y"
key = "Z"

auth_client = gdax.AuthenticatedClient(key, base64, passphrase, api_url="https://api-public.sandbox.gdax.com")
auth_client.get_products()

When I try to use the public client, I get products.
I tried with false API keys and the result is the same so I suppose one of these bugs:

GDAX is returning an empty response and gdax-python is trying to decode,
the client is not authenticated and GDAX is returning something not expected.

I found that requests is returning a 404 code. That's why r.json() is not working correctly.
I will check soon how we can handle this kind of errors.

Error handling is an open issue (see #27).


Fix issue now item does not move on scroll down

Fixed!!
Now items does not move down on scrolling

@CloudyPadmal do i need to generate another PR after deleting comment line?
How to generate the test link?


implement substraTEE-signer SGX demo

setup:

docker container running substraTEE-signer on Intel NUC Test machine devsgx, SGX in HW mode!
docker container running vanilla substrate --dev on Intel NUC Test machine devsgx. See parity/substrate dockerhub

success scenario:

User Hans creates a new substrate account, in custody of substraTEE-signer enclave
substrate standard user Alice sends 1000 tokens to Hans' new account
Hans sends 100 tokens back to Alice by calling a send function in the substraTEE-signer enclave
account balances are correct

nice-to-have improvements:

password protection of substraTEE-signer send function
OTP Password protection (GoogleAuthenticator, YubicoAuthenticator)

Hints:

check the following js code that performs the success scenario without SGX: https://github.com/paritytech/oo7/issues/102
https://polkadot.js.org/apps/#/explorer

This setup was rejected in favour of the proposed architecture containing the substraTEE-worker (see https://github.com/scs/substraTEE for the high-level architecture)


💡[Feature]: Title: Movie Genre Classification Feature Implementation 🎬📽

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
This feature will utilize machine learning algorithms to analyze movie data and classify them into appropriate genres. The implementation will involve collecting movie datasets, training a classification model, and integrating the genre classification system into the existing project. The primary goal is to enhance the repository by adding a useful tool for movie data analysis and categorization.

s 📷

Use Case
Use Cases for Movie Genre Classification Feature
Automated Genre Tagging for Streaming Services:
Streaming platforms like Netflix or Amazon Prime can use this feature to automatically tag new movie releases with appropriate genres, enhancing user searchability and personalized recommendations.
Content Management for Movie Databases:
Movie databases such as IMDb or Rotten Tomatoes can use this feature to streamline the process of categorizing movies, ensuring consistent genre tagging across their vast collections.
Enhanced User Experience for Movie Recommendation Apps:
Movie recommendation apps can leverage this feature to provide users with genre-specific recommendations based on their viewing history, improving user engagement and satisfaction.
Data Enrichment for Media Analytics Companies:
Companies that provide media analytics can use this feature to enrich their datasets with genre information, enabling more detailed analysis and insights into viewing trends and preferences.
Movie Production and Distribution Insights:
Production houses and distributors can use this feature to analyze genre trends and audience preferences, helping them make informed decisions on future projects and marketing strategies.
Educational Tools for Film Studies:
Educational platforms focused on film studies can use this feature to automatically classify movies used in coursework, aiding in the organization and study of films by genre.
Benefits
Efficiency: Automates the process of genre classification, saving time and reducing manual effort.
Accuracy: Provides consistent and accurate genre predictions using advanced machine learning techniques.
Scalability: Can be easily scaled to classify large datasets of movies.
Add ScreenShots

s 📷

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

this is already available, so i will be closing this issue


How to get my account activated

It is very helpful and useful

Do you know how much I am going to get