[Bug] Linker error against firebase::auth, firebase::rest

[REQUIRED] Please fill in the following fields:

Pre-built SDK from the website or open-source from this repo: Pre-built SDK.
Firebase C++ SDK version: 10.3.0
Problematic Firebase Component: _____ (Auth, Database, etc.)
Other Firebase Components in use: _____ (Auth, Database, etc.)
Platform you are using the C++ SDK on: Linux
Platform you are targeting: Desktop

[REQUIRED] Please describe the issue here:
(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)
Steps to reproduce:
Have you been able to reproduce this issue with just the Firebase C++ quickstarts ?
What's the issue repro rate? 100%
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
After compiling the entire source code within my project, linker throws many errors, from which I append a little amount of them.
/usr/bin/ld: ../3rdparty/firebase_cpp_sdk_10.3.0/libs/linux/x86_64/cxx11/libfirebase_storage.a(538e7a99191fd4c376929db91d6afe4a_curl_requests.cc.o):(.data.rel.ro._ZTVN8firebase7storage8internal24ReturnedMetadataResponseE[_ZTVN8firebase7storage8internal24ReturnedMetadataResponseE]+0x40): referencia a `firebase::rest::Response::GetBody(char const**, unsigned long*) const' sin definir
/usr/bin/ld: ../3rdparty/firebase_cpp_sdk_10.3.0/libs/linux/x86_64/cxx11/libfirebase_storage.a(538e7a99191fd4c376929db91d6afe4a_metadata_desktop.cc.o): en la función `firebase::storage::internal::MetadataInternal::ImportFromJson(char const*)':
metadata_desktop.cc:(.text+0x3282): referencia a `vtable for firebase::rest::util::JsonData' sin definir
/usr/bin/ld: metadata_desktop.cc:(.text+0x32b6): referencia a `firebase::rest::util::JsonData::Parse(char const*)' sin definir
/usr/bin/ld: metadata_desktop.cc:(.text+0x32da): referencia a `vtable for firebase::rest::util::JsonData' sin definir
/usr/bin/ld: metadata_desktop.cc:(.text+0x34fa): referencia a `firebase::Path::Path(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' sin definir
/usr/bin/ld: metadata_desktop.cc:(.text+0x3502): referencia a `firebase::Path::GetBaseName() const' sin definir
/usr/bin/ld: ../3rdparty/firebase_cpp_sdk_10.3.0/libs/linux/x86_64/cxx11/libfirebase_storage.a(538e7a99191fd4c376929db91d6afe4a_metadata_desktop.cc.o): en la función `firebase::storage::internal::MetadataInternal::ImportFromJson(char const*) [clone .cold]':
metadata_desktop.cc:(.text.unlikely+0x4fe): referencia a `vtable for firebase::rest::util::JsonData' sin definir
/usr/bin/ld: ../3rdparty/firebase_cpp_sdk_10.3.0/libs/linux/x86_64/cxx11/libfirebase_storage.a(538e7a99191fd4c376929db91d6afe4a_rest_operation.cc.o): en la función `firebase::storage::internal::RestOperation::~RestOperation()':
rest_operation.cc:(.text+0x474): referencia a `firebase::rest::TransportCurl::~TransportCurl()' sin definir
/usr/bin/ld: ../3rdparty/firebase_cpp_sdk_10.3.0/libs/linux/x86_64/cxx11/libfirebase_storage.a(538e7a99191fd4c376929db91d6afe4a_rest_operation.cc.o): en la función `firebase::storage::internal::RestOperation::RestOperation(firebase::storage::internal::StorageInternal*, firebase::storage::StorageReference const&, firebase::rest::Request*, firebase::storage::internal::Notifier*, firebase::storage::internal::BlockingResponse*, firebase::storage::Listener*, firebase::FutureHandle, firebase::storage::Controller*)':
rest_operation.cc:(.text+0x584): referencia a `firebase::rest::TransportCurl::TransportCurl()' sin definir
/usr/bin/ld: rest_operation.cc:(.text+0x648): referencia a `firebase::rest::TransportCurl::PerformInternal(firebase::rest::Request*, firebase::rest::Response*, std::unique_ptr<firebase::rest::Controller, std::default_delete<firebase::rest::Controller> >*)' sin definir
/usr/bin/ld: ../3rdparty/firebase_cpp_sdk_10.3.0/libs/linux/x86_64/cxx11/libfirebase_storage.a(538e7a99191fd4c376929db91d6afe4a_rest_operation.cc.o): en la función `firebase::storage::internal::RestOperation::RestOperation(firebase::storage::internal::StorageInternal*, firebase::storage::StorageReference const&, firebase::rest::Request*, firebase::storage::internal::Notifier*, firebase::storage::internal::BlockingResponse*, firebase::storage::Listener*, firebase::FutureHandle, firebase::storage::Controller*) [clone .cold]':
rest_operation.cc:(.text.unlikely+0xe9): referencia a `firebase::rest::TransportCurl::~TransportCurl()' sin definir
/usr/bin/ld: warning: creating DT_TEXTREL in a PIE
collect2: error: ld returned 1 exit status
gmake[2]: *** [CMakeFiles/myosoft.dir/build.make:421: myosoft] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:190: CMakeFiles/myosoft.dir/all] Error 2
gmake: *** [Makefile:136: all] Error 2

Compiled the project using:
mkdir build && cd build && cmake .. -Wno-dev && cmake --build . -j8
If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.
Relevant Code:
My CMakeLists.txt file contain these directives:
cmake_minimum_required(VERSION 3.14)

project(TestProject VERSION 2.4.0 LANGUAGES CXX)
add_definitions(-DAPP_VERSION="${CMAKE_PROJECT_VERSION}")

set(CMAKE_AUTOUIC ON)
set(CMAKE_AUTOMOC ON)
set(CMAKE_AUTORCC ON)
set(CMAKE_CXX_STANDARD 17)
set(CMAKE_CXX_STANDARD_REQUIRED ON)
...
add_subdirectory(3rdparty/firebase_cpp_sdk_10.3.0)
...
target_link_libraries(${PROJECT_NAME}
    firebase_app
    firebase_auth
    firebase_database
    firebase_firestore
    firebase_storage
)

My main.cpp file is just a test with example code retrieved from the examples folder in this repo, I don't really own it, I wanted to test the library:
// Main test for Firebase library

#include "firebase/auth.h"
#include "firebase/auth/credential.h"
#include "firebase/storage.h"
#include "firebase/util.h"

#include <unistd.h>
#include <iostream>

using ::firebase::App;
using ::firebase::AppOptions;
using ::firebase::Future;
using ::firebase::FutureBase;
using ::firebase::auth::Auth;
using ::firebase::auth::AuthError;
using ::firebase::auth::Credential;
using ::firebase::auth::EmailAuthProvider;
using ::firebase::auth::kAuthErrorNone;
using ::firebase::auth::SignInResult;
using ::firebase::auth::User;
using ::firebase::auth::UserInfoInterface;

auto const kEmail    =<EMAIL_ADDRESS>auto const kPassword = "blablabla";

bool ProcessEvents(int msec)
{
    usleep(msec * 1000);
    return false;
}

bool WaitForFuture(const FutureBase& future,
                   const char* fn,
                   AuthError expected_error,
                   bool log_error = true)
{
    // Note if the future has not be started properly.
    if (future.status() == ::firebase::kFutureStatusInvalid)
    {
        std::cout << "ERROR: Future for " << fn << " is invalid" << std::endl;
        return false;
    }

    // Wait for future to complete.
    std::cout << "  Calling " << fn << "..." << std::endl;
    while (future.status() == ::firebase::kFutureStatusPending)
    {
        if (ProcessEvents(100))
            return true;
    }

    // Log error result.
    if (log_error)
    {
        const AuthError error = static_cast<AuthError>(future.error());
        if (error == expected_error)
        {
            const char* error_message = future.error_message();
            if (error_message)
            {
                std::cout << fn << " completed as expected" << std::endl;
            }
            else
            {
                std::cout << fn << " completed as expected, error: " << error
                          << ", error_message: " << error_message << std::endl;
            }
        }
        else
        {
            std::cout << "ERROR: " << fn << " completed with error: " << error
                      << ", error_message: " << future.error_message() << std::endl;
        }
    }
    return false;
}

bool WaitForSignInFuture(Future<User*> sign_in_future,
                         const char* fn,
                         AuthError expected_error,
                         Auth* auth)
{
    if (WaitForFuture(sign_in_future, fn, expected_error))
        return true;

    const User* const* sign_in_user_ptr = sign_in_future.result();
    const User* sign_in_user            = sign_in_user_ptr == nullptr ? nullptr : *sign_in_user_ptr;
    const User* auth_user               = auth->current_user();

    if (expected_error == ::firebase::auth::kAuthErrorNone && sign_in_user != auth_user)
    {
        std::cout << "ERROR: future's user ("
                  << static_cast<int>(reinterpret_cast<intptr_t>(sign_in_user))
                  << ") and current_user ("
                  << static_cast<int>(reinterpret_cast<intptr_t>(auth_user)) << ") don't match."
                  << std::endl;
    }

    return false;
}

bool WaitForSignInFuture(const Future<SignInResult>& sign_in_future,
                         const char* fn,
                         AuthError expected_error,
                         Auth* auth)
{
    if (WaitForFuture(sign_in_future, fn, expected_error))
        return true;

    const SignInResult* sign_in_result = sign_in_future.result();
    const User* sign_in_user           = sign_in_result ? sign_in_result->user : nullptr;
    const User* auth_user              = auth->current_user();

    if (expected_error == ::firebase::auth::kAuthErrorNone && sign_in_user != auth_user)
    {
        std::cout << "ERROR: future's user ("
                  << static_cast<int>(reinterpret_cast<intptr_t>(sign_in_user))
                  << ") and current_user ("
                  << static_cast<int>(reinterpret_cast<intptr_t>(auth_user)) << ") don't match."
                  << std::endl;
    }

    return false;
}

int main(int argc, char* argv[])
{
    // Create app
    auto app = App::Create();

    // Create auth class for app
    ::firebase::ModuleInitializer initializer;
    initializer.Initialize(app, nullptr, [](::firebase::App* app, void*) {
        ::firebase::InitResult init_result;
        Auth::GetAuth(app, &init_result);
        return init_result;
    });

    while (initializer.InitializeLastResult().status() != firebase::kFutureStatusComplete)
    {
        if (ProcessEvents(100))
        {
            // return 1; // exit if requested
        }
    }

    if (initializer.InitializeLastResult().error() != 0)
    {
        std::cout << "Failed to initialize: " << initializer.InitializeLastResult().error_message();
        ProcessEvents(2000);
        // return 1;
    }

    auto auth = Auth::GetAuth(app);
    auto user = auth->current_user();

    // Check already signed-in user
    if (user == nullptr)
    {
        std::cout << "No signed in user." << std::endl;
    }
    else
    {
        std::cout << "Current signed in user: " << user->uid().c_str() << " - "
                  << user->display_name().c_str() << std::endl;
        auth->SignOut(); // Sign user out
    }

    // Test auth with credentials
    Credential email = EmailAuthProvider::GetCredential(kEmail, kPassword);

    Future<User*> sign_in_future = auth->SignInWithEmailAndPassword(kEmail, kPassword);
    WaitForSignInFuture(sign_in_future,
                        "Auth::SignInWithEmailAndPassword() existing email and password",
                        kAuthErrorNone, auth);

    // Sign out after sign in test
    if (sign_in_future.status() == ::firebase::kFutureStatusComplete)
    {
        std::cout << "Sign-in future completed." << std::endl;
        auth->SignOut();
    }
}

Hi @adrichainz,
Can you help verify something? First do you need to use storage or database or firestore SDKs? In you main cpp test code I only see the usage of auth apis, and the linker error is regarding to storage SDK. Let's simplify the scenario, can you only include firebase_app and firebase_auth in your cmake file to test if that builds?

Hi @cynthiajoan thanks for your response!
You're right, I was overloading my project unnecessarily. I just took out all the libs except firebase_app and firebase_auth but I still can't compile, now the only error I get is as follows:
gmake[2]: *** No rule to make target '../3rdparty/firebase_cpp_sdk_10.3.0/libs/linux/x86_64/cxx11/libfirebase_app.a', needed by 'TestProject'.  Stop.
gmake[2]: *** Waiting for unfinished jobs....

Looking at the error message above, I was wondering why the lib couldn't be found. Looking at the library structure, I saw that libs/linux directory doesn't exist.

I see that release 10.2.0's changeslist said "Fixed linux x86 libraries" but I can't find the libraries there either.

hmmm so here are two things to try:

I double checked the release package and find linux folder inside libs, can you download again and check the sdk package?
How you add the cpp sdk into the project is not align with the instruction, can you try follow this link to address these section:

Configure the testapp with the location of the Firebase C++ SDK. This can be done a couple different ways (in highest to lowest priority):

When invoking cmake, pass in the location with -DFIREBASE_CPP_SDK_DIR=/path/to/firebase_cpp_sdk.
Set an environment variable for FIREBASE_CPP_SDK_DIR to the path to use.
Edit the CMakeLists.txt file, changing the FIREBASE_CPP_SDK_DIR path to the appropriate location.

thanks @cynthiajoan you are right, I was including the SDK inside my project instead of placing it somewhere else and referencing it from the CMake configuration.
I changed my CMake configuration to add_subdirectory(/home/amg/software/firebase-cpp-sdk-10.3.0 bin/).
For compiling, I'm doing as following:
mkdir && cd build
cmake .. -DFIREBASE_CPP_SDK_DIR="/home/amg/software/firebase-cpp-sdk-10.3.0"
cmake --build . -j8

Now I'm not getting the linker errors and the libfirebase_app.a is found, but I'm getting a bigger problem: project keeps looking for Android dependencies, but my purpose is building for DESKTOP:
/home/amg/projects/personal/TestProject/build/bin/external/src/flatbuffers/samples/android/jni/main.cpp:15:10: fatal error: android/log.h: No such file or directory
   15 | #include <android/log.h>
      |          ^~~~~~~~~~~~~~~
compilation terminated.
/home/amg/projects/personal/TestProject/build/bin/external/src/uWebSockets/tests/main.cpp:3:10: fatal error: uWS.h: No such file or directory
    3 | #include "uWS.h"
      |          ^~~~~~~
compilation terminated.
/home/amg/projects/personal/TestProject/build/bin/external/src/flatbuffers/android/jni/main.cpp:17:10: fatal error: android_native_app_glue.h: No such file or directory
   17 | #include <android_native_app_glue.h>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

Am I missing anything? How can I explicitly tell to the SDK not to build for Android and to focus only on Desktop?
I've tried setting set(ANDROID OFF) but it's not solving anything.

Hi @adrichainz,
I highly recommend taking a step back and start with the re-use of one of our integration test cmake files. This has been configured to build and link against our SDKs in a way that we know works. Since your example code uses auth, you could use our Auth Integration Test cmake file as a guide. There are library link steps, including pthread, that aren't in your cmake file, for instance.
I'd also recommend paring down your example code to just try to initialize auth, and see if you can get that to compile and line.
Sorry I don't have any better suggestions, but I think this is probably the best way forward at this point.


Incorrect handling of missing values in Statistics

As per the parquet-format specs the min/max values in statistics are optional. Therefore, it is possible to have numNulls in Statistics while we don't have min/max values. In StatisticsFilter we rely on the method StatisticsFilter.isAllNulls(ColumnChunkMetaData) to handle the case of null min/max values which is not correct due to the described scenario.
We shall check Statistics.hasNonNullValue() any time before using the actual min/max values.
In addition we don't check if the null_count is set or not when reading from the parquet file. We simply use the value which is 0 in case of unset. In the parquet-mr side the Statistics object uses the value 0 to sign that the num_nulls is unset. It is incorrect if we are searching for null values and we falsely drop a column chunk thinking there are no null values but the field in the statistics was simply unset.
Reporter: Gabor Szadovszky / @gszadovszky
Assignee: Gabor Szadovszky / @gszadovszky
Related issues:

Release Parquet-mr 1.8.3 (blocks)
Parquet MR bug can lead to incorrect SQL results (causes)

PRs and other links:

GitHub Pull Request #465
PR

Note: This issue was originally created as PARQUET-1217. Please see the migration documentation for further details.

Zoltan Ivanfi / @zivanfi:
Issue resolved by pull request 458
https://github.com/apache/parquet-mr/pull/458


Stable candidate branch is not filtering out builds that are not longer in main

https://flutter-dashboard.appspot.com/#/build?taskFilter&authorFilter&messageFilter&hashFilter&showMac=true&showWindows=true&showiOS=true&showLinux=true&showAndroid=true&showStaging=false&repo=flutter&branch=flutter-3.10-candidate.1

The expectation is that all the yellow builders should be white instead.

This is working as expected the reason it seemed as it was not being filtered is that no new commits have landed in the branch since the filtering was implemented.


Obfuscating a sensitive field

I would like to track the history of an object with some sensitive fields (like a password).  The value of the change is irrelevant but who changed it and the fact that it changed is important.  Is there a configuration that will handle this?

I don't think we have anything built in to handle this, but we should. Labeling as a feature request, feel free to try to implement something.
Obviously, you should never store a password as is :)

I'll start taking a look at this.
I don't see a tag for 0.6.0, is it the current master branch?

The 0.6.0 release was made off a fork before we got hold of @aq1018 to move repos. I've tagged it on master, appreciate if you could double-check that I tagged the right revision please.


Added more replies to unknown

Added 4 more possible replies when the user sends a message that the bot cannot understand.

Suji wala response add kar na
On Tue 19 Feb, 2019, 12:05 PM Amey Khale<EMAIL_ADDRESS>wrote:

Added 4 more possible replies when the user sends a message that the bot
cannot understand.
You can view, comment on, or merge this pull request online at:
https://github.com/ArionMiles/MIS-Bot/pull/33
Commit Summary

Added more replies to unknown

File Changes

M mis_bot/misbot/general.py
https://github.com/ArionMiles/MIS-Bot/pull/33/files#diff-0 (6)

Patch Links:

https://github.com/ArionMiles/MIS-Bot/pull/33.patch
https://github.com/ArionMiles/MIS-Bot/pull/33.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ArionMiles/MIS-Bot/pull/33, or mute the thread
https://github.com/notifications/unsubscribe-auth/AbPF_w3L_BhjUI-NP7PUMqPidbM070tdks5vO5s4gaJpZM4bCRaP
.

Totally forgot, put your name in contributors section of README.


If wrong issuer url , the error management module is not triggered.

example of QR code value
openid-credential-offer://?credential_offer%7B%22credential_issuer%22%3A%22boruta%22%2C%22credentials%22%3A%5B%22VerifiableCredential%22%2C%22UniversityDegreeCredential%22%5D%2C%22grants%22%3A%7B%22urn%3Aietf%3Aparams%3Aoauth%3Agrant-type%3Apre-authorized_code%22%3A%7B%22pre-authorized_code%22%3A%22DFmOgsYuM5P5uoUcviasXuJrSEj2Rg3HQn3ehGSB1hGlqhf2RnYzgAPjLBsQkV8G1dbxhmPwhvk8Z0SCgShBNB%22%7D%7D%7D

The "=" for credential_offer parameter is missing.


[HIVEMALL-87] Add issues mailing list to the web site

What changes were proposed in this pull request?
Add issues mailing list to the web site.
https://hivemall.incubator.apache.org/mail-lists.html
What type of PR is it?
Documentation
What is the Jira issue?
https://issues.apache.org/jira/browse/HIVEMALL-87
How was this patch tested?
Ran mvn site and verified issues mailing list was added to ./target/site/mail-lists.html

Coverage remained the same at 36.739% when pulling eeb7e7731e49b175b0e6bc9a6999d763b17b36b2 on aajisaka:HIVEMALL-87 into 1cccf66829e2c9f6b6e51046c1fc8c19c9aff51b on apache:master.

@aajisaka Thank you for contribution! Will merge soon.

Merge. Thanks!
We have bin/build_site.sh for checking the project site.

Thank you for committing this and providing the information!


Bug: Goerli metrics not being fetched properly

Homepage shows metrics from the Beacon Chain. This is working on Mainnet version, but is broken on the Goerli version of the launchpad.

{"message":"no Route matched with those values"} returning from network request

Not seeing this anymore, closing out


Update Rayman 3 configuration

I made a few changes to Rayman 3's controls to be closer to the button configurations used in the console versions (specifically the Xbox/PS2 versions).

Thank you for these updates!


How to cancel/close a streaming response?

Req: 0.3.10
Finch: 0.16.0
I'm working on a ChatGPT client that streams responses. Following very closely to this example:
fun = fn request, finch_request, finch_name, finch_options ->
  fun = fn
    {:status, status}, response ->
      %{response | status: status}

    {:headers, headers}, response ->
      %{response | headers: headers}

    {:data, data}, response ->
      IO.puts(data)
      response
  end

  case Finch.stream(finch_request, finch_name, Req.Response.new(), fun, finch_options) do
    {:ok, response} -> {request, response}
    {:error, exception} -> {request, exception}
  end
end

Req.get!("https://httpbin.org/stream/10", finch_request: fun)

How do I cancel a streaming response? I couldn't find anything in the Req or Finch docs about that.
In my application.ex, there's this:
  {Finch, name: MyApp.OpenAIFinch}

I've wrapped the streaming call in a GenServer that I can message and shutdown, but the streaming execution continues probably because the pool is supervised separately.
Any advice or guidance on how to shutdown an actively streaming response?

I don’t think there’s a way to cancel the request started by Finch.stream function. On Finch main there are new async_request and cancel_async_request functions so I’d look into using those!

It's possible to cancel the request started by Finch.stream by throwing/raising from within the callback function. The async_request/cancel_async_request should be landing in a release soon though and should be a better option!

@brainlid fyi the plan is to have a Finch.stream_while where the callback function will return {:cont, acc} or {:halt, acc}, the latter cancelling the stream. And similarly we'd have something like:
Req.new(stream: fn {:data, data}, response ->
  IO.inspect data
  {:cont, response}
end)

stay tuned!

Closing in favour of #220.

I see the new streaming support in Req and am still wondering the best way to handle this as well. I have a function that wraps the req call which looks like:
def chat_completion(request_body, callback) do
  Req.post(@chat_completions_url,
    json: request_body,
    into: fn {:data, data}, {req, res} ->
      callback(data)
      {:cont, {req, res}}
    end
  )
end

I see that I can return {:halt, {req, res}} instead to cancel it. However, this seems to imply I need some state so that the function passed to the into option can check on each invocation if it has been cancelled and halt if so.
Is that right? Does this necessitate a genserver or agent with some state to make this work, or is there a simpler way?

There's an experimental API that uses process messages. It's available but undocumented at the moment. I'm pretty sure it will stay as is but there could be some changes before Req v1.0.
iex> Mix.install([:req])
iex> Req.async_request!("https://reqbin.org/ndjson")
iex> flush
{{Finch.HTTP1.Pool, #PID<0.243.0>}, {:data, "{\"y\":1,\"x\":1}\n"}}
{{Finch.HTTP1.Pool, #PID<0.243.0>}, {:data, "{\"y\":2,\"x\":2}\n"}}
{{Finch.HTTP1.Pool, #PID<0.243.0>}, {:data, "{\"y\":3,\"x\":3}\n"}}
{{Finch.HTTP1.Pool, #PID<0.243.0>}, :done}

iex> {req, resp} = Req.async_request!("https://reqbin.org/ndjson?delay=5000")
iex> Req.cancel_async_request(req)
iex> flush
{{Finch.HTTP1.Pool, #PID<0.243.0>}, {:data, "{\"y\":1,\"x\":1}\n"}}

That looks very helpful for removing glue code to make all this work otherwise, thank you!

Yup

Hey just a quick heads up, I ended up with a very similar but ultimately different API after all:
iex(1)> Mix.install([{:req, github: "wojtekmach/req"}])
:ok
iex(2)> resp = Req.get!("https://reqbin.org/ndjson", into: self())
#Req.Response<
  status: 200,
  headers: %{
    "cache-control" => ["max-age=0, private, must-revalidate"],
    "content-type" => ["application/x-ndjson; charset=utf-8"],
    "date" => ["Mon, 04 Mar 2024 15:20:25 GMT"],
    "fly-request-id" => ["01HR50THAK6SNNWZQX32BV1GYY-waw"],
    "server" => ["Fly/17ce28b7 (2024-03-02)"],
    "via" => ["2 fly.io"]
  },
  body: "",
  trailers: %{},
  private: %{},
  ...
>
iex(3)> Req.parse_message(resp, receive do message -> message end)
{:ok, [data: "{\"y\":1,\"x\":1}\n"]}
iex(4)> Req.parse_message(resp, receive do message -> message end)
{:ok, [data: "{\"y\":2,\"x\":2}\n"]}
iex(5)> Req.cancel_async_response(resp)
:ok

This is now on main and will be part of next release which should be out this week.


TypeError: 'NoneType' object is not subscriptable

Before submitting a bug report...

[X] This bug wasn't already reported.
(I have checked every bug report on GitHub)

[X] I've cleared the sessions folder.

Branch
master
Commit
v1.0.1
Describe the bug
Downloaded a new copy of 1.0.1. Previously using pre-release versions with success. Installed and upgraded all requirements. Login is fine, but there is an error every time it checks for daily promotions. I also note that it reports my current points a 0, so it's maybe not talking to the dashboard correctly.
Copy and paste your error
2024-09-01 17:23:35,743 [INFO] @outlook.com
2024-09-01 17:23:35,743 [DEBUG] in init
2024-09-01 17:23:51,953 [INFO] Screen size: 1890x958
2024-09-01 17:23:51,998 [INFO] Device size: 1835x807
2024-09-01 17:23:52,411 [DEBUG] out init
2024-09-01 17:23:52,411 [DEBUG] in enter
2024-09-01 17:24:45,744 [INFO] [LOGIN] Already logged-in
2024-09-01 17:25:23,318 [INFO] [POINTS] You have 0.00 points on your account
2024-09-01 17:25:23,318 [INFO] [DAILY SET] Trying to complete the Daily Set...
2024-09-01 17:26:36,653 [DEBUG] in exit exc_type=<class 'TypeError'> exc_value='NoneType' object is not subscriptable traceback=<traceback object at 0x000001A24118AA00>
2024-09-01 17:26:37,143 [ERROR]
Traceback (most recent call last):
File "C:\Users\FTP\Documents\MS-Rewards-Farmer-master\main.py", line 40, in main
earned_points = executeBot(currentAccount, args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\FTP\Documents\MS-Rewards-Farmer-master\main.py", line 243, in executeBot
DailySet(desktopBrowser).completeDailySet()
File "C:\Users\FTP\Documents\MS-Rewards-Farmer-master\src\dailySet.py", line 18, in completeDailySet
data = self.browser.utils.getDashboardData()["dailySetPromotions"]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable
2024-09-01 17:26:37,161 [WARNING] config-private.yaml doesn't exist
2024-09-01 17:26:37,161 [DEBUG] No urls found, not sending notification
2024-09-01 17:26:37,161 [INFO] [POINTS] Data saved for the next day.
Screenshots
n/a
Value of dashboard variable
Too long to paste

I came across this too. For whatever reason it takes src.utils.Utils.getBingInfo an hour or so after login to return meaningful information. Try rerunning and see what happens.

After clearing sessions again it seems to be working now. It now throws a similar error during mobile searches. This is after the previous version of the script has already done all the mobile searches for the day, so not sure if that is a factor. i will test again tomorrow.
2024-09-11 16:44:48,697 [INFO] [READ TO EARN] Completed the Read to Earn successfully !
2024-09-11 16:44:48,713 [INFO] [BING] Starting Mobile Edge Bing searches...
2024-09-11 16:45:37,408 [DEBUG] in exit exc_type=<class 'TypeError'> exc_value='NoneType' object is not subscriptable traceback=<traceback object at 0x0000027A4B765AC0>
2024-09-11 16:45:38,182 [ERROR]
Traceback (most recent call last):
File "C:\Users\FTP\Documents\MS-Rewards-Farmer-1.1.0\main.py", line 40, in main
earned_points = executeBot(currentAccount, args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\FTP\Documents\MS-Rewards-Farmer-1.1.0\main.py", line 267, in executeBot
searches.bingSearches()
File "C:\Users\FTP\Documents\MS-Rewards-Farmer-1.1.0\src\searches.py", line 119, in bingSearches
while (remainingSearches := self.browser.getRemainingSearches()) > 0:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\FTP\Documents\MS-Rewards-Farmer-1.1.0\src\browser.py", line 236, in getRemainingSearches
counters = dashboard["userStatus"]["counters"]
~~~~~~~~~^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable

Yeah saw same thing


Position scroll bar to the bottom always

Solves issue #36

I can see that 1 check is failed. But I can also see that this branch has no conflicts with the base branch. What are the chances we have now.

LGTM 💯

@Prathap-P  LGTM 💯


FBX Normal Mapping is not working

Describe the bug
A model with normal maps in FBX format is not shown with a normal map
To Reproduce
Steps to reproduce the behavior:

Open fbx file with normal mapping (normal.zip)

Normal mapping is not visible

normal.fbx : no normal, even though normal code is being executed

normal.glb: normal is working great

Expected behavior
Normal mapping should be visible
the fbx has been tested in Windows 3D viewer and works great.

@Meakk PTAL

That's because there is no tangents generated by the assimp importer. Let me check if I can fix that easily.


responseType – ignore 204 No Content?

My API returns JSON objects always, except in certain situations when a 204 No Content is returned. This is used, for instance, for successful deletes. (for further reading, check out the JSON API spec)
Setting responseType: 'json' blows up when this happens, because an empty response isn't json. The immediate reaction might be, well, don't specify the response type. I'd like to, however, because errors and all other unsuccessful deletes are returned in a JSON format.
Do folks think that it makes sense for responseType to skip trying to parse the (nonexistent) body if 204 is returned?

Oops – should have searched better. Just found this PR: https://github.com/Raynos/xhr/pull/106

Gonna reopen 'cause the JSON issue still seems to be a problem in 2.2.2.

responseType is a feature of XMLHttpRequest object see MDN and it's implemented by the browser as standard describes. It requires a JSON response no matter what and there's nothing xhr can do about it. Also, I'm not sure what the browser support is.
What you actually want is the json option for xhr (see README.md here and here)
It will not throw an error if parsing JSON fails.

Thanks, @naugtur ! I didn't think to use it because the docs only use the GET request example. Would you be open for a PR to make it a teeny bit more explicit how json can be used, and how it differs from responseType?

Sure!
It's demonstrated for GET because it wasn't obvious even for https://github.com/request/request users
I'm looking forward to a cleaner explanation. All I can ask is that you make sure it's short and not stealing attention from everything else in the README.md - other than that, there's nothing stopping what you write from getting merged.

Sure!

Awesome. I'll whip up a PR sometime in the next few days.

All I can ask is that you make sure it's short and not stealing attention from everything else in the README.md - other than that, there's nothing stopping what you write from getting merged.

Noted. I'll keep it succinct. :v:


Convert all tests to python

Fixes #189 #190 #191

Fixes #189 #190 #191

Why do we run the unit tests in containers? It feels like unnecessary work and potential for issues (hard coded paths, etc).

The tests run fine on my machine (using docker for mac). I like the setup.

LGTM


Fix broken link in documentation

In this documentation page : https://use-gesture.netlify.app/docs/motivation/
The link between "trigger logic when the gesture starts or ends out of the box" is broken
It might be because of the line break on line 22 ?

Hi, thanks for spotting the issue. I think it's related to the fact that I'm using an Easter egg wherever I mention React UseGesture.
It's actually a draggable component and its hand emoji changes every time you load the page. I guess no one noticed but anyway.
But the fact that it's positioned as the first element of the paragraph messes with MDX which considers the whole paragraph as JSX and not markdown.
I think the way to fix this at this point is to uses <code> tags instead of ticks and an actual <a> tag for the link.

Turns out adding  at the beginning of the line is enough :)

Hi, thanks for spotting the issue. I think it's related to the fact that I'm using an Easter egg wherever I mention React UseGesture.
It's actually a draggable component and its hand emoji changes every time you load the page. I guess no one noticed but anyway.
But the fact that it's positioned as the first element of the paragraph messes with MDX which considers the whole paragraph as JSX and not markdown.
I think the way to fix this at this point is to uses <code> tags instead of ticks and an actual <a> tag for the link.

The easter egg is noticed ;) I love it

Turns out adding  (invisible character) at the beginning of the line is enough :)

Awesome that you found a fix ! Thanks for your work on this library, it is so cool

Thanks! I'll fix this as part as upcoming v8.1 which should be around the corner hopefully this week!


Add RuntimeServices::query_variable_info

This provides information about variable storage space.

Looks good, thanks for taking the time to add this new method!


version compatibility

In a .NET Web API project targeting .NET 8, the latest FeatureManagementProvider is not compatible with the latest OpenFeature SDK (v1.5.1)

Running this from the project folder: dotnet add package OpenFeature.Contrib.Provider.FeatureManagement --version 0.0.1-pr.20240418T192045
gives this message:
warn : NU1603: FeatureFlagsWebApp depends on OpenFeature.Contrib.Provider.FeatureManagement (>= 0.0.1-pr.20240418T192045) but OpenFeature.Contrib.Provider.FeatureManagement 0.0.1-pr.20240418T192045 was not found. An approximate best match of OpenFeature.Contrib.Provider.FeatureManagement 0.0.1-preview was resolved.

That same message is seen in Visual Studio's project dependencies tree under this node:
OpenFeature.Contrib.Provider.FeatureManagement(0.0.1-preview)

The project builds successfully, but gives that same warning message in the build output.

The project runs, but when calling client.GetBooleanDetails, the FlagEvaluationDetails object returned has an ErrorMessage property with this value:
"Method not found: 'Void OpenFeature.Model.ResolutionDetails`1..ctor(System.String, !0, OpenFeature.Constant.ErrorType, System.String, System.String, System.String)'."

The end result is that all flags evaluated return false regardless of the values in appsettings.json

Of note, in this same project, same flags structure in appsettings.json, it all works correctly when using just Microsoft.FeatureManagement without OpenFeature.

Thanks for the reply! I have tried that package as well, with the same result. Since then, I removed both packages, and just added a class for the implementation of the feature provider for MS.FeatureManagement, it's basically identical to the class FeatureManagementProvider from OpenFeature.Contrib.Providers.FeatureManagement. Now with that arrangement, the error message I was seeing in the FlagEvaluationDetails object is gone. But unfortunately, the flags are all still evaluating as false.  Are there any code samples out there that are applicable enough to this use case to be helpful?
Thanks!

Could this be related to the fact that we haven't built this provider since we merged this change?
I saw something similar with flagd because we were using a constructor for ResolutionDetails which only existed in OpenFeature SDK 1.5+, but the dependency required was only 1.4+

I can't tell if this was explicitly expressed above, but it almost certainly due to the fact that the providers haven't been built since 1.5.x.  C# bakes in default values into the callers' assembly, so when default values are changed and added, calling assemblies will continue to use the old values until its rebuilt with the new code.
In this case, a new default value was added, so the callers assembly (in this case, the configcat provider) no longer matches the downstream assembly's method signature, resulting in this error.
Recompiling the bytecode with the new version should solve this issue.

I will be releasing all providers this week to resolve this issue elsewhere.
Thanks @dalinicus for bringing it up.

I will be releasing all providers this week to resolve this issue elsewhere.
Thanks @dalinicus for bringing it up.

I've done this.


Atlassian Setup for local development no longer available

Describe the bug

Due to policy change Atlassian will not support any more the Server services. We need to change our local testing setup to reflect the policy changes, as new developers will not be able to register for new Atlassian Server licenses.
As @Mtze mentioned there is a pre-live instance hosted at the chair, that could be used for our testing purposes.
We need to evaluate this soon, as for the next developers the last server licenses will expire soon.

Developers should use the Gitlab / Jenkins setup and test programming exercises with Bitbucket / Bamboo on the test servers. In case there is a developer who wants to further develop the connectors to Bitbucket / Bamboo, we will find a solution


Support SonarQube 7.6 and up

This plugin does not support the latest versions of SonarQube. With SonarQube 7.9 LTS being released, we should update it.
There is an error during the scan:
org.picocontainer.injectors.AbstractInjector$UnsatisfiableDependenciesException:
io.github.strykermutator.StrykerSensor has unsatisfied dependency 'class org.sonar.api.profiles.RulesProfile' for constructor 'public io.github.strykermutator.StrykerSensor(org.sonar.api.config.Settings,org.sonar.api.batch.fs.FileSystem,org.sonar.api.profiles.RulesProfile)'
from org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@5cbe2654:104<
[Immutable]:org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@3c9168dc:348<
[Immutable]:org.sonar.core.platform.ComponentContainer$ExtendedDefaultPicoContainer@535b1ae6:52<|

This deprecated API call was removed in SonarQube 7.6: https://github.com/SonarSource/sonarqube/commit/33851f1a19fcb539db658f22bd4015a01e6a9c9c

Hi Simon, I have this same error. Has a solution been implemented for this?

In general, the SonarQube fell out of favor at our company. If you want to update it, feel free to do so.

Has anyone made some progress on this?


SCM: Support input box spell checking

For longer commit messages it would be great to have a spell checker there. Ideally, VSCode would provide that out of the box but if the direction is to leave spell checking up to extensions (and there are already some great ones out there, like Spell Right by @bartosz-antosik), there could be an API for that.
Possibly related: Offline spell checker for VSCode #20266
UPDATE: since 2020, Electron supports spell checking natively, see below.

This could be interesting: https://github.com/electron-userland/electron-spellchecker

I would love to give this a go. The electron-spellchecker seems like a potential solution.

This would be a very valuable feature, there is nothing worse than creating a spelling mistake in a commit and discovering many commits later.

@joaomoreno , Working on this and using https://github.com/electron-userland/electron-spellchecker as suggested.

Is that module special? Does it need to run in Electron itself? Note that extensions do not run in Electron, but in an extension host.

@joaomoreno , I got the point that extensions run in extensions host, is there any way to install and use this module there ?
I also think that "electron-spellchecker" derives some information from electron (https://electron-userland.github.io/electron-spellchecker/docs/class/src/context-menu-builder.js~ContextMenuBuilder.html) as described here.
Also is there any external module used in any extension so that I can refer something from that ?
Thanks :)

I also think that "electron-spellchecker" derives some information from electron (https://electron-userland.github.io/electron-spellchecker/docs/class/src/context-menu-builder.js~ContextMenuBuilder.html) as described here.

That's a very good indication that this will not work. I suggest to pick another issue to work on. :+1:
I'll remove the help wanted label since this is not trivial and we're not sure how to proceed here.

@joaomoreno Could you maybe provide some "on changed" callback API call with the content of the edit box which e.g. a spell checking extension (like Spell Right of mine) could service? And another "diagnostics" type to provide suggestions?

That would be awesome, I use Spell Right all the time.

@joaomoreno , There is already a validateInput function that validates the input in many ways( e.g commitMessageWhitespacesOnlyWarning in https://github.com/Microsoft/vscode/blob/master/extensions/git/src/repository.ts#L658 ) .
As @bartosz-antosik suggested, is it possible to use Spell Right in validateInput?
I can look at this approach if you suggest me to go ahead :)
Thanks.

@skprabhanjan I was about to suggest we try that. Git now exposes a rich API. We could open that API to let extensions register additional input validators.

@joaomoreno , I will try with that but I have a small doubt,
Are you suggesting me to use any Git API's that are exposed(which still needs to be researched) or something like Spell Right?

We need to expose new Git extension API: one which lets other extensions register input validators.

@joaomoreno , Okay I will look into how to achieve that.
I will contact you in case of any queries.
Also an example of how to expose a new API would help me go in the rite direction.
Thanks for the help:)

@joaomoreno But it seems half way though: There needs to be some way to correct spelling (underline, right click menu etc.)

Is there any way to open a new editor tab the way Sublime Text does and use that for the commit message?

As a workaround you can open a new file, paste/write the commit message in there and copy it back into the commit afterwords.

Even underlining a spelling error with red would do the trick for 99% of cases. Like in the browser's  field - the browser underlines the errors natively; maybe it can be just enabled in VSCode's text field too?
I see in VSCode's developer tools that this commit message is currently represented as a textarea:
<textarea class="input" autocorrect="off" autocapitalize="off"
spellcheck="false" placeholder="Message (press ⌘Enter to commit)"
title="Message (press ⌘Enter to commit)"
style="background-color: rgb(60, 60, 60); color: rgb(204, 204, 204); height: 26px;"></textarea>

Any chances to make Git Commit Message editing to use the spellchecker?

why very basic feature request spread across years?

Electron 8 includes support for the built-in Chromium spellchecker. Maybe now this feature would be easier?

I would also like to see this in the github.vscode-pull-request-github extension as well. Microsoft just improved the spell checker in Chrome recently as well.

I too would love this feature, can't bare to think how many of my commit messages have terrible spelling in them., please keep me updated and if anyway I can help with this feature

Looking forward to it too.

Most expected feature for me

When will this feature be available?

There's hope. The request is not closed yet (4 years open). Someone must read this.

Most expected feature for me 🤞

Looking forward to it too 🤞

I would ask implementation of https://www.electronjs.org/docs/latest/tutorial/spellchecker be applied to all input boxes including the vscode comment API.
This would be a great quality of life improvement for people that want to center their workflow on vscode, especially for users using the built-in source code tool and writing descriptive commit messages or the GitHub pull request extension (which uses the comment API) and reviews a lot of code. It would also resolve this issue.
Hopefully, this change can be given priority!

Is there any way to open a new editor tab the way Sublime Text does and use that for the commit message?

Actually there's at least one extension ("Commit Message Editor") that does that, meaning opens the commit message in a separate, larger box, CME doesn't seem allow/support any spelling either. at least not wit cSpell. Or at least I haven't figured out how to configure cSpell for CME's buffers.

Looking forward to it 🚀

This feature would really help with accessibility.
I have a disability that makes spelling words hard, and adding spellchecking to the commit box would help accommodate me.

+1
I came here to suggest this and found it already suggested.
Also would like to see this enabled for the "git commit" file language type, markdown type, and text type -- dictionary selectable.

I find the title bit misleading because the major problem is the design flaw that assumed that a commit message needs an input box instead of a full blown editor tab/window. Lack of spellchecking is a side effect, one of many.
That is why I so never do commits from vscode UI, i use command line finely tuned to open commit message in vscode.

I find the title bit misleading because the major problem is the design flaw that assumed that a commit message needs an input box instead of a full blown editor tab/window. Lack of spellchecking is a side effect, one of many.
That is why I so never do commits from vscode UI, i use command line finely tuned to open commit message in vscode.

Nah, the title is exactly what it is. It's gonna be a text field with a lot of text for some folks, and very little text for others. While I completely agree that best practice for commit messages makes that tiny little text box a very, very strange choice, your process isn't my process isn't someone else's and we all deserve a spell checker to have our back.
Me, while I like the idea of how you've set up your workflow, it also wouldn't work well for me in practice. I prefer to stick to a GUI when using a GUI app, and stick to a CLI when using a CLI-app. I already pay enough in mental context switching cost as it is, adding more frequent context switches for me would be a headache. Instead, I just tell VSC to pop open a blank file and tell it that the language is a commit message, copy and paste into that box, no command line. Probably the only thing I'm going to do differently in the long run is bind the first and last parts of this process to two key chords -- one for creating the buffer and designating it as a commit message buffer, and a second for copying it, pasting that in the oddly mail-slot-sized box that was allotted for a commit message, making the commit, and destroying the buffer window. In other words, make it work like we kinda feel it should work, even if it's a bit of a weird work-around of a way.
But for those folks who are going to either compose their commit message right there (a lot like those folks who use -m on the command line, either always or selectively) they deserve spell checking just as much as you or I do.

4.5 years later still waiting.
What' wrong with a regular textarea, why can't it be used instead?

Desperately needed.

+1 do make it happen

In the latest Insiders release (2022-06-27), if you click on the commit button without a commit message, a full editor will open that can be used as an input for the commit message. This has the side effect that any spellchecker extensions will work in the commit message editor as well.
Next milestone, I will also look into the possibility of leveraging the built-in spellchecker or exposing the document behind the SCM Input so that spellchecker extensions can get access to the document, and provide markers for words that are mistyped.

@lszomoru I've just tried in VSCode 1.69 and it's awesome!

(This is the new feature in combination with Spell Right by @bartosz-antosik.)
If you can get the spell checker working in the sidebar, that would be even better but this is already great news! Thanks for your work on this.

I can confirm that spell checking works in the new commit message editor flow with Code Spell Checker too

Glad to hear that things are working as expected. Most of the credit goes to @JohnnyCrazy who contributed the new flow to use the full text editor as the commit message editor. In July I will take a look to see if there is a way to expose the document of the SCM input box to extensions to enable spell checking there as well. I will keep this issue updated with my progress.

If anyone else here wants to see Markdown preview support for the new commit message using an editor feature then please upvote https://github.com/microsoft/vscode/issues/154392. Thanks!

In the latest Insiders release (2022-06-27), if you click on the commit button without a commit message, a full editor will open that can be used as an input for the commit message. This has the side effect that any spellchecker extensions will work in the commit message editor as well.
Next milestone, I will also look into the possibility of leveraging the built-in spellchecker or exposing the document behind the SCM Input so that spellchecker extensions can get access to the document, and provide markers for words that are mistyped.

I tried to click commit button without a commit message but I get a Bad status code 500 error, is there a setting which I need to enable first?

@urenajose, you are hitting an issue that is currently being tracked as https://github.com/microsoft/vscode/issues/154449

@lszomoru, I tried to click commit button without a commit message but I get a Bad status code 500 error, is there a setting which I need to enable first?

Probably you didn't set user name and password for git.
You can check on output of vscode (when you open terminal, check the output tab (different tab))
Then you will see the error msg.

After talking to the team today, as it turns out, extensions already have access to the text document that is associated with the SCM input field which enables extension authors to implement spell check for the SCM input field. The text document is in the workspace.textDocuments array, and the workspace.onDidChangeTextDocument event fires when the text document changes. The text document has the vscode scheme and scminput languageId.
Today I have submitted a pull request to the Spell Right extension, and next I will be looking at the Code Spell Checker extension and will probably reach out to the extension author either with a pull request or with the exact steps that they need to make to their extension.
As soon as diagnostic information is emitted to the text document that is associated with the SCM input field, there are some "papercuts" that I need to address in the "Problems View": 1) the file name associated with the problem should have the repository name, 2) clicking on a problem should focus the SCM input field.

I have also submitted a pull request to the Code Spell Checker extension. The changes to that extension as minimal since all it has to do is remove vscode from the list of blocked schemes. As soon as that happens, spell checking for the SCM input can be enabled by tweaking the settings of the extension.

The author of the Code Spell Checker extension published an update (v2.3.1) that contains my proposed changes so you can enable spell checking in the commit input box by adding vscode to the allowed schemas, and scminput to the enabled file types:
  "cSpell.allowedSchemas": ["file", "gist", "sftp", "untitled", "vscode-notebook-cell", "vscode-userdata", "vscode"],
  "cSpell.enableFiletypes": ["scminput"],

@lszomoru,
It is better to use:

  "cSpell.allowedSchemas": ["file", "gist", "sftp", "untitled", "vscode-notebook-cell", "vscode-userdata", "vscode"],
  "cSpell.enableFiletypes": ["scminput"],

Because of limitations in the way VS Code merges settings, lists are overwritten instead of merged. So, setting enabledLanguageIds will disable all other file types.

Today's Insiders release (2022-070-26) contains a change so that we adopt a dedicated scheme, vscode-scm for the text document associated with the commit input. This enables extension authors to easily identify such documents. In case you are using the Code Spell Checker extension please update your user settings to:
  "cSpell.allowedSchemas": ["file", "gist", "sftp", "untitled", "vscode-notebook-cell", "vscode-userdata", "vscode-scm"],
  "cSpell.enableFiletypes": ["scminput"],

@Jason3S, with this change, you can add the vscode scheme back to the blocked list and add the vscode-scm scheme to the default list of schemes that are being processed. I have also pushed a commit so that problem markers for documents using the vscode-scm scheme will not appear in the problems view.

@lszomoru, I'll update the extension.


Is it possible to implement a feature for AIChat to reference the output or error message from the previous command

For example:   aichat  --lastOut   1   'What's the issue here'

We will not support this feature.
This feature requires tmux (or something similar) to access the terminal buffer, which contains previous commands and error messages.
Maybe you can write a script that invokes tmux and aichat to achieve the same functionality.

We will not support this feature.
This feature requires tmux (or something similar) to access the terminal buffer, which contains previous commands and error messages.
Maybe you can write a script that invokes tmux and aichat to achieve the same functionality.

I changed my approach by opening two windows in tmux. Window ID 0 is used for entering commands, while window ID 1 runs aichat. I then set up a hotkey set-keys > tmux capture-pane -t 0 -p -E 20 to pass the content from window ID 0 to ID 1. However, there's still an inconvenience: in the Chat-REPL, I can't execute capture-pane. I wish I could run bash commands directly within the REPL.


R beginners update ivy

Add material and data for part 2 of the workshop

The figures are screenshots. They are needed to be able to knit the Rmd into a pdf.


Route naming and Groups

I'm experiencing an issue with routing where the options in the route group (e.g. 'namespace') are being overwritten. For example, the following I would expect the URI admin/user/create to work:
$routes->group('admin', ['namespace' => 'Admin\Controllers'], function($routes)
{
	$routes->get('user/create', 'UserController::create', ['as' => 'user_create']);
}

However, because I added the ['as' => 'user_create'], it overwrites the default options and loses the 'namespace' option. I'd like to propose replacing the lines around 1120 in the RouteCollection::create method (https://github.com/bcit-ci/CodeIgniter4/blob/develop/system/Router/RouteCollection.php#L1120):
if (is_null($options))
{
	$options = $this->currentOptions;
}

with something like the following so that the current group options get merged with the passed options:
$options = array_merge((array)$this->currentOptions, (array)$options);

That's a good call. Care to submit a PR for that? :)

Yep... wanted to run by the solution first to make sure I wasn't missing something or if there was a preferred way of implementation. I'll send it in shortly.

Appreciate it. And that sounds good. That's what it was intended to do, but I obviously took a misstep :)


A query for usage over low-altitude dataset

Hey. I loved your work and idea.
I have a UAV dataset from the agricultural domain (~1500 images) captured at low altitude (UAV), focusing on crops and weeds. I am interested in applying the SiamSeg model to this dataset. Do I need to make any specific adjustments or consider any particular aspects when adapting the model to this type of imagery? Specifically, are there any challenges with the altitude-based perspective or image characteristics that I should be aware of when using your model for this task?

Hi @stardust-96:
In most cases, it is effective to apply SiamSeg directly to private datasets. It is recommended that you try training on a private dataset first and observe the experimental results.
Sincerely,
woldier


Queue emails help

Please help setting up queue, i need to add rmail job to queue on main database. UsesSystemConnection does not work, jobs are going to tenant db.
How to force it so they are saved in default database.
Thank you!

Have you tried the tenant aware job trait?

Hi, thank you for your reply, yes I have tried. I am trying to force mail class to send queue to system database.
MeetingController has 'tenancy.enforce' middleware on route level:
<?php

namespace App\Http\Middleware;

use Closure;
use Illuminate\Support\Facades\Config;

class EnforceTenancy
{
    /**
     * Handle an incoming request.
     *
     * @param  \Illuminate\Http\Request  $request
     * @param  \Closure  $next
     * @return mixed
     */
    public function handle($request, Closure $next)
    {
        Config::set('database.default', 'tenant');
        return $next($request);
    }
}

Class is called from MeetingController like this:
$invitation = new MeetingInvitation('test');
Mail::queue($invitation);

MeetingInvitation:
<?php

namespace App\Mail;

use Illuminate\Bus\Queueable;
use Illuminate\Mail\Mailable;
#use Illuminate\Queue\SerializesModels;
use Hyn\Tenancy\Queue\TenantAwareJob;
use Illuminate\Queue\InteractsWithQueue;
use Illuminate\Contracts\Queue\ShouldQueue;
use Hyn\Tenancy\Traits\UsesSystemConnection;
//todo https://laravel-tenancy.com/docs/hyn/5.x/queues
class MeetingInvitation extends Mailable
{
    #use Queueable, SerializesModels,UsesSystemConnection;
    use UsesSystemConnection,InteractsWithQueue, Queueable, TenantAwareJob;

    /**
     * Create a new message instance.
     *
     * @return void
     */
    public function __construct($test)
    {

    }

    /**
     * Build the message.
     *
     * @return $this
     */
    public function build()
    {
        return $this->from('admin<EMAIL_ADDRESS>        ->view('emails.meetinginvitation');
    }
}

Basically I want emails to be queued on default (non tenant) database (using one artisan listener), so if there is a way to switch connection so queue goes to 'jobs' table on main database?

Sorry, I just realized that by defining 'connection' parameter in config/queue.php solves my problem:
'connections' => [

        'database' => [
            'connection' => 'system',
            'driver' => 'database',
            'table' => 'jobs',
            'queue' => 'default',
            'retry_after' => 90,
        ],
],

Hope someone finds this useful.

Small update: Everything is working perfectly with TenantAwareJob, I have passed in Full models, they are resolved to correct database.


Add mondoo as an adopter

What type of PR is this?
/kind documentation
Does this PR introduce a user-facing change?
NONE

/close
Thanks!
I opened #1324


New version: MilosParipovic.OneCommander version 3.65.2

Pull request has been created with komac v2.0.0 :rocket:

Resolve: #135193

Microsoft Reviewers: Open in CodeFlow

For moderators
This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping @Exorcism0666, I'll get a notification.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

@wingetbot run

/AzurePipelines run

Hi @Exorcism0666,

This PR's version number 3.65.2 has 3 parameters (sets of numbers between dots - major, minor, etc), which is less than the current manifest's version <IP_ADDRESS>, which has 4 parameters.

Is this intentional?
(Automated response - build 629)

Hi @Exorcism0666,
This manifest adds Apps and Features entries that aren't present in previous PR versions. Should these entries also be added to the previous versions?
(Automated response - build 629.)


Help not always working for dotnet solution

Issue Type: Bug
The system info below (captured by Report Issue) doesn't make it clear (to me) that this is macOS Catalina 10.15.6.
Steps to Reproduce:

Use dotnet to create projects.
Open in Code
Sometimes syntax coloring and help are working and sometimes not.

In this repo: https://github.com/michaelgwelch/garbage
The Console project has help, the ClassLib doesn't. By which I mean, if I hover over a method in the Console app I get pop up help. If I hover over the method in ClassLib I just get type information.
ClassLib

Console:

Does this issue occur when all extensions are disabled?: Yes
I uninstalled every single extension (except OmniSharp) and restarted VS Code

VS Code version: Code 1.47.2 (17299e413d5590b14ab0340ea477cdd86ff13daf, 2020-07-15T18:18:50.054Z)
OS version: Darwin x64 19.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8210Y CPU @ 1.60GHz (4 x 1600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
5, 12, 9

Memory (System)
16.00GB (1.80GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (1)

Extension
Author (truncated)
Version

csharp
ms-
1.22.1

I think I discovered the issue. I switch to Visual Studio for Mac and noticed one of my class libs still wasn't showing help. So I added a new class lib to the solution.
I then look at the differences in their dependencies in the Project Explorer. What I saw was different. One listed a Framework and the other listed an SDK. I opened up the project files and saw they were identical expect one was netstandard2.0 and the other was netstandard2.1. The fix was to upgrade the project that didn't have help to net standard2.1. Then help started to work.
Since it impacts both IDEs I guess this may be a dotnet core issue?

Yes of course this is an extension. I don't know what I was thinking. I just associate VS Code and dotnet so much I didn't think of the omnisharp extension as "counting" as an extension. Thanks

Just in case anyone stumbles across this defect in this repo, the problem doesn't seem to be a VS Code issue, nor is it an extension issue. It appears it may be a dotnet runtime issue: https://github.com/dotnet/runtime/issues/39927


My first Pull Request

This Pull Request resolves Issue #1
Description:
In this Pull Request we have done the following additions/edits for the code:
Note: Delete all the text including this!

Make sure you replace #1 with the particular Issue that you are referencing with!
Make sure you describe the Issue properly and ask as many people as possible to review your Pull Request so that it can be merged as soon as possible!

Updates?

Any updates here? Or should we close the Pull Request?


Add more details to Open Issues metric definition

A detailed description and one extra use case were added.
Work done together with @alpgarcia, @jgbarah and @dicortazar

We moved the workgroup's efforts over to the wg-gmd branch of the metrics repository. Please resubmit this pull request there.
Thanks!
Sean

Oooops, moving this to the other repo, thanks @sgoggins

Reopening, since we're still working in this repository (see message to the mailing list).

There's a conflict we will resolve and then merge. @klumb : can you look into this.

This just a naming convention issue. File was renamed to issues-open.md

Once we're done with the comments in revisions, I can change the name of the file, which seems to be the reason for the conflict, when merging.

@sgoggins are you happy with my comments, and we can merge this pull request, or you still feel I need to do some change before merging?


Convert the Comparison Statistics to be part of the Metrics system

Issue Description
What did you expect to see happen?
The Comparison Statistics should be a metric that can be used with any metric processing.
What did you see instead?
Comparison Statistics is a monolith.
Do you have a suggested fix for the development team?

Convert Comparison Statistics to use Metrics
Subparts:
a. Make Data -> CDF more independent
b. Make Metrics have a way to specify that they take CDFs or Data
c. Make Data -> CDF be able to handle weights
d. Make Comparison Statistics a metric

Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or improvement?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

Issue Review by @joshua-cogliati-inl on 2017-Sept-6

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[x] 1. If the issue is a defect, is the defect fixed? no a defect_
[x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.) N/A
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?  This PR is a new feature, and will not impact the users
[x] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)? No
[x] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided? a merge request is provided

Checklists Passed. Issue Closure reviewed by Congjian Wang @wangcj05 on Oct. 4, 2017.

This issue can be closed by PR #354


Add an RPC mechanism to Lightning App

🚀 Feature

As a user, I would like to build an app that can act as a platform. Once the app is running in the cloud, I would like my users to be able to connect to the app and execute commands (RPC) calls to launch dynamically jobs.
Ideally, I would like to be able to execute some python code on the user client side, so more complex RPC calls can be implemented.
Example
Imagine you want to build a simplified application version of Grid.ai.
Using Grid, users can log in with grid login.
Once logged in, a user can execute their PyTorch Lightning scripts in the cloud with the following command:
grid run train.py --trainer.max_epochs=uniform(10, 100)

In order to create the same functionality with an app, we need a RPC API. Let's assume it exposes a sweep command.
lightning run app simplified_grid_app.py

Once running, users of the app could run the following command.
lightning connect app_id/url/app_name
lightning sweep script.py --trainer.max_epochs=uniform(10, 100) --compute="fast-gpu"

Here are the steps behind the sweep command:

[user machine] Enter the sweep command
[user machine] Upload the local source code to s3, send a request to the App RestAPI with all information to know where the code is, etc...
[Rest API] Receives the request and passes the payload to the flow.
[Flow] Execute the associated method with the payload.

Here is an example of the Sweep Method:
def sweep(self, request):
    self.flows.append(
        HPOCodeRunner(**request)
    )

Motivation

Pitch

Alternatives

Additional context

If you enjoy Lightning, check out our other projects! ⚡

Metrics: Machine learning metrics for distributed, scalable PyTorch applications.

Lite: enables pure PyTorch users to scale their existing code on any kind of device while retaining full control over their own loops and optimization logic.

Flash: The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, fine-tuning, and solving problems with deep learning.

Bolts: Pretrained SOTA Deep Learning models, callbacks, and more for research and production with PyTorch Lightning and PyTorch.

Lightning Transformers: Flexible interface for high-performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.

cc @borda @tchaton @justusschock @awaelchli

Is the idea here to add the sweep method (and others)? Or to add possibilities to call virtually any script?
I'd suggest to do this and then use the entrypoints from #13602 to optionally do stuff like sweeps.
I don't think sweeps would be something that need to be available on every app

I like this! One thing that could make UI development much cleaner IMO is if we also had a mechanism to trigger these commands from e.g. the react UI by sending an HTTP request or similar. That would avoid some tricks we currently use like setting a flag to trigger an action then unsetting the flag once the action starts (which works fine but gets cluttered when you are triggering several things in this way).

Hey @justusschock @ethanwharris.
Actually, the API in https://github.com/Lightning-AI/lightning/pull/13602 is too limited as there isn't any code execution on the client side.
I chatted with @carmocca to brainstorm on another API and we thought about this one.
from lightning import LightningFlow
from pydantic import BaseModel
from typing import List

class SweepConfig(BaseModel):
    github_repo: str
    script_path: str
    requirements: List[str]

class HPOFlow(LightningFlow):

    def sweep(self, sweep: SweepConfig):
        ...

    def configure_commands(self):
        return [
            {
                "name": "sweep",
                "server": self.sweep,
                "client": "sweep.py"    # optional
            },
            ...
        ]

When running `lightning command sweep, this would download locally the self-contained sweep.py, extract the sweep method and execute it over the user arguments
In this use case, this would enable to upload of the source code to s3 and then launch a sweep with the associated information.
What are your thoughts ?

After chatting with @justusschock and @lantiga.
Here is the proposed API.
The commands needs to be isolated from the rest of the codebase, so we can easily package them and enable the users to install them.
Here is a Sweep Command
# commands/sweep.py

from lightning.app.commands import ClientCommand

class SweepClientCommand(ClientCommand):

    def run(script_path, *args, **kwargs):
        remote_url = upload_local_dir_to_s3(script_path)
        response = self.invoke_handler(SweepConfig(remote_url, *args, **kwargs))  # This triggers the method on the CI and waits the response.

Here is a Predict Command
# commands/predict.py

class PredictClientCommand(ClientCommand):

    def run(image_folder):
        for file in os.listdir(image_folder):
            endpoint_url = self.invoke_handler()
            predictions = requests.post(endpoint_url, load_data(file))

from commands import PredictClientCommand, SweepClientCommand

class HPOFlow(LightningFlow):

    def run(self):
        for flow in self.flows:
            flow.run()

    def command_without_client(self, name: str):
        ...

    def sweep(self, sweep: SweepConfig):
        self.flows.append(HPOCodeRunner(sweep))

    def fetch_endpoint(self):
        return self.current_server.url

    def configure_commands(self):
        return [
            {"command_without_client": self.command_without_client},
            {"sweep": SweepClientCommand(self.sweep)},
            {"predict_from_folders": PredictClientCommand(self.fetch_endpoint)}
        ]

Looks good. One extra thing we aligned about is that we may need to pass more handlers to the command (in case one of the handlers need to be called conditionally or sequentially):
    def configure_commands(self):
        return [
            {"sweep": SweepClientCommand(sweep=self.sweep, single_run=self.single_run)},
        ]

In that case the idea is that invoke_handler needs to take an extra argument with the name of the handler (”sweep” or ”single_run” in the example above)


Problem with Grouped TableView

Thanks for this great library. Please add the following code to the SquareCashStyleViewController.m in the demo project to replicate the issue:

(NSInteger)numberOfSectionsInTableView:(UITableView *)tableView
{
return 2;
}

(NSString *)tableView:(UITableView *)tableView titleForHeaderInSection:(NSInteger)section
{
return @"This view will be out of place";
}

The group's header view does not move up with the custom bar when scrolling up.

Thanks for pointing this out. It definitely has something to do with the contentInset of the table view. I'll look into this more soon.

I noticed this too, tried to do some workarounds with my own behavior definer but didn't get perfect movement.

any updates for this? I synced to latest code but still not got fixed yet.

For people following this, I'm still looking into this. There's a pull request open right now that seems to partially fix it. It works for the Facebook behavior definer but not the square cash one. I'll get around to looking at that hopefully in the near future, but until then, anyone else is welcome to have a look.


Add ddev-get as a topic

Thanks for creating the addon!
Would you mind add ddev-get as a topic. This will allow others to discover this addon via ddev get --list --all
Steps

Done  👍

Confirmed.
$ ddev get --list --all
...
│ iljapolanskis/ddev-buggregator                    │ Buggregator service for DDEV (similar to Ray, but  │

Thanks you.


TOO MANY STEPS

And no option for skipping.
Find a way to simplify while still ensuring chain of thought, or just build separate speedy one.

Could add warning of length as user suggested response at beginning.


Request: Format change for doc test cli output

When running cargo test on a project with some doc tests I see the following output:
$ cargo test
    Finished dev [unoptimized + debuginfo] target(s) in 0.06s
     Running target/debug/deps/tq_parser-9edae091aa940c1c

running 1 test
test tokenizer::tests::string_literal::simple ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

   Doc-tests tq-parser

running 3 tests
test src/tokenizer.rs - tokenizer::Tokenizer<'text>::new (line 158) ... ok
test src/tokenizer.rs - tokenizer::Tokenizer (line 36) ... ok
test src/tokenizer.rs - tokenizer::Token (line 122) ... ok

test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

This ticket is focusing on this portion:
   Doc-tests tq-parser

running 3 tests
test src/tokenizer.rs - tokenizer::Tokenizer<'text>::new (line 158) ... ok
test src/tokenizer.rs - tokenizer::Tokenizer (line 36) ... ok
test src/tokenizer.rs - tokenizer::Token (line 122) ... ok

I believe this output could be more useful, perhaps at the cost of being 'pretty', if the line numbers were joined to the source file path with a : to produce a clickable (in some environments) path.
For example, if the output were the following
   Doc-tests tq-parser

running 3 tests
test src/tokenizer.rs:158 - tokenizer::Tokenizer<'text>::new ... ok
test src/tokenizer.rs:36 - tokenizer::Tokenizer ... ok
test src/tokenizer.rs:122 - tokenizer::Token ... ok

I could cmd-click on src/tokenizer.rs:158 and be taken, in my editor, directly to the doc test instead of having to open the file then navigate to the line.
This is more useful in the case of errors.
If I change the tokenizer::Tokenizer<'text>::new test to fail I get
test src/tokenizer.rs - tokenizer::Tokenizer<'text>::new (line 158) ... FAILED

Which could be
test src/tokenizer.rs:158 - tokenizer::Tokenizer<'text>::new ... FAILED

Yea, that looks nicer to me!  However, this output is generated by rustdoc (and in turn by libtest I believe), which are tracked at https://github.com/rust-lang/rust/issues.  Would you mind moving this issue over there?

Agh, so many interconnected parts it is difficult to tell where to file tickets!
Yep, I'll move it.


InvalidPathException thrown when parsing typeAliases elements using package as sub-tag

MyBatis version
3.5.4
Database vendor and version
MySQL v8.0.20
JDK version and OS
v9.0.1 & MacOS
Test case or example project
https://github.com/akamonk/mybatis-demo
Steps to reproduce
Use JDK9 as the running environment to build a named module. the module-info.java like as follows:

open module mybatis.demo {
    requires org.mybatis;
    requires java.sql;
}

When configuring, use package as a sub-tag of typeAliases tag.

<typeAliases>
      <package name="com.xxx.xxx.entity" />
</typeAliases>

then, build the SqlSessionFactory. When parsing the typeAliases element, an InvalidPathException was thrown.
My attempt:
When I removed module-info.java from the module, I got the expected result.
Expected result
Successfully constructed SqlSessionFactory
Actual result
InvalidPathException thrown

Thank you so much for the report and the repro, @akamonk !
I could easily reproduce the exception and plan to fix it as soon as possible.

@akamonk ,
It should be fixed in the latest 3.5.6-SNAPSHOT.
Please let me know if you experience any further issue.
Thank you again for your contribution!

Hi harawata.
When will latest 3.5.6 be released?

@TakeshiYonezawa ,
3.5.6 has just been released. 🎊


Optimize fixture view and project wide imports

Changes

FixtureView is optimized.
Imports optimization project-wide.

Upcoming changes

LazyColumn slider animations incoming 😎.
FixtureDetailsView incoming.

Screenshots

Theme
Screenshot

Light

Dark

Updated README.md to address the issue #7 .

Wow, it's really coming along now!  I'll hopefully grab some time soon and make similar changes to iOS SwiftUI client.

Sounds good! I'll try to bring the compose-desktop up-to-date as well 👍🏻.


chore(README): fix broken Github Actions Workflow Status icon

Commit 66771bd80d1fad1fe46cf79a4bd578dd90756f89 renames the file v2-tests.yml to tests.yml
in PR #5833 which broke the github actions test icon and link to the workflow.

Signed-off-by: Hemant Sachdeva<EMAIL_ADDRESS>
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
I changed the icon which was not showing up correctly in README. After I made changes icon and link to the workflow works fine now. Commit and PR number is mentioned above who broke the icon.

Thanks for noticing :P

Your welcome sir :)


fix: 'generate' vs 'interactive' prompt fixes

Description

I had to make some adjustments to the prompt logic for it to work correctly in 'generate' mode

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


[ort] Fixes reported OrtEngine version

Change-Id: Ibd25f34dd1057eb451186db97957f0b176870119
Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

Codecov Report

Merging #1950 (88a1208) into master (bb5073f) will decrease coverage by 2.15%.
The diff coverage is 67.25%.

@@             Coverage Diff              @@
##             master    #1950      +/-   ##
============================================
- Coverage     72.08%   69.93%   -2.16%
- Complexity     5126     5708     +582
============================================
  Files           473      544      +71
  Lines         21970    25193    +3223
  Branches       2351     2734     +383
============================================
+ Hits          15838    17619    +1781
- Misses         4925     6234    +1309
- Partials       1207     1340     +133

Impacted Files
Coverage Δ

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...rc/main/java/ai/djl/modality/cv/MultiBoxPrior.java
76.00% <ø> (ø)

...rc/main/java/ai/djl/modality/cv/output/Joints.java
71.42% <ø> (ø)

.../main/java/ai/djl/modality/cv/output/Landmark.java
100.00% <ø> (ø)

...main/java/ai/djl/modality/cv/output/Rectangle.java
72.41% <0.00%> (ø)

...i/djl/modality/cv/translator/BigGANTranslator.java
21.42% <0.00%> (-5.24%)
:arrow_down:

...odality/cv/translator/BigGANTranslatorFactory.java
33.33% <0.00%> (+8.33%)
:arrow_up:

...nslator/InstanceSegmentationTranslatorFactory.java
14.28% <0.00%> (-3.90%)
:arrow_down:

.../cv/translator/SemanticSegmentationTranslator.java
0.00% <0.00%> (ø)

.../cv/translator/StyleTransferTranslatorFactory.java
40.00% <ø> (ø)

... and 446 more

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


Use a machine-readable format for logs

Zap, as a structured logger, is a great candidate for example: https://github.com/uber-go/zap
A structured log will make things more portable too.

Looks like go as of recent versions have native structured log support.
We can use it instead of introducing another library.

ref: https://go.dev/blog/slog


[BUG] Custom Radio Station Names inconsistently persisting across updates

What version of Music Assistant has the issue?
2.0.0b103
What version of the Home Assistant Integration have you got installed?
No response
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
Inconsistently when updating Music Assistant custom names I have set for radio stations will be wiped and replaced with seemingly generic names. This causes automations which are relying on my custon names to break as well
How to reproduce
Add a radio station with a custom name. Update Music Assistant. Name should be replaced with something generic
Music Providers
Radio
Player Providers
N/A
Relevant log output
No response
Additional information
No response
What version of Home Assistant Core are your running
2024.2.2
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

Ok thanks. We will have a look at this in due course.

Also you used the word “inconsistently” in your title. Are you saying that some stations persist and some don’t or are you saying that sometimes after a restart the name resets and sometimes it doesn’t?

Sorry for being unclear. I am saying sometimes when I update music assistant it resets. I have not noticed it resetting purely from a restart/reboot.
In case it helps at all, I basically have an automation that functions like a music alarm clock. It goes off at a set time every morning, says an announcement, and then starts to play a radio station. Example of the service call below
service: mass.play_media
data:
  media_type: radio
  media_id: STATION NAME HERE
target:
  device_id: DEVICE ID HERE

Ive only noticed this issue because I use a specific name for this one radio station and sometimes after I upgrade music assistant it stops working and nearly every time that has happened its due to the name being reset. I am not 100% sure if its the integration or the addon that is breaking it, but my guess is its the addon updates that break it but cant quite confirm.

OK this will get looked at in due course

b120 includes a fix so this should no longer happen (from now on) - so if you add a manual url with name and/or image, that info will stay in the db and not get overwritten by the streamscanner.

Awesome, thanks so much for fixing. I am closing this, but will reopen if it reoccurs.


SMALL_SPIDER (tr2 enemy) has pathfinding issues

SMALL_SPIDER does not aggressively path towards and attack Lara unless she is extremely close. Once she gets more than a few tiles away, it loses interest and will instead run around aimlessly in circles. Expected behavior is that, like almost all enemies, it will seek Lara out no matter where she is, as long as it can potentially reach her on her current elevation.
https://user-images.githubusercontent.com/47687538/208378269-deaddbc6-4f1e-4c8c-9cc1-959e54af1082.mp4

For comparison, this is the same enemy's behavior in 1.0.2:
https://user-images.githubusercontent.com/47687538/208384161-48230494-03ab-4760-a151-c71d214043ed.mp4

Fixed in 93d8e309c9d862232dfe8cc22d5e6092dfdc94a5


Remove /invitations/send-invite URL

As pointed out in the Blackberry security assessment, regular users can invite other users by manually typing in the URL because we added all of the URLs in the invitations plugin.

Application uses external library, called django-invitations, to serve invitation feature for administrator and superuser roles. The application includes all views from external library. Two views from django-invitations require only logged-in user to sendinvitations.

This PR only includes the accept invite URL and removes the "create-invite" URL.
Screenshot
This is the screen we were able to see:

:+1:


DOC: Add example code snippets to jax.scipy.linalg.expm and jax.scipy.linalg.polar docs

Hi @jakevdp, Could you please have a look at this. All changes are made as suggested and squashed into single commit.


suggest event typing

suggest emit<> & on<> via regex \b(emit|on)(\(|<)((?!(Event>)).)*$
bad :

on('plop-ok')
on<PlopData>('plop-ok')
emit('plop-ok')

good :

on<PlopOkEvent>('plop-ok')

ideally suggest the name or fix directly, or create an eslint module, could be nice

I don't use events as much now ^^'


Bug: REL TABLE GROUP: Error: Parser exception: Invalid input <, FROM>: expected rule kU_CreateRelTableGroup (caused by whitespace)

Kùzu version
v0.4.2
What happened?
CREATE REL TABLE GROUP X (...) causes

Error: Parser exception: Invalid input <,                             FROM>: expected rule kU_CreateRelTableGroup (line: 1, offset: 257)

, despite being syntactically correct. It turns out to be a problem with whitespaces surrounding terms defined within parentheses.
Are there known steps to reproduce?
CREATE NODE TABLE V1 (id UUID, PRIMARY KEY (id));
CREATE NODE TABLE V2 (id UUID, PRIMARY KEY (id));

// auto-generated statement
// This caused error
CREATE REL TABLE GROUP has (
                            FROM V1
                            TO V1
                            ,
                            FROM V1
                            TO V2
                            ,
                            FROM V2
                            TO V2
                            , ONE_MANY);

// corresponds to (and also causes error)
CREATE REL TABLE GROUP has (  FROM V1  TO V1  ,  FROM V1  TO V2  ,  FROM V2  TO V2  , ONE_MANY);

// removing trailing whitespace after `TO <table>` works
CREATE REL TABLE GROUP has (  FROM V1  TO V1,  FROM V1  TO V2,  FROM V2  TO V2, ONE_MANY);

This should be fixed in #3549


Bug: Error Store Does Not Automatically Update

[x] Before posting an issue, read the FAQ and search the previous issues.

Description
The error store does not automatically update when an error changes.
A form can only be submitted if all fields are error-free. However, in this library, the error state does not update to reflect new errors if we trigger a new one immediately.
Only happens when use:enhance is turned on
Steps to Reproduce

Submit the form with an invalid field to trigger an error.
Resolve the initial error.
Trigger, at the same time a new error on the form.

Expected Behavior
The error store should update automatically to reflect the new errors.
Actual Behavior
The new error is not reflected in the UI, leading to inconsistencies.
This produces some weird side effects, like not reacting to errors when submitting the form for a second time
Workaround
A hacky workaround involves manually updating the error store using the onUpdate option:
const { form, errors, message, enhance } = superForm(data.form, {
	applyAction: true,
	// Hacky way to FIX this
	onUpdate: ({ form }) => {
		$errors = form.errors;
	},
});

If applicable, a MRE
Use this template project to create a minimal reproducible example that you can link to here:  link to open in a new tab)

I've got other reports for this, so will take a look at it now

Something breaks in the latest version of SvelteKit. If you use "@sveltejs/kit": "2.11.1" it works again.

Seems to be some problem with invalidateAll.

This line doesn't trigger the page update anymore, which in turn prevents the update code to run.

Possibly related to https://svelte.dev/docs/kit/$app-state

Reported on SvelteKit here: https://github.com/sveltejs/kit/issues/13200

Thanks for the quick response man!

Thanks for logging this! Could forms not being reset also be related to this? I was going to log an issue but basically form data is not being reset when I call form.reset() (using <AlertDialog.Root bind:open onOpenChange={() => form.reset()}>).


[Enhancement]: Chat Model per Tab

Before Requesting

[X] I have searched the existing issues, and there is no existing issue for my feature request

What feature do you want?
I would like to specify the chat model to use when creating a new tab in the chat panel. This would allow me to have specific tabs for specific types of requests that are tuned for a given model, e.g., translation, writing documentation, coding, etc. and maintain the context for each type of interaction separately.

You can already do that by right-clicking the title or each tab to open a context menu. You can change the chat model, temperature and scopes for each tab.
When you use multiple chat tabs, you may find a bug that you can only scroll up in the first chat tab. It will be fixed in the coming release this weekend.

Thank you!


No "Assume Role ARN" in Timestream datasource config

The docs say "The Timestream plugin authentication system matches the standard Cloudwatch plugin system.". Looking at the Cloudwatch documentation, I see "The Assume Role ARN field allows you to specify which IAM role to assume, if any. " There is no "Assume Role ARN" field in the Timestream datasource config (see screenshot). Instead, all I have are "Authentication Provider", "Endpoint", and "Default Region". How do I assume a different Role?

What version are you running?  This is what mine looks like:

Grafana v7.4.1 (07649d1313)

@kpeters-cbsi I think he meant Timestream plugin version. The latest is 1.3.3 https://github.com/grafana/timestream-datasource/releases/tag/v1.3.3

Oops. :) Timestream plugin 1.3.0. I take it I should upgrade?

Updating to 1.3.3 fixed it.


pull request for e2e test at 12/14/2016 14:56:09

:white_check_mark: Validation status: passed
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.


System crashes

version <IP_ADDRESS>
The RPi repeatvely chrash when I have the integration activated
After a restart it works fine for a while but- suddenly the system freez I se that the load get up badly ( very high)
After a couple of hours it start again

Looks like the problems I have, see #8

double


ControlPlayerJumpSystem shouldn't do actual jumping logic

ControlPlayerJumpSystem shouldn't change player gravity, instead another system
(or maybe the HandleMovablesSystem) should update the entity's gravity,
depending on Velocity, MoveAction (Jump, KillJump), standing on ground.
That way, every Jumper entity can actually have different gravities, not only the player.
Also, then we can use the MoveAction(Jump) action and it would change gravity properly.
Originally posted by @Noah2610 in https://github.com/Noah2610/deathfloor/issues/79#issuecomment-693435802

The HandleMovablesSystem should handle the jumping logic (change gravity, set jumper fields, etc.).
The ControlPlayerJumpSystem should only trigger a jump when the user presses the jump button.


Get keys from json object

Is it possible to get all keys from json object (like on picture)?

You may want to have a look at the items() function.

@Radmir2015 Can we close this issue or do you need further assistance?

Yes, of course. Thanks.


create card-component for visuals

The big cards used in the profile,, edit-profil, Register + login (and anywhere else) should be positioned the same and of the same size and color

why is it assigned to me?


jobs not submitted

I'm noticing that jobs aren't queueing including the monitoring process. Cluster usage (slurm) is high at the moment. Is there a built in hold on submit based on queue size?
 cat SLURM_controller78826543-733a-4213-b061-214bd39c6761

#!/bin/sh
#SBATCH -p normal
#SBATCH -J bcbio-c
#SBATCH -o bcbio-ipcontroller.out.%j
#SBATCH -e bcbio-ipcontroller.err.%j
#SBATCH -t 7-00:00:00
#SBATCH --cpus-per-task=1
#SBATCH -A euan
#SBATCH --mem=200

/share/PI/euan/apps/bcbio/anaconda/bin/python -E -c 'import resource; cur_proc, max_proc = resource.getrlimit(resource.RLIMIT_NPROC); target_proc = min(max_proc, 10240) if max_proc > 0 else 10240; resource.setrlimit(resource.RLIMIT_NPROC, (max(cur_proc, target_proc), max_proc)); cur_hdls, max_hdls = resource.getrlimit(resource.RLIMIT_NOFILE); target_hdls = min(max_hdls, 10240) if max_hdls > 0 else 10240; resource.setrlimit(resource.RLIMIT_NOFILE, (max(cur_hdls, target_hdls), max_hdls)); from cluster_helper.cluster import VMFixIPControllerApp; VMFixIPControllerApp.launch_instance()' --ip=* --log-to-file --profile-dir="/scratch/PI/euan/projects/athletes/bcbio/log/ipython" --cluster-id="ef247c8f-8ee6-425d-a359-8597a5381a0d" --nodb --hwm=1 --scheme=leastload --HeartMonitor.max_heartmonitor_misses=120 --HeartMonitor.period=60000

Hi Daryl,
Sorry for the issue; so that bcbio-ipcontroller job never gets queued, or does it never start? If it is not queued, the job might be being rejected by the scheduler for some reason. If you just submit that job script with sbatch < SLURM_controller78826543-733a-4213-b061-214bd39c6761, does SLURM give you an error?

Nice! It looks like the time request was too high. Should that have been
logged somewhere that I missed?
On Mon, Jan 26, 2015 at 8:49 PM, Rory Kirchner<EMAIL_ADDRESS>wrote:

Hi Daryl,
Sorry for the issue; so that bcbio-ipcontroller job never gets queued, or
does it never start? If it is not queued, the job might be being rejected
by the scheduler for some reason. If you just submit that job script with
sbatch < SLURM_controller78826543-733a-4213-b061-214bd39c6761, does SLURM
give you an error?
—
Reply to this email directly or view it on GitHub
https://github.com/chapmanb/bcbio-nextgen/issues/735#issuecomment-71589449
.

Hi Daryl,
Nope, you didn't miss anything-- if the jobs never get queued at all no log files get created, sorry about that, it makes it hard to figure out what went wrong. I added some logic for the SLURM scheduler to ipython-cluster-helper that checks to see if the requested time is more than the maximum time allowed on the cluster, and if it is, sets the time to be the maximum time allowed instead, so at least now the jobs will get queued.
You can force time to be something else by passing -r “time=1-00:00” in your call to bcbio-nextgen which should get you started. Thanks!


Improve indexify examples

Improve indexify examples
YouTube Video Summarizer Improvements
Key Improvements

Code Refactoring: Separated concerns more clearly, improved function naming, and streamlined the main execution flow.
Documentation: Added a comprehensive README that covers installation, usage, and customization.
Error Handling: Implemented more robust error catching and logging to help with debugging and user feedback.
Standardization: Ensured consistent coding style and structure throughout the project.

what do we want to do with indexify/examples/website_audio_summary ,  indexify/examples/tweetsgenerator, indexify/examples/multi_model_pdf_parser and indexify/examples/image_detection_indexing ?

@diptanu except for website audio (didnt have elevenlabs credits) rest are tested


Python bindings for scatter operations

Proposed changes
Expose scatter operations to the python API.
Any help on completing this is welcome.
It's up for discussion whether we should expose only the scatter operations with different modes or also the various scatter_add, scatter_prod,...
Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING document
[x] I have run pre-commit run --all-files to format my code / installed pre-commit prior to committing changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have updated the necessary documentation (if needed)

Ideally, we need examples in docs and tests for the binding.

Hi, thanks for starting this, that's great! However if we are to expose scatter it would be similar to C++ via scatter_add, scatter_prod etc. Not via a general scatter that accepts a mode parameter.
Additionally, indexing is generally a more friendly interface so it might be worth mapping those to x[indices] += y rather than scatter_add for instance. Albeit as I mentioned in #394 it would require several shenanigans so it might not be worth it.
The most probably future path, imho, is to expose scatter_{op} so I think the work you are doing is not in vain but I am writing so that we can coordinate.

Hi @angeloskath, great - we're iterating on exposing each scatter_{op}. Do you think having also the generic scatter with the mode parameter (as @gboduljak implemented in https://github.com/francescofarina/mlx/pull/1) would be handy? That's often available in other libraries.

The most probably future path, imho, is to expose scatter_{op} so I think the work you are doing is not in vain but I am writing so that we can coordinate.

As per @angeloskath's suggestion, I will work on exposing  scatter_{op} instead of generic scatter.

As per @angeloskath's suggestion, I will work on exposing scatter_{op} instead of generic scatter.

This is now done. @francescofarina please see new bindings PR.

I'm slightly confused, there are two ongoing PRs for scatter ops in MLX 🤔 (#394 has bindings as well). It seems like they are going for different APIs, but o/w mostly the same?

Looks like this one can be safely closed and we can move with https://github.com/ml-explore/mlx/pull/394 which has a different API. @angeloskath @gboduljak ?

Yeah, sorry for stepping on your toes guys.
It kinda evolved from writing the gradients for scatter and scatter_add and then realizing that scatter_{op} would be kinda hard for people to understand (or rather me to document properly) so I implemented the array.at interface which is much simpler to understand.

Closing this in favor of #394. @francescofarina @gboduljak your feedback on #394 is appreciated.