OpenXLSX-Exports.hpp is missing

Hello,
I've tried to use this librairy, but the file "OpenXLSX-Exports.hpp" is missing. Therefore I can't build it. Even in the legacy branch I can't find the file. Could you upload this file so we could use this librairy. Thanks in advance!
Build error message:
XLCell.hpp(54,10): fatal error C1083: Cannot open include file: 'OpenXLSX-Exports.hpp': No such file or directory

I added my own file and export definition, but later I found there's a flag to generate the file.
using visual studio, I found there were a couple of other compile errors using std17.
mostly just namespace ambiguities, pretty easy to work through.

I have this issue using Xcode - can you please help me with how to use the flag to generate the  hpp?

Please note that OpenXLSX uses CMake as a build script generator. So the OpenXLSX-Export.hpp file is not missing; it will be automatically generated by CMake when running it.
Instructions for how to build OpenXLSX using CMake can be found on the GitHub page: https://github.com/troldal/OpenXLSX#build-instructions
Note that CMake support has been a part of Visual Studio since 2017, so it should be possible to open the project directly in Visual Studio. However, the OpenXLSX CMake project may use features not included in Visual Studio 2017. It works flawlessly in Visual Studio 2019 though.

troldal, your instruction was not clear. Can you please put details step.

I am probably missing something and apologize for being very basic at
programming.. ...
I followed my untuition in a sense and executed cmake twice....
I am not sure whether this was a success.
Could anyone please see the logs and whether I have deviated from the
instructions?
It may probably have to do with where I created the directory..
First LOG

All my projects reside in a directory I created called OV-PROJS
I downloaded the zip file into a subdirectory created called 'OpenXLSX'
under OV-PROJS
I assumed this is the root directory as referred to in the instructions
created directory called 'build' and executed 'cmake ..' > the below log
file

OV-MBP:build ovandara$ cmake ..
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
Doxygen need to be installed to generate the doxygen documentation
-- Failed to find LLVM FileCheck
-- git Version: v1.5.2-bf585a27
-- Version: 1.5.2
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES -- failed to compile
-- Performing Test HAVE_STD_REGEX -- success
-- Performing Test HAVE_GNU_POSIX_REGEX -- failed to compile
-- Performing Test HAVE_POSIX_REGEX -- success
-- Performing Test HAVE_STEADY_CLOCK -- success
-- Configuring done
-- Generating done
-- Build files have been written to:
/Users/ovandara/Documents/OV-PROJS/OpenXLSX/build
OV-MBP:build ovandara$
SECOND LOG:

As the above failed log file is referring to doxygen...
I found another directory called doxy which contained cmake lists
created 'build' subdirectory in 'doxy' and executed 'cmake ..' > below
log

-MBP:OpenXLSX ovandara$ cd doxy
OV-MBP:doxy ovandara$ mkdir build
OV-MBP:doxy ovandara$ cd build
OV-MBP:build ovandara$ cmake ..
CMake Warning (dev) in CMakeLists.txt:
No project() command is present.  The top-level CMakeLists.txt file must
contain a literal, direct call to the project() command.  Add a line of
code such as
project(ProjectName)

near the top of the file, but after cmake_minimum_required().
CMake is pretending there is a "project(Project)" command on the first
line.
This warning is for project developers.  Use -Wno-dev to suppress it.
-- The C compiler identification is AppleClang <IP_ADDRESS>00032
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00032
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler:
/Library/Developer/CommandLineTools/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler:
/Library/Developer/CommandLineTools/usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
Doxygen need to be installed to generate the doxygen documentation
CMake Warning (dev) in CMakeLists.txt:
No cmake_minimum_required command is present.  A line of code such as
cmake_minimum_required(VERSION 3.19)

should be added at the top of the file.  The version specified may be
lower
if you wish to support older CMake versions for this project.  For more
information run "cmake --help-policy CMP0000".
This warning is for project developers.  Use -Wno-dev to suppress it.
-- Configuring done
-- Generating done
-- Build files have been written to:
/Users/ovandara/Documents/OV-PROJS/OpenXLSX/doxy/build
OV-MBP:build ovandara$
the directory structure:
[image: image.png]
On Tue, Dec 8, 2020 at 3:13 AM rz6955<EMAIL_ADDRESS>wrote:

troldal, your instruction was not clear. Can you please put details step.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/troldal/OpenXLSX/issues/63#issuecomment-740197526,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGBWB42B7RPZUKUNCOCTKSDSTVD6TANCNFSM4T4P2YNA
.

Hi troldal,
I wonder if your program works with office 365 excel?
Thanks
From: ovandara<EMAIL_ADDRESS>Sent: December 7, 2020 8:50 PM
To: troldal/OpenXLSX<EMAIL_ADDRESS>Cc: Richard Zhang<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [troldal/OpenXLSX] OpenXLSX-Exports.hpp is missing (#63)
I am probably missing something and apologize for being very basic at
programming.. ...
I followed my untuition in a sense and executed cmake twice....
I am not sure whether this was a success.
Could anyone please see the logs and whether I have deviated from the
instructions?
It may probably have to do with where I created the directory..
First LOG

All my projects reside in a directory I created called OV-PROJS
I downloaded the zip file into a subdirectory created called 'OpenXLSX'
under OV-PROJS
I assumed this is the root directory as referred to in the instructions
created directory called 'build' and executed 'cmake ..' > the below log
file

OV-MBP:build ovandara$ cmake ..
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
Doxygen need to be installed to generate the doxygen documentation
-- Failed to find LLVM FileCheck
-- git Version: v1.5.2-bf585a27
-- Version: 1.5.2
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES -- failed to compile
-- Performing Test HAVE_STD_REGEX -- success
-- Performing Test HAVE_GNU_POSIX_REGEX -- failed to compile
-- Performing Test HAVE_POSIX_REGEX -- success
-- Performing Test HAVE_STEADY_CLOCK -- success
-- Configuring done
-- Generating done
-- Build files have been written to:
/Users/ovandara/Documents/OV-PROJS/OpenXLSX/build
OV-MBP:build ovandara$
SECOND LOG:

As the above failed log file is referring to doxygen...
I found another directory called doxy which contained cmake lists
created 'build' subdirectory in 'doxy' and executed 'cmake ..' > below
log

-MBP:OpenXLSX ovandara$ cd doxy
OV-MBP:doxy ovandara$ mkdir build
OV-MBP:doxy ovandara$ cd build
OV-MBP:build ovandara$ cmake ..
CMake Warning (dev) in CMakeLists.txt:
No project() command is present. The top-level CMakeLists.txt file must
contain a literal, direct call to the project() command. Add a line of
code such as
project(ProjectName)
near the top of the file, but after cmake_minimum_required().
CMake is pretending there is a "project(Project)" command on the first
line.
This warning is for project developers. Use -Wno-dev to suppress it.
-- The C compiler identification is AppleClang <IP_ADDRESS>00032
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00032
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler:
/Library/Developer/CommandLineTools/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler:
/Library/Developer/CommandLineTools/usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
Doxygen need to be installed to generate the doxygen documentation
CMake Warning (dev) in CMakeLists.txt:
No cmake_minimum_required command is present. A line of code such as
cmake_minimum_required(VERSION 3.19)
should be added at the top of the file. The version specified may be
lower
if you wish to support older CMake versions for this project. For more
information run "cmake --help-policy CMP0000".
This warning is for project developers. Use -Wno-dev to suppress it.
-- Configuring done
-- Generating done
-- Build files have been written to:
/Users/ovandara/Documents/OV-PROJS/OpenXLSX/doxy/build
OV-MBP:build ovandara$
the directory structure:
[image: image.png]
On Tue, Dec 8, 2020 at 3:13 AM rz6955 <notifications<EMAIL_ADDRESS>wrote:

troldal, your instruction was not clear. Can you please put details step.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/troldal/OpenXLSX/issues/63#issuecomment-740197526,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGBWB42B7RPZUKUNCOCTKSDSTVD6TANCNFSM4T4P2YNA
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/troldal/OpenXLSX/issues/63#issuecomment-740373431, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASBDZCN7J7GN5Q67FWESXITSTWV75ANCNFSM4T4P2YNA.

I tried this library on ubuntu and it works fine.

create a folder  build
go inside build, then type (cmake dot dot),  cmake ..
type make
go to output folder
run examples  ./Demo1

When I tried to run the library on my own app (from another folder) is where I found the OpenXLSX-Exports.hpp issue but I can see is probably Im not configuring Cmake on my app properly.

@franciscotovarmit,

When did you download the OpenXLSX repo? I just pushed changes to the master branch a few days ago, and you should use the most recent version.
Can you attach the CMakeLists.txt file for your own project, so I can see what you are doing?

@franciscotovarmit,
* When did you download the OpenXLSX repo? I just pushed changes to the master branch a few days ago, and you should use the most recent version.

* Can you attach the CMakeLists.txt file for your own project, so I can see what you are doing?

Hi Troldal
I downloaded it a couple of weeks ago.
This is my CMakeLists.txt:
`
cmake_minimum_required(VERSION 3.0.0)
project(GetMarks)
find_package(OpenXLSX REQUIRED)
add_executable(GetMarks main.cpp)
target_include_directories(GetMarks PRIVATE ${})
target_link_libraries(GetMarks PRIVATE ${libOpenXLSX})
message("OpenXLSX Include Directories: "${OpenXLSX_INCLUDE_DIRS})
message("OpenXLSX Libraries: "${libOpenXLSX})`

Hi @franciscotovarmit,
I would recommend that you download the most recent version. You will notice that within the OpenXLSX repo, there is an OpenXLSX subfolder. This subfolder contains everything you need:

I can see you have installed OpenXLSX using make install, or something like that. I would recommend that you copy the OpenXLSX folder and use it as a subdirectory in your own project. Then you can use add_subdirectory instead of find_package. The CMakeLists.txt file for your own project would then look something like this (no need to use target_include_directories; all the header files should be available automatically):
cmake_minimum_required(VERSION 3.15)
project(GetMarks)
set(CMAKE_CXX_STANDARD 17)

add_subdirectory(OpenXLSX)

add_executable(GetMarks main.cpp)
target_link_libraries(GetMarks PRIVATE OpenXLSX::OpenXLSX)

OK Trodal
yes, thank you!  it works as you said.  I noticed some functions were updated too as my previous main.cpp was generating a dump error.
It amazing to be able create / extract excel data though C++ with a simple
using namespace OpenXLSX;``


docs(website): small spellfix on 3.5 update notes

Pre-flight checklist

[ ] I have read the Contributing Guidelines on pull requests.
[ ] If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
[ ] If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.

Motivation

Test Plan

Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/
Related issues/PRs

thanks 🤪


Fix last modified since error while writing settings

This PR fixes #142342

Handle settings save errors by the configuration editing service
Handle last modified since error and retry

From discussion:

debt week: move the revert closer where retry is done


Auto-registration for github

Add a configuration option to allow account auto-registration (similar to IU CAS) for github.

This has been implemented.


GraphQL requests does not work from Apollo on React Native

Current I have issue while using @nhost/react-auth and @nhost/react-apollo in an Expo (React Native) project, still not sure but based on the error message, I give it a try here.
The wrapper:
import { NhostAuthProvider } from '@nhost/react-auth';
import { NhostApolloProvider } from '@nhost/react-apollo';
...
      <NhostAuthProvider nhost={nhost}>
        <NhostApolloProvider nhost={nhost}>
        ...
              <RootStack />
        ...
        </NhostApolloProvider>
      </NhostAuthProvider>

The nhost:
export const nhost = new NhostClient({
  backendUrl: 'http://localhost:1337',
  clientStorage: SecureStore,
  clientStorageType: 'expo-secure-storage',
});

The query:
import gql from 'graphql-tag';
...
export const JOBS_NEARBY_AGGREGATE = gql`
  query JOBS_NEARBY_AGGREGATE (
    $args: jobs_nearby_args!,
    $limit: Int!,
    $offset: Int!,
    $where: jobs_bool_exp!
  ) {
    jobs_nearby_aggregate(args: $args, limit: $limit, offset: $offset, where: $where) {
      __typename
      nodes {
        id
        created_at
        description
        expiration_date
        quantity
        title
        updated_at
        address {
          id
          unstructured_value
          location
        }
      }
    }
  }
`;

The implementation:
  const { data, error } = useQuery(JOBS_NEARBY_AGGREGATE, {
    variables: {
      args: {
        distance: 9999,
        user_id: user?.id ?? '', // correct id
      },
      limit: 10,
      offset: 0,
      where: {
        company: {
          tenant_id: { _eq: '...' }, // correct id
        },
      },
    },
    fetchPolicy: 'network-only',
    errorPolicy: 'all',
  });

The issue:
Response: Bad Request

// Copied as cURL
curl 'http://localhost:1337/v1/graphql' \
  -H 'accept: */*' \
  -H 'Referer: ' \
  -H 'authorization: Bearer correct token here' \
  -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 12_0_1) AppleWebKit/537.36 (KHTML, like Gecko) ReactNativeDebugger/0.12.1 Chrome/87.0.4280.141 Electron/11.4.6 Safari/537.36' \
  -H '__RN_DEBUGGER_SET_HEADER_REQUEST_sec-websocket-protocol: graphql-ws' \
  -H 'content-type: application/json' \
  --data-binary $'{"operationName":"JOBS_NEARBY_AGGREGATE","variables":{"args":{"distance":9999,"user_id":"b63259c1-c4b6-450d-9ee7-baf297515570"},"limit":10,"offset":0,"where":{"company":{"tenant_id":{"_eq":"3ad7aaec-1ba8-476c-b378-d1257f212a94"}}}},"query":"query JOBS_NEARBY_AGGREGATE($args: jobs_nearby_args\u0021, $limit: Int\u0021, $offset: Int\u0021, $where: jobs_bool_exp\u0021) {\\n  jobs_nearby_aggregate(\\n    args: $args\\n    limit: $limit\\n    offset: $offset\\n    where: $where\\n  ) {\\n    __typename\\n    nodes {\\n      id\\n      created_at\\n      description\\n      expiration_date\\n      quantity\\n      title\\n      updated_at\\n      address {\\n        id\\n        unstructured_value\\n        location\\n        __typename\\n      }\\n      __typename\\n    }\\n  }\\n}\\n"}' \
  --compressed

Every time I make a query request from React Native, the nhost backend show this error message:
2021/12/07 18:58:21 websocketproxy: couldn't upgrade websocket: the client is not using the websocket protocol: 'upgrade' token not found in 'Connection' header

To compare, these response below are exactly the same query on Next.js application:
curl 'http://localhost:1337/v1/graphql' \
  -H 'Connection: keep-alive' \
  -H 'sec-ch-ua: " Not A;Brand";v="99", "Chromium";v="96", "Google Chrome";v="96"' \
  -H 'accept: */*' \
  -H 'content-type: application/json' \
  -H 'authorization: Bearer correct token here' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.55 Safari/537.36' \
  -H 'sec-ch-ua-platform: "macOS"' \
  -H 'Origin: http://localhost:3000' \
  -H 'Sec-Fetch-Site: same-site' \
  -H 'Sec-Fetch-Mode: cors' \
  -H 'Sec-Fetch-Dest: empty' \
  -H 'Referer: http://localhost:3000/' \
  -H 'Accept-Language: en-US,en;q=0.9,vi-VN;q=0.8,vi;q=0.7' \
  --data-raw $'{"operationName":"JOBS_NEARBY_AGGREGATE","variables":{"args":{"distance":9999,"user_id":"b63259c1-c4b6-450d-9ee7-baf297515570"},"limit":10,"offset":0,"where":{"company":{"tenant_id":{"_eq":"3ad7aaec-1ba8-476c-b378-d1257f212a94"}}}},"query":"query JOBS_NEARBY_AGGREGATE($args: jobs_nearby_args\u0021, $limit: Int\u0021, $offset: Int\u0021, $where: jobs_bool_exp\u0021) {\\n  jobs_nearby_aggregate(\\n    args: $args\\n    limit: $limit\\n    offset: $offset\\n    where: $where\\n  ) {\\n    __typename\\n    nodes {\\n      id\\n      created_at\\n      description\\n      expiration_date\\n      quantity\\n      title\\n      updated_at\\n      address {\\n        id\\n        unstructured_value\\n        location\\n        __typename\\n      }\\n      __typename\\n    }\\n  }\\n}\\n"}' \
  --compressed

Works on Next.js

Works on Postman

CC @elitan

We've confirmed that this issue is only present when using the CLI.
When making the same GraphQL request to Nhost directly (*.nhost.run/v1/graphql) the GraphQL request works.

It works with remote graphql url:

https://github.com/nhost/cli/blob/0c5700a1ad059ec47d2e21e5fdf79fc9b5e90926/proxy/proxy.go#L76
Possibly related?

https://github.com/nhost/cli/blob/0c5700a1ad059ec47d2e21e5fdf79fc9b5e90926/proxy/proxy.go#L76
Possibly related?

I'm trying to reproduce the error on my end. I'll have a look and update you guys.
Thanks for opening the issue!

This has been fixed in v0.5.11 onward.


WIP: pools of values + primitive golang types as values

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: #269
What is the new behavior?

Other information

Codecov Report

Merging #285 (2095a4e) into master (6c41559) will decrease coverage by 39.36%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master     #285       +/-   ##
===========================================
- Coverage   57.53%   18.17%   -39.37%
===========================================
  Files         134      131        -3
  Lines       15332    15227      -105
===========================================
- Hits         8821     2767     -6054
- Misses       5956    12246     +6290
+ Partials      555      214      -341

Flag
Coverage Δ

1.14.x
?

1.15.x
?

1.16.x
?

1.17.x
18.17% <ø> (-39.37%)
:arrow_down:

1.18.x
?

connection
12.79% <ø> (ø)

discovery
11.94% <ø> (ø)

e2e
18.17% <ø> (-27.67%)
:arrow_down:

integration
18.17% <ø> (-27.67%)
:arrow_down:

macOS-latest
?

ratelimiter
14.75% <ø> (ø)

scripting
?

table
?

ubuntu-latest
18.17% <ø> (-39.37%)
:arrow_down:

unit
?

windows-latest
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Updated doc

Description
Updated doc
Type of change

Documentation update

Testing steps
N/A
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report

Merging #167 (f448763) into master (f3b1c17) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #167   +/-   ##
=======================================
  Coverage   17.84%   17.84%
=======================================
  Files           3        3
  Lines         454      454
=======================================
  Hits           81       81
  Misses        362      362
  Partials       11       11

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 f3b1c17...f448763. Read the comment docs.


ETCPACK license

If I understand the ETCPACK license correctly, ETCPACK may only be distributed in binary form, with the exception of etcdec.cxx. However, Compressonator distributes etcimage.cxx and etcpack.cxx (as well as etcdec.cxx, which is fine).
Either my understanding of the license is wrong (I don't speak legalese), or this is a problem. Does AMD have an agreement with Ericsson allowing distribution of the source of those files? If so, how should I as a user relate to this?
Could a submodule be a solution? Then these files would not be distributed by this repository, strictly speaking, but by Ericsson's repository.

Thank you for your attention to the ETCPACK License.
According to our understanding, the license permits distributions including binary form, not only binary form as you understood. We have followed ETCPACK license by clone it open source unmodified.
Your suggestion to move it to a submodule would help in getting the latest updates and patches.
Since we have open sourced Compressonator in April 2016 prior to ETCPACK license publication in May 2016, we will now include it in Compressonator repository, thanks to your report.

etcpack.cxx does not appear to be unmodified. At least the #ifdef USE_IN_COMPRESSONATOR around the int main-definition looks suspiciously like something added in Compressonator. (The clue is in the define name.)

Good point, There are modifications in order remove compiler warnings and to add the lib to another application with a duplicated main() entry!


[Judgement View] Make preview longer

Preview videos (of presumably individual or a range of frames that have been submitted) tend to be very short. I think it would make sense to give a preview of at least 2s around the submitted frame so as to prevent rounding errors etc. to hinder the judge in reaching a clear verdict.

Play at least a few seconds of every submission, if necessary add padding

Implemented in 9b5195d52677feccc427492db9185da54dc6d997


Child theme custom module not available through page builder

Problem Description
I've duplicated the Team Member / Person module as a slightly different module in my child theme. In my child theme's functions.php, I have:
// Load Custom Divi Module
function divi_child_theme_setup() {
    if ( ! class_exists('ET_Builder_Module') ) {
        return;
    }
    get_template_part( 'includes/builder/module/AgriminStaff' );
}
add_action( 'et_builder_ready', 'divi_child_theme_setup', 9999 );

My AgriminStaff.php file is here. So far it's simply swapping the order of the Position and Name, and changing the position tag from a p to a h4.
In my child theme's includes folder, I have a file called widgets.php;
<?php
get_template_part( 'includes/builder/module/AgriminStaff' );

I receive no errors in the page builder, but the module 'Agrimin Staff' is not visible to be added to the page from the list of available modules.
Steps To Reproduce
See above

Hello @SRD75,
Could you please follow this article? https://intercom.help/elegantthemes/en/articles/2865589-moving-contact-form-module-to-child-theme


Fixes compatibility with GCC 6.3.0

This fixes compatibility with GCC 6.3.0 by using preprocessor instead of consts for size offsets in osrom2elf.  Closes bug #1.

Hi,
The commit itself looks good, but as stated in the README.md file I'd rather put a license first before accepting contributions. Is the 2-clause BSD license OK with you? If so, I'll merge this right away and then add the license file with the GitHub web interface, since I don't have access to my main computer right now.

Sorry about that, I didn't actually get as far as reading the README.
I unconditionally grant you all rights to this humble little patch, and to any future pull requests that I might send for your project.  2-clause BSD is a fine license, but you may use whatever license you like.
Cheers,
--Travis

OK then, I'm merging.
I should really get back to this project... I really need to create a HP Prime emulator, flashing the HP Prime under Windows over and over gets old rather fast.


[v1.5.x] Backport test_bilinear_resize_op fix (#15011)

Description
This PR backports PR #15011, which fixes the flaky test_bilinear_resize_op.
The test has been observed to fail on branch v1.5.x here
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[x] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[x] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

@mxnet-label-bot add [Test, Python, Operator, pr-awaiting-review]

we can close this now, 1.5.x is already synced with master on 05/26. I think it includes the fix.


intellisense @Model doesn't shows some properties.

Hi! Thanks for this amazing plugin.
Intellisense is able to show only some of the Model's properties. I think I get the reason, but i don't know how to fix. An example will get us on the right path:
Model:
public partial class MyModel
{
    public int ID {get; set;}
    public virtual OtherModel MyOtherModel {get;set;}
}

In the Html document if I use @Model.ID everything is fine. If I use @Model.MyOtherModel I get an error. I think the reason for this is related to the number of words in the property declaration.
The intellisense shows me that OtherModel is the name - which actually is the type-  of the property and virtual is the type -which is not the type-.
It seems that it splits the line and takes always the "second" word as the property's type and the third one as the Property's Name.
I don't think this issue is related to the plugins, os or visual studio core versions, but if they are needed let me know.
Thanks.

I have figured it out.
Inside this file declarationInfo.ts the method getProperties uses a RegExp to split the property line definition by fields. This RegExp doesn't matches two common scenarios:
a. public virtual Person _Person
b. public int? Size
Since the item.type and item.name are initialized to results[1] and results[2] respectively, the scenario
a makes to match Virtual as type and Person as name.
For the scenario b is different: the ? is a special char so the regexp doesn't match at all.
The fix is easy:
we could replace this line:
let propRegExp = /public\s(\w*<?\w+>?)\s(\w+)/g;

to
let propRegExp = /public\s(?:virtual\s)?(\w*<?\w+>?\??)\s(\w+)/g;

here we can test the regexp: newRegExp
For the scenario b the new regExp works great because it shows the ? as well, which notify the developer that this field is <Nullable>
I'm really sorry to not be able to make this change by myself. I tried to clone the project and run it in debug mode, but I'm not able to achieve this.
I'm so sorry.
p.s. If someone can help me to get it done I will appreciate. I really love this plugin, I think it's a shame for Microsoft to not fully support Razors and tag-helpers with visual studio code. I have a lot of problem formatting razor file as well.

Finally, I made a pull request #12
I hope this will be merged.

Hey :)
I merged the pull request.


[Bug]: SelectionOutputParser incorrectly parsing Router Query Engine

Bug Description
The SelectionOutputParser class in the llama-index library was unable to correctly parse JSON objects when used with a router query engine and a LLMSingleSelector with only one tool. The _marshal_llm_to_json method was designed to extract a JSON array from a string, but it failed when the output was a JSON object. This resulted in a json.JSONDecodeError: Expecting value: line 1 column 1 (char 0) error.
Version
The issue was observed in llama-index version v0.6.34.post1.
Steps to Reproduce

Set up a router query engine with a LLMSingleSelector with only one tool.
Use the GPT-4 model for the tool.
Create an instance of the SelectionOutputParser class.
Call the parse method on this instance, passing a string that represents a JSON object (not an array). For example: {"choice": 1, "reason": "The provided choice does not directly address the question, but it is the only choice available. The question asks for a specific task of data structuring, which is not covered in the given choice."}
4b. also if you attempt to ask a question that does have a tool that matches it still errors

output pre marshal {"choice": 1, "reason": "The provided choice does not directly address the question, but it is the only choice available. The question asks for a specific task of data structuring, which is not covered in the given choice."}
output post marshal
Error parsing JSON response: Expecting value: line 1 column 1 (char 0)
Relevant Logs/Tracbacks
{
  "type": "array",
  "items": [
    {
      "type": "object",
      "properties": {
        "choice": {
          "type": "integer",
          "value": 1
        },
        "reason": {
          "type": "string",
          "value": "The choice is relevant as it refers to the structuring of XXX data, which is the task at hand. The task involves XXX into a specific JSON format."
        }
      },
      "required": [
        "choice",
        "reason"
      ],
      "additionalProperties": false
    }
  ]
}
[2023-06-27 13:50:39 -0400] [79292] [ERROR] Error handling request /send_message
Traceback (most recent call last):
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/gunicorn/workers/gthread.py", line 271, in handle
    keepalive = self.handle_request(req, conn)
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/gunicorn/workers/gthread.py", line 323, in handle_request
    respiter = self.wsgi(environ, resp.start_response)
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/flask/app.py", line 2213, in __call__
    return self.wsgi_app(environ, start_response)
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/flask/app.py", line 2193, in wsgi_app
    response = self.handle_exception(e)
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/flask/app.py", line 2190, in wsgi_app
    response = self.full_dispatch_request()
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/flask/app.py", line 1486, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/flask/app.py", line 1484, in full_dispatch_request
    rv = self.dispatch_request()
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/flask/app.py", line 1469, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/flask_login/utils.py", line 290, in decorated_view
    return current_app.ensure_sync(func)(*args, **kwargs)
  File "/Users/shere/Documents/GitHub/dev-ai-chat-template/app/app.py", line 348, in send_message
    response = get_bot_response(user_question, user_id, project_name, chat_history_file_path, project_attributes, direct_ai_chat)
  File "/Users/shere/Documents/GitHub/dev-ai-chat-template/app/llm_handler.py", line 284, in get_bot_response
    response = handle_index_type(
  File "/Users/shere/Documents/GitHub/dev-ai-chat-template/app/llm_handler.py", line 304, in handle_index_type
    response_obj = query_router_index(
  File "/Users/shere/Documents/GitHub/dev-ai-chat-template/app/llm_handler.py", line 1672, in query_router_index
    response = query_engine.query(user_question)
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/llama_index/indices/query/base.py", line 23, in query
    response = self._query(str_or_query_bundle)
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/llama_index/query_engine/router_query_engine.py", line 116, in _query
    result = self._selector.select(self._metadatas, query_bundle)
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/llama_index/selectors/types.py", line 76, in select
    return self._select(choices=metadatas, query=query_bundle)
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/llama_index/selectors/llm_selectors.py", line 103, in _select
    parse = self._prompt.output_parser.parse(prediction)
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/llama_index/output_parsers/selection.py", line 71, in parse
    answers = [Answer.from_dict(json_dict) for json_dict in json_list]
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/llama_index/output_parsers/selection.py", line 71, in <listcomp>
    answers = [Answer.from_dict(json_dict) for json_dict in json_list]
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/dataclasses_json/api.py", line 72, in from_dict
    return _decode_dataclass(cls, kvs, infer_missing)
  File "/Users/shere/virtualenvs/dev-ai-chat-template/lib/python3.10/site-packages/dataclasses_json/core.py", line 159, in _decode_dataclass
    field_value = kvs[field.name]
KeyError: 'choice'

I think your solution makes sense, definitely feel free to raise a PR with this @sheresaidon !
Also just to note, we also have pydantic selectors that work with the new function calling API from OpenAI. These should be less prone to breaking, and I recommend trying them out :) https://gpt-index.readthedocs.io/en/latest/examples/query_engine/RouterQueryEngine.html#pydanticsingleselector


Multishot POC

Fixes #34
I have no expectation that this PR will be merged at all. This likely needs more design work, hence it's just a POC. I've made sure that there's near feature-compatibility, but of course the API had to change somewhat. The current version of kontinuity doesn't support Native because I haven't figured out how to shallow clone Continuations yet (I haven't tried hard enough though, so suggestions are very welcome).
I had to modify some of the tests that e.g. expected failures for things that are supported now. Also, tests for parameter being used inside of a Sequence couldn't work anymore because of the usage of suspend, and hence they had to be removed.

Closed in favour of #37 because I hadn't rebased correctly (oops)


Fix the link to Transport for Berlin, Germany API

Replaces broken link with its new version.
It seems like there is a new version of the API and docs. The old link is outdated.

Thank you!


update the coffea to root tool with configurations

updated based on PR#23.
now the script convertToRoot  can be run by editing the config files in the cfg directory:
python VHccPoCo/scripts/convertToRoot.py -c VHccPoCo/cfg/shapemaker_vhcc_run3/Zll_Shape.yaml

@De-Cristo I merged my development, now there are conflicts here, sorry.
Could you please resolve the conflits.


Quote primary table name if identifier quoting is enabled

With the latest master build we ran into the problem that COUNT(*)-queries to our order table failed. This patch ensures that the setting for identifier quoting is properly observed.
Note that I deliberately ignored the getSql helper-function in the test, as this behaviour is precisely what the getSql helper-function hides.

Was this a regression recently introduced?

I think so, as we didn't encounter the same problem before. However, I'm not entirely sure and I'm not interested in the finger-pointing game :smile_cat:

Codecov Report

Merging #1769 (db6641c) into master (1a3140e) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #1769      +/-   ##
============================================
+ Coverage     87.87%   87.89%   +0.01%
  Complexity     7826     7826
============================================
  Files           267      267
  Lines         22543    22543
============================================
+ Hits          19810    19814       +4
+ Misses         2733     2729       -4

Flag
Coverage Δ

5-max
87.89% <100.00%> (+0.01%)
:arrow_up:

7.4
87.89% <100.00%> (+0.01%)
:arrow_up:

agnostic
73.34% <100.00%> (ø)

mysql
69.89% <100.00%> (+0.01%)
:arrow_up:

pgsql
69.82% <100.00%> (+0.01%)
:arrow_up:

sqlite
67.81% <100.00%> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/Propel/Runtime/ActiveQuery/Criteria.php
89.97% <100.00%> (+0.44%)
:arrow_up:

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 1a3140e...db6641c. Read the comment docs.

All good - if anything we would rather use this to improve our code review skills :) After all, we approved and merged without seeing this.
Anyway, we do need a 2nd signoff on this to merge.


nat-gateways module: Avoid conversion to set to fix ordering issue

[x] Update the changelog
[ ] Make sure that modules and files are documented. This can be done inside the module and files.
[ ] Make sure that new modules directories contain a basic README.md file.
[ ] Make sure that the module is added to tests/main.tf
[ ] Make sure that the linting passes on CI.
[ ] Make sure that there is an up to date example for your code:
- For new modules this would entail example code for how to use the module or some explanation in the module readme.
- For new examples please provide a README explaining how to run the example. It's also ideal to provide a basic makefile to use the example as well.
[ ] Make sure that there is a manual CI trigger that can test the deployment.

Confirmed in private tracker.


[5.8] Add ArrayAccess to container contract

This PR adds ArrayAccess to the Container contract as Taylor suggested in #26364.

We've reverted this PR.


[22.05] backport haskell.packages.ghc924.hiedb: dontCheck

Description of changes
backport from https://github.com/NixOS/nixpkgs/pull/184194 to make hiedb build under new GHC
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
22.11 Release Notes (or backporting 22.05 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

(this is my first NixOS PR, hopefully it's simple enough that i didn't break anything :D)

@ofborg build haskell.packages.ghc924.hiedb haskell-language-server

Backport commits should be created using cherry-pick -x, so it's easier to find the original commit (see the backporting guide). Can you please fix that and force-push to this branch?

@sternenseemann done, thanks

@ofborg build haskell.packages.ghc923.hiedb haskell.packages.ghc924.hiedb


File Explorer Keyboard Navigation - Part 2: Input Focus Revamp

This changes the input handling to manage focus through the state and routes input "bottom-up" instead of "top-down" (or rather sometimes "top-down" as it was a bit of a hybrid) where focus is handled imperatively and focused nodes get input events on the nodes themselves.
This introduces a focus stack kept int he state to keep track of which parts of the UI has requested focus, but also a FocusManager that computes the actual focus based on the entire state in order to maintain other invariants, such as focus always being with he Quickmenu input if it is open, and (potentially) not being able to focus an element that is not actually visible.
A few other benefits:

A number of hacks have been removed because they're no longer necessary.
Input handling has been removed from OniInput to be put in InputModel, which provides for a much cleaner separation of concerns.

This changes the input handling to manage focus through the state and routes input "bottom-up" instead of "top-down" (or rather sometimes "top-down" as it was a bit of a hybrid) where focus is handled imperatively and focused nodes get input events on the nodes themselves.

Cool! Thanks for thinking about this, @glennsl . This bottom-up modeling seems much cleaner than what we had before, because there is a consistent source of the truth for what is focused (whereas what wasn't necessarily the case with the 'hybrid' approach before..)

A number of hacks have been removed because they're no longer necessary.

Nice!


allow helm serve to take a path to a local chart repository directory

Current default repository that helm serve uses as a local chart repository is $HELM_HOME/local.
Being able to pass in a path to directory would help chart developers mirroring a remote chart repository.

Closed by #1029


support read dwrf file from hdfs

What changes were proposed in this pull request?
support to read dwrf file from hdfs as described in #388
How was this patch tested?
manual tests

read the source file from hdfs ,like

val lineitem = spark.read.format("dwrf").load("hdfs://testcluster/user/hive/warehouse/lineitem_dw")

2 .and then run a tpch scripts
select
        l_returnflag,
        l_linestatus,
        sum(l_quantity) as sum_qty,
        sum(l_extendedprice) as sum_base_price,
        sum(l_extendedprice * (1 - l_discount)) as sum_disc_price,
        sum(l_extendedprice * (1 - l_discount) * (1 + l_tax)) as sum_charge,
        avg(l_quantity) as avg_qty,
        avg(l_extendedprice) as avg_price,
        avg(l_discount) as avg_disc,
        count(*) as count_order
from
        lineitem
where
        l_shipdate <= '1998-9-01'
group by
        l_returnflag,
        l_linestatus
order by
        l_returnflag,
        l_linestatus

We use this script to build velox, https://github.com/oap-project/gluten/blob/main/tools/build_velox.sh
Maybe you need to build support hdfs

We use this script to build velox, https://github.com/oap-project/gluten/blob/main/tools/build_velox.sh Maybe you need to build support hdfs

OK, I will try it

And add some unit tests

https://github.com/oap-project/gluten/pull/152/files @zhouyuan Can you take eye on this PR? It is similar to yours

@KevinyhZou Can you please do a rebase? The GHA failures should be fixed in main branch

@KevinyhZou Can you please do a rebase? The GHA failures should be fixed in main branch

done.

@KevinyhZou thanks for adding this feature!


Community Guide content has outdated call info

At https://github.com/odpi/egeria the top level README.md correctly lists our current calls on Tue/Wed/Thu

However if someone goes to https://egeria-project.org & then follows the link the 'Community Guide' they are presented with OLD information - with calls on a tuesday, and no links to the calendar.

Can we consolidate to a single copy of this information to avoid them getting out of sync
We need to ensure the up to date info is available to those going to the egeria-project.org page

Thanks for spotting @sumalaika , cc:  @davidradl @mandy-chessell

@adharida is interested in doing this change - he says he will do this today, as a way of contributing to Egeria - are you ok with this @planetf1 and @mandy-chessell. You may have already done though Mandy!

If I get approval, I would perform the change today.

Note that our web page docs are moving from https://github.com/odpi/egeria to https://github.com/odpi/egeria-docs . I would recommend searching both places for related text & consistency

@adinh808 Mandy and Nigel are fine with you doing this, I have assigned this issue to you. You are free to proceed, thank you for your interest and forthcoming contributions to Egeria.

@cmgrote drawing your attention to this docs change.

Hi @adinh808 -- indeed we've started to migrate some of this information, with the idea that the best approach for up-to-date call information is likely going to be just rendering our calendar itself (rather than needing to maintain the calendar and these static markdowns separately)...  The revised information is here:
https://odpi.github.io/egeria-docs/guides/community/
It does sound like there might be additional information in the top-level README, though, that is not currently in the community guide?  I wonder if it would make sense to move that information from the top-level README into the community guide, and then point the top-level README at the community guide?

The actual project Readme page (https://github.com/odpi/egeria) has all the info about calls and links to calendar. If the top level README page contains updated and all the necessary information, then we can add the same to https://odpi.github.io/egeria-docs/guides/community/ and https://egeria-project.org/community-guide pages. Definitely, we can point out the top level README page in these Community guides.

I see the content in https://github.com/odpi/egeria-docs/blob/main/site/docs/guides/community.md seems to be the latest and this can be integrated into https://egeria-project.org/community-guide page. I will validate the content across both pages.

@cmgrote I see what you are saying Chris. I assume we will lose the top level readme in the move to mkdocs. So copying over the content to the community guide should be an improvement for now. Maybe we remove from the top level readme as part of the transition - as people are used to seeing it there in the current structure. This would allow @adinh808 to complete his first contribution.

Should I go ahead and collate information from both sources and set up the data or wait for some more time to go with the update?

Ref the removal from the top level README. I would be inclined to agree - remove the info from there, but ensure there is a clear link in the readme to the location of the community guide which includes information about contribution and regular calls. I realise that link is a bit transient for now - I'm inclined to leave this until the main docs migration is at a point we were are back to doing small incremental changes rather than large restructuring.

+1

I have done the requested changes as per the comments mentioned in this issue. A Pull request opened for this update: 5603
Following are update,

Updated the Community Guide with information present in top level README.md file
Removed the content from top level README.md file
Updated the egeria-docs repo Communityguide page as well with latest information available in top level README.md file

@cmgrote I am looking for your approval or not of this change - as I do not want to interfere with your big change.

I think we pretty much focus on the new repo, with the expectation that will become the default 'soon'. I don't think it's particularly valuable to updat the existing docs. In some cases a link may be helpful, but even then it could be unnecessary (unless the source of that link remains long-term, such as the readme)

this is now fixed, as we embed a google calendar in the page


Scene Render Crashes with Large 3D Tiles

I'm trying to debug an unusual Cesium crash with 3D Tiles. A hierarchy of Composite-packed models is being loaded (although the same issue occurred with un-composited b3dm models). The top-level tile and model loads fine; after zooming, Cesium starts to load the child models. After a predictable amount of time, which appears from the Network debugging tab in Chrome to correspond to all child Composite tiles being loaded, Cesium crashes with the following error, context, and call stack.
Error (in cesium/Source/Renderer/Texture.js):
        if (width <= 0) {
            throw new DeveloperError('Width must be greater than zero.');
        }

Call stack:
Texture
createTexture
updateFramebuffers
GlobeDepth.update
updateAndClearFramebuffers
executeCommandsInViewport
updateAndExecuteCommands
render

The context (that is, scene._context) passed all the way down to Texture() from updateAndClearFramebuffer has width (drawingBufferWidth) and height (drawingBufferHeight) 0. Therefore, as far as I can tell, the models themselves are not the problem. How can I proceed in debugging this issue, as I suspect Cesium itself, not my models, are at fault? Thanks in advance, and my apologies if it turns out to be a spurious issue.

How large is the tileset? This sounds like an out of memory issue.

The top-level tile is a ~50MB cmpt, and the children sum to about ~200MB, so that could definitely be the case; I'll reduce the detail in the tiles and try again. To keep this as a potentially useful issue, is there possibly a cleaner way to handle this, for example to provide a callback to allow the application to catch when loading a tile is going to cause this to occur, or is there no good way to do so?

The memory situation should have been improved now that skipping lods and unloading based on memory usage are in.
I'm going to close for now, but feel free to comment if there are still issues.

Hi,
I am facing same error. Is there any solution for this?, kindly let me know.
Best Regards,
K.Jayakumar

@jkumar80 some things to try are

Lower maximumMemoryUsage, maybe to 256 or 128.
Raise maximumScreenSpaceError, maybe to 32.

However if the tileset isn't well optimized it may still run into out of memory problems.

Thanks Iilleyse for your reply. Please let me know how to optimize the tile set?

Hi,
I set maximumMemoryUsage = 512MB,But the browser memory uses 2G,And it will not fall.
My 3dtile has 100G size.

@itsegg Cesium's current strategy is to always load the amount of data required for the current scene and screen space error.  maximumMemoryUsage is just the size of the frame-to-frame cache.  We realize this is not ideal and plan on changing it, please follow #6226 for details.
In the meantime, your best solution is to raise maximumScreenSpace error for your tilesets.

Thanks for your reply.

@mramato
Hi mramato,
I found a place in Cesium that caused the memory to keep increasing,
When tile.unloadTile (), _request also occupies memory.
After this modification, the memory of my browser stabilized at about 1.5G.
My Cesium version is 1.69

@itsegg that looks suspiciously similar to https://github.com/CesiumGS/cesium/issues/8843

@mramato Hi! I try to load a large 3D tiles model more than 200GB and Cesium(version 1.71) crashes now. It is still out of memory. Now Is all I can do now is still raise maximumScreenSpace error?


Normal execution after cancellation due to onSuccess(...) in StageTransition.set(...)

Hi,
First of all, thank you for your code, it helped me really a lot as I needed in my GUI the ability to cancel the running underlying task. Moreover, your code enables me to extend this cancellation ability such that I could cancel the whole tree of underlying tasks which the "root" task depends on. This extension is currently in progress, and when finished I would like to share it with you. Would you be interested?
Anyway, I think I found an issue in the original code today. I wrote a simple test (OnSuccessTest) which runs two async tasks, the first one and then the second one. In the test I cancel the first task but the second one still can be executed which it should not as the first stage should complete exceptionally with CancellationException. For me the issue occurs when the first task is cancelled (from main thread) using AbstractCompletableTask.cancel(true) but the onError(...) in this method is DELAYed (I added some code before). In this case the StageTransition.set(...) method can be executed from FutureTask.run() during the DELAY on a thread pool thread and the first stage is completed successfully despite of its task was cancelled.
My solution is to test the completion status of the task in StageTransition.set(...) and call either onError(...) when the task was cancelled or onSuccess(...) otherwise.
test.zip

ajurcik,
I run your test and it's executed with green colors.
I modified it to add more explicit debug statements -- and it shows expected results.
s1 is canceled, s2 is not even started (see modified test attached).
Did you modify source code of the library itself? What version are you using (0.5.1 is a most recent bug-fix release)?
Could you please attach a test case that fails with assertions? Also, if you altered source code - could you attach a patch with your changes?
test.zip

Hi Valery,
Yes, I did changes in the library. Please, try the prepared patch which adds a delay to the AbstractCompletableTask.cancel(...) method. The patch was made on your lastest 0.5.1 release.
The test should now fail. At least it fails for me. If it won't fail, please, try to make the delay longer.
Cheers, Adam
tascalate-concurrent-cancel-failure.patch.zip

Moreover, your code enables me to extend this cancellation ability such that I could cancel the whole tree of underlying tasks which the "root" task depends on. This extension is currently in progress, and when finished I would like to share it with you. Would you be interested?

Could you elaborate more with what you try to get as final result? Preferably, with some (pseudo-) code?
Because functionality provided with class Promises (see methods all,  any, atLeast) already provide combinators with such cancellation capability...

Yeah. I will try to describe it.
Promise<T1> p1 = CompletableTask.complete(...)
    .thenApplyAsync(... Task 1 ...);
Promise<T2> p2 = p1.thenApplyAsync(... Task 2 ...);

return p???

Now I would like be able to return one Promise which would cancel (or prevent starting) both Task 1 and Task 2. If I return p2, I will not be able to cancel p1 if it will be still running. On the other hand when returning p1, I will not be able to cancel p2 after p1 completes.
Looking into Promises once again it seems that my goal could be achieved using it with caveats. I could create the all promise pMulti. The issue is here that I would get a list of results which I see inconvenient when creating and API which should expose only, e.g., last result. First, if I would wrap pMulti promise into a new promise pLast then again I would not be able to cancel pMulti by cancelling pLast. This could be solved by providing a new specialized Promise implementation. Second, all my promises which I would like to be to cancel their tasks would need to share a common super type among their results.
Did a make a mistake in my reasoning somewhere?
My implementation is almost complete. I will share a patch with you and you can decide whether it makes sense or not.

Now I would like be able to return one Promise which would cancel (or prevent starting) both Task 1 and Task 2. If I return p2, I will not be able to cancel p1 if it will be still running. On the other hand when returning p1, I will not be able to cancel p2 after p1 completes.

If you cancel p1  in your example then p2 will be completed with CompletionException (with CancellationException as a cause) as well. And the corresponding thread will be interrupted!
Please add the following to your test and see:
        p2.whenComplete((r, e) -> {
           if (null != e) {
               System.out.println("P2 Exception!");
               e.printStackTrace(System.out);
           } else {
               System.out.println("P2 Result: " + r);
           }
        });

So I see no need for extra behavior besides provided (and specified in CompletionStage API)

Yeah, but this does not test the case when p1 already completed and p2 started. In this case I want to be able to cancel also p2 but p1 already completed normally so it would not make sense to change its completion status to exceptional completion.
This is the right test to see the behaviour:
@Test
public void testChainCancellation() {
    State s1 = new State();
    State s2 = new State();

    Promise<?> p1 = CompletableTask.asyncOn(executor)
            .thenRunAsync(() -> longTask(5, s1));

    // This stage should not be executed, previous stage will be cancelled
    Promise<?> p2 = p1.thenRunAsync(() -> longTask(5, s2));

    p2.whenComplete((r, e) -> {
        if (null != e) {
            System.out.println("P2 Exception!");
            e.printStackTrace(System.out);
        } else {
            System.out.println("P2 Result: " + r);
        }
    });

    // Let the Task 1 complete normally
    trySleep(8);
    p1.cancel(true);
    trySleep(1);

    assertTrue("Expected s1 done, but is " + s1, s1.isDone());
    // This assertion also fails, uncommment to see
//        assertTrue("Expected s2 cancelled, but is " + s2, s2.isCancelled());

    // Wait Task 2 to complete as it was NOT cancelled
    trySleep(2);

    assertTrue("Expected s2 cancelled, but is " + s2, s2.isCancelled());
}

Here tascalate-concurrent-recursive-cancel.patch.zip is the patch for 0.5.2-SNAPSHOT which adds support for recursive cancellation. I added also a file with tests so that it can be directly taken for a test drive :) The patch already contains the previously discussed bug fix.
You can freely modify the code or decide not to use/merge it in any way.
Cheers, Adam

Adam,
I see your point. However, this somewhat contradicts with CompletionStage API contract -- completion stage may be completed only once, either successfully, or with exception, or cancelled. With your suggestion it's somewhat non-intuitive, especially when there is a race between completion and cancellation.
For now I've created a separate branch for your patch (with the patch applied). However, I would like to avoid mixing your changes with the code that adhere to CompletionStage contract. What I'm suggesting:

Work with the new branch for now.
Refactor AbstractCompletableTask to allow 2 extension hierachies -- the one for previously existed code, and the second for your extension. Please try to keep changes in AbstractCompletableTask to minimum.
Probably it's better to have separate method, cancelRecursive or cancelWithDependencies -- to have a separate execution path for this behavior.

At the end, I'll either include both class hierarchies into lib, or you will end up with good enough superclass(es) to extend the lib and add necessary behavior without patching lib sources.
Thank you for your interest & support,
Valery

Hi Valery,
what is the best way to do what you suggested? Should I fork your repository and create pull request for the new branch? Or should I commit to the new branch directly? I suppose, I should choose the first.

Reopening issue, was closed accidentally.
Transitive cancellation is indeed both practical and challenging topic that should be researched.

Yes, the first
I reviewed your code. There are a lot of questions:

doThenComposeAsync -- tempStage is a predecessor of the nextStage, why it's not listed in dependencies?
A lot of methods, like thenApply or exceptionally don't enlist dependencies at all.
In cancel, if you put onError(new CancellationException()); before cancelling dependencies you probably not need dependenciesMightHaveBeenInterrupted at all.
Why thenCombineAsync has whenComplete handler?

Also, I'm a bit skeptic about thenCombineAsync, applyToEitherAsync etc methods, that takes CompletionStage as an argument. This dependency is not owned exclusively by the newly created Promise. So cancelling them might be dangerous. Actually, no one guarantees that any  Promise here is an exclusive dependency, there are always chances that it's shared. So cancelling it will lead to unpredictable behavior, it would be hard to reason about the program behavior.
Regarding your example.
Promise<?> p1 = ...;
Promise<?> p2 = ...;
Promise<List<?>> cancelationToken = Promises.all(p1, p2);
...
cancelationToken.cancel(true);

This way you can cancel all required promises at once if they are not completed yet. Without any changes to current library code.
Thoughts?

Ad 1. Yeah, it might be more correct if tempStage is also included into dependencies. For my usage, I expected the function fn, which provides the next CompletionStage, to execute quickly.
Ad 2. Not directly, but look into internalCreateCompletionStage(...) implementations. The current completion stage is added as a dependency in this factory method.
Ad 3. If I put onError(...) before cancelling then the tests failed for me. Yet, I don't know exactly why. I will look into it more.
Ad 4. This for the case that the current stage is cancelled. Then I wanted to propagate the cancellation also to provided (combined) completion stage.
I see why are you sceptic. The dependencies might be shared, and in a complex scenario they probably will be. Thus this recursive (or transitive) cancellation would in such cases introduce unexpected behaviour. What about counting dependents? They are known through CallbackRegistry.
Yes, in the way you shown I am able to cancel all the required promises. The problem arises when I want to provide this "all cancelling" promise as a result of an API method. It is incovenient to provide all results (including intermediate) instead of the producet of the whole task chain.

Hi Valery.
I thought about 3. I can call onError(...) before cancelling but I still need to set the mightHaveBeenInterrupted flag even before onError(...). The reason is that when onError(...) is called and there are succeeding stages executed synchronously (such as whenComplete) they are reached recursively from onError(...). This is correct and it is not a problem regarding thread interruption at all. However, it is a problem of my forward-cancelling thenCombineAsync implementation which in this case does not know whether its predecessor could have been interrupted or not. Maybe, I am able to implement it in another way, e.g., I could extend CancellationException and propagate the flag value using it. However, it seems to me that it would be less intuitive to handle the flag in this manner.
Regarding the shared dependencies. Maybe this might be solved by providing new methods that have a new argument (after Execuror) which lets the programmer choose whether he wants to interrupt a possibly shared promise.
prev.thenCombineAsync(CompletionStage<?> other, Executor e, boolean mayCancelOther);

This might be possible by extending Promise into a new interface (let's say Operation) which could also contain a new method cancelRecursive or just cancel with a new parameter, e.g., mayCancelRecursive. In this manner a new extension hierarchy would be created. Is this what you meant?

Adam,
I reviewed thenComposeAsync and understand that I need cancellableOrigins anyway -- at least, for non-exposed helper stages. Please review my code in master branch -- now in thenComposeAsync first tempStage is registered as cancellable origin (so fn.apply() may be interrupted), then result of fn.apply() itself is enlisted.
Regarding your implementation of thenCombineAsync -- I don't understand here why whenComplete is necessary for you. Ain't it simpler to just add other parameter as a dependency to nextStage  ?
Still thinking on extra-methods with explicit parameter to mark cancellable origin...

Adam, please take a look at the following prototype code:
https://github.com/vsilaev/tascalate-concurrent/blob/master/src/main/java/net/tascalate/concurrent/RecursiveCancellationPromise.java
The idea is:
Promise<?> p1 = CompletableTask
     .asyncOn(executor)
     .thenRunAsync(() -> longTask(5, s1));

Promise<?> p2 = RecursiveCancellationPromise.from(p1).thenRunAsync(() -> longTask(5, s2));
RecursiveCancellationPromise.class.cast(p2).enlistCancellableOrigin(someOtherPromiseLikeCombineOrEitherParam):

p2.cancel(true);
// This will cancel p1 and its task, p2 and its task as well as everything explicitly enlisted

Thoughts?

Valery, I did not much today. Probably the only thing that I will have finished today is a test which shows a race in the new implementation of thenComposeAsync. I copy here the comment which I added also to the specific lines into AbstractCompletableTask:
                // TEST: There is a race when fn.apply(r) is completed
                // normally and nextStage is cancelled before returned is set
                // as its nextStage's cancellableOrigins. In this case,
                // execution of returned continues as nextStage cannot be
                // cancelled for a second time. However, completion stages after
                // nextStage are completed exceptionally (correctly) since when
                // moveToNextStage is executed nextStage is already completed
                // (cancelled) from cancel(...) -> onError(...). In order to
                // cancel returned here, I think you need to know whether
                // nextStage might have been interrupted.

I hit this issue before during my implementation and addressed it using the synchronization and possible cancelling using the remembered mayInterrupt... flag.
Here is a test (for master) which fails for me. thenComposeAsync-race-test.zip
Now, I will think about thenCombineAsync more.

Adam,
Thanks, fixed.
Checking nextStage.isCancelled() after resetting cancellableOrigins should work without synchronization, so no extra flags required.
Sleep in AbstractCompletableTask is commented out, so to check test uncomment locally
Regards,
Valery

Looks good. No other sync needed since cancelling can occur before or after reseting cancellable origins, but not in the same time. Sync is implicit due to sync in these methods.

Thanks,
Please look at RecursiveCancellationPromise
This is still work in progress. But! If we can go with such wrapper, with additionally overwritten *Either* and *Both* named methods to enlist CompletionStage parameter -- then I will definitely keep it in library for next release.
Valery

Some thoughts on thenCombineAsync.
Yes, you can add other into cancellableOrigins of nextStage, but they will be also manipulated (reset) in thenComposeAsync. In this manner, reseting could remove other from origins of nextStage. This could be handled by adding. However, it seemed to me quite elegant to implement thenCombineAsync using simpler operations such as internal whenComplete.
What do you think?
Anyway, I also thought about implementing thenComposeAsync using this approach. This could avoid solving sync issues and could make the code more easy to read and also to extend. I worked today on the second extension hierarchy and become stuck on thenComposeAsync since I extracted the new fields (origins, lock) from AbstractCompletableTask to new classes.

I looked at RecursiveCancellationPromise. Do you plan to support fluent style of programming?
I mean this:
RecursiveCancellationTask.supplyAsync(...)
    .thenApplyAsync(...)
    .thenAcceptBothAsync(p, true); // or something like thenAcceptBothCancellableAsync(p)

This seems to me much more easy to work with than keeping explicit references to your cancellable promises. Also, it might be less error prone, e.g., when you forgot to enlist a task.

Adam,
Yes, I've added missing methods, class is renamed to DependentPromise
DependentPromise<?> p1 = DependentPromise.from(someRegularStage);
DependentPromise<?> p2 = p1.thenApplyAsync(fn, true);
// same as p1.thenApplyAsync(fn);
// "this" is enlisted by default;
DependentPromise<?> p3 = p2.runAfterEitherAsync(otherStage, codeBlock);
// same as p2.runAfterEitherAsync(otherStage, codeBlock, PromiseOrigin.THIS_ONLY);
// "this" and only "this" is enlisted by default;
DependentPromise<?> p4 = p2.acceptEither(otherStage, someConsumer, PromiseOrigin.ALL);
// above both "this" and "otherStage" are enlisted
// otherStage will be cancelled if p4 is cancelled.

Please provide your feedback, probably we need nothing else in AbstractCompletableTask.
Plus, this wrapper may wrap anything besides AbstractCompletableTask, incl. standard CompletableFuture/
Regards,
Valery

Hi Valery, this seems the right direction to go.
Today, I don't have much time so I only modified one test and fixed a small mistake in DependentPromise. The first test passes and I expect also the others to pass.
I will be on a vacation during the weekend and will be back on Monday. I suggest that I modify all the other tests so that we can be sure about DependentPromise and I will suggest a DependentTask that would make the creation of the intial DependentPromise more covenient (see CompletableTask.runAsync(...)).
What about calling cancelOrigins(mayInterruptIfRunning = true) in doWrap? Is this ok if you do not known how the dependent promise was cancelled? For my usage, posibility of interruption is needed.
Last small suggestion. What about including a setting similar to defaultExecutor for a DependentPromise, defaultEnlistOrigins?

Today, I don't have much time so I only modified one test and fixed a small mistake in DependentPromise. The first test passes and I expect also the others to pass.

Thank you! The fix is applied.

and I will suggest a DependentTask that would make the creation of the intial DependentPromise more covenient (see CompletableTask.runAsync(...)).

Well, I don't see it should be included in the library itself, any library user can do this for itself on per-case basis (it's just two lib calls, one wrapped into another)

What about calling cancelOrigins(mayInterruptIfRunning = true) in doWrap? Is this ok if you do not known how the dependent promise was cancelled? For my usage, posibility of interruption is needed.

Please elaborate more. It's exactly cancellation of origins with interruption...

Last small suggestion. What about including a setting similar to defaultExecutor for a DependentPromise, defaultEnlistOrigins?

Thought about this.  I'd prefer to keep things explicit while abuse of this feature is quite dangerous. Even adding direct predecessor (as currently implemented) is somewhat dangerous.

What about calling cancelOrigins(mayInterruptIfRunning = true) in doWrap? Is this ok if you do not known how the dependent promise was cancelled? For my usage, posibility of interruption is needed.

Please elaborate more. It's exactly cancellation of origins with interruption...

I thought about a situation when a user wants to cancel a chain of tasks. Let's say we four thenRunAsync tasks from which the T1 is done, T2 is running and T3, T4 are waiting. Currently, you can cancel T3 and T4, and interrupt T2. But what if there is a case that you want to prevent T3 and T4 from running, but you want to let T2 to finish?
I don't see that the second scenario is possible now. Or am I missing something?
Please, see my patch.  tascalate-concurrent-recursive-tests.patch.zip
Also I suggested removing the to Promise cast from DependentPromise.doWrap method. I instead made the type of original parameters of doWrap and wrap stronger regarding type checking. Anyway, you are only able to cancel a task if you know it is a promise, i.e., it implements also Future.

I thought about a situation when a user wants to cancel a chain of tasks. Let's say we have four thenRunAsync tasks (T1-4) from which T1 is done, T2 is running, and T3, T4 are waiting. Currently, you can cancel T3 and T4, and interrupt T2. But what if there is a case that you want to prevent T3 and T4 from running, but you want to let T2 to finish?
I don't see that the second scenario is possible now. Or am I missing something?

``
DependentPromise T1 = DependentPromise.from( CompletableTask.supplyAsync(supplier1, executor) );
DependentPromise T2 = T1.thenRunAsync(run2);
DependentPromise T3 = T2.thenRunAsync(run3, false);
DependentPromise T3 = T3.thenRunAsync(run4, false);
...
T3.cancel(true);
T4.cancel(true);

Ok, but it is not possible to cancel T1 and T2 by using, .e.g, T4 now.
Maybe it is too general scenario which might not occur at all. At least for me it won't. I think you can close the issue now.

Adam,
Big thanks for all the work you did for this issue, and especially for tests.
I'm about to release new functionality -- I decided that all methods inherited from CompletionStage API should not add anything as cancelable origin. Only overloaded method calls should be used, with explicit arguments. I prefer the path of least surprise for the library user: DependentPromise is a Promise, and if it is passed to code that expect Promise (with no cancellation of anything besides the promise itself) it should work like this.
Tests are updated accordingly to use overloaded methods' variants with explicit arguments.
Thank you,
Valery


externalize blacklist

at some point i need to split off the blacklist and store that outside the code

Implemented for v3.2.2


Document Magento2 + Algolia setup

Related to https://gitlab.com/front-commerce/front-commerce/-/merge_requests/981
Main changes visible in:

https://deploy-preview-303--heuristic-almeida-1a1f35.netlify.app/docs/magento2/search-engine.html#Algolia
https://deploy-preview-303--heuristic-almeida-1a1f35.netlify.app/docs/appendices/migration-guides.html#2-12-0-gt-2-13-0

This MR was targetting main by mistake, the main commit has been reverted on
main and the branch manually merged into next


text disappears if @xml:lang in children of div[@type="edition"]

The text disappears if @xml:lang is put either on a div[@type="textpart"] or ab. I tried putting it both on div[@type="edition"] and "textpart"/ab for the experiment, and it doesn't appear. Seems like the only possibility is to have it on div[@type="edition"].
Needs fixing for cases of multiple languages in one inscription.

This is controlled in stylesheets/epidoc/prune-to-language.xsl, and further exceptions to the general rule should be added there. It may be that the existing template there should be changed to use xsl:copy-of to pull in all of the content regardless of language.

I changed the first line of the template to say <xsl:template priority="10" match="tei:div[@type='edition'] | tei:div[@type='textpart'] | tei:ab"> and it works. If this seems fine to people, I can commit. If you think it's neater to do xsl:copy-of, can try that too.

There are three considerations:

Can tei:div[@type='textpart'] or tei:ab occur in contexts outside of tei:div[@type='edition']?
Are there any other places within tei:div[@type='edition'] where a different xml:lang may be set (except on tei:foreign) and which should be displayed?
Conversely, are there any occasions in which part of a tei:div[@type='edition'] should not be displayed because it is in a different language?

If just the first has a positive answer, then you can just prepend "tei:div[@type='edition']//" to the two XPaths you added. If just the second has a positive answer, then the xsl:copy should be replaced by xsl:copy-of matching just on tei:div[@type='edition'].

Yes, occasionally.
Yes in theory, but I can't predict where at the moment. We can either use xsl:copy-of as you suggest, or wait until further examples arise and add them to the template as required.
Pretty definitely no. Any other div, yes, but edition (and descendents) no.

@simonastoyanova @ajenhl: what is the status of this ticket? Is everything working as it should be?
I was wondering if a solution might be to list the "suppressable" languages (languages of the edition, rather than of the texts) somewhere, and only supress those for i18n purposes. (I.e. a corpus might include inscriptions and parts of inscriptions in Greek, Latin, Hebrew, Old Church Slavonic, and Medieval Persian, and the edition might be bilingual in English and Russian. It is only the latter two languages that should trigger suppression/display in i18n function; all others should appear ubiquitously, whether in edition or elsewhere.)

Another related issue is that EFES by default is not displaying the content of xml files whose <TEI> element has an @xml:lang attribute with a value different from the default language, i.e. 'en'.


Update description for Grant module

:wave: I decided to update the description of my OAuth client, that I initially added to this list in 2015 https://github.com/sindresorhus/awesome-nodejs/pull/230
A lot have changed since then, and so I though that it might be useful to outline the key selling points as of today, because that might be useful information for anyone searching for such solution.
Main difference is that Grant now ships with 4 serverless handlers, making it a viable solution for Lambda Functions, and then I also added a handler for Fastify.

Sounds good, thanks @sindresorhus :+1:


Update README.md

Added section for Community Dashboard

The link open "Page 5" - So conceived?

@iSazonov that seems to be a behavior of PowerBI.  I actually rearranged the pages so that "Page 1" showed first, but it seems to default to the most recently edited page.

Thanks! I think this is not a problem.

Looks good, but maybe you could add a link to your blog explaining why and how it works?

For more information on how and why we built this dashboard, check out this blog post.

@SteveL-MSFT I don't want open an Issue. It seems the dashboard sums by month for all years. I see this on Page 1 (Top community contributorsover last 30 days ) in "PRs Opened" and "PR Comments" columns.

@iSazonov ..........oh. hm. let me look into that. good catch!


System crash/freeze due to full RAM/swap when restoring from snapshot

OS
openSUSE Tumbleweed x86_64
Versions
cardano-db-sync 13.0.0 - linux-x86_64 - ghc-8.10 git revision 67367b5ae317b2915de94dc3be43c29d796d876e
postgres (PostgreSQL) 14.4
Build/Install Method
nix (following building-running.md)
Run method
run.sh and restore.sh in attachments (running seems fine)
Additional context
When restoring the snapshot, my /tmp would fill up and my system would either crash or the process would give me an error saying there's not enough space left on device. (I fixed this by increasing the size of my /tmp)
Now, however, when I try to restore using the snapshot, my swap slowly fills up, my system grinds to a halt and eventually freezes (I have to reboot).
It can chug along for quite a while (1h+?) with swap hovering around 60+GB, growing and shrinking slightly, but filling up eventually.
Perhaps it's possible I have messed something up when I was trying to resize /tmp, but I find it unlikely.
It's possible the swap filling issue was present even before I have resized /tmp.
RAM/swap usage reported by htop doesn't seem to change after I terminate the execution. (They are not freed up)
htop reports RAM usage that's typical for my system (in this case it's 14GB since I'm also running a cardano-node, but the desktop widget reports usage of 30.4GB)
I have 32GB RAM, 64GB swap, over 1TB free space on the drive, filesystem is btrfs.
Below are some files that might come in handy, I can provide more on demand.
Problem Report

df.txt (output from ´df -a´, potentially relevant)
restoring.txt (all seems good here, AFAICT)
restore.sh.txt
run.sh.txt (should not be relevant to the issue)

That screenshot shows that your issue is with Xorg using up most of your RAM - which , as you'd see on searching stackoverflow is a common trouble when associated with storage device. Unrelated to dbsync itself

That screenshot shows that your issue is with Xorg using up most of your RAM - which , as you'd see on searching stackoverflow is a common trouble when associated with storage device. Unrelated to dbsync itself

The issue I have ONLY happens when I run ´restore.sh´ tho. (As soon as I run it, RAM/swap start filling up at a decently worrying rate)
It's certainly possible the issue is not with db-sync itself, but I find it hard to believe.

It's certainly possible the issue is not with db-sync itself, but I find it hard to believe.

The more you use storage R/W , higher memory being used, it is exactly as some of the other posts (besides, you're simply doing a restore (uses psql against postgres db, has not even reached dbsync yet 🙂 )

Dang, OK, I'm just completely guessing with my quite limited Linux knowledge, but is there any chance this is related to btrfs?

@rdlrt I added top.txt which might be useful, I guess.

Prolly best handled on stackoverflow instead dbsync github, but for starters you might want to use system without X11

Alright, thank you! Should I close this issue then?

SOLVED: Inserting TMPDIR=/var/tmp as the first thing in the restore.sh file seems to resolve the issue. This forces the application to use the hard drive for storing temporary files instead of RAM and swap.


TFTP improvements

added transfer mode check
added configurable TFTP timeout and retransmissions (library only)
fixed a bug in connection dropping if timeout reached

This looks generally good, I've added a few line comments on a few sections.

Looks good to me. @mmattioli Any comments?

@psychomario LGTM! :+1: @pbertera, just for your own future reference, create separate feature branches for your pulls because then they can be deleted after they're merged and you can create fresh new ones that are automatically based off of the newly updated main branch in the repo. It's more for your own organization than ours but good practice in general. I noticed you reused your development-logging branch for this pull, next time maybe use something along the lines of development-short-patch-name.


[windows] error - can't find dependency language_js

scoop install pragtical --global
scoop install https://gist.githubusercontent.com/maksimaliabyshev/6b311f327078022dd365eea96f2428e8/raw/pragtical-plugin-manager.json --global

ppm --version
1.2.9-x86_64-windows
ppm reinstall lsp lintplus snippets lsp_snippets lsp_* --assume-yes  --progress

warning: ayu-mirage stub on https://github.com/pragtical/colors.git:master has differing version from remote (1.0 vs 0.1); may lead to install being inconsistent
Uninstalling lsp will uninstall the following orphans: lintplus, lsp_snippets. Do you want to continue? [Y/n]: Y
Uninstalling plugin located at C:\Users\ma\.config\pragtical\plugins\lintplus
Uninstalling library located at C:\Users\ma\.config\pragtical\libraries\json.lua
Uninstalling plugin located at C:\Users\ma\.config\pragtical\plugins\lsp_snippets.lua
Uninstalling plugin located at C:\Users\ma\.config\pragtical\plugins\lsp
lsp is depended upon by lsp_tex. Remove as well? [Y/n]: Y
Uninstalling plugin located at C:\Users\ma\.config\pragtical\plugins\lsp_tex
Uninstalling plugin located at C:\Users\ma\.config\pragtical\plugins\snippets.lua
Installing complex plugin lintplus.
json is an optional dependency of lsp_snippets. Should we install it? [Y/n]: Y
Installing singleton library json.
Installing singleton plugin snippets.
Installing singleton plugin lsp_snippets.
Installing complex plugin lsp.
Installing complex plugin lsp_tex.
can't find dependency language_js

installed default language_js 3.5.0-jit status:core

Did you tried this https://pragtical.dev/docs/user-guide/plugins#troubleshooting ?

Did you tried this https://pragtical.dev/docs/user-guide/plugins#troubleshooting ?

tried it, this command removed folder "C:\Users\YourUserName.config\pragtical\ppm"
ppm purge

same error
 2.3 MB [   2.9 MB/s][100%]: Fetching https://github.com/pragtical/plugin-manager.git:latest...
 337.8 kB [   1.1 MB/s][100%]: Fetching https://github.com/pragtical/plugins.git:master...
  53.1 kB [ 565.5 kB/s][100%]: Fetching https://github.com/pragtical/colors.git:master...
   4.5 kB [   1.7 MB/s][100%]: Fetching https://github.com/chqs-git/code-plus.git:b336999b707709df2ddcb865f664623c5beceabb...
warning: Can't find manifest.json for https://github.com/chqs-git/code-plus.git:b336999b707709df2ddcb865f664623c5beceabb; automatically generating manifest.
warning: codeplus stub on https://github.com/pragtical/plugins.git:master has differing version from remote (1.0 vs 0.1); may lead to install being inconsistent
   6.2 kB [   2.7 MB/s][100%]: Fetching https://github.com/pragtical/console:66ded63e95aad7be78ae44040fbb5f647a0c0ea0...
warning: Can't find manifest.json for https://github.com/pragtical/console:66ded63e95aad7be78ae44040fbb5f647a0c0ea0; automatically generating manifest.
warning: console stub on https://github.com/pragtical/plugins.git:master has differing version from remote (0.2.1 vs 0.1); may lead to install being inconsistent
 166.3 kB [ 711.6 kB/s][100%]: Fetching https://github.com/FilBot3/lite-xl-language-containerfile:ae4eddc3f3fa1a0db56344b3b6db0ec0f2283880...
warning: Can't find manifest.json for https://github.com/FilBot3/lite-xl-language-containerfile:ae4eddc3f3fa1a0db56344b3b6db0ec0f2283880; automatically generating manifest.
   2.9 kB [   2.6 MB/s][100%]: Fetching https://github.com/Tamnac/lite-plugin-crystal:1913a6dd23a7640b507943230291a15aecc3235d...
warning: Can't find manifest.json for https://github.com/Tamnac/lite-plugin-crystal:1913a6dd23a7640b507943230291a15aecc3235d; automatically generating manifest.
   1.9 kB [   1.6 MB/s][100%]: Fetching https://github.com/Tamnac/lite-xl-djot:e92ad996aba56c3363ef83a2dd8d1026be56c730...
warning: Can't find manifest.json for https://github.com/Tamnac/lite-xl-djot:e92ad996aba56c3363ef83a2dd8d1026be56c730; automatically generating manifest.
   4.8 kB [   3.8 MB/s][100%]: Fetching https://github.com/anthonyaxenov/lite-xl-env-syntax:89a4274af6a786963930d7a8fb542dfe61daa801...
warning: Can't find manifest.json for https://github.com/anthonyaxenov/lite-xl-env-syntax:89a4274af6a786963930d7a8fb542dfe61daa801; automatically generating manifest.
   2.7 kB [   1.9 MB/s][100%]: Fetching https://github.com/anthonyaxenov/lite-xl-ignore-syntax:3a9a5e0ae03b82358473da5d1c6012944d65ea95...
warning: Can't find manifest.json for https://github.com/anthonyaxenov/lite-xl-ignore-syntax:3a9a5e0ae03b82358473da5d1c6012944d65ea95; automatically generating manifest.
  23.4 kB [ 316.5 kB/s][100%]: Fetching https://github.com/programutox/lite-plugin-vale:faa75f67b093978ceebc31bb7db8aa297f3c3e52...
warning: Can't find manifest.json for https://github.com/programutox/lite-plugin-vale:faa75f67b093978ceebc31bb7db8aa297f3c3e52; automatically generating manifest.
  61.8 kB [ 389.1 kB/s][100%]: Fetching https://github.com/liquidev/lintplus:56d229abb6d73519e356bc1aa2dac85f4292e2da...
   3.4 kB [   3.0 MB/s][100%]: Fetching https://github.com/sheetcoder/lorem:b2da386519850d6f91ef67097e50141b3b11a90e...
warning: Can't find manifest.json for https://github.com/sheetcoder/lorem:b2da386519850d6f91ef67097e50141b3b11a90e; automatically generating manifest.
 993.4 kB [   2.3 MB/s][100%]: Fetching https://github.com/pragtical/lsp:a13dfee696a929714e356343b27e049499f25f4c...
  26.4 kB [ 384.7 kB/s][100%]: Fetching https://github.com/vqns/lite-xl-snippets:1f0bba02bb3af6df9cb2ce72526851b427caf143...
  36.9 kB [   1.6 MB/s][100%]: Fetching https://github.com/lite-xl/lite-xl-lsp-servers.git:752ec6e3b9280425a5190ec69cf1b8bc6432136c...
 723.2 kB [   1.9 MB/s][100%]: Fetching https://github.com/juliardi/lite-xl-ayu-theme.git:33a514527d4870480554771c273e667eb6418873...
warning: Can't find manifest.json for https://github.com/juliardi/lite-xl-ayu-theme.git:33a514527d4870480554771c273e667eb6418873; automatically generating manifest.
warning: ayu-mirage stub on https://github.com/pragtical/colors.git:master has differing version from remote (1.0 vs 0.1); may lead to install being inconsistent
 482.7 kB [   1.2 MB/s][100%]: Fetching https://github.com/RohanVashisht1234/justperfect:1e055edd82fb672bfe82e26d2e920a022e601fd5...
warning: plugin lsp already installed
warning: plugin lintplus already installed
warning: plugin snippets already installed
warning: plugin lsp_snippets already installed
  34.8 kB [   1.4 MB/s][100%]: Fetching https://github.com/lite-xl/lite-xl-lsp-servers:89efc5642cb9abcd9023c8e5ef3dba85b399884e...
can't find dependency language_js

Couldn't reproduce here, so my next guess is that scoop installs pragtical to a location that can't be found by ppm which causes the error of not finding language_js,  but I was slow to notice this (sorry). To fix you should give additional parameters to ppm for it to be able to locate the system dependencies. Flags that should get you going as documented on the plugin manager help output:
--datadir=directory      Sets the data directory where core addons are located
                         for the system pragtical.
--binary=path            Sets the pragtical binary path for the system pragtical.

Now I should document this on the website scoop section...
Also, thanks to this I noticed that needed allowing skipping of argument flags for subcommands that may not register them directly using the core.cli interface like the plugin manager access thru pragtical pm, which I will fix for next release thru pragtical/pragtical#192 and a modification to the plugin_manager/init.lua to use the new option.

Couldn't reproduce here

Did you use the --global parameter?
scoop install pragtical --global
scoop install https://gist.githubusercontent.com/maksimaliabyshev/6b311f327078022dd365eea96f2428e8/raw/pragtical-plugin-manager.json --global

Pragtical will be installed in C:\ProgramData\scoop\apps\pragtical\current\
ppm correctly detects pragtical, in console work command pragtical and ppm
PowerShell Administration Rights
ppm reinstall lsp lintplus snippets lsp_snippets lsp_* --assume-yes  --progress --datadir="C:\ProgramData\scoop\apps\pragtical\current\data"

ppm searches the profile for some reason, ignoring the parameter datadir
error - doesn't convert double quotes correctly "C:\ProgramData\scoop\apps\pragtical\current\data"
ppm reinstall lsp lintplus snippets lsp_snippets lsp_* --assume-yes  --progress --datadir='C:\ProgramData\scoop\apps\pragtical\current\data'

Ignoring the parameter --datadir.
Installed sucesss, in user profile C:\Users\ma\.config\pragtical\
ppm reinstall lsp lintplus snippets lsp_snippets lsp_* --assume-yes  --progress --datadir='C:\ProgramData\scoop\apps\pragtical\current\data' --binary='C:\ProgramData\scoop\apps\pragtical\current'

Ignoring the parameter --datadir, --binary.
Installed sucesss, in user profile C:\Users\ma\.config\pragtical\
ppm reinstall lsp lintplus snippets lsp_snippets lsp_* --assume-yes  --progress --datadir='C:\ProgramData\scoop\apps\pragtical\current\data' --binary='C:\ProgramData\scoop\apps\pragtical\current\pragtical.exe'

Ignoring the parameter --datadir, --binary.
Installed sucesss, in user profile C:\Users\ma\.config\pragtical\

So basically specifying --datadir is enough to get it working right? Tested on the Win partition and seems the case, now this needs to be documented on the scoop or plugin manager section of the pragtical website for installations of the editor on non standard locations.
Thanks for the tests! This also inspired pragtical/pragtical#199 which will introduce a pragtical.com console mode binary wrapper around pragtical.exe to allow normal access to the cli interface when using CMD or PowerShell under windows.

Added solution to plugins troubleshooting section of website:
https://pragtical.dev/docs/user-guide/plugins#ppm-installed-from-scoop-fails-to-install-plugins


Object detection and Semantic segmentation

@vandit15  thanks for open-sourcing the code , is it possible to use Cb loss in the object detection or segmentation architecture ?? did you experiment  it with any std architecture as yolo retina, deeplab ?? since i am planning on using to our custom object detection architecture so

I have the same question, I have implemented it on SSD and the loss works, If I need to do six categories classification, my category number would be seven because there is one more 'background' class. But I couldn't get the number of samples of this class. I am so confused


Proposal for a material search tool based on shaders

Describe the problem
Sometimes I lost track of which parameter I was using as the number of material parameters increased.
So I have created a simple material search tool for myself first .

This little tool is more useful than I thought to me and I would love to contribute I hear your input.
Describe the solution you'd like
If you find this feature useful.
This is currently the shortest tool I have created for my own use.
I would like to clean up this tool as well as other MRGT codes, and also improve the EditorGUI layout by referring to measure tools.
Describe alternatives you've considered
Additional context
https://github.com/HoloMoto/MixedReality-GraphicsTools-Unity/tree/holomoto/MaterialSearch
You can try it out at this brunch.
The changes are in com.microsoft.mrtk.graphicstools.unity/Editor/Utilities/MaterialSearcher.cs
The new version is.
If you put this in the appropriate UnityPakcage, you can try it out.
You can check it from the world menu under Window/Graphics Tools/Material Search by Shader.
It's currently a prototype for my own use, so it may be difficult to use, but I think you get the idea of the functionality I'm suggesting!

This looks wonderful! I'd be happy to merge this into Graphics Tools if you create a pull request.

@Cameron-Micka
Thank you Cameron-san! and Happy new year!
I'm new to extending the editor to create such a tool so I'll make some adjustments and push!
I will can get a PR out within a week or two!
I would like to get reviews and feedback from everyone at that time.

That sounds great, happy new year!


Hide MacroCallLoc outside hir_expand

This PR refactor MacroCallLoc such that it  be hided to become implementation details of hir_expand.

Nice!
bors r+


Create a logo

We cannot have the eye of the jailer as a logo forever. We should have a nice logo that fits the name "raidsimp".

Released in 1.0.0


Update documentation texts

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind documentation

What this PR does / why we need it:
Fixes the following

typos , formatting , verbosity , 3rd person
Which issue(s) this PR fixes:

Fixes #85
Test Report Added?:

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind TESTED

Test Report:

Special notes for your reviewer:

@kumarashit @skdwriting @anvithks Please review .


Relative paths

Codecov Report

Merging #125 (2cfdf84) into master (35d4785) will decrease coverage by 0.02%.
The diff coverage is 96.15%.

@@            Coverage Diff             @@
##           master     #125      +/-   ##
==========================================
- Coverage   98.32%   98.29%   -0.03%
==========================================
  Files          59       59
  Lines        3100     3110      +10
==========================================
+ Hits         3048     3057       +9
- Misses         52       53       +1

Flag
Coverage Δ

network
36.49% <26.92%> (-0.06%)
:arrow_down:

unit
98.13% <96.15%> (-0.03%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.


Support Snap package

Hello! Thanks for kubepug
Could project create snap package?

Hey @patsevanton thanks for using the project.
I need to take a look on how to do it. (and also on brew probably!) Do you have any clues? :D Thanks!

@patsevanton started to implement this, I have already reserved the snap name kubepug and was able to build it successfully.
I just need to get my snap login working somewhere here, as my remote build machine is not able to get logged in correctly, then after publishing the first package the other ones should be automatic

Snap is available now at https://snapcraft.io/kubepug and being built linked to the repo, thanks for using the project!


Hooked up buttons for create/edit user forms.  Fixed issue with admin…

… toggle on edit user form submission.  Temporary fix for issue where static pages weren't being rendered

Closing this in favour of recent commits making these enhancements. Thanks for your efforts but too PR required a lot of changes.