"Go to Definition" and "Go to Declaration" have disappeared

Type: Bug
I just upgraded VSCode to 1.89.0 and the right-click "Go to Definition" and "Go to Declaration" options disappeared. They're absent from the right-click menu in all files. Restarting VSCode and my computer had no effect. I haven't installed any new extensions recently. I do not have the "Go" extension installed (I saw that suggested as the cause).

VS Code version: Code 1.89.0 (Universal) (b58957e67ee1e712cebf466b995adf4c5307b2bd, 2024-05-01T02:10:10.196Z)
OS version: Darwin x64 23.4.0
Modes:
Remote OS version: Linux x64 5.15.0-97-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 2600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
2, 2, 2

Memory (System)
16.00GB (0.09GB free)

Process Argv
--crash-reporter-id d187a3bf-57b9-4875-8360-f73b34c81fda

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: svdi-u8q-142.vdi.zooxlabs.com

OS
Linux x64 5.15.0-97-generic

CPUs
Intel(R) Xeon(R) Gold 6248R CPU @ 3.00GHz (8 x 2999)

Memory (System)
31.34GB (22.06GB free)

VM
100%

Extensions (21)

Extension
Author (truncated)
Version

jupyter-keymap
ms-
1.1.2

remote-ssh
ms-
0.110.1

remote-ssh-edit
ms-
0.86.0

remote-explorer
ms-
0.4.3

vscode-bazel
Baz
0.10.0

vscode-markdownlint
Dav
0.55.0

xml
Dot
2.5.1

gitlens
eam
14.9.1

dbc
lha
2.0.0

black-formatter
ms-
2024.2.0

debugpy
ms-
2024.6.0

isort
ms-
2023.10.1

python
ms-
2024.6.0

vscode-pylance
ms-
2024.5.1

jupyter
ms-
2024.4.0

jupyter-keymap
ms-
1.1.2

vscode-jupyter-cell-tags
ms-
0.1.9

vscode-jupyter-slideshow
ms-
0.1.6

cpptools
ms-
1.19.9

bazel-stack-vscode
Sta
1.9.8

vscode-proto3
zxh
0.5.5

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
chatpanelt:31018789
dsvsc021:30996838
f3je6385:31013174
dwnewjupytercf:31039676

Please use the Start Extension Bisect command to investigate whether the problem is being caused by one of your extensions.

What language is this for?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


WIP:  Add webhooks to namespaces and projects for editing PSA labels

Note, currently based on PR #150, will rebase once that merges

Will rebase once #150 merges

Ok, many updates here, chiefly, adding support to validating Create requests in addition to Update.  Will look at integration tests tomorrow.

Note, currently based on PR #150, will rebase once that merges

This has now been rebased

https://github.com/rancher/charts/pull/2281


Installation under Windows (using Visual Studio)

I received an email regarding some issues while installing Mantella under Windows, suggesting C++11 incompatibilities by Visual Studio. As I haven't any details at hand, we could get a Visual Studio licence to investigate on this ourself.
Visual Studio 2015 seems to be the first VS version being compatible with enough C++11 features to compile Mantella (https://msdn.microsoft.com/de-de/library/hh567368.aspx), so we should start with this one.

As I haven't any details at hand, we could get a Visual Studio licence to investigate on this ourself.

Microsoft is handing out licenses for VS via dreamspark (or whatever it's called now) including 2015. Could try quickly with one of those ;)

Yes, obtaining it via DreamSpark seems to be the way to go for us :smile:
I am currently working on other parts of the project, adding several code checks (iwyu, valgrind, clang-format, ...), adding missing unit tests and fixing some files if an issue is caught, wherefore I am  unable to look after it before these tasks are finished.
So if you have some spare time, fell free and please add an installation instruction for Windows / Visual Studio, so we could add it later on to the documentation.

Just got around to try it out. I'm getting these two errors if i include mantella:
Severity	Code	Description	Project	File	Line
Error	C2899	typename cannot be used outside a template declaration	mantellaTest	C:\mantellaTest\mantellaTest\mantella\include\mantella_bits\optimisationProblem\blackBoxOptimisationBenchmark\gallaghersGaussian101mePeaksFunction.hpp	40
Error	C2899	typename cannot be used outside a template declaration	mantellaTest	C:\mantellaTest\mantellaTest\mantella\include\mantella_bits\optimisationProblem\blackBoxOptimisationBenchmark\gallaghersGaussian21hiPeaksFunction.hpp	40
If i remove the gallaghers from include/mantella it works.
Also i'm not sure if i did the include right since i've actually never included a library with uncompiled sources under windows. Had to change config.hpp.cmake to a real hpp file and removed line 12. CBA to try to get cmake working with VS.
What i'm doing right now is having armadillo and mantella headers included under C/C++ -> Additional Include Directories and ARMA_USE_LAPACK;ARMA_USE_BLAS as Preprocessor Definitions. Under Linker -> Additional Library Directories i have "lib_win64;mantella\src" (the former directory is where the precompiled lapack and blas are located, which come with armadillo). Under Linker -> Input -> Additional Dependencies "lapack_win64_MT.lib;blas_win64_MT.lib" are added (also needed for armadillo).

Glad to hear, that you already got time to look into this.
If I understand the error message correctly, Visual Studio is bothered by the typename inside const typename arma::Col<double>::fixed<101> weight_;. This was previously required by the compiler in 07f0b613533dcc39847f58dd7b9c502937ced8b4 when all BBOB were templated.
While it is not required anymore, as of C++11 the compiler shouldn't throw an error at this point, but handle it as an redundant notice instead (previously to C++11, it would be correct to raise an error). I already applied a patch, revoking typename from these lines (there are also no further occurrences within the library), so you could try again to get it working.
Regarding the uncompiled sources include; I did not understood why you had to change config.hpp.cmake manually into config.hpp, could you please elaborate on this? My suggestion would be, that cmake wasn't able to locate Armadillo and create a solution file (i.e. Visual Studio project) for Mantella, is this correct?

Had to do that because i didn't even use cmake^^ But that's the next thing i want to do and see if there are any other error possibilites there.

Ok, this makes it clear to me. Let me know how it worked :smile:.

Mhm i think i've got it semi-working so far, unfortunately:
1>C:\mantellaTest\mantellaTest\mantella\src\helper\geometry.cpp(16): error C2398: Element '1': conversion from 'double' to 'char' requires a narrowing conversion
And a lot more similar errors. Which come from the initialiser lists. But i think it's not missing support, since for example std::vector<double> blub {1.0, 2.0, 3.0, 4.0}; works. The error is always converting X to char. Full log here
As a quick write up how i got where i am:

download Mantella.
create build folder in basefolder and open it.
cmake -DARMADILLO_INCLUDE_DIR=%armadillo location% -DOPENBLAS_LIBRARIES=%precompiled blas lib location% ..
precompiled blas comes with arma (which i don't think is actually needed there, but find_openblas will fail otherwise).
open the result in VS.
build the sub project mantella.

Nevermind all that, the whole problem was that i trusted armas config file. While it says it will "ARMA_USE_CXX11 is automatically enabled when a C++11 compiler is detected" it doesn't for the VS-compiler. I'm not sure if this wai and just how it is because of how i'm using arma or an actual bug.
So by forde enabling ARMA_USE_CXX11 these errors all resolve and i get Error	LNK1104	cannot open file 'C:\mantellaTest\mantellaTest\lib_win64\blas_win64_MT.obj'	mantella	C:\mantellaTest\mantellaTest\mantella\build\LINK	1
which is obviously caused by setting wrong variables for cmake. Need advice on how to properly link blas and lapack so that:

arma and mantella can use it
find_openblas finds it

I am not entirely sure how your folder structure is set up, but lets discuss the installation procedure first. Please correct me, or add anything if I missing something.

Install Visual Studio 2015
Install CMake
Download Armadillo into C:\Armadillo
Activate/uncomment ARMA_USE_CXX11 in C:\Armadillo\include\armadillo_bits\config.hpp
Deactivate/outcomment ARMA_USE_WRAPPER in C:\Armadillo\include\armadillo_bits\config.hpp
Extract pre-compiled OpenBLAS binaries into C:\OpenBLAS
Download Mantella into C:\Mantella
Open the console (cmd) and proceed with the following commands:
mkdir C:\Mantella\build
cd C:\Mantella\build
cmake -DCMAKE_PREFIX_PATH=C:\Armadillo;C:\OpenBLAS ..

After this, I would expect as the final step to build the solution in Visual Studio, correct?

Yes, except for the actual cmake command and that i did not comment out ARMA_USE_WRAPPER. If i use your cmake command i get Could NOT find OpenBLAS (missing: OPENBLAS_LIBRARIES) i downloaded and used this version and path was simply the base directory of that.
From here are two things i tried:

Specifying OPENBLAS_LIBRARIES myself, by trying out bin/libopenblas.dll ; lib/libopenblas.dll.a which both lead to more errors (unresolved symbol / some read error with an offset)
Looking at lib/cmake/openblas/OpenBLASConfig.cmake i see that there are some absolute paths specified in it which ofcourse are wrong. I'm not sure if this file get's automatically used by cmake if i only specify the basefolder on CMAKE_PREFIX_PATH. If it does, this might be the problem why it can't find openblas on it's own.

Besides that, it seems that atleast the generated VS-Project for Mantella seems to be correct and it's just linking to OpenBLAS which is the problem.

Based on the latest commit from the functional branch (30956f7949357757b8d72fab2b2b7835f3cfbe4f), the following install instructions should successfully build Mantella under Windows using Visual Studio 2015:

Install Visual Studio 2015 Community (or better)
Install CMake (at least version 2.8.2)
Download the latest version of Armadillo (http://arma.sourceforge.net/download.html) and copy its contents into C:\Armadillo
Activate/uncomment ARMA_USE_CXX11 in C:\Armadillo\include\armadillo_bits\config.hpp
Deactivate/outcomment ARMA_USE_WRAPPER in C:\Armadillo\include\armadillo_bits\config.hpp
Download the precompiled OpenBLAS binary package (http://www.openblas.net/) and copy its contents into C:\OpenBLAS
Download Mantella and copy its contents into C:\Mantella
Open the console (cmd) and proceed with the following commands:
mkdir C:\Mantella\build
cd C:\Mantella\build
cmake -DCMAKE_PREFIX_PATH=C:\Armadillo\include;C:\OpenBLAS -G "Visual Studio 14 2015 Win64" ..
cmake --build . --config Release

Now you should find the a Mantella library file under C:\Mantella\lib\Release\mantella.dll

Last step fails:
http://pastebin.com/qJYmgb3Q Mostly narrow conversions errors, but also initializer list conversion errors.
(Yes, i used the linked commit ;) and VS 2015 Enterprise )

Looking at the errors, it seems that Armadillo is not using the C++11 features.
Could it be, that ARMA_USE_CXX11 is not set?

You just added those two lines right :boar:
Uncommenting the Wrapper-Line breaks it, Mantella can't find Armadillo then:
CMake Error at CMakeLists.txt:58 (message):
Armadillo's runtime library could not be found, undefine/outcomment
ARMA_USE_WRAPPER inside Armadillo's configuration file, if we should link
directly againt OpenBLAS instead.
If it's commented, this step works. But on building it obviously fails with a lot of linker errors.

These were already in my comment from the 24. October :ghost:
Yes, as mentioned above, ARMA_USE_WRAPPER should be deactivated/outcommented, as we link directly againt openblas, skipping the step to compile Armadillo.
Which OpenBLAS version did you choose, the 64 bit version (OpenBLAS-v0.2.15-Win64-int32) ?

Ah, using the (suggested by sourceforge) latest version downloads the 32bit version. That indeed was the problem. Build goes through now.
Did you try to use the dll in a new project? I get this: http://i.imgur.com/zfD8Ws0.png
via Rightclick Reference->Add Reference->Browse->Select dll->OK
(As a sidenote, for some reason you can only add dlls in CLR projects, otherwise the browse option is missing)
But i also cannot add other dlls (same error) besides the ones from MS in the .NEFramework...

Another thing: Is it intentionally not producing a lib file?

I was also stumbling over the *.lib file. After some reading, handling as well as creating a shared library under Windows does not seems to be something we want to do.
Therefore, as of 8c7b648973988290aa07982e113aae5e337bac65, we will now generate a static library for Windows builds, instead of a shared one.
Does this help when used in a new project (I have yet to check this myself)?

I guess i'm doing something wrong, when i do it like http://stackoverflow.com/questions/3663439/how-to-add-an-external-static-library-to-a-visual-c-2010-express-project i get Cannot open include file: 'mantella_bits/config.hpp': No such file or directory. Probably doing something wrong (used the normal mantella include-directory for headers)

I did the following to include Mantella's headers and link against the library file:

Right-click the project and select Properties
Go to VC++ Directories
Add under Include Directories
- C:\Armadillo\include
- C:\Mantella\include
Add under Library Directories
- C:\OpenBLAS\lib
- C:\Mantella\lib\Release
Go to Linker -> Input  and add under Additional Dependencies (in this order)

libopenblas.dll.a
mantella.lib

Add some code and compile the project

After this, my simple Hello World project compiled just fine. However, after adding C:\OpenBLAS\bin to the system path, I am now stuck with some MinGW related errors (cannot found libgcc_s_seh-1.dll and so on), as OpenBLAS seems to be precompiled against MinGW.

If have just experimented with different MinGW providers (especially 64 bit variants) and the only one to be working with OpenBLAS seems to be MinGW-w64.
During the installation, the following configuration should work (the Architecture and Exception setting is mandatory).

Version: latest
Architecture: x86_64
Threads: win32
Exception: seh
Build revision: 1

To summarise everything, this is the current installation instruction for Visual Studio / Windows builds:
The following steps are written for 64-bit systems (tested). If you want to work with a 32-bit version, it should be sufficient to replace OpenBLAS and MinGW with their 32-bit counterpart and choose "Visual Studio 14 2015" as generator at step 6.3. It is also possible to use any other BLAS/LAPACK library beside OpenBLAS.
Compiling Mantella:

Install Visual Studio 2015 Community (or better)
Install CMake (at least version 2.8.2)
Download the latest version of Armadillo (http://arma.sourceforge.net/download.html) and copy its contents into C:\Armadillo

Activate/uncomment ARMA_USE_CXX11 in C:\Armadillo\include\armadillo_bits\config.hpp
Deactivate/outcomment ARMA_USE_WRAPPER in C:\Armadillo\include\armadillo_bits\config.hpp

Download the precompiled 64-bit OpenBLAS binary package (http://www.openblas.net/,  OpenBLAS-vX.X.XX-Win64-int32) and copy its contents into C:\OpenBLAS
Download Mantella and copy its contents into C:\Mantella
Open the console (cmd) and proceed with the following commands:
mkdir C:\Mantella\build
cd C:\Mantella\build
cmake -DCMAKE_PREFIX_PATH=C:\Armadillo\include;C:\OpenBLAS -G "Visual Studio 14 2015 Win64" ..
cmake --build . --config Release
You should now find a Mantella library file under C:\Mantella\lib\Release\mantella.dll

Include Mantella to a new or existing Visual Studio project:

Right-click the project and select Properties
Go to VC++ Directories
Add under Include Directories
- C:\Armadillo\include
- C:\Mantella\include
Add under Library Directories
- C:\OpenBLAS\lib
- C:\Mantella\lib\Release
Go to Linker -> Input  and add under Additional Dependencies (in this order)

libopenblas.dll.a
mantella.lib

Add some code and compile the project.
You should now have an executable file (*.exe).

Running your executable:

Install MinGW-w64  into C:\MinGW-w64 (OpenBLAS depends on this. You can skip this, if your BLAS/LAPCK library does not depend on MinGW)

Version: latest
Architecture: x86_64
Threads: win32
Exception: seh
Build revision: 1

Choose either of the following options:

Add the following locations to your system path (PATH).

C:\OpenBLAS\bin
C:\mingw-w64\mingw64\bin

Copy the following libraries into same location as your executable

C:\OpenBLAS\bin\libopenblas.dll
C:\OpenBLAS\bin\libgcc_s_seh-1.dll
C:\OpenBLAS\bin\libgfortran-3.dll
C:\OpenBLAS\bin\libquadmath-0.dll

Run your executable

@wlfbck Could you check these instructions on your system again?

Works up until Running your executable (haven't installed MinGW yet, cause conflicts with TDM-GCC-64 i don't have time for, but!), couple of things:

Before applying the VS settings it's important to switch the platform and configuration to either 'All Platforms/Configurations' or 'x64'
libgcc_s_seh-1.dll, libgfortran-3.dll, libquadmath-0.dll are part of MinGW and thus not in the OpenBLAS folder but in MinGW-w64\bin - copying these 3 should not be necessary btw
In TDM-GCC-64 libgcc_s_seh-1.dll doesn't exist, but libgcc_s_seh_64-1.dll does. Renaming does work. There are also 64 bit version of the other 2, which i also used and renamed. For these 2 the 32bit versions are also available. With these it does not work.

Yes, I forgot to mentioning the switch to Release/x64, this is added now. The copy&paste type (OpenBLAS -> mingw-w64) is now also fixed, thanks.
Running the script with TDM-GCC-64 doesn't worked on my system, simply renaming libgcc_s_seh_64-1.dll to libgcc_s_seh-1.dll resulted in a 0xc00007b error (the application was unable to start correctly).

This was added in 4e117678207d3466d3acebb6d7621eb909de8183

Hello,
I'm new to mantella and try to compile it. I folowed previously described steps, but I get a lot of linking errors (see below).  Do you have any idea what is going wrong?
DB.
Microsoft (R) Build Engine version 14.0.25420.1
Copyright (C) Microsoft Corporation. All rights reserved.
Build started 18. 09. 2016 12:24:33.
Project "C:\Mantella\build\ALL_BUILD.vcxproj" on node 1 (default targets).
Project "C:\Mantella\build\ALL_BUILD.vcxproj" (1) is building "C:\Mantella\build\ZERO_CHECK.vcxproj" (2) on node 1 (def
ault targets).
InitializeBuildStatus:
Creating "x64\Release\ZERO_CHECK\ZERO_CHECK.tlog\unsuccessfulbuild" because "AlwaysCreate" was specified.
CustomBuild:
All outputs are up-to-date.
FinalizeBuildStatus:
Deleting file "x64\Release\ZERO_CHECK\ZERO_CHECK.tlog\unsuccessfulbuild".
Touching "x64\Release\ZERO_CHECK\ZERO_CHECK.tlog\ZERO_CHECK.lastbuildstate".
Done Building Project "C:\Mantella\build\ZERO_CHECK.vcxproj" (default targets).
Project "C:\Mantella\build\ALL_BUILD.vcxproj" (1) is building "C:\Mantella\build\mantella.vcxproj" (3) on node 1 (defau
lt targets).
InitializeBuildStatus:
Touching "mantella.dir\Release\mantella.tlog\unsuccessfulbuild".
CustomBuild:
All outputs are up-to-date.
ClCompile:
All outputs are up-to-date.

Hello @Bracun, welcome to Mantella.
I see a lot linking errors to LAPACK functions (like dgesdd_).

Are you using Mantella together with OpenBLAS or a different BLAS/LAPACK library?
Where are these libraries located and how is it added to the PATH environment variable?

Just to let you know, we are currently in the progress to ship some major changes/improvements, especially regarding function templates and dependencies (this might be of interest for you).
You still want to fix the aforementioned linking errors as BLAS & LAPACK will still be required to use Mantella, but as we are switching (because of the massive use of templates in the next version) to deliver Mantella as a header-only library, you do not need to build Mantella itself on your system anymore, just include its header file into the project you are working on and ensure that this one is linked to some BLAS & LAPACK library.
As everything looks now, it should be merged into the master branch near the end of the upcoming week.

I have downloaded OpenBLAS 0.2.19; However, there were no binaries - only source code; I sucessfully build it (installed MinGW-w64, MSYS, etc) and got directory bin with subdirectoris bin, include and lib, with libopenblas.dll in bin subdirectory.   This three subdirectories are added to PATH.
PATH:
...
C:\MinGW-w64\mingw64\bin;
C:\Armdillo\include;
C:\OpenBLAS\bin\bin;
C:\OpenBLAS\bin\include;
C:\OpenBLAS\bin\lib;
?

Regarding OpenBLAS, you can find pre-build binaries with Version 0.2.15 on Sourceforge (https://sourceforge.net/projects/openblas/files/v0.2.15/), just to ease your build process for the moment.
In order to get to your problem's root, I have written you two example files - only relying on either BLAS or LAPACK. I already tested these on my machine with OpenBLAS (in a Linux environment however).
blas.cpp
#include <array>
#include <iostream>

extern "C" {
  void dgemm_(
      const char* trans_a,
      const char* trans_b,
      const int* n,
      const int* m,
      const int* k,
      const double* alpha,
      const double* a,
      const int* lda,
      const double* b,
      const int* ldb,
      const double* beta,
      double* c,
      const int* ldc);
}

int main() {
  const char trans_a = 'N';
  const char trans_b = 'N';
  const int n = 3;
  const int m = 3;
  const int k = 3;
  const double alpha = 1.0;
  const std::array<double, 9> a = {1.0, 2.0, 3.0, 1.0, 2.0, 3.0, 1.0, 2.0, 3.0};
  const int lda = 3;
  const std::array<double, 9> b = {1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0};
  const int ldb = 3;
  const double beta = 0.0;
  std::array<double, 9> c;
  const int ldc = 3;

  dgemm_(&trans_a, &trans_b, &n, &m, &k, &alpha, a.data(), &lda, b.data(), &ldb, &beta, c.data(), &ldc);

  std::cout << "/ "  << c[0] << ", " << c[3] << ", " << c[6] << " \\\n"
            << "| "  << c[1] << ", " << c[4] << ", " << c[7] << " |\n"
            << "\\ " << c[2] << ", " << c[5] << ", " << c[8] << " /"    << std::endl;

  return 0;
}

Can you compile this with c++ -std=c++14 blas.cpp -lopenblas? (-std=c++14 is not required for this example, but Mantella is based on it).
lapack.cpp
#include <array>
#include <iostream>

extern "C" {
  void dgesvd_(
      const char* job_u,
      const char* job_vt,
      const int* m,
      const int* n,
      double* a,
      const int* lda,
      double* s,
      double* u,
      const int* ldu,
      double* vt,
      const int* ldvt,
      double* work,
      const int* lwork,
      int* info);
}

int main() {
  const char job_u = 'A';
  const char job_vt = 'A';
  const int m = 3;
  const int n = 3;
  std::array<double, 9> a = {-0.558253, -0.411397, 0.285389, -0.0461681, 0.0365854, -0.313789, -0.505735, 0.199707, 0.200189};
  const int lda = 3;
  std::array<double, 3> s;
  std::array<double, 9> u;
  const int ldu = 3;
  std::array<double, 9> vt;
  const int ldvt  = 3;
  std::array<double, 15> work;
  const int lwork = 15;
  int info;

  dgesvd_(&job_u, &job_vt, &m, &n, a.data(), &lda, s.data(), u.data(), &ldu, vt.data(), &ldvt, work.data(), &lwork, &info);
  if (info > 0) {
    std::cout << "Failed to converge" << std::endl;
  }

  std::cout << "( "  << s[0] << ", " << s[1] << ", " << s[2] << " )" << std::endl;

  return 0;
}

Can you compile this with c++ -std=c++14 lapack.cpp -lopenblas?

Many thanks for help.
Working in Windows; Command prompt;  c:\OpenBLAS\bin>c++ blas.cpp -lopenblas
C:/mingw-w64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/6.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: cannot find -lopenblas
collect2.exe: error: ld returned 1 exit status
?cannot find -lopenblas? I couldn't find any lib.
My files are:
c:\OpenBLAS\bin>tree
Folder PATH listing
Volume serial number is 5A57-66AE
C:.
├───bin (libopenblas.dll)
├───include (cblas.h, f77blas.h, openblas_config.h)
└───lib (libopenblas.a, libopenblas.dll.a, libopenblas_penrynp-r0.2.19.a)
└───cmake
└───openblas (...)

If I create project (Console application) in VisualStudio15 it start complaining:
Error	LNK2019	unresolved external symbol dgemm referenced in function _main	... i guess missing h or/and lib files.

blas.cpp ... works in VisualStudio.
What I have to do is:
(1) copy libopenblas.dll, libopenblas.dll.a, cblas.h, f77blas.h, openblas_config.h to my project dir ;
(2) add libopenblas.dll.a to source files; cblas.h to header files
(3) #include "cblas.h"

lapac.cpp compiles in VisualStudio.
I have downloaded liblapack.lib, liblapack.dll,  libblas.lib, libblas.dll and added them to project as before.
But does not work because it wants mingw libraries. I have mingw-w64. ??

Nothing ..

Hi Bracun,
sorry to have let you wait so long for a response, I am currently working on finishing the next release.
Regarding what you already did, the include of neither cblas.h nor lapacke.h is needed, as a wrote the likake (the extern "C" part) for there Fortran-Library, which is one abstraction level below CBLAS and LAPACKE (both are actually just wrapper for the Fortran-Library).
Regarding running lapack.cpp (I assume from your words, that blas.cpp runs without problems?), I will need a few moments to test it myself. I will add another comment after this.

So I just installed Visual Studio, OpenBLAS (extending the system environment path and so on) an everything went fine.
Looking again at the libraries you mentioned to have added to the project, did you also added the libraries from mingw64_dll.zip (downloaded from https://sourceforge.net/projects/openblas/files/v0.2.15/)?
Also, feel free to poke me any time again I a response comes in late :)

With #217 , the installation on Windows should finally be trivial, as Mantella is now a header-only library (so you don't need to compile Mantella anymore) and (this came late during development and was the main reason for the delay), everything is built upon the C++ standard library.
So beside having a C++14 compatible compiler, there is no further dependency whatsoever anymore.

As the latest version on the master branch should fix this, this issue is now again closed until further comments.


[BUG]: referancing to some 'drizzle-orm/casing'

What version of drizzle-orm are you using?
0.35.1
What version of drizzle-kit are you using?
0.26.2
Describe the Bug
I am getting this error in arbitrary moments on trying to migrage
bunx drizzle-kit migrate
my migration is as simple as that:
ALTER TABLE "custom"."users" ADD COLUMN "password" text DEFAULT 'password' NOT NULL;
Error that I am facing:
`❯ bunx drizzle-kit migrate
node:internal/modules/cjs/loader:1228
throw err;
^
Error: Cannot find module 'drizzle-orm/casing'
Require stack:

<EMAIL_ADDRESS>at Module._resolveFilename (node:internal/modules/cjs/loader:1225:15)
at Module._load (node:internal/modules/cjs/loader:1051:27)
at Module.require (node:internal/modules/cjs/loader:1311:19)
at require (node:internal/modules/helpers:179:18)
at src/utils.ts (/private/tmp/bunx-501-drizzle-kit@latest/node_modules/drizzle-kit/bin.cjs:6775:21)
at __init (/private/tmp/bunx-501-drizzle-kit@latest/node_modules/drizzle-kit/bin.cjs:10:56)
at Object. (/private/tmp/bunx-501-drizzle-kit@latest/node_modules/drizzle-kit/bin.cjs:85751:1)
at Module._compile (node:internal/modules/cjs/loader:1469:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)
at Module.load (node:internal/modules/cjs/loader:1288:32) {
code: 'MODULE_NOT_FOUND',
requireStack: [
<EMAIL_ADDRESS>]
}

Node.js v20.17.0`
Expected behavior
No response
Environment & setup
No response

sorry guys, i was just in wrong dir. And still, err msg is wierd)


Allow users to purchase profile albums from BP store

The implementation should also include a page to show the history of profile albums as well as the ability to purchase them from an album torrent page as well. On the profile history, users should be able to hide a profile album from view.

What is meant by "profile album"?


[WIP] feat(auth): add OAuth2 login with GitHub and Google

This PR implement the OAuth2 login with GitHub and Google.
See #109.
Currently, this feature is still work in progress, it's not recommended to deploy it to production.
Screenshots

BUG
The link function on user page cannot work, I'll work on it in next several days.
TODO

[x] Other platforms (please comment below)
[x] OIDC
[ ] Revoke
[ ] TOTP
[ ] Error page

Currently GitHub login process in handled manually and Google is handled by passport-google-oauth20.
But passport implementation now has security problem since it uses express-session to store state param, and it's too heavy to import express-session as a dependency, so I'm still hesitating to rewrite it or not.

That's awesome, thanks! Do you think it is possible to create a generic OAuth2 configuration? If this would be possible, the admins could enter the parameters of their own identity provider, e.g., Authentik.
I've been struggling with that too, but it seems like you know OAuth2 better than me. What do you think?

General OAuth2 is impossible, but there is a standard OAuth2 authentication protocol called OpenID Connect (OIDC).
Almost all these platform support OIDC as provider, including Authentik.

Authentik
Authelia
Casdoor
Keycloak

So implementing OIDC protocol is enough for these authentication platoforms.

Okay, sorry I've never implemented OAuth2 before so I might make some thinking mistakes. But this is the opportunity to understand it better :)
If I understand it correctly every company implemented OAuth2 a bit differently so it is impossible to make this generic. OIDC is more standardized so this would allow a generic implementation?
E.g if there is a new OIDC provider we don't have to update the code right?

@stonith404 Yes, you are right :)
A standard OAuth procession includes the following steps:

Our website redirect user to the provider's login page with our client ID (URL of provider's login page is unknown)
After logged in provider's website, the provider will redirect user to a callback URL of our website with a code in query.
With the code, our website needs request an access token URL to get access token (URL of access token is also unknown)
After getting access token, our website now is able to get user info （but both the URL of user info API and format of user info is unknown)

In summary, it's nearly impossible to implement a generic OAuth2 login.
To solve the problems above, OIDC defines a configuration URL (example provided by Casdoor), with this URL we will know the necessary URLs during the processing of OAuth authentication (login, access token, user info etc.). Also, OIDC give us an id token (JWT) containing the user info, and it' filed name is fixed (example). Once we implement OIDC protocol, we'll have compatibility with all OIDC providers.

@zz5840 Ohh I think I got it now. Thanks for explaining :) Would it be possible then to implement OIDC instead of OAuth2 in this case? GitHub and Google sign in can also be used with OIDC, right?
Maybe you know Immich, they have the following configuration page for "OAuth":

They call it "OAuth" but it's basically OIDC, or I'm wrong?

@stonith404 Oh yes, according to the docs of Immich, they only support OIDC provider. Google does support both OAuth2 and OIDC, but GitHub does not support OIDC.
By the way, OAuth2 is an authorization method, which means access token returned by OAuth is able to access many resources in user's account (for example user's file in Google Drive). But OIDC is just an authentication method, we will only get limited user info if using OIDC.
Since google support OIDC, I will rewrite the google login with OIDC and add general OIDC support in next few days.

Awesome. Sorry the GitHub issue was incorrectly formulated, I hope that you don't have to rewrite much :/
I think we could drop the support for signing in with Github as it would need a custom implementation. Or do you think we should still support it? I'm not sure if many admins actually want to use IDPs that are not self-hosted anyway.

@stonith404 The OAuth login is not only for enterprise, but also for public users. If I deploy this project to my server and make it available to public, I hope users can login with their familiar social account rather than register a new one, so it's necessary for us to adapt as many platforms as possible.
As shown below, Gitea (a self-hosted GitHub alternative) provide a bunch of OAuth2 platforms to chosen from, and many of them do not support OIDC.

@zz5840 Ah okay I see, that absolutely makes sense. Thanks!

@stonith404 I'm not so familiar with Nest.js, is it possible to get JWT token with without @UseGuards(JwtGuard) (that means JWT token is optional, and I'll handle it manually).

@stonith404 Sorry, I mean I need user (exactly user id)

@zz5840 That's not possible as the user context gets set by the JWT claim sub. Without the JWT there is no way the backend knows who requests the route.
Where exactly would you need this functionality?

Where exactly would you need this functionality?

Linking account.
I need to judge if user has logged in in callback route. If user has logged in, link their OAuth account to our account, and create a new account if not.

I need to judge if user has logged in in callback route

Sorry could you elaborate? In the github/callback route you check with this line if the user has an account already by making a db query with the information provided by the token of GitHub. Why do you need the token additionally?

Oh, or do you mean if the user already has a Pingvin Share account and he wants to link his existing Pingvin Share account from the db with e.g GitHub?

Oh, or do you mean if the user already has a Pingvin Share account and he wants to link his existing Pingvin Share account from the db with e.g GitHub?

Yes, the following line is just used to login.
https://github.com/stonith404/pingvin-share/blob/c85eaade6a08e278941a7165e55e34923623ccde/backend/src/oauth/oauth.service.ts#L61-L63

Okay I see. You have to parse the jwt manually as far as I know.
In the controller you can get the jwt with req.cookies.access_token. Then you create a simple function:
  async getUserIdFromAccessToken(accessToken: string) {
    try {
      const { sub } = this.jwtService.verify(accessToken);
      return sub;
    } catch {
      // not logged in
      return null;
    }
  }

Oh, I see. Thx :)

@zz5840  No problem, just let me know if you need anything :) You can text me on Discord too (stonith404) if this is easier for you.
But I take a break for today, I had an extremely long day.

@stonith404 Ok, have a good rest.

@stonith404 OAuth processing is contains multiple redirects, so it's hard to show TOTP on login page, maybe we need a new TOTP page instead of integrating it with login page.
Error page for the same reason.

@zz5840 Yeah you're right this would make more sense.

But does it even make sense to have TOTP when the user signs in with an IDP? Because I can't remember where I was able to specify a 2FA method on an app itself when I've used OAuth because TOTP would get requested by the IDP's login page itself. Or, did I misunderstand something?

@stonith404 I add a config to control whether TOTP should be checked when using OAuth, just leave it to the administrator.

@zz5840 It looks extremely promising, I've just tested it successfully with Keycloak and GitHub and it works with no problems! I'll take a closer look ASAP.

@zz5840  I think it would make more sense to set the password to null if you sign up with OAuth instead of setting a random password. I thought about something like this:

The user info end would need to return an additional property like hasPassword.
What do you think?

@stonith404 OK, I'll modify it later.
By the way, I think we can put both password and totp into security panel. It's a little messy now.

@stonith404 I think I must do it after you making the password nullable. It occurs some error when I simply edit prisma model. Maybe some changes should apply to the auth code.

@zz5840 I've implemented the nullable password. I also updated the frontend behaviour when the user doesn't have a password.
Could you please run the formatter when you're done with your changes (npm run format)?

@stonith404 Sorry, I will run it in next commit.

@zz5840 No problem, it just could result in merge conflicts because my IDE formats automatically.

@stonith404 Random username and password is fixed, I'll deal with TOTP in following commit. It seems to be a big task. 😫

@zz5840  Yeah this could get a bit difficult. Take your time and let me know if you need anything :) I think after that the feature is ready!

@stonith404 Server will return login token only if username and password have been verified, is it necessary to pass the password and verify the user in signInTotp again?
https://github.com/stonith404/pingvin-share/blob/8827ab622fb8647dce6a065e7929607eaa5fe6f2/backend/src/auth/auth.service.ts#L55-L69

Yeah and I see that's not ideal for TOTP. A potential solution would be to store the userId with the Login Token, then we wouldn't have to enter the email and password again.

@stonith404 OK, I'll solve it.

@stonith404 TOTP works now! Could you please test it?

@zz5840 Great! I'll look into it ASAP

Everything looks fine for me. I'm in love with the new TOTP page, it looks awesome :)
I'll test it a bit more over the weekend but after that it should be ready to merge. I built a Docker image if you want to test it on your server too stonith404/pingvin-share:development

@stonith404 I will make it ready to merge after I complete the error page today.

@stonith404 The error page is completed, I think it's ready for review now.
So sorry I forgot this is a PR and rebased it to master, there's lots of unrelated commits now.

@zz5840 Awesome, I'll look into it ASAP.

I've just made a minor change that it will display the original error message of the OAuth provider if available:

Even though this message is only in English, it's still better than a generic error message, in my opinion. Would you agree?

@stonith404 Maybe the backend should only response with a i18n key rather than the explicit message. The error message should be written in local files.

According to the documentation of GitHub OAuth App (https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/authorizing-oauth-apps#error-codes-for-the-device-flow), most error code except access_denied and expired_token is insignificant. So other messages could just return default message. (I will add expired_token later)

@zz5840 Yeah that makes sense, thanks! I'll test it again tomorrow and then I'll merge it :)

@zz5840 Sorry, I'm a bit busy. I'll make the final checks over the weekend and merge it afterwards.

@stonith404 OK, I'll do some checking before then. 😃

@stonith404 So does it need to be global, I'll delete it if not.
https://github.com/stonith404/pingvin-share/blob/08ffa5481a81e4a098ac0ba895face94616d134a/backend/src/main.ts#L10

@zz5840 Oh yeah, this doesn't need to be global. Because we only return this error page if something went wrong with OAuth, right? For other backend errors we show toasts.

@stonith404 OK, I think we can merge it.

Oh I almost forgot to create a migration. I'll do it quickly

I have created the migration, and I want to test it on my development server. Strangely, the build of the Docker image fails due to connectivity errors with npm. I will try again tomorrow.

Thx, I didn't even know it's necessary to install Python when installing nanoid. 😖


Update u-boot

Used commit rev instead of tag because it contains various fixes, mainly usb-related crashes

Not really comfortable grabbing untagged releases. I know the crashes are kind of annoying but they are not hard to resolve. Can the relevant commits just be added as patches?

Should i leave commit rev or switch to a tag?


feature request - VR

In this very nice looking workflow are there plans to add any automated variance reduction? Magic? You could imagine a check on the tally to determine if passing some metric and if not running some automated VR routines, depending on if global or target based VR is required.  Considering OpenMC VR is only just in most recent versions, I guess this might needs OpenMC developments as well.

Yep Magic is being worked into OpenMC, I guess it is about 2 months away. I had a quick go at the weight windows but it is difficult without Magic.


ReadTheDocs version selector custom CSS stopped working

For some reason, the version dropdown menu stopped working on our website...
There is a div with a specific class in the HTML that should trigger readthedocs to inject the version menu there, but that doesn't happen anymore.

this seems to be related to readthedocs beta features that got enabled without us noticing

Result of some research on this: we were enrolled into some readthedocs beta and therefore many features work differently now. We found a fitting workaround for now with the version menu still in the corner, but the rest working.


Update to Graph/Outlook comparison doc

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/rest/compare-graph-outlook.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update techCompanies.js

Added Vodafone to the Json file. Kindly check and merge

@Victorayo i will be closing this PR, Vodafone is not an African company.


Extras optionals must be defined on top level dependencies.

Codecov Report

Merging #7 (8f4586e) into main (eb43b5c) will decrease coverage by 7.49%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##              main       #7      +/-   ##
===========================================
- Coverage   100.00%   92.50%   -7.50%
===========================================
  Files           10       10
  Lines          307      307
  Branches        33       21      -12
===========================================
- Hits           307      284      -23
- Misses           0       21      +21
- Partials         0        2       +2

Impacted Files
Coverage Δ

django_cache_mock/backends/redis.py
87.36% <0.00%> (-12.64%)
:arrow_down:

tests/conftest.py
87.75% <0.00%> (-12.25%)
:arrow_down:

tests/test_backends.py
91.07% <0.00%> (-8.93%)
:arrow_down:

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


feature： Support protocol http forced jump to https

Support protocol http forced jump to https

you can use the redirect plugin to do that.


Discuss RealSense rgb / depth frames and alignment in simulation

I was trying to visualize the point cloud from ergoCub1_1 in simulation with rviz2 and I was superimposing it on the 3D model of the robot rendered according to the forward kinematics and I noticed the following misalignment:

As the red arrows try to indicate, the point cloud is not perfectly superimposed on the model - something that 1) I was not expecting and that 2) actually does not happen on other robots, e.g., iCubGazeboV2_5_visuomanip.
URDF investigation
I then investigated the urdf of the robot ergoCubGazeboV1_1 and I noticed the following facts:

a realsense frame is defined and two childs

realsense_depth_frame
realsense_rgb_frame
via two fixed joints

the way the RGB camera plugin is configured is not really clear to be honest:

the sensor is referring to the link realsense instead of realsense_rgb_frame
https://github.com/icub-tech-iit/ergocub-software/blob/a092c3a53ab2ab8c9e46bd0a4210ee8815cbaf52/urdf/ergoCub/robots/ergoCubGazeboV1_1/model.urdf#L3488
the pose of the sensor is changed in other two places (3492, 3494)
https://github.com/icub-tech-iit/ergocub-software/blob/a092c3a53ab2ab8c9e46bd0a4210ee8815cbaf52/urdf/ergoCub/robots/ergoCubGazeboV1_1/model.urdf#L3492-L3495
an additional pose reference is given later on
https://github.com/icub-tech-iit/ergocub-software/blob/a092c3a53ab2ab8c9e46bd0a4210ee8815cbaf52/urdf/ergoCub/robots/ergoCubGazeboV1_1/model.urdf#L3520-L3523
all these transformation makes it quite hard to understand what is going on

the depth camera is configured similarly but with different numbers

Proposed changes
I propose the following changes:

(I know that not all might agree on that) we should make sure that the RGB and depth sensors are configured to produce perfectly aligned frames. Even if the simulator can handle two different frames for the RGB and depth parts, as the real camera has a shift between the two, the final aim of the simulator should be that of reproducing a real setup and on the real setup we always, not sure if someone does not, activate the alignment between RGB and depth frames at the YARP-level or ROS2-level, i.e. the final images on ports/topic are already aligned.
simplify a lot the way the sensors are configured in the URDF by making these changes:

make sure that both the RGB and depth sensors refer to the frame realsense_rgb_frame
removing all the other change of poses
keep only the <pose>0.0 0.0 0.0 0.0 -1.57 1.57</pose> correction which make sure that the usual orientation used for cameras in robotics (y down, x right, z out of image plane) is aligned with the convention used inside Gazebo (z up, y left, x out of image plane)

The final configuration becomes:
<gazebo reference="realsense_rgb_frame">
    <sensor name="realsense_head_depth" type="depth">
      <always_on>1</always_on>
      <update_rate>30.000000</update_rate>
      <pose>0.0 0.0 0.0 0.0 -1.57 1.57</pose>
      <camera name="intel_realsense_depth_camera">
      (etc)
  </gazebo>
  <gazebo reference="realsense_rgb_frame">
    <sensor name="realsense_head_rgb" type="camera">
      <always_on>1</always_on>
      <update_rate>30.000000</update_rate>
      <pose>0.0 0.0 0.0 0.0 -1.57 1.57</pose>
      (etc)
  </gazebo>

Comparison
Using the above proposals, we get the alignment as expected:

Superimposition is quite nice also when closing fingers:

I would be happy to discuss on the above with you in order to understand how to possibly fix the configuration for Gazebo, keeping in mind that there is a part of automatic generation going on in this repository.
cc @traversaro @pattacini @Nicogene

the way the RGB camera plugin is configured is not really clear to be honest:

I think I can help a bit on this:

the sensor is referring to the link realsense instead of realsense_rgb_frame

realsense_rgb_frame is not a real frame with a mass, it is just an additional mass-less links used in URDF to represent a frame. It is lumped away in the URDF --> SDF conversion, i.e. removed. The <model>--><gazebo> reference attribute require that a "real" link (or joint) is passed as argument.

an additional pose reference is given later on

You can ignore that tags. <model>--><sensor> tags in URDF are ignored by Gazebo/SDF, that only considers <model>--><gazebo>--><sensor> tags. The <model>--><sensor> tags are part of an URDF extension that was never implemented by sdformat/Gazebo: http://wiki.ros.org/urdf/XML/sensor .

The <model>--><gazebo> reference attribute require that a "real" link (or joint) is passed as argument (unless you are using a really recent version of sdformat, if I am not wrong).

Just to elaborate more on this, which version of Gazebo and sdformat you used for your tests?

To be addressed after our PI16, that is in two weeks.
/remind October 30 cc @Nicogene

Even if the simulator can handle two different frames for the RGB and depth parts, as the real camera has a shift between the two, the final aim of the simulator should be that of reproducing a real setup and on the real setup we always, not sure if someone does not, activate the alignment between RGB and depth frames at the YARP-level or ROS2-level, i.e. the final images on ports/topic are already aligned.

Related to that, we should check which configuration files we ship by default to access the realsense and what is set there.

Thanks @traversaro and @pattacini for your answers.
I did not know that the frame used in the reference tag had to be "real". If realsense_rgb_frame gets lumped away, it is then strange that I was able to run the simulation with reference = realsense_rgb_frame. But, as you said, maybe it depends on the version of gazebo and sdf.

Just to elaborate more on this, which version of Gazebo and sdformat you used for your tests?

I am using

Gazebo multi-robot simulator, version 11.13.0 (the apt package is gazebo11/unknown,now 11.13.0-1~focal amd64 [installed]

the sdf of the world where I put ergoCubGazeboV1_1 had sdf version="1.7" within the xml

I am composing the point cloud in YARP and then sending it to ROS2 with a custom module. That module is using the frame realsense_rgb_frame to tag the point cloud - this tag is then used within rviz2 to properly place the cloud in the space

this seems consistent with the configuration done for the RGBD sensors on ROS2 in simulation, see:

https://github.com/icub-tech-iit/ergocub-software/blob/a092c3a53ab2ab8c9e46bd0a4210ee8815cbaf52/urdf/ergoCub/conf/sensors/rgbd_camera_wrapper_ros2.xml#L9

Related to that, we should check which configuration files we ship by default to access the realsense and what is set there.

In simulation, it seems that the alignment was assumed, i.e.:
https://github.com/icub-tech-iit/ergocub-software/blob/a092c3a53ab2ab8c9e46bd0a4210ee8815cbaf52/urdf/ergoCub/conf/sensors/rgbd_camera_wrapper_ros2.xml#L9-L10
On the real robot, it seems that the alignment is enabled as well:
https://github.com/robotology/robots-configuration/blob/master/ergoCubSN001/sensors/realsense.xml#L12

Actually I was just relying on memory, and I could not find anything on this, so I may be not recalling correctly. If attaching to a fake link works fine on the Gazebo available via apt on Ubuntu 22.04 (i.e. sdformat9 9.7.0/Gazebo 11.10.2), it is ok for me.

actually this test was done on Ubuntu 20.04 but we also have an easy way to test it on Ubuntu 22.04 so that we can be sure

If attaching to a fake link works fine on the Gazebo available via apt on Ubuntu 22.04

I tried with Ubuntu 22.04 with Gazebo 11.0.2 and your suspicions were correct @traversaro: using a fake link as a reference tag does not work (the image was badly rotated).
Nonetheless, the actual problem is more the fact that vision and kinematics do not agree - as the point cloud reveals.
In this regard, I tried to restore the original URDF and then use the same pose parameters of the RGB sensor, i.e.,
https://github.com/icub-tech-iit/ergocub-software/blob/a092c3a53ab2ab8c9e46bd0a4210ee8815cbaf52/urdf/ergoCub/robots/ergoCubGazeboV1_1/model.urdf#L3492-L3495
for the depth sensor and that was enough to solve the problem.

Thanks! Yes, the two problems (that the sensor stuff is complex, and that the RGB and the depth are not aligned while in reality they are) are distinct. I think we can keep the issue to track the second problem.

In this regard, I tried to restore the original URDF and then use the same pose parameters of the RGB sensor

I forgot to mention that maybe also the <horizontal_fov> tags should be matched so as to have the same intrinsics on both sensors.

Hi @xEnVrE,
Since in the urdf there is not a single sensor that handles both streams, but depth and rgb are disjointed sensors, a way to align it could be take this
https://github.com/icub-tech-iit/ergocub-software/blob/f7ba46bb2a6a9aa94f0402916b7a2288a6d9cd84/urdf/creo2urdf/data/ergocub1_1/ERGOCUB_all_options.yaml#L817-L851
Changing frameName to SCSYS_HEAD_RGB and <horizontal_fov>1.57079</horizontal_fov> to <horizontal_fov>1.2217</horizontal_fov> should mimic what happens on the real robot.
About the pose
https://github.com/icub-tech-iit/ergocub-software/blob/f7ba46bb2a6a9aa94f0402916b7a2288a6d9cd84/urdf/creo2urdf/data/ergocub1_1/ERGOCUB_all_options.yaml#L825
I probably copied it from icub3 yaml so it can be wrong but I don't think it is the problem here.

I probably copied it from icub3 yaml so it can be wrong but I don't think it is the problem here.

Maybe I am wrong, but should not we have the same pose for both sensors to get the alignment? Otherwise they will observe a different scene.

but should not we have the same pose for both sensors to get the alignment?

If I am not wrong that pose is referred to the frameName, it is already the same for the 2 sensors, so changing the frame could do the trick
I committed here https://github.com/icub-tech-iit/ergocub-software/tree/fix/depthAlignment the urdf of ergoCubGazeboV1_1 w/ the depth aligned w/ the rgb camera, if it is correct I do the same thing also for the other robots and open a PR

if it is correct I do the same thing also for the other robots and open a PR

I can make some tests and let you know between today and tomorrow

Hi @Nicogene,
I tested your branch and the result seems fine so far:

PR opened:

https://github.com/icub-tech-iit/ergocub-software/pull/188


DBZ-2045 Refresh postgres schema when a new enum value is noticed

Hey @bradengroom, howdy? Where are we with this PR? Could you rebase it to the current master? Is it good to go from you PoV otherwise?

Hey @bradengroom, are you still planning to wrap up this one?

Yes, sorry. I’m planning to come back to this. I’ve just been a bit busy on
my end.
On Wed, Jun 3, 2020 at 2:05 AM Gunnar Morling<EMAIL_ADDRESS>wrote:

Hey @bradengroom https://github.com/bradengroom, are you still planning
to wrap up this one?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/debezium/debezium/pull/1477#issuecomment-638066385,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMEVJQTO7PQLCKXMV44WNLRUYG67ANCNFSM4M2ERFMQ
.

No worries. Actually, I'll just finish it up myself if you don't mind. Seems there's not much missing anyways than a small doc update. Thanks!

Hi @bradengroom, as the 1.3 cycle is soon going to come to an end, it would be nice to wrap this up and get it included.  Would it be possible if you could take a quick moment and answer the pending questions that Gunnar has above?  Thanks!

Going to close this one, as it's quite oudated by now. Thanks nevertheless, @bradengroom.


WorkloadIdentityFederation auth support

Task name: AzureResourceGroupDeploymentV2
Description: Updated azure-pipelines-tasks-azure-arm-rest-v2 dependency for workloadIdentityFederation auth support
Documentation changes required: (Y/N) N
Added unit tests: (Y/N) N
Attached related issue: (Y/N) N
Checklist:

[x] Task version was bumped - please check instruction how to do it
[ ] Checked that applied changes work as expected

/azp run


Fix a-vs-an typos

Fix a-vs-an typos.

@wilmerpaulino Thanks for reviewing. Now updated. Please re-review :-)

@wilmerpaulino Updated again to fix spaces. Please re-review :-)

Needs to be rebased!

Rebased! :-)

Are the build errors related to the changes made in this PR?

@practicalswift No, shouldn't be.
I think it could be worth splitting this PR into several small ones, restricted to one package at the time say. That would make it easier to get merged before the branch gets out of date 😀

@halseth Oh, that's a lot of PR:s – it'll probably be easier for me to just keep rebasing :-)
Any chance of a review soon? :-)


[Google Chrome] Search Bookmarks Error - "no bookmarks"

Extension
https://www.raycast.com/Codely/google-chrome
Description
I've installed the latest Raycast and Chrome Extension, but continue to run into this error when attempting to search my bookmarks in Chrome. It's unclear if there are permissions I need to setup, etc.
🚨Error: Google Chrome browser has no bookmarks. Please add some bookmarks to continue using this command.

I do have bookmarks lol
I've tried:

restarting Raycast
uninstalling/reinstalling the Chrome Extension

Any help appreciated!
Steps To Reproduce

Install latest Raycast + Chrome Extension (note: install this using Raycast, no via browser)
Open Raycast
type 'Chrome'
Select 'Search Bookmarks' option
Press ENTER

Current Behaviour
I receive the following error:
🚨Error: Google Chrome browser has no bookmarks. Please add some bookmarks to continue using this command.

Expected Behaviour
Bookmarks are searched

Update, installing this via the browser store (as opposed to within Raycast itself) resolved this, leaving the issue in case it's worth investigating

The same problem, through the web download still can't solve

Some problem here.

me  too


Content under image

How can I add content under the image when modal is opened (a la modal-body on bootstrap)
Thanks

You can't; you can add to the footer, or use a remote link?


Add SECURITY.md to outline security issue reporting

Add a SECURITY.md file to provide guidelines for reporting security issues. This will help in the responsible disclosure of security bugs by detailing the process for reporting vulnerabilities. It includes a link to the GitHub Security Advisory for ease of access and ensures contributors are informed about the handling of their reports.

Hmm... what's broken on it? Pretty sure this: @sublinks/sublinks-frontend-service works (same format that is in the file and I didn't change those)

@lazyguru Are you seeing this if you go to review the file changes?

In the app I don't:

On the web I do though:

Found the problem:

It's the part about write access.

Found the problem:
It's the part about write access.

Great! I just found the small dots that opened the detailed explanation 😓

I guess it kind of makes sense that the group would need write access, but the idea was that I want their approval but also want to control which PRs get merged. I'll have to think on it, but for now the main change is renaming developer to owner


Documentation changes

- What I did Update the documentation in at_client_spec.dart and sync
- How I did it
- How to verify it
- Description for the changelog

The dart docs are out of date. Hence closing the PR.


Could not load dynamic library 'libcudart.so.11.0'

When I try the example script, it reports errors:

My cuda version 12.7. I would like to ask if the cuda version is required to be 11.x. Thanks a lot in advance!
Environment information:
Python: 3.10.9
CUDA: 12.7
I just create the environment following the instruction
git clone git@github.com:sail-sg/oat.git
cd oat
pip install vllm==0.6.2 && pip install -e .

Hi @MYC000801, I think cuda12 should be fine. Here are my packages when I run pip list | grep cuda:

I think your issue may be resolved by setting the LD_LIBRARY_PATH to point to your python package's lib. For me, I put this line in my ~/.zshrc (or ~/.bashrc if you do not use zsh):
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/aiops/liuzc/miniforge3/envs/oat/lib/

Ref: https://stackoverflow.com/a/21173918. Hope this helps!


Debian stretch package out of date

The apt package for Debian 9 stretch is currently version 1.0.0-1 which was released in December 2015.
Can you update the apt package please?
apt-cache show rbenv indicates that the package maintainer is Debian Ruby Extra Maintainers contactable at<EMAIL_ADDRESS>I'm unsure if I should be asking here or emailing the apt listed maintainer?

I've also just discovered that the apt package does not install ruby-build which is required to actually install new versions of Ruby.
Is it possible for this to be bundled with the apt package?

If you say about rbenv package of Debian, you can request as wishlist bug to https://bugs.debian.org/rbenv.

Sorry, I do not maintain the Debian package for rbenv. You will have to reach out to those who have initially set it up.


New release?

Hi there, librespot 0.5.0 is out, can you please run your CI/CD to produce a new build?

Just did it (will probably take at least 30 min). Doing a pre-release as iI don’t have time to test. Let me know how it goes.

The old build failed. Got it fixed by bumping the OpenWrt version to the latest but there is still an issue as the new librespot has another dependency ( bindgen-cli ).

Sorry, I missed your message somehow. I'll give it a go in the coming days

There is nothing to check the build failed. I need to fix the dependency.

for what's worth, your build/release from a few hours ago works perfectly. Thanks!

Great! Thanks for checking it out. It was a long shot as I was not sure what I was doing…
I saw there is a v0.6 - will give it a go later in the week.

Did a successful build for v0.6. I close this ticket but leave the new build as a pre-release until I have time to test it.


[DGS] Include license header in other sources

Add license header to non-java sources.
Type of request

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Refactoring
[x] Documentation or documentation changes

Related Issue(s)

Concept

Description of the change

Description of current state
Description of target state
Estimated investment / approximate investment

Initiator
name / company / position / created at
Technical information
Platform / target area

known side-effects
other
DB Changes (if so: incl. scripts with definitions and testdata)
How has this Tested?

Screenshots, Uploads, other documents (if appropriate):

Checklist:

[x] My code follows the code style of this project.

[x] I have read the CONTRIBUTING docs.
[x] I have added/updated necessary documentation (if appropriate).

The purpose of this PR was modified after #5; edited title and information. First commit should still fail, and second should pass.

@pfistererm - this is ready to review. Thank you!


Allow using the verosity flag (-v) when testing

See https://github.com/spf13/pflag/issues/65

 You should sign our Contributor License Agreement in order to get your pull request merged.

So you are using pflag without Cobra and consequently the workaround in Cobra isn't working for you.
I think this is an acceptable fix. As it only applies to shorthand flags which wouldn't work with the syntax provided, I don't see any side effects that are hindered by this.
I've squashed it into one commit and merged at cb88ea7


Create formatted documentation

Checkout some examples to get the gist of how to make a nice readme doc
https://pypi.org/project/flask-s3up/

Check out sphynx and other preset formats that can help host the documentation:
https://packaging.python.org/tutorials/creating-documentation/


Shader conversion to GLSL v3.0

Shader conversion to glsl v3.0 has a problem with the following playground https://playground.babylonjs.com/#YMZ7V3
These three lines
// varying
varying vec2 vUV
varying vec2 vPosition;

are converted to
// out out vec2 vUV;
out vec2 vPosition;

As you can see there is a missing new line between the two out words.
When you add a new line manually everything works fine.
// varying

varying vec2 vUV
varying vec2 vPosition;

Version: v3.0-alpha

Also reported here. http://www.html5gamedevs.com/topic/30388-unable-to-compile-effect-error/

The issue is coming from the replacement in the comment (varying is replaced), I am making a fix for it, during this time, you can workaround it by not placing variyng at the end of your comment line.
https://playground.babylonjs.com/#YMZ7V3#2


ERROR: Failed to resolve: com.github.kk121:File-Loader:1.2

i write dependency and syn the project
repositories {
mavenCentral()
maven { url 'https://jitpack.io' }
}
dependencies {
implementation 'com.github.kk121:File-Loader:1.2'
}

Hi, did you found some fix for this???

You should add maven's to allprojects repositories, and it should looks like this:
allprojects { repositories {         ***         mavenCentral()         maven { url 'https://maven.google.com' }     }
Sometimes poeple are misinformed and add it to buildscript.

As stated in this tutorial; https://blog.mindorks.com/how-to-open-a-pdf-file-in-android-programmatically You can define repositories like this;
repositories {
    google()
    jcenter()
    maven {url "https://jitpack.io"}//add this line
}

yes i founded solution thanks for support


Update fortigate-ssl-vpn-tutorial.md

Attempting to update the NOTE below.
Note
These values are just patterns. You need to use the actual Sign on URL, Identifier, Reply URL, and Logout URL. Contact the FortiGate SSL VPN client support team<EMAIL_ADDRESS>to get the actual values. You can also refer to the patterns shown in the Basic SAML Configuration section in the Azure portal.
needs to be changed to something like:
Note
These values are just patterns. You need to use the actual Sign on URL, Identifier, Reply URL, and Logout URL. Contact the Fortinet support  (=https://support.fortinet.com) for guidance. You can also refer to the example patterns shown in the Fortinet doc and the Basic SAML Configuration section in the Azure portal.

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

@Kherzog-FTNT - I've cleaned up the markdown. Should be good now.
@jeevansd - can you take a look and approve if if look good to you? Thanks.

#sign-off


Changes to Cosmos client for ATOM

The only problem we encountered with xchainjs, is having api.cosmos.network being CORS restricted.
We therefore implemented our own API into the client.
We also set the default amount for the DEFAULT_FEE  for transactions. Should I include those changes as well?

Feedback, in any way, very welcome!

Closing in favour of #599


import and export base. creating backups.

I think it will be in demand

Upgrade, Backup, and Restore
Database Upgrade
The recommended way to upgrade from one version of the database engine to the next version is to create a backup of the database (in the form of a SQL script) using the old engine, and then execute the SQL script using the new engine.
Backup using the Script Tool
The recommended way to backup a database is to create a compressed SQL script file. This will result in a small, human readable, and database version independent backup. Creating the script will also verify the checksums of the database file. The Script tool is ran as follows:
java org.h2.tools.Script -url jdbc:h2:~/test -user sa -script test.zip -options compression zip

It is also possible to use the SQL command SCRIPT to create the backup of the database. For more information about the options, see the SQL command SCRIPT. The backup can be done remotely, however the file will be created on the server side. The built in FTP server could be used to retrieve the file from the server.
Restore from a Script
To restore a database from a SQL script file, you can use the RunScript tool:
java org.h2.tools.RunScript -url jdbc:h2:~/test -user sa -script test.zip -options compression zip

For more information about the options, see the SQL command RUNSCRIPT. The restore can be done remotely, however the file needs to be on the server side. The built in FTP server could be used to copy the file to the server. It is also possible to use the SQL command RUNSCRIPT to execute a SQL script. SQL script files may contain references to other script files, in the form of RUNSCRIPT commands. However, when using the server mode, the references script files need to be available on the server side.
Online Backup
The BACKUP SQL statement and the Backup tool both create a zip file with the database file. However, the contents of this file are not human readable.
The resulting backup is transactionally consistent, meaning the consistency and atomicity rules apply.
BACKUP TO 'backup.zip'

The Backup tool (org.h2.tools.Backup) can not be used to create a online backup; the database must not be in use while running this program.
Creating a backup by copying the database files while the database is running is not supported, except if the file systems support creating snapshots. With other file systems, it can't be guaranteed that the data is copied in the right order.

@arturmon backup and restore feature added.
https://github.com/mycontroller-org/mycontroller/commit/d2d41e6bd36abec09319f792cf9ddc1fb741c53d

[image: Встроенное изображение 1]
2016-02-17 1:37 GMT+03:00 Jeeva Kandasamy<EMAIL_ADDRESS>
Closed #59 https://github.com/mycontroller-org/mycontroller/issues/59.
—
Reply to this email directly or view it on GitHub
https://github.com/mycontroller-org/mycontroller/issues/59#event-552752410
.


Remove point node from label annotation

Fix #556

I noticed you used the point extensively in #553, are you sure? :)

Well, I thought that the point implementation in the label was done because I'm personally still convinced that the point could be important to be highlighted but, playing with samples, I discovered can a user could want to highlight the point with different shapes or with another annotation, therefore I think to have a point as possible options has got more cons than pro (mainly duplication code and config).
I'm learning step by step... Sorry.

I wait to merge for the decision about the other PR about position options, about percentage about number, in order to rebase the other PR going to the shared decision.


cookie parsing containing a = in value

https://github.com/30-seconds/30-seconds-of-code/blob/master/snippets/js/s/parse-cookie.md
if a cookie value contains an = would this break

const parseCookie = (str) =>
  str
    .split(';')
    .map((v) => {
      const equalSignIndex = v.indexOf('=');
      const name = v.substr(0, equalSignIndex).trim();
      const value = v.substr(equalSignIndex + 1).trim();
      return [name, value];
    })
    .reduce((acc, [name, value]) => {
      acc[decodeURIComponent(name)] = decodeURIComponent(value);
      return acc;
    }, {});

const parseCookie = str => str .split(/;\s(?![^=]+=[^=]+)/) // Split only on semicolons followed by a space, not preceded by an equal sign .map(v => v.split('=')) .reduce((acc, v) => { acc[decodeURIComponent(v[0].trim())] = decodeURIComponent(v[1].trim()); return acc; }, {});

console.log(parseCookie('foo=bar; equation=E%3Dmc%5E2'))
//{ foo: "bar; equation" }

To avoid this problem, you should encode any = characters in cookie values using the encodeURIComponent() function.
document.cookie = foo=${encodeURIComponent('foo=bar')};

Thanks for opening an issue about this. As shown in the example below the code, if properly encoded, = is not going to be a problem. parseCookie is meant to be used in combination with serializeCookie, explaining the "correct" way to store and retrieve cookie values.


fix Issue 16307 - [ndslice] should be safe

I don't have the power to merge or reject PRs but I would personally not accept a PR that marked large swathes of code like this @trusted.

.slice.Slice trusted, except only one methods that are designed for interaction with other libraries such as NumPy. They are ptr and this, all other methods must be save or must not be added into the structure.
.iteration & .selection - safe transformations on lengths and strides by definition. They must not manage pointers or underlaying ranges. The concept of ndslice and Mir library is to split system code from math code.

As strong a veto as I can have, we cannot accept @trusted: anywhere in any file.
The proper mechanism for templates is to mark the parts @trusted that should be with escapes, and let the compiler infer the @safe tag on the function itself. Mark your unittests as @safe to ensure they are being correctly inferred.

Yeah, I'm very uncomfortable with marking large swathes of code as @trusted. There is just too much room for error.  Generally, @trusted should be avoided as much as possible, and confined to as small a fragment of code as possible, so that it's easier to review and verify its trustworthiness.
Putting @safe: at the top of the module is OK, but definitely not @trusted:. Perhaps one approach is to put @safe: at the top and then narrow down exactly which parts of the code fail to compile, and either fix them or add appropriate @trusted helpers.
I'd also say that marking an entire function as @trusted is also suspect, unless the function is small. Marking template functions as @trusted is especially suspect, because the template arguments may contain @system primitives from user code that's beyond your control, and it would be very bad to have @trusted apply to such arbitrary code.
If a function needs to do @system operations but you're sure it can be trusted, the piece of code that performs said operations should be wrapped in a @trusted lambda, and we need to be absolutely sure that this code will never invoke anything outside its control, like a user-supplied type that may contain arbitrary code in @system methods.

I'd also say that marking an entire function as @trusted is also suspect, unless the function is small.

This I don't necessarily agree with. One trap to be careful to avoid is to do operations in @trusted escapes that affect data outside the trusted escape in such a way that the entire function becomes essentially trusted, but not marked as such. This is very dangerous as well.

@schveiguy I agree. That is why @trusted fragments of code must be as small as possible, otherwise it's impractical to verify that it's not actually doing something unsafe with stuff in its context, like affecting variables outside the trusted lambda in ways that "taint" the code outside.
If the entire function (or worse, module) is marked @trusted, you basically have no practical way to verify that it's actually trustworthy because there'd be too many places for untrustworthy code to hide.
Of course, just because the trusted fragment is small is no guarantee that it's actually OK. It needs to be as self-contained as possible, preferably touching as few things as possible outside of its own scope.  Because of that I'd say, any @trusted lambda that manipulates user-supplied template types is suspect. There is no way to guarantee the user-supplied type doesn't do all sorts of nasty things behind your back -- you have no control over what the user-supplied type does.
In the case of this module, the only obvious thing that I can think of that might require @trusted is pointer arithmetic involving slices. This should be very self-contained and more-or-less independent of template arguments -- so anything in this module that directly references a template type from inside a trusted lambda, I'd consider as suspect, or at the very least deserving of thorough scrutiny.

ndslice is used on top of raw pointers in real live, because this works faster then ndslices on top of arrays.

@9il pointer arithmetic is fine. but should be escaped with @trusted lambdas instead of blanket @trusted: blocks.
It's also OK to mark entire functions as @trusted if warranted, but on an individual basis, not the entire module.

OK, just have another more important PRs for ndslice. Will open PR for trusted later


add autofocus to #search-bar-input

Hey @wijaksanapanji Thanks for the PR.
I had already added a line of code in the JS to add focus to the search bar but it doesn't work because the browser overrides that to put the focus on the top bar instead.
So, did you try this implementation locally? An by locally I mean by installing the extension and checking if the focus is on the search bar if a new tab page is installed.?
Once you confirm that, I'll merge.

@deepjyoti30 what I tried is clone the repo, edit the index.html and open the index.html on firefox and chrome, and it's seem to autofocus on the search input

@wijaksanapanji I'm sure that won't work since I'm already doing that from JS. Anyway, if you can test and confirm it's working I can still merge.

@deepjyoti30 hmm you are right, I just notice that, sorry, I will close the PR.


Refresh not being called on the first element after the first time

My testing seems to be showing that the Refresh override method is not getting called on the first element beyond when the carousel is initialised. Each cell after that has Refresh called as you scroll from one to the other, but going back to the first element does not fire it. I suspect the issue is deeper and in FancyScrollView though. Possibly the UpdateCells method

On top of this, possibly related?, the OnVisibilityChanged callback only seems to be happening for the second item and ONLY with going back to the first element. I cannot find a reliable way, within my CarouselCell class, to know when an element is the "current" one and when it's not. I need some, for example, to play audio while they're the current one and stop it once they're not.

But the last element, when dragged as if there might be another element beyond it, triggers the visibility changed with a false value every time. But NOT when dragged back to the second last element. Am I missing something about this callback and when it should be fired?

Also, the CarouselView.CarouseCellVisibilityChanged callback seems to never be called as far as I can tell. The only thing that seems to be reliable is the CarouselView.ActiveCellChanged callback which only gives an index of the new active cell and is useless for doing anything on the actual CellView

First, can this be reproduced in my demo?
After reading the entire text above, I understand that your issue consists of the following four points:

Refresh is not called correctly.
OnVisibilityChanged is not called correctly.
There is no way to distinguish whether it is the "current" cell.
CarouselView.CarouseCellVisibilityChanged is not called.

For points 1, 2, and 4, I could not reproduce them in my demo.
If you can reproduce them in my demo, please provide the steps to do so.
If you cannot reproduce them in my demo, please provide an another minimal project that can.
Please also let me know the version of FancyScrollView.
For point 3, please implement it as follows:
FancyCarouselView carouselView;
carouselView.CarouselCellVisibilityChanged += (cell, visibility) =>
{
    // Use carouselView.ActiveCellIndex here
};

However, it's not possible for the library to accurately determine what is considered your "current" cell.
(For example, if there are always 5 cells visible on the screen, which one is the "current" cell?)

I have tried using that callback, it isn't always called. I will take a look at your demo and see, but I am having a heck of a time getting accurate callbacks. I have just one cell on screen at a time and the timing of callbacks is all over the place for me. I'll take a look at the demo

I added a _carouselView.CarouselCellVisibilityChanged listener in your Demo script and it's never called.
I added some logging into the other methods, and it looks like my issue is that in my carousel, i don't quite have the cells the full width of the screen. Because I don't know what the screen might be, If I do manually set it to the size of the container, I see the results I need with respect to the refresh and visibility calls. But the top level CarouselCellVisibilityChanged callback doesn't seem to happen.

However, considering things like CarouselCellInstantiated, it's still better to register the callback before Setup.

I see, I didn't know to do that, I'll try registering all the callbacks before Setup. Thanks

Did it work well?
Regarding the order of registering callbacks, it is unclear, so I will add it to the documentation later.


Allen & Heath Avantis integration

Hi, I'm looking for a way to integrate an Avantis console with Companion to trigger scenes.

@Bambii556 are you done with this module? Does it work?


Fix typos in Ukrainian translation

Typos was in levels: intro1, intro2.

hrm, im guessing that the build failure was just transient. will monitor upon merge. thanks again :tada:

yeah:

Finished in 2.576 seconds
126 tests, 113 assertions, 0 failures, 0 skipped

(node) util.print is deprecated. Use console.log instead.

Done, without errors.


ETA for training

Hi team,
I would like to know if there is a way to know the estimated time for the lumi train -c config.yaml method. AFAICT, I created a dataset contains 7809 images (coco style), and the config.yaml is
train:
  # Run name for the training session.
  run_name: my_run
  job_dir: jobs
  learning_rate:
    decay_method: piecewise_constant
    # Custom dataset for Luminoth Tutorial
    boundaries: [90000, 160000, 250000]
    values: [0.0003, 0.0001, 0.00003, 0.00001]
dataset:
  type: object_detection
  dir: tf
model:
  type: fasterrcnn
  network:
    num_classes: 13

I run the training on CPU (Intel(R) Core(TM) i7-7600U CPU @ 2.80GHz), and here is a sample output
INFO:tensorflow:Saving checkpoints for 20689 into jobs/my_run/model.ckpt.
INFO:tensorflow:step: 20689, file: JPEGImages/cap198.jpg, train_loss: 1.96116948128, in 20.54s
INFO:tensorflow:step: 20690, file: JPEGImages/cap541.jpg, train_loss: 2.02766418457, in 27.07s
INFO:tensorflow:step: 20691, file: JPEGImages/cap220.jpg, train_loss: 1.91760718822, in 24.67s
INFO:tensorflow:step: 20692, file: JPEGImages/cap299.jpg, train_loss: 2.05084943771, in 21.31s

It is running before 4 days ago, is this expected and how can I know how much remaining (if possible)?
Thanks a million,
Mughrabi

Instead of using CPU, I used GCloud based on the https://luminoth.readthedocs.io/en/latest/usage/cloud.html. It is running from 2 days ago.
I 2019-09-16T19:41:32.707196950Z master-replica-0 [master-0] - step: 138172, file: JPEGImages/cap036.jpg, train_loss: 1.38995575905, in 1.12s master-replica-0
I 2019-09-16T19:41:33.865154027Z master-replica-0 [master-0] - step: 138173, file: JPEGImages/cap624.jpg, train_loss: 1.34886920452, in 1.16s master-replica-0

Can you please advise how to know the remaining time for the training to be completed? am I falling in an infinite loop?

Can you please advise how to know the remaining time for the training to be completed? am I falling in an infinite loop?

I found a way to compute it!

Assume that the batch_size is B, the average time spent for 1 step is S, the number of epochs is 'P' in seconds.
The initial ETA is (P / B) * S in seconds.


Invalid source release error

When I try to run an app I got this error (I0m using version 1.1.1):
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':screen_protector:compileDebugJavaWithJavac'.

invalid source release: 11

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 8s
Running Gradle task 'assembleDebug'...                              8.8s
Exception: Gradle task assembleDebug failed with exit code 1
This is the output of flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.0.2, on Linux Mint 20.3 5.4.0-120-generic, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Linux toolchain - develop for Linux desktop
[!] Android Studio (not installed)
[✓] VS Code (version 1.68.1)
[✓] Connected device (2 available)
[✓] HTTP Host Availability
! Doctor found issues in 2 categories.
In build.grade I have this
...
compileSdkVersion 31
compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}

kotlinOptions {
    jvmTarget = '1.8'
}

defaultConfig {
...
minSdkVersion 21
targetSdkVersion flutter.targetSdkVersion
versionCode flutterVersionCode.toInteger()
versionName flutterVersionName
}
...

Have the same error.

Have the same error.
  ] * What went wrong:
[        ] Could not determine the dependencies of task ':screen_protector:compileDebugAidl'.
[        ] > Could not resolve all task dependencies for configuration ':screen_protector:debugCompileClasspath'.
[        ]    > Could not find com.github.prongbang:screen-protector:1.0.0.
[        ]      Required by:
[        ]          project :screen_protector
[        ] * Try:
[        ] Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
[        ] * Get more help at https://help.gradle.org
[        ] BUILD FAILED in 45s

I also have this problem, Were you able to find a solution?

@ArielM24 Were you able to find a solution?

@ArielM24 Were you able to find a solution?
in android/build.grade I had this lines comment this lines and add the maven url

allprojects {
repositories {
google()
mavenCentral()
maven { url 'https://jitpack.io/' }
}
//tasks.withType(JavaCompile).configureEach {
//     javaCompiler = javaToolchains.compilerFor {
//       languageVersion = JavaLanguageVersion.of(8)
//    }
// }
}

Fixed 1.1.5
Thank you for report 👍


feat: multiple custom protocols

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[x] Yes. Issue #___
[ ] No

The PR fulfills these requirements:

[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix: #xxx[,#xxx], where "xxx" is the issue number)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

This is so awesome!
Do the custom protocols get handled as proper origins by the browser?

It is on Windows last time I checked it. But on macOS there are some subtle issues.
I believe this is also something to do with #85


Downstream changes

This brings in all the rebased downstream changes. This still needs some cleanup.

I think it's good now, I'll do a final squash and testing pass tomorrow and merge it.


feat: add support for Apple Silicon chromium builds

Google has published Chromium builds for Apple Silicon so we can fetch it now
Related to https://github.com/puppeteer/puppeteer/issues/6622

@googlebot I signed it!

I got 3 tests failed, but not sure that it's related to this PR
  1) Accessibility
       roledescription:
     Error: expect(received).toEqual(expected) // deep equality

Expected: "foo"
Received: undefined
      at Context.<anonymous> (test/accessibility.spec.ts:171:50)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)

  2) network
       Response.fromCache
         should work:
     Error: expect(received).toBe(expected) // Object.is equality

Expected: 304
Received: 200
      at Context.<anonymous> (test/network.spec.ts:166:56)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)

  3) network
       Page.authenticate
         should not disable caching:
     Error: expect(received).toBe(expected) // Object.is equality

Expected: 304
Received: 200
      at Context.<anonymous> (test/network.spec.ts:606:56)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)

I can confirm that the three test failures you described are related to Chromium changes that we haven't rolled into Puppeteer yet.

The change looks good to me from a technical standpoint but we'll have to wait for the next Chromium roll to land it.
That one is currently blocked on some network related changes but I'll make sure to include this change with the next roll.
Thanks so much for your contribution!

Sure! Feel free to ping me. Thanks

Any chance to merge this PR?
Related issue - https://github.com/puppeteer/puppeteer/issues/7632

Would love to see this land. As an alternative approach, would anyone be opposed to this function searching PATH for chromium? In our case brew install chromium drops it in /opt/homebrew/bin/chromium per Homebrew on Apple Silicon.

any progress ?

@jschfflr as I understand, we are not blocked anymore. Should I update PR?
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/938248/
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac_Arm/938248/

Also, as I understand, it would be nice to test against MacOS ARM? But it's currently blocked by https://github.com/actions/virtual-environments/issues/2187

Let's wait for GitHub Actions to support it or can we land it as an experimental opt-in feature?

@OrKoN honestly I prefer to release it as an opt-in because we don't really have any timeline for GitHub Actions release. Maybe we can download the ARM version only if env variables set? Something like PUPPETEER_CHROMIUM_ARM?

yes, I think an env var would work. Perhaps PUPPETEER_EXPERIMENTAL_CHROMIUM_MAC_ARM?

I will update PR on this weekend or next week

@OrKoN does it look good?
Also I checked that the current chrome version exists https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac_Arm/961656/

Some errors seem to be related to the Firefox binaries.

Is there any updates?

Will try to finish it on next week

Hi. Can I test if this change actually solve my problem? Until it merged… Is there a version i can install in package.json to test it?

@OrKoN could you trigger actions please?

11 tests failed within `npm run unit`
  1) Emulation
       Page.emulateCPUThrottling
         should change the CPU throttling rate successfully:
     Error: Timeout of 25000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/v7rulnik/projects/oss/puppeteer/test/emulation.spec.ts)
      at listOnTimeout (internal/timers.js:557:17)
      at processTimers (internal/timers.js:500:7)

  2) headful tests
       HEADFUL
         background_page target type should be available:
     Error: Failed to launch the browser process!
assertion failed [precise_state_mode == PreciseStateMode::UpdateLiveState]: not updating live register state but no fpr state passed in
(ThreadContextRegisterState.cpp:559 move_to_instruction_boundary)

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

      at onClose (src/node/BrowserRunner.ts:268:9)
      at ChildProcess.<anonymous> (src/node/BrowserRunner.ts:255:61)
      at ChildProcess.emit (domain.js:470:12)
      at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)

  3) Mouse
       should send mouse wheel events:
     Error: expect(received).toMatchObject(expected)

- Expected  - 2
+ Received  + 2

  Object {
-   "height": 230,
-   "width": 230,
+   "height": 345,
+   "width": 345,
  }
      at Context.<anonymous> (test/mouse.spec.ts:198:30)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)

  4) Screenshots
       ElementHandle.screenshot
         should take into account padding and border:
     Error: screenshot-element-padding-border.png mismatch! Output is saved in "output-chromium" directory
      at Context.<anonymous> (test/screenshot.spec.ts:215:26)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)

  5) Screenshots
       ElementHandle.screenshot
         should capture full element when larger than viewport:
     Error: screenshot-element-larger-than-viewport.png mismatch! Output is saved in "output-chromium" directory
      at Context.<anonymous> (test/screenshot.spec.ts:241:28)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)

  6) Screenshots
       ElementHandle.screenshot
         should scroll element into view:
     Error: screenshot-element-scrolled-into-view.png mismatch! Output is saved in "output-chromium" directory
      at Context.<anonymous> (test/screenshot.spec.ts:276:26)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)

  7) Screenshots
       ElementHandle.screenshot
         should work for an element with fractional dimensions:
     Error: screenshot-element-fractional.png mismatch! Output is saved in "output-chromium" directory
      at Context.<anonymous> (test/screenshot.spec.ts:327:26)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)

  8) Screenshots
       ElementHandle.screenshot
         should work for an element with an offset:
     Error: screenshot-element-fractional-offset.png mismatch! Output is saved in "output-chromium" directory
      at Context.<anonymous> (test/screenshot.spec.ts:337:26)
      at runMicrotasks (<anonymous>)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)

  9) Tracing
       should output a trace:
     Error: Timeout of 25000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/v7rulnik/projects/oss/puppeteer/test/tracing.spec.ts)
      at listOnTimeout (internal/timers.js:557:17)
      at processTimers (internal/timers.js:500:7)

  10) Tracing
       should work without options:
     Error: Timeout of 25000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/v7rulnik/projects/oss/puppeteer/test/tracing.spec.ts)
      at listOnTimeout (internal/timers.js:557:17)
      at processTimers (internal/timers.js:500:7)

  11) Tracing
       should support a buffer without a path:
     Error: Timeout of 25000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/v7rulnik/projects/oss/puppeteer/test/tracing.spec.ts)
      at listOnTimeout (internal/timers.js:557:17)
      at processTimers (internal/timers.js:500:7)

@OrKoN I think I found a bug. Could you trigger one more time, please?

Looks good, thanks for the contribution! May I ask you to update the documentation please? E.g., I could think of mentioning the new flag as experimental here https://github.com/puppeteer/puppeteer/blob/main/docs/api.md#environment-variables

@OrKoN added some info to docs/api.md and to contributing.md Feel free to change wordings if they are not correct

Great to see this close to landing.
I'm guessing this won't help people running puppeteer in Docker on Apple Silicon?
https://github.com/garris/BackstopJS/issues/1300
Are there Arm builds of Chromium for Debian running in Docker?

@cdeutsch I am not aware of Arm builds for Debian that are available for download (but I might just not know)
@7rulnik thanks for the PR, it looks good  to me!

Was this one supposed to fix https://github.com/puppeteer/puppeteer/issues/7916 ?

@artyil nope. It's not related to any Linux (inside docker too) at all. Just native M1.

@7rulnik the referred issue is related to m1 only - “[Bug]: Docker M1 Mac fails to open new page (Target.createTarget) #7916”
Can you elaborate what am I missing there?

@artyil this PR is related only to M1. This https://github.com/puppeteer/puppeteer/pull/7546 issue is about docker so it's about chromium and puppeteer on Linux. Also I see this comment https://github.com/puppeteer/puppeteer/issues/7916#issuecomment-1060034559 and looks like in this case it's about native run (without docker) too, but I'm not sure. WIll try to run example from it.


GetSystemInfoAsync() doesn't work!

Hello I'm trying to get docker.net to work
I want to get info, like the command: docker info
I've tryed: info = client.Miscellaneous.GetSystemInfoAsync().Result;
also tryed running my program (and VS) with admin rights but it still don't work,
i get no exceptions the programs doesn't terminate :'(
However await client.Miscellaneous.PingAsync(); works

That is weird @Raffa50
If you put it in a try/catch it still not throw an exception? I'm using this method without problems...

yeah it was in a try catch... maybe is my pc... it needs a cleanup? I'll try on my other pc

It works in a console application, but not in a Windows Forms Application, you know why?

solved: function that communicate with docker need to run on a different thread (not form thread)
a backgroundworker is fine!

@Raffa50 that is weird... There are XXXAsync() methods which should be fine to be called from the main thread, as long as you make the method async and call with await XXXAsync().
What may be happening with you, is that you are calling XXXAsync().Wait() or XXXAsync().Result. That will block the current thread.

What may be happening with you, is that you are calling XXXAsync().Wait() or XXXAsync().Result. That will block the current thread.

That's what he's doing wrong
op:

I've tryed: info = client.Miscellaneous.GetSystemInfoAsync().Result;


Error with terraform rules (multiple)

Error with some rules

Specifications

docker image checkmarx/kics:latest v1.3.0

@jonny-wg2 hello, I'm hope you're doing well. Could you elaborate what kind of problems are happening with those queries? Also, if it is possible, could you provide an example the scenario they happens?

I'm closing this as stale, @jonny-wg2 can reopen providing additional info.


Add and test NordLEI witness/vlei-server configuration

The vlei-verifier verification service has been configured with the NordLEI witnesses provided by Daniel and deployed in the test environment.

We are including all public witnesses in combination here https://github.com/GLEIF-IT/vlei-verifier/blob/main/scripts/keri/cf/verifier-config-public.json