Semantic predicate for CCG parser

A little bit of the background: I was one of the @ewan-klein's student that extended the CCG parser in 2009. Sadly, the code was never merged. But I'd like to make the work into the codebase.
The extension included:

Semantic predicate calculation
Probability calculation
Feature value -- right now we have NP[sg]. But NP[num=sg] or NP[num=?x] (variable-value) are better because it fits better with the word the -> NP[num=?x]/NP[num=?x]
Packed chart technique

We can talk about those in detail later and discuss whether or not to integrate a feature. For example, the packed chart technique is an optimisation that removes some similar parses, so it might not be useful for educational purpose.
I'd like to integrate the above features one-by-one in order to avoid driving reviewers crazy. And it's probably better for code quality maintenance as well.
So, first I'd like to start with semantic predicate calculation.
Here's how the lexicon should look like:
    :- S, NP, N
    TransVsg :: (S\NP[sg])/NP {sem=\x y.SYM(y,x)}

    She => NP[sg] {sem=she}
    has => TransVsg  {sym=have}
    a => NP[sg]/N[sg] {sem=\x.one(x)}
    book => N[sg] {sem=book}

and here's how the output should look like:
       She                         has                                   a                         book
 NP[sg] {she}  ((S\NP[sg])/NP) {\x y.have(y,x)}  (NP[sg]/N[sg]) {\x.one(x)}  N[sg] {book}
------------------------>T
(S/(S\NP[sg])) {\T.T(she)}
-------------------------------------------------------------------->B
                      (S/NP) {\x.have(she,x)}
                                                                    ------------------------------------------------------------------>
                                                                                NP[sg] {one(book)}
-------------------------------------------------------------------------------------------------------------------------------------->
                                                       S {have(she,one(book))}

Here are questions I'd like to address:

Should we integrate the semantic predicate calculation at all? Would it be useful?
Does the formalisation of semantic predicate look good?
Should the semantic predicate be optional (on the lexicon level)? I lean toward making it optional because it'll be annoying to force everyone to use the semantic predicate. On another hand, it makes the code more complicated.

Thank you!

The semantic predicate computation is merged #1321


Set status of application through request

by placing a request in the /applications/$id/requests/ path the node worker will see it and make the change, creating the proper timestamp and recording who made the change. as well as sending out any notifications needed.

Actually admin have the ability to write to the /meta/statuses/ leaf so we save the time and who.. and since /requests/ path is writable by non-admins it would cause problems if applicants could accept their own application!


Fix model order

I noticed all electricity activities had the world average (!), and noticed the order of the models was wrong.
Also noticed the hotel key hadn't been migrated.

I don't think this is why the world-average fallback is in use though, as we have the following in the app:
export const carbonModels = [
  // will try to run carbonModels in this order
  // Remember to change increment below, when the order has changed
  electricityCarbonModel,
  ...contribCarbonModels,
];

You're right! Let me do a bit more investigating

Double checked - you're right.
The fallback model is actually used because the electricityMap API reports an error (not enough data available to compute a daily average).
So it makes sense!
I still think the PR applies as I moved the purhcase model down the list.
The rationale is that CO2 models based on $ amount should have the least priority, given that someone could take a flight purchase and then add airports, which would warrant using the flight model instead!

Sure thing! We will have to update the selectorVersion as well in app, but it can wait a bit since we can't bump contrib yet due to eslint changes :)

yup!


GitHub Actions security hardening for this repository

Introduction
I think I found some things for you to look into. I've linked to relevant documentation so you can review the docs and decide what to do. 😉
Things to check
pull_request_target in workflow files
You're using pull_request_target in your workflow files, for example:
https://github.com/dangoslen/dependabot-changelog-helper/blob/4735b98713bc2d4ae49f00221196489900f47a6c/.github/workflows/pull-request.yml#L3
This may be dangerous. Here's a quote from GitHub's security lab blog post: ^security-lab

TL;DR: Combining pull_request_target workflow trigger with an explicit checkout of an untrusted PR is a dangerous practice that may lead to repository compromise.

Manually approve workflow run from public forks
You may want to require manual approval before a workflow runs from a public fork. Quote: ^gh-docs-workflow-approval

Anyone can fork a public repository, and then submit a pull request that proposes changes to the repository's GitHub Actions workflows. Although workflows from forks do not have access to sensitive data such as secrets, they can be an annoyance for maintainers if they are modified for abusive purposes.
To help prevent this, workflows on pull requests to public repositories from some outside contributors will not run automatically, and might need to be approved first. By default, all first-time contributors require approval to run workflows.
Note
Workflows triggered by pull_request_target events are run in the context of the base branch. Since the base branch is considered trusted, workflows triggered by these events will always run, regardless of approval settings.

Because you're using pull_request_target the workflow ran immediately on my PR, as mentioned in the quote above.
Security hardening for GitHub Actions
GitHub has good documentation on how to improve the security hardening of your actions. ^gh-docs-security-hardening

This guide explains how to configure security hardening for certain GitHub Actions features.

Hey @HonkingGoose! Thank you for raising this.
I'm aware of these issues and have implemented them in other repos.. just haven't fully gotten around to this one. I should have time this week to address them and get it complete
And thank you for your PR!

You're welcome! 😄 I'll let you fix these things then. 😉


Bug 2036194: Rename name to Data Foundation

/approve
/hold
waiting for PX confirmation

/hold cancel

/lgtm

/cherry-pick release-4.10

can we please backport this to 4.10


Lists module 2 different views.

When you create a new list item in the admin by it's submenu item, it still shows the admin menu, see:

When you first go to the List and then create a new list item (from top right corner), see:

it creates a fullscreen overlay and you can't see the admin menu anymore. This is inconsitent, see:

Looks legitimate, but I don't understand the issue, would you mind joining us during a meeting and show what your problem is?


Unable to connect to Meet

Meet does not send a pop-up that connects the wallet with UI, instead, an endless download of the connection occurs.
Reproducible on 54b729c / 0.4.2 , wallet commit cee877f / v.0.7.0

Tested on 48f49ed / 0.5.3 and e347f17 / 0.5.3, LGTM. This issue can be closed.


[common/tocketbucket] Switch to benbjohnson/clock

What changed?
Switched from a mix of time.Source and real time.Sleep usage to benbjohnson/clock which provides a better way to wrap time related operations with a testable functionality.

Why?
To avoid time related tests in dependant packages and provide an example for time related test solution.

How did you test it?
unit tests

Potential risks

Release notes

Documentation Changes

I really like this API in most ways (and facebookgo/clock it forked from).  Advancing time also auto-firing related timers and channels and whatnot is a wonderful simplification for many conceptual time-uses, and it prevents firing things in an unrealistic order or forgetting to do related things by accident, and the mock-clock-advancing is very like our client library's time simulation and it speeds things up a TON.
The main complication might be that both facebookgo/clock and benbjohnson/clock are read-only archived repos :|  It does seem simple enough that we could re-implement or fix if necessary, I'm just not sure if there's a "healthy" fork anywhere and it's... somewhat risky in principle to depend on a declared-dead project.  Though the go module proxy should mean we always have access to the contents at least.

oh, I've seen that benbjohnson/clock was used a lot in the monorepo, but I've tried writing a test around consume, and it is hard (catching that we've started waiting is nearly impossible). So it is hard to use for cases with Timers and Sleep.
Ok. I've tried https://github.com/jonboulle/clockwork which looks much easier to use. See new tests for consume.
For future migration possibilities, I've introduced a wrapper layer, though, it complicates implementation traversal a bit.


[DOCS] - Update READMEs with the upcoming furyctl v1.0.0 version

As per title, updating furyctl reference to use the new command structure of the upcoming v1.0.0 version

@sbruzzese902 do not merge this PR yet

Closing without merging


Add support for url in sp_addsubscription backupdevicetype

The stored procedure sp_addsubscription, when using @sync_type = "initialize with backup", supports setting @backupdevicetype to "url".
While migrating our backups to S3-compatible storage, we initially referred to the documentation, which seemed to indicate that the url type was unsupported, leading us to consider some workarounds. However, upon testing with @backupdevicetype = "url", the subscription functioned as expected.

Thanks, @AbbasLB.


Add tests for ExpandableGroup component

We have React Testing Library and Vitest (as a test runner) set up for our components' unit tests.
Tasks:

[ ] Create a <component-name>.test.tsx file
[ ] Run yarn test to start Vitest, it'll automatically run tests when the above file changes.
[ ] Write some tests, aim for 100% code coverage.

Useful links:

Example test file
RTL cheatsheet
RTL tutorial
RTL common mistakes

PR feedback provided in https://github.com/cfpb/design-stories/pull/65


Uploading, unzipping, parsing, and inserting user files to Database

Description
This is a draft. Please do not allow it to be reviewed for a merge request yet. I or TJ will do that when it's ready.
Working off from this trello card
Finish-line:
File is successfully uploaded on the endpoint url.
We can unzip file, read and parse the CSV.
Mapping datapoints to correct and expected names.
Successfully entered into ds model, which should return predictions.
Give predictions back to user.

Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Change Status

[ ] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] There are no merge conflicts

TJ created a different branch that is for this same purpose.


test-branch/execute-job/wrong-commit-sha-on-pr/d30d66a4-4b31-4231-9929-bb0fdefd6fee

PR for testing 9978754ca88c9063e6c10997bdeb0d7d128e0a9d

/canonical/self-hosted-runners/run-workflows 931ad21dd9ace68aaa0a7d341e94de96ad93fa6b


Check shell instead of terminal profile

Codecov Report

Merging #8340 (0e8ce56) into main (7406de0) will decrease coverage by 0%.
The diff coverage is 33%.

@@          Coverage Diff          @@
##            main   #8340   +/-   ##
=====================================
- Coverage     71%     71%   -1%
=====================================
  Files        374     374
  Lines      23559   23560    +1
  Branches    3625    3625
=====================================
- Hits       16897   16890    -7
- Misses      5203    5207    +4
- Partials    1459    1463    +4

Impacted Files
Coverage Δ

src/client/common/installer/productInstaller.ts
50% <33%> (+<1%)
:arrow_up:

...ascience/notebook/outputs/rendererCommunication.ts
48% <0%> (-14%)
:arrow_down:

...ook/intellisense/pythonKernelCompletionProvider.ts
73% <0%> (-4%)
:arrow_down:

...ent/datascience/jupyter/pythonVariableRequester.ts
65% <0%> (-3%)
:arrow_down:

src/client/datascience/jupyter/kernelVariables.ts
56% <0%> (-2%)
:arrow_down:

.../datascience/notebook/notebookControllerManager.ts
74% <0%> (+<1%)
:arrow_up:

...ience/kernel-launcher/localKernelSpecFinderBase.ts
76% <0%> (+2%)
:arrow_up:


S3 bucket is not accessible

While it is possible to use https://aws-blogs-artifacts-public.s3.amazonaws.com/BDB-3696/dataFeedMskArtifacts.zip
to download artifacts, the same can be done using aws s3 cp
There are missing instructions on how to update properties to use the bucket created via the CF template of the project.

Fixed with new code.


Caching the metadata with additional fields.

This CR fixes the issue when the user calls the first time the
metadata without additional fields and then calls the second time
the same metadata, but with additional fields.
SDK was returning from cache the metadata without additional fields.
For fixing that, we're adding additional fields to the cache key
and the cache will store separate objects for each metadata
request with different params.
Resolves: OLPSUP-11727
Signed-off-by: Oleksii Zubko<EMAIL_ADDRESS>

Codecov Report

Merging #373 into master will decrease coverage by 0.0415%.
The diff coverage is 100.0000%.

@@               Coverage Diff                @@
##             master       #373        +/-   ##
================================================
- Coverage   88.5608%   88.5193%   -0.0414%
================================================
  Files            70         70
  Lines          2133       2134         +1
  Branches        224        225         +1
================================================
  Hits           1889       1889
  Misses          156        156
- Partials         88         89         +1

Impacted Files
Coverage Δ

...aservice-read/lib/cache/MetadataCacheRepository.ts
100.0000% <100.0000%> (ø)

...dataservice-read/lib/client/VolatileLayerClient.ts
82.0513% <0.0000%> (-1.2820%)
:arrow_down:

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 8d50c07...4bd7bfd. Read the comment docs.


vcpkg install benchmark fails Ubuntu 16.04 with clang 6.0.1

I am trying to install benchmark using vcpkg on Ubuntu 16.04 with clang 6.0.1 and it fails. Any insight on how to resolve this would be appreciated.
owe043@bullet-cl:/software/vcpkg$ ./vcpkg install benchmark
The following packages will be built and installed:
benchmark[core]:x64-linux
Starting package 1/1: benchmark:x64-linux
Building package benchmark[core]:x64-linux...
-- Using cached /software/vcpkg/downloads/google-benchmark-v1.4.1.tar.gz
-- Using source at /software/vcpkg/buildtrees/benchmark/src/v1.4.1-c49a4f802a
-- Configuring x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:56 (message):
Command failed: /software/vcpkg/downloads/tools/cmake-3.11.4-linux/cmake-3.11.4-Linux-x86_64/bin/cmake;/software/vcpkg/buildtrees/benchmark/src/v1.4.1-c49a4f802a;-DBENCHMARK_ENABLE_TESTING=OFF;-DCMAKE_DEBUG_POSTFIX=d;-DCMAKE_MAKE_PROGRAM=/software/vcpkg/downloads/tools/ninja-1.8.2-linux/ninja;-DCMAKE_SYSTEM_NAME=Linux;-DBUILD_SHARED_LIBS=OFF;-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=/software/vcpkg/scripts/toolchains/linux.cmake;-DVCPKG_TARGET_TRIPLET=x64-linux;-DVCPKG_PLATFORM_TOOLSET=external;-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON;-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON;-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON;-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE;-DCMAKE_VERBOSE_MAKEFILE=ON;-DVCPKG_APPLOCAL_DEPS=OFF;-DCMAKE_TOOLCHAIN_FILE=/software/vcpkg/scripts/buildsystems/vcpkg.cmake;-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON;-DVCPKG_CXX_FLAGS=;-DVCPKG_CXX_FLAGS_RELEASE=;-DVCPKG_CXX_FLAGS_DEBUG=;-DVCPKG_C_FLAGS=;-DVCPKG_C_FLAGS_RELEASE=;-DVCPKG_C_FLAGS_DEBUG=;-DVCPKG_CRT_LINKAGE=dynamic;-DVCPKG_LINKER_FLAGS=;-DCMAKE_INSTALL_LIBDIR:STRING=lib;-DCMAKE_INSTALL_BINDIR:STRING=bin;-G;Ninja;-DCMAKE_BUILD_TYPE=Debug;-DCMAKE_INSTALL_PREFIX=/software/vcpkg/packages/benchmark_x64-linux/debug
Working Directory: /software/vcpkg/buildtrees/benchmark/x64-linux-dbg
See logs for more information:
/software/vcpkg/buildtrees/benchmark/config-x64-linux-dbg-out.log
/software/vcpkg/buildtrees/benchmark/config-x64-linux-dbg-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:255 (vcpkg_execute_required_process)
ports/benchmark/portfile.cmake:20 (vcpkg_configure_cmake)
scripts/ports.cmake:71 (include)
Error: Building package benchmark:x64-linux failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: benchmark:x64-linux
Vcpkg version: 0.0.113-unknownhash
Additionally, attach any relevant sections from the log files above.
owe043@bullet-cl:/software/vcpkg$ cat /software/vcpkg/buildtrees/benchmark/config-x64-linux-dbg-out.log
-- The C compiler identification is Clang 6.0.1
-- The CXX compiler identification is Clang 6.0.1
-- Check for working C compiler: /software/clang+llvm-6.0.1-x86_64-linux-gnu-ubuntu-16.04/bin/clang
-- Check for working C compiler: /software/clang+llvm-6.0.1-x86_64-linux-gnu-ubuntu-16.04/bin/clang -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /software/clang+llvm-6.0.1-x86_64-linux-gnu-ubuntu-16.04/bin/clang++
-- Check for working CXX compiler: /software/clang+llvm-6.0.1-x86_64-linux-gnu-ubuntu-16.04/bin/clang++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found Git: /usr/bin/git (found version "2.7.4")
-- Performing Test HAVE_CXX_FLAG_STD_CXX11
-- Performing Test HAVE_CXX_FLAG_STD_CXX11 - Success
-- Performing Test HAVE_CXX_FLAG_WALL
-- Performing Test HAVE_CXX_FLAG_WALL - Success
-- Performing Test HAVE_CXX_FLAG_WEXTRA
-- Performing Test HAVE_CXX_FLAG_WEXTRA - Success
-- Performing Test HAVE_CXX_FLAG_WSHADOW
-- Performing Test HAVE_CXX_FLAG_WSHADOW - Success
-- Performing Test HAVE_CXX_FLAG_WERROR
-- Performing Test HAVE_CXX_FLAG_WERROR - Success
-- Performing Test HAVE_CXX_FLAG_PEDANTIC
-- Performing Test HAVE_CXX_FLAG_PEDANTIC - Success
-- Performing Test HAVE_CXX_FLAG_PEDANTIC_ERRORS
-- Performing Test HAVE_CXX_FLAG_PEDANTIC_ERRORS - Success
-- Performing Test HAVE_CXX_FLAG_WSHORTEN_64_TO_32
-- Performing Test HAVE_CXX_FLAG_WSHORTEN_64_TO_32 - Success
-- Performing Test HAVE_CXX_FLAG_WFLOAT_EQUAL
-- Performing Test HAVE_CXX_FLAG_WFLOAT_EQUAL - Success
-- Performing Test HAVE_CXX_FLAG_FSTRICT_ALIASING
-- Performing Test HAVE_CXX_FLAG_FSTRICT_ALIASING - Success
-- Performing Test HAVE_CXX_FLAG_WSTRICT_ALIASING
-- Performing Test HAVE_CXX_FLAG_WSTRICT_ALIASING - Success
-- Performing Test HAVE_CXX_FLAG_WD654
-- Performing Test HAVE_CXX_FLAG_WD654 - Failed
-- Performing Test HAVE_CXX_FLAG_WTHREAD_SAFETY
-- Performing Test HAVE_CXX_FLAG_WTHREAD_SAFETY - Success
-- Performing Test HAVE_CXX_FLAG_COVERAGE
-- Performing Test HAVE_CXX_FLAG_COVERAGE - Success
-- Configuring incomplete, errors occurred!
See also "/software/vcpkg/buildtrees/benchmark/x64-linux-dbg/CMakeFiles/CMakeOutput.log".
See also "/software/vcpkg/buildtrees/benchmark/x64-linux-dbg/CMakeFiles/CMakeError.log".
owe043@bullet-cl:/software/vcpkg$ cat /software/vcpkg/buildtrees/benchmark/config-x64-linux-dbg-err.log
-- git Version: v0.0.0
-- Version: 0.0.0
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES -- failed to compile
-- Performing Test HAVE_STD_REGEX
-- Performing Test HAVE_STD_REGEX
-- Performing Test HAVE_STD_REGEX -- failed to compile
-- Performing Test HAVE_GNU_POSIX_REGEX
-- Performing Test HAVE_GNU_POSIX_REGEX
-- Performing Test HAVE_GNU_POSIX_REGEX -- failed to compile
-- Performing Test HAVE_POSIX_REGEX
-- Performing Test HAVE_POSIX_REGEX
-- Performing Test HAVE_POSIX_REGEX -- failed to compile
CMake Error at CMakeLists.txt:229 (message):
Failed to determine the source files for the regular expression backend
owe043@bullet-cl:/software/vcpkg$ clang++ --version
clang version 6.0.1 (tags/RELEASE_601/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /software/clang+llvm-6.0.1-x86_64-linux-gnu-ubuntu-16.04/bin
From my bashrc (environment variables to ensure I am using clang with its own standard library):
export CC=clang
export CXX=clang++
export CXXFLAGS=-stdlib=libc++
export LDFLAGS=-stdlib=libc++

?
export CC=clang
export CXX=g++

clang ver 5 or ver 7 ?

Hi. I'm using clang 6.0.1 which I downloaded from their website as a pre built binary and includes their standard library which I believe I am using. There are older versions of g++ and clang installed in system locations (via standard package manager installation) but the configure output indicates the version I want is being picked up. Although, maybe I'm getting the wrong standard library???

I installed the pre-built binary from the llvm website but not via the apt package manager. It was just uncompressed into a directory.
I have added the repos for xenial from that website and removed clang and reinstalled it but I still get the same error. Note this is a multi-user system and while I have sudo privileges I am concerned about making system wide changes that will affect other users in surprising ways.
owe043@bullet-cl:/software/vcpkg$ cat /software/vcpkg/buildtrees/benchmark/config-x64-linux-dbg-err.log
-- git Version: v0.0.0
-- Version: 0.0.0
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES
-- Performing Test HAVE_THREAD_SAFETY_ATTRIBUTES -- failed to compile
-- Performing Test HAVE_STD_REGEX
-- Performing Test HAVE_STD_REGEX
-- Performing Test HAVE_STD_REGEX -- failed to compile
-- Performing Test HAVE_GNU_POSIX_REGEX
-- Performing Test HAVE_GNU_POSIX_REGEX
-- Performing Test HAVE_GNU_POSIX_REGEX -- failed to compile
-- Performing Test HAVE_POSIX_REGEX
-- Performing Test HAVE_POSIX_REGEX
-- Performing Test HAVE_POSIX_REGEX -- failed to compile
CMake Error at CMakeLists.txt:229 (message):
Failed to determine the source files for the regular expression backend

It seems to be that my CXXFLAGS is being ignored but not my CXX. If I set
export CXX=clang++-libc++
Everything works as expected. Note:
owe043@bullet-cl:~$ cat $(which clang++-libc++)
#!/bin/sh
clang++ -stdlib=libc++ "$@"

https://github.com/Microsoft/vcpkg/blob/master/docs/users/triplets.md#vcpkg_cxx_flags

root@net:~/tmp/vcpkg# export CC=clang
root@net:~/tmp/vcpkg# export CXX=clang++
root@net:~/tmp/vcpkg# ./vcpkg install benchmark
Your feedback is important to improve Vcpkg! Please take 3 minutes to complete our survey by running: vcpkg contact --survey
The following packages will be built and installed:
    benchmark[core]:x64-linux
Starting package 1/1: benchmark:x64-linux
Building package benchmark[core]:x64-linux...
-- Downloading https://github.com/google/benchmark/archive/v1.4.1.tar.gz...
-- Extracting source /root/tmp/vcpkg/downloads/google-benchmark-v1.4.1.tar.gz
-- Using source at /root/tmp/vcpkg/buildtrees/benchmark/src/v1.4.1-c49a4f802a
-- Configuring x64-linux-dbg
-- Configuring x64-linux-rel
-- Building x64-linux-dbg
-- Building x64-linux-rel
-- Performing post-build validation
-- Performing post-build validation done
Building package benchmark[core]:x64-linux... done
Installing package benchmark[core]:x64-linux...
Installing package benchmark[core]:x64-linux... done
Elapsed time for package benchmark:x64-linux: 3.598 min

Total elapsed time: 3.598 min

The package benchmark:x64-linux provides CMake targets:

    find_package(benchmark CONFIG REQUIRED)
    target_link_libraries(main PRIVATE benchmark::benchmark benchmark::benchmark_main)

export CMAKE_CXX_FLAGS="-stdlib=libc++"
export VCPKG_CXX_FLAGS="-stdlib=libc++"

export CMAKE_C_FLAGS="-stdlib=libc++"
export VCPKG_C_FLAGS="-stdlib=libc++"

root@net:~/tmp/vcpkg# ./vcpkg remove benchmark
Your feedback is important to improve Vcpkg! Please take 3 minutes to complete our survey by running: vcpkg contact --survey
The following packages will be removed:
    benchmark:x64-linux
Removing package benchmark:x64-linux...
Removing package benchmark:x64-linux... done
Purging package benchmark:x64-linux...
Purging package benchmark:x64-linux... done
root@net:~/tmp/vcpkg# ./vcpkg install benchmark --debug
[DEBUG] Using vcpkg-root: /root/tmp/vcpkg
The following packages will be built and installed:
    benchmark[core]:x64-linux
Starting package 1/1: benchmark:x64-linux
Building package benchmark[core]:x64-linux...
[DEBUG] popen(which cmake 2>&1)
[DEBUG] _pclose() returned 0 after   129643 us
[DEBUG] popen("/root/tmp/vcpkg/downloads/tools/cmake-3.11.4-linux/cmake-3.11.4-Linux-x86_64/bin/cmake" --version 2>&1)
[DEBUG] _pclose() returned 0 after  1275742 us
[DEBUG] popen("/root/tmp/vcpkg/downloads/tools/cmake-3.11.4-linux/cmake-3.11.4-Linux-x86_64/bin/cmake" "-DCMAKE_TRIPLET_FILE=/root/tmp/vcpkg/triplets/x64-linux.cmake" -P "/root/tmp/vcpkg/scripts/get_triplet_environment.cmake" 2>&1)
[DEBUG] _pclose() returned 0 after   143463 us
[DEBUG] popen(shasum -a 1 "/root/tmp/vcpkg/triplets/x64-linux.cmake" 2>&1)
[DEBUG] _pclose() returned 0 after   571431 us
[DEBUG] popen(shasum -a 1 "/root/tmp/vcpkg/scripts/toolchains/linux.cmake" 2>&1)
[DEBUG] _pclose() returned 0 after   168370 us
[DEBUG] popen(which ninja 2>&1)
[DEBUG] _pclose() returned 0 after    63512 us
[DEBUG] popen("/root/tmp/vcpkg/downloads/tools/ninja-1.8.2-linux/ninja" --version 2>&1)
[DEBUG] _pclose() returned 0 after   129853 us
[DEBUG] popen(which git 2>&1)
[DEBUG] _pclose() returned 0 after    62551 us
[DEBUG] popen("/usr/bin/git" --version 2>&1)
[DEBUG] _pclose() returned 0 after   174471 us
[DEBUG] system("/root/tmp/vcpkg/downloads/tools/cmake-3.11.4-linux/cmake-3.11.4-Linux-x86_64/bin/cmake" "-DCMD=BUILD" "-DPORT=benchmark" "-DCURRENT_PORT_DIR=/root/tmp/vcpkg/ports/benchmark" "-DTARGET_TRIPLET=x64-linux" "-DVCPKG_PLATFORM_TOOLSET=external" "-DVCPKG_USE_HEAD_VERSION=0" "-D_VCPKG_NO_DOWNLOADS=0" "-D_VCPKG_DOWNLOAD_TOOL=BUILT_IN" "-DGIT=/usr/bin/git" "-DFEATURES=core" "-DALL_FEATURES=" -P "/root/tmp/vcpkg/scripts/ports.cmake")
-- Using cached /root/tmp/vcpkg/downloads/google-benchmark-v1.4.1.tar.gz
-- Using source at /root/tmp/vcpkg/buildtrees/benchmark/src/v1.4.1-c49a4f802a
-- Configuring x64-linux-dbg
-- Configuring x64-linux-rel
-- Building x64-linux-dbg
-- Building x64-linux-rel
[DEBUG] system() returned 0 after 147785430 us
-- Performing post-build validation
-- Performing post-build validation done
Building package benchmark[core]:x64-linux... done
Installing package benchmark[core]:x64-linux...
Installing package benchmark[core]:x64-linux... done
Elapsed time for package benchmark:x64-linux: 2.512 min

Total elapsed time: 2.512 min

The package benchmark:x64-linux provides CMake targets:

    find_package(benchmark CONFIG REQUIRED)
    target_link_libraries(main PRIVATE benchmark::benchmark benchmark::benchmark_main)

[DEBUG] ../src/vcpkg/install.cpp(683)
[DEBUG] Exiting after 151424100 us (151390248 us)

Nope. Still dies.
owe043@bullet-cl:/software/vcpkg$ export CMAKE_CXX_FLAGS="-stdlib=libc++"
owe043@bullet-cl:/software/vcpkg$ export VCPKG_CXX_FLAGS="-stdlib=libc++"
owe043@bullet-cl:/software/vcpkg$ ./vcpkg install benchmark
The following packages will be built and installed:
benchmark[core]:x64-linux
Starting package 1/1: benchmark:x64-linux
Building package benchmark[core]:x64-linux...
-- Using cached /software/vcpkg/downloads/google-benchmark-v1.4.1.tar.gz
-- Using source at /software/vcpkg/buildtrees/benchmark/src/v1.4.1-c49a4f802a
-- Configuring x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:56 (message):
Command failed: /software/vcpkg/downloads/tools/cmake-3.11.4-linux/cmake-3.11.4-Linux-x86_64/bin/cmake;/software/vcpkg/buildtrees/benchmark/src/v1.4.1-c49a4f802a;-DBENCHMARK_ENABLE_TESTING=OFF;-DCMAKE_DEBUG_POSTFIX=d;-DCMAKE_MAKE_PROGRAM=/software/vcpkg/downloads/tools/ninja-1.8.2-linux/ninja;-DCMAKE_SYSTEM_NAME=Linux;-DBUILD_SHARED_LIBS=OFF;-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=/software/vcpkg/scripts/toolchains/linux.cmake;-DVCPKG_TARGET_TRIPLET=x64-linux;-DVCPKG_PLATFORM_TOOLSET=external;-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON;-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON;-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON;-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE;-DCMAKE_VERBOSE_MAKEFILE=ON;-DVCPKG_APPLOCAL_DEPS=OFF;-DCMAKE_TOOLCHAIN_FILE=/software/vcpkg/scripts/buildsystems/vcpkg.cmake;-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON;-DVCPKG_CXX_FLAGS=;-DVCPKG_CXX_FLAGS_RELEASE=;-DVCPKG_CXX_FLAGS_DEBUG=;-DVCPKG_C_FLAGS=;-DVCPKG_C_FLAGS_RELEASE=;-DVCPKG_C_FLAGS_DEBUG=;-DVCPKG_CRT_LINKAGE=dynamic;-DVCPKG_LINKER_FLAGS=;-DCMAKE_INSTALL_LIBDIR:STRING=lib;-DCMAKE_INSTALL_BINDIR:STRING=bin;-G;Ninja;-DCMAKE_BUILD_TYPE=Debug;-DCMAKE_INSTALL_PREFIX=/software/vcpkg/packages/benchmark_x64-linux/debug
Working Directory: /software/vcpkg/buildtrees/benchmark/x64-linux-dbg
See logs for more information:
/software/vcpkg/buildtrees/benchmark/config-x64-linux-dbg-out.log
/software/vcpkg/buildtrees/benchmark/config-x64-linux-dbg-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:255 (vcpkg_execute_required_process)
ports/benchmark/portfile.cmake:20 (vcpkg_configure_cmake)
scripts/ports.cmake:71 (include)
Error: Building package benchmark:x64-linux failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: benchmark:x64-linux
Vcpkg version: 0.0.113-unknownhash
Additionally, attach any relevant sections from the log files above.

Adding to triplets/x64-linux.cmake does work:
set(VCPKG_CXX_FLAGS -stdlib=libc++)
set(VCPKG_C_FLAGS '')

Please open a new issue if this is still a problem for you.
Thanks.


Stronger Verification for Azure Credential Factory test

The test for TokenCredentialFactory will now invoke getToken() on the TokenCredential. This will light up some additional Azure SDK code, and catch defects like this: https://github.com/Azure/azure-sdk-for-java/pull/39002
The defect linked to above will cause AZURE_DEFAULT/auto-detect authentication to fail when a AZURE_CLIENT_SECRET and AZURE_CLIENT_CERTIFICATE are not configured. Users may hit this when attempting to use AZURE_USERNAME and AZURE_PASSWORD for authentication.
Users can work around this by pulling in the latest azure-identity module in their own pom.xml:
    <dependency>
      <groupId>com.azure</groupId>
      <artifactId>azure-identity</artifactId>
      <version>1.12.1</version>
    </dependency>

This is real tricky one to catch! Notice how our CI run did not fail? That's because we have set AZURE_CLIENT_SECRET as an environment variable. When we do that, the DefaultCredential won't attempt to use the AZURE_USERNAME and AZURE_PASSWORD, even though we've set those as environment variables too.
Only way to really verify scenarios like this is to have two separate test runs which use different environment variables. So while the changes in this branch do add some value, they are not doing as much as I had hoped. To truly verify all scenarios, we'll need future work on the CI run. But for now, I'll add this test scenario to the list of those I verify manually before a release (the list already includes interactive authentication methods, might well add this too) .


Expose read only property in the playground-file-editor

My goal is to use this package to create both an interactive demo experience for our component library (built using lit) and to provide inline (non-editable) demo snippets that users can quickly copy paste.
I noticed the playground-code-editor component has a readonly property that is set but it would be nice if the file editor exposed an override to make it always non-editable. If possible maybe hiding the cursor in readonly mode.
Side-note: Is there instructions for contributing to the project and getting it set up locally? I attempted to pull and run the code but wasn't successful getting it running

Sure, adding a readonly property to file-editor makes sense.
If you're interested in contributing, that should be a pretty straightforward feature to add!
I've just sent out https://github.com/PolymerLabs/playground-elements/pull/151 with a quick setup guide for contributors. Here it is rendered: https://github.com/PolymerLabs/playground-elements/blob/c25598bb1f474b6c06640efa2d9f43d0380fb611/README.md#contributing

Awesome! Thanks for adding the contributing section. I'm more than happy to add that in myself

Published in v0.9.4


IndexError choosing receptor reference atoms coming from ligand_2_ref_idxs

Hi, thanks again for putting this together. I'm taking a look at some internal test cases and we're seeing an issue where we get an IndexError when choosing receptor reference atoms. This is coming from the backbone/ligand distance matrix calculation.
Tracing this backwards, inside of septop._setup._setup_system, I see that ligand_2_ref_idxs are offset by the number of atoms in ligand_1:
        ligand_2_ref_idxs = tuple(i + len(ligand_1.atoms) for i in ligand_2_ref_idxs)

At this point, ligand_2_ref_idxs can contain indices that are larger than the number of atoms in ligand 2. That is, if ligand 1 has 10 atoms and ligand 2 has 10 atoms and the ligand_2_ref_idxs starts at [5, 6, 7] (from femto.fe.reference.select_ligand_idxs), it will end up as [15, 16, 17].
Then, when select_receptor_idxs(...) is called for the ligand 2, and then _filter_receptor_atoms(...) is called, the third argument is ligand_ref_idxs[0]. In the hypothetical example, this will be called with 15 for ligand 2. When the distances are calculated:
    distances = scipy.spatial.distance.cdist(
        backbone.xyz[0, rigid_backbone_idxs, :], ligand.xyz[0, [ligand_ref_idx], :]
    )

ligand (which is ligand 2 in our example) is indexed directly by ligand_ref_idx -- which is 15 in our example -- even though the total length of ligand.xyz would be 10. This leads to an IndexError.
It seems like the intended way to index using an already-offset ligand_ref_idx would be in the combined ligand topology. But, oddly, we have run other systems without running into this issue, so I'm questioning whether my understanding of the code is correct. An obvious resolution would be to un-offset the index for ligand 2 at this point, but I'm not certain I have a full grasp of what's going on. Can you comment @SimonBoothroyd on if you've seen this before and if your indexing with the offset index is intentional?

Looking a little further, I think this bug only occurs if you go down the "alternate receptor reference atoms for ligand 2" path and if you avoid that, then you only index into ligand 1. It's this second function call that causes the problem.
        receptor_ref_idxs_1 = femto.fe.reference.select_receptor_idxs(
            receptor, ligand_1, ligand_1_ref_idxs
        )
        receptor_ref_idxs_2 = receptor_ref_idxs_1

        if ligand_2 is not None and not femto.fe.reference.check_receptor_idxs(
            receptor, receptor_ref_idxs_1, ligand_2, ligand_1_ref_idxs
        ):
            _LOGGER.info("selecting alternate receptor reference atoms for ligand 2")

            # Calling `selector_receptor_idxs` with ligand 2 is the issue.
            receptor_ref_idxs_2 = femto.fe.reference.select_receptor_idxs(
                receptor, ligand_2, ligand_2_ref_idxs
            )

It seems like there could be two issues. I think this
femto.fe.reference.check_receptor_idxs(receptor, receptor_ref_idxs_1, ligand_2, ligand_1_ref_idxs)

Should actually be
femto.fe.reference.check_receptor_idxs(receptor, receptor_ref_idxs_1, ligand_2, ligand_2_ref_idxs)

And then this
receptor_ref_idxs_2 = femto.fe.reference.select_receptor_idxs(receptor, ligand_2, ligand_2_ref_idxs)

Should actually be something like
# Reverse the offset
_ligand_2_ref_idxs = tuple(i - len(ligand_1.atoms) for i in ligand_2_ref_idxs)
receptor_ref_idxs_2 = femto.fe.reference.select_receptor_idxs(receptor, ligand_2, _ligand_2_ref_idxs)

I will test.

thanks so much for looking into this @slochower! I think @ajsilveira is planning to take a look at this and your fix!

fixed by #16


Warning with Core 2024.7 deprecated code 2025.1 with fix proposition

Core 2024.7.2
Supervisor 2024.06.2
Operating System 12.4
Interface utilisateur 20240703.0
2024-07-14 11:38:48.172 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'veolia' calls async_add_job, which is deprecated and will be removed in Home Assistant 2025.4; Please review https://developers.home-assistant.io/blog/2024/03/13/deprecate_add_run_job for replacement options at custom_components/veolia/init.py, line 52: hass.async_add_job(hass.config_entries.async_forward_entry_setup(entry, platform)), please create a bug report at https://github.com/kugan49/veolia-custom-component-HACS/issues
2024-07-14 11:38:48.208 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration, veolia with title<EMAIL_ADDRESS>- 063xxxxxxxxxxxxxxx and entry_id: 01a0c7d0cb5caf4c2d1ae3b254200eaa, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead. Please report this issue.
Stack (most recent call last):
File "", line 198, in _run_module_as_main
File "", line 88, in _run_code
File "/usr/src/homeassistant/homeassistant/main.py", line 223, in
sys.exit(main())
File "/usr/src/homeassistant/homeassistant/main.py", line 209, in main
exit_code = runner.run(runtime_conf)
File "/usr/src/homeassistant/homeassistant/runner.py", line 190, in run
return loop.run_until_complete(setup_and_run_hass(runtime_config))
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 674, in run_until_complete
self.run_forever()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 641, in run_forever
self._run_once()
File "/usr/local/lib/python3.12/asyncio/base_events.py", line 1990, in _run_once
handle._run()
File "/usr/local/lib/python3.12/asyncio/events.py", line 88, in _run
self._context.run(self._callback, *self._args)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2099, in async_forward_entry_setup
report(
File "/usr/src/homeassistant/homeassistant/helpers/frame.py", line 151, in report
_LOGGER.warning(msg, stack_info=True)

https://github.com/kugan49/veolia-custom-component-HACS/releases/tag/v1.3.1


Make archetype ready for CentOS 8 and Python3

Some of the role versions have to be fixed once there is a new release of them.

@bellackn since CentOS8 eol is already announced for end of 2021 and based on all the problems we had we CentOS7 and Python 3 I suggest to close this PR and stop supporting CentOS.
See also #41


add btrack to model catalogue

https://github.com/quantumjot/btrack/blob/main/examples/example_tracking_pipeline-features.ipynb


⚠ Bofrost.at has degraded performance

In 2255473, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2199 ms

Resolved: Bofrost.at performance has improved in b22661e after 303 days, 14 hours, 25 minutes.


Problem with the menu on FBI.

FBI acts as if I have "up" pressed on the D-PAD. If I go down and let go it will go to the first option of the menu.
I can select options if I hit A on any of them but the selection doesn't stay still until it has reached the top option of the current menu.
I have a n3ds on arm9lh, latest luma3ds, and sysnand 10.6

Are you sure you aren't accidentally pressing left (page scroll up), up on the circle pad, or touching the screen?

The only recent change that I have made is move from Sysnand+Emunand to Updated sysnand. FBI was installed on Emunand the first time. I have tried without success:

Reinstall FBI.
Install the original Health app and install FBI again.
Recreate the injected FBI app with the original hs.app.
Tested the older version and it has the same problem.

It would seem that the problem is FBI, the thing is that if I start DevMenu or SaveDataFilter it doesn't happen. On the homemenu it doesn't happen, or in games either.
What could be causing this?

Does this happen on any other homebrew applications?

No, In the video I show DevMenu opened without the issue.
With the testing build: On the top left it reads: 0x40000000 without any button pressed.
When I hit down it changes to: 0x40000080 and when released it goes back to 0x40000000.
When I hit right it changes to: 0x40000010 and when released it goes back to 0x40000000.
When I hit up it changes to: 0x40000040 and when released it goes back to 0x40000000.
Seems like is not moving from reading button input.

DevMenu is not homebrew software, it's from the Nintendo SDK. I meant something created with ctrulib.

After trying to calibrate the circle pad seems like it has some issues for some reason. The down only goes up to half.
I'm going to try and replace it and see if that's the issue.
Thanks for your time and help.


LibGDX ignore image / jpeg EXIF orientation

Issue details
Mobile camera, capture and store pixmap data as always landscape, and it just store info about the rotation in EXIF "orientation", ignoring those data will result in loading images rotated 90 degree

Reproduction steps/code
Take a camera picture from Android / iOS in Portrait mode and try to load it in LibGDX
Test Image
Browsers may also not honoring the jpeg exif orientation?

Version of LibGDX and/or relevant dependencies
1.9.8
Please select the affected platforms

[X] Android
[X] iOS (robovm)
[X] iOS (MOE)
[X] HTML/GWT
[ ] Windows
[ ] Linux
[ ] MacOS

remove
On Wed, May 2, 2018 at 3:44 AM doit-ceo<EMAIL_ADDRESS>wrote:

Issue details
Mobile camera, capture and store pixmap data as always landscape, and it
just store info about the rotation in EXIF "orientation", ignoring those
data will result in loading images rotated 90 degree
[image: selection_751]
https://user-images.githubusercontent.com/8027780/39516309-3ff28a24-4e05-11e8-92da-aee70cd52992.png
Reproduction steps/code
Take a camera picture from Android / iOS in Portrait mode and try to load
it in LibGDX
Test Image
Browsers may also not honoring the jpeg exif orientation?
[image: 20180502_121404]
https://user-images.githubusercontent.com/8027780/39516463-b63f7d90-4e05-11e8-9c77-11dbe8ca3682.jpg
Version of LibGDX and/or relevant dependencies
1.9.8
Please select the affected platforms

Android
iOS (robovm)
iOS (MOE)
HTML/GWT
Windows
Linux
MacOS

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/libgdx/libgdx/issues/5206, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEzyzXcD-nmK88rDcbIQOoko2sMcYhHxks5tuYAIgaJpZM4TvKBA
.

I don't think libgdx should handle EXIF information. But you can implement it using (this library)[https://drewnoakes.com/code/exif/].

Agreed, probably best to read the EXIF info yourself and rotate when needed.


Change default shell signal from SIGTERM to SIGINT

For historical reasons when we send interrupts to process groups, we default to using SIGTERM:
https://github.com/buildkite/agent/blob/b9bc5ecc8e67fd6734d8930fb5ebb848902d99f2/process/signal.go#L35-L38
When we send SIGTERM to a process group, bash exits without waiting on its child processes to exit safely. In many cases, the child processes end from other effects, such as SIGPIPE caused by trying to read or write over an orphaned pipeline. This unreliability can lead to lost output or incorrect shutdowns of subprocesses. A script author could potentially work around this using a signal handler. A better approach would be to send a SIGINT signal instead, which will be followed by a SIGKILL if the group takes too long to respond. SIGINT only gets propagated to foreground child processes, so special case handling will still be required for users who are backgrounding processes.
Most processes treat SIGINT the same as SIGTERM, but we can't be sure if anyone is relying on this behaviour. Therefore, this should be considered a breaking change. A user can experiment with this change ahead of time by using the configurable cancel signals introduced by #1041 and #1390.
I've tried to carefully research this and get the above details correct, but please feel free to contribute any corrections or details I might have missed.

Interesting — have you come across any good links explaining the differences between SIGINT and SIGTERM?
My understanding over the years has stopped at “SIGINT is usually ctrl-c, SIGTERM is usually kill or program-initiated termination, SIGKILL is the kernel just no longer scheduling the process”. I never knew any difference with SIGINT vs SIGTERM around how it's propagated in progress groups between process leader / others processes and/r foreground processes. My understanding of process groups overall is pretty sketchy.
Got any links to things that explain SIGTERM vs SIGINT behaviour?

My understanding of process groups overall is pretty sketchy.

Yeah, same! Learning this as I go. 😅

Interesting — have you come across any good links explaining the differences between SIGINT and SIGTERM?

This is cobbled together across various bits and pieces. I'll pop a few of the references I used down:

Probably the best, details about foreground and background signal handling, with a focus on how to propagate to child processes: https://linuxconfig.org/how-to-propagate-a-signal-to-child-processes-from-a-bash-script
Reference for bash ignoring/not forwarding SIGTERM signals while a process is running: https://unix.stackexchange.com/questions/146756/forward-sigterm-to-child-in-bash
Discussion about SIGINT and foregrounding: https://unix.stackexchange.com/a/149756
Another suggestion for propagating SIGTERM in scripts: http://veithen.io/2014/11/16/sigterm-propagation.html
Reference for the SIGPIPE detail/how orphaned processes terminate: https://stackoverflow.com/a/34520362


errors when switching windows

the plugin works but when I go to the window below the css file I get these errors
Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   11:
E688: More targets than List items
Press ENTER or type command to continue
Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   12:
E121: Undefined variable: l:guibg
Press ENTER or type command to continue
Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   14:
E121: Undefined variable: l:group
Press ENTER or type command to continue
Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   14:
E116: Invalid arguments for function hlexists(l:group) == 0
Press ENTER or type command to continue
Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   23:
E121: Undefined variable: l:tdx
Press ENTER or type command to continue
Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   28:
E121: Undefined variable: l:cssname
Press ENTER or type command to continue
Error detected while processing WinEnter Autocommands for "*"..function vim_sass_colors#run:
line   33:
E121: Undefined variable: l:hsl
Press ENTER or type command to continue

Running this plugin on Neovim version image below

gives me similar error


There is a gray locker below the research area. If you enter it, you get TELEPORTED somewhere else.
If the locker is locked, however, you got soft locked.
Can we make it so if someone is in a locked locker, they can break out?
Plus, they could open the locker on the way.
Seems logical someone inside a locker could force it open?

So that's where the cursed locker is, in saltern...

Also

If the locker is locked, however, you got soft locked.

Intended. This cursed locker simply needs to be removed from the map, it should be an admin-only entity, really.

This is secret content
Delete this

n o


Question: why not move NWO to eu4 or hoi4?

I ask this because victoria 2 uses a really old engine and everywhere I go I see complaints about how modding is difficult. I know this would be a monumental undertaking but in the long run it would be beneficial and allow you to do thing leaps and bounds ahead of what victoria 2 allows you to do.
P.S I have no idea how to mod eu4 or victoria 2 so i have no idea how difficult it is.

That idea would be perfect with all the advanced military and economic play mechanics of both eu4 and hoi4 it will give this mod soo much potentials and new horizons to develop

Actually I have contemplated this on more than one occasion (sort of in the back of my mind 2.00 of NWO wold be a eu4 version), but each time backed of from the enormous amount of work. There are a lot of things in eu4 that is superior to vic2. To mention some diplomacy, elites/royal families, religions and trade. But there are also things missing, like no pops, factories and ideologies, and the economy is at its core less realistic.
Furthermore it is huge work to port all events to it, _so at the moment there are no such plans. _
But please post this in the forum thread to see if there is more interest.

On a port of NWO to hoi4. This post discuss it (written before playing hoi4). From playing some hoi4 my conclusion is that this is a war only game. At it is really not what NWO/vi2 is about. One could consider a limited cold war scenario where 100% tension at all costs must be avoided (i.e. MAD Armageddon), and whomever breaches the 100% looses the game. But the economics, trade, etc is simply to simplistic and by it self not entertaining enough. So there will be no NWO port to by me. There are other mods as mentioned in the post that might tries to do post-WW2 scenario that might be worth testing out.

Well pops is not really necessary since they added a manpower resource. Its a resource though and not an actual pop. There are Technology group you could repurpose to work as ideologies and development could be used as factories. yes the economy is less in depth as in vic2 but that's a small downside to how better everything else is.
P.S What forum? The paradox forum? If it is I could never get that to work. So just stopped trying. Even after they updated the system it still doesn't work. So could someone do post that for me?

Or post in this reddit thread. Will close this issue awaiting such discussion. As mentioned previously no plans for a port.


Custom ESP32-S3 External RAM Configuration

Following on from the issue: https://github.com/mocleiri/tensorflow-micropython-examples/issues/40
Error produced when trying to run the Micro-Speech example on the ESP32-S3 was:
Connecting to /dev/tty.SLAB_USBtoUART...
ESP-ROM:esp32s3-20210327
Build:Mar 27 2021
rst:0x10 (RTCWDT_RTC_RST),boot:0x8 (SPI_FAST_FLASH_BOOT)
SPIWP:0xee
mode:DIO, clock div:1
load:0x3fcd0108,len:0xf60
load:0x403b6000,len:0x978
load:0x403ba000,len:0x2c80
entry 0x403b616c
W (25) bootloader_random: RNG for ESP32-S3 not currently supported
W (313) bootloader_random: RNG for ESP32-S3 not currently supported
Traceback (most recent call last):
File "main.py", line 14, in
ImportError: no module named 'audio_frontend'
MicroPython 59e6194 on 2021-12-18; ESP32S3 module (microlite-spiram) with ESP32S3
Type "help()" for more information.
I'll also look into the RNG errors produced as well.

@TGiles1998
That error is most likely due to my moving audio_frontend from a separate module into another type in microlite.
Try
''''
af = microlite.audio_frontend()
af.configure()
af.execute(...)
'''
I updated the main.py and micro_speech.py here to use the new location:
https://github.com/mocleiri/tensorflow-micropython-examples/tree/main/examples/micro-speech/esp32
The model.tflite comes from here:
https://github.com/mocleiri/tensorflow-micropython-examples/tree/main/examples/micro-speech/lib
This is a short video of the example running for me:
https://youtu.be/FBUwIvzNVd4
That video was the double check that micro-speech still ran after the audio_frontend was integrated.
You need to change the I2S pins in main.py to match how you connected the microphone.
There is definitely room for improvement in the examples so please continue to report any problems you find with them so I can improve things.

That patch seems to work thanks! I will continue to test and expand on these examples.
Would it be possible to further customize the GPIO 20 CS build to allow for the full 8MB of  SPI-RAM to be used? I believe it just requires the ESP32S3 specific config options in the "idf.py menuconfig" to be selected with the CONFIG_SPIRAM_TYPE_ESPPSRAM64.
I think I put the config options here: https://github.com/mocleiri/tensorflow-micropython-examples/issues/40#issuecomment-989323462
Thanks so much!

Can you report what micropython.mem_info() shows ?
Unexpected Maker flashed essentially the same config but without the spiram size given and it found all 8MB automatically.  Start at the 15 minute mark: https://youtu.be/rcTrYBtaAMc

@TGiles1998 I went back and applied all the options you reported originally on #40.
This built locally for me so I think it will via the github actions aswell.
https://github.com/mocleiri/tensorflow-micropython-examples/actions/runs/1614197339
I left the CPU frequency at 240 MHz but all of the options you had should be applied now.

@mocleiri
Sorry for the late reply! Thank you that's fantastic! Will start testing this!

@TGiles1998 I will close this issue.  Please open others if you want further adjustments made to the configs or anything else.


Immersive Mode doesn't work at all

None of the full screen, status bar, or nav bar modes worked.
SystemUI Tuner version: 342
Android version: 12 (June 2022)
Device: Pixel 4a 5G

Please read the Safety/Warnings section of the terms.

@zacharee I'm a bit confused by the part about immersive mode in the terms you linked. If apps can no longer change immersive mode, how do full-screen apps like videos work?

This is good 👍


Return value check for pqueue_insert()

Hi,
The patch commit for CVE-2014-3507 adds some new return value check for the function pqueue_insert.
- pqueue_insert(s->d1->buffered_messages, item);
+ item = pqueue_insert(s->d1->buffered_messages, item);
+ /* pqueue_insert fails iff a duplicate item is inserted.
+ * However, |item| cannot be a duplicate. If it were,
+ * |pqueue_find|, above, would have returned it and control
+ * would never have reached this branch. */
+ OPENSSL_assert(item != NULL);

There is another call site for this function which do not have this return value check.
./ssl/statem/statem_dtls.c : dtls1_buffer_message()

It needs to be patched too.

There can be no duplicate message inserted this way so there is no point in checking the return value. The pqueue_insert can never fail there.
It still might make sense to add the check with the assert anyway but it is not a real bug.

Marking as inactive, to be closed at the end of 3.4 dev barring further input


images don't switches in the gallery

Note: for support questions, please use stackoverflow. This repository's issues are reserved for feature requests and bug reports.

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.

Do you want to request a feature or report a bug?
report a bug

What is the current behavior?
images are switched only after two clicks on the arrow in the gallery on the dashboard

If the current behavior is a bug, please provide the steps to reproduce, ideally also a screenshot or gif if it's a style issue

open dashboard link
click 'explore gallery' button
try to switch image

What is the expected behavior?
images should be switched after every click

What is the motivation / use case for changing the behavior?

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Can you check if it works now? Works all right for me.


added counter program

What does the program do ?
Basic counter.

In what programming language it is written?
HTML and Javascript.

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


Linking Dart functions to a native binary

Is it possible to link Dart functions to a native binary the same way as with JavaScript and WebAssembly? In JS it's possible to pass an object with imports to instantiateStreaming method. Does Dart have a similar feature? Assuming desktop and mobile targets.

Thanks for a quick reply! Thank you for the links, haven't seen the second one yet.
I'm checking the limits of dart ffi. So far I've figured out that we can invoke the native function using .lookup().asFuntion() method. Also, it's possible to pass a static Dart function into a native function as a callback. But is it possible to link Dart functions to a native module? Something like an alternative to DynamicLibrary.open with second argument, which contains hashmap with functions to link.

The closest alternative I can think off is to create a struct with a bunch of function pointers on the native side and then fill it in from Dart side, thus emulating what runtime linker would do for two shared objects. Something like this:
// C++
struct Imports {
  void (*callback1)(int x);
  void (*callback2)(double y);
  void (*callback3)(void* whatever);
  void (*callback4)(const char* something);
};

EXPORT_SYMBOL Imports imports;

// Use somewhere in the code:
imports.callback1(0);

// Dart

class Imports extends Struct {
  // ...
}

final lib = DynamicLibrary.open("foo");
final imports = lib.lookup<Imports>("imports");
imports.ref
  ..callback1 = Pointer.fromFunction(callback1)
  ..callback2 = Pointer.fromFunction(callback2)
  ..callback3 = Pointer.fromFunction(callback3)
  ..callback4 = Pointer.fromFunction(callback4);

This looks great, thanks! I'll give it a try!


Disabled deprecated haproxy_global_nbproc and haproxy_global_cpu_maps

Disabled options haproxy_global_nbproc and haproxy_global_cpu_maps by default as they deprecated and will be removed in the HaProxy 2.5
Currently, if apply role on HAProxy version 2.3 occurred this warning:
    [WARNING] 362/134414 (345606) : nbproc is deprecated!
      | For suffering many limitations, the 'nbproc' directive is now deprecated
      | and scheduled for removal in 2.5. Just comment it out: haproxy will use
      | threads and will run on all allocated processors. You may also switch to
      | 'nbthread 2' to keep the same number of processors. If you absolutely
      | want to run in multi-process mode, you can silence this warning by adding
      | 'nbthread 1', but then please report your use case to developers.

This PR prevent warning.

Hi @pavel-z1,
Could you please update the README too?

Hi @goldyfruit
README updated.

Hi @Fishwaldo
Can you help please with review of this PR?

Thanks. :+1:


Idea/use case: cfgrib

Hi Tom,
I missed your AMS talk this week because of a conflict, but I looked through the slides (thanks for posting those). Maybe I'll run into  you later at AMS.
Just about all numerical weather model data is distributed in the grib format. Xarray has an engine for reading grib and grib2 files (cfgrib) that works great. One limitation with cfgrib is that when a file has variables on multiple types of levels (i.e., temperature at 2 meters, at 500 mb, and at cloud top height) cfgrib can't read the data into a single dataset, so instead it reads the data and returns a list of datasets when you do cfgrib.open_datasets(gribfileName).
If I understand the basics of datatree correctly, it sounds like datatree would be the better way for cfgrib to handle reading this data.
Have you looked at cfgrib and grib data before?

Hi Brian!

I missed your AMS talk this week because of a conflict, but I looked through the slides (thanks for posting those). Maybe I'll run into you later at AMS.

No worries - are you coming to the pangeo workshop on Friday?

Have you looked at cfgrib and grib data before?

I have never personally used grib data, but I would be happy to help you make it work in xarray!

One limitation with cfgrib is that when a file has variables on multiple types of levels (i.e., temperature at 2 meters, at 500 mb, and at cloud top height) cfgrib can't read the data into a single dataset, so instead it reads the data and returns a list of datasets when you do cfgrib.open_datasets(gribfileName).

Do you know how you might organise this data in terms of nested groups / nodes? If those group names can be derived from your file then this should be pretty simple. You can see how datatree handles netCDF and Zarr here.

Here's a brief snippet of code that could act as a starting point, given the one level depth of organization of datasets output by cfgrib (though could likely be cleaned up if integrated directly into cfgrib to use private functions):
import cfgrib
from datatree import DataTree

def cfgrib_open_datatree(file, **kwargs):
    ds_list = cfgrib.open_datasets(file, **kwargs)
    ds_dict = {}
    for ds in ds_list:
        type_of_level = next(ds.data_vars.values()).attrs.get("GRIB_typeOfLevel", "undef")
        ds_dict[type_of_level] = ds
    return DataTree.from_dict(ds_dict)

That looks pretty neat already @jthielen ! Could we just add something like that to cfgrib?
Ideally we want this to work:
dt = open_datatree("data.grib", engine="cfgrib")

but I'm not familiar enough with xarray's backend code to know if that can be done purely with changes to cfgrib or whether it requires changes to xarray (/integration of datatree in xarray).  cc @jhamman ?

My hunch is that we could easily add a cfgrib.open_datatree() method to supplement/replace the existing cfgrib.open_datasets() from what I had (to https://github.com/ecmwf/cfgrib/blob/master/cfgrib/xarray_plugin.py), but supporting the backend engine would take more work (though, perhaps it may only entail adding the appropriate method to BackendEntrypoint? )

Looks great @jthielen! And so quick.
@TomNicholas, unfortunately I won't be at AMS Friday for the pangeo workshop.

I really like the idea of supporting open_datatree(engine=...) for certain backends. We already have open_dataarray and open_dataset so this will be a natural extension to include in xarray. We will need to do some dedicated design planning to figure out how to integrate with Xarray's backends. I'm thinking that sketching this out at the Pangeo meeting on Friday may be a good use of time.

The integration of datatree into xarray's backend entrypoint system has now been done, so if anyone wants to try making their grib reader return xarray.core.datatree.DataTree objects they can! You might also be interested in the new open_groups function (https://github.com/pydata/xarray/issues/9137).
As xarray doesn't ship a grib reader, and this should now be possible in xarray upstream, I'm going to close this in favour of cfgrib tracking this enhancement to their package.


Add more customized inputs for recommendations

The Spotify Web API for recommendations offers the option to add more inputs, such as:

acousticness
instrumentalness
speechiness
tempo
valence (Tracks with high valence sound more positive (e.g. happy, cheerful, euphoric), while tracks with low valence sound more negative (e.g. sad, depressed, angry).)

Note: These should all be optional inputs.

Hey,
I will take a look at this one!

@harshalitalele Great, thank you!

Hi @RyanRussell00 ! I have created a PR for this issue - https://github.com/RyanRussell00/personal-dj/pull/33
Please check and let me know if any changes are required.
Though this issue seems to have been already assigned, since the comments were from 2 days, I gave it a try. Seems like a nice project.


Model size for wildshapes

Most wildshape models are scaled too small, particularly the gorilla which is smaller than a player character despite being size large.
I wanted to make a PR adding an option to increase wildshape model size but I'm not sure where the values for the MonsterDefinitions database are being pulled from.

check https://github.com/SolastaMods/SolastaUnfinishedBusiness/blob/062fb2a2f09220f9a1392fd548fff1ca451c18cc/SolastaUnfinishedBusiness/Settings.cs#L180 on how I change their size.
Moving to discussions as it isn't an issue.


MRG, MAINT: Check usage

Codespell recently added a usage dictionary to move toward #7901. This just has us use it, with an exception for master for now (no other changes needed for our codebase).

Not sure why the Python 3.8 job keeps failing because it times out after 1 hour - is this OK?

I'm working on adding more tests to slow to try to work around it


[T2A2][W15-A3]Jasper Lee

Ready for review

@jasperlee27

for boolean isChanged or isDeleted you can think of naming it such that "what is changed" will become apparent
err, why are you passing matchedPersons and returning the same? thinking c? :-P
in general, pay more attention to coding standards violation.
some useful ones include checking how conditional statements are written, naming conventions etc.,


[addons]  Use public NVIDIA image repository for nvidia-device-plugin

Background
To bypass the Dockerhub rate limits for the nvidia-device-plugin image, I'd like to use the public image registry which NVIDIA manages.
This PR also includes a small change for aws-ebs-csi-driver which was generated by executing hack/generate_addons.sh.

The change https://github.com/cookpad/terraform-aws-eks/commit/38af30601b44f535da1be8f5a5dcc46902c2db9f does not seem better than before. I personally think GCR is much more reliable than quay. Let me check it out again.

Let me focus on the image update of nvidia-device-plugin in this PR. I will handle the update of aws-ebs-csi-driver with https://github.com/cookpad/terraform-aws-eks/pull/196

Thanks!


DS212j registration successful but cannot connect

Hi, I have a DS212j synology NAS and I'm trying to run tailscale.
I saw in the README.md that someone has confirmed that it's working there. Well, for me it's not working.
I can register the NAS with tailscale and I can see the IP and trying to connect from another network.
When I tried to connect I see no connectivity (not answering to ping, timeout while ssh and web).
To discard connectivity issues I set up a raspberry pi in the same home router and worked perfectly, so I'd discard router issues. The issue must be in the NAS itself.
Is there any log file in the NAS, so I can continue debugging?

Hey, Adrian!
All logs should be in /var/packages/tailscale/target/var/
I'm due updating tailscale to the newest version. So maybe it could be that. Can you check which version is running in raspberry?
I'll try to release a new build today, regardless.

Yep, I was also thinking about something with versions.
From the tests I have been doing it might be something related with the NAT traversal.

Version in DiskStation: v0.97-45-g02c73501
Version in Raspberry: v0.99.1-0-gf3199dd1

Feel free to ask for help build the pkg ;)

Hey, Adrian.
I've been trying to get the new version out, but 0.98.0 and 0.99.1 are not working for me.
I'm trying to figure out and get more info to open a bug report with tailscale.

Those versions are also not working for me either. My tailscale0 adapter on host is not getting an IP address, not sure if you are seeing similar. Tailscale logs itself didn't show obvious issues. Please link to tailscale issue once you open.

@rishid @adriangalera
v0.99.1 is not working for me.
It's the same behaviour @rishid described: tailscale0 doesn't get an IP address assigned, no routes are added, etc. I opened a bug report in https://github.com/tailscale/tailscale/issues/451
I went back and forth between 0.97-45, 0.98-0 and 0.99.1, both restoring state and starting from scratch. Version 0.98.0 works reliably in my DS218+, so I released it:
https://github.com/nirev/synology-tailscale/releases/tag/v0.98-0


Dev

Hi @rosafilgueira,
does this address any open issue? If not, should we open one due to a bug?
Thanks!

Hi @dgarijo.
Yep, they fix two of the bugs reported in two issues (#365, and #374). I have already clossed them.

Thanks!!


Setup Postgres DB in AWS

Need to setup Postgres DB with backend user with read/write permissions. There should be a db 'nbody_db' with schemas 'dev' and 'prod'.
nbody_db

dev
prod

Database has been created with user and schemas initialized. No code change is needed.


Focus css

move  outline: none; into .rz-active

Current coverage is 100% (diff: 100%)

Merging #389 into master will not change coverage

@@           master   #389   diff @@
====================================
  Files           1      1
  Lines         846    846
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
  Hits          846    846
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 324ea00...9a72539

What's the goal of this pull request?

Remove focus borders on webkit browser (Safari and Chrome).
The same as the first you close yesterday. A mistake sorry !
It is a pull request for my master branch.
I notice you prefer to keep on the default focus.
For the UX the dark-blue dot is good focus.
I don't like the default border. It is too much. The squared focus does not match the circle. It is ugly.


VIP address not being automatically removed after Service deletion

Describe the bug
When using kube-vip to manage LoadBalancer services, the VIP address is not being automatically removed from the network interface after the corresponding Service is deleted. This causes the VIP to remain assigned to the node, leading to potential conflicts when new services are created or re-used.
To Reproduce
Create a LoadBalancer type service with a specific VIP.
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginxapp
spec:
  selector:
    matchLabels:
      app: nginxapp
  template:
    metadata:
      labels:
        app: nginxapp
    spec:
      containers:
      - name: nginxapp
        image: nginx
        resources:
          limits:
            memory: "128Mi"
            cpu: "500m"
        ports:
        - containerPort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: nginxapp
spec:
  selector:
    app: nginxapp
  type: LoadBalancer
  ports:
  - port: 80
    targetPort: 80
    protocol: TCP
  loadBalancerIP: <IP_ADDRESS>

kubectl get po,svc
NAME                            READY   STATUS    RESTARTS   AGE
pod/nginxapp-67d9758fbf-xk8c6   1/1     Running   0          11s

NAME                 TYPE           CLUSTER-IP       EXTERNAL-IP   PORT(S)        AGE
service/kubernetes   ClusterIP      <IP_ADDRESS>        <none>        443/TCP        13h
service/nginxapp     LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>    80:30404/TCP   12s

Observe that the VIP is correctly added to the network interface (e.g., ens160):
ip addr show ens160
2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global ens160
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/32 scope global ens160
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/32 scope global ens160
       valid_lft forever preferred_lft forever

Delete the service:
kubectl delete
Check the network interface again. The VIP <IP_ADDRESS>/32 is still present on the interface ens160.
ip addr show ens160
2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    inet <IP_ADDRESS>/16 brd <IP_ADDRESS> scope global ens160
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/32 scope global ens160
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/32 scope global ens160
       valid_lft forever preferred_lft forever

log
time="2024-09-04T19:42:20Z" level=info msg="Starting kube-vip.io [v0.8.0]"
time="2024-09-04T19:42:20Z" level=info msg="namespace [kube-system], Mode: [ARP], Features(s): Control Plane:[true], Services:[true]"
time="2024-09-04T19:42:20Z" level=info msg="prometheus HTTP server started"
time="2024-09-04T19:42:20Z" level=info msg="Using node name [master2]"
time="2024-09-04T19:42:20Z" level=info msg="Starting Kube-vip Manager with the ARP engine"
time="2024-09-04T19:42:20Z" level=info msg="beginning services leadership, namespace [kube-system], lock name [plndr-svcs-lock], id [master2]"
I0904 19:42:20.750014       1 leaderelection.go:250] attempting to acquire leader lease kube-system/plndr-svcs-lock...
time="2024-09-04T19:42:20Z" level=info msg="Beginning cluster membership, namespace [kube-system], lock name [plndr-cp-lock], id [master2]"
I0904 19:42:20.753661       1 leaderelection.go:250] attempting to acquire leader lease kube-system/plndr-cp-lock...
I0904 19:42:20.797305       1 leaderelection.go:260] successfully acquired lease kube-system/plndr-cp-lock
I0904 19:42:20.797493       1 leaderelection.go:260] successfully acquired lease kube-system/plndr-svcs-lock
time="2024-09-04T19:42:20Z" level=info msg="Node [master2] is assuming leadership of the cluster"
time="2024-09-04T19:42:20Z" level=info msg="(svcs) starting services watcher for all namespaces"
time="2024-09-04T19:42:20Z" level=info msg="Gratuitous Arp broadcast will repeat every 3 seconds for [<IP_ADDRESS>/ens160]"
time="2024-09-04T20:29:02Z" level=info msg="(svcs) [calico-system/calico-kube-controllers-metrics] has been deleted"
time="2024-09-04T20:29:04Z" level=info msg="(svcs) [calico-system/calico-typha] has been deleted"
E0904 21:07:06.573653       1 leaderelection.go:332] error retrieving resource lock kube-system/plndr-cp-lock: etcdserver: leader changed
time="2024-09-04T21:44:34Z" level=info msg="(svcs) [calico-apiserver/calico-api] has been deleted"
time="2024-09-04T21:44:34Z" level=info msg="(svcs) [calico-system/calico-kube-controllers-metrics] has been deleted"
time="2024-09-04T21:47:23Z" level=info msg="(svcs) [calico-system/calico-typha] has been deleted"
time="2024-09-04T16:25:15Z" level=info msg="(svcs) [calico-apiserver/calico-api] has been deleted"
time="2024-09-04T16:38:34Z" level=info msg="(svcs) [calico-system/calico-kube-controllers-metrics] has been deleted"
time="2024-09-04T16:38:39Z" level=info msg="(svcs) [calico-system/calico-typha] has been deleted"
time="2024-09-05T01:25:15Z" level=info msg="(svcs) [metallb-system/metallb-webhook-service] has been deleted"
time="2024-09-05T01:29:15Z" level=info msg="(svcs) adding VIP [<IP_ADDRESS>] via ens160 for [default/nginxapp]"
time="2024-09-05T01:29:15Z" level=info msg="[service] synchronised in 50ms"
time="2024-09-05T01:29:15Z" level=warning msg="(svcs) already found existing address [<IP_ADDRESS>] on adapter [ens160]"
time="2024-09-05T01:29:18Z" level=warning msg="Re-applying the VIP configuration [<IP_ADDRESS>] to the interface [ens160]"
time="2024-09-05T01:33:24Z" level=info msg="(svcs) [default/nginxapp] has been deleted"
E0905 01:48:36.399150       1 leaderelection.go:332] error retrieving resource lock kube-system/plndr-svcs-lock: etcdserver: leader changed
time="2024-09-05T01:50:01Z" level=info msg="(svcs) adding VIP [<IP_ADDRESS>] via ens160 for [default/nginxapp]"
time="2024-09-05T01:50:02Z" level=info msg="[service] synchronised in 110ms"
time="2024-09-05T01:50:02Z" level=warning msg="(svcs) already found existing address [<IP_ADDRESS>] on adapter [ens160]"
time="2024-09-05T01:50:04Z" level=warning msg="Re-applying the VIP configuration [<IP_ADDRESS>] to the interface [ens160]"
time="2024-09-05T01:52:43Z" level=info msg="(svcs) [default/nginxapp] has been deleted"

Expected behavior
The VIP (<IP_ADDRESS>/32) should be automatically removed from the network interface once the corresponding LoadBalancer service is deleted.
Environment (please complete the following information):
kube-vip 版本: v0.8.0 (请替换为实际版本)
Kubernetes 版本: v1.28.12 (请替换为实际版本)
calico:
Kube-vip.yaml:
apiVersion: v1
kind: Pod
metadata:
  creationTimestamp: null
  name: kube-vip
  namespace: kube-system
spec:
  containers:
  - args:
    - manager
    env:
    - name: vip_arp
      value: "true"
    - name: port
      value: "6443"
    - name: vip_nodename
      valueFrom:
        fieldRef:
          fieldPath: spec.nodeName
    - name: vip_interface
      value: ens160
    - name: vip_cidr
      value: "32"
    - name: dns_mode
      value: first
    - name: cp_enable
      value: "true"
    - name: cp_namespace
      value: kube-system
    - name: svc_enable
      value: "true"
    - name: svc_leasename
      value: plndr-svcs-lock
    - name: vip_leaderelection
      value: "true"
    - name: vip_leasename
      value: plndr-cp-lock
    - name: vip_leaseduration
      value: "5"
    - name: vip_renewdeadline
      value: "3"
    - name: vip_retryperiod
      value: "1"
    - name: address
      value: <IP_ADDRESS>
    - name: prometheus_server
      value: :2112
    image: ghcr.io/kube-vip/kube-vip:v0.8.0
    imagePullPolicy: IfNotPresent
    name: kube-vip
    resources: {}
    securityContext:
      capabilities:
        add:
        - NET_ADMIN
        - NET_RAW
    volumeMounts:
    - mountPath: /etc/kubernetes/admin.conf
      name: kubeconfig
  hostAliases:
  - hostnames:
    - kubernetes
    ip: <IP_ADDRESS>
  hostNetwork: true
  volumes:
  - hostPath:
      path: /etc/kubernetes/admin.conf
    name: kubeconfig
status: {}

Additional context
none
Please help me~~~~

When i create a new one, the old one is automatically deleted.


Applied a terraform deployment and did not get the wg_config file as output.

Terraform Version
~/opt/mytrunk/terraform/my-first-project$ terraform -v
Terraform v1.0.10
on linux_amd64
+ provider registry.terraform.io/threefoldtech/grid v0.1.13

Affected Resource(s)
Did not get wg_config output file. Deployment did not produce any errors.
~/opt/mytrunk/terraform/my-first-project$ terraform show
# grid_deployment.d1:
resource "grid_deployment" "d1" {
    id           = "260"
    ip_range     = "<IP_ADDRESS>/24"
    network_name = "network"
    node         = 41

    vms {
        cpu         = 1
        entrypoint  = "/sbin/zinit init"
        flist       = "https://hub.grid.tf/tf-official-apps/base:latest.flist"
        ip          = "<IP_ADDRESS>"
        memory      = 1024
        name        = "vm1"
        planetary   = true
        publicip    = false
        rootfs_size = 0

        env_vars {
            key   = "SSH_KEY"
            value = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDAOP0h6VImNcxnIBRMoMfbMfb0xwGHDlaPxZ+nu0CL8ATJekVDHDLMGEPdvACfHBe0sqIw/l6jqoEMR4Dzhjgm4bVEUBVEnG1FvkeNB59sT2DOxDCZuqJvjx2M1bJlH8AR/JQXxUQ+zvfTbavc4/zfCuJm4PYNUsmEt/IQmRwLznGOkoJbwYLhKCC3ykZd0EGpmCWgUUYn0ihaaYkyrliQi5Ny00x0s6jOIJg0CG2Xh5xcrkhOfCZMxZAB+/LGQpZ3tu+Cy5jRf8V/JZ8XQmtYM2GmBUZ1KGcMcsGzrtuudn13JeYLtWJBw6A7Q3Fb7dQSCMLC9UA0uMSZk67M6DFV john@RescuedMac"
        }
    }
    vms {
        cpu         = 1
        entrypoint  = "/sbin/zinit init"
        flist       = "https://hub.grid.tf/tf-official-apps/base:latest.flist"
        ip          = "<IP_ADDRESS>"
        memory      = 1024
        name        = "anothervm"
        planetary   = true
        publicip    = false
        rootfs_size = 0

        env_vars {
            key   = "SSH_KEY"
            value = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDAOP0h6VImNcxnIBRMoMfbMfb0xwGHDlaPxZ+nu0CL8ATJekVDHDLMGEPdvACfHBe0sqIw/l6jqoEMR4Dzhjgm4bVEUBVEnG1FvkeNB59sT2DOxDCZuqJvjx2M1bJlH8AR/JQXxUQ+zvfTbavc4/zfCuJm4PYNUsmEt/IQmRwLznGOkoJbwYLhKCC3ykZd0EGpmCWgUUYn0ihaaYkyrliQi5Ny00x0s6jOIJg0CG2Xh5xcrkhOfCZMxZAB+/LGQpZ3tu+Cy5jRf8V/JZ8XQmtYM2GmBUZ1KGcMcsGzrtuudn13JeYLtWJBw6A7Q3Fb7dQSCMLC9UA0uMSZk67M6DFV john@RescuedMac"
        }
    }
}

# grid_network.net1:
resource "grid_network" "net1" {
    add_wg_access      = false
    description        = "newer network"
    external_sk        = "iOg/GcrM6HRkfjviCUijGZcXv4s+Y1+nTNCsRR6ZqkE="
    id                 = "f569934d-99c6-453c-8471-ca4ca1dfb0e5"
    ip_range           = "<IP_ADDRESS>/16"
    name               = "network"
    node_deployment_id = {
        "41" = 258
        "42" = 259
    }
    nodes              = [
        41,
        42,
    ]
    nodes_ip_range     = {
        "41" = "<IP_ADDRESS>/24"
        "42" = "<IP_ADDRESS>/24"
    }
    public_node_id     = 0
}

Outputs:

node1_container1_ip = "<IP_ADDRESS>"
node1_container2_ip = "<IP_ADDRESS>"
public_ip = ""
wg_config = ""

Expected Behavior
What should have happened?  I should he been presented a wg_config.
Actual Behavior
What actually happened?  Successful deployment, just did not get the information to set up a wireguard VPN to the private network.
Terraform file
terraform {
  required_providers {
    grid = {
      source = "threefoldtech/grid"
    }
  }
}

provider "grid" {
#    twin_id = 86
    mnemonics = "elegant lawn power carpet real into police credit brown copy law wagon"
    network = "test"
}

resource "grid_network" "net1" {
    nodes = [41, 42]
    ip_range = "<IP_ADDRESS>/16"
    name = "network"
    description = "newer network"
}
resource "grid_deployment" "d1" {
  node = 41
  network_name = grid_network.net1.name
  ip_range = grid_network.net1.nodes_ip_range["41"]
  vms {
    name = "vm1"
    flist = "https://hub.grid.tf/tf-official-apps/base:latest.flist"
    cpu = 1
#    publicip = true
    memory = 1024
    entrypoint = "/sbin/zinit init"
    env_vars {
      key = "SSH_KEY"
      value = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDAOP0h6VImNcxnIBRMoMfbMfb0xwGHDlaPxZ+nu0CL8ATJekVDHDLMGEPdvACfHBe0sqIw/l6jqoEMR4Dzhjgm4bVEUBVEnG1FvkeNB59sT2DOxDCZuqJvjx2M1bJlH8AR/JQXxUQ+zvfTbavc4/zfCuJm4PYNUsmEt/IQmRwLznGOkoJbwYLhKCC3ykZd0EGpmCWgUUYn0ihaaYkyrliQi5Ny00x0s6jOIJg0CG2Xh5xcrkhOfCZMxZAB+/LGQpZ3tu+Cy5jRf8V/JZ8XQmtYM2GmBUZ1KGcMcsGzrtuudn13JeYLtWJBw6A7Q3Fb7dQSCMLC9UA0uMSZk67M6DFV john@RescuedMac"

    }
  }
  vms {
    name = "anothervm"
    flist = "https://hub.grid.tf/tf-official-apps/base:latest.flist"
    cpu = 1
    memory = 1024
    entrypoint = "/sbin/zinit init"
#    publicip = true
    env_vars {
      key = "SSH_KEY"
      value = "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDAOP0h6VImNcxnIBRMoMfbMfb0xwGHDlaPxZ+nu0CL8ATJekVDHDLMGEPdvACfHBe0sqIw/l6jqoEMR4Dzhjgm4bVEUBVEnG1FvkeNB59sT2DOxDCZuqJvjx2M1bJlH8AR/JQXxUQ+zvfTbavc4/zfCuJm4PYNUsmEt/IQmRwLznGOkoJbwYLhKCC3ykZd0EGpmCWgUUYn0ihaaYkyrliQi5Ny00x0s6jOIJg0CG2Xh5xcrkhOfCZMxZAB+/LGQpZ3tu+Cy5jRf8V/JZ8XQmtYM2GmBUZ1KGcMcsGzrtuudn13JeYLtWJBw6A7Q3Fb7dQSCMLC9UA0uMSZk67M6DFV john@RescuedMac"
    }
  }
}
output "wg_config" {
    value = grid_network.net1.access_wg_config
}
output "node1_container1_ip" {
    value = grid_deployment.d1.vms[0].ip
}
output "node1_container2_ip" {
    value = grid_deployment.d1.vms[1].ip
}
output "public_ip" {
    value = grid_deployment.d1.vms[0].computedip
}

@ashraffouda please check

Did not specify that I wanter wireguard conf.  My bad.


Gaget-tized the C++ header generator

Added new gadgets to generate accessor functions, namespaces, and
dependencies

Re-wrote the C++ header generator to use gadgets

Signed-off-by: JaredWright<EMAIL_ADDRESS>

So, this is what a generator ends up looking like using the decorator-based gadget idea (Issue #18) to its full potential.
What do you think @JWZepf ? Did this end up better or worse than before?

Ok @JWZepf, I believe that I addressed all of your comments. Take a look through my follow up commit, and then I can squash it if you're happy.
As we discussed on Friday, I renamed "regs.h" to "aarch64_gcc_accessor_macros.h". This file now gets installed alongside all generated files and #include'ed in, instead of copy/pasting it into generated files.

Ok, this all looks great to me! Merging 👍


Nested router example

Added nested router example. Similar example was here before: https://github.com/rustasync/tide/commit/4bb3d3f19861d567ad319372d4ce93a7c04a7970, but disappeared during refactoring.

LGTM. :+1:


Update Build.sbt with exterbal resolvers

Update POM File with profile and properties

@agibsonccc @huitseeker We're still missing dependencies to support Scala 2.12...

@smaryn Let me know that this works! Thanks


Gnome sort using python

it's my first time contributing to hacktoberfest and it is not a spam.please help

Hey @killer0921 this is not the way for contributing in this repository. Please read our Contributing guide
You can make this pull requests to that repository: https://github.com/ReciHub/FunnyAlgorithms

As you asked, i made the 4 PR's in FunnyAlgorithm repository.now
please.........
On Mon, Oct 28, 2019 at 8:18 PM Otacilio Saraiva Maia Neto <
<EMAIL_ADDRESS>wrote:

Hey @killer0921 https://github.com/killer0921 this is not the way for
contributing in this repository. Please read our Contributing guide
https://github.com/OtacilioN/awesome-hacktoberfest-2019/blob/master/CONTRIBUTING.md
You can make this pull requests to that repository:
https://github.com/ReciHub/FunnyAlgorithms
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OtacilioN/awesome-hacktoberfest-2019/pull/161?email_source=notifications&email_token=ANQE6PH676QQBOJIDSUNAPLQQ33TPA5CNFSM4JFXD2NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECNEKGY#issuecomment-546981147,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANQE6PEBGF2MR3IRKE7K7MDQQ33TPANCNFSM4JFXD2NA
.


Modification failed to apply when using external drive

When I try to change the tags of files stored on a USB drive, no changes will be saved even after applying the changes.

Did you install Tagger via flatpak?

I installed the flatpakversion via the gnome-software-store

The flatpak version only has permission to access the home directory.
I recommend installing Flatseal and change the permissions of Tagger to access the whole filesystem to allow it to write to a USB

It worked, thanks.


custom control

prepare at least one custom control
like this: multiple selections

added: zcl_guidrasil_control_multisel
table entry in zguidrasil_ctls must be added manually


chore: bump slf4j to 2.0.11

?

not sure what happened here why was it closed. (it wasn't done manually by me, at reals not consciously ), then created a new PR: https://github.com/operator-framework/java-operator-sdk/pull/2298


Dreamview: replace boost rwlock by std rwlock

@unacao  reply to #9578

[23:55:31]./modules/dreamview/backend/data_collection_monitor/data_collection_monitor.h:23:24: fatal error: shared_mutex: No such file or directory
[23:55:31] #include <shared_mutex>
We use C++11 in our build environment, and rwlock is not supported in this version.

The master branch use C++1y(C++14), not C++11.
 76 # Enable C++14
 77 build --cxxopt="-std=c++1y"
 78 # Enable colorful output of GCC
 79 # build --cxxopt="-fdiagnostics-color=always"

Got it. Building env setting is different from the master branch.

Should the building env be updated the ./tools/bazel.rc same as the master branch?

@unacao reply to #9578

[23:55:31]./modules/dreamview/backend/data_collection_monitor/data_collection_monitor.h:23:24: fatal error: shared_mutex: No such file or directory
[23:55:31] #include <shared_mutex>
We use C++11 in our build environment, and rwlock is not supported in this version.

The master branch use C++1y(C++14), not C++11.
 76 # Enable C++14
 77 build --cxxopt="-std=c++1y"
 78 # Enable colorful output of GCC
 79 # build --cxxopt="-fdiagnostics-color=always"

are you able to compile successfully in your docker env?

Looks like it has something to do with the g++ version in the docker env. Currently g++ 4.8.5 is installed, which means only -std=c++1y can be used to enable part of the C++14 standard. The complete standard can only be enabled with -std=c++14 in g++ version 5.2 onwards.


SAK-12148 fix first-time startup errors around SakaiBootstrap

CC: @austin48

does this also fix SAK-47265?

thanks, it partially fixes SAK-47265.  One of the indexes (SAM_AG_AGENTID_I) in that jira still wasn't created after applying this patch.
note, when applying the patch (on my MacBook), I had to use --ignore-whitespace because it looks like the patch adds different line endings .  I'm not sure if that would affect github merging.

Okay, can you add SAM_AG_AGENTID_I to this PR via the Edit PR button?
On Thu, May 5, 2022 at 3:08 PM austin48 @.***> wrote:

thanks, it partially fixes SAK-47265. One of the indexes
(SAM_AG_AGENTID_I) in that jira still wasn't created after applying this
patch.
note, when applying the patch (on my MacBook), I had to use
--ignore-whitespace because it looks like the patch adds different line
endings . I'm not sure if that would affect github merging.
—
Reply to this email directly, view it on GitHub
https://github.com/sakaiproject/sakai/pull/10513#issuecomment-1118953164,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGF4CPURVY7HBGOO4FZA33VIQMBHANCNFSM5VDXPXOA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I don't think I have edit permission for this PR?  but here's the original index
./docs/conversion/sakai_2_6_0_mysql_conversion.sql:152:
create index SAM_AG_AGENTID_I on SAM_ASSESSMENTGRADING_T (AGENTID);


test: add fail-on-console plugin

Codecov Report

:exclamation: No coverage uploaded for pull request base (v5@8ef1cb1). Click here to learn what that means.
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@          Coverage Diff          @@
##             v5    #4880   +/-   ##
=====================================
  Coverage      ?   89.62%
=====================================
  Files         ?      105
  Lines         ?     3751
  Branches      ?      951
=====================================
  Hits          ?     3362
  Misses        ?      362
  Partials      ?       27

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


ci: [SDP-15829] move ci server env

So if I exclude the configure-oci-credentials step from the test job in the workflow, the test job looks like this

i.e. confirming that to access the repo, you need to be authenticated
If I add back in the configure-oci-credentials step to the test job then we get this:

i.e. confirming that the action is working


[Alternative Request] Usage of other storage solution than cache for validating state.

According to this old thread issue.
https://code.djangoproject.com/ticket/7639
LocMemCache is not ideal for production environments. In fact each process contains it's own cache object. So, in practice validate_state could always be false if you are running more than one thread to serve a Django application. (e.g. gunicorn)
While setting up a cache that spans across threads is the next ideal step this increases the dependencies for using the library in a production environment.

@izdi I can understand from a security standpoint the point of validate_state but it easier to add flag to disable that or update your documentation to state that you have to setup a cache system.

@avelis I assumed that production ready projects use a caching layer other than LocMemCache. So in my opinion, cacheobject uses cache backend specified in settings.py which eliminates need for additional documentation.
But I'll stick with you and add a check for cache backend.

Added proper documentation in 36178ffd740f3ec50fb31a1f34cdb0ff5dca1870


Cityflow Installationn

Hello all,
I am trying to install cityflow on Oracle Virtual box but getting the following error on windows 10...
$ sudo pip install .
Processing /media/sf_PhD_data/execution/colight-master/CityFlow
Building wheels for collected packages: CityFlow
Building wheel for CityFlow (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-graxh3bh/setup.py'"'"'; file='"'"'/tmp/pip-req-build-graxh3bh/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-k710sfqb
cwd: /tmp/pip-req-build-graxh3bh/
Complete output (35 lines):
running bdist_wheel
running build
running build_ext
CMake Error: The current CMakeCache.txt directory /tmp/pip-req-build-graxh3bh/CMakeCache.txt is different than the directory /media/sf_PhD_data/execution/colight-master/CityFlow where CMakeCache.txt was created. This may result in binaries being created in the wrong place. If you are not sure, reedit the CMakeCache.txt
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-req-build-graxh3bh/setup.py", line 60, in
setup(
File "/usr/lib/python3/dist-packages/setuptools/init.py", line 144, in setup
return distutils.core.setup(**attrs)
File "/usr/lib/python3.8/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/lib/python3.8/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/wheel/bdist_wheel.py", line 223, in run
self.run_command('build')
File "/usr/lib/python3.8/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/usr/lib/python3.8/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/usr/lib/python3.8/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/tmp/pip-req-build-graxh3bh/setup.py", line 32, in run
self.build_extension(ext)
File "/tmp/pip-req-build-graxh3bh/setup.py", line 56, in build_extension
subprocess.check_call(['cmake', ext.sourcedir] + cmake_args, cwd=self.build_temp, env=env)
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '/tmp/pip-req-build-graxh3bh', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/tmp/pip-req-build-graxh3bh/build/lib.linux-x86_64-3.8', '-DPYTHON_EXECUTABLE=/usr/bin/python3', '-DVERSION="0.1"', '-DCMAKE_BUILD_TYPE=Release']' returned non-zero exit status 1.
ERROR: Failed building wheel for CityFlow
Running setup.py clean for CityFlow
Failed to build CityFlow
Installing collected packages: CityFlow
Running setup.py install for CityFlow ... error
ERROR: Command errored out with exit status 1:
command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-graxh3bh/setup.py'"'"'; file='"'"'/tmp/pip-req-build-graxh3bh/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /tmp/pip-record-oi9cw0zl/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.8/CityFlow
cwd: /tmp/pip-req-build-graxh3bh/
Complete output (37 lines):
running install
running build
running build_ext
CMake Error: The current CMakeCache.txt directory /tmp/pip-req-build-graxh3bh/CMakeCache.txt is different than the directory /media/sf_PhD_data/execution/colight-master/CityFlow where CMakeCache.txt was created. This may result in binaries being created in the wrong place. If you are not sure, reedit the CMakeCache.txt
Traceback (most recent call last):
File "", line 1, in
File "/tmp/pip-req-build-graxh3bh/setup.py", line 60, in
setup(
File "/usr/lib/python3/dist-packages/setuptools/init.py", line 144, in setup
return distutils.core.setup(**attrs)
File "/usr/lib/python3.8/distutils/core.py", line 148, in setup
dist.run_commands()
File "/usr/lib/python3.8/distutils/dist.py", line 966, in run_commands
self.run_command(cmd)
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/usr/lib/python3/dist-packages/setuptools/command/install.py", line 61, in run
return orig.install.run(self)
File "/usr/lib/python3.8/distutils/command/install.py", line 589, in run
self.run_command('build')
File "/usr/lib/python3.8/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/usr/lib/python3.8/distutils/command/build.py", line 135, in run
self.run_command(cmd_name)
File "/usr/lib/python3.8/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
cmd_obj.run()
File "/tmp/pip-req-build-graxh3bh/setup.py", line 32, in run
self.build_extension(ext)
File "/tmp/pip-req-build-graxh3bh/setup.py", line 56, in build_extension
subprocess.check_call(['cmake', ext.sourcedir] + cmake_args, cwd=self.build_temp, env=env)
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '/tmp/pip-req-build-graxh3bh', '-DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/tmp/pip-req-build-graxh3bh/build/lib.linux-x86_64-3.8', '-DPYTHON_EXECUTABLE=/usr/bin/python3', '-DVERSION="0.1"', '-DCMAKE_BUILD_TYPE=Release']' returned non-zero exit status 1.
----------------------------------------
ERROR: Command errored out with exit status 1: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-graxh3bh/setup.py'"'"'; file='"'"'/tmp/pip-req-build-graxh3bh/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record /tmp/pip-record-oi9cw0zl/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.8/CityFlow Check the logs for full command output.
how to resolve it?
thanks in advanced.... :)

I'm stuck with a similar issue. Have you fix it?

Did you run pip install . at CityFlow root directory?

How to install cityflow into a specified virtual enviorment? Is pip install . available?