ERROR:  could not open extension control file "/usr/share/postgresql/9.4/extension/postgis.control": No such file or directory

Hi,
I tried to run CREATE EXTENSION postgis; on the image mdillon/postgis:9.4 from the docker hub. It complained that it couldn't find the file /usr/share/postgresql/9.4/extension/postgis.control
running bash inside the container reveals that in fact this file exists!
I already tried the following things:

building from this repository
changing ownership of /usr/share/postgresql/9.4/extension/ to the postgres user (RUN chown -R postgres:postgres /usr/share/postgresql/9.4/extension/)

Could you please look into this?
Cheers

How did you run the CREATE EXTENSION statement? Did you connect to the container with psql or something else?

I am using fig (http://fig.sh) for running a ruby on rails app which uses postgis. When I am running fig run app rake db:migrate rails tries to create the posgis extension with CREATE EXTENSION postgis; which then fails.

I just tested this successfully:
$ docker pull mdillon/postgis:9.4
# Time passes...
$ docker run -d --name some-postgis -e POSTGRES_PASSWORD=p mdillon/postgis:9.4
4825867790a1583c8bd9c58498ed876197795166855c513fca501d7c78a53f83
$ docker run -it --link some-postgis:postgres --rm postgres \
   sh -c 'exec env PGPASSWORD="$POSTGRES_ENV_POSTGRES_PASSWORD" \
             psql -h "$POSTGRES_PORT_5432_TCP_ADDR"
                     -p "$POSTGRES_PORT_5432_TCP_PORT" -U postgres'
psql (9.4.0, server 9.4.1)
Type "help" for help.
postgres=# create database postgis;
CREATE DATABASE
postgres=# \c postgis
psql (9.4.0, server 9.4.1)
You are now connected to database "postgis" as user "postgres".
postgis=# create extension postgis;
CREATE EXTENSION

Can you post your fig.yml? It might also be relevant to find out what version of Fig you're using, but probably not.

fig --version returns fig 1.0.0
my fig.yml is
db:
  image: mdillon/postgis:9.4
  ports:
    - "5432"
  environment:
    - POSTGRES_PASSWORD=yoloswag

app:
  build: .
  links:
    - db
  environment:
    - RAILS_ENV=production
    - DEVISE_SECRET_KEY=swaghettiYolonaise
    - SECRET_KEY_BASE=swaghettiYolonaise
    - OAUTH_FACEBOOK_KEY=swaghettiYolonaise
    - OAUTH_FACEBOOK_SECRET=swaghettiYolonaise
    - OAUTH_TWITTER_KEY=swaghettiYolonaise
    - OAUTH_TWITTER_SECRET=swaghettiYolonaise
    - OAUTH_GOOGLE_KEY=swaghettiYolonaise
    - OAUTH_GOOGLE_SECRET=swaghettiYolonaise
    - HOSTNAME=localhost:3000
    - SMTP_HOST=smtp.mandrillapp.com
    - SMTP_PORT=25
    - SMTP_USER=SOMEUSER
    - SMTP_PASSWORD=SOMEPASS
    -<EMAIL_ADDRESS>    - SENTRY_DSN=http://localhost

the dockerfile for the app installs postgresql-client

I can't see anything there that would affect whether or not the extension control file would be found or readable by the Postgres process.
Any chance you could post the exact error you get back when you run fig run app rake db:migrate? You may also want to look at what fig logs db has to say after the failure.

the error rails produces:
==<PHONE_NUMBER>0245 CreateFeatures: migrating ===================================
-- enable_extension("postgis")
rake aborted!
StandardError: An error has occurred, this and all later migrations canceled:

PG::UndefinedFile: ERROR:  could not open extension control file "/usr/share/postgresql/9.4/extension/postgis.control": No such file or directory
: CREATE EXTENSION IF NOT EXISTS "postgis"/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `async_exec'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `block in exec_no_cache'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract_adapter.rb:373:in `block in log'
/usr/local/bundle/gems/activesupport-4.1.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract_adapter.rb:367:in `log'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `exec_no_cache'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql/database_statements.rb:137:in `exec_query'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:663:in `enable_extension'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:656:in `block in method_missing'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:628:in `block in say_with_time'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:628:in `say_with_time'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:648:in `method_missing'
/usr/src/app/db/migrate/20140418190245_create_features.rb:3:in `change'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:602:in `exec_migration'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:586:in `block (2 levels) in migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:585:in `block in migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:294:in `with_connection'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:584:in `migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:759:in `migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:998:in `block in execute_migration_in_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:1044:in `block in ddl_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `block in transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in `within_new_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/transactions.rb:208:in `transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:1044:in `ddl_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:997:in `execute_migration_in_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:959:in `block in migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:955:in `each'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:955:in `migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:814:in `up'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:792:in `migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/railties/databases.rake:34:in `block (2 levels) in <top (required)>'
ActiveRecord::StatementInvalid: PG::UndefinedFile: ERROR:  could not open extension control file "/usr/share/postgresql/9.4/extension/postgis.control": No such file or directory
: CREATE EXTENSION IF NOT EXISTS "postgis"
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `async_exec'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `block in exec_no_cache'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract_adapter.rb:373:in `block in log'
/usr/local/bundle/gems/activesupport-4.1.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract_adapter.rb:367:in `log'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `exec_no_cache'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql/database_statements.rb:137:in `exec_query'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:663:in `enable_extension'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:656:in `block in method_missing'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:628:in `block in say_with_time'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:628:in `say_with_time'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:648:in `method_missing'
/usr/src/app/db/migrate/20140418190245_create_features.rb:3:in `change'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:602:in `exec_migration'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:586:in `block (2 levels) in migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:585:in `block in migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:294:in `with_connection'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:584:in `migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:759:in `migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:998:in `block in execute_migration_in_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:1044:in `block in ddl_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `block in transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in `within_new_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/transactions.rb:208:in `transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:1044:in `ddl_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:997:in `execute_migration_in_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:959:in `block in migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:955:in `each'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:955:in `migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:814:in `up'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:792:in `migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/railties/databases.rake:34:in `block (2 levels) in <top (required)>'
PG::UndefinedFile: ERROR:  could not open extension control file "/usr/share/postgresql/9.4/extension/postgis.control": No such file or directory
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `async_exec'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `block in exec_no_cache'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract_adapter.rb:373:in `block in log'
/usr/local/bundle/gems/activesupport-4.1.9/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract_adapter.rb:367:in `log'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:822:in `exec_no_cache'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql/database_statements.rb:137:in `exec_query'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/postgresql_adapter.rb:663:in `enable_extension'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:656:in `block in method_missing'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:628:in `block in say_with_time'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:628:in `say_with_time'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:648:in `method_missing'
/usr/src/app/db/migrate/20140418190245_create_features.rb:3:in `change'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:602:in `exec_migration'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:586:in `block (2 levels) in migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:585:in `block in migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:294:in `with_connection'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:584:in `migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:759:in `migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:998:in `block in execute_migration_in_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:1044:in `block in ddl_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `block in transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in `within_new_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/transactions.rb:208:in `transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:1044:in `ddl_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:997:in `execute_migration_in_transaction'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:959:in `block in migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:955:in `each'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:955:in `migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:814:in `up'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/migration.rb:792:in `migrate'
/usr/local/bundle/gems/activerecord-4.1.9/lib/active_record/railties/databases.rake:34:in `block (2 levels) in <top (required)>'
Tasks: TOP => db:migrate
(See full trace by running task with --trace)

and fig logs db
...
db_1 | LOG:  received smart shutdown request
db_1 | LOG:  autovacuum launcher shutting down
db_1 | LOG:  shutting down
db_1 | LOG:  database system is shut down
db_1 | LOG:  database system was shut down at 2015-02-14 00:01:24 UTC
db_1 | LOG:  autovacuum launcher started
db_1 | LOG:  database system is ready to accept connections
db_1 | ERROR:  could not open extension control file "/usr/share/postgresql/9.4/extension/postgis.control": No such file or directory
db_1 | STATEMENT:  CREATE EXTENSION IF NOT EXISTS "postgis"

And you said you were able to confirm that /usr/share/postgresql/9.4/extension/postgis.control exists with that exact path? Could you provide the output of docker exec $CONTAINERID ls -l /usr/share/postgresql/9.4/extension/postgis.control?

BTW, you probably don't want that ports: "5432". That's exposing your container Postgres on the Docker host's IP with a random port. The linked container will work directly with port 5432 inside the container with the ports declaration.

It seems fig doesn't recognize changes in the fig yml. Earlier I had image: postgres and now it starts the postgres image :| After I changed the name of the db to postgis fig recognized the different image. It now works
Sorry I've bothered you :( This is a flaw in fig.

Glad you figured it out. Since we took the time to debug it, it may be worth seeing if the issue has been reported at https://github.com/docker/fig


Test, cleanup, and document project build instructions

I'd like to get a few things cleaned up with the new build:

Add an install-nix.sh script to this repo for installing nix. (Crib from try-reflex)
Add a vagrant setup file to this repo for setting up a valid linux dev box for this project. Use this box for testing the build on linux, and it'll also be useful if there's any devs on Windows who want to work on the project.
Once we have these, and assuming everything works:

Delete the existing SETUP.sh and shared sandboxes stuff.
Update README with build instructions.

Build instructions shouldn't assume any knowledge of nix, cabal, or even Haskell. A monkey should be able to follow the instructions and know at the end whether they have a working setup. For example:
$ git clone https://github.com/unisonweb/platform.git unison
$ cd unison
$ # if you don't already have Nix package manager installed
$ ./nix-install.sh
# you'll be prompted to install nix package manager
$ cd node
$ nix-shell
# wait a while
$ cabal configure
$ cabal test
... # if all goes well
Test suite tests: RUNNING...
Test suite tests: PASS
Test suite logged to: dist/test/unison-node-0.1-tests.log
1 of 1 test suites (1 of 1 test cases) passed.

@Ericson2314 I can take care of the README updates, but do you think you could test out the build on Linux inside a Vagrant environment? Assuming that works, we can check in the vagrantfile.

Also, @Ericson2314 after this we should find something more interesting for you to work on, I know this is not super exciting. :) I might have some ideas.

Wait: does this mean Nix will now be required to use Unison?

@kirbyfan64 no definitely not. Unison should be usable on just about any platform. Nix would just be required for development of Unison. And we are talking about Nix the package manager, not Nix the OS.

@Ericson2314 okay, so current status is:

Build works on mac (or at least on my machine!), but waiting to hear from @joshcough who is trying it from fresh install.
Build does not work on linux. On the vagrant box I tried, I didn't even get as far as a successful install of Nix (see below), and apparently even after that it tries to compile the entire universe instead of getting binary caches. I think this is the most pressing issue, we really should have a working build on mac AND linux.
You had some suggestions for updating the instructions and using nix-build, and also for switching the vagrant box to NixOS. Please go for it!

Since I have a working build on mac, I'm going to focus on writing some real code for a bit. :) I'm hoping you can get build stuff sorted soon. Please let me know if I can help, though, or if you are just sick of working on it and would like to pass the torch to me or someone else. :)
Btw, here is the error I was getting, if we are switching the vagrant box to nixos, then it doesn't really matter, but just fyi -
$ vagrant up
...
==> default: error: the group ‘nixbld’ specified in ‘build-users-group’ does not exist
==> default: nix-binary-tarball-unpack/nix-1.9-x86_64-linux/install: unable to install Nix into your default profile
...
$ vagrant ssh
vagrant@vagrant-ubuntu-trusty-64:~$ cd /vagrant/node
vagrant@vagrant-ubuntu-trusty-64:/vagrant/node$ ./shell.nix
./shell.nix: line 1: syntax error near unexpected token `.unisonPackages.ghc7101.unison-node.env'
./shell.nix: line 1: `(import ../env.nix).unisonPackages.ghc7101.unison-node.env'

I did not get around to trying it last night, but will definitely tonight.

@pchiusano I think you need to run nix-shell instead of just ./shell.nix...

@kirbyfan64 ha, you are right. I meant to type shell.sh there. Trying again now...

Hmm, it looks like nix-shell did not even end up on the path after the install. Based on the warning message, I'm guessing it just didn't get added and I need to do it manually. I gotta work on other stuff right now but maybe will take a look later.

Going to close this and reopen a ticket just tracking the vagrant box setup.


[C++][CI] "C++ / AMD64 Ubuntu 20.04 C++ ASAN UBSAN" is failed

Describe the bug, including details regarding any error messages, version, and platform.
C++ / AMD64 Ubuntu 20.04 C++ ASAN UBSAN (link) is failing with following error:
[90/890] Building CXX object CMakeFiles/substrait.dir/substrait_ep-generated/substrait/extensions/extensions.pb.cc.o
FAILED: CMakeFiles/substrait.dir/substrait_ep-generated/substrait/extensions/extensions.pb.cc.o
/usr/bin/ccache /usr/lib/ccache/clang++-14  -DADDRESS_SANITIZER -DARROW_HAVE_RUNTIME_AVX2 -DARROW_HAVE_RUNTIME_AVX512 -DARROW_HAVE_RUNTIME_BMI2 -DARROW_HAVE_RUNTIME_SSE4_2 -DARROW_HAVE_SSE4_2 -DARROW_NO_DEPRECATED_API -DARROW_UBSAN -DARROW_WITH_RE2 -DARROW_WITH_UTF8PROC -Isubstrait_ep-generated -Iprotobuf_ep-install/include -Isrc -I/arrow/cpp/src -I/arrow/cpp/src/generated -Qunused-arguments -fcolor-diagnostics  -Wall -Wextra -Wdocumentation -Wshorten-64-to-32 -Wno-missing-braces -Wno-unused-parameter -Wno-constant-logical-operand -Wno-return-stack-address -Wno-unknown-warning-option -Wno-pass-failed -msse4.2  -fsanitize=address -DADDRESS_SANITIZER -fsanitize=undefined -fno-sanitize=alignment,vptr,function,float-divide-by-zero -fno-sanitize-recover=all -fsanitize-coverage=pc-table,inline-8bit-counters,edge,no-prune,trace-cmp,trace-div,trace-gep -fsanitize-blacklist=/arrow/cpp/build-support/sanitizer-disallowed-entries.txt -g -Werror -O0 -ggdb -fPIC   -fsanitize-coverage=pc-table,inline-8bit-counters,edge,no-prune,trace-cmp,trace-div,trace-gep -std=c++17 -Wno-error=shorten-64-to-32 -MD -MT CMakeFiles/substrait.dir/substrait_ep-generated/substrait/extensions/extensions.pb.cc.o -MF CMakeFiles/substrait.dir/substrait_ep-generated/substrait/extensions/extensions.pb.cc.o.d -o CMakeFiles/substrait.dir/substrait_ep-generated/substrait/extensions/extensions.pb.cc.o -c substrait_ep-generated/substrait/extensions/extensions.pb.cc
In file included from substrait_ep-generated/substrait/extensions/extensions.pb.cc:4:
In file included from substrait_ep-generated/substrait/extensions/extensions.pb.h:24:
In file included from protobuf_ep-install/include/google/protobuf/arena.h:52:
protobuf_ep-install/include/google/protobuf/arena_impl.h:45:10: fatal error: 'sanitizer/asan_interface.h' file not found
#include <sanitizer/asan_interface.h>
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.

@kou Do you have any idea?
Originally posted by @wgtmac in https://github.com/apache/arrow/issues/33656#issuecomment-1382730294
Component(s)
C++, Continuous Integration

It seems that it's a problem of deb package provided by LLVM.
In new packages, sanitizer/asan_interface.h is included in libclang-rt-14-dev but it's conflicted with libclang-common-14-dev. And clang-14 requires libclang-rt-14-dev. It means that we can't install both of clang-14 and libclang-rt-14-dev at once...


IgnoreFocusOut

ignoreFocusOut for inputboxOption and quickpickOptions is missing from the vscode.d.ts file.
It causes an error in my extension unless I manually change this typing whenever I do an npm install.

VSCode Version: 1.8.1
OS Version: Mac OS X

Steps to Reproduce:

npm install vscode
observe the IgnoreFocusOut property is missing

@dbaeumer I'm not too familiar with the vscode npm package and don't even see a vscode.d.ts file. Can you please take a look

Refer to this issue
https://github.com/Microsoft/vscode-extension-vscode/issues/45
On Thu, Jan 12, 2017 at 2:25 PM Matt Bierner<EMAIL_ADDRESS>wrote:

@dbaeumer https://github.com/dbaeumer I'm not too familiar with the
vscode npm package and don't even see a vscode.d.ts file. Can you please
take a look
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/18433#issuecomment-272257162,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEwP3j23EMsO_KnIgL3oGxm15yLskseIks5rRn40gaJpZM4LhXH9
.

Moving to @bpasero. Hope that is correct.

@celador make sure you declare a more recent vscode dependency. IgnoreFocusOut was introduced in August 2016 it seems (https://github.com/Microsoft/vscode/commit/cfbf71725cf9e626d21c9847fc517df7c877fc45)
http://code.visualstudio.com/docs/extensions/debugging-extensions#_common-questions

Thanks Ben, I updated my engine number and did npm install and everything is great again.  Thanks.


Bump Folders version to v2

https://cloud.google.com/resource-manager/reference/rest/v2/folders

from #556:
Folders are now GA, so it should no longer be necessary to use v2beta1 in order to get all the folder features.
WARNING init API "cloudresourcemanager" version v2beta1 is not formally supported in Forseti, proceed at your own risk.
You can get/set folder org polices in v1:
https://cloud.google.com/resource-manager/reference/rest/v1/folders
And all the get/set IAM policy stuff as well as create/delete/get/list/move/patch/search are all in v2:
https://cloud.google.com/resource-manager/reference/rest/v2/folders

This will be taken care of by #562
@lukwam


Forms - create form - create field - type "select" - minor error

When you create a new field of type "select", the application add "_id" to the field name but if you change the exhibition/display name, loses the "_id" and you have to select another type and select again (the type "select") to add again "_id".

Ready for the next version.
Thank you.

Ready for the next version.
Thank you.


Could be it pruned to ResNet model ?

so so

Temporarily, we are not planning to release the code for ResNet and Xception, due to non-technical issue. However, they can easily be implemented actually.

https://github.com/yihui-he/channel-pruning/releases/tag/ResNet-50-2X


This is set output test.

Proposed changes:

...

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

/modeltest


Set up Spills Salesforce Palletjack Instance

Benefit
The ERSpillsDatabase is to be replaced by the new Environmental Incidents Salesforce app.
Acceptance Criteria

[ ] https://github.com/agrc/deq-enviro/issues/665

Notes
No response
Risks
No response
Issue Reference
refs #

Sprint 3

Most of the work this sprint was dedicated to implementing table updating in palletjack. That PR is very close to being merged.
I have the deq-eid skid working with the version of palletjack that I've been working on. Once that palletjack PR is merged, then I should be able to deploy the skid and close out this issue.

24.1.4
https://github.com/agrc/deq-eid-skid has been deployed to production and enviro has been pointing at the new AGOL services. Still waiting on Michelle to create the dry cleaners layer but I think that's a small thing that doesn't need to be tracked in PI planning.


Added --force (-n) option. Fixes #1059

Fixes #1059

Thanks @sasidhar! Is there any specific reason you chose -n as an alias for --force? I'm thinking we should just have --force and not bother with a shorthand -n option.

@JKillian Sure. I will update and send another PR.

No worries @sasidhar, I had a spare moment so I just made the tweaks myself over in https://github.com/palantir/tslint/pull/1073. Thanks for this PR, this'll be a useful feature!


Order HDMI & USB Drives for Embedded Systems

3 HDMI cables (gold plated)
2 USB 3.0 drives > 16 gb
2 SDHC or SDXC Cards > 16 gb

3x http://a.co/8qFXxnZ
3x http://a.co/3jqHSZv
2x http://a.co/2BF2mnt
2x http://a.co/9wH3FgC


Test the runtime performance of the CV stack

Time estimate: 5-15 hours
Description of task:
The runtime performance of the Vortex-CV pipeline needs to be quantized in terms of general and unitary resources use, module optimization, and runtime speed of individual functions and packages, as well as the stack as a whole.
Should be done both in the OpenCV is in CPU-only mode, and with GPU-computing enabled (  #67 ).

The performance has been solved by having Xavier as a dedicated flight computer.


[Tabs] mat-tab-header doesn't horizontally scroll to the end (till div.mat-tab-header-pagination)

Reproduction
Use StackBlitz to reproduce your issue: https://stackblitz.com/angular/gopxbvgdpkv?file=app%2Ftab-group-dynamic-example.ts

Steps to reproduce:

Add tabs until the div.mat-tab-header-pagination element appear
Select the last tab
Start deleting tabs one by one

Expected Behavior
The tab header section should re-scroll horizontally to the end (that is, where it meets the paginator)
Actual Behavior
The tab header does not re-scroll.
Environment

Angular: 8.1.4
Browser(s): All modern browsers

Agreed, on a mobile device with 3 tabs, the user has to manually click the > button in order for the scroll to reach the limit.


Update deps

Dependency roll-up, bypassing GreenKeeper
This PR is BROKEN!!
GK PR "Update fontfaceobserver to version 2.0.1" breaks the project but all tests and build pass in GK, Travis, AppVeyor and Local (Mac OS).
Execution in browser produces console error:
Uncaught TypeError: openSansObserver.check is not a function localhost/:75
This PR is submitted to demonstrate the hazard of merging GK PRs that pass without further human inspection. Is it possible/practical to create automated integration testing?

Coverage remained the same at 98.217% when pulling 7b5c23a1c048a61ec60dd65abb47113f210bd5d4 on gihrig:update-deps into 22e359b92ba2bf890165605a4e1124201a4fa083 on mxstbr:master.

Coverage remained the same at 98.217% when pulling a6d811782dfd049a8fffbd3cdef4d7aa974f8ff9 on gihrig:update-deps into 22e359b92ba2bf890165605a4e1124201a4fa083 on mxstbr:master.

PR is FIXED

Brings all packages up to latest (July 8 2016 @16:46 PDT)
Fixes breakage caused by fontfaceobserver 2.0.1
Tested in dev and production, including tunnel, setup, clean and generate (does not fix existing generate issues #337)
Triggers warning on browser console in dev mode only:

offline-plugin: runtime.install() was executed without OfflinePlugin being added to webpack.config.js. The installation of offline-plugin has not been performed. You can ignore this message if you are skipping the OfflinePlugin during development. Otherwise, you may have a configuration issue. runtime.js?11f5:7

Awesome, thanks so much @gihrig!

Is it possible/practical to create automated integration testing?

We probably should, but the problem is that it shouldn't live in this repo since that's what users clone. Any ideas?

@mxstbr Percy was the only thing that looked close on GitHub's Integrations page. It does cloud based UI testing, not exactly what I was looking for, but if the example app works as expected, I guess that's a pretty good integration test.
Percy integrates with Travis, setup looks to be straightforward
If this looks like something you would consider, I'll be glad to look into it in more detail.

Please do @gihrig!

As of today, percy still does not support React.


Confusing UI in case of automatic retry

Repro:

Schedule task to run with dimensions that make it runnable only on one bot.
Task fails with BOT_DIED after generating stdout.
Task is rescheduled automatically.
Task stays in PENDING state.

Expected:

UI explicitly states what is happening.

Actual:

UI shows the task is in PENDING yet shows stdout. It stays in this state for several minutes. This is very confusing for the user.

With the new UI, there is a bit more explaining about what is going on with the auto retries: https://chromium-swarm.appspot.com/task?id=332a28c3d025e310&refresh=10

In the new UI, this can still be a bit confusing: https://chromium-swarm.appspot.com/task?id=33e91f3119745610&refresh=10
The stdout/milo shows up, but pending/cancelled shows up in the request spot.


Navigation styling is broken

The navigation styling is broken. I can see there is a nav-current class for styling the current page, but there is no logic setup to change this when the user switches pages. Here is the code:

The home code was commented out, but uncommenting it and building the website shows the issue. Without it there is no indication as to what page the user is on.
Here is a screen shot of what is rendered, note the user is actually on the about page here, not the home page as indicated:

Is this something you plan to address?

I didn't know about the problem.
In the 'London' that became the base of this starter, I will check about that.

I didn't know about the problem.
In the 'London' that became the base of this starter, I will check about that.


Small UI Bug

Small UI Bug around when I'm not using the application with a very large screen. at the time the screen size was probably 800 X 600 px

Happens for me as well on MacOS, and it's always like that when the app is not in fullscreen mode. Version of the app I'm using is <IP_ADDRESS>91443794.

@austinlg this is a duplicate of #264, suggest to close this one.


Question about the localhost:8000/index.html

Question about Get metric values (e.g. service availability, message loss rate) in real-time as time series graphs. Does this feature still work.
Where is the port for the web app configured now that it has been removed from the kafka-monitor.properties. I cannot hit localhost:8000/index.html successfully (the site can't be reached)

+1

Hi msgPDC, we previously removed some unnecessary dependencies on Jetty. which is needed only for Jolokia Service, to narrow down the scope of the testng dependency..
It will initiate the embedded web server if you wanted to run the service.
+1 @smccauliff if he wants to add any extra insights.

index.html is just a static page, I think you can put the related static resources into a web server and then open it. I adjusted the position of /js /.. to ./js/.. and quickly opened it via IDEA.


Update to Python 3.6 also on AppVeyor

I forgot to update python3 on AppVeyor in #2429.

Appveyor build fails...

Oh, Python 3.6 requires VC2015, but we are still using VC2010 on AppVeyor.
I think we should keep using VC2010 so that C99 style code can be detected on each PR.
(VC2015 can compile C99 style code.)
I withdraw this PR.


Enhacements.

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

[x] Remove npm dependency.
[x] Add tests Assets.
[x] Fixed minor corrections.

👍


Merge of 4.Future => Master

Pull Request Test Coverage Report for Build 82184

0 of 0   changed or added relevant lines in 0 files are covered.
991 unchanged lines in 89 files lost coverage.
Overall coverage decreased (-0.5%) to 76.834%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Twilio/TwilioAdapter.cs
1
85.71%

/libraries/integration/Microsoft.Bot.Builder.Integration.ApplicationInsights.Core/ApplicationBuilderExtensions.cs
1
71.43%

/libraries/integration/Microsoft.Bot.Builder.Integration.AspNet.Core/ConfigurationChannelProvider.cs
1
75.0%

/libraries/Microsoft.Bot.Builder.AI.LUIS/Generator/Age.cs
1
75.0%

/libraries/Microsoft.Bot.Builder.AI.LUIS/Generator/Money.cs
1
75.0%

/libraries/Microsoft.Bot.Builder.AI.LUIS/Generator/Temperature.cs
1
75.0%

/libraries/Microsoft.Bot.Builder.AI.LUIS/LuisApplication.cs
1
95.45%

/libraries/Microsoft.Bot.Builder/BotStateSet.cs
1
85.0%

/libraries/Microsoft.Bot.Builder.Dialogs/Prompts/NumberPrompt.cs
1
99.04%

/libraries/Microsoft.Bot.Builder.Dialogs/Prompts/PromptRecognizerResult.cs
1
85.71%

Totals

Change from base Build 82147:
-0.5%

Covered Lines:
7111

Relevant Lines:
9255

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3


Python 3.9 image build broken

Located at https://github.com/shivupa/cclib-ci/runs/4653867940?check_suite_focus=true#step:6:2539, it's from https://github.com/rpmuller/pyquante2/blob/6e34cb4480ae7dbd8c5e44d221d8b27584890c83/cython/cone.c#L5318, which is the C code distributed with pyquante2. We could either:

replace pyquante2 (https://github.com/cclib/cclib/issues/1077, most likely solution)
fork pyquante2, rerun Cython, commit the new C code
fork pyquante2, delete all the C code, run Cython during each image build

Fixed in #11 and then #15


[Backend] DB design for Video Conference Service

Support individual video rooms and password to join rooms

Completed.
https://app.zenhub.com/files/335822753/f28c5abb-23d0-4228-ae20-2df49d8ceea4/download


fix: update to latest flagger

update flagger lib version to support flagger 1.16.

@Duologic tagging to get your attention, since the last PR on flagger seems to have had you as a reviewer. Please redirect as appropriate.

Merged from https://github.com/jsonnet-libs/k8s/pull/95. Thank you for your contribution @brewkode !


Added TCHAR_TO_WCHAR to fix issue 602

This pr is a fix for issue #602
Please let me know if there is anything else it should include.  Thanks to @ishyesh for figuring out the solution.

Thanks


Additional fix for #4444 to prevent errors on windows

Summary
See https://github.com/facebook/jest/issues/4444#issuecomment-843766162
I would love to get ay feedback on what kind of fix would be accepted, this is just one possibility.
Test plan
This issue is intermittent and windows only.

Codecov Report

Merging #11423 (2c2d59b) into master (2047a36) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #11423      +/-   ##
==========================================
- Coverage   69.32%   69.31%   -0.01%
==========================================
  Files         311      311
  Lines       16241    16243       +2
  Branches     4700     4701       +1
==========================================
  Hits        11259    11259
- Misses       4954     4956       +2
  Partials       28       28

Impacted Files
Coverage Δ

packages/jest-transform/src/ScriptTransformer.ts
78.57% <0.00%> (-0.48%)
: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 2047a36...2c2d59b. Read the comment docs.

https://github.com/facebook/jest/releases/tag/v29.1.0


Unique environment variable per server not working.

With mupx I could add unique environment variables to each server, specifically hostname. It doesn't seem to work with kadirahq/meteor-up

#313


Scale object in theme

💬 Questions and Help
I wonder is there any way to do responsive scale in theme object, like how styled-system does https://styled-system.com/theme-specification#scale-objects.
{
...
  texts: {
    heading: {
      fontSize: { sx: '14px', md: '16px', lg: '18px' }, // does't work with xstyled
      // fontSize: ['14px', '16px', '18px'], with styled-system
    },
  }

<x.p text="heading" />

Thanks!

Actually that's not the way it works but I will consider it! Thanks.

Thanks! I wonder how did you handle it?
or something like:
<x.p text={{ xs: 'heading1', lg: 'heading2' }} />

<x.p text={{ xs: 'heading1', lg: 'heading2' }} />

yeah


Clarify supported pattern matchers

From the README the following is not clear IMHO:

Which patterns are supported/implemented?
That this package follows EventBridge pattern matching, i.e. highlight as feature in README to reuse EB patterns?

Having a table which maps existing patterns, e.g. from EventBridge, to supported/unsupported in the README would be nice, e.g.:

Pattern
Suppported
Notes

exists
Yes

shellstyle
Yes*
Only single wildcard * supported

number
Yes*
Number matching is weak

Thoughts?

Agreed.


Update to support CF API Tokens ?

HI @pmeenan  any plans on updating your example cf-worker scripts to support Cloudflare's new API token method https://blog.cloudflare.com/api-tokens-general-availability/ where CF Global API Keys are currently used ?

I'm not actively working on any of them but I'm happy to accept (tested) pull-requests.

thanks Patrick for the reply - unfortunately I am not javascript savy - hence the question :)


Importing scoped npm modules without scope name

This is a question.
We have some private NPM packages using npmjs' private repository. Assume

scope name : @scope
private package name as : private-package

When we install this NPM package using
npm install @scope/private-package
It is installed to : ./node_modules/@scope/private-package
In VSCode, to import some thing from this package, we need to do
import {SomeThing} from '@scope/private-package'
Is there anything in TypeScript configuration that we can re-map
@scope/private-package to private-package
so that we can use like
import {SomeThing} from 'private-package' instead of adding@scope?

See paths tsconfig.json option - https://github.com/Microsoft/TypeScript/issues/5039#pathMappings and https://github.com/Microsoft/TypeScript/pull/5728

@Arnavion Thanks for the references.
I tried paths with 1.8.9 and found it is not yet out.
Seems it is planned for 1.9.0.


[HUDI-3883] Add new Bulk Insert mode to repartition the dataset based on Partition Path without sorting

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
Adding new bulk-insert mode PARTITION_NO_SORT which performs re-partitioning using hoodie.table.partition.fields, without additional sorting w/in the partition which allows to address following issues:

Using NONE mode while bulk-inserting into partitioned table (with N partitions and parallelism P) unless inserted dataset has been re-partitioned prior using table's partition columns, at least N x P files will be created (at least P files in every partition). This occurs simply b/c w/o any repartitioning or sorting (on partition column) every Spark partition is likely to contain records belonging to every partition, therefore every executor handling individual partitions will be writing into table's every physical partition independently producing poorly sized tables. Example of that could be found in the HUDI-3883.
Using GLOBAL_SORT or PARTITION_SORT, aforementioned problem is alleviated (b/c the dataset is ordered/partitioned by the partition column) but it adds an overhead of the need to do global/local sorting (while bringing benefits files ordered by primary key which is beneficial for upsert performance)

That way PARTITION_NO_SORT is a middle-ground which is still performing re-partitioning aligning well Spark partitions with table's physical partitions.
Brief change log

Cleaning up existing partitioner impls (avoiding unnecessary transformations, simplifying)
Added new PartittionNoSortPartitioner
Added tests

Verify this pull request
This pull request is already covered by existing tests, such as (please describe tests).
This change added tests and can be verified as follows:
Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

high level comment. I would prefer to introduce a new sort mode instead of fixing NONE. and add documentation around when to use which sort mode so that users are aware of diff sort modes and their implications

@alexeykudinkin : please address the feedback on adding a new sort mode.

CI is green:
https://dev.azure.com/apache-hudi-ci-org/apache-hudi-ci/_build/results?buildId=10228&view=results

@yihua can you please elaborate on the repartitioner you're referring to?

CI is green:

https://dev.azure.com/apache-hudi-ci-org/apache-hudi-ci/_build/results?buildId=10343&view=results

@alexeykudinkin any change you have revised the PR based on the discussion to have new bulk insert modes for the repartitioning behavior?

Superseded by 7872


Issue with az vm list-skus

I have a customer who is having issues with az vm list-skus CLI command not listing a particular VM SKU(D15_v2) in a region(CentralUS) as being available.

But the SKU is shown as being available in PS AzureRM command Get-AzureRmVMSize and also shows up as available in the Azure Portal.
Interestingly the VM with that SKU can be deployed using portal as well as using CLI. It just the CLI command az vm list-skus does not show the SKU as being available.
Would appreciate if we can find the reason on why the SKU does not show as being available even though deploying the same VM SKU works just fine.
Thanks in advance!

hi @qwordy could you pls check why the sku not sured? this is pure rest call. Maybe caused by API version difference?

Please note the issue persistent in cloud shell session too.

My result.
yfy@DESKTOP-ARGPJS4:~$ az vm list-skus --location centralus | grep D15
    "name": "Standard_D15_v2",
    "size": "D15_v2",

Can you add --debug to your command to check the request and response?

Your log:
msrest.http_logger : Request URL: 'https://management.azure.com/subscriptions/1fd1d0ad-a457-4f28-a2e7-810438683bc1/providers/Microsoft.Compute/skus?api-version=2019-04-01'
msrest.http_logger : Request method: 'GET'

My log:
msrest.http_logger : Request URL: 'https://management.azure.com/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/providers/Microsoft.Compute/skus?api-version=2019-04-01'
msrest.http_logger : Request method: 'GET'

The only difference is subscription.
Can you try GET https://management.azure.com/subscriptions/1fd1d0ad-a457-4f28-a2e7-810438683bc1/providers/Microsoft.Compute/skus?api-version=2020-06-01

Are you saying to run this?
az rest -m get --header "Accept=application/json" -u ‘https://management.azure.com/subscriptions/{subscriptionId}/providers/Microsoft.Compute/skus?api-version=2020-06-01'

I usually send HTTP request using Postman. Command line tool is also a good choice, like az rest, curl, wget.

I check the result you send to me and find that Standard_D15_v2 appears. We will upgrade the API version of "list skus".

@avirishuv
Do you think we should use
https://management.azure.com/subscriptions/0b1f6471-1bf0-4dda-aec3-cb9272f09590/providers/Microsoft.Compute/skus?api-version=2020-06-01

instead of 2019-04-01?
However, I can't find skus.json in
https://github.com/Azure/azure-rest-api-specs/tree/master/specification/compute/resource-manager/Microsoft.Compute/stable/2020-06-01

Looking into the issue

Assigned to Avi.

@avirishuv Kindly ping.

@avirishuv - Request any update on this please.

@qwordy @smoop-msft as discussed, the issue was related to zone level availability for the specific deployment. The API and CLI responses were as per the expected behavior. Closing the issue, thanks.


client should be able to redirect and indicate it is a 404

Something like
GET /urlz/param
document.location = /urlz/param?code=404
the server then knows that next time /urlz/param is requested, the statusCode is 404, not 200.

Actually, the correct way to handle this should be with throw new HTTPError(404)

No no no, the correct way is to always redirect.


Cleanup of k8petstore json formatting flaw, and parameterization of kube...

This fixes a json error (which I think is new, maybe the json libs got updated or something), and also parameterizes kubectl so that it can easily be used in dev/test environments,

Can you add the k8spetstore JSON to examples_test?  I recently removed core yaml support in the API which triggered stricter checking, and we rely on examples_test.go to catch formatting errors.

Oh, I see it's only in your script.  Never mind about examples test, it can't find things in bash scripts (yet)...

@smarterclayton  I have a PR going in to make it easier to call kubectl examples #5773 ... From there i can i think write it into  examples_test. maybe     ?  will look into it now.
great idea!

LGTM


Resource Templates Created using "Copy" Function Won't Open for Editing

I recently created a number of new resource templates in production, using the "copy" function. After creating these new templates, a number of the original templates they were based on were deleted per issue #2809 because they were no longer needed. Now, we (University of Washington Libraries) are unable to open the new templates for editing, and get an error message saying "Error retrieving [URL for old template]: Error parsing resource: Sinopia API returned not found". Here's an example:

This is making it impossible for us to edit our templates, which we need to do before uploading our BIBFRAME data to Sinopia.
We would like to be able to open and edit the following resource templates without this error, preferably without needing to re-create the templates one by one. Did we create these templates incorrectly, or is this a bug? It struck me as odd that the URL in the error message was not the URL for the resource we're trying to open, but for the resource it was copied from.
WAU:RT:BF2:Work
WAU:RT:BF2:VariantTitle
WAU:RT:BF2:Identifier
WAU:RT:BF2:Frequency
Thanks,
Crystal Clements
@gerontakos
@briesenberg07
@mcm104
@JianPLee
@lu-wa

Yes, this is fixed. Thank you @justinlittman !


Line splitting for ++ operator

How is this different from line splitting of any other binary operator?

@whatyouhide it line splits the same way as the <> operator, except I forgot to implement it. The issue is just to remind myself. 😛


fix: invalidate computed variables in Project Job Scheduling correctly

Due to incorrectly invalidated busy dates for allocations, no new best solutions were found, and therefore the screen was never refreshed.

Thanks for the review. On the whole, I agree - this example is complex, and it is a use case which we should be able to show off better.
Taking into account the priorities, I do not think it will happen any time soon.
Examples are in maintenance mode, and have been for a very long time now.


Update README.md

Not sure why you are proposing this change. Closing this issue. This is not an acceptable change for this repo's Readme.


Text overflow in settings > vencord > plugins

I hope this is the correct place to post this but the picture below is self explanatory

here is the full screen for reference

if you didn't quite get it big plugin names go out of the box.

will be fixed in the next push 👍

btw it's Comfy's repository here, not Couve

will be fixed in the next push 👍

Noice


Could we add support for iPhone XS Max?

I need support for iPhone XS Max. Was not able to send pull request because of authentication failure. Could anyone help to add the following? Thanks.
{
 "type": "ios",
  "rules": [
    {
      "res": [
        1242,
        2688
      ]
    }
  ],
  "dpi": 458,
  "bw": 4,
  "ac": 1000
},

I have added a PR for this!

Closed via #51


containerd 1.4.1 ; openssh client in sshd

Two changes:

bumps the linuxkit/sshd version to the latest. The only real difference is that this one includes openssh-client package, so you can ssh from within the device, as well as scp from and to the device
bumps the linuxkit/containerd version to the latest. This bumps the containerd version to 1.4.1, which has better memory management (among other things)

Unclear if this will resolve the "many goroutines" question, but it is something we have wanted to do anyways.

I don't understand why this is failing. Well I do, because it is looking for a signed version of linuxkit/containerd:a4aa19c608556f7d786852557c36136255220c1f-amd64, which doesn't exist; only linuxkit/containerd:a4aa19c608556f7d786852557c36136255220c1f (without the amd64) does exist.
But why is it trying to get linuxkit/containerd:a4aa19c608556f7d786852557c36136255220c1f-amd64 (with -amd64)? The change to the hash exists only in one file images/rootfs.yml.in, and that one has the right tag.
@rvs do you understand this build process?
here are the relevant lines from CI:
patching file images/rootfs-kvm.yml.in.sed (read from images/rootfs.yml.in)
./tools/makerootfs.sh images/rootfs-kvm.yml /home/circleci/project/dist/amd64/installer/rootfs-0.0.0-pull_1546-1fd4fb12-kvm-amd64.squash squash
Extract kernel image: lfedge/eve-new-kernel:b3f036b5a6acb7660eaafedc58a8cbbe0de61cbe-amd64
Pull image: lfedge/eve-new-kernel:b3f036b5a6acb7660eaafedc58a8cbbe0de61cbe-amd64
Add init containers:
Process init image: linuxkit/init:v0.5-amd64
WARN[0002] Error getting targets/rolf: valid signatures did not meet threshold for targets/rolf
WARN[0002] targets/justin metadata is nearing expiry, you should re-sign the role metadata
Pull image: docker.io/linuxkit/init:v0.5-amd64@sha256:3af573658bd0a42e497f7a00b9541830d3145b4c7df64bdea482c910a0ca9f98
Process init image: linuxkit/runc:f79954950022fea76b8b6f10de58cb48e4fb3878-amd64
ERRO[0004] Metadata for targets/justin expired
WARN[0004] Error getting targets/justin: targets/justin expired at Sun Aug 16 13:47:33 +0100 2020
ERRO[0004] Metadata for targets/riyaz expired
WARN[0004] Error getting targets/riyaz: targets/riyaz expired at Mon May 25 15:32:34 -0700 2020
WARN[0004] Error getting targets/rolf: valid signatures did not meet threshold for targets/rolf
Pull image: docker.io/linuxkit/runc:f79954950022fea76b8b6f10de58cb48e4fb3878-amd64@sha256:879748f7ed03b51f562022b73f964f90b893ca0ba269c84e7dd4d485afefdaf0
Process init image: linuxkit/containerd:a4aa19c608556f7d786852557c36136255220c1f-amd64
ERRO[0006] Metadata for targets/justin expired
WARN[0006] Error getting targets/justin: targets/justin expired at Sat Sep 19 21:27:19 UTC 2020
ERRO[0006] Metadata for targets/riyaz expired
WARN[0006] Error getting targets/riyaz: targets/riyaz expired at Sat Jun 6 08:35:43 -0700 2020
WARN[0006] Error getting targets/rolf: valid signatures did not meet threshold for targets/rolf
FATA[0006] Failed to build init tarball from linuxkit/containerd:a4aa19c608556f7d786852557c36136255220c1f-amd64: Could not pull image linuxkit/containerd:a4aa19c608556f7d786852557c36136255220c1f-amd64: Trusted pull for linuxkit/containerd:a4aa19c608556f7d786852557c36136255220c1f-amd64 failed: No valid trust data for a4aa19c608556f7d786852557c36136255220c1f-amd64

Hey @deitch a few answers:

don't understand why this is failing. Well I do, because it is looking for a signed version of linuxkit/containerd:a4aa19c608556f7d786852557c36136255220c1f-amd64, which doesn't exist; only linuxkit/containerd:a4aa19c608556f7d786852557c36136255220c1f (without the amd64) does exist.

Au contraire -- it seems that on my end -- I have no trouble pulling both:
$ docker pull linuxkit/containerd:a4aa19c608556f7d786852557c36136255220c1f-amd64
...
Status: Downloaded newer image for linuxkit/containerd:a4aa19c608556f7d786852557c36136255220c1f-amd64
docker.io/linuxkit/containerd:a4aa19c608556f7d786852557c36136255220c1f-amd64

That said -- the whole "trust data" thing needs to be looked at because I see it is failing the same way for me.

But why is it trying to get linuxkit/containerd:a4aa19c608556f7d786852557c36136255220c1f-amd64 (with -amd64)? The change to the hash exists only in one file images/rootfs.yml.in, and that one has the right tag.

We relying on explicit architecture tagging to make sure we can assemble ARM64 images on x86 host. Hence tools/parse-pkgs.sh has logic to add that to the actual yaml it generates for the build.

Ah that explains it. The official linuxkit images are signed only once, at the multiarch manifest level. So only abcdef1234 is signed, and not abcdef1234-amd64, since the first includes the hash for the second which includes the hashes for each layer. It is the same reason it doesn't sign the hash for each layer.

When you pull abcdef1234, it automatically resolved it to abcdef1234-amd64 when you are on amd64.
I think you are saying, "that's nice, but I want to assemble for arm64, if I choose to do so, even if I am on amd64." Is that right?
I had thought lkt had an option for that, but if not, we certainly can add it. Is that what you were after?

I think you are saying, "that's nice, but I want to assemble for arm64, if I choose to do so, even if I am on amd64." Is that right?

yes

I had thought lkt had an option for that, but if not, we certainly can add it. Is that what you were after?

well, we have that option today ;-)
the problem is -- linuxkit is somehow screwing up that trust thing again -- as I noted I have no problem fetching that -amd64 image via Docker CLI alone
I think we need to get to the bottom of what's wrong with linuxkit

Sorry @deitch -- missed this:

Ah that explains it. The official linuxkit images are signed only once, at the multiarch manifest level. So only abcdef1234 is signed, and not abcdef1234-amd64, since the first includes the hash for the second which includes the hashes for each layer. It is the same reason it doesn't sign the hash for each layer.

welp -- then linuxkit, indeed, needs to be updated

You are using the "implicit API" here. Sure, the amd64 image underlying abcd1234 is abcd1234-amd64, but it doesn't have to be, and there are some areas where it isn't (luckily, eve doesn't need any of those for now), and it might change in the future. The only thing guaranteed is:

abcd1234 is multi arch
abcd1234 is signed

You are saying that lkt needs an explicit api to get at those images per platform. Definitely agreed.

As discussed offline, what we really are trying to do is use lkt to build an image for arm64 while on amd64 (or vice-versa). We made it happen by "hacking" at the image tags, which is the "implicit API" represented above. But that API was never fully supported, e.g. you cannot rely on the image tag for one arch being "image tag for multiarch with -<ARCH> appended, and lkt doesn't sign the arch-specific images, only the manifest.
The right solution is to get lkt to support lkt build --arch arm64 and it will build for arm64, no matter what you are on.
We are going to leave this open until we get that support into linuxkit, which I am working on.

Thanks @deitch -- waiting for upstream linuxkit fix then -- in the meantime shouldn't we close this PR?

Nope, we can leave it open. The actual hash version won't change; just the linuxkit build tool.
I already am engaged in conversations about how that should look.

I am super confuse by the latest changes in this PR @deitch ;-)

Don't worry about it. This will remain open until we can get the lkt cross build in place.
Short form is that it updated to latest:
containerd: for 1.4.1
sshd: for ssh client
init: for logging features

I removed the sshd update, based on the work @rvs did on #1640 . So this is just updates to linuxkit/init and linuxkit/containerd.
Also I manually signed those packages, so this will pass, until cross-arch building works in linuxkit.


Need help using global appModel/understanding data binding

Hi - I am starting to learn preact/vdom/data-binding internals, and as an experiment looking to port automatic data-binding (like in vue.js framework by the use of watchers) to preact.  It would be on the lines of generating a watch expression for all dependencies in a component and then subscribing to it by using Object proxies whenever an attribute changes. The idea is to implement something like this:
A global object representing the state of various pieces:
var appModel = {
  'user': {  },
  'tweets': [ ],
  'notifications': [],
  'followers': []
}

And, different components watching/binded over parts of the above model:
Preact.render(<ProfileBox user={ appModel.user } />, document.getElementById('profile'));
Preact.render(<TweetList list={ appModel.tweets } />, document.getElementById('tweetList'));

What would be a good starting point to explore this?
Are there ways already with preact to achieve something like above?
Are there any major challenges that are foreseen in developing an example as above.

Vue is build with mutation in mind by converting data model's to getter/setter for dependency tracking and change notifications. While preact follows react's immutability and state cannot be changed. Using a Object proxy is kind of defeating the purpose here.
However, you can have one object converted to getter/setter, with setter doing setState, and getter getting the state.

Hi @yaodingyd - thanks for the info. As I mentioned I would like to add binding via mutation to preact if needed, as an experiment to see how a single global object model can be used for state changes.
I will try the approach mentioned above by converting setters to setState and see if that works as expected.

If you are looking for a single global object model for state change, then it's exactly what Redux is doing: one single data store which is the sole source of truth. But I think the focus of what you want to achieve is notification through mutation, not to call setState repeatedly.

Am looking at both. So I wanted to try to convert to use notifications for object mutation handling than calling setState repeatedly. To build a working example I chose to have a global object model. I haven't used Redux before - let me take a look on how it works. Thanks a lot for the guidance.

MobX is also a decent source of inspiration here. If you're looking at setting up a subscription mechanism (eg: via context) rather than using Preact's own state management, you should be able to use Component#forceUpdate() or Component#setState({}) to trigger arbitrary re-renders of a wrapper component in response to your state object being mutated.
@sangupta you might find this Gist I created a while ago interesting:  it's more like Redux than Vue's state management, but shows you how to set up subscriptions:
https://gist.github.com/developit/55c48d294abab13a146eac236bae3219
Also, if you're just looking for mutations that automatically trigger rendering, you might find this tiny implementation of Glimmer's @tracked decorator interesting - it lets you create observed properties that are treated as Preact state:
https://gist.github.com/developit/006c58bba02be99e9a2ea1aca536dd33

@developit thanks a bunch for the advice. I had worked the @tracked decorator approach after suggestions from @yaodingyd.
I assume the approach mentioned in the first gist is the one that is being used in https://github.com/nightwolfz/mobx-preact - it uses the same provider concept.
Anyhow, it has been a great learning curve for me with preact till now. Thanks @developit for the wonderful framework.
@developit  I have added some notes (JSDoc) to functions in preact code to make it more meaningful for newbee's like me - should I raise a PR for them?

Totally @sangupta! I've been meaning to improve the JSDoc annotations in Preact for a while.  That, or convert it to typescript :)

Am closing this one now, as my queries have been answered. Thanks to everyone on the team.


fix(coverage): exclude no effect expressions from coverage

Motivation
Closes #7476

Solution

exclude from coverage expressions that doesn't have effect
compare LHS and RHS expression name and exclude if same
test

going to close this per https://github.com/foundry-rs/foundry/pull/8442#pullrequestreview-2176685556


make ready for telegraf 0.10.x

make ready for telegraf 0.10.x

Hey what's the status on this?  Any work I can pick up and help finish?

Hey,
Wanted to use the module too.I found that today that might help(didn't test
it yet)
https://forge.puppetlabs.com/datacentred/telegraf/readme
Seems to be compatible with the latest config file changes that rpl's
module is missing.
Cheers
On 9 Mar 2016 4:51 p.m., "Ashton Davis"<EMAIL_ADDRESS>wrote:

Hey what's the status on this? Any work I can pick up and help finish?
—
Reply to this email directly or view it on GitHub
https://github.com/rplessl/puppet-telegraf/issues/19#issuecomment-194392771
.

Thanks a lot, I'll check that out in the meantime.

close this issue will merge telegraf ready parts in new issue


PrivetRegistration.PrinterPanelCancel/PrivetAPI.RegistrationInvalidUserAuthToken failed

Our printer is the button LED control panel, only have OK button on it.
Test case "PrivetRegistration.PrinterPanelCancel" will be skipped if set PRINTER_PANEL_UI to false, the final results are passed. but test case "PrivetAPI.RegistrationInvalidUserAuthToken" will be failed because PRINTER_PANEL_UI is false that scripts will not prompt user to click OK button on control panel.
Can you help check to see if google can change the scripts or we can click the OK button while run this test?
Thanks,
Andy

Hi Andy,
I have pushed up a change that should address your issue. https://github.com/google/cloudprint_logocert/commit/c199006ea578c81e4bb88ecd1e2e73bfe0b817a6
Please pull from master, keep the 'PRINTER_PANEL_UI' flag as true, and run both of the tests you mentioned. Let me know if that works for you.
Thanks,
Kevin

Hi Kevin,
Thanks for making change on the scripts. it works now.
Andy


Support classic citation format

First of all, thank you for providing the academic template. I enjoy it very much.
Would it be possible to add an option to choose a more traditional citation style for the publication list? Moreover, would it be possible to make the filter of the publication list optional?

Support for a more classic style of citation has been added. Feel free to update your theme and let me know your feedback.
Note there is a breaking change: default_list parameter has become list_format, which has the following acceptable values:
0 = Simple
1 = Classic
2 = Detailed
E.g. set list_format = 0 in the publication widgets and in /publication/_index.md for all listings to be formatted in a classic style.

Excellent, I love it! Thanks for this great update. I have a couple of additions to the wish list, namely new fields:

volume: as typically the journal volume
pages: as the page range
year: as the year of the publication. Note that given the potential discrepancy between the date of (on-line) publication and the actual 'year' of publication (which is the additional time before it makes it to a journal issue), the classic style should use year for the citation (and potentially, but arguably, for the sorting too), and maybe add [first published on-line: 'date'].

Thanks!


[Tables] Remove await_prepared_test from asynctestcase.py

This functionality is deprecated
https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/tables/azure-data-tables/tests/_shared/asynctestcase.py#L32-L43

Hey @seankane-msft ; took care of this one too
Ran the tox tests:

Here is the PR: https://github.com/Azure/azure-sdk-for-python/pull/14444


Feature Request: Start/stop recording + Take Photo

Is your feature request related to a problem? Please describe.
My feature request is related to the fact that I need to use the TAPO APP in order to start/stop a recording or take a photo
Describe the solution you'd like
I'd like to see some services or entities that allows me to

start/stop a recording to the SD card
take a photo to the SD card

Describe alternatives you've considered
N/A
Additional context
N/A

Duplicate of https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/issues/40

Recording to SD card is manage to by camera itself. There is no way how to manually start or stop recording via api


Run tests in nix build

See discussion in https://github.com/benwis/benwis_leptos/issues/2

Meanwhile, we have to run cargo leptos test in the dev shell.


"return" or implied return at end of anonymous sub in a BEGIN block generates incorrect code

"return" or implied return at end of anonymous sub in a BEGIN block generates incorrect code.  E.g.
BEGIN {
    *G = sub { 1 };
}

generates a "break" instead of a "return".

Fixed in v0.968


Cannot reload or quit VSCode after debugging extension on macOS

VSCode Version: 1.47.2, 1.48.0-insider
OS Version: macOS 10.15.6

Steps to Reproduce:

Start debugging https://github.com/REditorSupport/vscode-r-lsp
Quit the extension host window
Quit or reload the extension editor window nothing happens. I could only quit VSCode by force quit.

Following is a screencast to demonstrate the issue:

Does this issue occur when all extensions are disabled?: Yes

Cannot reproduce with 1.47.2 on macOS 10.15.6:

Does the problem also happen if you launch with all extensions disabled?

Yes, it still happens if I launch with all extensions disabled.
I also tried only open the vscode-r-lsp project without open any files, and launch the debugger without open any files in the extension host, but unluckily it still occurs.
I tried with debugging another extension but everything works well.
Something must happen in background for this specific project I work with.

As long As I cannot reproduce the issue, I'll not be able to investigate...

I also tried with 1.48.0-insider and the behavior is exactly the same.
Is there any logging output I could put here to help?

In the latest release, this problem no longer exists. Closing now.


Add retries to delivery attempts.

Codecov Report

Merging #75 into master will increase coverage by 2.65%.
The diff coverage is 85.24%.

@@            Coverage Diff             @@
##           master      #75      +/-   ##
==========================================
+ Coverage   67.76%   70.41%   +2.65%
==========================================
  Files           6        7       +1
  Lines         639      676      +37
==========================================
+ Hits          433      476      +43
  Misses        188      188
+ Partials       18       12       -6

Impacted Files
Coverage Δ

src/caduceus/caduceus.go
5.88% <0%> (-0.08%)
:arrow_down:

src/caduceus/simpleCounter.go
100% <100%> (ø)

src/caduceus/senderWrapper.go
90.59% <100%> (+0.16%)
:arrow_up:

src/caduceus/metrics.go
100% <100%> (ø)
:arrow_up:

src/caduceus/outboundSender.go
87.28% <82.5%> (+4.01%)
:arrow_up:

Continue to review full report at Codecov.

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


Package request: gh-copilot

Project description

Metadata

homepage URL: https://github.com/github/gh-copilot
source URL: https://github.com/github/gh-copilot
license: Not sure
platforms: macOS - not sure about others

Add a :+1: reaction to issues you find important.

Don't know if you get a notification, but I created a PR for this request - #297073.


Fix GetDataLimits when AxisLine or AxisSpan is present

Fixes #1415 #1505

Looks great, thanks @EFeru!


Failed to configure a cmake project under drive root

Brief Issue Summary
CMakeLists.txt
cmake_minimum_required(VERSION 3.30)
project(tmp)
file(TOUCH tmp.cpp)
add_library(tmp tmp.cpp)

Put the CMakeLists.txt under drive root, e.g. D:, (or any folder and then subst), then open drive root with vscode.
CMake Tools Diagnostics
{
  "os": "win32",
  "vscodeVersion": "1.92.1",
  "cmtVersion": "1.18.44",
  "configurations": [
    {
      "folder": "d:\\",
      "cmakeVersion": "3.30.2",
      "configured": true,
      "generator": "Ninja",
      "usesPresets": false,
      "compilers": {
        "C": "C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.40.33807/bin/Hostx64/x64/cl.exe",
        "CXX": "C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.40.33807/bin/Hostx64/x64/cl.exe"
      }
    }
  ],
  "cpptoolsIntegration": {
    "isReady": true,
    "hasCodeModel": true,
    "activeBuildType": "Debug",
    "buildTypesSeen": [
      "Debug"
    ],
    "requests": [
      "file:///d%3A/hello.cpp"
    ],
    "responses": [],
    "partialMatches": [],
    "targetCount": 1,
    "executablesCount": 1,
    "librariesCount": 0,
    "targets": [
      {
        "name": "tmp",
        "type": "EXECUTABLE"
      }
    ]
  },
  "settings": [
    {
      "communicationMode": "automatic",
      "useCMakePresets": "auto",
      "configureOnOpen": false
    }
  ]
}

Debug Log
[proc] : "C:\Program Files\CMake\bin\cmake.EXE" -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE --no-warn-unused-cli -SD:. -Bd:/build -G Ninja
[cmake] Not searching for unused variables given on the command line.
[cmake] -- The C compiler identification is MSVC 19.40.33813.0
[cmake] -- The CXX compiler identification is MSVC 19.40.33813.0
[cmake] -- Detecting C compiler ABI info
[cmake] -- Detecting C compiler ABI info - done
[cmake] -- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.40.33807/bin/Hostx64/x64/cl.exe - skipped
[cmake] -- Detecting C compile features
[cmake] -- Detecting C compile features - done
[cmake] -- Detecting CXX compiler ABI info
[cmake] -- Detecting CXX compiler ABI info - done
[cmake] -- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Enterprise/VC/Tools/MSVC/14.40.33807/bin/Hostx64/x64/cl.exe - skipped
[cmake] -- Detecting CXX compile features
[cmake] -- Detecting CXX compile features - done
[cmake] -- Configuring done (1.3s)
[cmake] CMake Error at CMakeLists.txt:4 (add_library):
[cmake]   Cannot find source file:
[cmake]
[cmake]     tmp.cpp
[cmake]
[cmake]
[cmake] CMake Error at CMakeLists.txt:4 (add_library):
[cmake]   No SOURCES given to target: tmp
[cmake]
[cmake]
[cmake] CMake Generate step failed.  Build files cannot be regenerated correctly.

Additional Information
I suspect the option -SD:. passed to cmake is the cause.

The issue you're encountering with CMake appears to be related to the file(TOUCH tmp.cpp) command in your CMakeLists.txt. The file(TOUCH tmp.cpp) command creates an empty file tmp.cpp but doesn't ensure it is correctly handled by CMake, especially if the file isn't present at the time of configuration. Here are steps to resolve the problem:

Create the Source File Manually: Ensure that tmp.cpp exists in the directory where CMake expects it. You can manually create tmp.cpp with some placeholder content, such as:
// tmp.cpp
int main() {
    return 0;
}

Modify CMakeLists.txt: To make your CMakeLists.txt more robust, you might want to specify tmp.cpp directly in the file command or use file(WRITE ...) to ensure the file content is initialized properly. For example:
cmake_minimum_required(VERSION 3.30)
project(tmp)

# Ensure tmp.cpp exists with some content
file(WRITE ${CMAKE_BINARY_DIR}/tmp.cpp "int main() { return 0; }")

# Add the library
add_library(tmp ${CMAKE_BINARY_DIR}/tmp.cpp)

Note that ${CMAKE_BINARY_DIR} is used to ensure the file is created in the build directory.

Verify Paths: Ensure that paths are correctly specified. The error might also be due to an issue with where CMake is looking for tmp.cpp. Ensure that tmp.cpp is present in the expected location relative to the CMakeLists.txt.

Re-run CMake: After making these changes, delete the existing build directory or any existing configuration files, and then re-run CMake:
cmake -DCMAKE_BUILD_TYPE=Debug -G Ninja ..

Check CMake Presets: If you're using CMake presets, ensure that the preset configuration matches the setup you intend to use. For instance, if using presets, you might need to adjust settings or paths in your CMakePresets.json file.

By ensuring tmp.cpp is present and correctly referenced in CMakeLists.txt, you should be able to resolve the issues you're facing.

Reported upstream https://gitlab.kitware.com/cmake/cmake/-/issues/26222.

@huangqinjin, thanks for reporting this issue. Today we verified this issue with the CMakeLists.txt you mentioned, but we didn't repro it. Please see the below video. Could you please verify this issue using CMake high version such as 3.29 to verify this issue again? If it doesn't repro, then it could be considered a problem with a specific version of CMake. you could you continue to follow your issue Reported upstream https://gitlab.kitware.com/cmake/cmake/-/issues/26222. Thanks.
ENV:
VS Code:1.92.2
CMake Tools: v1.18.44
CMake from in VS: 3.29.5-msvc4

@Evelyn-001 you are configuring the project from command line, nothing related to cmake-tools, please check the upstream issue.
To reproduce my issue reported here (cmake-tools), please simply click the Build button at the bottom status bar.

@huangqinjin, Thanks for your reply. We have reproduced this issue with below ENV. Our development team will investigate this issue later and we will provide you with any updates. Thank you for your support.
Env:
VS code: 1.92.2
CMake Tool: v1.18.44


Hearing ads on top of youtube video

Script version
Version 5.5
Describe the bug
When I play a video, I hear an ad but the video is also playing. I do not see the ad, but both sounds play at the same time. The issue sometimes resolves itself if I refresh the page once or twice.
Desktop (please complete the following information):
Brave: Version 1.66.118 Chromium: 125.0.6422.147 (Official Build) (64-bit)]
OS: Windows 10 Pro, 19045.4412, just updated

Same here

it's also showing on some channels that all of the content is not viewable

Me to, it's double the video in 1 tap, the one on top is free ads and good but there's another video, same video on the back somewhere that the ads is not blocked, and some video is black screen and only audio....

same

same
solution i found (for Chrome)  is to pause the video in the audio tab icon on the top right, which will stop the video in the youtube player also, then hit play again in the youtube player.

Same...last update was good where ads are sped up instead of blocking them..in this update i am getting tha video but ad is also playing in the background..which is kinda annoying

same

this fixed it for me https://github.com/TheRealJoelmatic/RemoveAdblockThing/issues/544#issuecomment-2156076563


[Flaky Test] Fix Flaky Test SearchTimeoutIT.testSimpleTimeout

Description
When numDocs=1000:

The testSimpleTimeout will cost several  minutes, when scoring each doc, it will cost 500ms, it's a long time to iterating all the doc in queryphase.
https://github.com/opensearch-project/OpenSearch/blob/5aa65096ff3ca3aec8eb563a8ac52c5e42bf5009/server/src/internalClusterTest/java/org/opensearch/search/SearchTimeoutIT.java#L138
ReaderContext is created before executing queryphase and released after the fetchphase.
the life time of ReaderContext is 1min(determined by search.keep_alive_interval)
If queryPhase costs too much time, the ReaderContext may be released before fetchphase, so the fetch/Id will be failed, which hit the case.

Related Issues
Resolves #16056 #9401

Check List

[x] Functionality includes testing.
[ ] API changes companion pull request created, if applicable.
[x] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

❌ Gradle check result for d1fc8be: FAILURE
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

SpecificClusterManagerNodesIT.testElectOnlyBetweenClusterManagerNodes #15944

@reta @jed326, please have a look when you are free.

@reta @jed326, please have a look when you are free.

Thanks @kkewwei , I am actually a bit surprised by your findings

If queryPhase costs too much time, the ReaderContext may be released before fetchphase, so the fetch/Id will be failed, which hit the case.

The query phase has to be terminated early by timeout, right? So it should be not much longer then timeout itself?

timeout

timeout

❕ Gradle check result for d1fc8be: UNSTABLE
Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

Yes, the query phase has to be terminated early by timeout, but the fetch phase is not affected by the timeout. timeout is checked every bulk docs, In case the size of bulk docs exceeds 120, the query phase will consume more than 1min.

@reta Yes, the query phase has to be terminated early by timeout, but it may be much longer than timeout. timeout is checked every bulk docs(scoreRange, initial_interval=1024), In case the size of bulk docs exceeds 120, the query phase will consume more than 1min.

Thanks @kkewwei , I think this is the problem, not the test, right? If timeout does not early terminate the query within reasonable time margin, it is not very useful.

right

@reta Yes, the query phase has to be terminated early by timeout, but it may be much longer than timeout. timeout is checked every bulk docs(scoreRange, initial_interval=1024), In case the size of bulk docs exceeds 120, the query phase will consume more than 1min.

Thanks @kkewwei , I think this is the problem, not the test, right? If timeout does not early terminate the query within reasonable time margin, it is not very useful.

@reta  timeout is a  shard-level setting,  there exists a possibility where the actual timeout could be several times of the timeout, I tried to use cancel_after_time_interval instead of timeout (maybe not suitable) #11642.
To avoid excessive timeouts, maybe we should decrease the upper interval(100m), such as 100k?

@reta timeout is a shard-level setting, there exists a possibility where the actual timeout could be several times of the timeout, I tried to use cancel_after_time_interval instead of timeout (maybe not suitable) #11642.

@kkewwei thanks for staying with me, timeout is search request based setting (which we pass to shards), the intuition regarding the timeout (at least the one I built out of documentation https://www.elastic.co/guide/en/elasticsearch/reference/current/search-your-data.html#search-timeout) is that each shard has to respect the timeout (more or less), it is fine to be not precise but the search request with timeout of 5ms should not take 1m to complete for this specific test.
I only briefly looked at overall implementation and it looks like we may lost some timeout handling guarantees, likely while implementing the concurrent search. Do you mind if I push some changes into your pull request? Thank you.

@reta timeout is a shard-level setting, there exists a possibility where the actual timeout could be several times of the timeout, I tried to use cancel_after_time_interval instead of timeout (maybe not suitable) #11642.

@kkewwei thanks for staying with me, timeout is search request based setting (which we pass to shards), the intuition regarding the timeout (at least the one I built out of documentation https://www.elastic.co/guide/en/elasticsearch/reference/current/search-your-data.html#search-timeout) is that each shard has to respect the timeout (more or less), it is fine to be not precise but the search request with timeout of 5ms should not take 1m to complete for this specific test.
I only briefly looked at overall implementation and it looks like we may lost some timeout handling guarantees, likely while implementing the concurrent search. ~Do you mind if I push some changes into your pull request?~ Thank you.
Opened up #16882

@reta  Of course, please free free to go ahead.

@reta, it seems #16882  can't solve the flay test. Short-circuiting only accelerates the response time of the shard, if first searchLeaf call costs 1min(for example, 150 docs, each wait time is 500ms), it will also continue hit the case.

@reta, it seems #16882 can't completely solve the flay test.

You are absolutely correct @kkewwei , we only check for timeouts in some places, but in general - we could not preemptively abort the process. Thanks!


Remove rollout call for quality stats

Now that this feature is enabled for all repos, we can remove the check

/cc @codeclimate/review

:+1:


[Feature Request] Show additional trade info

I would appreciate if the plugin would display additional info about the trade in the log, such as:

Name of the items
Name (steamid64) of the trader
Trade message if given by the trader

It will make asf behavior inconsistent, since you will get this info only for trades handled by plugin, but not for trades handled by ASF itself. Unsure if I want to implement it this way.

Why not leave it as an additional setting that can be toggled manually. That way people wanting a consistent behavior won't be bothered by it

I guess I will decline this feature request after all. Additional logging for trades should be done within ASF itself, or as a separate plugin (but the latter will require changes on ASF side anyway, since for now ASF does not return all required data for accepted trades).

Gotcha, thanks anyway. If logging will be done through another plugin, is there any way for that plugin to check wether it was your plugin that accepted the trade?

I don't think so


Legacy rebased

All those old changes...

This was split into:

https://github.com/paritytech/sccache/pull/64 (merged)
https://github.com/paritytech/sccache/pull/65 (merged)
https://github.com/paritytech/sccache/pull/66 (pending review)
https://github.com/paritytech/sccache/pull/67 (pending review)

and I skipped some minor things like extraneous clippy::... annotations, fs::metadata reshufflings in tests or reverting changes that were done upstream in the meantime (e.g. reintroducing ServerNonce::from_rng)
When the last aforementioned PRs are merged, I'd say we can safely close this and remove the branch.

I'd like to keep the test assert cleanup, the rest can happily bite the dust - the whole clippy lint topic should be dealt with in a separate PR.

I'd also wait until the PRs are merged and see what effective delta is left, so we can then start new PRs based on those hints

I created a delta between what'll be merged with those 4 PRs and what was left in legacy-rebased: https://commie.io/#5Jpe4qwN. Each change contains a rationale behind it.

I'd like to keep the test assert cleanup (...)

I can submit a PR reintroducing it if you feel strongly about it, but here are some of my thoughts (note more or less copied from the linked delta) and the change discussed:
         // Ensure that the object file was created.
-        assert!(0 < fs::metadata(&obj).unwrap().len());
+        assert!(fs::metadata(&obj).map(|m| m.len() > 0).unwrap());

I really don't think it pulls its weight at the cost of increasing divergence and growing the diff between forks. It's basically unwrapping first, rather than mapping the value undearneath, coupled with reverse, almost C/C++ yoda-style comparison.
If we want to increase legiblility/benefit, we should either

switch around the sides of the comparison to read more naturally or
somehow assert that fs::metadata(&obj).map(|m| m.len()) matches Ok(1..) or Ok(val) if val > 0 to get more info reported by the macro in case we encounter an Err
(optionally coupled with assert_ne! in both of the cases)

Until then, it just feels like switching around without any benefit (at least it makes it harder for me to read) while costing us a maintenance effort to keep this difference between the forks.
Let me know if I'm too much in the weeds on this one; I'd happily just skip the change altogether.

I agree, the current change is insignificant and assert_matches!(fs::meta(), Ok(1..)) is a way prettier approach anyways!

Alright, this is done then :wave:


Add dashboard via Docker to display scan results

I'm doing some test runs with https://github.com/smiegles/subdomainDB to see if i can port it to local network with Nginx

https://github.com/x1mdev/ReconPi/tree/dev/dashboard this is the branch that I have been testing it on
https://github.com/x1mdev/ReconPi/commit/34c7631c4c7c452ee9e3af597df578a1f78f990e

Also, something weird is up with the color in [+] : install.sh
Color not added, just the var name

Added the dashboard and nginx config, working now. https://github.com/x1mdev/ReconPi/commit/96e7824b00dd3d9541dbf3efcd3b6a69be183c82
Also fixed the color issue: https://github.com/x1mdev/ReconPi/commit/45e8e24e32bb2235f300ec41ddc1d15436fb2594


Document Library Bug

On my Tenant I have a site collection with a document library and inside it I have folders.
I am developing a script to remove automatically folders from document libraries and when I am doing my tests I get a bug in folders.
If I'm inside a folder and I delete it using Powershell, in my case I'm using PNP (Remove-PnPFolder) commands, my page changes to a photo like this one.

The problem is that the image changes constantly, simultaneously with others and never stops. It is an infinitive loop.
To test this create a document library in Sharepoint Online and inside it create a folder. Then go into the folder. Now using powershell, run the following command "Remove-PnPFolder" and delete your folder. If you look to the browser again you are still inside the folder, but you got an image error always popping.

@dudax97 thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.
@officedocsbot close

@officedocsbot close


Only top bar is visible when keyboard is visible on Landscape mode on mobile.

Bug report
When trying to use keyboard with Text Field on the wolt page in Landscape mode in mobile, Only top bar is visible and the main content can't be accessed. As We can't see the text field or scroll in the main content.
Expected behavior
We need to have option to hide the top bar so we can hide it when the keyboard is visible.
Maybe when the leadingNavBarWidget, trailingNavBarWidget, topBar and topBarTitle are all null we can hide the toolbar
Also it would be nice to customize the top bar padding.
Here is a screenshots of the issue.

@basemosama You can actually do this behavior.

Use flutter_keyboard_visibility package to listen to the keyboard visibility changes
Utilize the decorator field for state management so that when the keyboard is visible, mark the decorator as dirty, let the page rebuild.
set hasTopBar field to false.

decorator -> ChangeNotifierProvider(create => Your provider) (Example here)
pageListBuilder(context) {
    final isKeyboardVisible = contex.watch<YourProvider>().isKeyboardVisible;
    return [
        WoltModalSheetPage(
            hasTopBarLayer: !isKeyboardVisible;
       );
    ]
}

================
Alternative way, easier way:

Use flutter_keyboard_visibility package to listen to the keyboard visibility changes.
Create your custom top bar and provide it to the WoltModalSheet
Wrap your topbar with KeyboardVisibilityBuilder

WoltModalSheetPage(
    topBar: KeyboardVisibilityBuilder(
        builder: (context, isKeyboardVisible) {
          return isKeyboardVisible ? SizedBox.shrink() : MyCustomTopBar();
        }
    ),
)

For the first solution unfortunately I am currently using getx as state management not provider so I can, t use the concept of context.watch for keyboard visibility.
For the second one I think it's the better solution but there's only one problem:
Even when returning Sizedbox.shrink for top bar the top bar overlay is still visible. I can only hide the top bar overlay when passing hasTopLayer:false
Here is a screenshot of how it looks

@basemosama What if you set isTopBarLayerAlwaysVisible to true when using keyboard visibility builder?
WoltModalSheetPage(
    isTopBarLayerAlwaysVisible: true,
    topBar: KeyboardVisibilityBuilder(
        builder: (context, isKeyboardVisible) {
          return isKeyboardVisible ? SizedBox.shrink() : MyCustomTopBar();
        }
    ),
)

Still the same To hide the top layer i have to change hasTopLayer:false and not pass any widget for top bar


App Config Spring - Fix Normalize Null usage

Fixed Issues where empty label FF wouldn't trigger refreshes when value changed

API change check
API changes are not detected in this pull request.