fix(ui): typo in ota update tab

Fixed a typo in loading text caption

I already fixed it in zwavejs 10 PR, BTW I dunno when I will merge that so giving that this is the 3rd PR I receive to fix this typo I will accept it 😆 Thanks! 🙏🏼

Ha, apologies for the duplication and failure to check the other PRs :D

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 24.785%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3682

Relevant Lines:
15693

💛  - Coveralls


Inconsistent Error Message Displayed for Network Connectivity Issue

Version: 1.79.0-insider (user setup)
Commit: f1258a5fbed44b8f84a097c73c1799c13c5c3646
Date: 2023-05-17T05:27:38.052Z
Electron: 22.5.2
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Test Report - Copilot Chat Network Error Handling
Test Case ID: COPILOT-CHAT-NET-001
Test Case Description: Verify error handling when the network is not available.
Test Steps:

Disable network connectivity on the testing device.
Perform an action that requires network access, such as sending a message or loading a conversation.
Verify the displayed error message.

Test Data:

Network connectivity disabled

Expected Results:

The system should detect the lack of network connectivity.
An appropriate error message should be displayed, indicating a network issue.
The error message should prompt the user to check the log for more details.

Test Execution Results:
Test Case Status: Failed
Test Execution Notes:
During the execution of the test case, when network connectivity was disabled, the system did not display an appropriate error message. Instead, the error message "Error on conversation request. Check the log for more details." was displayed. This error message does not clearly indicate a network issue.
Defect Details:
Defect ID: COPILOT-CHAT-NET-001
Defect Description: Incorrect error message displayed for network connectivity issue.
Severity: Medium
Priority: High
Assigned To: Development Team
Status: New
Recommendations:

Update the error message to clearly indicate a network issue, such as "Error: Network not available. Please check your network connection and try again."
Provide a user-friendly prompt or suggestion to resolve the network issue, if applicable.
Improve error handling to gracefully handle network connectivity problems and provide informative messages to users.

Attachments:
N/A
Test Environment:

Testing device: Laptop
Operating System: Windows 10
Network Connectivity: Disabled

Tester's Name: Kalyan Chakravarthy
Date of Execution: 20 May 2023
Please note that this test report is based on the observation during the testing phase. The development team should review the report and take necessary actions to address the identified defect and implement the recommendations provided.

I encountered the same issue. The internet connection is too unstable and it keeps loading in circles, unable to refresh.

@chakravarthik27 for future tickets, please stick the original template and don't add overhead by running your filed issues through ChatGPT.

Error message should be improved and next release


Not seeing video of a mobile participant from the react web app

Hi,
I'm not sure if this is a bug from this react app example, but:
When creating a small group room
ex: 2 mobile participants and 2 web participants
From the react web app:

When a mobile join a video (flutter app), we don't see the video of the mobile participant from the web app
But we see the videos of others web participants

From the mobile app:

We see all videos participants (web & mobiles)

Sound is working.
To Reproduce
Steps to reproduce the behavior:

Create a room
Have two or more participants in it (at least 1 mobile and 1 web)
Join the room
In the web app the video of the mobile participant is not displayed: it is like if the mobile stopped his video)
In others mobile we see all participants video.

Expected behavior
We see the video of the mobile participant from the webapp
Screenshots
N/A
Environment (please complete the following information):

MacOS (chrome & safari last versions)
Current master

Additional context
N/A

Thanks for the issue @rodriguezc!
It's hard to say what the problem might be without seeing the code to the Flutter app, but I have a guess.
In order for the React app to differentiate between a user's camera track and a user's screen share track, we give the tracks names before they are published to the room. Then, this app renders the track named 'camera' in the participant thumbnails, and it renders any screen share track (with name 'screen') in the main window.
In your flutter app, can you try naming a user's camera track "camera" before publishing it to the room? I'm not sure how this would work in flutter, but in JS, we can pass a name property in the CreateLocalTrackOptions object: https://media.twiliocdn.com/sdk/js/video/releases/2.12.0/docs/global.html#CreateLocalTrackOptions
Let me know how this works out for you. Thanks!

Hi @timmydoza ,
Thank you for your answer. You were right. We had to specify "camera" as track name in the flutter app. For my understanding, why do you look for the track name instead of track kind for the video in this react app ?
Thank you,
Best regards,

Great question @rodriguezc!
We look at track.name instead of track.kind because it is possible for a user to be publishing multiple video tracks. When a user is sharing their screen while their camera is on, they are publishing two video tracks to the room. Since both of these tracks have track.kind equal to 'video', we need to look at the name property in order to distinguish them. For example:
const cameraTrack = tracks.find(track => track.name.includes('camera'));
const screenShareTrack = tracks.find(track => track.name.includes('screen'));

I'll close this issue since it sounds like your flutter app is working as expected, but please let me know if you have any other questions. We're always happy to help!


Webpack 4, mini-css-extract-plugin and Material Icons

Hi, it appears that the mini-css-extract-plugin as recommended when using Webpack 4 doesn't support remote requests. As such the line 318 VuePictureSwipe.vue @import "https://fonts.googleapis.com/icon?family=Material+Icons"; creates an error
Unexpected format https://fonts.googleapis.com/icon?family=Material+Icons
The only way to rectify it is to copy/paste the code from the remote URL in place of that line:
/* fallback */
@font-face {
  font-family: 'Material Icons';
  font-style: normal;
  font-weight: 400;
  src: url(https://fonts.gstatic.com/s/materialicons/v41/flUhRq6tzZclQEJ-Vdg-IuiaDsNcIhQ8tQ.woff2) format('woff2');
}

.material-icons {
  font-family: 'Material Icons';
  font-weight: normal;
  font-style: normal;
  font-size: 24px;
  line-height: 1;
  letter-spacing: normal;
  text-transform: none;
  display: inline-block;
  white-space: nowrap;
  word-wrap: normal;
  direction: ltr;
  -moz-font-feature-settings: 'liga';
  -moz-osx-font-smoothing: grayscale;
}

For those who had this or a similar problem as I did, getting errors like:

Error: /iconfont/material-icons.css
Module build failed...
ModuleParseError: Module parse failed: Unexpected character '

I solved it by doing what was done here: https://stackoverflow.com/a/51701648/1599699

Thank you @AndrewDavis !


BLD: update for new python version

@mrakitin once tests pass, mind giving this another look? Should resolve your comment above.
(... look at all those glorious force-pushes as I upgraded from trusty -> xenial!)

Codecov Report

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

@@            Coverage Diff            @@
##             master     #583   +/-   ##
=========================================
  Coverage          ?   88.08%
=========================================
  Files             ?       55
  Lines             ?     8664
  Branches          ?        0
=========================================
  Hits              ?     7632
  Misses            ?     1032
  Partials          ?        0

Continue to review full report at Codecov.

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

Thanks @mrakitin !


Allow custom target dirs

It would be nice if this could be used to push all files, not just workflows, to a repo. Some tools like Dependabot or labeler require a file in .github or in the root dir instead.
I'm not familiar with the package, so this is untested. Feel free to push to the branch directly, too.

The line between this package and the more low-level GitHub.jl is a bit blurry, so it's not always an easy call. If we do this the change needs to propagate to the docstring, README etc, so that the documentation isn't lying.

Bump @SaschaMann @timholy

@SaschaMann @timholy I'm closing this PR as stale.
Maybe instead of this package, we could put this code in a separate package? GitHubUtils.jl or GitHubUtilities.jl or GitHubConvenience.jl or something like that?

Oops, I forgot about the PR. I ended up solving it differently. Sorry for the noise.


Fix memory error

I have made two things.

Combined matrix multiplication is divided into pairs.
Input data of NaCl ridge regression test was made smaller.

Codecov Report

Merging #8 (12a44fe) into develop (52bf706) will increase coverage by 0.68%.
Report is 7 commits behind head on develop.
The diff coverage is 100.00%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##           develop       #8      +/-   ##
===========================================
+ Coverage    90.94%   91.63%   +0.68%
===========================================
  Files            7        7
  Lines          486      514      +28
===========================================
+ Hits           442      471      +29
+ Misses          44       43       -1

Files Changed
Coverage Δ

src/symfc_alm/ridge.py
95.78% <100.00%> (+1.67%)
:arrow_up:

tests/test_ridge.py
96.82% <100.00%> (+0.49%)
:arrow_up:

tests/test_symfc-alm.py
90.29% <100.00%> (+0.09%)
:arrow_up:


Cannot "precompile" on macOS 10.14.5

> Executing task: ninja -f ninja/macos.ninja <

[0/3] cd 3rd/bee.lua && ninja -f ninja/macos.ninja
[43/89] Compile CXX build/macos/obj/bee/lua_filesystem.obj
FAILED: build/macos/obj/bee/lua_filesystem.obj
g++ -MMD -MT build/macos/obj/bee/lua_filesystem.obj -MF build/macos/obj/bee/lua_filesystem.obj.d -std=c++17 -O2 -Wall -I3rd/lua/src -I3rd/lua-seri -I3rd/incbin -I. -Dspan_FEATURE_BYTE_SPAN=1 -DNDEBUG -fPIC -o build/macos/obj/bee/lua_filesystem.obj -c binding/lua_filesystem.cpp
In file included from binding/lua_filesystem.cpp:7:
./bee/utility/path_helper.h:8:71: error: 'path' is unavailable: introduced in macOS 10.15
    _BEE_API auto dll_path(void* module_handle)->nonstd::expected<fs::path, std::exception>;
                                                                      ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
In file included from binding/lua_filesystem.cpp:7:
./bee/utility/path_helper.h:9:52: error: 'path' is unavailable: introduced in macOS 10.15
    _BEE_API auto exe_path()->nonstd::expected<fs::path, std::exception>;
                                                   ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
In file included from binding/lua_filesystem.cpp:7:
./bee/utility/path_helper.h:10:52: error: 'path' is unavailable: introduced in macOS 10.15
    _BEE_API auto dll_path()->nonstd::expected<fs::path, std::exception>;
                                                   ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
In file included from binding/lua_filesystem.cpp:7:
./bee/utility/path_helper.h:11:29: error: 'path' is unavailable: introduced in macOS 10.15
    _BEE_API bool equal(fs::path const& lhs, fs::path const& rhs);
                            ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
In file included from binding/lua_filesystem.cpp:7:
./bee/utility/path_helper.h:11:50: error: 'path' is unavailable: introduced in macOS 10.15
    _BEE_API bool equal(fs::path const& lhs, fs::path const& rhs);
                                                 ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
binding/lua_filesystem.cpp:18:37: error: 'path' is unavailable: introduced in macOS 10.15
            directory_container(fs::path const& o)
                                    ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
binding/lua_filesystem.cpp:20:17: error: 'directory_iterator' is unavailable: introduced in macOS 10.15
            fs::directory_iterator begin() const { return fs::directory_iterator(p); }
                ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:2408:7: note: 'directory_iterator' has been explicitly marked unavailable here
class directory_iterator {
      ^
binding/lua_filesystem.cpp:21:17: error: 'directory_iterator' is unavailable: introduced in macOS 10.15
            fs::directory_iterator end() const { return fs::directory_iterator(); }
                ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:2408:7: note: 'directory_iterator' has been explicitly marked unavailable here
class directory_iterator {
      ^
binding/lua_filesystem.cpp:24:23: error: 'path' is unavailable: introduced in macOS 10.15
            const fs::path& p;
                      ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
binding/lua_filesystem.cpp:20:63: error: 'directory_iterator' is unavailable: introduced in macOS 10.15
            fs::directory_iterator begin() const { return fs::directory_iterator(p); }
                                                              ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:2408:7: note: 'directory_iterator' has been explicitly marked unavailable here
class directory_iterator {
      ^
binding/lua_filesystem.cpp:20:59: error: 'directory_iterator' is unavailable: introduced in macOS 10.15
            fs::directory_iterator begin() const { return fs::directory_iterator(p); }
                                                          ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:2420:12: note: 'directory_iterator' has been explicitly marked unavailable here
  explicit directory_iterator(const path& __p)
           ^
binding/lua_filesystem.cpp:20:59: error: '~directory_iterator' is unavailable: introduced in macOS 10.15
            fs::directory_iterator begin() const { return fs::directory_iterator(p); }
                                                          ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:2445:3: note: '~directory_iterator' has been explicitly marked unavailable here
  ~directory_iterator() = default;
  ^
binding/lua_filesystem.cpp:21:61: error: 'directory_iterator' is unavailable: introduced in macOS 10.15
            fs::directory_iterator end() const { return fs::directory_iterator(); }
                                                            ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:2408:7: note: 'directory_iterator' has been explicitly marked unavailable here
class directory_iterator {
      ^
binding/lua_filesystem.cpp:21:57: error: 'directory_iterator' is unavailable: introduced in macOS 10.15
            fs::directory_iterator end() const { return fs::directory_iterator(); }
                                                        ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:2418:3: note: 'directory_iterator' has been explicitly marked unavailable here
  directory_iterator() noexcept {}
  ^
binding/lua_filesystem.cpp:21:57: error: 'directory_iterator' is unavailable: introduced in macOS 10.15
            fs::directory_iterator end() const { return fs::directory_iterator(); }
                                                        ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:2418:3: note: 'directory_iterator' has been explicitly marked unavailable here
  directory_iterator() noexcept {}
  ^
binding/lua_filesystem.cpp:21:57: error: '~directory_iterator' is unavailable: introduced in macOS 10.15
            fs::directory_iterator end() const { return fs::directory_iterator(); }
                                                        ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:2445:3: note: '~directory_iterator' has been explicitly marked unavailable here
  ~directory_iterator() = default;
  ^
binding/lua_filesystem.cpp:29:20: error: 'path' is unavailable: introduced in macOS 10.15
        static fs::path& to(lua_State* L, int idx) {
                   ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
binding/lua_filesystem.cpp:30:26: error: 'path' is unavailable: introduced in macOS 10.15
            return *(fs::path*)getObject(L, idx, "filesystem");
                         ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
binding/lua_filesystem.cpp:35:31: error: 'path' is unavailable: introduced in macOS 10.15
            new (storage) fs::path();
                              ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
[46/89] Compile CXX build/macos/obj/bee/lua_subprocess.obj
FAILED: build/macos/obj/bee/lua_subprocess.obj
g++ -MMD -MT build/macos/obj/bee/lua_subprocess.obj -MF build/macos/obj/bee/lua_subprocess.obj.d -std=c++17 -O2 -Wall -I3rd/lua/src -I3rd/lua-seri -I3rd/incbin -I. -Dspan_FEATURE_BYTE_SPAN=1 -DNDEBUG -fPIC -o build/macos/obj/bee/lua_subprocess.obj -c binding/lua_subprocess.cpp
In file included from binding/lua_subprocess.cpp:4:
./bee/lua/path.h:29:42: error: 'path' is unavailable: introduced in macOS 10.15
            const fs::path& path = *(fs::path*)getObject(L, idx, "filesystem");
                                         ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
In file included from binding/lua_subprocess.cpp:4:
./bee/lua/path.h:29:23: error: 'path' is unavailable: introduced in macOS 10.15
            const fs::path& path = *(fs::path*)getObject(L, idx, "filesystem");
                      ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
In file included from binding/lua_subprocess.cpp:4:
./bee/lua/path.h:30:25: error: 'string' is unavailable: introduced in macOS 10.15
            return path.string<lua::string_type::value_type>();
                        ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:990:3: note: 'string' has been explicitly marked unavailable here
  string(const _Allocator& __a = _Allocator()) const {
  ^
In file included from binding/lua_subprocess.cpp:4:
./bee/lua/path.h:30:25: error: 'string<char, std::__1::char_traits<char>, std::__1::allocator<char> >' is unavailable: introduced in macOS 10.15
            return path.string<lua::string_type::value_type>();
                        ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:990:3: note: 'string<char, std::__1::char_traits<char>, std::__1::allocator<char> >' has been explicitly marked unavailable here
  string(const _Allocator& __a = _Allocator()) const {
  ^
4 errors generated.
[47/89] Compile CXX build/macos/obj/bee/path_helper.obj
FAILED: build/macos/obj/bee/path_helper.obj
g++ -MMD -MT build/macos/obj/bee/path_helper.obj -MF build/macos/obj/bee/path_helper.obj.d -std=c++17 -O2 -Wall -I3rd/lua/src -I3rd/lua-seri -I3rd/incbin -I. -Dspan_FEATURE_BYTE_SPAN=1 -DNDEBUG -fPIC -o build/macos/obj/bee/path_helper.obj -c bee/utility/path_helper.cpp
In file included from bee/utility/path_helper.cpp:1:
./bee/utility/path_helper.h:8:71: error: 'path' is unavailable: introduced in macOS 10.15
    _BEE_API auto dll_path(void* module_handle)->nonstd::expected<fs::path, std::exception>;
                                                                      ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
In file included from bee/utility/path_helper.cpp:1:
./bee/utility/path_helper.h:9:52: error: 'path' is unavailable: introduced in macOS 10.15
    _BEE_API auto exe_path()->nonstd::expected<fs::path, std::exception>;
                                                   ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
In file included from bee/utility/path_helper.cpp:1:
./bee/utility/path_helper.h:10:52: error: 'path' is unavailable: introduced in macOS 10.15
    _BEE_API auto dll_path()->nonstd::expected<fs::path, std::exception>;
                                                   ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
In file included from bee/utility/path_helper.cpp:1:
./bee/utility/path_helper.h:11:29: error: 'path' is unavailable: introduced in macOS 10.15
    _BEE_API bool equal(fs::path const& lhs, fs::path const& rhs);
                            ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
In file included from bee/utility/path_helper.cpp:1:
./bee/utility/path_helper.h:11:50: error: 'path' is unavailable: introduced in macOS 10.15
    _BEE_API bool equal(fs::path const& lhs, fs::path const& rhs);
                                                 ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
bee/utility/path_helper.cpp:51:43: error: 'path' is unavailable: introduced in macOS 10.15
    auto exe_path()->nonstd::expected<fs::path, std::exception> {
                                          ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
bee/utility/path_helper.cpp:62:20: error: 'path' is unavailable: introduced in macOS 10.15
        return fs::path(buf.data(), buf.data() + path_len - 1);
                   ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
bee/utility/path_helper.cpp:62:16: error: 'path<char *>' is unavailable: introduced in macOS 10.15
        return fs::path(buf.data(), buf.data() + path_len - 1);
               ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:778:3: note: 'path<char *>' has been explicitly marked unavailable here
  path(_InputIt __first, _InputIt __last, format = format::auto_format) {
  ^
bee/utility/path_helper.cpp:62:16: error: 'path' is unavailable: introduced in macOS 10.15
        return fs::path(buf.data(), buf.data() + path_len - 1);
               ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:778:3: note: 'path' has been explicitly marked unavailable here
  path(_InputIt __first, _InputIt __last, format = format::auto_format) {
  ^
bee/utility/path_helper.cpp:62:16: error: '~path' is unavailable: introduced in macOS 10.15
        return fs::path(buf.data(), buf.data() + path_len - 1);
               ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:791:3: note: '~path' has been explicitly marked unavailable here
  ~path() = default;
  ^
bee/utility/path_helper.cpp:99:62: error: 'path' is unavailable: introduced in macOS 10.15
    auto dll_path(void* module_handle)->nonstd::expected<fs::path, std::exception> {
                                                             ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
bee/utility/path_helper.cpp:104:24: error: 'absolute' is unavailable: introduced in macOS 10.15
            return fs::absolute(dl_info.dli_fname).lexically_normal();
                       ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:1477:39: note: 'absolute' has been explicitly marked unavailable here
inline _LIBCPP_INLINE_VISIBILITY path absolute(const path& __p) {
                                      ^
bee/utility/path_helper.cpp:104:33: error: 'path<const char *, void>' is unavailable: introduced in macOS 10.15
            return fs::absolute(dl_info.dli_fname).lexically_normal();
                                ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:773:3: note: 'path<const char *, void>' has been explicitly marked unavailable here
  path(const _Source& __src, format = format::auto_format) {
  ^
bee/utility/path_helper.cpp:104:33: error: '~path' is unavailable: introduced in macOS 10.15
            return fs::absolute(dl_info.dli_fname).lexically_normal();
                                ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:791:3: note: '~path' has been explicitly marked unavailable here
  ~path() = default;
  ^
bee/utility/path_helper.cpp:104:20: error: '~path' is unavailable: introduced in macOS 10.15
            return fs::absolute(dl_info.dli_fname).lexically_normal();
                   ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:791:3: note: '~path' has been explicitly marked unavailable here
  ~path() = default;
  ^
bee/utility/path_helper.cpp:104:52: error: 'lexically_normal' is unavailable: introduced in macOS 10.15
            return fs::absolute(dl_info.dli_fname).lexically_normal();
                                                   ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:1110:8: note: 'lexically_normal' has been explicitly marked unavailable here
  path lexically_normal() const;
       ^
bee/utility/path_helper.cpp:104:52: error: '~path' is unavailable: introduced in macOS 10.15
            return fs::absolute(dl_info.dli_fname).lexically_normal();
                                                   ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:791:3: note: '~path' has been explicitly marked unavailable here
  ~path() = default;
  ^
bee/utility/path_helper.cpp:109:43: error: 'path' is unavailable: introduced in macOS 10.15
    auto dll_path()->nonstd::expected<fs::path, std::exception> {
                                          ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
bee/utility/path_helper.cpp:129:20: error: 'path' is unavailable: introduced in macOS 10.15
    bool equal(fs::path const& lhs, fs::path const& rhs) {
                   ^
/Library/Developer/CommandLineTools/usr/bin/../include/c++/v1/filesystem:739:24: note: 'path' has been explicitly marked unavailable here
class _LIBCPP_TYPE_VIS path {
                       ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
[52/89] Compile CXX build/macos/obj/bee/lua_filewatch.obj
ninja: build stopped: subcommand failed.
FAILED: build/macos/_/bee
cd 3rd/bee.lua && ninja -f ninja/macos.ninja
ninja: build stopped: subcommand failed.
The terminal process terminated with exit code: 1

What is your compiler version?
Your compiler includes filesystem but can't compile it.

You're right, I was set to a different compiler for some reason.  Running this command fixed my issue:
xcode-select -r


e.value is null

Setup

Rancher version: v2.7.6
Rancher UI Extensions: none?
Browser type & version: Firefox 121.0.1 (64-bit) on Windows

Describe the bug
Frequently when I navigate the Rancher GUI, I get presented with a blank screen saying "e.value is null". It's not a great user experience and I find it annoying.
To Reproduce
Sorry for a bad bug report. I'm tired and just need to post this so I remember to do it. It feels like "anything I do results in this", but that's mostly me being tired and having run into it about 10 times the last hour. I'll update this post if/when I can reliably reproduce it. Should not be too hard, I think…
Result

Expected Result
If something is wrong, give me a popup or warning on the screen, do not flush the whole web app with a less then helpful error message. If something is not wrong, please don't crash.
Screenshots

Additional context
Feels like this kind of bug should be easy to find with automated linting tools and/or typechecking.
Very similar to #10128

This will be the result of a developer error page mistakenly being shown in production and is resolved in 2.8 and the next feature release of 2.7 (for tracking see https://github.com/rancher/dashboard/issues/9542)
There will be an underlying error, but after upgrading if there are functional issues please just let us know via a fresh gh issue.


Another try at dockerversion placeholder for library import

Hope it does not broke everything again :scream:

On this one decided to keeps the version package — looked accross other docker/* project and almost all of them are using this package for versions (swarm, distribution, libcompose, …) — and decided to rename VERSION to VERSION.txt 🐍.

Ping @cpuguy83 @icecrime @jhowardmsft and any other folks that is building docker something else than Linux 🐧 for testing this on your computers (until I get my hands on some windows or apple computers xD).
Ping @tianon @jfrazelle on the VERSION to VERSION.txt files. I've updated docs and rules (for debian) that refers to this file but it might be used elsewhere — and if we can't rename that one, we'll find another package :wink: .

I'll squash the commits if the move VERSION to VERSION.txt is ok.
To re-add some context :

what about doing this, instead, as a placeholder? https://gist.github.com/erikh/e6f0c5e4b7b6c2483d52
you could leave this in the repository so it's still go-gettable, but then overwrite it during the build. how does this sound?

To add to the discussion, quotation from @ibuildthecloud

I know people shouldn't import non-pkg code but I don't like that effectively docker makes it not possible. If people want to import stuff at their own risk, just let them.

🐸

The "VERSION" filename is a pretty well-established convention across
projects, so doing this just because we can't think of a better
name/location for the version package feels wrong IMO.  We've also got a
lot of people using this file in scripting outside our repo (both packaging
and otherwise) so this might cause some backlash there.
The "version" package was "dockerversion" before it moved into autogen fwiw.

@tianon feels ok to me to keep dockerversion name, or even autogen/dockerversion :stuck_out_tongue_closed_eyes: (it feels safer and less changes too :wink: ).

ping @cpuguy83 @icecrime @jhowardmsft for trying this out on case-insensitive fs :cat:
ping @jfrazelle @tianon @calavera  for LGTMs :kissing_cat:

Yay, it compiles. I think you need to add dockerversion/ to .gitignore though.

Ohh right, true :wink:

LGTM otherwise.

LGTM pending .gitignore entry updating :+1:

LGTM


git-flow

Hi
Sorry for being bit critical, but I think honest opinion can be more than constructive. I love your project, your effort and the idea. Problem is process. I tried to install JAWS from npm and both jaws and jaws-framework seemed to lack module install option (as it was removed) and postinstall haven't executed at all. I tried to checkout v1.4 head and I got:
TypeError: BbPromise.catch is not a function
    at Object.exports.execute (/usr/local/lib/node_modules/jaws-framework/lib/utils/index.js:61:13)
    at Object.<anonymous> (/usr/local/lib/node_modules/jaws-framework/bin/jaws:11:11)
    at Module._compile (module.js:434:26)
    at Object.Module._extensions..js (module.js:452:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:475:10)
    at startup (node.js:117:18)
    at node.js:951:3

and when I checked out 1 checking before removing module install from master project create didn't work.
As you can imagine I was almost going to stop using JAWS. But as we are all early adopters I have bit more will to stay and don't want to reinvent the wheel.
Scary thing is that some people commit directly to master or version branch and seems that there is no review or tests. There are lot of commits like in progress. All of it is bit against idea how git should be used.
  Then once you are happy and all is tested you do git rebase to squash all crappy name commits and create PR to man repository.
It is a bit overhead, but you would need to adapt it to build sustainable development is such big team. I may be wrong, but current process can only kill the project.

Agreed 100%

I completely agree with you. Our codebase and workflow is really messy right now. It's mostly because we're still figuring out lots things, specifically for the team & workflow.
We try to keep master as clean as possible, and we don't encourage checking out v1.4 at all, since it'll always be breaking. Once it's complete and tested we'll merge into master. This workflow is far from perfect, but we're improving rapidly (got lots of awesome things coming up :wink:)
Thanks so much for your feedback. And please, keep it coming!

will do :) project is great


switch zarr dev testing to v3 branch

It looks like v2 is being removed in https://github.com/zarr-developers/zarr-python/pull/1898 so this isn't going to work. We should probably just pin zarr to less than 3.


Failed to load 'magit' and 'org' package incrementally

What actually happened?
When I open doom-emacs I receive two similar error messages:
Failed to load 'magit' package incrementally because (user-error The Org-roam database was created with a newer Org-roam version)
and
Failed to load 'org' package incrementally because (user-error The Org-roam database was created with a newer Org-roam version)
System information:

((emacs
  (version . "26.3")
  (features . "XPM JPEG TIFF GIF PNG RSVG SOUND NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS THREADS LCMS2")
  (build . "Aug 29, 2019")
  (buildopts "--without-dbus --host=x86_64-w64-mingw32 --without-compress-install 'CFLAGS=-O2 -static -g3'")
  (windowsys . batch)
  (daemonp . server-running))
 (doom
  (version . "2.0.9")
  (build . "HEAD -> develop a262527a7 2020-05-21 04:33:39 -0400")
  (dir . "~/.doom.d/"))
 (system
  (type . windows-nt)
  (config . "x86_64-w64-mingw32")
  (shell . "C:/Program Files/emacs-26.3-x86_64/libexec/emacs/26.3/x86_64-w64-mingw32/cmdproxy.exe")
  (uname . "n/a")
  (path "c:/Program Files/PowerShell/7-preview" "C:/Python38/Scripts/" "C:/Python38/" "C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v10.2/bin" "C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v10.2/libnvvp" "C:/Windows/system32" "C:/Windows" "C:/Windows/System32/Wbem" "C:/Windows/System32/WindowsPowerShell/v1.0/" "C:/Windows/System32/OpenSSH/" "C:/Program Files/Git/cmd" "C:/ProgramData/chocolatey/bin" "C:/Program Files/emacs-26.3-x86_64/bin" "C:/Program Files (x86)/Calibre2/" "C:/Program Files/NVIDIA Corporation/Nsight Compute 2019.5.0/" "C:/Program Files (x86)/NVIDIA Corporation/PhysX/Common" "C:/Program Files/NVIDIA Corporation/NVIDIA NvDLISR" "~/AppData/Local/Programs/Julia/Julia-1.4.1/bin" "C:/Program Files (x86)/Vim/vim82" "C:/Program Files/Calibre2/" "~/.emacs.d/bin" "C:/Program Files/PowerShell/7-preview/preview" "C:/Program Files/sqlite3" "~/scoop/apps/graphviz/2.38/bin" "~/scoop/apps/gcc/current/bin" "~/scoop/shims" "~/AppData/Local/Microsoft/WindowsApps" "~/AppData/Local/Programs/Microsoft VS Code/bin" "~/AppData/Local/Programs/MiKTeX 2.9/miktex/bin/x64/" "~/AppData/Local/Julia-1.3.1/bin" "C:/Program Files/wkhtmltopdf/bin" "~/Anaconda3" "~/Anaconda3/Scripts" "~/AppData/Local/atom/bin" "~/AppData/Local/Pandoc/" "~/CMD" "C:/Program Files (x86)/GnuWin32/bin" "c:/Program Files/emacs-26.3-x86_64/libexec/emacs/26.3/x86_64-w64-mingw32"))
 (config
  (envfile . envvar-file)
  (elc-files . 0)
  (modules :completion company helm ivy :ui deft doom doom-dashboard doom-quit hl-todo modeline ophints (popup +defaults) unicode vc-gutter vi-tilde-fringe workspaces :editor (evil +everywhere) file-templates fold snippets :emacs dired electric undo vc :term term :checkers syntax spell grammar :tools (eval +overlay) lookup magit :lang emacs-lisp julia latex markdown (org +roam) python sh :config (default +bindings +smartparens))
  (packages (emacsql-sqlite3) (org-ref) (org-roam-bibtex))
  (unpin "n/a")
  (elpa "n/a")))

Disabling roam in your doom.d/init.el will fix this.
Assuming you can rebuild your org-roam db (or don't care if it gets wiped), deleting the database file should also do the trick.

@leoalekseyev And after that, shall I be able to reinstall org-roam again without problem? I simply followed the instructions to install it in the init file (org +roam). I don't understand why the error message says "it was created with a newer Org-roam version".

Solved! Both in Windows and MacOS with (unpin! org-roam) and after that doom update.

I ran into a similar issue. All I added was +roam to my init.el and after a doom up I was greeted with
Failed to load org package incrementally, because: (error Selecting deleted buffer). If I remove the +roam tag from lang>org and run doom up the problem is fixed. However, I can't use org-roam :(

System Info

```
((emacs
  (version . "27.0.91")
  (features . "RSVG IMAGEMAGICK DBUS GLIB NOTIFY KQUEUE ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS XWIDGETS JSON PDUMPER LCMS2 GMP")
  (build . "May 15, 2020")
  (buildopts "--disable-dependency-tracking --disable-silent-rules --enable-locallisppath=/usr/local/share/emacs/site-lisp --infodir=/usr/local/Cellar/emacs-plus/HEAD-e75f6be/share/info/emacs --prefix=/usr/local/Cellar/emacs-plus/HEAD-e75f6be --with-xml2 --with-gnutls --with-dbus --with-imagemagick --with-json --with-modules --with-rsvg --without-pop --with-xwidgets --with-ns --disable-ns-self-contained")
  (windowsys . batch)
  (daemonp . server-running))
 (doom
  (version . "2.0.9")
  (build . "HEAD -> develop 847bbf380 2020-06-13 17:12:23 -0400")
  (dir . "~/.config/dotfiles/Emacs/.doom.d/"))
 (system
  (type . darwin)
  (config . "x86_64-apple-darwin19.4.0")
  (shell . "/usr/local/bin/zsh")
  (uname . "Darwin 19.5.0 Darwin Kernel Version 19.5.0: Tue May 26 20:41:44 PDT 2020; root:xnu-6153.121.2~2/RELEASE_X86_64 x86_64")
  (path<EMAIL_ADDRESS>"~/.cargo/bin" "/usr/local/bin" "/usr/bin" "/bin" "/usr/sbin" "/sbin" "/Applications/Wireshark.app/Contents/MacOS"<EMAIL_ADDRESS>"~/.emacs.d/bin" "/usr/local/bin" "~/.emacs.d/bin" "/usr/local/Cellar/emacs-plus/HEAD-e75f6be/libexec/emacs/27.0.91/x86_64-apple-darwin19.4.0"))
 (config
  (envfile . envvar-file)
  (elc-files .  Then unpin! org-roam in packages.el. And finally doom update.
That's what I did and it works.

@sbacelar I followed your instructions and experience the same issue. Also, trying to load magit with SPC g g returns Selecting deleted buffer and magit won't open.
The only fix I've found is to remove the +roam tag then doom sync doom update
Notice my error is Selecting deleted buffer instead of user-error The Org-roam database was created with a newer Org-roam version Perhaps this warrants a new issue?

@chrislockard Yes and maybe you can open also an issue in Org-roam. That's what I did.

Opened https://github.com/hlissner/doom-emacs/issues/3403


Feature/const normals

Continuing to replace Lazy values with const values. This PR trades the once_cell dependency for constgebra, allowing the vector calculations to also be completed at compile time. Also did some work on constgebra for this to improve the API. Understand if you think this is too much for just dropping a couple lazily computed values; I'm weird about liking stuff done at compile time.

It took a little contemplating, but I think I'm on board.
This PR has made me realize, however, that my implementation of normals is incorrect -- those won't be normalized at all lol.
Would you mind fixing that while you're at it? Shouldn't cost anything to do at runtime since this is all going to be done at compiletime anyway.

Sure! Will work on that when I have time next

Thanks! Sorry for kind of springing it on you, but thankfully it shouldn't be too complex to implement :)

@OptimisticPeach Gave it a shot. I linked the source I used in the comment for normal if you want to compare/check that it's the correct procedure.

Ah 😅 I wasn't really clear about what was wrong with my approach. The original vectors were pointing in the right direction, it's just tha they had the wrong magnitude (something < 1 given how I was computing it... it should be 1).
My approach worked on the basis that all of the triangles had normals that were facing away from the origin, hence the normal should point in the direction equal to the average of the three vertices.
Your approach works too, however the source you linked is misleading, in that it too won't produce vectors of length 1!
In reality, what both of our methods are missing is normalizing the vector -- dividing it by its length.
I'll add a commit which does that (and I'll probably use my old method, since getting the ordering correct is annoying when using the cross product method) and get this merged after that.

Ah ok, I've never messed with those before lol. Sorry about that


Fix issue #2357

Added some JS code to fix the issue with enter starting a new message even if nothing is in the search box

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

@Bickio This looks great, but we can clean up the commit message here.  How about...
Do not open compose box if user sidebar search is empty.

Fixes #2357

There you go!

Fix merged, thanks @Bickio!!


Ability to flatten nest models

It would  be nice to have a function which can flatten a model of models so that doing model.layers does not contain any model.engine.training.Model objects.

This would also help with #5937


OptionController value coercing number to string

Inside OptionController by using the HTML DOM option object and specifically the inherited setAttribute method any value in a list of possible options that should be a number will subsequently be converted into a string by the native implementation of setAttribute method.
https://github.com/dataarts/dat.gui/blob/8cd1b4d2ae0982b63105deedac320004373af99b/src/dat/controllers/OptionController.js#L54
Happens when wanting to have multiple numbers as options when using add with args that are of type:
 add(target: Object, propName:string, items:number[]): GUIController;
https://developer.mozilla.org/en-US/docs/Web/API/Element/setAttribute

The values of a select input will always be of type string. That's the HTML spec, and so cannot remain a number.
You could subscribe to the onchange event and coerce them back using Number or parseInt.

Yep, I've already done that as a solution but I feel it just makes the system inflexible. Why can this not be refactored to use a data object that can support number values?
The type definitions specify support for the following data types:
    add(target: Object, propName:string, status: boolean): GUIController;     add(target: Object, propName:string, items:string[]): GUIController;     add(target: Object, propName:string, items:number[]): GUIController;     add(target: Object, propName:string, items:Object): GUIController;
Otherwise this seems misleading to specify that this function supports number arrays.
Refactoring this to use something else could even allow other types that can be represented as strings for the sake of the interface but reference any object type so that every case where someone want to use a list of non-string objects doesn't require onChange reverse lookup style re-parsing...

Was this intended to be a breaking change, though?
I was fine with coercing the values from the select back to Numbers, but in the latest version my numeric selects don't render an input or a select at all. I just get an empty field in my GUI.
For example, this used to work:
gui.add(context, "lightSize", { sm: 30, md: 50, lg: 80, xl: 110 })

But now it only renders a label. It seems like it could at least try to render those values for me, but I can also see how it might be more confusing to put in a number and get a string back. 🤔

@geekytime There was no change to this functionality. It still has it's intended behaviour.
Your code seems to be working fine in dat.gui version 0.7.6: https://jsfiddle.net/L2akrcwd/
Check your console for any errors in your code.

Hah! I didn't have any errors in my console, but after comparing my example to your fiddle, I discovered that the select element is rendering, but it's somehow inheriting the background-color from the gui control panel in my app, so it's essentially invisible. 🤔
I didn't change anything other than my version of dat-gui, so I'm not sure what's going on, but it doesn't appear to be related to the number parsing. Sorry for the confusion.

I was also stumped for a little while on how to elegantly solve this issue. The following function worked for me:
function toNumber(value) {
    this.object[this.property] = Number(value);
}

gui.add(obj, "name", { Zero: 0, One: 1 }).onChange(toNumber);

I do think that it would be good to mention this constraint (and perhaps provide alternative solutions such as the above function) somewhere in the documentation.


Add timestamps to queryid and cookie tables to allow purging old records

Since we now store query IDs in a DB, we need a way to clean them up. This PR adds timestamps so that we can decide which ones are safe to delete.

Related to the question posed in the other PR... how does purging work? Is there a separate process that checks the timestamps and if they are older than some delta, they are removed? Just curious.

LGTM


No use in declaring static final methods. Removing final keyword

Coverage decreased (-0.01%) to 46.36% when pulling cd5dc27d543a179e40c16c549fda99e0e3a8a9c8 on jitsni:cleanup into c6c021931b633866fbdf2415f16cdaec00cfce3c on kaazing:develop.


Process didn't exit successfully

Description

rustc 1.67.1 (d5a82bbd2 2023-02-07)
Microsoft Windows 10.0.19044.2604
Reproduction

just clone and cargo run get

Try
Try to comment out the following code, then cargo run works
https://github.com/sindresorhus/win-wallpaper/blob/b55c6f6c20d629627d215d43836f9e8eed2547c2/src/lib.rs#L142
I am not good at Rust or C++,  so I try to fix this by the post.

// @a-isaiahharvey


Update Apple Music Extension

Extension
https://www.raycast.com/fedevitaledev/music
Description
Design the extension to resemble the style of Spotify's extension.
Who will benefit from this feature?
Every extension user
Anything else?

can't be done due to api limitations 😅

@raycastbot close this issue


⚠ ClamAV has degraded performance

In 3f21c2a, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 70 ms

Resolved: ClamAV performance has improved in 46eef5b.


Fix https://github.com/nrc/rustfmt/issues/376

Could you add a test please?

Some tests already exist in tests/target/paths.rs, this PR is just a refactor to use ast::Ty::rewrite.

Thanks! Except for the tiny nit, this is ready to merge.


Add initial version of in-source documentation

JerryScript-DCO-1.0-Signed-off-by: Evgeny Gavrin<EMAIL_ADDRESS>If you have any suggestions please feel free to propose enhancements.

+1

Looks good to me

@zherczeg @galpeter could you please check this?

@galpeter @zherczeg @LaszloLango may I merge this?

I have no objection to merge this. +1 lgtm

Thank you!


Select custom toolchain

Problem you are trying to solve
Currently, it is not possible to use for instance a default and a custom toolchain together.
Which means that I can only have one co-exist at a time, which is really not practical.
Solution you'd like
I would like to be able to do something like:

fuelup toolchain latest  when I want to use the latest toolchain
fuelup toolchain mine when I want to use my custom toolchain named mine.

Notes
No response

@iqdecay  I'm not sure I understand what you're trying to do. Is this different from switching the default toolchain? e.g.
fuelup default latest
fuelup default mine


Change the logging scope from 'admin' to 'write' for GCL driver.

Updated the log file name to 'kubernetes.io/events'

I tested this manually with just write scope enabled for logging and it works.

LGTM


fix job.emit stringify on circular objects

Hi there,
I've run into this issue when cascading using async module and returning a job to the callback of a job processing.
As jobs are circular, that had the effect of completely crashing my app.
Here's a proposal to avoid crashing, using try/catch, performances might get slightly affected although it is already used here (https://github.com/Automattic/kue/blob/master/lib/queue/worker.js#L178-L183).
Provided tests should fail if this patch to events.js is not applied.
Tell me what you think.
Cheers!

I can't merge this until all tests pass @risseraka

Woops, indeed, will take a look, thanks.

@behrad here you are, all green!
Issue was pretty sly and took some time to spot where it came from.
I've added comment to test/test_mode.js as a reminder.
https://github.com/Automattic/kue/pull/745/files#diff-220e5536ec8a442ca27c544ae735ae6eR5
Cheers.

and one thing else: Silently skipping user's data sounds no good idea. it causes user miss-conception on their side, if we want to omit circular data, we should add some clue/note about that either in documentation or in event's arguments in code

closing since it gets old enough


improvements to 'from_orm' to work better with root validators

Fix #821
Change Summary

add getter_dict to Config
modify GetterDict to be a proper Mapping object and thus easier to work with
add tests demonstrating usage of getter_dict and root_validator(pre=True) for ORM decomposition

Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.rst file added describing change
(see changes/README.md for details)

This looks great! Thanks for implementing this!

This looks great, I think it'd definitely solve my current issue related to #380 - would love to see it merged.

I just wanted to verify this would fix the issue I'm encountering and it does seem to do so - I've added a test case to a fork to demonstrate, you're welcome to include it if you think it's any use:
https://github.com/bharling/pydantic/commit/09cd0fdd81fb3584fcb367513afed32285027419
Was mainly just to check that the _decompose_class function is called properly in derived classes and the correct getter_dict is returned.


fix(app): use correct module order to get usb port

Overview
The Multiples of a Module feature relies on following the prescribed order of the modules called in a protocol.
The protocol modules are currently sorted by the slot number when matching to the physical modules on the client side, which does not match the backend work implemented in #7532. This PR fixes that.

Changelog

added getModulesByProtocolLoadOrder to ApiSessionModules
use the new selector in getMatchedModules
removed unused declaration in the getModules selector

Review requests
Upload a protocol with multiple modules of the same type, and verify that the one plugged in to the lower port number is actually the first loaded module.

Risk assessment
Low, very small changes and the moam feature is not released yet so no user should be affected by this.

I tested on my robot with multiple modules of the same kind and the behavior was correct for me.


Use semantic version in order to create new versions

Is your feature request related to a problem? If so, please describe.
Actually we are using SemVer when creating tags, but it's necessary to automatize this specially on Pull Request.
What feature or improvement would you like to see?
Use this Action: https://github.com/PaulHatch/semantic-version
Additional context
No response

Closing due high complexity


Cannot deploy to multiple servers with same hostname

With the following configuration:
server 'web.example.com', user: 'deploy', roles: %w{web app db}, port: 2201
server 'web.example.com', user: 'deploy', roles: %w{web app db}, port: 2202
Capistrano only runs on a single machine. Is it possible to do what I want with the current setup?
Cheers

#1368 successfully ressurects this issue.
What should I do in the case of
server '<IP_ADDRESS>', user: 'user', port: '12345', roles: %w[ web ], no_release: true
server '<IP_ADDRESS>', user: 'user', port: '12346', roles: %w[ app db web ]
server '<IP_ADDRESS>', user: 'user', port: '12347', roles: %w[ app web ]

cap stage deploy:check does absolutely nothing (as I have understand all servers goes merged into one with :no_release option as it is implemented in #1368).
Naming these servers with different names in ~/.ssh/config helps.
Is there any way to avoid merging these servers into single one without ~/.ssh/config edits?

@leehambley what if we could add merge: false option to the server DSL to solve the issue described by @Envek?

I'm really not in favour of that, since I honestly think that the project-local SSH config is enough, since it goes along with the project in the SCM repository… but it seems whatever we do with the server merging, it's wrong in some cases for some people, but when we take a hash of server properties and we then also take some behavioural options in the same hash, with keys with special meanings, I suspect we might make the API worse.

Aside from downgrading to 3.3.5, is there a workaround for if I have two servers that share the same host, but have different ports? I.e. if port forwarding is being used to share one domain between two servers. @townsen

Mike, as a workaround you can set up two different hosts with the same
hostname in the .ssh/config file.
On Wednesday, May 6, 2015, Mike Stewart<EMAIL_ADDRESS>wrote:

Aside from downgrading to 3.3.5, is there a workaround for if I have two
servers that share the same host, but have different ports? I.e. if port
forwarding is being used to share one domain between two servers. @townsen
https://github.com/townsen
—
Reply to this email directly or view it on GitHub
https://github.com/capistrano/capistrano/issues/784#issuecomment-99332052
.

It's not a workaround, and you can see it documented here, https://github.com/capistrano/sshkit#tunneling-and-other-related-ssh-themes you can also commit an ssh config to your repository and we'll honour it.

also @mike-stewart I'll extend you the same offer as in the other open issue about host identity, provide test cases for your intended use-cases, and we'll work with you to get the tests up to scratch and get your desired behaviour in, if we have unclear, untested cases, it's a perfect opportunity to plant your flag and make an impression on how you would like it to work, our test suite is very approachable, especially the unit tests.

Here's the failing spec
# spec/integration/dsl_spec_failing.rb

require 'spec_helper'

describe Capistrano::DSL do

  let(:dsl) { Class.new.extend Capistrano::DSL }

  before do
    Capistrano::Configuration.reset!
  end

  describe 'when defining two servers on same host' do
    before do
      dsl.server 'user_a@example.com:1234', roles: %w(app)
      dsl.server 'user_b@example.com:5678', roles: %w(web)
    end

    it 'can fetch the first server' do
       hosts = dsl.roles(:app).map { |server| "#{server.user}@#{server.hostname}:#{server.port}" }
       expect(hosts[0]).to eq 'user_a@example.com:1234'
    end

    it 'can fetch the second server' do
      hosts = dsl.roles(:web).map { |server| "#{server.user}@#{server.hostname}:#{server.port}" }
      expect(hosts[0]).to eq 'user_b@example.com:5678'
    end
  end
end

I'm trying to do the same thing using docker containers locally and am having the same issue. While the .ssh/config option works, I think working out this issue is worth it. The reason being to reduce the required steps for setting up an environment. With docker you basically can get your setup down to one command, except for a few configuration options. This would be another additional option that would have be documented and explained to developers.

@pwaterz Since this issue is closed, can we move this discussion to #1427? I believe #1427 is the same problem.

SSHKit and hence Capistrano will pick up a .ssh/config file checked into
your project for cases such as this.
(Sent from my Nexus 6, please forgive typos!)
On Oct 13, 2016 02:26, "Matt Brictson"<EMAIL_ADDRESS>wrote:

@pwaterz https://github.com/pwaterz Since this issue is closed, can we
move this discussion to #1427
https://github.com/capistrano/capistrano/issues/1427? I believe #1427
https://github.com/capistrano/capistrano/issues/1427 is the same
problem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/capistrano/capistrano/issues/784#issuecomment-253377549,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABKCKROY3l7GcOXSRTZpwMgX_-3mu_wks5qzXq2gaJpZM4BNokv
.


Implement class for handling HI tables

I foresee something along the lines of:
Create pymds/antigenic.py with:
class Table(object):

    def __init___(self, table_data):
        self.dm = make_distance_matrix(table_data)

Where make_distance_matrix returns an instance of pymds.mds.DistanceMatrix

Hi @davipatti
This feature would be very useful.
For example, the exact way the table h3map2004_hitable.csv is preprocessed, and returns similar-looking map as shown:
Example map in Racmacs
If the bandwidth now allowing, would you please tell me the exact preprocessing steps to reproduce the map like above?
Thanks.
Best,
Hansaim

Just to add to my comment above, I tried to convert the h3map2004_hitable.csv into distance matrix and visualized using pymds. The results look like something is wrong.
It's perhaps due to some missing steps in the preprocessing, so the above functionality is indeed necessary to use pymds.
example_distance_file = './h3map2004_hitable.csv'
censored_distance_value = 1.0  # +- directly to the distance
missing_value = 0  # for non-metric MDS -- 0s considered missing value
zero_distance = 1e-6  # nonzero value to replace known 0s
minimum_column_basis = 6.0
missing_value_indicators = ['*', '-', 'NA', 'Unknown']
serum_values = defaultdict(list)
with open(example_distance_file, mode='r') as inf:
    lines = csv.reader(inf)
    antisera = next(lines)
    if antisera[0] == '':
        antisera = antisera[1:]
    antigens = []
    antigen2titers = {}
    for line in lines:
        if len(line) == 0:
            continue
        antigen = line[0].strip()
        antigens.append(antigen)
        titers = line[1:]
        for idx,t in enumerate(titers):
            ## should never skip a value in this loop
            # at this point, titer values
            serum = antisera[idx]
            if t in missing_value_indicators:
                t = missing_value
            elif '>' in t:
                pass
            elif '<' in t:
                pass
            else:
                #known, uncensored, valid titer
                t = float(t)
                serum_values[serum].append(t)  # to be used for column basis -- only valid titers
            titers[idx] = t

        antigen2titers[antigen] = titers  # all titers for each antigen - censored titers stay censored
    column_bases = {s:np.nanmax(serum_values[s]) for s in serum_values}
    submatrix = np.zeros((len(antigens), len(antisera)))
    for row_idx, antigen in enumerate(antigens):
        row = []  # cleaned, distances
        for col_idx, t in enumerate(antigen2titers[antigen]):
            col_basis = column_bases.get(antisera[col_idx], minimum_column_basis)
            if t == missing_value:
                dist = t
            elif '>' in str(t):
                # titer greater than x
                # distance shorter than log(x)
                t = float(t[1:])
                dist = (np.log2(col_basis) - np.log2(t)) - censored_distance_value  # for censored >x data
                if dist < zero_distance:
                    dist = zero_distance
            elif '<' in str(t):
                t = float(t[1:])
                dist = (np.log2(col_basis) - np.log2(t)) + censored_distance_value # for censored <x data
                if dist < zero_distance:
                    dist = zero_distance
            else:
                dist = np.log2(col_basis) - np.log2(t)
                if dist < zero_distance:
                    dist = zero_distance
            row.append(dist)
        submatrix[row_idx,:] = row
    # print(submatrix.shape)
    # print(len(antigens), len(antisera))

    antigens_antisera = antigens+antisera
    matrix = np.zeros((len(antigens_antisera), len(antigens_antisera)))
    matrix[0:len(antigens), len(antigens):] = submatrix
    matrix[len(antigens):, 0:len(antigens)] = submatrix.T

original = DistanceMatrix(matrix).optimize(n=2)
shrunk = DistanceMatrix(matrix*0.65).optimize(n=2)
original.plot(c='black', edgecolor='white', s=50)
original.plot_lines_to(shrunk, linewidths=0.5, colors='black')


add analysis to umbrella_pipeline

Description
Provide a brief description of the PR's purpose here.
Todos
Notable points that this PR has either accomplished or will accomplish.

[ ] TODO 1

Questions

[ ] Question1

Status

[ ] Ready to go

Codecov Report

Merging #19 (3303d71) into main (aa6b976) will decrease coverage by 0.33%.
The diff coverage is 60.00%.


Fix ListBox (grid layout) keyboard navigation TypeError

Closes https://github.com/adobe/react-spectrum/issues/6168
While fixing the bug, I've noticed a horizontal grid ListBox also has the same issue when navigating left and right via keyboard ('arrowLeft' and 'arrowRight'). Included unit test covers both cases.
By the way, these bugs can be seen in the docs as well

https://react-spectrum.adobe.com/react-aria/ListBox.html#vertical-grid
https://react-spectrum.adobe.com/react-aria/ListBox.html#horizontal-grid

✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[x] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[x] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:
Story

http://localhost:9003/?path=/story/react-aria-components--list-box-grid

🧢 Your Project:

GET_BUILD

By the way, these bugs can be seen in the docs as well

I'm unable to see this happening in the docs. Anything I need to do other than:

tab to example
arrow key off the side in any direction

GET_BUILD


Need Transparent Bg

Hi,
I working with your lib. it looks good UI, but I have several doubts. kindly help me. Thanks in advance.

when I run with iOS 12.1 I didn't get the shadow of your tab bar, but I gotta shadow in 12.
How I can remove that background I need transparent, once that tab bar and circle. I will attach a screenshot for ur reference.
Animation when I select tab bar I icon move's top first and then circle move to the index. I need to do move both at the same time.

kindly do needfully

Hey,
first of all: have you modified the code or use it as it is?
1.: In general there are now shadows (see also my example screenshoot). Are you sure that you don't have set a shadow by yourself? Can you provide your code that I can check that?
2. Simply set the BackgroundColor of the TabBar to Transparent. In general it has it per default. Again: could you provide your code? There is no shadow/background in the demo.
3.: The duration of the "hide" animation and their duration is here:
https://github.com/v-braun/VBRRollingPit/blob/cb2a709e7dadeecd85526b181b7014166f57a11d/VBRRollingPit/VBRRollingPit/RollingPitTabBar.swift#L237
the roll animation is here:
https://github.com/v-braun/VBRRollingPit/blob/cb2a709e7dadeecd85526b181b7014166f57a11d/VBRRollingPit/VBRRollingPit/RollingPitTabBar.swift#L247
simply adjust these two values.

How to reduce the animation of move circle?

close because of inactivity

Hey @v-braun , same issue here. Your RollingPitTabBar also includes the portion covered in the red rectangle of the above screenshot. So basically if we add a view(like tableview in screenshot) inside the viewcontroller, we can see a blank space from the bottom of the view to the tabbar.

Hey @v-braun , same issue here. Your RollingPitTabBar also includes the portion covered in the red rectangle of the above screenshot. So basically if we add a view(like tableview in screenshot) inside the viewcontroller, we can see a blank space from the bottom of the view to the tabbar.

RollingPit.zip
Hi hello,
herewith I added sample projects kindly check it once.

@syedrazackimran & @hamedazhar
the BG is transparent. You have a View (on root level) with a grey Baground and your CollectionView has constraints that say they should be within the safearea of that view.
Looks for me that you use a ViewController instead of a CollectionViewController to represent your data.
See the screenshoot and compare the view hierarchies.
"Item Scene" works as expected because the collection view is expanded over the entire screen (and is also behind the TabBar).


spark/databricks execution error AttributeError: 'NoneType' object has no attribute 'sql'

Environment:
$ poetry show | grep soda                                                                                [10:26:29]
soda-core                              3.0.38        Soda Core library & CLI
soda-core-spark                        3.0.38
soda-core-spark-df                     3.0.38

Configuration (specifics redacted):
data_source databricks:
  type: spark_df
  catalog: spark_catalog
  schema: <schema>
  method: databricks
  host: ${DATABRICKS_HOST}
  http_path: <http_path>
  token: ${DATABRICKS_TOKEN}

Check file:
checks for
:
  - row_count > 0:
      name: The table is not empty
  - missing_count(column_name) = 0:
      name: Ensure there are no null values in the column_name column

I'm running the following command:
poetry run soda scan -V -d databricks -c soda/config/databricks.yml soda/checks/
/check.yml

And I'm getting the following error:
[10:30:27] Soda Core 3.0.38
[10:30:27] Reading configuration file "soda/config/databricks.yml"
[10:30:27] Reading SodaCL file "soda/checks/
/check.yml"
[10:30:27] Scan execution starts
[10:30:27] Query databricks.
.aggregation[0]:
SELECT
  COUNT(*),
  COUNT(CASE WHEN <column_name> IS NULL THEN 1 END)
FROM <schema>.

[10:30:27] Query execution error in databricks.
.aggregation[0]: 'NoneType' object has no attribute 'sql'
SELECT
  COUNT(*),
  COUNT(CASE WHEN column_name IS NULL THEN 1 END)
FROM <schema>.

  | 'NoneType' object has no attribute 'sql'
  | Stacktrace:
  | Traceback (most recent call last):
  |   File "<path>/.venv/lib/python3.10/site-packages/soda/execution/query/query.py", line 122, in fetchone
  |     cursor.execute(self.sql)
  |   File "<path>/.venv/lib/python3.10/site-packages/soda/data_sources/spark_df_cursor.py", line 15, in execute
  |     self.df = self.spark_session.sql(sqlQuery=sql)
  | AttributeError: 'NoneType' object has no attribute 'sql'

[10:30:27] Metrics 'row_count' were not computed for check 'row_count > 0'
[10:30:27] Metrics 'missing_count' were not computed for check 'missing_count(column_name) = 0'
[10:30:27] Scan summary:
[10:30:27] 1/1 query ERROR
[10:30:27]   databricks.
.aggregation[0] [ERROR] 0:00:00.000738
SELECT
  COUNT(*),
  COUNT(CASE WHEN column_name IS NULL THEN 1 END)
FROM <schema>.

[10:30:27]     'NoneType' object has no attribute 'sql'
[10:30:27] 2/2 checks NOT EVALUATED:
[10:30:27]
 in databricks
[10:30:27]       The table is not empty [soda/checks/
/check.yml] [NOT EVALUATED]
[10:30:27]         check_value: None
[10:30:27]       Ensure there are no null values in the column_name column [soda/checks/
/check.yml] [NOT EVALUATED]
[10:30:27]         check_value: None
[10:30:27] 2 checks not evaluated.
[10:30:27] 3 errors.
[10:30:27] Oops! 3 errors. 0 failures. 0 warnings. 0 pass.
ERRORS:
[10:30:27] Query execution error in databricks.
.aggregation[0]: 'NoneType' object has no attribute 'sql'
SELECT
  COUNT(*),
  COUNT(CASE WHEN column_name IS NULL THEN 1 END)
FROM <schema>.

  | 'NoneType' object has no attribute 'sql'
  | Stacktrace:
  | Traceback (most recent call last):
  |   File "<path>/.venv/lib/python3.10/site-packages/soda/execution/query/query.py", line 122, in fetchone
  |     cursor.execute(self.sql)
  |   File "<path>/.venv/lib/python3.10/site-packages/soda/data_sources/spark_df_cursor.py", line 15, in execute
  |     self.df = self.spark_session.sql(sqlQuery=sql)
  | AttributeError: 'NoneType' object has no attribute 'sql'

[10:30:27] Metrics 'row_count' were not computed for check 'row_count > 0'
[10:30:27] Metrics 'missing_count' were not computed for check 'missing_count(column_name) = 0'

After doing some debugging it looks like the SparkDfCursor object is not being initialized properly. The spark_session object is coming in None which is causing the error here.
Is this a bug or is there something wrong with my configuration (user error)?

SODA-1742

Hey @drsnyder spark_df type with python/pyspark. Can you try specifying the type: spark  - please see https://docs.soda.io/soda/connect-spark.html#connect-to-spark-for-databricks-sql

Hey @drsnyder spark_df type with python/pyspark. Can you try specifying the type: spark - please see https://docs.soda.io/soda/connect-spark.html#connect-to-spark-for-databricks-sql

If I use type: spark the client is unable to connect to the databricks server.
[11:04:13] Could not connect to data source "databricks": Encountered a problem while trying to connect to spark: Error during request to server
  | Encountered a problem while trying to connect to spark: Error during request to server

I'm not sure if it's related but the code seems to suggest that spark_df is the expected value. I've also tried using soda directly in a databricks notebook and in that context the following fails:
scan = Scan()
scan.set_scan_definition_name("test")
scan.set_data_source_name(f"spark") # <---
scan.add_spark_session(spark)

But changing the 3rd line to scan.set_data_source_name(f"spark_df") works.

If you are using with Python/Notebook then indeed you should use spark_df, the spark type is for connecting to Databricks via Databricks spark connector.

If you are using with Python/Notebook then indeed you should use spark_df, the spark type is for connecting to Databricks via Databricks spark connector.

That doesn't work for me inside databricks. As mentioned above, I have to use "spark".
This specific issue is separate-- I'm trying to use soda from the command line to validate a table in databricks. It could be that I'm doing something wrong with the configuration (help!). There could also be an issue with the code.


Govinfo Parser

Can you rebase into one commit?
https://stackoverflow.com/questions/6884022/collapsing-a-group-of-commits-into-one-on-git
You need to remove the APIKEY so it's not publicly googleable by hackers.
Put it into the api_key.yaml and copy the same I/O from parsers/yahoo_fin/yahoo_fin.py
Do not upload CSVs of actual data -- github is not the place to store them -- we will upload them into Drive for now.


fix: add wheel command to not generate output

Closes #28

Hello,
I tried to add a test but I have trouble making the test suite work locally. Not sure if I miss some dependencies.

To test the CLI entrypoints, you would need to use typer.testing.CliRunner.
There are some examples in Pyodide repository, which might be helpful to you. If you find it difficult to write tests, let us know. I think we can merge this PR and add some tests later.

I gave it a try: https://github.com/pyodide/pyodide-lock/actions/runs/9431128434/job/26020165688?pr=29
But it is not clear to me why the test fails at this point. If you have any input would be grateful, otherwise I try to have a look in the following days.

But it is not clear to me why the test fails at this point.

It's becuase that function has a decorator @main.command(), and typer converts the function internally to make it work as a CLI entrypoint. Calling the typer-decorated function directly will not work as expected. Could you take a look at the link that I provided?


Detect cyclical light chains

I don't want to admit how much time I spent pounding my head against the keyboard trying to figure out why my game kept hanging on bootup without any logs or errors.
Suffice it to say, here's a PR that detects when a light chain of previous: declarations creates an infinite loop and lets the user know where the infinite loop is :)

LGTM!


Remove support-v13 dependency

Currently there's only one usage of the v13 support library which can be achieved with v4.
This saves pulling another dependency with ~200 referenced methods and fixes recent issues of unmatching support library versions, because v13 is rarely included in projects.

when release a new version for this fix?


Deserialise meta into metadata in 0.6 deserialiser

This fixes the bug that is worked around in https://github.com/apiaryio/Paw-APIBlueprintImporter/blob/568d73e44bdff23495c24fb3f4b5cd2d1cc8025a/src/APIElementImporter.js#L8 and is also causing documentation team problems.
Meta will be correct deserialised in 0.6 as metadata as an object element with this fix.

@kylef after upgrading we see a change the meta.toValue() contents:
<EMAIL_ADDRESS>element.attributes.get('meta').toValue():
[
  {
    "key": "FORMAT",
    "value": "1A"
  },
  {
    "key": "HOST",
    "value": "https://localhost/"
  }
]

<EMAIL_ADDRESS>element.attributes.get('metadata').toValue():
{
  "FORMAT": "1A",
  "HOST": "https://localhost/"
}


feat: relative differentials as a presheaf of modules

In this PR, we define the type M.Derivation φ of derivations with values in a presheaf of R-modules M relative to
a morphism of φ : S ⟶ F.op ⋙ R of presheaves of commutative rings over categories C and D that are related by a functor F : C ⥤ D. In the particular case F is the identity functor, we construct the universal derivation.

[x] depends on: #14030

This is a refactor of #11570

Thanks :tada:
bors merge


Point graphic not showing

I have a problem, when I generate my release apk the points doesn't show on map. Any help??

I also got same error

But I found the solution.
If you use the online image for the pointer, it will work.

What do you mean online image?


Remove modifications on the default privileged SCC.

Since we already have dedicated SCC for each of the relevant components we don't need to modify the default privileged SCC anymore.
Signed-off-by: Igor Bezukh<EMAIL_ADDRESS>What this PR does / why we need it:
We want to mitigate upgrade issues of the underlying provider such as OCP.
Further discussion can be found here:
http://post-office.corp.redhat.com/archives/cnv-devel/2020-April/msg00105.html
Which issue(s) this PR fixes
https://bugzilla.redhat.com/show_bug.cgi?id=1831536
Release note:
None

/assign @davidvossel

/assign @stu-gott

Do we want to undo adding our users too? Because if yes, I think that you have to keep this code, and ensure that ServiceAccounts is empty, so that we remove our modification.

Hey, so what happens is new install strategies no longer involve adding any users to the privileged SCC... That's what this PR removes from the install strategy.
However, the strategy.customSCCPrivileges field is still a part of the installstrategy API. meaning it's still interpreted as part up updates for adding/removing users.
This means when updating, the old install strategy that sets users on privileged SCC is taken into account. So old modifications are removed from the privileged SCC during the update and we proceed with the new way of generating our own unique SCCs instead.

/lgtm

@enp0s3  can we get confirmation on ocp update testing so we can remove the hold? thanks

#> @enp0s3 can we get confirmation on ocp update testing so we can remove the hold? thanks
I can confirm that the update test passed on a OCP+KV setup.

/hold cancel

/lgtm

/override pull-kubevirt-e2e-k8s-1.17
failing test is known and being addressed separately

/cherry-pick release-0.30


CI for Avalanche

The CI generates each day with the new master the following targets:

x86_64 Linux
x86_64 Windows
x86_64 MacOS
The haswell version of the above
Aarch64 MacOS
m1 Specific MacOS

Looks great, thanks very much :))


[Bug]: Auto Height for container widget is not working as expected

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The container fails to expand in preview mode when hidden table is visible.
Steps To Reproduce

Create a container
Add a button to facilitate the visibility toggle using storeValue
Add a table and set its visibility based on the above toggle
Go to preview mode observer how container doesn't expand even if the table is in visible state.

Caveat - I couldn't reproduce this issue on a brand-new app. Although, I produced this in an old app by creating a new page
Public Sample App
No response
Environment
Production
Issue video log
https://www.loom.com/share/93781c74dd914e5e82cee26d8e78b58b
Version
v1.9.15
 Front conversations

same issue!

Steps To Reproduce

Create a container
Add list widget
Add image below list widget
set visible list = false
Go to preview mode and see the image still in bottom of container

I think the reason is old app misses config collapseInvisibleWidgets.
https://github.com/appsmithorg/appsmith/pull/20118/files#diff-5213fb244bf59ac26b2b2310ac284bc69b4c811b39b8fe1557b04bfc7adf9374R30

this is a non-issue on anvil layout system hence closing it


feat: Support and test Sentry.sendFeedback

Closes #834
This PR ensures that feedback can be sent from the renderer process and adds a test to ensure the envelopes correctly get passed through the main process.

Also as a headsup, we're looking at consolidating captureUserFeedback with sendFeedback (and likely killing the latter API) for v8

we're looking at consolidating captureUserFeedback with sendFeedback

Yep no problem, will update all these tests when it happens.
I think the main difference (in features/behaviour at least!) is that sendFeedback doesn't have a way to attach a related event id?

I think the main difference (in features/behaviour at least!) is that sendFeedback doesn't have a way to attach a related event id?

Yep exactly


ListView - reordering items with drag n drop

It is suprised that this common and important feature still has not been officially supported by Xamarin Forms: https://github.com/xamarin/Xamarin.Forms/issues/4676
Is there any chance that Fabulous will support this feature? It is fine if iOS and Android are targeted.

@katatunix Unfortunately, Fabulous is not meant to add features missing in Xamarin.Forms.
We only provide wrappers over existing GUI frameworks like Xamarin.Forms so they can be used in a functional way with the MVU pattern.
For missing features, I recommend you look at 3rd party libraries such as SyncFusion, Telerik and others.

Closing since this is a feature request for Xamarin.Forms but Fabulous is not meant to compensate missing features of Xamarin.Forms.


Link under these steps seemed broken

edited the link and added https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/storage/common/storage-explorer-troubleshooting.md#Mac-Keychain-Errors

@DiegoRamirez-MSFT : Thanks for your contribution! The author, @Deland-Han, has been notified to review your proposed change.


[BUG] Run with CLI

Example
javascript-obfuscator index.js --config config.json # work

javascript-obfuscator --config config.json  index.js # error
# return: ReferenceError: Given input path must be a valid `.js` file or directory path

Expects
file what would be obfuscated should be parse fine. Flags, like --config or any else (like -o or --output and etc) shouldn't destroy command run if flags would be placed before js file.

Hi. Hm. Currently i got the file path here:
https://github.com/javascript-obfuscator/javascript-obfuscator/blob/master/src/cli/JavaScriptObfuscatorCLI.ts#L140
Maybe I can change the logic to parse arguments and detect argument with the input file path

Will fix it today. PR is almost ready.

Released as 2.11.1


Use Dockerfile to build the image

Hi. Usually most Docker images are built using a Dockerfile. It would be nice if either -

The supabase/postgres image could also be built via a Dockerfile, thereby simplifying the build process

or

The readme could be updated to educate users like me about the reason for choosing ansible over a Dockerfile.

Sorry no one got back to you on this
We have recently revamped our docker build and are in the process of documenting all the changes.
In the short term you can build the docker image locally like this:
docker build -f Dockerfile-156 -t supa-15-6 .

better docs to follow


Decorative Star space missing from website?

Was using the editor earlier in the day and had access to the decorative star space which I was using for a project, but not it's not a selectable space type? Did this addition get chopped? Thanks for reading!

Additional kinds of spaces will appear only when the Advanced features is checked on the settings page.


Support coming for FontAwesome v5.13.1

Just letting everyone know, as of this moment I'm having some issues updating master because of a cli-swift issue.
Support is coming for the latest FontAwesome icons, as soon as I get this figured out. Thank you all for your patience

In case it helps, the script works with tools that are a bit older, I have Xcode 11.5 (11E608c) installed and it runs for me.  However, I'm trying to generate all of the Pro fonts and it seems to be missing the duotones and light fonts completely.  I turned on "Use Pro Fonts", do you have any other tips for generating ALL of the Pro fonts?  Thank you!

FYI, I got much further with the swift CLI script running by renaming /Library/Developer/CommandLineTools and then performing a sudo xcode-select --install.  Now the script compiles and tries to run, but I get a segmentation fault that I am trying to debug.

Ensure that you've installed the submodule. There's a lot of force-unwrapping optionals in there, especially when it comes to decoding and reading the metadata file.
To install with pro fonts, you'll need to replace the FortAwesome/FontAwesome submodule with the FortAwesome/FontAwesome-Pro submodule, and change the path inside the script

I got the cli-swift file to run properly on one of the developer preview Macs!

Is duotone supported?  It looks like I only see 1 of the colors.

duotone is not currently supported. I am debating how to show them, and whether to allow them in UILabels. Ligatures and SVGs are the two paths that seem readily available, but i'm not sure if either is the right choice. For now, I am closing all PRs related to them

I created a SwiftUI "demo" app for viewing the FontAwesome images...  FontAwesome.SwiftUI.demo

any ETA?

Still working on a few things with the next version. Updated font support will be bundled in. If you need it in the meantime, you can manually add the library and update the font. You can still add it into your pod file, just ensure that it is pointed towards the local path and not the git repository. See more here

5.15.1 is the current version, hope that when you do find the time to upgrade, you can upgrade to the newest version :)

Updating right now. Had to fix some shit with swift giving me the runaround. small changes to how things are done under the hood, but no changes to any of the core library or the release process

07883a32d49dfc7bdedbeea115067b53dfbeeb43 pushed to master and CP, closing

As a note, @thii I was having issues specifically with the ./codegen.swift command. I was getting "This copy of libswiftCore.dylib requires an OS version prior to 10.14.4." I couldn't figure out what was causing it, and since I'm loathe to roll back to a previous version of Xcode, I just went ahead and added an executable target in the Package.swift and changed ./codegen.swift -> swift run tools. codegen.swift got changed to ROOT/tools/main.swift

Looks like a prolem with your machine's installed Swift runtime.

It might very well be. I don't have a lot of space so I also only have one version of Xcode/swift installed atm. I'm working on getting CI to take care of bumps for us atm


ubuntukylin 安装，启动报如下错误，不能启动

<EMAIL_ADDRESS>start /home/leonis/source/electronic-wechat
electron src/main.js

No protocol specified
npm ERR! Linux 4.4.0-21-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `electron src/main.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'electron src/main.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the electronic-wechat package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     electron src/main.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs electronic-wechat
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls electronic-wechat
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/leonis/source/electronic-wechat/npm-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prestart, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/home/leonis/source/electronic-wechat/node_modules/.bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/leonis/source/electronic-wechat
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'electron src/main.js' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
14 verbose stack Error<EMAIL_ADDRESS>start: `electron src/main.js`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:239:16)
14 verbose stack     at emitTwo (events.js:100:13)
14 verbose stack     at EventEmitter.emit (events.js:185:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:100:13)
14 verbose stack     at ChildProcess.emit (events.js:185:7)
14 verbose stack     at maybeClose (internal/child_process.js:850:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /home/leonis/source/electronic-wechat
17 error Linux 4.4.0-21-generic
18 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
19 error node v5.10.1
20 error npm  v3.8.3
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>start: `electron src/main.js`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>start script 'electron src/main.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the electronic-wechat package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     electron src/main.js
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs electronic-wechat
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls electronic-wechat
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

@vinartis 确保你的electron版本是最新v0.37.6，有API改动。


egressgw: reject config with EnableIPv4Masquerade false

Currently, the condition check in the egw cell code is not strict enough. EGW doesn't work with EnableIPv4Masquerade false, but it doesn't reject that config if EnableIPv6Masquerade is true.
This commit rejects that invalidated config.

/test


Export Models

Summary by CodeRabbit

New Features

Introduced a new search functionality for accounting exports, errors, and summaries.
Added ability to update accounting export summaries with counts of failed and successful exports.
Implemented a new AccountingDataExporter class for exporting data to external accounting systems.
Added new models for journal entries, line items, and purchase invoices with creation and update capabilities.
Added a new URL path for triggering exports within a workspace.
Enhanced expense management with the introduction of ExpenseFilter and Expense models.

Improvements

Updated TYPE_CHOICES to reflect more accurate accounting export types.
Improved error and exception handling for business central operations.
Enhanced the export process with new functions and classes for journal entries and purchase invoices.
Added new utility methods for better integration with Fyle and Business Central.
Improved workspace model with additional fields and updated export mode choices.
Updated requirements.txt with newer versions of dependencies for better performance and stability.

Bug Fixes

Fixed an issue with expense object creation to ensure proper association with accounting exports.

Documentation

Updated documentation to reflect new features and improvements in accounting exports and workspace management.

Refactor

Reorganized code related to expense import and synchronization for better maintainability.
Cleaned up import statements and removed unused imports across various files.

Style

Modified code styling for consistency and readability in models and utility files.

Chores

Performed routine codebase maintenance tasks to keep the application up-to-date.

Codecov Report
Attention: 282 lines in your changes are missing coverage. Please review.

Comparison is base (9d2d9bc) 90.96% compared to head (f3b5841) 82.81%.

Files
Patch %
Lines

apps/workspaces/tasks.py
14.63%
70 Missing :warning:

apps/business_central/exceptions.py
28.07%
41 Missing :warning:

apps/business_central/exports/helpers.py
30.00%
35 Missing :warning:

apps/business_central/exports/base_model.py
35.41%
31 Missing :warning:

apps/business_central/exports/accounting_export.py
30.76%
27 Missing :warning:

...ps/business_central/exports/journal_entry/tasks.py
42.10%
22 Missing :warning:

...s/business_central/exports/journal_entry/models.py
64.00%
18 Missing :warning:

...s/business_central/exports/journal_entry/queues.py
31.57%
13 Missing :warning:

apps/business_central/utils.py
48.00%
13 Missing :warning:

apps/business_central/actions.py
27.27%
8 Missing :warning:

... and 3 more

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #52      +/-   ##
==========================================
- Coverage   90.96%   82.81%   -8.16%
==========================================
  Files          51       61      +10
  Lines        2513     2950     +437
==========================================
+ Hits         2286     2443     +157
- Misses        227      507     +280

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


Second of two Orbit sliders doesn't display first slide's content

Test page.
Foundation 5.2.2.
In various browsers and devices, very often on page-load the second Orbit slider doesn't display the first slide.
After a right + left, the first slide is shown.

THANK YOU David!
I also had to add CSS Z Index as well, then this worked.
$('.orbit-container li:first-of-type').addClass('active');
$(".orbit-container li:first-of-type").css({ 'z-index': "4" });

THANK YOU David!
I also had to add CSS Z Index as well, then this worked.
$('.orbit-container li:first-of-type').addClass('active');
$(".orbit-container li:first-of-type").css({ 'z-index': "4" });

THANK YOU David!
I also had to add CSS Z Index as well, then this worked.
$('.orbit-container li:first-of-type').addClass('active');
$(".orbit-container li:first-of-type").css({ 'z-index': "4" });

THANK YOU David!
I also had to add CSS Z Index as well, then this worked.
$('.orbit-container li:first-of-type').addClass('active');
$(".orbit-container li:first-of-type").css({ 'z-index': "4" });

So good!


Fail to execute "Run Node"

HKube micro-service
To which micro-service the bug related to, Dashboard ,Monitor-Server etc.
Describe the bug
Fail to execute "Run Node" the job stay in "active" mode
when trying to "run node" on Simple pipeline on the yellow node
the following  Pipeline Driver errors appear:

unable to find watcher for /jobs/tasks/main:simple:pn15aa8d/
unable to stop pipeline, Cannot read property '_getNodesAsFlat' of null
node "yellow" is depend on node "green" which is not exists

@tamir321
Actually, this is one bug that created a chain reaction:
node "yellow" is depend on node "green" which is not exists.
Just a Bug in the DAG :-)
Fixed

tested on version
systemVersion: "v2.0.16",
fullSystemVersion: "v2.0.16-1605190942320",


python312Packages.ollama: 0.1.9 -> 0.2.0, oterm: 0.2.7 -> 0.2.8

Diff: https://github.com/ollama/ollama-python/compare/refs/tags/v0.1.9...v0.2.0
Changelog: https://github.com/ollama/ollama-python/releases/tag/v0.2.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 310777 run on x86_64-linux 1

6 packages built:

oterm
oterm.dist
python311Packages.ollama
python311Packages.ollama.dist
python312Packages.ollama
python312Packages.ollama.dist

Result of nixpkgs-review pr 310777 run on x86_64-linux 1

6 packages built:

oterm
oterm.dist
python311Packages.ollama
python311Packages.ollama.dist
python312Packages.ollama
python312Packages.ollama.dist


Rename Language Server assemblies

Includes https://github.com/Microsoft/PTVS/pull/4496, will updated when it is merged. Changes namespace but only in the LS.

Do we need to do anything specific for the client-side update?

I think I looked at the relevant commits, but I'll review properly once the other changes are not in this PR any more - they're far too distracting.

Client side went in here https://github.com/Microsoft/vscode-python/pull/2122


Welcome page

Rename asset folders
Improve the welcome page
removed use of clientUuid

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


指数成分格式

比如沪深300的这种格式，被调出的股票以后必然不会被再调入吗？
若是有可能再调入，则现在的格式的表达方式是不是并不适合？

A symbol whose index has been moved out may be moved in again; the format can now represent multiple moves in and out.
For example(csi300.txt):
SH600004	2005-01-01	2011-12-30
SH600004	2018-12-17	2021-06-10

SH600004 was added to csi300 on 2005-05-01(the earliest record publicly available), moved out on 2011-12-30; moved in again on 2018-12-17 and continues to the present (2021-06-10 date of data update)

@jingmouren
Would you mind sending a PR to improve the docs about this Question?
Other users who have similar confusion will be grateful to you :)
Thanks