entt symbols are not exported with MinGW64

When exporting symbols from an executable with MinGW64 on Windows nothing is exported.
The main reason is that class functions are implemented within classes, for example:
struct ENTT_API type_seq final {
    [[nodiscard]] static id_type next() ENTT_NOEXCEPT {
        static ENTT_MAYBE_ATOMIC(id_type) value{};
        return value++;
    }
};

This SO answer mentions, that:

C++ functions implemented inside of a class declaration are automatically defined inline.

So there is an inconsistency (at least in MinGW64):

for shared libraries the symbols are exported
for executables the symbols are inlined and not exported
for executables and in-class implemented functions that are explicitly marked dllexport the symbols are also exported.

I know that there are workarounds to just compile entt as a dll, or maybe set a noinline option , etc. But I really would like to avoid that.
For example, I have a core application that loads plugins, and those plugins are using symbols exported from the core executable.

according to mingw documentation regarding dllexport:

When applied to C++ classes, the attribute marks defined non-inlined member functions and static data members as exports. Static consts initialized in-class are not marked unless they are also defined out-of-class.

It is not clear though what it implies about non-inlined functions: whether they are marked inline by user or inlined by compiler.
I tried to compile a dll that includes entt/entt.h, but nothing is exported whatsoever.

Unfortunately, this stuff is not regulated by the standard. So, roughly speaking, it's chaos and nothing more. 😄

C++ functions implemented inside of a class declaration are automatically defined inline.

That's true. However, the dll export directive should inhibit the inlining for itself. That's how it works with all major compilers.
Out of curiosity, do you pass ENTT_API_EXPORT and ENTT_API_IMPORT during compilation? Otherwise ENTT_API isn't defined and this would explain the inlining. Also, have you tried the -fvisibility flag or equivalent with mingw?

I compile core with ENTT_API_EXPORT  and plugins with ENTT_API_IMPORT. Though the symbols are not exported. If I explicitly mark class methods for dllexport, the symbols are exported. Also I opened a bug report.

Ironically, I remember that I had to move the dll export/import tag at class level because of an ICE with a version of MSVC.
So, honestly, I don't even know how to help here without risking to break existing code. It seems an idiosyncrasy of mingw but it's also the first time it's been reported.

I suppose then I will fork for now and introduce some workaround macro explicitly for mingw...
I am not sure though that I am doing it right. In the wiki it is mentioned that a meta context could be passed to a plugin. Does it mean that a plugin would use a pointer to to static variables within a core that exposes that meta context?
For now I have a code for a plugin that gets a pointer to the registry from the core. But gdb says that type_seq::next() used is within the dll, not the core.
#include "export_types.h"

extern "C"
{
    void initialize(const entt::registry* );
    void say_msg();
}

#include <iostream>

static const msg_struct *msgStruct = nullptr;

void initialize(const entt::registry *pRegistry)
{
    auto view = pRegistry->view<const msg_struct>();

    // if (!view.size_hint()) // does not compile: "has no member size_hint"
    if (!std::distance(view.begin(), view.end()))
    {
        std::cerr << "Plugin: no msg entities found!" << std::endl;
        return;
    }

    msgStruct = std::addressof(view.get<const msg_struct>(view.front()));
}

void say_msg()
{
    if (!msgStruct)
    {
        std::cerr << "Plugin: entity was not registered" << std::endl;
        return;
    }

    std::cout << msgStruct->msg << std::endl;
}

The only valid solution to use symbols with one definition is to make a custom impl.hpp header that would include headers with implementations. If one would like to compile the lib as a standalone module,  one would include that source once in his .cpp file.
In ASIO  this looks like:
//
// impl/src.hpp
// ~~~~~~~~~~~~
//
// Copyright (c) 2003-2021 Christopher M. Kohlhoff (chris at kohlhoff dot com)
//
// Distributed under the Boost Software License, Version 1.0. (See accompanying
// file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
//

#ifndef ASIO_IMPL_SRC_HPP
#define ASIO_IMPL_SRC_HPP

#define ASIO_SOURCE

#include "asio/detail/config.hpp"

#if defined(ASIO_HEADER_ONLY)
# error Do not compile Asio library source with ASIO_HEADER_ONLY defined
#endif

#include "asio/impl/error.ipp"
#include "asio/impl/error_code.ipp"
#include "asio/impl/execution_context.ipp"
#include "asio/impl/executor.ipp"
#include "asio/impl/handler_alloc_hook.ipp"
#include "asio/impl/io_context.ipp"
...

That, of course, means, there needs to be a series of implementation headers.

Honestly, I'd try to get why mingw behaves differently from everyone else rather than messing up the entire library to please it.
Also, what symbols are we talking about? If I understand correctly, only the id generator interests you, right?

I am not sure that it is the only thing that interests me, maybe there are other symbols I am not aware of yet.
The goal is to preserve the core ABI when adding new components (and not removing or modifying the existing), so the existing plugins would still work.

I've checked with MSVC and debugger - the type_seq::next that is invoked from within the dynamically loaded plugin is found inside the core executable:
(lldb) image lookup --address 0x00007ff7f2cc97f0
      Address: sb.entt_core.exe[0x00000001400197f0] (sb.entt_core.exe...text + 100336)
      Summary: sb.entt_core.exe`entt::internal::type_seq::next() at type_info.hpp:26

That means that MSVC does export in-class implemented (inlined, I guess) functions and successfully imports them.
I've decided to check with Clang. Just like MSVC it did exported symbols and created a static lib, which was successfully linked with plugins. I thought that it is indeed the MinGW, who misbehaves among the mainstream compilers. But nevertheless I checked the symbols. And I found out that it only seem to work.
This is the address of a symbol when invoked from within the core exe:
(gdb) info sym 0x00007ff691b83010
entt::internal::type_seq::next() in section .text of C:\dev\repos\entt_test\cmake-build-debug-clang64\sb.entt_core.exe

But regardless of exported symbols and successful linkage, the plugin has violated ODR:
(gdb) info sym 0x00007ffc6d3a2170
entt::internal::type_seq::next() in section .text of C:\dev\repos\entt_test\cmake-build-debug-clang64\libsb.entt_plugin.dll

As you can see, MinGW is not the only one who needs to be pleased...
On the other hand, I don't see how a compiler would understand, that it does not have to compile a function for a plugin, when it sees that function has an inline implementation.
Consider this:
struct __declspec(dllimport) type_seq final {
    [[nodiscard]] static id_type next() ENTT_NOEXCEPT {
        static ENTT_MAYBE_ATOMIC(id_type) value{};
        return value++;
    }
};

How is a compiler to know, that next() need not to be compiled? My wild guess is that it does compile the definition for type_seq::next(). And eventually it works because the linker maybe eliminates duplicated symbols.
The only way to check it is to look inside .obj files for identical symbols. If this is the case, I think separating implementation from declaration to different headers would be inevitable if one would want to share symbols across modules.

Technically speaking, no one violates the ODR here since the standard doesn't take in consideration the fact that we use libraries in the real world and therefore it doesn't rule about them. 😄
Anyway, from your description I don't get if you're linking to the main executable or blindly loading a plugin. Those are very different cases and ask for different approaches. In any case, the lib dir contains examples for all them and I'm pretty sure that things work as expected with all major compilers (that is, the ones supported by this library, but I can't speak for mingw honestly, even though it seems on the wrong side of the fence here).
My suspect is that you're hitting that infamous problem due to static stuff which is not regulated by the standard and hasn't a common behavior on all platforms. If this is the case, things should change soon as mentioned here since I plan to switch to a static-less solution. In the meantime, you can use a type context map as pointed out in the same comment (or any other solution that centralizes the id generation, direct indexing is still faster than name based lookups and that's why I'm spending lot of time to find the best approach so as not to sacrifice performance).

On the other hand, I don't see how a compiler would understand, that it does not have to compile a function for a plugin, when it sees that function has an inline implementation.

The compiler doesn't really care about it. The linker discards a symbol eventually. Otherwise all sides of a boundary will have their own copy of a static variable or whatever. That's how things work on all platforms. What changes is usually the default visibility and whatnot.

I think separating implementation from declaration to different headers would be inevitable if one would want to share symbols across modules.

It won't be because you would have to mark the external implementations as inline to guarantee backward compatibility. So, the next step would be to make an optional ENTT_INLINE tag or similar to also disable it on need.
In any case, all this won't solve any issue because, yeah, things just work across boundaries already and in many projects, so probably the issue isn't that we need to split them. On the other side, it will complicate everything by several order of magnitude and make the whole thing very hard to maintain and to extend.
Therefore, I don't think this will happen any time soon. I'm sorry. 🙂

After a fair amount of attempts and research I figured out the way to make it work with MinGW64.
Basically one has to create a shared library with exported symbols. Something like:
// export_types.cpp
#include "export_types.h"

template struct entt::type_seq<bar_0>;
template struct entt::type_seq<msg_struct>;

// export_types.h
#pragma once

#include <entt/entt.hpp>

struct bar_0{};

struct msg_struct
{
    char msg[256]{};
};
extern template struct entt::type_seq<bar_0>;
extern template struct entt::type_seq<msg_struct>;

In this case it does work with MinGW64 and Clang.  However, MSVC will fail:
When compiling export lib I get warnings:
[ 50%] Building CXX object original/CMakeFiles/export_lib.dir/export_lib.cpp.obj
export_lib.cpp
C:\dev\repos\entt_test\original\export_types.h(14): warning C4910: 'entt::type_seq<bar_0,void>': '__declspec(dllexport)' and 'extern' are incompatible on an explicit instantiation
C:\dev\repos\entt_test\original\export_types.h(15): warning C4910: 'entt::type_seq<msg_struct,void>': '__declspec(dllexport)' and 'extern' are incompatible on an explicit instantiation
[100%] Linking CXX shared library export_lib.dll
[100%] Built target export_lib

When trying to link a plugin against exported lib, I get unresolved symbols:
LINK Pass 1: command "C:\PROGRA~2\MICROS~1\2019\COMMUN~1\VC\Tools\MSVC\1427~1.291\bin\Hostx64\x64\link.exe /nologo @CMakeFiles\sb.entt_plugin_original.dir\objects1.rsp /out:sb.entt_plugin_original.dll /implib:sb.entt_plugin_original.lib /pdb:C:\dev\repos\entt_test\cmake-build-debug-visual-studio\original\sb.entt_plugin_original.pdb /dll /version:0.0 /machine:x64 /debug /INCREMENTAL export_lib.lib kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:CMakeFiles\sb.entt_plugin_original.dir/intermediate.manifest CMakeFiles\sb.entt_plugin_original.dir/manifest.res" failed (exit code 1120) with the following output:
   Creating library sb.entt_plugin_original.lib and object sb.entt_plugin_original.exp
plugin.cpp.obj : error LNK2019: unresolved external symbol "__declspec(dllimport) public: static unsigned int __cdecl entt::type_seq<class entt::sigh_storage_mixin<class entt::basic_storage<enum entt::entity,struct msg_struct,class std::allocator<struct msg_struct>,void> >,void>::value(void)" (__imp_?value@?$type_seq@V?$sigh_storage_mixin@V?$basic_storage@W4entity@entt@@Umsg_struct@@V?$allocator@Umsg_struct@@@std@@X@entt@@@entt@@X@entt@@SAIXZ) referenced in function "class entt::type_info __cdecl entt::type_id<class entt::sigh_storage_mixin<class entt::basic_storage<enum entt::entity,struct msg_struct,class std::allocator<struct msg_struct>,void> > >(void)" (??$type_id@V?$sigh_storage_mixin@V?$basic_storage@W4entity@entt@@Umsg_struct@@V?$allocator@Umsg_struct@@@std@@X@entt@@@entt@@@entt@@YA?AVtype_info@0@XZ)
  Hint on symbols that are defined and could potentially match:
    "__declspec(dllimport) public: static unsigned int __cdecl entt::type_seq<struct msg_struct,void>::value(void)" (__imp_?value@?$type_seq@Umsg_struct@@X@entt@@SAIXZ)
sb.entt_plugin_original.dll : fatal error LNK1120: 1 unresolved externals

So far this way is not really portable on Windows (on Ubuntu everything works fine).
Another way I thought of was to link directly against an exporting executable, but on windows it is problematic (MinGW allows direct linkage to dll without a static lib). I have a question  on SO about that.

Let's see what comes out from the SO question. Keep me posted please. Thanks.

The question is important indeed. Since MinGW linker has another bug - it can create an empty import table when linked to an MSVC-compiled library (to import C functions). I faced it when tried to make a node js addon. You also have to link against a node core, which is an executable... If one could easily link directly against an executable it would solve all of those problems.

I feel that you also would like to take a look at this SO question. As some people pointed out in the comments, implicitly inlined methods (in-class implementations) are not guaranteed to be exported at all. As a matter of fact, on Windows neither or MSVC Clang or MinGW64 has exported any of non-template in-class implemented methods.
When linking to a dll with exported types I can invoke 2 functions:
entt::type_seq<msg_type>::value(); // explicitly instantiated in exports dll
entt::internal::type_seq::next();

Explicitly instantiated template will in turn invoke entt:internal::type_seq::next() from within the dll. But direct invocation of entt:internal::type_seq::next() will be calling an entirely different symbol defined within the executable. This is because it has never been exported neither by Clang nor by MinGW.  So the compiler just generated new code for it. I suppose on Ubuntu the behavior will be the same.
At the end of the day, everything will be working seemingly fine and as expected if nobody calls entt::internal functions directly.  They are internal for a reason, they are not expected to be called directly.
However, this is rather fragile and you never know when something goes wrong. And it would be impossible to find out why.
Take a look at the SO question I've mentioned at the beginning of this comment.

What they say in the SO Q/A is right. Probably the expectation is wrong. A function declared inline is not guaranteed to be exported. On the other side, it's perfectly fine if you can see type_seq<T>::value and internal::type_seq::next, since they are marked to be exported. I would be worried if those symbols weren't visible.
Though, this is in contrast with what you said in the first comment:

When exporting symbols from an executable with MinGW64 on Windows nothing is exported.

So, I'm now wondering what the case is (and I'd say it's the former, given that I'm happily exporting and using those functions on all platforms - granted, not mingw).

However, this is rather fragile and you never know when something goes wrong. And it would be impossible to find out why.

I mean, if someone invokes a function explicitly marked as internal and something goes wrong, I don't think that the problem is in the fragility of a solution. It's likely on the other side of the monitor instead. 😅
What would be the other way around. To turn off inlining and force all functions in the library to be exported? This has a (huge) cost under many aspects. It solves by far more problems than what it is meant to solve, especially if it meant to protect me from people who invoke internal functions of a header-only library.

Take a look at this output for an exe or dll compiled with Clang on Windows (from my question):
Dump of file libapp.dll.a

File Type: LIBRARY

     Exports

       ordinal    name

                  _ZN5foo_tIiE3barEv
                  _ZN5foo_tIiE3buzEv
                  _ZN5foo_tIiEaSERKS0_
```

There are no `foo` symbols. That is `foo` is a non-template class marked for export with `__declspec(dllexport)` and in-class methods implementations. Just like non-template `entt:internal::type_seq`.

Anyway, I don't think that rushing to solutions is a good idea. Now I have a working in an expected way code.
I think I will add a test that proves or disproves my theory about non-exported symbols. You have all the CI needed to get the result immediately. Afterwards it will be clearer whether something needs to be and may done.

At some point in time my "workaround" with entt as a shared library with exported explicit template instantiations failed to work. In Release with MinGW it does not pass my project's CI tests. So I think it is safe to say that my team is stuck :(
I gave the problem some further investigation and have found out that linker optimization for importing symbols can optimize out those even if they have been exported. In some cases I have entt::internal::type_seq exported only in Debug, but not in Release, in other cases it is not imported in either configuration. For MSYS2 Clang64 the results differ in many ways then for MinGW64.
So I added 3 tests in an attempt to expose implementation-dependent differences. I have succeeded to reproduce my problem for MinGW64: increment test is passed in Debug, but segfaults in Release.
For MSYS2 Clang64 in Debug and Release the results differ from MinGW, but are consistent between configurations:
C:\dev\repos\entt\cmake-build-debug-clang64\test\lib\registry_shared_lib\importing_core.exe
[==========] Running 3 tests from 1 test suite.
[----------] Global test environment set-up.
[----------] 3 tests from shared_registry_lib
[ RUN      ] shared_registry_lib.compare_ids_within_core
../test/lib/registry_shared_lib/main.cpp:36: Failure
Expected equality of these values:
  entt::type_seq<test_increment>()
    Which is: 0
  1
[  FAILED  ] shared_registry_lib.compare_ids_within_core (0 ms)
[ RUN      ] shared_registry_lib.compare_ids_across_modules
../test/lib/registry_shared_lib/main.cpp:65: Failure
Expected equality of these values:
  pGetId()
    Which is: 0
  2
[  FAILED  ] shared_registry_lib.compare_ids_across_modules (0 ms)
[ RUN      ] shared_registry_lib.test_increment
[       OK ] shared_registry_lib.test_increment (0 ms)
[----------] 3 tests from shared_registry_lib (1 ms total)

[----------] Global test environment tear-down
[==========] 3 tests from 1 test suite ran. (2 ms total)
[  PASSED  ] 1 test.
[  FAILED  ] 2 tests, listed below:
[  FAILED  ] shared_registry_lib.compare_ids_within_core
[  FAILED  ] shared_registry_lib.compare_ids_across_modules

 2 FAILED TESTS

Process finished with exit code 1

Unfortunately, the github workflow does not run tests for MSYS2 Clang64 or MinGW64.
It is however, very interesting on GCC for Ubuntu. Despite the fact that all checks in github workflow for Linux have passed successfully (that was not what I expected), the test did fail on my colleague's Ubuntu gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0 (I don't have it on my laptop):
Release:
/tmp/entt/cmake-build-release/test/lib/registry_shared_lib/importing_core --gtest_filter=shared_registry_lib.compare_ids_across_modules:shared_registry_lib/*.compare_ids_across_modules:*/shared_registry_lib.compare_ids_across_modules/*:*/shared_registry_lib/*.compare_ids_across_modules --gtest_color=no
Testing started at 10:52 ...
../test/lib/registry_shared_lib/main.cpp:65: Failure
Expected equality of these values:
  pGetId()
    Which is: 0
  2

Process finished with exit code 1

Debug:
/tmp/entt/cmake-build-debug/test/lib/registry_shared_lib/importing_core --gtest_filter=shared_registry_lib.compare_ids_across_modules:shared_registry_lib/*.compare_ids_across_modules:*/shared_registry_lib.compare_ids_across_modules/*:*/shared_registry_lib/*.compare_ids_across_modules --gtest_color=no
Testing started at 10:52 ...
../test/lib/registry_shared_lib/main.cpp:65: Failure
Expected equality of these values:
  pGetId()
    Which is: 1
  2

Process finished with exit code 1

As can be seen, both tests have failed but with different output. The more interesting fact is that for the first build in Release all the tests have passed. But the second and following attempts we could not reproduce it - failed each time.
As for MSVC - it will not compile...

At some point in time my "workaround" with entt as a shared library with exported explicit template instantiations failed to work.

What workaround exactly? Not sure I know what you're talking about here.

In Release with MinGW it does not pass my project's CI tests. So I think it is safe to say that my team is stuck :(

I'm sorry to hear this.

I gave the problem some further investigation and have found out that linker optimization for importing symbols can optimize out those even if they have been exported.

The linker is a runtime thing, so this means that symbols are exported as it ought to be. No idea why it should optimize them out but can it be due to the fact that they aren't used on both sides of a boundary? Hard to say without looking at the code. 🤷♂

So I added 3 tests in an attempt to expose implementation-dependent differences. I have succeeded to reproduce my problem for MinGW64: increment test is passed in Debug, but segfaults in Release.

Ahaaaa... the PR? Those tests are odd honestly. The non-linked one shows that ENTT_API_* stuff doesn't work and it's expected but it doesn't depend on EnTT, it's just that declspec and the others are meant for linked libraries.
The plugins are curious instead. They don't work but from what I can see in the code it's expected, so probably the problem was in the initial expectation? This or I'm missing some details, it wouldn't be the first time that I don't fully get something.

As can be seen, both tests have failed but with different output. The more interesting fact is that for the first build in Release all the tests have passed. But the second and following attempts we could not reproduce it - failed each time.

Without a shared generator, it only depends on the execution flow. Yo ucan run it 1000 times and see it pass 500, 0, all times. All results would be fine.

PS: should I post messages on the topic here or in PR thread?

This issue contains the whole story, so I would continue here (also helpful for future readers).

did you try the new version of mingw here I was having awkward problems with the old one


Instant query with no data causes a panic

Looks like running an instant query against an empty series set series can cause a panic
panic: runtime error: index out of range [4] with length 0

goroutine 348 [running]:
github.com/thanos-community/promql-engine/physicalplan/aggregate.(*aggregate).workerTask(0x100e48a40?, 0x14000091668?, {0x0, {0x0, 0x0, 0x0}, {0x0, 0x0, 0x0}})
	/Users/fpetkovski/Projects/promql-engine/physicalplan/aggregate/hashaggregate.go:155 +0x11c
github.com/thanos-community/promql-engine/worker.(*Worker).Start(0x14000eacc80)
	/Users/fpetkovski/Projects/promql-engine/worker/worker.go:65 +0xdc
created by github.com/thanos-community/promql-engine/worker.Group.Start
	/Users/fpetkovski/Projects/promql-engine/worker/worker.go:24 +0x30

Will TAL!


CMake error when compiling java version

D:\Desktop\td-lib\example\java\build>cmake -DCMAKE_BUILD_TYPE=Release -DTd_DIR=D:/Desktop/td-lib/example/java/td/lib/cmake/Td -DCMAKE_INSTALL_PREFIX:PATH=.. ..
CMake Error at CMakeLists.txt:5 (find_package):
Could not find a configuration file for package "Td" that is compatible
with requested version "".
The following configuration files were considered but not accepted:
D:/Desktop/td-lib/example/java/td/lib/cmake/Td/TdConfig.cmake, version: 1.2.0 (64bit)

-- Configuring incomplete, errors occurred!
See also "D:/Desktop/td-lib/example/java/build/CMakeFiles/CMakeOutput.log".
How i can resolve this issue ?

Thanks so much


🐛 Android front camera seems to not work after 3.6

What's happening?
Black screen when using front camera, on android.
Also i get weird logs about camera disconnection:
 Camera onError:  [session/camera-has-been-disconnected: [session/camera-has-been-disconnected] The given Camera device (id: 1) has been disconnected! Error: DISCONNECTED]
 WARN  Camera onError:  [unknown/unknown: [unknown/unknown] CameraDevice was already closed]

Reproduceable Code
const device = useCameraDevice('front');
const format = useCameraFormat(device, [{videoResolution: {width: 1920, height: 1080}, fps: 30}]);

if (!device) {
  return <></>;
}

return (
  <Camera
    key={device.id}
    ref={props.cameraRef}
    style={props.style}
    video={true}
    audio={false}
    onError={props.onError}
    device={device}
    isActive={true}
    fps={30}
    format={format}
    resizeMode="contain"
    onInitialized={onCameraReady}
  />
)

Relevant log output
I  Legacy camera service transitioning to state ERROR
2023-10-24 17:36:48.103  1759-7112  CameraManagerGlobal     com.android.systemui                 I  Camera 0 facing CAMERA_FACING_BACK state now CAMERA_STATE_IDLE for client com.package.name API Level 1
2023-10-24 17:36:48.103  2910-2929  CameraManagerGlobal     com.sec.android.sdhms                I  Camera 0 facing CAMERA_FACING_BACK state now CAMERA_STATE_IDLE for client com.package.name API Level 1
2023-10-24 17:36:48.103 22508-22585 CameraManagerGlobal     com.package.name                   I  Camera 0 facing CAMERA_FACING_BACK state now CAMERA_STATE_IDLE for client com.package.name API Level 1
2023-10-24 17:36:48.606   868-18567 CameraService           cameraserver                         I  finishCameraOps: Finish camera ops, package name = com.package.name, client UID = 11583
2023-10-24 17:36:48.610  2910-2929  CameraManagerGlobal     com.sec.android.sdhms                I  Camera 0 facing CAMERA_FACING_BACK state now CAMERA_STATE_CLOSED for client com.package.name API Level 1
2023-10-24 17:36:48.610 22508-22585 CameraManagerGlobal     com.package.name                   I  postSingleUpdate device: camera id 0 status STATUS_PRESENT
2023-10-24 17:36:48.611  1759-7112  CameraManagerGlobal     com.android.systemui                 I  Camera 0 facing CAMERA_FACING_BACK state now CAMERA_STATE_CLOSED for client com.package.name API Level 1
2023-10-24 17:36:48.611 22508-22894 CameraDevices           com.package.name                   I  Camera #0: Available!
2023-10-24 17:36:48.612 22508-22585 CameraManagerGlobal     com.package.name                   I  Camera 0 facing CAMERA_FACING_BACK state now CAMERA_STATE_CLOSED for client com.package.name API Level 1
2023-10-24 17:36:48.615   868-18567 CameraService           cameraserver                         I  service.camera.client set to com.package.name
2023-10-24 17:36:48.615   868-18567 CameraService           cameraserver                         I  startCameraOps: Start camera ops, package name = com.package.name, client UID = 11583
2023-10-24 17:36:48.619 22508-22585 CameraManagerGlobal     com.package.name                   I  postSingleUpdate device: camera id 1 status STATUS_NOT_AVAILABLE
2023-10-24 17:36:48.620 22508-22894 CameraDevices           com.package.name                   I  Camera #1: Unavailable!
2023-10-24 17:36:48.621  2910-2929  CameraManagerGlobal     com.sec.android.sdhms                I  Camera 1 facing CAMERA_FACING_FRONT state now CAMERA_STATE_OPEN for client com.package.name API Level 1
2023-10-24 17:36:48.621  1759-7112  CameraManagerGlobal     com.android.systemui                 I  Camera 1 facing CAMERA_FACING_FRONT state now CAMERA_STATE_OPEN for client com.package.name API Level 1
2023-10-24 17:36:48.622 22508-22585 CameraManagerGlobal     com.package.name                   I  Camera 1 facing CAMERA_FACING_FRONT state now CAMERA_STATE_OPEN for client com.package.name API Level 1
2023-10-24 17:36:48.731 22508-23999 CameraManager           com.package.name                   I  Camera 0: Opened!
2023-10-24 17:36:48.731 22508-23999 CameraManager           com.package.name                   I  Camera 0: Disconnected!
2023-10-24 17:36:48.737 22508-23999 CameraManager           com.package.name                   I  Camera 1: Opened!
2023-10-24 17:36:48.751 22508-23999 PreviewView             com.package.name                   I  Resizing PreviewView to 1024 x 768...
2023-10-24 17:36:48.751 22508-23999 CameraSession           com.package.name                   I  Successfully configured Camera #0!
2023-10-24 17:36:48.761 22508-23999 CameraSession           com.package.name                   I  Configuring Session for Camera #0...
2023-10-24 17:36:48.764 22508-23999 CameraSession           com.package.name                   I  Adding 1472 x 1104 Video Output in Format #34...
2023-10-24 17:36:48.778 22508-23999 VideoPipeline           com.package.name                   I  Initializing 1472 x 1104 Video Pipeline (format: NATIVE)
2023-10-24 17:36:48.793 22508-23999 CreateCaptureSession    com.package.name                   I  Camera 0: Creating Capture Session #1000... Hardware Level: 2} | Outputs: [android.hardware.camera2.params.OutputConfiguration@e8750dd0]
2023-10-24 17:36:48.794 22508-23999 CreateCaptureSession    com.package.name                   I  Using new API (>=28)
2023-10-24 17:36:48.797 22508-23999 CameraSession           com.package.name                   E  Failed to configure CameraSession! Error: CameraDevice was already closed, Config-Diff: Difference(deviceChanged=true, outputsChanged=true, sidePropsChanged=true)
                                                                                java.lang.IllegalStateException: CameraDevice was already closed
                                                                                at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2550)
                                                                                at android.hardware.camera2.impl.CameraDeviceImpl.createCaptureSessionInternal(CameraDeviceImpl.java:648)
                                                                                at android.hardware.camera2.impl.CameraDeviceImpl.createCaptureSession(CameraDeviceImpl.java:634)
                                                                                at com.mrousavy.camera.extensions.CameraDevice_createCaptureSessionKt.createCaptureSession(CameraDevice+createCaptureSession.kt:57)
                                                                                at com.mrousavy.camera.core.CameraSession.configureOutputs(CameraSession.kt:356)
                                                                                at com.mrousavy.camera.core.CameraSession.configure(CameraSession.kt:136)
                                                                                at com.mrousavy.camera.core.CameraSession$configure$1.invokeSuspend(Unknown Source:15)
                                                                                at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
                                                                                at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
                                                                                at android.os.Handler.handleCallback(Handler.java:883)
                                                                                at android.os.Handler.dispatchMessage(Handler.java:100)
                                                                                at android.os.Looper.loop(Looper.java:237)
                                                                                at android.os.HandlerThread.run(HandlerThread.java:67)
2023-10-24 17:36:48.797 22508-23999 CameraView              com.package.name                   E  invokeOnError(...):
2023-10-24 17:36:48.798 22508-23999 System.err              com.package.name                   W  java.lang.IllegalStateException: CameraDevice was already closed
2023-10-24 17:36:48.798 22508-23999 System.err              com.package.name                   W  	at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2550)
2023-10-24 17:36:48.798 22508-23999 System.err              com.package.name                   W  	at android.hardware.camera2.impl.CameraDeviceImpl.createCaptureSessionInternal(CameraDeviceImpl.java:648)
2023-10-24 17:36:48.798 22508-23999 System.err              com.package.name                   W  	at android.hardware.camera2.impl.CameraDeviceImpl.createCaptureSession(CameraDeviceImpl.java:634)
2023-10-24 17:36:48.798 22508-23999 System.err              com.package.name                   W  	at com.mrousavy.camera.extensions.CameraDevice_createCaptureSessionKt.createCaptureSession(CameraDevice+createCaptureSession.kt:57)
2023-10-24 17:36:48.798 22508-23999 System.err              com.package.name                   W  	at com.mrousavy.camera.core.CameraSession.configureOutputs(CameraSession.kt:356)
2023-10-24 17:36:48.798 22508-23999 System.err              com.package.name                   W  	at com.mrousavy.camera.core.CameraSession.configure(CameraSession.kt:136)
2023-10-24 17:36:48.799 22508-23999 System.err              com.package.name                   W  	at com.mrousavy.camera.core.CameraSession$configure$1.invokeSuspend(Unknown Source:15)
2023-10-24 17:36:48.799 22508-23999 System.err              com.package.name                   W  	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
2023-10-24 17:36:48.799 22508-23999 System.err              com.package.name                   W  	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
2023-10-24 17:36:48.799 22508-23999 System.err              com.package.name                   W  	at android.os.Handler.handleCallback(Handler.java:883)
2023-10-24 17:36:48.799 22508-23999 System.err              com.package.name                   W  	at android.os.Handler.dispatchMessage(Handler.java:100)
2023-10-24 17:36:48.799 22508-23999 System.err              com.package.name                   W  	at android.os.Looper.loop(Looper.java:237)
2023-10-24 17:36:48.799 22508-23999 System.err              com.package.name                   W  	at android.os.HandlerThread.run(HandlerThread.java:67)
2023-10-24 17:36:48.817 22508-23999 PreviewView             com.package.name                   I  Resizing PreviewView to 1024 x 768...
2023-10-24 17:36:48.818 22508-23999 CameraSession           com.package.name                   I  Successfully configured Camera #1!
2023-10-24 17:36:48.826 22508-23999 CameraSession           com.package.name                   I  Configuring Session for Camera #1...
2023-10-24 17:36:48.828 22508-23999 CameraSession           com.package.name                   I  Adding 1472 x 1104 Video Output in Format #34...
2023-10-24 17:36:48.828 22508-23999 VideoPipeline           com.package.name                   I  Initializing 1472 x 1104 Video Pipeline (format: NATIVE)
2023-10-24 17:36:48.838 22508-23999 CreateCaptureSession    com.package.name                   I  Camera 1: Creating Capture Session #1001... Hardware Level: 2} | Outputs: [android.hardware.camera2.params.OutputConfiguration@818293af]
2023-10-24 17:36:48.838 22508-23999 CreateCaptureSession    com.package.name                   I  Using new API (>=28)
2023-10-24 17:36:48.842 22508-23999 CameraDeviceState       com.package.name                   I  Legacy camera service transitioning to state CONFIGURING
2023-10-24 17:36:48.843 22508-24076 RequestThread-1         com.package.name                   I  Configure outputs: 1 surfaces configured.
2023-10-24 17:36:48.843 22508-24076 Camera                  com.package.name                   D  app passed NULL surface
2023-10-24 17:36:48.883 22508-24077 libc                    com.package.name                   E  Access denied finding property "persist.camera.legacy_perf"
2023-10-24 17:36:48.889 22508-23999 CameraDeviceState       com.package.name                   I  Legacy camera service transitioning to state IDLE
2023-10-24 17:36:48.891 22508-23999 CameraSession           com.package.name                   I  Updating CameraSession Configuration...
2023-10-24 17:36:48.892 22508-23999 CameraSession           com.package.name                   I  Configuring Camera #0...
2023-10-24 17:36:48.893 22508-23999 CameraManager           com.package.name                   I  Camera 0: Opening...
2023-10-24 17:36:48.905 22508-23999 CameraManager           com.package.name                   I  Using legacy camera HAL.
2023-10-24 17:36:48.907   868-1785  CameraService           cameraserver                         I  CameraService::connect call (PID -1 "com.package.name", camera ID 0) for HAL version default and Camera API version 1
2023-10-24 17:36:48.908   868-1785  CameraService           cameraserver                         I  CameraService::validateClientPermissionsLocked is ok : calling pid 22508, calling uid 11583, client com.package.name , cameraservice pid=868, device user 0, currently allowed device users: 0
2023-10-24 17:36:48.909 22508-24036 Camera                  com.package.name                   E  Error 2
2023-10-24 17:36:48.909 22508-24036 RequestThread-1         com.package.name                   I  Flushing all pending requests.
2023-10-24 17:36:48.909 22508-24036 RequestQueue            com.package.name                   E  cancel failed: no repeating request exists.
2023-10-24 17:36:48.909 22508-24036 CameraDeviceState       com.package.name                   I  Legacy camera service transitioning to state ERROR
2023-10-24 17:36:48.910  1759-6844  CameraManagerGlobal     com.android.systemui                 I  Camera 1 facing CAMERA_FACING_FRONT state now CAMERA_STATE_IDLE for client com.package.name API Level 1
2023-10-24 17:36:48.910 22508-22585 CameraManagerGlobal     com.package.name                   I  Camera 1 facing CAMERA_FACING_FRONT state now CAMERA_STATE_IDLE for client com.package.name API Level 1
2023-10-24 17:36:48.910  2910-2927  CameraManagerGlobal     com.sec.android.sdhms                I  Camera 1 facing CAMERA_FACING_FRONT state now CAMERA_STATE_IDLE for client com.package.name API Level 1
2023-10-24 17:36:48.938   868-1785  CameraService           cameraserver                         I  finishCameraOps: Finish camera ops, package name = com.package.name, client UID = 11583
2023-10-24 17:36:48.939  1759-6844  CameraManagerGlobal     com.android.systemui                 I  Camera 1 facing CAMERA_FACING_FRONT state now CAMERA_STATE_CLOSED for client com.package.name API Level 1
2023-10-24 17:36:48.940 22508-22585 CameraManagerGlobal     com.package.name                   I  postSingleUpdate device: camera id 1 status STATUS_PRESENT
2023-10-24 17:36:48.940 22508-22894 CameraDevices           com.package.name                   I  Camera #1: Available!
2023-10-24 17:36:48.940  2910-2927  CameraManagerGlobal     com.sec.android.sdhms                I  Camera 1 facing CAMERA_FACING_FRONT state now CAMERA_STATE_CLOSED for client com.package.name API Level 1
2023-10-24 17:36:48.940 22508-22585 CameraManagerGlobal     com.package.name                   I  Camera 1 facing CAMERA_FACING_FRONT state now CAMERA_STATE_CLOSED for client com.package.name API Level 1
2023-10-24 17:36:48.943   868-1785  CameraService           cameraserver                         I  service.camera.client set to com.package.name
2023-10-24 17:36:48.943   868-1785  CameraService           cameraserver                         I  startCameraOps: Start camera ops, package name = com.package.name, client UID = 11583
2023-10-24 17:36:48.948  1759-7112  CameraManagerGlobal     com.android.systemui                 I  Camera 0 facing CAMERA_FACING_BACK state now CAMERA_STATE_OPEN for client com.package.name API Level 1
2023-10-24 17:36:48.948 22508-22585 CameraManagerGlobal     com.package.name                   I  postSingleUpdate device: camera id 0 status STATUS_NOT_AVAILABLE
2023-10-24 17:36:48.948  2910-2929  CameraManagerGlobal     com.sec.android.sdhms                I  Camera 0 facing CAMERA_FACING_BACK state now CAMERA_STATE_OPEN for client com.package.name API Level 1
2023-10-24 17:36:48.948 22508-22894 CameraDevices           com.package.name                   I  Camera #0: Unavailable!
2023-10-24 17:36:48.949 22508-22585 CameraManagerGlobal     com.package.name                   I  Camera 0 facing CAMERA_FACING_BACK state now CAMERA_STATE_OPEN for client com.package.name API Level 1
2023-10-24 17:36:49.026 22508-23999 CreateCaptureSession    com.package.name                   I  Camera 1: Capture Session #1001 configured!
2023-10-24 17:36:49.026 22508-23999 CameraManager           com.package.name                   I  Camera 1: Disconnected!
2023-10-24 17:36:49.028 22508-23999 CameraSession           com.package.name                   E  Camera Device android.hardware.camera2.impl.CameraDeviceImpl@51d64d2 has been disconnected!
                                                                                com.mrousavy.camera.core.CameraDisconnectedError: [session/camera-has-been-disconnected] The given Camera device (id: 1) has been disconnected! Error: DISCONNECTED
                                                                                at com.mrousavy.camera.extensions.CameraManager_openCameraKt$openCamera$2$callback$1.onDisconnected(CameraManager+openCamera.kt:38)
                                                                                at android.hardware.camera2.impl.CameraDeviceImpl$7.run(CameraDeviceImpl.java:246)
                                                                                at android.os.Handler.handleCallback(Handler.java:883)
                                                                                at android.os.Handler.dispatchMessage(Handler.java:100)
                                                                                at android.os.Looper.loop(Looper.java:237)
                                                                                at android.os.HandlerThread.run(HandlerThread.java:67)
2023-10-24 17:36:49.028 22508-23999 CameraView              com.package.name                   E  invokeOnError(...):
2023-10-24 17:36:49.029 22508-23999 System.err              com.package.name                   W  com.mrousavy.camera.core.CameraDisconnectedError: [session/camera-has-been-disconnected] The given Camera device (id: 1) has been disconnected! Error: DISCONNECTED
2023-10-24 17:36:49.029 22508-23999 System.err              com.package.name                   W  	at com.mrousavy.camera.extensions.CameraManager_openCameraKt$openCamera$2$callback$1.onDisconnected(CameraManager+openCamera.kt:38)
2023-10-24 17:36:49.029 22508-23999 System.err              com.package.name                   W  	at android.hardware.camera2.impl.CameraDeviceImpl$7.run(CameraDeviceImpl.java:246)
2023-10-24 17:36:49.029 22508-23999 System.err              com.package.name                   W  	at android.os.Handler.handleCallback(Handler.java:883)
2023-10-24 17:36:49.029 22508-23999 System.err              com.package.name                   W  	at android.os.Handler.dispatchMessage(Handler.java:100)
2023-10-24 17:36:49.029 22508-23999 System.err              com.package.name                   W  	at android.os.Looper.loop(Looper.java:237)
2023-10-24 17:36:49.029 22508-23999 System.err              com.package.name                   W  	at android.os.HandlerThread.run(HandlerThread.java:67)
2023-10-24 17:36:49.037 22508-23999 CameraManager           com.package.name                   I  Camera 0: Opened!
2023-10-24 17:36:49.037 22508-23999 CameraSession           com.package.name                   I  Successfully configured Session with 1 outputs for Camera #1!
2023-10-24 17:36:49.037 22508-23999 CameraSession           com.package.name                   I  Updating Video Outputs...
2023-10-24 17:36:49.037 22508-23999 VideoPipeline           com.package.name                   I  Removing FrameProcessor Output...
2023-10-24 17:36:49.038 22508-23999 VideoPipeline           com.package.name                   I  Removing RecordingSession Output...
2023-10-24 17:36:49.038 22508-23999 CameraSession           com.package.name                   W  Preview Output is null, aborting...
2023-10-24 17:36:49.038 22508-23999 CameraSession           com.package.name                   I  Successfully updated CameraSession Configuration! isActive: true
2023-10-24 17:36:49.038 22508-23999 CameraView              com.package.name                   I  invokeOnInitialized()
2023-10-24 17:36:49.039 22508-22893 ReactNativeJS           com.package.name                   W  'Camera onError: ', { [session/camera-has-been-disconnected: [session/camera-has-been-disconnected] The given Camera device (id: 1) has been disconnected! Error: DISCONNECTED]
                                                                                name: 'session/camera-has-been-disconnected',
                                                                                _code: 'session/camera-has-been-disconnected',
                                                                                _message: '[session/camera-has-been-disconnected] The given Camera device (id: 1) has been disconnected! Error: DISCONNECTED',
                                                                                _cause: undefined }
2023-10-24 17:36:49.052 22508-23999 PreviewView             com.package.name                   I  Resizing PreviewView to 1024 x 768...
2023-10-24 17:36:49.052 22508-23999 CameraSession           com.package.name                   I  Successfully configured Camera #0!
2023-10-24 17:36:49.061 22508-23999 CameraSession           com.package.name                   I  Configuring Session for Camera #0...
2023-10-24 17:36:49.061 22508-23999 SurfaceOutput           com.package.name                   I  Closing 1472x1104 Video Pipeline..
2023-10-24 17:36:49.063 22508-23999 CameraSession           com.package.name                   I  Adding 1472 x 1104 Video Output in Format #34...
2023-10-24 17:36:49.063 22508-23999 VideoPipeline           com.package.name                   I  Initializing 1472 x 1104 Video Pipeline (format: NATIVE)
2023-10-24 17:36:49.073 22508-23999 CreateCaptureSession    com.package.name                   I  Camera 0: Creating Capture Session #1002... Hardware Level: 2} | Outputs: [android.hardware.camera2.params.OutputConfiguration@d4d42a2b]
2023-10-24 17:36:49.074 22508-23999 CreateCaptureSession    com.package.name                   I  Using new API (>=28)
2023-10-24 17:36:49.075 22508-23999 CameraDeviceState       com.package.name                   I  Legacy camera service transitioning to state CONFIGURING
2023-10-24 17:36:49.076 22508-24114 RequestThread-0         com.package.name                   I  Configure outputs: 1 surfaces configured.
2023-10-24 17:36:49.076 22508-24114 Camera                  com.package.name                   D  app passed NULL surface
2023-10-24 17:36:49.089 22508-24115 libc                    com.package.name                   E  Access denied finding property "persist.camera.legacy_perf"
2023-10-24 17:36:49.095 22508-23999 CameraDeviceState       com.package.name                   I  Legacy camera service transitioning to state IDLE
2023-10-24 17:36:49.096 22508-23999 CameraSession           com.package.name                   I  Updating CameraSession Configuration...
2023-10-24 17:36:49.097 22508-23999 CameraSession           com.package.name                   W  Called configure(...) but nothing changed...
2023-10-24 17:36:49.097 22508-23999 CreateCaptureSession    com.package.name                   I  Camera 1: Capture Session #1001 closed!
2023-10-24 17:36:49.097 22508-23999 CameraSession           com.package.name                   I  Camera Session android.hardware.camera2.impl.CameraCaptureSessionImpl@b48fc1e has been closed!
2023-10-24 17:36:49.098 22508-23999 CreateCaptureSession    com.package.name                   I  Camera 0: Capture Session #1002 configured!
2023-10-24 17:36:49.098 22508-23999 CameraSession           com.package.name                   I  Updating CameraSession Configuration...
2023-10-24 17:36:49.107 22508-23999 CameraSession           com.package.name                   I  Configuring Session for Camera #1...
2023-10-24 17:36:49.107 22508-23999 SurfaceOutput           com.package.name                   I  Closing 1472x1104 Video Pipeline..
2023-10-24 17:36:49.110 22508-23999 CameraSession           com.package.name                   I  Adding 1472 x 1104 Video Output in Format #34...
2023-10-24 17:36:49.110 22508-23999 VideoPipeline           com.package.name                   I  Initializing 1472 x 1104 Video Pipeline (format: NATIVE)
2023-10-24 17:36:49.113 22508-23999 CameraSession           com.package.name                   I  Adding 1024 x 768 Preview Output...
2023-10-24 17:36:49.114 22508-23999 PreviewView             com.package.name                   I  Resizing PreviewView to 1024 x 768...
2023-10-24 17:36:49.124 22508-23999 CreateCaptureSession    com.package.name                   I  Camera 1: Creating Capture Session #1003... Hardware Level: 2} | Outputs: [android.hardware.camera2.params.OutputConfiguration@9b1a661a, android.hardware.camera2.params.OutputConfiguration@157a519]
2023-10-24 17:36:49.124 22508-23999 CreateCaptureSession    com.package.name                   I  Using new API (>=28)
2023-10-24 17:36:49.125 22508-23999 CameraSession           com.package.name                   E  Failed to configure CameraSession! Error: CameraDevice was already closed, Config-Diff: Difference(deviceChanged=false, outputsChanged=true, sidePropsChanged=true)
                                                                                java.lang.IllegalStateException: CameraDevice was already closed
                                                                                at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2550)
                                                                                at android.hardware.camera2.impl.CameraDeviceImpl.createCaptureSessionInternal(CameraDeviceImpl.java:648)
                                                                                at android.hardware.camera2.impl.CameraDeviceImpl.createCaptureSession(CameraDeviceImpl.java:634)
                                                                                at com.mrousavy.camera.extensions.CameraDevice_createCaptureSessionKt.createCaptureSession(CameraDevice+createCaptureSession.kt:57)
                                                                                at com.mrousavy.camera.core.CameraSession.configureOutputs(CameraSession.kt:356)
                                                                                at com.mrousavy.camera.core.CameraSession.configure(CameraSession.kt:136)
                                                                                at com.mrousavy.camera.core.CameraSession$configure$1.invokeSuspend(Unknown Source:15)
                                                                                at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
                                                                                at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
                                                                                at android.os.Handler.handleCallback(Handler.java:883)
                                                                                at android.os.Handler.dispatchMessage(Handler.java:100)
                                                                                at android.os.Looper.loop(Looper.java:237)
                                                                                at android.os.HandlerThread.run(HandlerThread.java:67)
2023-10-24 17:36:49.125 22508-23999 CameraView              com.package.name                   E  invokeOnError(...):
2023-10-24 17:36:49.125 22508-23999 System.err              com.package.name                   W  java.lang.IllegalStateException: CameraDevice was already closed
2023-10-24 17:36:49.125 22508-23999 System.err              com.package.name                   W  	at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2550)
2023-10-24 17:36:49.125 22508-23999 System.err              com.package.name                   W  	at android.hardware.camera2.impl.CameraDeviceImpl.createCaptureSessionInternal(CameraDeviceImpl.java:648)
2023-10-24 17:36:49.125 22508-23999 System.err              com.package.name                   W  	at android.hardware.camera2.impl.CameraDeviceImpl.createCaptureSession(CameraDeviceImpl.java:634)
2023-10-24 17:36:49.125 22508-23999 System.err              com.package.name                   W  	at com.mrousavy.camera.extensions.CameraDevice_createCaptureSessionKt.createCaptureSession(CameraDevice+createCaptureSession.kt:57)
2023-10-24 17:36:49.125 22508-23999 System.err              com.package.name                   W  	at com.mrousavy.camera.core.CameraSession.configureOutputs(CameraSession.kt:356)
2023-10-24 17:36:49.126 22508-23999 System.err              com.package.name                   W  	at com.mrousavy.camera.core.CameraSession.configure(CameraSession.kt:136)
2023-10-24 17:36:49.126 22508-23999 System.err              com.package.name                   W  	at com.mrousavy.camera.core.CameraSession$configure$1.invokeSuspend(Unknown Source:15)
2023-10-24 17:36:49.126 22508-23999 System.err              com.package.name                   W  	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
2023-10-24 17:36:49.126 22508-23999 System.err              com.package.name                   W  	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
2023-10-24 17:36:49.126 22508-23999 System.err              com.package.name                   W  	at android.os.Handler.handleCallback(Handler.java:883)
2023-10-24 17:36:49.126 22508-23999 System.err              com.package.name                   W  	at android.os.Handler.dispatchMessage(Handler.java:100)
2023-10-24 17:36:49.126 22508-23999 System.err              com.package.name                   W  	at android.os.Looper.loop(Looper.java:237)
2023-10-24 17:36:49.126 22508-23999 System.err              com.package.name                   W  	at android.os.HandlerThread.run(HandlerThread.java:67)

Camera Device
{
  "hardwareLevel": "legacy",
  "neutralZoom": 1,
  "supportsFocus": true,
  "supportsLowLightBoost": false,
  "hasTorch": false,
  "supportsRawCapture": false,
  "sensorOrientation": "landscape-left",
  "maxZoom": 4,
  "physicalDevices": [
    "wide-angle-camera"
  ],
  "isMultiCam": false,
  "id": "1",
  "position": "front",
  "minZoom": 1,
  "hasFlash": false,
  "name": "FRONT (1)"
}

Device
samsung tab A8
VisionCamera Version
3.6.3
Can you reproduce this issue in the VisionCamera Example app?
I didn't try (⚠ your issue might get ignored & closed if you don't try this)
Additional information

[ ] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Resolved by removing key from the camera component:
<Camera
   key={device.id} // <-- Remove this

Oh that was happening because i was switching from back to front device very quickly. in componentDidMount i was changing the CameraPosition to front from back and this leads to the above error when also setting the key prop to camera component.


Fix ToS link to point to correct file

the external adminguide file moved, this updates link
@stvstnfrd & @mondiaz

@caesar2164 I see this is for suclass-theme. We don't have TOS on SUClass (see https://suclass.stanford.edu/tos) but we do have TOS on CME now (see https://cme.class.stanford.edu/tos).

@mondiaz CME uses the suclass theme...

+1


Vocab selection cool-down

Please add default behavior such that the same word is not selected from a vocab file multiple times in a row, unless the alternative would be no selection at all.

DUPE


Add aria-live assertive for recording countdown

Also centred text for "connecting" dialog

This kind of works and kind of doesn't. NVDA is too busy reading out things from previous focus, current focus, and the fact that a dialog has appeared. It's just too slow to be useful. It continues to read 3, 2, 1 etc, but it's well behind what is changing on screen. By the time it says "recording", the recording has practically finished.
The progress bar has some built in aria-live features. For NVDA it's an incredibly irritating noise starting low in pitch and getting higher until it stops.
Windows narrator does a slightly better job. It is busy reading that a close button is focussed, misses the start of the countdown, but keeps pace. It's normally "2 , 1..." or "1, recording". It also doesn't produce a noise during the progress dialog transition.
I don't really know the best way to fix this. There could well be options in the screen reader settings that would improve the experience.
One thing we don't do at the moment is tell you when the recording stops. You only get a sense that it does because a different button becomes focussed when the dialog closes.

This kind of works and kind of doesn't. NVDA is too busy reading out things from previous focus, current focus, and the fact that a dialog has appeared. It's just too slow to be useful. It continues to read 3, 2, 1 etc, but it's well behind what is changing on screen. By the time it says "recording", the recording has practically finished.
The progress bar has some built in aria-live features. For NVDA it's an incredibly irritating noise starting low in pitch and getting higher until it stops.
Windows narrator does a slightly better job. It is busy reading that a close button is focussed, misses the start of the countdown, but keeps pace. It's normally "2 , 1..." or "1, recording". It also doesn't produce a noise during the progress dialog transition.
I don't really know the best way to fix this. There could well be options in the screen reader settings that would improve the experience.

Hmm.. sounds like the experience for NVDA and windows narrator are different to Mac voice over experience. 🤔 Below is a video for what I experience using the Mac voice over.
https://github.com/user-attachments/assets/776da433-734b-4297-8202-74c195ffd017
I'm not sure what's the best way to fix this too.

One thing we don't do at the moment is tell you when the recording stops. You only get a sense that it does because a different button becomes focussed when the dialog closes.

Maybe adding a toast that says "Recording added" or something along those lines could hint to the user that the recording has stopped? Suggestions welcomed

Parking this one until we can try out in person and discuss next week.

You can hit the NVDA key + spacebar when the dialog opens to stop it reading out the dialog info and just listen to the aria-live region which then works pretty well. I want to explore NVDA settings / modes to see if we can suggest something that will work well for the recording process.

You can hit the NVDA key + spacebar when the dialog opens to stop it reading out the dialog info and just listen to the aria-live region which then works pretty well. I want to explore NVDA settings / modes to see if we can suggest something that will work well for the recording process.

Seems like you can just hit CTRL when the dialog opens to interupt NVDA, it will then announce the countdown. This is not a very practical fix as it requires relatively quick reactions and fine motor skills.


Update index.js

401 Error handling

Fixed OrganizationalResource spelling bug. However I want library to remain agnostic with respect to error messsages, because it should return the same information (or absence of) as the Autotask REST API.


Test: Extension repository link

Tests https://github.com/Microsoft/vscode/issues/27331

[ ] @RMacfarlane
[x] @kieferrm

Complexity 1
Make sure extensions which have an associated repository in the Marketplace show the Repository link in the extension editor: https://github.com/Microsoft/vscode/pull/31487

Covered Mac and Windows.


How to Test the scripts with Reservation API

I would like to know If there is a way to call the reservation API while writing the script without buying the reservations?

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

ID: 901b8caf-6a63-d728-ce50-511197316e91
Version Independent ID: 49fcf728-bc45-7dcb-07a7-8d0c3a21b40a
Content: APIs for Azure reservation automation
Content Source: articles/billing/billing-reservation-apis.md
Service: cost-management-billing
GitHub Login: @yashesvi
Microsoft Alias: banders

@karthick3d Thank you for your feedback! We will review and update as appropriate.

@Karthick3d, as far as I know, you need to have/purchase a reservation Plan to call the APIs
@yashesvi  - please confirm.

@karthick3d you will have to buy an RI to try the APIs.

We will now close this issue. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.


Don't Merge! PR real time test for source branch full build

Docs Build status updates of commit a6b2729:
:clock10: Full build: the average full build time is 6 min(s) 6 sec(s), this is based on the last 295 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

Docs Build status updates of commit a6b2729:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

docfx.json
: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.


Dragging mouse on board creates post-it

It shouldn't create a post-it when you drag across the board to scroll, but as of now it makes one every time you move the board and release the mouse.

Fixed.


Error with Installing tensorflow error using Virtualenv

Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
It shouldn't be a TensorBoard issue. Those go here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No custom code was written steps followed from the installtensorflow webpage:
https://www.tensorflow.org/install/install_mac
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Mac OSX El Capitan version 10.11.6
TensorFlow installed from (source or binary): error in installing tensorflow
TensorFlow version (use command below):
Python version: Python 3.6
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): not sure
CUDA/cuDNN version:
GPU model and memory: MacBook Pro 13 inch(early 2011), Processor: 2.3 GHz Intel Core I5, Memory: 16GB 1333 MHz DDR3, Graphics: Intel HD Graphics 3000 512 MB
Exact command to reproduce:  error when using the following command
$ virtualenv --system-site-packages -p python3 ~/tensorflow

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
I am trying to install tensorflow for mac os El Capitan, using Virtualenv as instructed in the tensorflow installation webpage: https://www.tensorflow.org/install/install_mac these are the steps i have taken and errors recieved:
1.Start a terminal (a shell). You'll perform all subsequent steps in this shell.

Installed pip and Virtualenv sucessfully by issuing the following commands:

$ sudo easy_install pip
$ pip install --upgrade virtualenv

successfully Created a Virtualenv environment by issuing a command of one of the python 3 format:

$ virtualenv --system-site-packages -p python3 ~/tensorflow
the following e4 errors were displayed in terminal after step 3:
ERROR: The executable /Users/User/tensorflow/bin/python3 is not functioning
ERROR: It thinks sys.prefix is '/Users/User' (should be '/Users/User/tensorflow')
ERROR: virtualenv is not compatible with this system or executable

I get an error when doing step 4 :Activate the Virtualenv environment by issuing one of the    following commands:

$ cd targetDirectory
$ source ./bin/activate      # If using bash, sh, ksh, or zsh
$ source ./bin/activate.csh  # If using csh or tcsh
the error i ger is: -bash: ./bin/activate: No such file or directory
Please help with this problem is greatly appreciated,  I have tried 1 other times using different methods to install tensorflow and it hasn't worked. Next ill try native pip method.
i have attached a terminal screenshot of the whole process:

Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.

I don't believe this is a TensorFlow problem. The virtualenv command failed, which suggests your computers python install is broken, before you have done anything TensorFlow specific. Closing for now.


Update styling to make screens use similar patterns

Why:
We were using different design patterns on different screens, which made the app
feel disjointed and created a suboptimal user experience.
This commit:
Updates various screens to use the same design patterns.

@johnschoeman Thoughts on the new design for the symptom log time header? It feels cleaner to me.


Feature/mega linter

Everything disabled except a few python checks. Should raise PRs to fix them.
https://github.com/LukePrior/nbn-upgrade-map/issues/90

See the checks on this PR itself for an example of the GHA in action.  I'm going to PR a lint error into this PR now, and see how/if it raises a PR to remedy.

I don't know why it didn't create a PR to fix the malformed file. I'll dig into it.


Fedora Server 37 unable to conpile (CXX identifcation)

I decided to give Fedora 37 a try today and one of my tests was compiling SE. Unfortunately it failed. While I'll probably use a AlmaLinux 9 podman container to compile for now I just wanted to let you know this since Fedora 37 is the "Preview" for the next big Enterprise distros.
OUTPUT:
owner@localhost SoftEtherVPN]$ ./configure
---------------------------------------------------------------------
SoftEther VPN for Unix

Copyright (c) all contributors on SoftEther VPN project in GitHub.
Copyright (c) Daiyuu Nobori, SoftEther Project at University of Tsukuba, and SoftEther Corporation.

Licensed under the Apache License, Version 2.0 (the License).

Read and understand README, LICENSE and WARNING before use.
---------------------------------------------------------------------

Welcome to the corner-cutting configure script !

'rpm' executable found, CPack will generate RPM packages.

-- Build date: 25/11/2022
-- Build time: 09:49:01
-- The CXX compiler identification is unknown
CMake Error at src/Mayaqua/3rdparty/cpu_features/CMakeLists.txt:3 (project):
  No CMAKE_CXX_COMPILER could be found.

  Tell CMake where to find the compiler by setting either the environment
  variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
  to the compiler, or to the compiler name if it is in the PATH.

-- Configuring incomplete, errors occurred!
See also "/home/owner/SoftEtherVPN/build/CMakeFiles/CMakeOutput.log".
See also "/home/owner/SoftEtherVPN/build/CMakeFiles/CMakeError.log".

Extra info:
I tried messing with the CMAKE_CXX_COMPILER and CXX variables to no success.

CXX is usually autodetected c++ compiler, i.e. g++
do you have installed one ?
I guess, more diag is at
See also "/home/owner/SoftEtherVPN/build/CMakeFiles/CMakeOutput.log".
See also "/home/owner/SoftEtherVPN/build/CMakeFiles/CMakeError.log".

Yeah for some reason g++ was not installed when I sudo yum -y groupinstall "Development Tools" after installing it manually it was fixed. I would suggest adding G++ to the manual dependency install command in the Build UNIX script.

Also Clang works.


Title:  A backend Dance Website

Is your proposal related to a problem? Please describe.
Made this website using only backend language. Simple and understandable code
Add any other context or screenshots about the proposal request here.
No response

@Laraibnehal Describe more about this .

I made a website using only backend languages where I also created a form page where it gets submitted to database directly.And code is easy to understand and simple.

@Kushal997-das

@Laraibnehal Add some images at least name of your project

Laraib's dance academy is the project's name


[dv/hmac] improve hmac scb

While fixing the corner cases in PR #3334, i found a few stall codes in
hmac_scb. This PR cleans up the code (no functional change), and modify
a few comments to make it eaiser to read.
Signed-off-by: Cindy Chen<EMAIL_ADDRESS>

Run into a corner case, I will close it temporarily and fix the issue first.

The bug I ran into is a general HMAC tb issue, not related to this change. I will work on the fix soon.


Track shadow rift scaling

Track combats in the shadow rift and scale shadow monster resistance accordingly. Still need info on other stat scaling

Are you sure the physical resistance scales? Here is the very first shadow monster I fought:
[68860] Unknown Adventure #567
Encounter: shadow devil
*** Monster 'shadow devil' has monsterId = 2273 and image 'shadowdevil.gif'
Round 0: Brianna wins initiative!
Round 1: Brianna attacks!
Round 2: shadow devil takes 1 damage.
Round 2: Brianna casts SAUCEGEYSER!
Round 3: shadow devil takes 806 damage.

Which is to say, my experience is that all shadow monsters have 100% physical resistance.

I'm not sure! I just picked this up somewhere between the wiki, forums, kol chat and Discord

If someone knows the correct relationship between shadow monsters and fights in the rift, please let me know!

The Wiki says this:
Each rift leads to a mysterious shadowy realm with twelve different shadowy enemies, each guarding a unique shadowy item. All monsters in the Shadow Rifts have 100% Physical Resistance - use elemental damage to combat them. Three of the enemies await behind each entrance rift.

To be even more clear: once you make Physical Resistance be 100% - which I proved was the case with my session log - I will approve this.

As coded, your test was depending on an impossible code path.
I adjusted it to test the actual code path.
And then I adjusted that code path to actually work the wy you'd hoped it would.
I also adjusted the Physical Resistance to 100%, which, as I said, my session logged proved it to be.
This should be good to go now.


Auto commenting feature for new PR raised

This feature aims to address the problem of delayed and inconsistent communication following the raising of PRs. By automatically commenting on PRs as soon as they are raised, it ensures that contributors receive immediate feedback and acknowledgment for their efforts. This fosters a positive and supportive environment for collaboration, encouraging continued participation and engagement from contributors.
Could you please assign me this issue under GSSOC'24.

could you share how you would make this automated ??

assign me in this issue to contribute

could you share how you would make this automated ??

I will be adding a YAML file in the .github directory to define this workflow of auto commenting on the trigger of a pull request being raised


Add Anzen to ecosystem page

What changed? Why?
Adding Anzen to Ecosystem page
Notes to reviewers
Anzen is a RWA-backed stablecoin
Additional Informational Links:

https://partners.circle.com/anzen
https://app.rwa.xyz/assets/USDz
https://defillama.com/protocol/anzen-v2
https://coinmarketcap.com/currencies/anzen-finance/

How has it been tested?
Anzen has been audited by Zellic, Peckshield, and Halborn.
https://docs.anzen.finance/developer-resources/audits

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

@bshyong
Hi there! Thanks for this PR! We require that defi-related additions linked to from base.org include a terms of service / terms and conditions page for users. It doesn't appear that this is present on the linked page. In order to continue the review, could you all please update and resubmit?

thanks @wbnns. Updated and resubmitted here
https://github.com/base-org/web/pull/1191


Switch whether Config API Gets called from ort script based on mode

Now, the API gets called no matter the mode, but in REVALIDATE mode, the API should not be called.

Added with 0d4764c4ef33fb9ed6348e1e1627118e0710c0a2


Chef-13: remove method_missing access to node object.

So again the reasons why we break this:

node.class vs. node['class'] kinds of problems
adding node#foo to Chef::Node as an extension to the API and
breaking node.foo meaning node["foo"] (we can't make exensions
to that class without possibly breaking someone)
crazy things like the old CHEF-3799 issue in the old ticketing
system where IO#puts in ruby blindly calls #to_ary on stuff and
expects it to raise -- whereas we would potentially autovivify
a 'to_ary' hash key and return nil which breaks the world.

This also has caused issues with the hashie gem and they've gone to
spamming warnings by default to try to deal with it:
https://github.com/berkshelf/berkshelf/issues/1665

@chef/client-core travis willing this should be ready to review


Polyfill groups are not guarded on missing a native implementation

If browsers start natively supporting GroupEffect or SequenceEffect the polyfill will overwrite them with it's own incomplete implementation (group easing is not supported). See src/group-constructors.js.

This is intentional -- there are no native implementations to fall back on. We don't know what the native implementations of these features are going to look like yet, automatically falling back would likely break content.


AnimatedSprite normal maps not working when the project is run (only works in the editor)

Bugsquad note: This issue has been confirmed several times already. No need to confirm it further.

Godot version:

Godot_v3.2.3-stable_win64
OS/device including version:

Windows 10, OpenGL ES 3.0 Renderer: GeForce GTX 970/PCIe/SSE2
Issue description:

When adding a normal map to an AnimatedSprite, the normal map does not always take effect as expected. It seems to work in the editor, but not when the scene is run. Issue https://github.com/godotengine/godot/issues/38509 includes a comment saying this feature "doesn't work", but I don't know if the issue was subsequently resolved, since the documentation was updated to suggest that it should be working.
Steps to reproduce:
Add an Animation to the SpriteFrames for an Animated sprite, and add another Animation with a normal map using the same name with _normal appended. The expected behaviour (the normal map affects lighting) can be seen in the editor, but is not seen when the scene is run. Opening an existing project with normal maps already added also exhibits the same problem.
Minimal reproduction project:

2D Lighting.zip
The normal map animation (spin_normal) doesn't take effect in the editor unless the spin animation is either removed and re-added or renamed to something else and the renamed back to spin. the normal map also doesn't take effect when the scene is run.

I have also encountered this issue.

As a workaround, I suppose you can use the Sprite + AnimationPlayer workflow instead of AnimatedSprite. It requires more work to setup, but it's technically a more powerful approach.

I began doing that but my sprite sheets have sizes that's a power of two (like 512x512, 1024x1024 etc) and there's blank space padded at the bottom or spacing between rows of sprites. The slicing algorithm does not seem to handle that afaik, which is topic for another issue. I was hoping to use the simpler and easier to use AnimatedSprite for static (but animated) objects like trees, torches etc as it seems perfect for that.

In my project it is working like a charm. Maybe the issue can be closed now?

@pietrodito can you please provide some insight how it is working like a charm for you?

Here the initial project of the OP with normal map fixed.
Here a .gif that shows it works on my v3.3.1
Here a StackExchange question for details

The "fixed" project includes a custom shader.
This seems like a good workaround, but I don't think I'd consider the issue fixed unless the intended behaviour is for normal maps to do nothing by default.

Yes, still a problem.

Is this still reproducible in the latest 4.x builds?

Add an Animation to the SpriteFrames for an Animated sprite, and add another Animation with a normal map using the same name with _normal appended.

In 4.0, support for normal and specular maps in AnimatedSprite2D (via _normal and _specular) has been removed in #43052 in favor of CanvasTexture.
But I don't know if this issue remained in one form or another in 4.0 and in 3.x.

so there's no way to use normal/specular maps with an animated sprite at all anymore then?

Ah ok I see, so you just add the frames from a CanvasTexture resource in the SpriteFrames editor

Fixed by #80406.


fix: google docstrings warns section

The Warns sections of google docstrings were incorrectly marked as Attributes. I saw this while trying to build a site using mkdocstrings-python.

Ha, good catch, thank you so much!

Happy to help!


fix(ssl): verify host on macos [INS-3424]

Always verify the hostname on macOS even when Validate certificates is disabled.

Can't reproduce this issue on Windows with validate certificates disabled, but not verify it on Linux, so I think OpenSSL always verifies the hostname.
To make the smallest change, it only enables the hostname verification on macOS.

Have verified locally, that the regression issue has been fixed on macOS.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

To make the smallest change, it only enables the hostname verification on macOS.

Correcting it is enabled by default on macOS, this change removes the line disabling it on macOS


Use a CODEOWNERS file to identify maintainers?

Following discussion at this week's Pythia Community Meeting, I'm looking into some easy steps we could take to have identified maintainers for each cookbook repo. The overarching idea is that when people contribute new cookbook content to the gallery, we're setting an expectation that someone will help keep an eye on its health.
Features that I think would be helpful to have:

specific individual users identified as having opted in to being maintainers for the cookbook content
Maintainers (along with the core Pythia team) have push access to the repo
Maintainers get tagged for PR reviews
Maintainers receiving notifications when health-testing builds are failing

Seems to me the simplest way to achieve at least goals 1 - 3 is just to include a .github/CODEOWNERS file in each cookbook repo. The content of that file can be as simple as
* @[maintainer1 username]

or for multiple maintainers
* @[maintainer1 username] @[maintainer2 username] @[maintainer3 username]

etc.
As part of the Cookbook review process, prior to accepting a new Cookbook into the gallery, reviewers can just check to see that maintainers have been specified in the CODEOWNERS file, and verify that those individuals have consented to this.
Future changes to the maintainer list would just take the form of PRs making changes to the CODEOWNERS file.
This seems like something simple enough that we can implement it very quickly, with an empty CODEOWNERS file here in the template, and a brief update to our Contributor's Guide explaining how to add names to a new cookbook.
The big advantage that I see to this approach is that it keeps things simple. We don't build any new automation that we need to then maintain. All the automation comes from GitHub itself, which will use the CODEOWNERS file to auto-tag maintainers for reviews of PRs.

An alternative is to create GitHub teams associated with each cookbook. Team members would be the identified maintainers. In this case, we would still have a CODEOWNERS file but it would look like
* @ProjectPythia/[name of the cookbook team]

and all maintainers would need to be members of the ProjectPythia organization (which is already our goal).
One advantage of this approach is it would let us ping the maintainers with an @ reference to the team rather than individually. But that doesn't seem like a big deal. There might be bigger advantages to setting up teams with respect to setting up automation in the future.

I've been looking at how this all works in conda-forge as a model, where individual feedstock repos have identified maintainers who are members of the broad organization but only have push access to the feedstock repos they maintain.
@dopplershift I have a question that you might be able to answer about how teams are used in feedstock repos.
For example, one of the feedstocks I maintain has this team:
https://github.com/orgs/conda-forge/teams/climlab
but it also has a CODEOWNERS file with the same individuals explicitly listed:
https://github.com/conda-forge/climlab-feedstock/blob/main/.github/CODEOWNERS

Why does the CODEOWNERS file list individuals rather than listing the team? Does this apparent redundancy serve a purpose?
Is the team used in some of the conda-forge automation in ways that might become useful for Project Pythia?
Should we stick with the simple, explicit approach of just manually editing a CODEOWNERS file instead?

I'm not sure why the CODEOWNERS doesn't list a team, but I will say that the team roster is managed by a bot, and that the CODEOWNERS is automatically generated, all from the list of maintainers in the recipe.
Since teams are an organization-level concept, there are a few feedstocks that use the same team across multiple feedstocks. I believe most of the R ecosystem has this.

Maybe this is something the infrastructure team can discuss during next week's hackathon. I would love to have some minimal system in place after hackathon to keep track of maintainers.

One case to consider: We have Cookbooks written by a team of scientists, one of them does all of the work to push their final code to its Cookbook repo (or to take a tutorial they wrote together and translate it into a Cookbook). In this case there are authors that are manually added that aren't represented in the contributor's file. Should we still give them maintainer status?

One case to consider: We have Cookbooks written by a team of scientists, one of them does all of the work to push their final code to its Cookbook repo (or to take a tutorial they wrote together and translate it into a Cookbook). In this case there are authors that are manually added that aren't represented in the contributor's file. Should we still give them maintainer status?

That decision should be made by the author team, not us. We're looking for individuals who volunteer some interest in staying connected to the cookbook over time.


There was an error provisioning

Keybase GUI Version: 1.0.23-20170522110822+8a8aea0
Not specifically a problem with the GUI version. It started when I wanted to add a public ZCash address via the website. That didn't work, with the below error. Then I downloaded the mobile and desktop clients but cannot login in either because they give this same error after entering the device name.
There was an error provisioning
Unknown error: downgrade lease (by KID) active for 0101188a...........very long string...........

On it, thanks!

Wow, that's lightspeed. Did I press submit already?

should be fixed!  though i hope you are not in a stuck state
can you try it again?

 Thanks.

thank you, sorry for the bug!!!


Container: set name when known

jenkins/superCI comment

Status: success, return code = 0
Result url: https://da.gd/HbXw
Comment: See details for logs

jenkins/superCI comment

Status: success, return code = 0
Result url: https://da.gd/wppJN
Comment: See details for logs


BA-361 remove padding bottom from text-2-up so when multiple are stac…

…ked it looks tighter

spacing will need to be added to pages with spacer component

@lisafolkerson This ones to master sneaky sneaky!

@Braedencraig 🤠 sorry i keep making it the wild west out here. it is changed!


feat: add dapr lib and method invocation to podtato-service/main

Signed-off-by: Engin Diri<EMAIL_ADDRESS>

Hi @dirien - thanks for trying this, we'd love to integrate some infrastructure and use Dapr here! Perhaps you'd like to open an issue to discuss and coordinate further. Best -Josh.

hi @joshgav, oh sorry, i wanted to do the PR on my Fork and wrongly created it on the upstream. :)
But, yes i can create an issue, to see what could be a good way to incorporate dapr in the podtato-head project.


feat: mock nfts and txs hiro requests

Try out Leather build e52e0d9 — Extension build, Test report, Storybook, Chromatic

This pr adds mocking of hiro txs, bns names and nfts requests in tests

Is this issue needed for linking? https://github.com/leather-io/issues/issues/193

@markmhendrickson I'm continue working on the task, there will be one more pr at least


I want to add a loaded animation when using link loading

I want to add a loaded animation when using link loading

you can use component from ui framework like this
https://www.antdv.com/components/spin

However, Vue PDF is responsible for loading files when using links. I cannot add spin at the beginning and end

I am now requesting Base64 and adding animation

Thanks for the suggestion @tomhoma!
However, I would suggest to convert this issue to discussion, as it doesn't refer directly to the library, but rather to its application.
It also depends on whether you are displaying all pages at once or page by page. Please provide more details when opening a discussion. Thanks!


Error: unreachable or not Linux x86_64

VSCode Version: x64 1.34.0-insider
OS Version: Win7

Steps to Reproduce:

Attempt to ssh to remote machine (CentOS with default shell tcshell (/bin/bash is exists))
Output:
Confirming that foo is a valid reachable host
Running type "C:\Users\me\AppData\Local\Temp\vscode-linux-multi-line-command-        foo.sh" | ssh  foo to confirm the host platform
>
> Pseudo-terminal will not be allocated because stdin is not a terminal.
>
> Warning: Permanently added the RSA host key for IP address 'xx.xxx.xxx.xxx' to the list of  known hosts.
> Warning: no access to tty (Bad file descriptor).
> Thus no job control in this shell.
> TERM: Undefined variable.
>
"uname" terminal command done
foo: unreachable or not Linux x86_64. (TERM: Undefined variable.)

Same issue here. Trying to connect to a Azure VM on my local Mac machine. Failed.

Trying to log in to Centos 7,
)```


[1888] Add higher spec device to guidance

Context

https://trello.com/c/2rGmfvqf/1888-upload-device-content-for-persona-i

Changes proposed in this pull request

Update device guidance to container higher spec device specifications

Guidance to review

Visit https://dfe-ghwt-pr-1596.herokuapp.com/devices/device-specification
See updated content and table about higher spec device

@markhallen agreed. not sure how we can improve this though


Serverside sessions

I wrote up a little session implementation based on an unencrypted memory store.
Added a little example and doc as well.
I'm currently considering implementing a redis based store as well and checking if I can somehow encrypt the stored data.
~ Lars

@LarsVomMars Thank you!  I’ll review tomorrow (it’s late in my time zone now


Problem with creating access control for service

Hello,
I have problem with creating Access Permission Restricted for Service (Group access). It's JS error in console:
On Firefox (latest):
m.resourceControl is undefined
On Chrome (latest) more info (2 errors):
TypeError: a.go is not a function     at app.c952d291.js:29     at o.$broadcast (app.c952d291.js:3)     at app.c952d291.js:10     at o.$broadcast (app.c952d291.js:3)     at app.c952d291.js:3     at o.$eval (app.c952d291.js:3)     at o.$digest (app.c952d291.js:3)     at o.$apply (app.c952d291.js:3)     at app.c952d291.js:1     at Object.invoke (app.c952d291.js:1)
Uncaught TypeError: Cannot read property 'ResourceId' of undefined     at k (app.c952d291.js:32)     at ea.fn.init.<anonymous> (app.c952d291.js:32)     at ea.fn.init.a.buttons.confirm.callback (app.c952d291.js:20)     at e (app.c952d291.js:20)     at HTMLButtonElement.<anonymous> (app.c952d291.js:20)     at HTMLDivElement.dispatch (app.c952d291.js:17)     at HTMLDivElement.q.handle (app.c952d291.js:16)
Result: unable to confirm assigment of permission to group.
Portainer version: 1.13.6 (installed as docker image from docs with mounted docker.sock and local data folder)

Hi @masahuku, this issue has been fixed via: https://github.com/portainer/portainer/issues/1043
It will be released soon, in the meantime you can use our unstable build via portainer/portainer:develop (Linux amd64 build).

Thx! Could not find that before, apologies :).


Split existing docs content into How-To And Reference

Most of the docs content for the Paketo buildpacks currently sits in the How-To section. The current docs content for each buildpack should be split into How-to and Reference pages, in keeping with the new information architecture of the site.
For ease of logistics, each buildpack's docs should be split in its own pull request. Language family maintainers should be contacted to have a look at reorganized docs before merging.

[x] .NET Core https://github.com/paketo-buildpacks/paketo-website/pull/206
[x] Go https://github.com/paketo-buildpacks/paketo-website/pull/205
[x] NGINX https://github.com/paketo-buildpacks/paketo-website/pull/208
[x] HTTPD https://github.com/paketo-buildpacks/paketo-website/pull/208
[x] Ruby https://github.com/paketo-buildpacks/paketo-website/pull/215
[x] Java Native Image https://github.com/paketo-buildpacks/paketo-website/pull/227
[x] Java https://github.com/paketo-buildpacks/paketo-website/pull/227
[x] Node.js https://github.com/paketo-buildpacks/paketo-website/pull/222
[x] PHP https://github.com/paketo-buildpacks/paketo-website/pull/224

Since all of the PRs for individual languages have been merged, this megaissue is done.


Check for duplicates in related questions

"Where can I learn about AI alignment" is definitely an important and popular question, but we shouldn't need to show it multiple times on a page. In general, if a question is already on the page, we probably should remove and keep the one closest to top of screen?

Wiki issue with redirects, one is page id 5635, the other 8125.
@plexish said it would be solved by the big cleanup they are doing with Matt, so let's see after that.

I think #25 was our plan for this, but we can patch for now by fixing the initial questions related lists.

Yes, they're very similar but I was more concerned with the initial interactions here. Overall, things already look a whole lot better today with the initial questions & their related questions cleaned up. So, I'll close this one out.
It sounds like the UI is already checking for duplicates using page id but the wiki had the same question with 2 separate page ids (5635 & 8125). I'm still able to get that question more than once on screen, so something still amiss.


Separate "Reset Homebridge" button at bottom of status page

Please separate the "reset homebridge - homebridge-config-ui-x v3.9.6 - node.js v11.4.0" buttons at bottom of Status page.  It is not intuitive that these are separate and it looks like one big long string.  Caused some unnecessary troubleshooting issues today when helping users.

Links will now underline when the user hovers over them to show they are separate:


New Stratis Core 2.0 Features / UI

A number of updates for the new UI, just here for visibility.

Merging so we can both work from this, comments will be handled in an upcoming PR.


Merge beta changes to alpha

Description
This will solve a bunch of sonar issues already solved in beta.
Breaking Changes
NA
JIRA Link
NA
Checklist

[ ] Updated the Readme.md (if required) ?

I left 2 code smells saying change || into ?? operator. I think its reasonable. I think its better to update them instead of ignoring.

:tada: This PR is included in version 20.2.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 21.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Create different file formats, add notes and shutdown after specific time(for Windows)

First feature: Say "create filename word document" and benji will create a word document "filename.docx" on the desktop. This feature works with text, word, powerpoint/presentation, excel, visio, rtf(rich). The first and the last words are constant.
Second feature: Say "note .........." and benji will create "Notes.txt" file on the desktop and save whatever you spoke.
Third feature: Say "shutdown after 0 hours 30 minutes" and benji will shutdown after the specified time. Only the numbers will change. Rest are constant. You can abort the shutdown by saying "cancel shutdown".
If you say "shutdown now", it will shutdown instantly. If you say "restart now", it will restart instantly.

NOTE(For linux): I have included "three" modules. 1) subprocess 2) pptx 3) xlsxwriter. I think, there will be a change in the path of the directory for linux. If any issue arises, the reason could be the "path".

Great work! Merging it!


Update to C# 9

copy some files from osu.framework.
change the target to C# 9

Guess the config has been updated, see #127
Another step is update target language to C# 9 and adjust the code.

Implemented.


Logs and Traces schema documentation

This PR documents the Arrow Schema for Logs and Traces.
Hopefully, the syntax used is relatively self-explanatory.aThis PR documents the Arrow scheme for logs and traces.
As far as I know, there is no official format to represent an Arrow schema. The syntax used is inspired by the one used by the Rust implementation. I hope that the syntax used is relatively explicit.
The documentation of the Metrics Arrow Schema will be part of another PR.

Can we somehow avoid repeating the schema for attributes many times?

Yes working on improving the schema description.


Closing Bracket are not Converted into Text formate

Microsoft PowerToys version
"0.62.1"
Running as admin

[X] Yes

Area(s) with issue?
TextExtractor
Steps to reproduce
This is not an error but little bit of enhancement is needed.
✔ Expected Behavior
When I tried to Extract some text with brackets, the closing brackets were missing. Opening brackets and all other text is translated fine but closing brackets get missing.
❌ Actual Behavior
Closing Brackets are Not being converted when I tried this
Other Software
No response

This is a shortcoming of the OCR engine and out of the scope of Text Extractor.


 Now rather than exiting we should probably simply report those illegal nested "uses" annotations and only use the top-level one.

Current impact handles self dependencies cleanly.  If you turn on the -v flag (e.g., when installing) it also warns about invalid dependencies.  Not sure if that is sufficient.  Feel free to reopen, but this definitely shouldn't be part of the v0.7.0 milestone in any case (since that is related to indexing)


SSLHandshakeException Received fatal alert: handshake_failure  sun.security.ssl.Alerts.getSSLException

I'm using clj-htp 1.1.0 and got this handshake_failure error.
clj-sample.core=> (require '[clj-http.client :as client]) (def url "https://8999uojw48.execute-api.us-east-1.amazonaws.com/prod/webhook")  (client/get url)
nil
#'clj-sample.core/url

SSLHandshakeException Received fatal alert: handshake_failure  sun.security.ssl.Alerts.getSSLException (Alerts.java:192)

The site only supports TLS and I'm wondering if this is caused by clj-http not using TLS for some reasons. I understand this must be handled by Apache http client but could it be the case that clj-http doesn't use TLS support?
Please let me know if you need more info. Thank you for your help!

@kimh There's support for this coming in the 3.0 branch, as mentioned here: https://github.com/dakrone/clj-http/issues/202

@jackrusher ok, that sounds good. I can close this issue, but where do I see 3.0 branch?

@kimh dunno, I've requested that the author/maintainer make a provisional release to clojars, but haven't heard anything yet.

@jackrusher @kimh I've pushed 3.0.0-SNAPSHOT to clojars, it definitely still has rough edges though!

I'll close this issue since this is already being discussed in #202

Thanks, @dakrone!