Background color

How to change the background color of the site?

Open css/custom.css
Change this
body {
  padding-top: 56px;
}

Make it look like this
body {
  padding-top: 56px;
  background-color: #YOUR-COLOR-CODE-HERE;
}

You can find lots of color codes here:
https://www.w3schools.com/cssref/css_colors.asp

How to change the background color of the site?

Open css/custom.css
Change this
body {
  padding-top: 56px;
}

Make it look like this
body {
  padding-top: 56px;
  background-color: #YOUR-COLOR-CODE-HERE;
}

You can find lots of color codes here:
https://www.w3schools.com/cssref/css_colors.asp

It does not work, the background remains white

It does not work, the background remains white

Try to do a CTRL + F5 in your browser. The Browser might be caching the CSS from before.
If that doesen't work. Can you paste the output of the custom.css?


[Docs] All links under Developer guide are broken

If it's [1] still under WIP please ignore.
[1] https://is.docs.wso2.com/en/5.9.0/using-wso2-identity-server/developer-Guide/

The links on the menu bar are working, just not under the "developer guide" page

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Embedding struct?

Hello!
Input: (PostgreSQL)
-- name: PreFetchContentsByGroup :many
SELECT c.*, array_agg(g.id)::INT[] AS Ids
FROM contents c
         INNER JOIN content_group_links cgl ON c.id = cgl.content_id
         INNER JOIN groups g ON cgl.group_id = g.id
WHERE g.id = ANY ($1::INT[])
GROUP BY c.id;

const preFetchContentsByGroup = `-- name: PreFetchContentsByGroup :many
SELECT c.id, c.name, c.type, c.file, c.category, c.description, c.priority, c.enable, c.sys_1, c.sys_2, c.text_field_1, c.text_field_2, c.text_field_3, c.text_field_4, c.name_i18n, c.protected, c.uidx, c.name_i, c.description_i, c.text_field_1_i, c.text_field_2_i, c.text_field_3_i, c.text_field_4_i, c.file_i, array_agg(g.id)::INT[] AS Ids
FROM contents c
         INNER JOIN content_group_links cgl ON c.id = cgl.content_id
         INNER JOIN groups g ON cgl.group_id = g.id
WHERE g.id = ANY ($1::INT[])
GROUP BY c.id
`

Output:
type PreFetchContentsByGroupRow struct {
	ID           int32
	Name         sql.NullString
	Type         string
	File         uuid.UUID
	Category     sql.NullInt32
	Description  sql.NullString
	Priority     int16
	Enable       bool
	Sys1         sql.NullString
	Sys2         sql.NullString
	TextField1   sql.NullString
	TextField2   sql.NullString
	TextField3   sql.NullString
	TextField4   sql.NullString
	NameI18n     sql.NullInt32
	Protected    bool
	Uidx         uuid.UUID
	NameI        sql.NullString
	DescriptionI sql.NullString
	TextField1I  sql.NullString
	TextField2I  sql.NullString
	TextField3I  sql.NullString
	TextField4I  sql.NullString
	FileI        sql.NullString
	Ids          []int32
}

Is it possible to do so ...
type PreFetchContentsByGroupRow struct {
	Content
	Ids          []int32
}

Can this be?

Thank you for the feature request. I agree that the PreFetchContentsByGroupRow generated struct isn't very useful for this given query. However, right now I don't have any plans on returning nested structures from queries.
If it is added in the future, it will probably work as you've outlined. c.* expressions would be scanned into separate structs on the return row.
For others reading this issue, feel free to post your own queries that could be helped by embedding structs in the return result (or just hit the 👍 button)

Here's a proposed spec for modified star expansion in generated Go code to satisfy this feature request:
Stating this as three simple rules:

If the only returned value of a query is table_name.* then there is no behavior change.
Otherwise, each occurrence of table_name.* is expanded to its model struct in the result row struct.
As a special case, * now expands to table_1.*, table_2.*, table_3.* for each table in the query

Here are a set of examples illustrating the proposed behavior changes:

SELECT * FROM table_a -> remains unchanged
SELECT table_a.* FROM table_a -> remains unchanged
SELECT table_a.*, LENGTH(table_a.foo) FROM table_a -> now outputs a row struct with an embedded model for table_a as well as any other columns selected:

type Row struct {
  TableA TableA
  Col_2  int
}

SELECT table_a.*, table_b.foo FROM table_a, table_b -> this functions like the previous example outputting a row struct of:

type Row struct {
  TableA TableA
  Foo    int
}

SELECT table_a.*, table_b.* FROM table_a, table_b -> now outputs a row struct with embedded  models for both table_a and table_b:

type Row struct {
  TableA TableA
  TableB TableB
}

SELECT * FROM table_a, table_b -> this is equivalent to the previous example. the * is expanded to table_a.*, table_b.*:

type Row struct {
  TableA TableA
  TableB TableB
}

Thanks for writing up a spec. I want to have an agreed upon design before any code is written.
As designed, this is a breaking change. The final spec should be opt-in, either in the configuration file or on a per-query basis.
This proposal doesn't play well with CTEs and other nested queries. Given this query:
WITH foobar as (
    SELECT foo.*, bar.* FROM foo, bar
), subquery as (
    SELECT foobar.*, foobar.* FROM foobar
)
SELECT subquery.* FROM subquery

would we expect the output to be?
type Foobar struct {
  Foo Foo
  Bar Bar
}

type Subquery struct {
  Foobar Foobar
  Foobar_1 Foobar
}

type Row struct {
  Subquery Subquery
}

My proposal is that we introduce a sqlc function that explicitly signals that a star expansion should be embedded.
-- name: FooLength :many
SELECT sqlc.embed(foo.*), LENGTH(foo.bar) as bar_len FROM foo;
-- name: FooBaz :many
SELECT sqlc.embed(foo.*), bar.baz FROM foo, bar;
-- name: FooBar :many
SELECT sqlc.embed(foo.*), sqlc.embed(bar.*) FROM foo, bar;

// FooLength return value
type Row struct {
  Foo Foo
  BarLen int32
}

// FooBaz return value
type Row struct {
  Foo Foo
  Baz int
}

// FooBar return value
type Row struct {
  Foo Foo
  Bar Bar
}

Note that in this proposal, the behavior for  SELECT * FROM foo, bar; would not change.
In the future, I'd like to support the same feature using composite types, which is part of the SQL standard. Sadly, the lib/pq driver and database/sql packages don't support composite types because they don't use the binary protocol for PostgreSQL. It's possible that we should wait on implementing this feature and instead focus on adding support for pgx. With composite type support, the queries would be much cleaner:
-- name: FooLength :many
SELECT foo, LENGTH(foo.bar) as bar_len FROM foo;
-- name: FooBaz :many
SELECT foo, bar.baz FROM foo, bar;
-- name: FooBar :many
SELECT foo, bar FROM foo, bar;

Let me play around with pgx composite type support.

Just to follow up here we've run into another situation where this would be beneficial. It's a standard many-to-many relationship where we want to pull out a list of objects and all of objects that they're related to via a join table. Given sqlc's examples, it's basically this query:
SELECT author.*, book.* FROM author
JOIN author_to_books
JOIN books
WHERE author.first_name = 'John'

Instead of doing this the way we'd like we're going to do an application level join instead (select all the books, select all the authors, stitch them together in memory).
Re your questions:

This proposal doesn't play well with CTEs and other nested queries. Given this query:
would we expect the output to be?

I'd expect more complex query constructions like CTEs to continue with their existing output behavior (all rows combined) until there's time/demand to add the additional smarts to the codegen to propagate typing through where possible.
Looking at this a second time, I think these might be orthogonal concerns. Does your sqlc.embed() proposal solve that problem with your nested CTE example? e.g. if I embed sqlc.embed() into a CTE nested a few CTEs deep, will it be any less hard to propagate that marker through the AST? I'm definitely not expert enough here to understand the implementation nuances, but it appears like these might be two unrelated problems:

Should star expansion yield typed table definitions in the codegen be explicit (sqlc.embed or implicit?)
Implementing sql table -> output type mapping choice propagation through nested CTEs or subqueries


Fix Deterministic blending with Dominant/Recessive doesn't have initial value even if there is no Discrete track

Follow up #89389. Fixes https://github.com/godotengine/godot/issues/92127.
I listed the behaviors, some of which were problematic:

Deterministic
RESET Track
CallbackModeDiscrete
Is init value appeared in animation with lacking some tracks

true
None (but there is track in another animation)
Dominant
No, init value may be discrete

true
None (but there is track in another animation)
Recessive
No, init value may be discrete

Indeed, the Reset track can be Discrete, but if there is no Discrete track in the other animations, it should be considered Continuous. This causes problems in Deterministic blending, where the results may be inconsistent as https://github.com/godotengine/godot/issues/92127.
With this PR, the Dominant/Recessive mode will first check for the presence of a Reset track, and if there is none, it will check for the presence of blended Discrete track. So the list will be:

Deterministic
RESET Track
CallbackModeDiscrete
Is init value appeared in animation with lacking some tracks

true
None (but there is track in another animation)
Dominant
Yes, if "there is no other discrete track blended" and "continuous track is blended or blend amount is zero" / But not so, it is No since discrete value should be take precedence

true
None (but there is track in another animation)
Recessive
Yes, if "there is no other discrete track blended" and "continuous track is blended or blend amount is zero" / But not so, it is No since discrete value should be take precedence

I was organizing the documentation on Discrete mode, and since the https://github.com/godotengine/godot/pull/89389 was invading the role of the Deterministic option and generating confusion, I have reorganized the behavior.
This causes #89163 to recur, but that is the intended specification. It needs to be controlled by the Deterministic option.

Adding the is_init flag used by A and B instead of init_use_continuous solves this.
I remember conversing with reduz a bit about this at the beginning of 4.0, but the problem with https://github.com/godotengine/godot/issues/92127 in the first place is that the reset animation does not play when the blend amount is 0.
The workaround is to either apply the reset animation even if the blend amount is 0, or to use a flag to apply the reset animation only once. This PR will use the former for Force Continuous and the latter for Dominant and Recessive. This will make the Dominant mode reset occur only once, so the problem in #89163 should not recur.

Now I make Recessive the default due to reevaluating the overall behavior.
In the past, we changed it once in #88492 because there was a problem with the Reset track taking precedence, but this should not be a problem now, and Recessive should be a better default because it does not have the flicker that can occur with Dominant, and it gives the same results as 3.x.
In there is 2 animations:
https://github.com/godotengine/godot/assets/61938263/a967ece8-9d2c-46c6-9d9d-f4178f400889
https://github.com/godotengine/godot/assets/61938263/71d11caf-0c92-44d8-a9cb-b94f3c5cdee0
Force Continuous:
https://github.com/godotengine/godot/assets/61938263/9bcb86b2-d688-45b6-9755-db5cb5119b12
Dominant:
https://github.com/godotengine/godot/assets/61938263/83d4a9b7-0b74-43c9-867e-3a401ef7576f
Recessive:
https://github.com/godotengine/godot/assets/61938263/846adf88-e43c-41c5-acd7-45568611dcdd

I would like to include this in beta1 as this changes the default value.

Thanks!


Bluetooth: CAP: Add size and rank checks for CAS register

For the CAP acceptor the size and rank characteristic shall be set as per the CAP spec. Add checks for 0, as 0 indicates not initializing the characteristics in the CSIS instance.
Fixes https://github.com/zephyrproject-rtos/zephyr/issues/55456

@Thalley the linked issue is marked as an enhancement, not a bug, however this very much looks like a bug fix to me. Could you change that? Enhancement PRs are not really appropriate anymore at this late stage of release stabilisation.

@Thalley the linked issue is marked as an enhancement, not a bug, however this very much looks like a bug fix to me. Could you change that? Enhancement PRs are not really appropriate anymore at this late stage of release stabilisation.

I am fine with keeping this an enhancement, as it just adds simple API checks (that can even be disabled), and in the end it is the application's responsibility to be spec compliant.


Enable automerge 22.12 to 23.02 [skip ci]

Signed-off-by: Peixin Li<EMAIL_ADDRESS>Automerge from branch-22.12 to branch-23.02

build


Gracefully handle non-existent env

Fix https://github.com/TheSnakePit/mamba/issues/346

Thanks! By the way, conda has the same deficiency, so if you were interested you could also contribute this fix to conda :)


Packaging: register as a project on PyPI

Register on PyPI so that package can be installed via pip install.

If I understand it right, we need to either consolidate the system dependent make commands into the setup.py or provide pre-compiled executables in order to do this.


[Release][Ruby] Investigate why we require to install libffi manually on a new M2 to run verification

Describe the bug, including details regarding any error messages, version, and platform.
As discussed here:
https://github.com/apache/arrow/pull/39960#discussion_r1491520898
I did require to add:
   # libffi required for gobject-introspection gem
   brew install libffi

In order to run verification successfully on a new macOS ARM (M2). Otherwise we got the following error:
Resolving dependencies...
Fetching power_assert 2.0.3
Fetching native-package-installer 1.1.9
Fetching pkg-config 1.5.6
Installing power_assert 2.0.3
Installing native-package-installer 1.1.9
Installing pkg-config 1.5.6
Fetching test-unit 3.6.2
Fetching glib2 4.2.0
Installing test-unit 3.6.2
Installing glib2 4.2.0 with native extensions
Fetching gobject-introspection 4.2.0
Installing gobject-introspection 4.2.0 with native extensions
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

current directory:
/private/var/folders/rr/t_15q7dx4_lf1nv0btypffcw0000gn/T/arrow-15.0.0.XXXXX.li0gqOMB3O/apache-arrow-15.0.0/c_glib/vendor/bundle/ruby/3.3.0/gems/gobject-introspection-4.2.0/ext/gobject-introspection
/opt/homebrew/opt/ruby/bin/ruby extconf.rb
checking for --enable-debug-build option... no
checking for -Wall option to compiler... yes
checking for -Wcast-align option to compiler... yes
checking for -Wextra option to compiler... yes
checking for -Wformat=2 option to compiler... yes
checking for -Winit-self option to compiler... yes
checking for -Wlarger-than-65500 option to compiler... yes
checking for -Wmissing-declarations option to compiler... yes
checking for -Wmissing-format-attribute option to compiler... yes
checking for -Wmissing-include-dirs option to compiler... yes
checking for -Wmissing-noreturn option to compiler... yes
checking for -Wmissing-prototypes option to compiler... yes
checking for -Wnested-externs option to compiler... yes
checking for -Wold-style-definition option to compiler... yes
checking for -Wpacked option to compiler... yes
checking for -Wp,-D_FORTIFY_SOURCE=2 option to compiler... yes
checking for -Wpointer-arith option to compiler... yes
checking for -Wundef option to compiler... yes
checking for -Wout-of-line-declaration option to compiler... yes
checking for -Wunsafe-loop-optimizations option to compiler... no
checking for -Wwrite-strings option to compiler... yes
checking for Homebrew... yes
checking for gobject-introspection-1.0... yes (1.78.1)
creating rbgiversion.h
creating gobject-introspection-enum-types.c
creating gobject-introspection-enum-types.h
creating ruby-gobject-introspection.pc
creating Makefile

current directory:
/private/var/folders/rr/t_15q7dx4_lf1nv0btypffcw0000gn/T/arrow-15.0.0.XXXXX.li0gqOMB3O/apache-arrow-15.0.0/c_glib/vendor/bundle/ruby/3.3.0/gems/gobject-introspection-4.2.0/ext/gobject-introspection
make DESTDIR\= sitearchdir\=./.gem.20240216-45788-684atu sitelibdir\=./.gem.20240216-45788-684atu clean

current directory:
/private/var/folders/rr/t_15q7dx4_lf1nv0btypffcw0000gn/T/arrow-15.0.0.XXXXX.li0gqOMB3O/apache-arrow-15.0.0/c_glib/vendor/bundle/ruby/3.3.0/gems/gobject-introspection-4.2.0/ext/gobject-introspection
make DESTDIR\= sitearchdir\=./.gem.20240216-45788-684atu sitelibdir\=./.gem.20240216-45788-684atu
compiling gobject-introspection-enum-types.c
compiling rb-gi-arg-info.c
In file included from rb-gi-arg-info.c:21:
In file included from ./rb-gi-private.h:24:
In file included from
/private/var/folders/rr/t_15q7dx4_lf1nv0btypffcw0000gn/T/arrow-15.0.0.XXXXX.li0gqOMB3O/apache-arrow-15.0.0/c_glib/vendor/bundle/ruby/3.3.0/gems/glib2-4.2.0/ext/glib2/../../lib/rbgobject.h:27:
In file included from
/private/var/folders/rr/t_15q7dx4_lf1nv0btypffcw0000gn/T/arrow-15.0.0.XXXXX.li0gqOMB3O/apache-arrow-15.0.0/c_glib/vendor/bundle/ruby/3.3.0/gems/glib2-4.2.0/ext/glib2/../../lib/rbgutil.h:26:
In file included from /opt/homebrew/Cellar/ruby/3.3.0/include/ruby-3.3.0/ruby/encoding.h:22:
/opt/homebrew/Cellar/ruby/3.3.0/include/ruby-3.3.0/ruby/internal/encoding/ctype.h:82:46: warning: unused parameter 'enc' [-Wunused-parameter]
rb_enc_isascii(OnigCodePoint c, rb_encoding *enc)
                                             ^
In file included from rb-gi-arg-info.c:21:
In file included from ./rb-gi-private.h:28:
/opt/homebrew/Cellar/gobject-introspection/1.78.1/include/gobject-introspection-1.0/girffi.h:25:10: fatal error: 'ffi.h' file not found
#include <ffi.h>
         ^~~~~~~
1 warning and 1 error generated.
make: *** [rb-gi-arg-info.o] Error 1

make failed, exit code 2

Gem files will remain installed in
/private/var/folders/rr/t_15q7dx4_lf1nv0btypffcw0000gn/T/arrow-15.0.0.XXXXX.li0gqOMB3O/apache-arrow-15.0.0/c_glib/vendor/bundle/ruby/3.3.0/gems/gobject-introspection-4.2.0 for inspection.
Results logged to
/private/var/folders/rr/t_15q7dx4_lf1nv0btypffcw0000gn/T/arrow-15.0.0.XXXXX.li0gqOMB3O/apache-arrow-15.0.0/c_glib/vendor/bundle/ruby/3.3.0/extensions/arm64-darwin-23/3.3.0/gobject-introspection-4.2.0/gem_make.out

  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/rubygems/ext/builder.rb:125:in `run'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/rubygems/ext/builder.rb:51:in `block in make'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/rubygems/ext/builder.rb:43:in `each'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/rubygems/ext/builder.rb:43:in `make'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/rubygems/ext/ext_conf_builder.rb:42:in `build'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/rubygems/ext/builder.rb:193:in `build_extension'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/rubygems/ext/builder.rb:227:in `block in build_extensions'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/rubygems/ext/builder.rb:224:in `each'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/rubygems/ext/builder.rb:224:in `build_extensions'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/rubygems/installer.rb:852:in `build_extensions'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/bundler/rubygems_gem_installer.rb:76:in `build_extensions'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/bundler/rubygems_gem_installer.rb:28:in `install'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/bundler/source/rubygems.rb:205:in `install'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/bundler/installer/gem_installer.rb:54:in `install'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/bundler/installer/gem_installer.rb:16:in `install_from_spec'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/bundler/installer/parallel_installer.rb:132:in `do_install'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/bundler/installer/parallel_installer.rb:123:in `block in worker_pool'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/bundler/worker.rb:62:in `apply_func'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/bundler/worker.rb:57:in `block in process_queue'
  <internal:kernel>:187:in `loop'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/bundler/worker.rb:54:in `process_queue'
  /opt/homebrew/Cellar/ruby/3.3.0/lib/ruby/3.3.0/bundler/worker.rb:90:in `block (2 levels) in create_threads'

An error occurred while installing gobject-introspection (4.2.0), and Bundler cannot continue.

In Gemfile:
  gobject-introspection
Failed to verify release candidate. See /var/folders/rr/t_15q7dx4_lf1nv0btypffcw0000gn/T/arrow-15.0.0.XXXXX.li0gqOMB3O for details.

Some info on the same comment thread:
% pkg-config --cflags gobject-introspection-1.0
-I/opt/homebrew/Cellar/gobject-introspection/1.78.1/include/gobject-introspection-1.0 -I/opt/homebrew/Cellar/glib/2.78.4/include -I/opt/homebrew/Cellar/glib/2.78.4/include/glib-2.0 -I/opt/homebrew/Cellar/glib/2.78.4/lib/glib-2.0/include -I/opt/homebrew/opt/gettext/include -I/opt/homebrew/Cellar/pcre2/10.42/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include/ffi

raul@raul-MacBook-Pro % ls -l /Library/Developer/CommandLineTools/SDKs/
total 0
drwxr-xr-x  7 root  wheel  224 Nov 19  2021 MacOSX12.1.sdk
drwxr-xr-x  3 root  wheel   96 Feb 10 14:11 MacOSX12.3.sdk
raul@raul-MacBook-Pro % sw_vers -productVersion
14.3.1

After manually adding the link sudo ln -s MacOSX12.3.sdk /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk it still failed.
Component(s)
Release, Ruby

Could you show the output of the following command line after you install pkg-config gem by PATH=$(brew --prefix ruby)/bin:$PATH gem install pkg-config?
PATH=$(brew --prefix ruby)/bin:$PATH ruby -r pkg-config -e 'p PKGConfig.cflags("gobject-introspection-1.0")'

Could you also show the output of the following command line?
pkg-config --debug --cflags libffi

Thanks for remembering this!
It seems that detected -Is are expected. ffi.h may not exist in /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include/ffi.
Could you show the output of the following command lines?
ls -lah /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include
ls -lah /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include/ffi


LZW decoder walks off the end of the code array

I have a test that works based on page 30 of the 98 CHAM

e2501b85b1351acf14f0dc8ce6d2b2cff00b27c8
fixed
We create one extra spot at the top of the decoder dictionary.  When we run out of space, we put each new run into the top spot and then immediately write it out before it gets replaced on the next code to be read.


TBI - Enhance ABAP deploy/undeploy flow to support service cli param

Description (include screenshots)
When running the ABAP deploy or undeploy commands, for example
npx deploy --url 'https://server.exmaple' -name ZJLONG0205 --transport 'Y11'  --package  '$tmp' --cloud --cloud-service-env --verbose --no-retry --archive-folder ./dist --noConfig

npx undeploy --url 'https://server.exmaple' --name 'ZJLONG0205' --transport 'Y11' --cloud --cloud-service-env --verbose --no-retry --noConfig

I should be able to append the --service param so that the SAPUI5 Repositroy OData service specified is used instead of the default /sap/opu/odata/UI5/ABAP_REPOSITORY_SRV.
This should also be supported if defined in the ui5-deploy.yaml, for example;
- name: abap-deploy-task
  configuration:
    log: 5
    app:
      name: Z_TEST
      package: $TMP
    target:
      url: https://target.example,
      service: 'bc/myservice'

Value
Improved way of deploying to a ABAP cloud.
Architecture Elaboration
No
Notes

axios-extension allows an alias to be passed to the getUi5AbapRepository method when generating the ABAP deploy service.

Tasks

[ ] Update CLI params to support --service
[ ] Update readme.md
[ ] Update test cases

Could you please inform the project piper team to include this parameter into the step transportRequestUploadCTS?
See Params:
https://www.project-piper.io/steps/transportRequestUploadCTS/

Confirmed as working in tools-suite.


Automate tag creation and artifact deployment

Part of automating the release process.
Changes

Use Travis stages instead of matrix

Jobs in a stage run concurrently
Jobs in a stage only start once all previous stages have completed successfully

Create a GitHub tag and deploy to OSSRH when triggering a build using the Travis API (more info below)

Build types
The type of build dictates which stages are executed:

Build type
Stages

PRs (unchanged)
test
All tests are run

Merge into master (unchanged)
deploy
Artifacts are deployed to OSSRH

API triggered (changed)
test, tag, release
All tests are run, tag is created, uploaded to GitHub, and deployed to OSSRH

Release builds (API triggered builds)
Release builds can be triggered for any branch by making a request to the Travis HTTP API (or through the Travis Web UI):
body='{
"request": {
"branch":"my-branch"
}}'

curl -s -X POST \
   -H "Content-Type: application/json" \
   -H "Accept: application/json" \
   -H "Travis-API-Version: 3" \
   -H "Authorization: token <Travis token> \
   -d "$body" \
   https://api.travis-ci.com/repo/jpmorganchase%2Ftessera/requests

This will:

Run the test stage on my-branch
Run the tag stage on my-branch

Creates a release branch from my-branch
Creates a tag from the release branch and uploads to GitHub
Increments the version on my-branch and the release branch

Run the release stage on my-branch (currently doesn't do anything)

ToDo

Test it works.

On my repo I've tested the GitHub tag functionality works but haven't yet tried the OSSRH deployment.
I don't know if Travis will be able to push changes to master which is necessary to do releases direct from master

Look into Travis Deployments.  The release stage currently does nothing but may be able to create a draft or full GitHub Release.  This should be done as a separate change.

Codecov Report

Merging #786 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #786   +/-   ##
=========================================
  Coverage     99.43%   99.43%
  Complexity     1917     1917
=========================================
  Files           288      288
  Lines          5700     5700
  Branches        289      289
=========================================
  Hits           5668     5668
  Misses            5        5
  Partials         27       27

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 a15ee00...a4d7872. Read the comment docs.

https://github.com/jpmorganchase/tessera/issues/738


Feature request: serve static assets with cache-control

As the title, in express it is supported by option of express.static like
const express = require('express');
const server = express();

const oneHour = 3600000;    // 3600000msec == 1hour
server.use(express.static('www', { maxAge: oneHour })); // Client-side file caching

server.get('/', function(req, res) {
  res.sendFile(__dirname + '/index.html');
});

server.listen(3000);

It makes sense.  I will going to add this feature for http.serve


[Bug] Span operation chain  is interrupted in the grpc plugin's onError method

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache SkyWalking Component
Java Agent (apache/skywalking-java)
What happened

The trace is not completed and disordered in a grpc request.
The agent log reports TracingContext|-|More than 300 spans required to create. In fact, there is not 300 span in the segment.

What you expected to happen
org.apache.skywalking.apm.plugin.grpc.v1.server.TracingServerCallListener
    public void onCancel() {
        final AbstractSpan span = ContextManager.createLocalSpan(operationPrefix + REQUEST_ON_CANCEL_OPERATION_NAME);
        span.setComponent(ComponentsDefine.GRPC);
        span.setLayer(SpanLayer.RPC_FRAMEWORK);
        ContextManager.continued(contextSnapshot);
        try {
            super.onCancel();
        } catch (Throwable t) {
            ContextManager.activeSpan().log(t);
            throw t;
        } finally {
            ContextManager.stopSpan();
            asyncSpan.asyncFinish();
        }
    }

The  contextSnapshot and asyncSpan are all null at some situation. This result in the cancal span is not stoped. when skywalking calls the getOrCreate method to create TracingContext, it will use the cancel tracingContext. Because the value of  CONTEX.get is not null.  Further more, This caused an error that exceeded the span quantity threshold.
org.apache.skywalking.apm.agent.core.context.ContextManager
    private static AbstractTracerContext getOrCreate(String operationName, boolean forceSampling) {
        AbstractTracerContext context = CONTEXT.get();
        if (context == null) {
            if (StringUtil.isEmpty(operationName)) {
                if (LOGGER.isDebugEnable()) {
                    LOGGER.debug("No operation name, ignore this trace.");
                }
                context = new IgnoredTracerContext();
            } else {
                if (EXTEND_SERVICE == null) {
                    EXTEND_SERVICE = ServiceManager.INSTANCE.findService(ContextManagerExtendService.class);
                }
                context = EXTEND_SERVICE.createTraceContext(operationName, forceSampling);

            }
            CONTEXT.set(context);
        }
        return context;
    }

How to reproduce
I will explain it with a demo. Suppose there are two applications named agent_test_2 and agent_test_3.
Agent_test_2 calls a grpc method named sayHello of Agent_test_3. There are many grpc calls at the same time. Some calls time out.  In this case, the trace is wrong.
Let's see the right traces.
A completed trace without error

A completed trace with timeout error

Let's see the wrong traces.
this trace is not completed

this trace is disordered

I have changed the code in my local computer and verify it. It works well.
org.apache.skywalking.apm.plugin.grpc.v1.server.TracingServerCallListener
    public void onCancel() {
        final AbstractSpan span = ContextManager.createLocalSpan(operationPrefix + REQUEST_ON_CANCEL_OPERATION_NAME);
        span.setComponent(ComponentsDefine.GRPC);
        span.setLayer(SpanLayer.RPC_FRAMEWORK);
        if (contextSnapshot != null) {
            ContextManager.continued(contextSnapshot);
        }
        try {
            super.onCancel();
        } catch (Throwable t) {
            ContextManager.activeSpan().log(t);
            throw t;
        } finally {
            ContextManager.stopSpan();
            if (asyncSpan != null) {
                asyncSpan.asyncFinish();
            }
        }
    }

Anything else
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@wu-sheng I have submitted a Agent PR, Please help me review it, Thank you!


TiKV running over 2 years may panic

Bug Report

What version of TiKV are you using?
nightly(this case also appears on v3.0.5)
What operating system and CPU are you using?

Steps to reproduce

Running TiKV for 795 days, then some RPC failure may cause panic.

No fatal error with TiKV.
What did happened?
TiKV quits with fatal error.
[2022/02/08 20:32:34.418 +08:00] [ERROR] [util.rs:419] ["request failed, retry"] [err_code=KV:PD:Unknown] [err="Other(\"[components/pd_client/src/tso.rs:85]: TimestampRequest channel is closed\")"]
[2022/02/08 20:32:34.418 +08:00] [ERROR] [util.rs:419] ["request failed, retry"] [err_code=KV:PD:Unknown] [err="Other(\"[components/pd_client/src/tso.rs:85]: TimestampRequest channel is closed\")"]
[2022/02/08 20:32:34.418 +08:00] [ERROR] [util.rs:419] ["request failed, retry"] [err_code=KV:PD:Unknown] [err="Other(\"[components/pd_client/src/tso.rs:85]: TimestampRequest channel is closed\")"]
[2022/02/08 20:32:34.418 +08:00] [ERROR] [util.rs:419] ["request failed, retry"] [err_code=KV:PD:Unknown] [err="Other(\"[components/pd_client/src/tso.rs:85]: TimestampRequest channel is closed\")"]
[2022/02/08 20:32:34.421 +08:00] [FATAL] [lib.rs:465] ["index out of bounds: the len is 6 but the index is 6"] [backtrace="   0: tikv_util::set_panic_hook::{{closure}}\n             at /home/jenkins/agent/workspace/optimization-build-tidb-linux-amd/go/src/github.com/pingcap/tikv/components/tikv_util/src/lib.rs:464:18\n   1: std::panicking::rust_panic_with_hook\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/panicking.rs:626:17\n   2: std::panicking::begin_panic_handler::{{closure}}\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/panicking.rs:519:13\n   3: std::sys_common::backtrace::__rust_end_short_backtrace\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/sys_common/backtrace.rs:141:18\n   4: rust_begin_unwind\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/panicking.rs:515:5\n   5: core::panicking::panic_fmt\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/core/src/panicking.rs:92:14\n   6: core::panicking::panic_bounds_check\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/core/src/panicking.rs:69:5\n   7: <usize as core::slice::index::SliceIndex<[T]>>::index_mut\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/core/src/slice/index.rs:190:14\n      core::slice::index::<impl core::ops::index::IndexMut<I> for [T]>::index_mut\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/core/src/slice/index.rs:26:9\n      <alloc::vec::Vec<T,A> as core::ops::index::IndexMut<I>>::index_mut\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/alloc/src/vec/mod.rs:2445:9\n      tokio_timer::wheel::Wheel<T>::insert\n             at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-timer-0.2.13/src/wheel/mod.rs:114:9\n      tokio_timer::timer::Timer<T,N>::add_entry\n             at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-timer-0.2.13/src/timer/mod.rs:324:15\n   8: tokio_timer::timer::Timer<T,N>::process_queue\n             at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-timer-0.2.13/src/timer/mod.rs:301:21\n   9: <tokio_timer::timer::Timer<T,N> as tokio_executor::park::Park>::park\n             at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-timer-0.2.13/src/timer/mod.rs:361:9\n      tokio_timer::timer::Timer<T,N>::turn\n             at /rust/registry/src/github.com-1ecc6299db9ec823/tokio-timer-0.2.13/src/timer/mod.rs:256:21\n  10: tikv_util::timer::start_global_timer::{{closure}}\n             at /home/jenkins/agent/workspace/optimization-build-tidb-linux-amd/go/src/github.com/pingcap/tikv/components/tikv_util/src/timer.rs:98:17\n  11: std::sys_common::backtrace::__rust_begin_short_backtrace\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/sys_common/backtrace.rs:125:18\n  12: std::thread::Builder::spawn_unchecked::{{closure}}::{{closure}}\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/thread/mod.rs:476:17\n  13: <std::panic::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/panic.rs:347:9\n  14: std::panicking::try::do_call\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/panicking.rs:401:40\n      std::panicking::try\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/panicking.rs:365:19\n      std::panic::catch_unwind\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/panic.rs:434:14\n      std::thread::Builder::spawn_unchecked::{{closure}}\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/thread/mod.rs:475:30\n      core::ops::function::FnOnce::call_once{{vtable.shim}}\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/core/src/ops/function.rs:227:5\n  15: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/alloc/src/boxed.rs:1572:9\n      <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/alloc/src/boxed.rs:1572:9\n      std::sys::unix::thread::Thread::new::thread_start\n             at /rustc/2faabf579323f5252329264cc53ba9ff803429a3/library/std/src/sys/unix/thread.rs:91:17\n  16: start_thread\n  17: __GI___clone\n"] [location=/rust/registry/src/github.com-1ecc6299db9ec823/tokio-timer-0.2.13/src/wheel/mod.rs:114] [thread_name=timer]

Because all the versions of TiKV use the deprecated tokio-timer, the bug exists in all versions.
https://github.com/tikv/tikv/blob/ddec018650bc47425369b4aaa9e4ba9c1fd68924/Cargo.toml#L152
The problem comes here(fixed in the latest tokio).

fn level_for(elapsed: u64, when: u64) -> usize {
    const SLOT_MASK: u64 = (1 << 6) - 1;

    // Mask in the trailing bits ignored by the level calculation in order to cap
    // the possible leading zeros
    let masked = elapsed ^ when | SLOT_MASK;

    let leading_zeros = masked.leading_zeros() as usize;
    let significant = 63 - leading_zeros;
    significant / 6
}

In which, elapsed stands for the elapsed time since the process is started, and when stands for the expired wake-up time since the process is started. Suppose elapsed is 2 ^ 36 - 1 and when is 2 ^ 36, we'll get masked with 27 leading zeros, and the result level is 6 which causes the "index out of bounds" error.

/severity Critical

interesting

@you06 Any plans to upgrade to use the replacement module?

As you mentioned, tokio-timer is now a feature of tokio, I'm afraid there are some differences in the usage, liketokio::timer is relied on the tokio's runtime. On the other hand, yatp does not support the time feature, so the fix needs to be discussed.

Do we have a workaround?

Do we have a workaround?

Rolling restarting TiKV cluster every 2 years.

What we want is a timer with customizable now implementation. Perhaps we can just maintain our own crate without depending on specific runtime.

@BusyJay For an easy approach, what about futures-timer?. CDC is using it, and I'm currently trying to replace tokio-timer with it.
https://github.com/tikv/tikv/blob/3433be962dabf8662181fc1f81c421d95a8b86e5/components/cdc/Cargo.toml#L56

No, it doesn't support custom new.

@BusyJay Sorry I don't understand the relationship between custom now and this issue. Even there is a custom now in TiKV, the incorrect time wheel calculation can still lead to panic. Custom now looks like an enhancement to me. May you explain what needs to be replaced and how to fix this issue?

A customized new will not fix the issue. What I mean is new implementations should allow customizing new, because TiKV needs a steady timer to guarantee correctness.

@BusyJay  Do you think it's necessary to fork tokio-timer and fix this bug so that we can do a hotfix? We can replace this when a self-maintained time crate is available in the future.

LGTM


Custom bubble and handle catch the touches/clicks/scrolling gestures after they are hidden

I have a recycler view with custom cards and the fast scroller in a relative layout.
I used a custom view provider which is mostly based on the default view provider except for a few changes to the bubble's layout. Things work smoothly w.r.t to scrolling and indexing.
However, when the bubble hides after being released, all the touches, clicks, scrolls made on the "bubble area" are being blocked by the invisible bubble and thereby prevents the recycler view from collecting them. So, the recycler view basically does nothing when tapped or scrolled on the region where the bubble is present. In the sample project , this does not happen though.
Any ideas on what might be causing this?

Figured it out. I had an onTouchListener buried deep inside my code which was picking up the gestures. Thanks for reading.


Add support for device actions

Ready to review, but please do not merge until both this and https://github.com/FlowFuse/flowfuse/pull/3548 are approved
(in case of change requests from either side)
Description
Outline
Adds support for suspend, start  and restart MQTT command actions (via the platform device comms)
Demo of FF side

Sample output from device agent when the actions are executed:

Details

Adds new command route to mqtt.js: "action"

Supports "start", "suspend", "restart"

Adds targetState property (persisted to the project file to ensure reboots to correct target state)

targetState supports only "running" and "suspended" at this time

Converted hardcoded "state" strings into a an enum (was getting lost with all the supported states) $ added helper functions for verifying state
To support timely and more accurate state feedback to FF, checkin is now called when state changes inside the launcher (important now we have transitional state info reporting on FF and necessary for good UX on the Actions menu items availability)
Attempts to mitigate issue when agent is busy installing modules and the launcher is stopped by awaiting the install process for a few seconds grace before forcefully stopping. This was done as I managed cause a lock ups by ill timed restarts and suspends during testing.

NOTE: This was a balance struck on making the device "do what it is told" vs "leaving it "stuck installing" or "stuck starting" etc.
We may want to revisit and simply inhibit actions altogether while installation is occurring.

Tests added
  Agent
    actions
      ✔ suspends Node-RED
      ✔ reloads target state as suspended
      ✔ reloads target state as running
      ✔ restarts Node-RED
      ✔ starts Node-RED after suspend
    getState
      ✔ returns state when suspended

  MQTT Comms
    ✔ suspend action calls agent.suspendNR and checks in (573ms)
    ✔ start action calls agent.startNR and checks in (567ms)
    ✔ restart action calls agent.restartNR and checks in (576ms)
    ✔ Invalid action responds with error (568ms)

  State validation
    ✔ isValidState should return true for valid states
    ✔ isValidState should return false for invalid states
    ✔ isTargetState should return true for valid target states
    ✔ isTargetState should return false for invalid target states
    ✔ isTransitionState should return true for valid transition states
    ✔ isTransitionState should return false for invalid transition states

Related Issue(s)
https://github.com/FlowFuse/flowfuse/issues/3292
Checklist

[x] I have read the contribution guidelines
[x] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

[ ] Upgrade instructions
[ ] Configuration details
[ ] Concepts

[ ] Changes flowforge.yml?

[ ] Issue/PR raised on FlowFuse/helm to update ConfigMap Template
[ ] Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

[ ] Backport needed? -> add the backport label
[ ] Includes a DB migration? -> add the area:migration label

No structural changes being made in the forge app around how it will send commands to the device agent. We are only shipping the restart command initially as there are unresolved questions on the semantics of suspend (and thus start is also unnecessary).
@Steve-Mcl I think we're okay to merge this as-is?

No structural changes being made in the forge app around how it will send commands to the device agent. We are only shipping the restart command initially as there are unresolved questions on the semantics of suspend (and thus start is also unnecessary).
@Steve-Mcl I think we're okay to merge this as-is?

Yeah. Ben and I have tested against local and staging.


Window Focus Refetching

React query has a really nice feature that automatically requests fresh data when the user refocuses on the window. Is there any way to do that with gqty?

Note to self: useIsWindowVisible(), depends on: query.$refetch()


Version mentioned in 4.0 seems wrong

Hi,
I have built 4.0 version from 4.0 branch but version file mentions 5.0.0-alpha. Can someone please clarify what is wrong here?
Thanks and Regards,
codec

Please respect guidelines for posting issue: use tesseract user forum for asking questions/support.

master branch is 5.0.0-alpha. If you need 4.ox, clone 4.1 branch

The VERSION file in the 4.0 branch was indeed wrong. I now fixed it in commit c69859cacb040a518cd64206ab1a2d6e48d17854.
@codecolony, thank you for reporting this.

@stweil Thanks a lot for clarifying. Appreciate your effort.


Shows a blank display name after pasting the connection string of one Germany account

Storage Explorer Version:1.4.1
Platform/OS Version: Windows 10/ Linux Ubuntu 16.04/ MacOS High Sierra
Architecture:ia32/x64
Build Number:20180820.1
Commit:bbb595d2
Regression From: Not a regression
Steps to Reproduce:

Sign in with one Germany account.
Create a SAS connection string for one account like below.AccountName=cawatest03;
SharedAccessSignature=sv=2018-03-28&ss=bfqt&srt=sco&sp=rwdlacup&st=2018-08-21T10%3A04%3A12Z&se=2018-08-22T10%3A04%3A12Z&sig=uGGtL5jl9l99AYJxqV9d4T3AM7ABnindrz%2Fd%2FE5gphg%3D;
BlobEndpoint=https://cawatest03.blob.core.cloudapi.de/;
FileEndpoint=https://cawatest03.file.core.cloudapi.de/;QueueEndpoint=https://cawatest03.queue.core.cloudapi.de/;
TableEndpoint=https://cawatest03.table.core.cloudapi.de/;

Open Connect dialog and pasting the created connection string -> Check whether the default account name auto shows under 'Display name' or not.

Expected Experience:
The default account name auto shows under 'Display name'.
Actual Experience:
Display a blank display name under 'Display name'.

By design. We only auto-fill the display name if the connection string has an AccountName value.

I'm calling shenanigans on that @craxal . We auto fill the name for a public Azure SAS URI. I don't think this needs to be in 1.4.1, but I'm going to put it in 1.5.0.

Oh, whoops, you're right. Had to take a closer look at the code.

This issue also reproduces on the latest master build 20190813.3.

@v-xianya I am unable to reproduce this bug on main branch. Can you verify whether this reproduces on your end? If so, please provide more information that may be helpful.

@craxal Verified this issue on build main/20201201.2. Reproduce. The record please see the below.


SQLSTATE[HY000]: General error: 1 ambiguous column name: name

Expected behaviour
When browse to "Project Management" there should be no ERROR.
Actual behaviour
SQL error occurs see in debug.log;-
[2016-04-05 20:52:19] [debug] SELECT projects.*, users.username AS owner_username, users.name AS owner_name FROM "projects" LEFT JOI
N "users" ON "users"."id"="projects"."owner_id"  WHERE projects.id IN (?, ?)   ORDER BY "name" ASC  LIMIT 20  OFFSET 0
[2016-04-05 20:52:19] [debug] SQLSTATE[HY000]: General error: 1 ambiguous column name: name
Page displays the following:-
Users overview
Projects Gantt chart
Internal Error: SQL error: SQLSTATE[HY000]: General error: 1 ambiguous column name: name
Id 	Status 	▲ Project 	Start date 	End date 	Owner 	Users 	Columns
Steps to reproduce

Try browse to "Project Management"
SQLSTATE[HY000]: General error: 1 ambiguous column name: name page display

Configuration
Copy and paste the configuration section from the Kanboard settings page or fill these fields:

Kanboard version: 1.0.27
Database type and version:  sqlite 3.3.6
PHP version: php.x86_64   5.1.6-45.el5_11
OS: CentOS Linux 2.6.18-407.el5xen
Browser: Firefox 45.0.1

Duplicate of #1976.
Which version of Centos do you have? 5.1?


Refactoring QA line extraction for new LE method

We will now be integrating the new eynollah line extraction method into the current QA code for the purposes of comparing it to the original watershed line extraction method.

Paused while error investigation/error processing for line extraction QA is implemented.

Notes from this afternoon's meeting with @nvog and @kartikgo
For line_extract_eynollah.sh in code folder:

[ ] Comment out last line until rest working python3 -u $CODE/eynollah_line_image_extraction.py...
[ ] Get full shell script to run on example
[ ] Try without downscaling first for baseline times
[ ] Cpu count will probably have to be ~8 per process with 2GB memory each
[ ] Introduce downscaling
[ ] Converting parts of shell script to Python calls like with watershed
[ ] Downscale via image library and then save images to disk
[ ] Try 25% of original image for downscaling

Reopening this issue as running Eynollah from QA needs to be reimplemented using the new Eynollah workflow scripts.


Menu Dropdown Value Change

Fixes #1458
Additional description
When the dropdown value is being changed in nextProps, we are passing in nextProps.options along with nextProps.value, to handle the case where the options list changes and we are selecting a value within this new options list.
CONTRIBUTOR checklist (do not remove)
Please complete for every pull request

[ ] First-time contributors should sign the Contributor License Agreement.  If you haven't before, wait a few minutes and a bot will comment on this pull request with instructions.
[ ] npm run lint:fix has been run and linting passes.
[ ] Mocha, Jest (Storyshots), and components/component-docs.json CI tests pass (npm test).
[ ] Tests have been added for new props to prevent regressions in the future. See readme.
[ ] Review the appropriate Storybook stories. Open http://localhost:9001/.
[ ] The Accessibility panel of each Storybook story has 0 violations (aXe). Open http://localhost:9001/.
[ ] Review tests are passing in the browser. Open http://localhost:8001/.
[ ] Review markup conforms to SLDS by looking at DOM snapshot strings.

REVIEWER checklist (do not remove)

[ ] TravisCI tests pass. This includes linting, Mocha, Jest, Storyshots, and components/component-docs.json tests.
[ ] Tests have been added for new props to prevent regressions in the future. See readme.
[ ] Review the appropriate Storybook stories. Open http://localhost:9001/.
[ ] The Accessibility panel of each Storybook story has 0 violations (aXe). Open http://localhost:9001/.
[ ] Review tests are passing in the browser. Open http://localhost:8001/.
[ ] Review markup conforms to SLDS by looking at DOM snapshot strings.
[ ] Add year-first date and commit SHA to last-slds-markup-review in package.json and push.
[ ] Request a review of the deployed Heroku app by the Salesforce UX Accessibility Team.
[ ] Add year-first review date, and commit SHA, last-accessibility-review, to package.json and push.
[ ] While the contributor's branch is checked out, run npm run local-update within locally cloned site repo to confirm the site will function correctly at the next release.

I looked at the component tests but didn't feel it was necessary to add one for this use case. Let me know otherwise.

@alexxpan You have an invite to this org at: https://github.com/salesforce
Once accepted refresh the CLA bot: https://cla.salesforce.com/status/salesforce/design-system-react/pull/1459

@alexxpan Thanks for the pull request. We'll try to get it looked at in the next week.
@futuremint Could you review this? Seems like we may not be getting our internal state right (and updating when props change).

@interactivellama I worked on this PR with @alexxpan (he's on my team). Do you think we can get this in soon enough for feature freeze?

@interactivellama I read through the code and it looks ok to me. The only internal state derived from props are for the selectedIndices, and those are updated from componentWillRecieveProps.  However we should probably add some unit tests around controlled components and making sure they keep their state synced after prop changes.


Ejecting should git add scripts and config folders

If we use git, then you should be auto-added on eject so that you can commit right away.

Hey @gaearon! I really love this tool & would really love to start contributing to it. Could I grab this to try & get my feet wet with the project?

Yes, it's all yours!

Closed via #5960


allow more networks for proxy contracts

Description
We recently merged #80, it was a quick fix but maybe instead of relying on ethers for alchemy provider (which has very limited providers) we rely on general JsonRpcProvider and get the alchemy link from viem chains.
Also updated the logic a bit so now we only check for proxy contracts if we have viem's alchemy link for that chain

Thanks Port, Merging this for now but lets get our custom solution once read 🙌!


G_Attractor_Mass initialization

It seems G_Attractor_Mass initialization is missing... or am I wrong?
Because it should be null when you try to assign it to the vec.w
vec.w = G_Attractor_Mass[i];

Yes, you are completely right.
I commented it out, because like observed, it is not properly used.
And not read at all. So it just set vec.w to Zero (constantly) for now.
Thanks!


Introduce a better way to define the UI

Is your feature request related to a problem? Please describe.
A common question is how to customize the UI to your own needs. Sometimes some options already exist such as show-bread-crumbs.
Describe the solution you'd like
I have thought of templating for the UI.
Each element can be placed in a desired position or hidden. Additionally, a set of options can be defined for each element:

Background
Font
Height
Width
...

Maybe it's not the best idea. But I think offering config options for everything is also rather not a good idea as it fragments the configuration and there is little consistency.
Additional context
What is the background of my idea?
vscode does not have a very comfortable interface. Happily, there is a plugin that allows extensive customization customize-ui. Microsoft broke it. And it seems like they dont want to rollback the change. There are many PRs for the customizations to support them natively but they have not been worked on for several years now. The extension was installed over 140.000 times. The disappointment is huge: https://github.com/iocave/customize-ui/issues/156
Don't be like Microsoft. Give the user the possibilities from the beginning.

What is currently not possible what you listed?

Line height works for editor, but not for UI.
I would also like to hide the titlebar.
But to be honest: That is not my point here.
I followed the discussion at vscode and customize-ui and I have seen the big interesst in personal customization and the fact that its to much to define it in a traditional config file.
As lapce is very young with a great community I just wanted to share this observation.

Most of the list issues are already opened for tracking or fixed


Run tests in CI

Codecov Report

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

@@           Coverage Diff           @@
##             main      #28   +/-   ##
=======================================
  Coverage        ?   98.88%
=======================================
  Files           ?        7
  Lines           ?      180
  Branches        ?       49
=======================================
  Hits            ?      178
  Misses          ?        2
  Partials        ?        0

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Tasks always terminate with exit code 2 on Samba directory on Windows

Issue Type: Bug

Create a tasks.json:

{
    // See https://go.microsoft.com/fwlink/?LinkId=733558
    // for the documentation about the tasks.json format
    "version": "2.0.0",
    "tasks": [
        {
            "label": "test",
            "type": "shell",
            "command": "dir",
        },
    ]
}

Run the task, it outputs:

The terminal process terminated with exit code: 2

VS Code version: Code 1.32.3 (a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4, 2019-03-14T23:43:35.476Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz (4 x 3912)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
3.91GB (0.59GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

vscode-wordcount-cjk
hol
1.3.0

background
sha
1.1.19

vim
vsc
1.2.0

If you cd to the Samba directory from the VS Code integrated terminal and run dir from there does it work?

If you cd to the Samba directory from the VS Code integrated terminal and run dir from there does it work?

Yes, and other commands also work.

Only commands defined in tasks.json do not work.

If you scroll up in terminal that the task runs in (up before the The terminal process terminated with exit code: 2) is there any other information?

If you scroll up in terminal that the task runs in (up before the The terminal process terminated with exit code: 2) is there any other information?
There is no except Executing task

What happens if you set a cwd on the task? https://code.visualstudio.com/Docs/editor/tasks#_custom-tasks

Seems that it's because Windows's cmd isn't compatible with remote directory. After upgrading both Windows and vscode I get The terminal shell CWD "\\\wsl$\Arch\tmp" does not exist as command output.
I don't know if it's because cmd changes its way to output error message, or vscode's terminal changed its way to get program output. I don't know if this issue(error message of cmd doesn't appear on terminal output) still exists on old versions of Windows either.
System info:
Version: 1.38.1 (system setup)
Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0
Date: 2019-09-11T13:35:15.005Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18362

Thanks, and sorry for wasting your time.

Thanks for checking again. Sounds like it's safe to close!


test: enabling Spark tests with offHeap requirement

Which issue does this PR close?
Rationale for this change
After https://github.com/apache/datafusion-comet/pull/1062 We have not running Spark tests for native execution
What changes are included in this PR?
Removed the off heap requirement for testing
How are these changes tested?
Bringing back Spark tests for native execution

Merged, thanks @andygrove


Added plot data, code and pngs

I've stolen this and improved it in my branch. Closing and opening other MR


Rename local variables to shadows issue

Issue # 📐

I Jai Marothiya have worked for #195

Guidelines 🔐
I accept the fact that I have followed the guidelines and have not copied the codes from around the internet

[x] Contribution Guidelines
[x] Code of Conduct

Issue to be closed 🛅

My pull request closes #

Screenshots 📷
Here are the pictures of changes that I have made 🔽

@Jai-Marothiya make the changes in the title as the bot has suggested


KAFKA-17534: Add configuration to disable the heartbeats topic replic…

…ation by MirrorSourceConnector
Introducing heartbeats.replication.enabled to explicitly disable the default heartbeats topic replication. This change implements KIP-1089.
More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@urbandan merged it, thanks for your contribution!

@urbandan I can't thank you enough for this!! This will be super helpful!

@pedro-te Great to hear, thanks! :)


The optimizations we need and deserve

Closes #27

Benchmarks again on my machine:
Fibonacci - 1.8s
Arithmetic Operations Loop - 1.025s
Empty Loop - 215ms


[codespaces] bump oryx to 20210319.1

closes https://github.com/microsoft/vssaas-planning/issues/1813
closes https://github.com/microsoft/vssaas-planning/issues/1982
Bumps oryx version, fixing some python scenarios.

lets do it now - get these python issues closed :)

CI for dev tag is now running: https://github.com/microsoft/vscode-dev-containers/actions/runs/680245077


Check for capitalization

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

@timabbott, can you please review this? The architecture is complete so it would be great if you can take a look.

I am also trying to add some code which will make the checker a bit more aware of the common words like 'Zulip' which will always be capitalized.

Added code to ignore phrases. Still need to add tests.

@timabbott, @showell: Please view.

Yep, will tomorrow.
On Mon, Mar 6, 2017 at 6:31 PM showell<EMAIL_ADDRESS>wrote:

@showell commented on this pull request.
In tools/lib/capitalization.py
https://github.com/zulip/zulip/pull/3905#discussion_r104413189:

+TRANSLATION_FUNCTION = [

('^\s*{}', START_PLACEHOLDER),
('.\s+{}', '. ' + PUNCTUATION_PLACEHOLDER),
('!\s+{}', '! ' + PUNCTUATION_PLACEHOLDER),
('?\s+{}', '? ' + PUNCTUATION_PLACEHOLDER),
+]

+def apply_translation_function(string):

type: (str) -> str

for phrase in IGNORED_PHRASES:

   for regex_template, placeholder in TRANSLATION_FUNCTION:

       regex = regex_template.format(phrase)

       string = re.sub(regex, placeholder, string)

   string = string.replace(phrase, phrase.lower())

   string = string.replace(START_PLACEHOLDER, phrase.capitalize())

I would add comments here explaining the purposes of the PLACHEHOLDERs.
For the punctuation piece, are sure it doesn't make sense to do something a
little less hacky like break the string into a list of phrases?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip/pull/3905#pullrequestreview-25248794, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAnK4_dbRusLrJ02vRfT7IC5wmIV0j3bks5rjAq9gaJpZM4MSOFU
.

--
Sent from mobile.

Mostly done with the new method of splitting string in sentences. Still need to handle some edge cases.

@timabbott and @showell, please review now.

Found https://github.com/zulip/zulip/issues/3981 while testing this :)

You are up so late :).

Cool, I think at least these seems wrong and we should change them:
API Key
Alert Word
Allow Subdomains
Change Password
Copy from Stream
Deactivate Account
Delete Alert Word
Delete Avatar
Edit User
Exit Tutorial
Full Bot Name
Generate new API Key
No Drafts.
Not Delivered: Delete
Not Delivered: Edit
Not Delivered: Resend
Only Admins may now add new emoji!
Only Admins may now create new streams!
Stream Name
Upload New Avatar
View Source
View Source / Edit Topic
waiting period threshold changed!
Bot Email
Log In
Only Basic authentication is supported.
Organization Type
Short Name
Zulip Dev Login
Zulip Features

You can add commits to this branch fixing the capitalization of these, one commit per term, and we can merge those :)

Sure. Doing it.

I should have mentioned -- you need to git grep for these words, since they can appear in the user documentation (templates/zerver/help/, etc.)

I merged a bunch of these after doing the greps; the ones I didn't merge I think maybe we want to change the text more extensively.

I think maybe we want to change the text more extensively than just the capitalization while we're at it

Shall I go ahead with it?

I think maybe I should just spend half an hour going through the rest of the errors, since there aren't many left...

OK.

I cleaned up a bunch of broken or incorrectly tagged for translation strings that this found for us,  and merged this as 83dd901ecf601cb79981ccee8222fd1a2407a422 to stem the tide of new capilization errors going in.  There's a few hacks that I had to add in check_capitalization that it'd be great if you investigated @umairwaheed; I wasn't able to get those to work by adding them to the exclude list.
Huge thanks for building this, I think it's going to save a ton of time and mistakes :)

Oh. Sure, I'll check those out.


Charging attribute : issue or feature ?

Hello,
"Charging" attribute is set to true or false if "Charge State" > 0 by : self._attrs[ATTR_CHARGING] = jsonresult['chargingStatus'] > 0
Is this a feature ? Because, charging status could have values between 0 and 1. And for my perception this values are "not charging" (charging = false). https://github.com/jamesremuscat/pyze/blob/05dbe5d28ff73ecf0553bc33c7ab5913cb786cfe/src/pyze/api/kamereon.py#L371
In my opinion only value 1.0 is "charging".  But it could be a position to set "charging" to true when value > 0 and let people check "charge state" for the "real status".
What do you think about it ?
Thanks for your time.

Hi @PysX,
Can you update to v3.0.0 and see if that is still an issue?

Hi @epenet, what a nice upgrade !
v3.0.0rc2 installed and running. I will plug my car tomorrow and let you informed of results for charge state / status.
i will monitor other sensors to review if they are working like in the v2.x.
Actuallay, one sensor is missing ("charging remaining time"), may be it's a sensor's state and the car need to be in charging state. I will check that too.
Thanks for your work!

Keep me posted about "charging remaining time". It's true that it's not one I've paid attention to so I may have missed it.

Hi !
Since Saturday, the v3 rc2 is working great on my home assistant and the subject of this issue is closed.
About charging remaining time, i do not have the sensor. I tried to remove / reconfigure the integration during charge: no effect.
I will provide more info with debug log and some testing.

Ok, some testing with conclusion that's just a missing "entities.append" !
I suggest the following PR : #52 , tested on my installation.
I you want you can close this issue ! Thanks !

Nice spot.
Thanks @PysX


Dynamic attributes are not rendered correctly on Firefox after page refresh

Environment
------------------------------
- Operating System: Darwin
- Node Version:     v19.8.1
- Nuxt Version:     3.6.5
- Nitro Version:    2.5.2
- Package Manager<EMAIL_ADDRESS>- Builder:          vite
- User Config:      -
- Runtime Modules:  -
- Build Modules:    -
------------------------------

Reproduction
https://stackblitz.com/edit/nuxt-starter-g6fvbn?file=app.vue
Describe the bug
If an attribute is toggled dynamically, on first-page load it is rendered correctly and works as expected.
After a full page refresh, the attribute is not rendered correctly anymore.
Steps to reproduce

Open Firefox and visit the reproduction
Click on Toggle Button State, this will enable the button as expected
Refresh the page (the StackBlitz one)
Notice that the button has no attribute disabled

Additional context
The issue is not just on the dev server, It persists also in prod.
Logs
No response

Sorry if I haven't been clear enough, maybe a video is better. When I refresh the page, I expect the button to be disabled as the ref is initialized with false.
https://github.com/nuxt/nuxt/assets/60471784/38bfd77f-e637-495a-bdd8-5a5932d0f163

Oki, thanks for clarifying.

you're very welcome!

Opened an issue here: https://bugzilla.mozilla.org/show_bug.cgi?id=1848982


It does not work with angular 8.0.0 and ivy enabled

when building I get error:
ERROR in node_modules/ng2-password-strength-bar/lib/passwordStrengthBar.module.d.ts(1,22): error TS-996002

Any chance of updating the library to support Angular 9? Or do you accept PR?

@jhkueh I'm not sure how backward compatibility would work, but I'd be happy to evaluate a PR. Thanks!

Please see https://github.com/rnadler/ng2-password-strength-bar/issues/26#issuecomment-640323525.


Update README.md

There was a parenthesis and curly parenthesis error in the custom dialog example, a small contribution.

Hello @mahirozdin 👋
We appreciate your efforts but sadly we are moving forward without accepting this PR, As we are preparing to launch QuicklAlert 2.0 and we'll have a newly updated readme.md file.
Happy Coding ✨

Hi. No worries just wanted to help little. I wish you very best of luck
with 2.0 we are using quick alert on every project. Very useful.
Best Regards
8 Mar 2023 Çar, saat 20:35 tarihinde Akash S @.***>
şunu yazdı:

Hello @mahirozdin https://github.com/mahirozdin 👋
We appreciate your efforts but sadly we are moving forward without
accepting this PR, As we are preparing to launch QuicklAlert 2.0 and we'll
have a newly updated readme.md file.
Happy Coding ✨
—
Reply to this email directly, view it on GitHub
https://github.com/belovance/QuickAlert/pull/16#issuecomment-1460554701,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACINF4P2YKO5OEFBEIXIHDLW3C7MZANCNFSM6AAAAAAVIOH3NA
.
You are receiving this because you were mentioned.Message ID:
@.***>


With Hive 1.1.0 not working

Hi,
we would like to create virtual schemas on Hive 1.1.0 but it's not working.
We get the error message:
SQL Error [22002]: VM error:
com.exasol.adapter.AdapterException: Unable create Virtual Schema "HIVE_TEST". Cause: "No suitable driver found for jdbc:hive2://app-qhaphiv-vc1.fhm.de:10000
Stack trace:
com.exasol.adapter.jdbc.JdbcAdapter.createVirtualSchema(JdbcAdapter.java:39)
com.exasol.adapter.RequestDispatcher.dispatchCreateVirtualSchemaRequestToAdapter(RequestDispatcher.java:110)
com.exasol.adapter.RequestDispatcher.processRequest(RequestDispatcher.java:70)
com.exasol.adapter.RequestDispatcher.executeAdapterCall(RequestDispatcher.java:52)
com.exasol.adapter.RequestDispatcher.adapterCall(RequestDispatcher.java:41)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.base/java.lang.reflect.Method.invoke(Method.java:566)
com.exasol.ExaWrapper.runSingleCall(ExaWrapper.java:95) (Session:<PHONE_NUMBER>554256568)

We have Hive 1.1.0 and use the jdbc-driver hive-jdbc-1.1.0-cdh5.16.2-standalone.jar.
Best regards
Nicola

I've updated to the newest release of the virtual schema adapter and now I get the following:
SQL Error [22002]: VM error:
com.exasol.adapter.jdbc.RemoteMetadataReaderException: Unable to create Hive remote metadata reader.
Stack trace:
com.exasol.adapter.dialects.hive.HiveSqlDialect.createRemoteMetadataReader(HiveSqlDialect.java:126)
com.exasol.adapter.dialects.AbstractSqlDialect.readSchemaMetadata(AbstractSqlDialect.java:138)
com.exasol.adapter.jdbc.JdbcAdapter.readMetadata(JdbcAdapter.java:56)
com.exasol.adapter.jdbc.JdbcAdapter.createVirtualSchema(JdbcAdapter.java:33)
com.exasol.adapter.RequestDispatcher.dispatchCreateVirtualSchemaRequestToAdapter(RequestDispatcher.java:110)
com.exasol.adapter.RequestDispatcher.processRequest(RequestDispatcher.java:70)
com.exasol.adapter.RequestDispatcher.executeAdapterCall(RequestDispatcher.java:52)
com.exasol.adapter.RequestDispatcher.adapterCall(RequestDispatcher.java:41)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.base/java.lang.reflect.Method.invoke(Method.java:566)
com.exasol.ExaWrapper.runSingleCall(ExaWrapper.java:95) (Session:<PHONE_NUMBER>554256568)

Another update: using the hive driver hive-jdbc-2.3.7-standalone.jar I get the same error

On the other end, if I use hive-jdbc-2.3.7-standalone.jar with version 3.1.0 of the adapte I get the following error:
SQL Error [22002]: VM error:
com.exasol.adapter.AdapterException: Unable create Virtual Schema "HIVE_TEST". Cause: "Could not open client transport with JDBC Uri: jdbc:hive2://app-qhaphiv-vc1.fhm.de:10000: Could not establish connection to jdbc:hive2://app-qhaphiv-vc1.fhm.de:10000: Required field 'client_protocol' is unset! Struct:TOpenSessionReq(client_protocol:null, configuration:{set:hiveconf:hive.server2.thrift.resultset.default.fetch.size=1000, use:database=default})
Stack trace:
com.exasol.adapter.jdbc.JdbcAdapter.createVirtualSchema(JdbcAdapter.java:39)
com.exasol.adapter.RequestDispatcher.dispatchCreateVirtualSchemaRequestToAdapter(RequestDispatcher.java:110)
com.exasol.adapter.RequestDispatcher.processRequest(RequestDispatcher.java:70)
com.exasol.adapter.RequestDispatcher.executeAdapterCall(RequestDispatcher.java:52)
com.exasol.adapter.RequestDispatcher.adapterCall(RequestDispatcher.java:41)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.base/java.lang.reflect.Method.invoke(Method.java:566)
com.exasol.ExaWrapper.runSingleCall(ExaWrapper.java:95) (Session:<PHONE_NUMBER>554256568)

Hello @nicolamarangoni !
For the first error message: as the driver you are using is different from the recommended one, you need to find and register the right parameters for it in EXAOperation (main class, prefix, files). You could also check carefully the driver name in the adapter script, maybe you copied and pasted it with typos.
Unfortunately, we have not tested the hive dialect with Hive 1.1.0. The latest tested Hive version is 2.3.2.
Also, the drivers you're using are not tested too, we recommend using Hive JDBC Connector if it's possible (check the link here: https://github.com/exasol/virtual-schemas/blob/master/doc/dialects/hive.md).
The second exception doesn't contain any valuable information. We need logs from virtual schemas to diagnose a problem. Please, check how to start remote logging here: https://docs.exasol.com/database_concepts/virtual_schema/logging.htm
The third error sounds like a connection problem. You could try to connect to Hive with that driver without Virtual Schemas first to test the connection.
If your problem persists we will need logs and the statements you used to create an adapter script, virtual schema, and connection (please, be careful with your private information).
Best Regards,
Anastasiia Sergienko

Hello @AnastasiiaSergienko,
I cannot use the hive driver of version > 2.x with dbeaver. I get the same error:
'client_protocol' is unset! Struct:TOpenSessionReq(client_protocol:null, configuration:{set:hiveconf:hive.server2.thrift.resultset.default.fetch.size=1000, use:database=default})
I suppose that I should use the 1.1.0 deiver in any case.
I have already correctly registered the driver 1.1.0 in ExaOperations and it works, I can import from tables in Hive.
This is the adapter DDL:
CREATE OR REPLACE JAVA ADAPTER SCRIPT adapter.jdbc_adapter_hive AS
  %scriptclass com.exasol.adapter.RequestDispatcher;
  %jar /buckets/bucketfs1/bucket_adapter/virtualschema-jdbc-adapter-dist-3.1.0.jar;
  %jar /buckets/bucketfs1/bucket_adapter/hive-jdbc-1.1.0.jar;
/

The driver-file has the name hive-jdbc-1.1.0.jar in both EXAOperations and in the bucket.
The class name is org.apache.hive.jdbc.HiveDriver and is correctly configured in EXAOperations (imports work).
Best regards,
Nicola

Hello @AnastasiiaSergienko ,
I also discovered the following:
virtualschema-jdbc-adapter-dist-3.1.0.jar show more details in the error message, while virtual-schema-dist-5.0.4-bundle-4.0.3.jar just give back the generic message in my 2nd question: com.exasol.adapter.jdbc.RemoteMetadataReaderException: Unable to create Hive remote metadata reader, I discovered it with another adapter/connection to MS SQLSever.
Using 3.1.0:
com.exasol.adapter.AdapterException: Unable create Virtual Schema "myVirtualShema". Cause: "The TCP/IP connection to the host <IP_ADDRESS>, port 1433 has failed. Error: "Connection refused (Connection refused). Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".
Using 4.0.3:
com.exasol.adapter.jdbc.RemoteMetadataReaderException: Unable to create Hive remote metadata reader
So it is quite possible that the problem with the JDBC driver for Hive is always the same but version 4.0.3 just give back a generic error message.
The behaviour of version 3.1.0 of the adapter look much better when errors occur.
Best regards,
Nicola

Hi @nicolamarangoni ,
I'm glad to hear that you were able to connect to Hive via Virtual Schemas!
Thank you for reporting your experiments. I'll create a ticket and investigate the error handling in our latest version. It definitely looks better in 3.1.0 with all those details.
Please let us know if you have more questions.
Best Regards,
Anastasiia Sergienko

I'm closing this issue for now. Please, feel free to re-open it if some other questions appear.

Hi @AnastasiiaSergienko,
just to precise:
what I can do is to create a CONNECTION and then perform an IMPORT on tables in hive using the driver 1.1.x.
What I cannot do is to create a virtual schema. I still get "No suitable driver found".
I have the impression that the adapter simply doesn't work for Hive < 2.x.x.
So if you plan to test and eventually fix the adapter with Hive 1.1.x you can reopen the issue, otherwise you can leave it closed.
Best regards,
Nicola

Hello @nicolamarangoni ,
we have investigated the problem you reported. So, the driver you use has two problems so far, one of them can be solved and the other one actually can't, so we strongly recommend upgrading a Hive and use another driver if you want to use Hive with the Virtual Schemas.
The test was performed with:

Hive version: 1.1.0
Hive JDBC driver: jdbc-driver hive-jdbc-1.1.0-cdh5.16.2-standalone.jar

The problems are:

The driver does not register itself automatically, and it caused the problem you've reported. It's actually a bug in the driver. To fix it, you need to add a file META-INF/services/java.sql.Driver inside the jar archive. In this file, you need to register the main driver's class. In our case it is  org.apache.hive.jdbc.HiveDriver. This fixes the problem of the No suitable driver found exception.

But here we encounter the second issue:

The exception is
com.exasol.adapter.jdbc.RemoteMetadataReaderException: Unable to create schema adapter notes from remote schema. at       .... Caused by: java.sql.SQLException: Method not supported at org.apache.hive.jdbc.HiveDatabaseMetaData.storesLowerCaseIdentifiers(HiveDatabaseMetaData.java:820) at com.exasol.adapter.jdbc.AbstractRemoteMetadataReader.getSchemaAdapterNotes(AbstractRemoteMetadataReader.java:159) ... 13 more
This means that the driver doesn't support a method that the Virtual Schema uses to collect the metadata, so it's not possible to create a Hive dialect with this JDBC driver. We don't want to change this behavior, because the newer Hive drivers work fine here and it's not nice to hardcode the metadata only because of an old driver that contains bugs.

Please, always feel free to contact us if you have more questions.
Best Regards,
Anastasiia Sergienko

Dear @AnastasiiaSergienko ,
many thanks for your analysis.
The Hive-driver 2.x doesn't work with version 1.1.x on our server. Therefore we will try to create these virtual schemas after the upgrade to Hive 2.x or 3.x next year.
Best regards,
Nicola Marangoni


The banner ad refreshes in the backstack

MAX Plugin Version
2.4.6
Flutter Version
3.7.7
Device/Platform Info
iOS 16.1
Current Behavior
The banner ad refreshes in the backstack when you navigate from one screen to another. A banner ad is on the home page of my app. When I navigate to another page (for example, the settings page), spend some time there (2-3 minutes), and then return to the home page, the banner ad refreshes. I noticed that the banner ad refreshes.
Is this correct behavior?
If I don't see an ad, can I keep refreshing the ad or should I stop refreshing?
In my service, I'm using visibility_detector to perform stopAutoRefresh().
Expected Behavior
No response
How to Reproduce

load banner ad ( screen A )
navigate to screen B ( screen B )
wait
The ad on screen A is refreshed ( screen B )

Additional Info
No response

When the banner or MREC is not visible, you should stop autorefresh, resuming only when it is visible again.


How could you get FID on Fashion-mnist??

The image of Fashion is gray image which is 28x28x1, but the inception-v3 requires the channels of input image is 3. Thus you transform the size of images from Fashion? If so, how to do it in your code?
Thanks, please.

For channels, we tile: https://github.com/google/compare_gan/blob/560697ee213f91048c6b4231ab79fcdd9bf20381/compare_gan/src/eval_gan_lib.py#L786
For resolution, it's resized by tfgan library:
https://github.com/google/compare_gan/blob/560697ee213f91048c6b4231ab79fcdd9bf20381/compare_gan/src/fid_score.py#L151

Thanks for the details by you, so the gray scale image was transformed to rgb by repeating channels. and you mean that the Fashion images' resolution(28x28) were resized? I don't think it needs.

The input to the Inception is not of size 28x28, so it's needed to resized. How would you compute the embedding otherwise?

Inception doesn't limit the input size just acquires the input channel is three. I got the Inception Score without resize op on Fashion.
https://github.com/openai/improved-gan/blob/0a09faccb45088695228bbf50435ee71e94eb2ce/inception_score/model.py#L77
input_tensor = tf.placeholder(tf.float32, shape=[None, None, None, 3]
the FID is the wassertain distance of two Gaussian distribution estimated by the Inception pool3, the embedding dimensions will be consistent only if the input size is the same for real images and fake images. Moreover, if it resized, the data distribution will be distorted.
And I don't find the resize needed in the lib by authors:
https://github.com/bioinf-jku/TTUR
...Maybe I'm wrong based my shallow knowledge, thanks.

OpenAI and tf.gan code differ at which place they input the data to Inception (before or after preprocessing).  tf.gan uses input node 'Mul:0' while OpenAI uses input node 'ExpandDims:0'.
As far as I remember this explained the difference, because the resizing to 299x299 happens between those 2 nodes.


fix: change folder name

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


DOLFIN swig version is not the same as extension module swig version: '3.0.5' != '3.0.7' .

Hi,
first of all many thanks for all the work and effort you have put in this.
I encounter the following error when I try to run an example script called run_lshape_DL.py, using the Anaconda distribution and FEniCS on Ubuntu 14.04 LTS. The error happens also with any of the examples provided in the FEniCS tutorial webpage.
Traceback (most recent call last):
  File "run_lshape_DL.py", line 32, in <module>
    ue = Expression("sin(pi*x[0])*sin(pi*x[1])",degree=2)
  File "/home/dimitrios/anaconda/envs/fenics27/lib/python2.7/site-packages/dolfin/functions/expression.py", line 602, in __new__
    mpi_comm=mpi_comm)
  File "/home/dimitrios/anaconda/envs/fenics27/lib/python2.7/site-packages/dolfin/compilemodules/expressions.py", line 217, in compile_expressions
    mpi_comm=mpi_comm)
  File "/home/dimitrios/anaconda/envs/fenics27/lib/python2.7/site-packages/dolfin/compilemodules/expressions.py", line 145, in compile_expression_code
    mpi_comm=mpi_comm)
  File "/home/dimitrios/anaconda/envs/fenics27/lib/python2.7/site-packages/dolfin/compilemodules/jit.py", line 64, in mpi_jit
    return local_jit(*args, **kwargs)
  File "/home/dimitrios/anaconda/envs/fenics27/lib/python2.7/site-packages/dolfin/compilemodules/compilemodule.py", line 416, in compile_extension_module
    check_swig_version(compiled_module)
  File "/home/dimitrios/anaconda/envs/fenics27/lib/python2.7/site-packages/dolfin/compilemodules/compilemodule.py", line 249, in check_swig_version
    (cpp.__swigversion__, compiled_module.swigversion))
  File "/home/dimitrios/anaconda/envs/fenics27/lib/python2.7/site-packages/dolfin/cpp/common.py", line 2611, in dolfin_error
    return _common.dolfin_error(location, task, reason)

RuntimeError:
*** -------------------------------------------------------------------------
*** DOLFIN encountered an error. If you are not able to resolve this issue
*** using the information listed below, you can ask for help at
***
***<EMAIL_ADDRESS>***
*** Remember to include the error message listed below and, if possible,
*** include a *minimal* running example to reproduce the error.
***
*** -------------------------------------------------------------------------
*** Error:   Unable to compiling extension module.
*** Reason:  Incompatible swig versions detected. DOLFIN swig version is not the same as extension module swig version: '3.0.5' != '3.0.7' .
*** Where:   This error was encountered inside compilemodule.py.
*** Process: 0
***
*** DOLFIN version: 1.6.0
*** Git changeset:
*** -------------------------------------------------------------------------

Any advice is welcome!
Dimitris

Hi @dlouk, thanks for your nice comments :) You are totally right, I'm providing the wrong version of SWIG in my packages. I will try to fix that today, shouldn't take much time.

I just uploaded new versions of dolfin and ffc which in principle specify the right swig version. Could you please try updating and see if the issue is gone? If it is we can close the issue :)

Sorry for the late reply. I am on a short vacation, so I will check first thing on Wednesday. Thanks for the update!

It seems to be working fine now. I guess that you can close the issue now.

Perfect, thanks! :smile:


How to detect if user have stopped typing.

Like in SearchView there is this function onQueryTextSubmit(String query) can called when user submits the query. How to do similar thing using this search library ?

This is what I do:
mSearchView.setOnQueryChangeListener(new FloatingSearchView.OnQueryChangeListener() {
    @Override
    public void onSearchTextChanged(String oldQuery, String newQuery) {
        if(newQuery.length() >= MIN_QUERY_LENGTH){
            query = newQuery;
            mHandler.removeCallbacksAndMessages(null);
            mHandler.postDelayed(mSendQuery, QUERY_DELAY);
        }
    }
});

Basically I schedule a runnable for QUERY_DELAY ms in the future. If the user keeps typing, the following call to onSearchTextChanged will override this and schedule a new one. All of this until he finally stops and the last scheduled runnable is allowed to run with the most up to date query.

Do this
var handler = Handler()
 mSearchView.setOnQueryChangeListener { oldQuery, newQuery ->             if (newQuery.length < 3)                 mSearchView.clearSuggestions()             else {                 handler.removeCallbacksAndMessages(null)                 handler.postDelayed({                     mPresenter.loadSuggestions(newQuery)                 }, 500)             }         }


"PGPException: unknown public key algorithm encountered" at least say which one

org.bouncycastle.openpgp.PGPException: unknown public key algorithm encountered
at org.bouncycastle.openpgp.operator.jcajce.JcaPGPKeyConverter.getPublicKey(329)
Please

give some hint on what is visible about the not yet supported algorithm

support it

<EMAIL_ADDRESS>https://keys.openpgp.org/vks/v1/by-fingerprint/6A4A18D8A80D2C025C2F65A49FAD90D84CD488DC

I've added the algorithm number. Which version of BC is this? The keyring appears to contain EdDSA and ECDH keys - both of which we support.

Thanks  - will soon go from 1.64 to 1.71 ;)

Resolved.


Automate release process

Current situation
The release process requires following a recipe doc with several steps.
Impact
We need to fully follow stuff like renaming packages, etc. which can leads to errors and takes time.
Ideal future situation
Some of the steps should be automated so things become quicker and less error prone.

There's always things related to releases we need to automate or fix. We have a release label now.
So, I think we can close this old issue and use the release label.


purge opencv 2.4.9 since opencv3.1 is present

removing opencv2.4.9 to be able to pass verification test

next time, anything we can do to break up the massive package list?  Makes history unreadable.


Unknown file format when using normal XZ file

I'm trying to decompress data from the reddit comment archives in a stream, but it doesn't seem to work...
let file = fs.createReadStream(currentFile, {flags: "r", encoding: "utf-8"});
stream = lzma.createDecompressor();
file.pipe(stream);

I checked the file, and it downloaded properly, and I can also extract it with unxz file and xz -d file

@Kitsumi Using encoding: "utf-8" makes Node.js read the file as UTF-8 text, which is not what you want when reading a binary file. Just leave out the encoding: bit and things should work fine. :)

Oof, you're right, I didn't see that at first! I guess doing code super late at night isn't a good idea.
Thanks so much.


SAK-40361: Assignments > visually distinguish sections of the students view of returned submission

https://jira.sakaiproject.org/browse/SAK-40361
The current state of the student's view grade/submission/feedback UI can become cluttered if all possible sections are present (assignment instructions, assignment attachments, original submission text, original submission attachments, instructor feedback, instructor feedback attachments).
This PR visually distinguishes these sections by giving each "panel" a border. See before and after screenshots on the JIRA.

Yeah this does aid in organizing those sections on the page. In bootstrap 4 they have a nice set of utilities for borders to bad we couldn't use those vs creating our own!!!