Checked arithmetic and unit test

@akoptelov
closing this, I rebase my fixes on this here: https://github.com/tezedge/tezedge/pull/643


[SIL Utils] Move IndexTrieNode into its own header in Utils. NFC.

Move IndexTrieNode from DeadObjectElimination into its own header. I plan to
use this data structure when diagnosing static violations of exclusive access.

\cc @atrick

@swift-ci please smoke test and merge

@swift-ci Please smoke test and merge


Changing dark mode from the settings doesn't change the status bar color

when toggling dark mode settings in iOS and when theme mode is set to thememode.settings the  background color is changing according to dark and light mode  but status bar color doesn't change . only when we tap settings button that calls setthememode is when the status bar color is changing . is there a way to dynamically change status bar when we toggle dark mode from settings

mmmmmmmm, i was wondering when this will come up. I will most likely have to re-apply the appropriate theme when the application gets back into the foreground. It's not implemented yet but I'll update this issue and i'll work on it.

I've actually done a pr so if you can look at it that would be great !  also if you don't find it the best way i please explain me the reason so I can improve my future prs

Thanks for the PR. I forgot to close this afterwards. It's working well :)


chore: remove obsolete routes

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

GitHub release
v3.9.0

Your semantic-release bot :package::rocket:


backend: add docs for backend

the backend is facing errors while starting the project in local

Follow the readme for backend setup, you need to configure your environmental variables and also connect with your own database.


[3.x] Add selection getter methods to LineEdit

This is a 3.x backport of #53000 by @Chaosus, who I've made a co-author of the commit.

Thanks!


usability: duplicate repo show "connection error" error message

when adding duplicate repo which already have an entry in the argo source control, it gave "connection error"  message which is confusing. I think the more meaningful error should be "repo already exist" instead of connection error.

This is argo v1


GraphQL Support

@mnovozhylov
Hi! I commented 3 weeks ago on issue #8 regarding REST API Sunset.
The question is will this package support new GraphQL methods? Because it's more convenient to use the package instead of writing anything by yourself.
The second reason is that I have some problems with running vanilla GraphQL queries. For example, when running jobPosting, I got the next error:  "message": "'openingsV2DS',  'getOpening',  'Opening not found for uid='~some_string''".
How the jobPostingID should look like? My guess that it must be something like this ~some_string, but maybe I am wrong, because there is nothing described in the documentation yet.
Also, do you plan to release functionality to duplicate REST search for jobs endpoint (https://developers.upwork.com/?lang=python#jobs_search-for-jobs)?
Thank you in advance!

Hi @Kick28 ,

The library already supports GraphQL requests. See the example - https://github.com/upwork/python-upwork-oauth2/blob/master/example/myapp.py#L74-L86
The questions, not related to the library, should be addressed to Support Team

My bad, didn't check everything well. Thank you for the answer.


Fix item edit bug

This PR updates the SDK core to a newer version which contained a bug that would cause unsupported item fields to be deleted when items were edited via the SDK.

Functionally tested and it works well.


Add GDAL, versions 1.10.1 and 1.11.1_3

GDAL (http://www.gdal.org/) is a library package, and some of the projects that depend on it are version-sensitive, so being able to explicitly install a specific version should be helpful to others.

Per lack of reply to Jack's comments, closing. Feel free to reopen a new PR if you're still interested.

Somehow I missed the original notifications, I am definitely still interested. I have created a new PR #675 that addresses the comments.
This is my first foray into homebrew-ing, thanks for your patience.


Documentation

Describe the bug
Documentation - where is the backup file saved to?

It gets uploaded to the root of your google drive upon creation of a backup. If you're asking this question because you don't see them them outra probably because this plugin only works in octoprint 1.5.0 or newer, which isn't released yet.


write base class for other status page providers

https://cachethq.io/
https://www.pingdom.com/
http://www.stashboard.org/
https://github.com/darkpixel/statuspage
https://statuskit.com/
https://hund.io/
https://statushub.io/
https://www.exoscale.ch/runstatus/

This would be nice to have, I wrote a small connector for cachethq since we're using it, but ATM is only a PoC, but it is working so far:

I'd be glad to contribute.

@ruiztulio very cool, It's certainly very welcome


Retry PR 76. Use real SSL cert instead of self signed one.

@ivan-shaporov this PR looks like it includes really old commits. Could you please create a new topic branch for every change and PR? I am guessing that you are re-using the same branch over and over, which is a bad practice.


why cant use "

Version
Microsoft Windows [版本 10.0.22000.556]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
5.10.16
Distro Version
Ubuntu
Other Software
No response
Repro Steps
i want to install unzip
put into command "apt install unzip"
it shows
"
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package unzip
"
and
I want use command " apt-get update"
it return
"Err:1 https://mirrors.ustc.edu.cn/ubuntu focal InRelease
Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out
Err:2 https://mirrors.ustc.edu.cn/ubuntu focal-updates InRelease
Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable)
Err:3 https://mirrors.ustc.edu.cn/ubuntu focal-backports InRelease
Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable)
Err:4 https://mirrors.ustc.edu.cn/ubuntu focal-security InRelease
Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable)
Reading package lists... Done
W: Failed to fetch https://mirrors.ustc.edu.cn/ubuntu/dists/focal/InRelease  Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out
W: Failed to fetch https://mirrors.ustc.edu.cn/ubuntu/dists/focal-updates/InRelease  Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable)
W: Failed to fetch https://mirrors.ustc.edu.cn/ubuntu/dists/focal-backports/InRelease  Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable)
W: Failed to fetch https://mirrors.ustc.edu.cn/ubuntu/dists/focal-security/InRelease  Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable)
W: Some index files failed to download. They have been ignored, or old ones used instead."
It seems I can not install any app in ubuntu
Expected Behavior
i want to  install app in this ubuntu
Actual Behavior
it return
"Err:1 https://mirrors.ustc.edu.cn/ubuntu focal InRelease
Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out
Err:2 https://mirrors.ustc.edu.cn/ubuntu focal-updates InRelease
Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable)
Err:3 https://mirrors.ustc.edu.cn/ubuntu focal-backports InRelease
Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable)
Err:4 https://mirrors.ustc.edu.cn/ubuntu focal-security InRelease
Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable)
Reading package lists... Done
W: Failed to fetch https://mirrors.ustc.edu.cn/ubuntu/dists/focal/InRelease  Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out Could not connect to mirrors.ustc.edu.cn:443 (<IP_ADDRESS>), connection timed out
W: Failed to fetch https://mirrors.ustc.edu.cn/ubuntu/dists/focal-updates/InRelease  Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable)
W: Failed to fetch https://mirrors.ustc.edu.cn/ubuntu/dists/focal-backports/InRelease  Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable)
W: Failed to fetch https://mirrors.ustc.edu.cn/ubuntu/dists/focal-security/InRelease  Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::110). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:95::94). - connect (101: Network is unreachable) Cannot initiate the connection to mirrors.ustc.edu.cn:443 (2001:da8:d800:931::95). - connect (101: Network is unreachable)
W: Some index files failed to download. They have been ignored, or old ones used instead."
Diagnostic Logs
No response

It seems that your network connection is poor. Have you tried ping to mirrors.ustc.edu.cn or other domain names in China like baidu.com?


Extension for vs code

This issue is about requirements for vs code extension.

Create flutter-tizen project.
Debug/Run tizen emulator

3.Flutter widget inspector
4.Performance view
5.CPU profiler view
6.Memory view
7.Network View
8.Logging view
9.app size tool

There are several ways to implement the VS Code extension for flutter-tizen:

Create a fork of the official Flutter extension (https://github.com/Dart-Code/Dart-Code)
Contribute to the official extension (by somehow integrating flutter-tizen with the extension as an external plugin)
Create from scratch

Each has its pros and cons, and whichever way you choose, implementing and maintaining the extension will be time-consuming and difficult. More importantly, how much benifit can we earn from implementing such an extension for flutter-tizen? flutter-tizen has very limited number of users, and the number of users who want to use advanced debugging features when developing Tizen apps should be even lower. Please note that flutter-tizen already supports DevTools which comes with a source-level debugger although it's not as usable as a standalone extension for IDEs.

The development of a dedicated extension for Tizen has been paused after discussion with @xuelian-bai, because the VS Code debugger support has already been added by https://github.com/flutter-tizen/flutter-tizen/pull/196 (See Debugging apps for usage) and the developer experience would not be greatly improved by offering the extension. The decision may be changed if there is high demand from users in the future.


feat(device): add display of tags, entry of tags and device details

Codecov Report

Merging #89 (1ad7de3) into master (c4982df) will decrease coverage by 0.01%.
The diff coverage is 30.95%.

@@            Coverage Diff             @@
##           master      #89      +/-   ##
==========================================
- Coverage   42.32%   42.30%   -0.02%
==========================================
  Files          28       28
  Lines         612      650      +38
  Branches       56       59       +3
==========================================
+ Hits          259      275      +16
- Misses        338      360      +22
  Partials       15       15

Impacted Files
Coverage Δ

src/app/configs/configs.component.ts
45.83% <0.00%> (-2.00%)
:arrow_down:

...p/domains/domain-detail/domain-detail.component.ts
36.58% <0.00%> (-0.92%)
:arrow_down:

src/app/devices/devices.component.ts
36.00% <11.11%> (-16.95%)
:arrow_down:

src/app/devices/devices.service.ts
11.53% <14.28%> (+1.01%)
:arrow_up:

...rofiles/profile-detail/profile-detail.component.ts
24.73% <20.00%> (-0.91%)
:arrow_down:

...p/devices/device-detail/device-detail.component.ts
76.92% <88.88%> (+22.37%)
: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 c4982df...1ad7de3. Read the comment docs.


Add LDBC SNB Interactive queries

This PR contains a few queries from the LDBC SNB Interactive workload. While this is primarily an OLTP workload, implementing its queries can still be beneficial for testing features in DuckDB, and a DuckDB implementation can be useful for validating the SQL reference implementation of the Interactive workload.
This PR contains all 'short' queries (1-7) and the following 'complex' queries: 2 3 5 6 7 8 9 10 11 12.
The reasons for omitting the rest of the queries are the following:

1: needs array
~4: uses not exists (probably possible to rewrite to an antijoin)~
13: uses not exists, needs recursive views, runs into an infinite loop
14: needs array

To elaborate on Q13, other than missing clauses, one of its subqueries runs into an infinite loop (presumably caused by the graph having cycles):
WITH RECURSIVE search_graph(link, depth) AS (
		SELECT<PHONE_NUMBER>4856, 0 -- the big number is the start person Id
		UNION ALL
		(SELECT distinct k_person2id, x.depth+1
		FROM knows, search_graph x
		WHERE x.link = k_person1id)
)
select * from search_graph

Interestingly, the same code terminates under Postgres (v12.4):
      link      | depth
----------------+-------
<PHONE_NUMBER>4856 |     0
(1 row)

Do you have any advice on how to stop infinite loops caused by recursive queries? (Checked PR #404 but it doesn't seem conclusive regarding this.)

Thanks for the PR! I actually already ported some LDBC queries, but running on an empty database (see here). For testing purposes, it would be nice if there were unittests with data as well. We could either add tests using a small subset of the data, or add something similar to the sqllogictests which gets downloaded separately using make sqlite (which is hosted in a separate repo, here). That way we can get notified if something breaks in the CI.
For benchmarking purposes it might be nice to actually add the queries to the benchmark runner (see e.g. the strftime benchmark file we have).
As for the non-working queries:

1: needs array
14: needs array

We do support arrays (we call them lists), but the syntax needs to be extended to match the syntax of PostgreSQL. I noticed this before when running the LDBC queries as well. The main offender seems to be that we don't support the syntax ARRAY[]::bigint[] for creating empty arrays, which is used in the benchmark. This is primarily a parser/transformer issue, and shouldn't require big changes in the engine. We do support array_agg and string_to_array, which seems to be the other functions that are used.

4: uses not exists (probably possible to rewrite to an antijoin)

NOT EXISTS is supported by DuckDB and should work. In fact, it should be rewritten to an anti-join internally. Could you share the exact error you get here?

13: uses not exists, needs recursive views, runs into an infinite loop

The infinite loop smells like a bug to me. As far as I know Postgres doesn't have any special infinite loop handling either (i.e. if it's actually an infinite loop, Postgres would not terminate either). This needs some more investigation.
Thanks again for the effort!

My mistake, Q4 indeed works. I just pushed it.

Great!

Now I'm working to adapt the SNB update (=insert) queries as they are defined over the schema used in LDBC which used a common message table that contained both post and comment nodes. I'll definitely need those for the completeness of the LDBC benchmark but I'm not sure whether they belong to this repository. WDYT?

I assume these are relatively large (>5MB), right? In that case I would prefer not to add them to the main repository to avoid unnecessary bloat from test data. For TPC-H/TPC-DS we have added the data generators directly to the project. This is one possibility. Another is to create a separate repo that can be cloned during testing of the queries like we do for the SQLite Logic Tests (as they contain around 1.2GB of test data).

I assume these are relatively large (>5MB), right?
With all the data, sure. But the queries themselves with a few example parameters are just a couple of kB.

@Mytherin I turned the infinite loop problem to a separate issue #1088. The queries in this PR work as intended, so I think this PR is good to go.

Thanks again for the PR and thanks for filing the issue. Will merge this one then!


Add option to reduce disk usage

Summary:
The tensilelt disk usage can reach up to hundreds of GBs in some cases. This work adds new behavior that removes temporary build artifacts and generated code during the build process to keep the disk space high-water mark down. The old behavior can be enabled by using the new option --keep-build-tmp.
Outcomes:
tensilelt hard disk usage is reduced by as much as 80%.
Notable changes:
--keep-build-tmp option was added.
Testing and Environment:

./install -dc -a gfx942
./build/release/clients/staging/hipblaslt-test

[==========] 35356 tests from 13 test suites ran. (1735740 ms total)
[  PASSED  ] 35356 tests.
hipBLASLt version: 800

@jichangjichang let me know if there is any additional testing required before I remove noCI label

@jichangjichang let me know if there is any additional testing required before I remove noCI label

Have you verified that "./install -dc -a gfx942 --keep-build-tmp" can keep all the temp files?

@jichangjichang let me know if there is any additional testing required before I remove noCI label

Have you verified that "./install -dc -a gfx942 --keep-build-tmp" can keep all the temp files?

Yes tested ./install -dc -a gfx942 --keep-build-tmp on the most recent commit.

@ellosel Why did you still use "Draft" for this PR?

If any CI is not avaliable, you need to manually test CI on that local machine.
./hipblaslt-test under build/release/clients/staging
Run "tox -v --workdir /tmp/.tensile-tox -e py3 -- Tensile/Tests -m common" under tensilelite folder.


KAFKA-6747 Check whether there is in-flight transaction before aborting transaction

As Frederic reported on mailing list under the subject "kafka-streams Invalid transition attempted from state READY to state ABORTING_TRANSACTION", producer#abortTransaction should only be called when transactionInFlight is true.
Committer Checklist (excluded from commit message)

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

Call for review @bbejeck @vvcephei

@tedyu Thanks for the PR, the fix looks good to me. Could we add a unit test to expose this issue and illustrate that it is fixed in this PR? For example:

create a new StreamTask (beginTransaction not called yet).
call task.close() immediately after the construction; without the fix it should be reproducing the error trace, and with the fix it should be fine.

Should we cherry-pick this to 1.1 branch?

Also cherry-picked to 1.1 branch

Is there a workaround for this until 1.1.1 is released?

Also cherry-picked to 1.0 and 0.11.0


can't add the Prometheus metrics for kubernetes Provider

Hi, I'm running manageiq in my local server and im using the latest version of manageiq morphy.
Recently, i add my container provider Kubernetes and i successfullly added. But, when im trying to add monitoring prometheus i got an ssl error and i selected ssl without validation as security protocol.
I exposed prometheus in nodeport. Also i shared screenshot below.

Hi @remo233, when you say you're running this from your local server do you mean you're running it in "dev mode" and not using an appliance or podified?
Can you try running the following: openssl s_client -connect <IP_ADDRESS>:30199
A lot of times "wrong version number" means the server doesn't actually use SSL, for example:
$ openssl s_client -connect localhost:3000
CONNECTED(00000003)
139912628688256:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331:

Hi, @agrare Thanks for your reply. I Solved the error by configuring Prometheus in ingress. And I'm using appliance manageiq not the dev mode.
Now, I'm facing another issue in the self-service portal. when I provision a VM in manageiq. I cant see metrics there.
Also, I tried with the OpenStack cloud provider and in OpenStack, i enabled ceilometer and shared the screenshot below.

Hi @remo233 thanks for following-up with the prometheus fix,  self-service metrics sounds like a separate issue can you open another issue for that?  Thanks.


Concept Creation: Enhancing Casper Blockchain Explorer with DeFi Insights

Reward Size in USD
500 USD
Reward category
DApps
Description
The DeFi landscape is currently evolving, and TVL (Total Value Locked) is a valuable indicator of the level of activity occurring on the blockchain within the context of the DeFi ecosystem. The Casper Mainnet Blockchain is open source, and various blockchain explorers have made some of its data accessible. This DevReward project aims to create a data tool that provides a comprehensive overview of the blockchain's daily activity related to TVL and DEX (Decentralized Exchange) activity. The primary objective is to gain a better understanding of TVL on the blockchain, active DEXs, and the corresponding liquidity pools.
Acceptance Criteria
•	The required data must be sourced from the Mainnet of the Casper Blockchain.
•	This Developer Reward is focused on Teams with  Casper Blockchain Explorer, which, in a second step, would be able to
include the  concept directly into their explorer if all acceptance criteria are met.
•	Prepare a robust concept and mock-up for indicating TVL, active DEXs and Bridges, and the included liquidity pools. This
mock-up should have the following required MVPs that can be assessed:
o	A comprehensive overview of all DEXs and bridges using the Casper Blockchain.
o	A comprehensive overview of all available liquidity pools that are included.
o	A total overview of the entire existing TVL on the Casper blockchain and the daily changes in these volumes.
o	The data should be available as downloadable .csv files.
o	Make suggestions for 5-10 KPIs that should be available and explain the added value they would bring.
o	Data must be available for download in .csv format and easily accessible. It should be available for at least the year 2023
and, preferably, for the entire blockchain history up to the Genesis block if applicable.
•	Provide a detailed description of how the different sections were categorized, the calculations behind them, the data
processing methods employed, and make the source code accessible.
•	As soon as this data and MVP are ready, schedule a meeting with the corresponding deployer of the concept and we will
request a demo of the MVP.
•	If all acceptance criteria are met, please provide a time schedule for implementing the solution and an implementation
schedule.


Integration Flow strange behaviour

Hello,
I have a problem with an integration flow.
return IntegrationFlows.from(Amqp.inboundGateway(simpleListnerContainer))
           .transform(Transformers.fromJson(ClassToTransform.class))
           .handle(service)
           .transform(Transformers.toJson())
           .log()
           .get();

Because of that .log() this integration flow fails with Dispatcher has no subscribers:
Caused by: org.springframework.integration.MessageDispatchingException: Dispatcher has no subscribers
	at org.springframework.integration.dispatcher.UnicastingDispatcher.doDispatch(UnicastingDispatcher.java:154)
	at org.springframework.integration.dispatcher.UnicastingDispatcher.dispatch(UnicastingDispatcher.java:121)
	at org.springframework.integration.channel.AbstractSubscribableChannel.doSend(AbstractSubscribableChannel.java:89)
	... 79 common frames omitted

If I comment that .log() line, everything works fine.
Can someone help me understand why is this?
Thank you

That has been fixed in the Spring Integration 5.0 recently: https://jira.spring.io/browse/INT-4210.
And see explanation and solution in the StackOverflow: https://stackoverflow.com/questions/41695292/httprequestexecutingmessagehandler-no-output-channel-or-replychannel-header-ava/41699176#41699176
Closed as fixed.

Thank you so much for the fast reply :)


Create releases on each build

It might also nice to have releases so that folks can just download and start working with them. A release could be drafted through Github with compiled tarballs

Changed topic to "create releases on each build" because the build actually is stable, we just don't preserve the build artifacts.

Closing as duplicate of  #116


Add test for #205

Codecov Report

Merging #419 (8485253) into main (5416d00) will decrease coverage by 0.21%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main     #419      +/-   ##
==========================================
- Coverage   76.33%   76.11%   -0.22%
==========================================
  Files          17       17
  Lines        4226     4229       +3
==========================================
- Hits         3226     3219       -7
- Misses       1000     1010      +10

Impacted Files
Coverage Δ

src/compiler.jl
74.74% <50.00%> (-0.05%)
:arrow_down:

src/compiler/orcv2.jl
61.90% <0.00%> (-10.48%)
:arrow_down:

src/Enzyme.jl
87.94% <0.00%> (+1.06%)
:arrow_up:

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


empty Json[] fields turn to null (instead of an empty []) when accessed through a join using the new relationJoins feature

Bug description
Hey guys, I found a pretty concrete bug that unfortunately blocks our adoption of the relational joins.
Basically, if you have a JSON[] field on a model, and you query that model directly, it resolves as an empty array or a populated array ( as it should). However, when you query that model through a join the empty Json[] fields resolve to null :O This breaks the typings, and the projects client side, because we often try to read .length of the presumed empty arrays.
Even more concrete example:
model Profile {
	id: Int
	userId: String
	links: Json[]
}

model User {
	id: String
	profile: Profile
}

Querying profile alone resolves correctly with links as [].
Querying User joined with Profile resolves with links to NULL (again, assuming they have not been populated).
Changing the relationLoadStrategy to "query" resolves the issue for now.
What do you guys think? Easy fix?
How to reproduce

Have two models that are related to each other
The second one has a Json[] field
Try to access that field through a join from the first model

Expected behavior
Empty Json[] fields should return an empty [] like they used to
Prisma information

model User {
    id               String    @id @default(cuid())
    name         String // needed for next auth (I think)
    email         String    @unique

    profile            Profile?
}

model Profile {
    id        Int      @id @default(autoincrement())
    createdAt DateTime @default(now())
    updatedAt DateTime @default(now()) @updatedAt

    featuredLinks Json[] // {title: string, description: string, url: string, imageUrl: string}[]

    userId String @unique
    user   User   @relation(fields: [userId], references: [id], onDelete: Cascade)

}

In a React Server Component, but also reproduced this in a regular ts file with tsx and node

  let userWithProfile = await prisma.user.findUnique({
    where: {
      id: id,
    },
    include: {
profile: true
},
  });

Environment & setup

OS: Mac locally and presumably linux (Vercel cloud functions)
Database: PostgreSQL(Supabase)
Node.js version: 18.18 locally

Prisma Version
^5.8.0 (as in anything above 5.7.1, including 5.9)

@janpio @Weakky Any updates on this? Looks like the PR passes the checks :)
Until this works we are unable to use relation joins, and we'd love to start using those as soon as possible :)

PR actually has tests failing for CockroachDB, but we will further look into this soon to make the preview feature more usable. Sorry you have to wait a bit longer - but effectively that is what the preview phase is for of course. Thanks for reporting and caring.


Schedule call with Water Board

Kim intro'd us to Eric Zuniga from Division of Drinking Water. Goal is to schedule a meeting with them to discuss potential future MDSA work in 2nd or 3rd week of November.

Done, meeting scheduled for 11/17.


Accelerated networking for Windows

What this PR does / why we need it: Adds accelerated networking support for Windows nodes. The reason for using a separate var for Windows is that using the same variable as Linux would break back compat because the var could have previously set to true even though the property wasn't applied on windows nodes and so it is not an accurate representation of the current state of the cluster.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #3678
Special notes for your reviewer:
If applicable:

[x] documentation
[ ] unit tests
[x] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

back compat: https://jenkins.azure-containers.io/view/acs-engine ad-hoc/job/k8s-upgrade/151/console

/hold   failed back compat

new back compat: https://jenkins.azure-containers.io/view/acs-engine ad-hoc/job/k8s-upgrade/155/console

/hold cancel

@PatrickLang this is ready for review

@dineshgovindasamy @daschott - any concerns with allowing accelerated networking for Kubernetes nodes? It's off by default but customers can opt-in on compatible VM SKUs

@jmesser81 any concerns with this?

@PatrickLang as is the PR is actually enabling it by default (same as for Linux) for supported SKUs. I will change it to disabled by default for now since it seems to be what we want.

@daschott @CecileRobertMichon - no concerns with having it be as an opt-in. I don't think we've tested this but there isn't any reason why it shouldn't just work.

/lgtm

@CecileRobertMichon is this still possible? Having accelerated networking enabled for windows node?

@romina2001 this issue has the latest status on this: https://github.com/Azure/aks-engine/issues/2281


The virtualized scroll prop was causing the elements in the grid view to show under the appheader as it was scrolling up the page

Current dependencies on/for this PR:

main

PR #12   👈

This comment was auto-generated by Graphite.


Series.nonzero() method not listed in API reference

I cannot find the Series.nonzeros() method in the API Reference documentation-page for pandas <= 0.18.1.

http://pandas.pydata.org/pandas-docs/version/0.18.0/generated/pandas.Series.nonzero.html?highlight=nonzero#pandas.Series.nonzero
you have to look at a specific version. Note this is only a wrapper around a numpy rountine.

Maybe the inline link was not that clear.
I'm not referring to the documentation. I can indeed find this page in any pandas-version.
I'm referring to this page listing ALL functions of pandas (possibly even numpy wrappers): http://pandas.pydata.org/pandas-docs/stable/api.html#series

see listing here of the open issues to document things in the API.rst. This was/is pretty manual. If someone wants to step up and actually add these, great. Even better would be an automated scripts to fail builds that has functions not listed.


Moved the word 'the' so the sentence makes sense.

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[X] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-343


Wrong encoder used in resnet101dilated config file

In config/ade20k-resnet101dilated-ppm_deepsup.yaml, the part define the encoder is
MODEL:
  arch_encoder: "resnet50dilated"
  arch_decoder: "ppm_deepsup"
  fc_dim: 2048

Shouldn't it be resnet101dilated? Thanks.

I wonder if the result on the readme is incorrect

Fixed. The results should be correct. Thanks for finding this typo.


Compatibility with micro:bit v2

Hi @DFRobot,
As you might have seen from microsoft/pxt-microbit#3506 this extension is currently not compiling against the latest version of Micro:bit CODAL. This means it will not work with micro:bit V2.
Software for micro:bit V2 boards is built using CODAL rather than the DAL, and no longer includes the mbed layer. We’ve implemented the most frequently used mbed classes to support easy porting of existing extensions, but there may still be corner cases with this compatibility layer.
As your extension is currently not building, it will be disabled for micro:bit V2. People attempting to use your extension with a micro:bit V2 board will get error 929. This extension will only be re-enabled on micro:bit V2 once it is fixed.
There are details on how to ensure extensions work on both version of the micro:bit here (lancaster-university/codal-microbit-v2#31).
Looking at your extension source I believe that your extension falls under this category:

Use of mbed APIs that are not included in the compatibility layer, or microbit-dal APIs that need different constructors

/home/build/prjclone/pxtapp/NaturalScience/ds18b20.cpp:33:30: fatal error: TimedInterruptIn.h: No such file or directory

@tangjie133 - Are you able to look at this issue?

@tangjie133 - Are you able to look at this issue?

@tangjie133 is this extension compatible with micro:bit V2?
Looking at the C++ code in https://github.com/DFRobot/pxt-DFRobot-NaturalScience/blob/master/ds18b20.cpp there is conditional code for V1 and V2, so it does look like it has been updated to run in V2. Could you confirm if that is the case?
Currently it is marked as V1-only inside MakeCode:
https://github.com/microsoft/pxt-microbit/blob/v7.0.13/targetconfig.json#L268
So a user loading this extension on a micro:bit V2 would see only see the error code 927 (programme not compatible) and the programme won't run. If you can confirm the extension works for V2 we can update MakeCode so that it loads correctly in V2.


Mongodb configuration file generation

The helper for the mongodb configuration template fails to delete the null values and update the hash, as the object being received by it is of type ImmuatableMash.

@vachanda could you please share Chef client/server version and OS details? would be great to have stack trace and chef client run error message.

Hey sorry, I forgot to mention this in my earlier comment. The Chef version is 11.10 and OS is Ubuntu 14.04 LTS. The stack trace is not available as it is been removed when the ec2 machine was terminated. It basically says "Cannot set the value of a node.default['key'] = value, use set method to do it". This is because in the helper you are trying to remove the keys and store it in the same object. This is not possible since the object is immutable.

@vachanda Thank you for heads up. I'll take a look.

Close via https://github.com/sunggun-yu/chef-mongodb3/pull/22.

Thank you!


Install: fails to install TIGRE

Using the command
conda create --name cil -c conda-forge -c intel -c ccpi cil=23.0.1 astra-toolbox tigre ccpi-regulariser tomophantom "ipywidgets<8"

suggested in the README results in conflict. Mamba reports:
Encountered problems while solving:
  - package tigre-2.4-np121py39h0a26027_0 requires cudatoolkit >=10.2,<10.3.0a0, but none of the providers can be installed

I think this is a problem of my machine, where the driver is for cuda 10.1.


HomeWorks H4P5-CE

Does your plugin work with HomeWorks H4P5-CE Processor?

I have no idea. This plugin users telnet to talk to the processor. If your processor uses telnet my guess is that it will. Newer processors use a different way of talking with accessories and peripherals.


environment variables not being set

In my nx expo project, the process.env object shows the following
{
"NODE_ENV": "development",
}
None of the variables in my .env file are being included.

https://docs.expo.dev/guides/environment-variables/

I'm also facing this problem. I've read docs of @leggomuhgreggo , but I don't know how to configure this in theproject.json.
It seems that I can't add env variables to the@nrwl/expo:startexecutor. Any help/ideas?

@BlumDev92 Here's how I fixed the problem. I changed my app.json to app.config.js and added the following code.
module.exports = {
  expo: {
    //...
    extra: {
      env: getNXVariables(),
    },
  },
};

/**
 * Nx isn't passing env variables to expo so we need to add them to the extra section of the config
 * then manually set process.env when our app starts
 *
 */
function getNXVariables() {
  let result = {};
  for (const key in process.env) {
    if (key.startsWith('NX_')) {
      result[key] = process.env[key];
    }
  }
  return result;
}

Then run expo install expo-constants and add the following code to your javascript before any other code is executed
import Constants from 'expo-constants';

(function setEnvironmentVariables() {
  Object.assign(process.env, Constants.manifest?.extra?.env);
})();

Now you can use process.env.NX_ANYTHING to your heart's delight!


Update Budget Record loading state

Include the update loading in the ProjectBudget.tsx loading state

It's two pieces, the budget line and the total.  When I was testing the update was really quick, do you expect his to be a big enough issue to warrant a specific loading state?

It's two pieces, the budget line and the total.

loading also goes to the table which I think makes the whole thing loading. Maybe I'm wrong though I haven't checked out the code.

When I was testing the update was really quick, do you expect his to be a big enough issue to warrant a specific loading state?

Yeah just because the API is fast on your machine doesn't mean that's always going to be the case in every situation.

Changed to only load the row and the total.  I don't know how to add more rows to the table so haven't been able to test that yet.

There's a react warning that was already there
Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in the componentWillUnmount method.
    in MTableEditCell (created by WithTheme(MTableEditCell))
    in WithTheme(MTableEditCell) (created by MTableBodyRow)

I tried to do a little debug bug couldn't solve it.  Not sure if either anyone else have ideas or it's just part of the MUI table

Not sure if either anyone else have ideas or it's just part of the MUI table

This is a bug in material-table; I have an issue open for it


feat(unpivot): add quote identifier parameter to handle case sensitive columns

resolves #216
This is a:

[ ] documentation update
[ ] bug fix with no breaking changes
[x] new functionality
[ ] a breaking change

All pull requests from community contributors should target the main branch (default).
Description & motivation
Added quote_identifiers parameter to unpivot to handle case-sensitive column names. This fixes #216
Checklist

[x] This code is associated with an Issue which has been triaged and accepted for development.
[x] I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)

[ ] BigQuery
[x] Postgres
[ ] Redshift
[ ] Snowflake

[x] I followed guidelines to ensure that my changes will work on "non-core" adapters by:

[x] dispatching any new macro(s) so non-core adapters can also use them (e.g. the star() source)
[x] using the limit_zero() macro in place of the literal string: limit 0
[x] using dbt.type_* macros instead of explicit datatypes (e.g. dbt.type_timestamp() instead of TIMESTAMP

[x] I have updated the README.md (if applicable)
[x] I have added tests & descriptions to my models (and macros if applicable)
[x] I have added an entry to CHANGELOG.md

CircleCI Jobs for BigQuery, Redshift and Snowflake fail due to database connection errors. This needs to be fixed in the Build server configuration.

rebased to current main and resolved merge conflicts in CHANGELOG.md

Anything missing to get this merged?

ping

Any upates on this? I have encountered a similar scenario where i use date yyyy-mm-dd as the format, it end up evaluating  the date string into an arithmic operation. Quoting seems quite useful here.

Hi @joellabes and @error418 what are we waiting on for this to be merged ?
I have faced a similar issue

@error418 and @joellabes  i have tested the changes for bigquery warehouse also and its work fine.

hey @error418 @joellabes, facing a similar issue and need to have this merged. can you merge this asap please?

@Shadowsong27 @Ishankoradia @Abhishek-N at the moment I am waiting for a review by @joellabes (or any maintainer of dbt-utils).
@Ishankoradia thank you for testing the changes for BigQuery
Should there be any remaining issues with this PR I am happy to provide the necessary fixes.

bump

What's missing here? I need this fix to be deployed. Thanks.

What's missing here? I need this fix to be deployed. Thanks.

@joellabes could you please provide some information about the status of this pull request?
This is stalling for a while now without any feedback from the maintainers, which sadly becomes a bit frustrating.
Thanks

Hi all,
This is our highest priority PR to review right now, and I'll be diving deeper into it this week.
After taking an initial look, the heart of the implementation looks good.
The main thing I'd like to follow-up on prior to approving + merging is the testing:

It looks like there is special configuration in the CI tests so that Snowflake and Redshift pass

So I'd like to:

Make sure that the test is running for Redshift.
Align how Snowflake is handled across similar tests. i.e., either standardize on prior art or standardize on the adapter.quote() approach in this PR

@error418 I think I figured out the root cause of the Redshift test failures in CI.
As you noted, the default behavior in Redshift is to lowercase all column names even if a table is created with quoted mixed-case column names.
It looks like the solution is to set enable_case_sensitive_identifier to true. I'm going to try  adding that configuration to the CI cluster or workgroup's parameter group and see if that allows this test to pass for Redshift.


nfc plugin does not retain the last view app

Hi, i have installed the pluggin but I have a problem. it works correctly reading mifare tag when my phonegap app is showing but if I close it and I open it again does not keep the last view and my app login page appears.
any ideas?
OS Android 4.1.2, Sony Xperia
Thank you for your prompt reply.

I don't think this is related to the plugin, what do you mean by the
"login" page?
I believe you might be asking about restore the state of your application
which is unrelated to this plugin.
Allan
On Monday, June 1, 2015, pcalderoncity<EMAIL_ADDRESS>wrote:

Hi, i have installed the pluggin but I have a problem. it works correctly
when my phonegap app is showing but if I close it and I open it again does
not keep the last view and the login page appears.
any ideas?
Thank you for your prompt reply.
—
Reply to this email directly or view it on GitHub
https://github.com/chariotsolutions/phonegap-nfc/issues/188.

Thanks for your replay Allan, Excuse me for my english is not so good. I will try to explain what is my problem. My phonegap app works correctly restoring the last view but when I install the nfc plugin and it reads the card if I close the app and i open it again the last view is missing and the app loses the last state. I think that i am doing something wrong. Can you help me with any idea?
Thanks again.

@pcalderoncity I agree with @allannaranjo that this sounds more like an application state problem than a problem with phonegap-nfc.
Do you see any errors from your app if you view the logs with  adb logcat or device monitor?
If you remove the plugin, does your application retain state when you exit and re-open it?
How does your application decide which page should be show? Are you overwriting this data after you read a nfc tag?

Hi Don,
The logcat shows that my app calls again to the create method CordovaActivity.onCreate() and the life cicle starts again in my app login page.
Reading only one card the app loses the state. I do not why?. Obiously if I do not put the card the problem does not appear. The app loses the state when it reads the first card.  My app is built with jquery using multi-page template, that is to say, multiple views in the same page.
For me is transparent the way that jquery or cordova handle the states, it works correctly by default.
I am new in the android world, I will appreciate any help.
Thanks Don.

So the login page appears after you scan a NFC tag? If that's the case, you may be doing something that causes the page to navigate, reloading the app. Look at the JavaScript where you're processing the nfcEvent. Look for javascript errors at runtime. Run jshint on your code.
Also look at the log before you see CordovaActivity.onCreate() are there any errors? If you see a Java stack trace, it's possible the plugin is causing an issue. Send me the details.
If you share your code I can take a quick look.

Thanks for your advice, I
will run the jshint tool but it should be noted that I commented the js lines where it set the nfc listener, therefore I think my personal code is not the problem. Just installing the plugin without the listener and put the card for reading originates my bug.
Line 1298
//nfc.addTagDiscoveredListener(_onNfc,function (status){alert(">>>>" + status);},function (error) { CM_SUBE_BAJA_OBJ.showMessage(MSG_NFC_ERR + JSON.stringify(error));});
Thanks for your attention.
Below my code:

SUBE-BAJA
<link rel="stylesheet" href="css/jquery-ui.min.css" >
<link rel="stylesheet" href="css/jquery.mobile-1.4.5.min.css">
<link rel="stylesheet" href="css/index.css">
<script src="js/jquery-1.11.0.min.js"></script>
<script src="js/jquery-ui.min.js"></script>
<script src="js/jquery.mobile-1.4.5.min.js"></script>

<script type="text/javascript" src="cordova.js"></script>

<style>
 .ui-header {

height: 41px;
}
.ui-autocomplete {
position: absolute;
top: 100%;
left: 0;
z-index: 10000;
float: left;
display: none;
min-width: 160px;
_width: 160px;
padding: 4px 0;
margin: 2px 0 0 0;
list-style: none;
background-color: #ffffff;
border-color: #ccc;
border-color: rgba(0, 0, 0, 0.2);
border-style: solid;
border-width: 1px;
-webkit-border-radius: 5px;
-moz-border-radius: 5px;
border-radius: 5px;
-webkit-box-shadow: 0 5px 10px rgba(0, 0, 0, 0.2);
-moz-box-shadow: 0 5px 10px rgba(0, 0, 0, 0.2);
box-shadow: 0 5px 10px rgba(0, 0, 0, 0.2);
-webkit-background-clip: padding-box;
-moz-background-clip: padding;
background-clip: padding-box;
*border-right-width: 2px;
*border-bottom-width: 2px;
.ui-menu-item > a.ui-corner-all {
display: block;
padding: 3px 15px;
clear: both;
font-weight: normal;
line-height: 18px;
color: #555555;
white-space: nowrap;
&.ui-state-hover, &.ui-state-active {
  color: #ffffff;
  text-decoration: none;
  background-color: #0088cc;
  border-radius: 0px;
  -webkit-border-radius: 0px;
  -moz-border-radius: 0px;
  background-image: none;
}

}
}
.ui-popup-container, .ui-popup {
height: 90%;
width: 98%;
position: absolute;
top: 5%;
left:0;
}
</style>

AUTENTICACIÓN

 Usuario

 Password

SELECCIONE PUNTO DE RELEVO

{USERNAME_TITLE}

Home
{APP_TITLE}
Salir

{USERNAME_TITLE}

Home
{APP_TITLE}
Salir

NUEVO RELEVO

{USERNAME_TITLE}

Home
{APP_TITLE}
Salir

OS:

BUS:

OB:

Motivo Cambio OB

SUBIDA
BAJADA

Patente

Conductor

{USERNAME_TITLE}

Home
{APP_TITLE}
Salir

 Acerque la tarjeta al lector

ACEPTAR

Conductor

{USERNAME}

Home
SUBE-BAJA
Salir

OS:

BUS:

OB:

SUBIDA
BAJADA

Patente

Conductor

{USERNAME}

Volver
SUBE-BAJA
Eliminar

ÚLTIMAS OPERACIONES:

One

Two

Three

Rather than pasting code here, a github repo or gist would be better.

I am Sorry, the problem is not the plugin.  I think that it is jquery-cordova bug. Without the plugin occurs the same issue.
Thank you very much for your time.


Register a .well-known URI

RFC 5785 provides a registry from "well-known URIs".
Well known URIs "are designed to facilitate discovery of information on a site when it isn't practical to use other mechanisms".
As a maintainer of the Drupal-based implementation of JSON API, this could be incredibly useful to us.
How?
We allow every instance of a Drupal application using the JSON API module to define their own API path prefix. Additionally, the spec does not define any kind of URL structure.
Therefore, having a well-known URI would allow us to write a generic Drupal JS API client that would work for any site, with any URL structure, with minimal configuration (simply tell it the protocol + domain). With a well-known URI, this client would then only need to visit the well-known URI where it could discover the entry point to the rest of the API.
I'm happy to lead and help with this effort, but I imagine that the spec maintainers would like to be involved with that :)

Hmm. If you're already configuring the client with the protocol and domain, is it really extra work to also configure it with the entry point path?

Not terribly, but then one can't change the prefix without changing every hardcoded instance of it. The point is to promote evolvability :)

Down the line, I can imagine having a home document like file at either a well-known uri or provided as a Link response header for GET / on the host

My intention was to respond with a 302 redirect to our own version of the home document (we already have one), not to start the process of defining what a home document should be :)
Personally, I think a well-known URI is designed exactly for this use case. Coming up with some header-based negotiation of our own isn't really necessary.

I'm not sure there's enough value creating that if all it would contain is the api path prefix

I'm not suggesting that the spec should change in anyway or that we should standardize some kind of response from that URI and certainly not that we'd just respond with the prefix (yuck!)
I think the most this would involve in this repo is to perhaps provide a recommendation that applications respond with a redirect to a home document or primary collection.

Also, it's not even necessary to provide the protocol and domain if you default to https and the window.location domain (which mitigates CORS headaches). Basically, the client is then just a drop-in piece of code.

@gabesullice Sorry for my slow response here. I'm still not sure I totally follow your proposal, or that a well-known URI makes sense.
Can you explain exactly what you're imagining would go in the JSON:API spec? Is it just something to the effect that "The well-known URI /.well-known/jsonapi should redirect to the API's entry point"? If so, that intuitively strikes me as too narrow a feature to reserve a URI for (well-known URIs in particular are a scarce resource). Also, what if the same host has multiple json:api APIs running on it?
I'm all for evolvability, and I wish json:api used more hypermedia in general, but the entry point url seems like a low priority case. Even in the purest of REST discussions, the home URI is usually the one URI that the client memorizes.

Personally, I think a well-known URI is designed exactly for this use case. Coming up with some header-based negotiation of our own isn't really necessary.

Here's sorta what I'm imagining for the Link case, just to flesh it out:
Client: GET /
Server:
HTTP/1.1 200 OK
Link: </api>; rel="https://jsonapi.org/rels/entrypoint"
Access-Control-Expose-Headers: Link
// ...

In this case, we'd be defining the https://jsonapi.org/rels/entrypoint url, instead of a well-known url. That doesn't seem like any more of "coming up with our own thing", and it has a couple advantages:

the url is scoped to jsonapi.org, and therefore less scarce than .well-known urls.
it supports the case of multiple APIs running on the same host (just add multiple entry point links).

What is it about the Link approach that doesn't sit right with you, or doesn't seem to fit the use case?
As you quoted, well known URIs are designed for use "when it isn't practical to use other mechanisms", so I want to explore those other mechanisms first.

Sorry for my slow response here.

Please don't apologize!

Can you explain exactly what you're imagining would go in the JSON:API spec?

I really didn't imagine much, if anything, would make it into the spec. Perhaps just a recommendation to do something at the .well-known resource. I think that something remains undefined. Perhaps it's your Link based suggestion.

Here's sorta what I'm imagining for the Link case, just to flesh it out:
Client: GET /

Ah, but what is /? Is that not a well-known path prefix? Wouldn't it be better to dedicate a specific path prefix for this so as not to collide with any existing resources at that path?

we'd be defining the https://jsonapi.org/rels/entrypoint [link relation type URI]

That'd be great. I'd love to see JSON API start defining some link relation types :)

[A JSON API specific link relation type] is less scarce than .well-known urls

Frankly, I wouldn't be too worried about their scarcity. Since 2010, only 34 have been registered.
The JSON API specification is an open standard that's seen wide internet adoption. I think it'd be reasonable to reserve: org.jsonapi for the purpose of providing a globally unique URL where a JSON API client could discover the API's home document.
From that URL, perhaps the spec could recommend that the resource at the well-known URL SHOULD serve a home document or respond with one or more link headers from which a home document can be obtained.

I think you're a step ahead of where I am coming from. You want to codify how the resource at the well-known URL should respond. I'm just proposing that one should exist.
I made this issue when I realized that if I wanted to have a truly zero-knowledge client, I'd have to have a standard URI from which that client could "enter" a JSON API's hypermedia space. I though it would be naive to presume that / would work—better to have a new, globally unique URI for that purpose.
Once there, how that client would navigate that space isn't yet defined.

FWIW, I would also love if it if JSON API defined what a home document should actually be ;)
But that's out of scope here I think.


Fix gdb_compatible build

This would break the updater (see https://github.com/mkw-sp/mkw-sp/commit/9062cc5dc643a96aa015c7b7a984950e17285d30).

Resolved in the latest push


build: add build:qe script for pr_check

Still failing :(

as expected @ezr-ondrej, the routes also need to change in qe tests

Could you add in comment what the new routes are? I guess we can merge this, so QE can try this out :)

this workaround failed to work, closing


Option to modify background color for message?

Are you planning to modify the background color for the message, so that a different color can be used for the user and the bot? This would be a nice alternative to using avatars.

I've faced the same problem. Have you found a solution?


Lock scrolling

Is there any way to lock scrolling and enable only the use of buttons to go to the different views?

Ok, I solved with a simple:
scrollview.scrollEnabled = false
BTW, how can I enable or disable scrolling in particular views?
Thanks for the work. This class is wonderful.

You make it right :) this is the easiest way to lock the scroll. If you want to lock it only for some view (IMO it's a strange behaviour), you can just verify the current page and enable or disable the scroll.

It's not a strange Behaviour and I can explain it: the first pages are used to show the main app features, then I need to set some data and I don't want that users can skip pages, so I show the next button only when users input that data.
Thanks for reply.

@ecstaticax Got it, makes absolutely sense :+1:  Even if I've already seen a lot of Apps using it for a variety of different tasks I'm still thinking about BWWalkthrough as a simple...walkthrough. Thanks for sharing your experience!

BTW I wasn't able to find a way to check the page number :-/

check the currentPage property.

This is my actual extract from BWWalkthroughViewController
 override func viewWillAppear(animated: Bool) {
        super.viewWillAppear(animated);

        pageControl?.numberOfPages = controllers.count
        pageControl?.currentPage = 0
        scrollview.scrollEnabled = false

    }

I realized that it is loaded only the first time and not everytime. So how can check, when a view is loaded, its currentPage property and set scrollview.scrollEnabled true or false?
Thanks for support.

The currentPage is a property that gives you information about the current page shown by the walkthrough and it is read only.
var currentPage:Int{    // The index of the current page (readonly)
        get{
            let page = Int((scrollview.contentOffset.x / view.bounds.size.width))
            return page
        }
    }

If you want to disable the scroll for a given page why don't you use delegate function walkthroughPageDidChange(page:Int) ?

Thanks! I solved it!
private func updateUI(){
    // Get the current page

    pageControl?.currentPage = currentPage

    // Notify delegate about the new page

    delegate?.walkthroughPageDidChange?(currentPage)

    if (currentPage < 3)
    {
        scrollview.scrollEnabled = true
    }

    else
    {
        scrollview.scrollEnabled = false
    }

    // Hide/Show navigation buttons

    if currentPage == controllers.count - 1{
        nextButton?.hidden = true
    }else{
        nextButton?.hidden = false
    }

    if currentPage == 0{
        prevButton?.hidden = true
    }else{
        prevButton?.hidden = false
    }
}


Implement the Ouroboros BFT protocol

This resolves #193.

I will merge this pull request without review, since this code needs to be transferred to the new repository ouroboros-high-assurance, where any further development will take place.


NoTrailingWhitespaceInStringFixer - introduction

This (risky) fixer removes trailing whitespace in strings.
The fixer is added to @PhpCsFixer:risky.

@kubawerlos thanks! test added, code fixed. ;)

Thanks @gharlan  :+1:  nice to have this in!


fix: Update return type annotation for Thread.update_state() methods.

Summary
The response body of the endpoint POST /threads/{thread_id}/state looks like this:
{
    "checkpoint": {
        "thread_id": "e2496803-ecd5-4e0c-a779-3226296181c2",
        "checkpoint_ns": "",
        "checkpoint_id": "1ef4a9b8-e6fb-67b1-8001-abd5184439d1",
        "checkpoint_map": {}
    }
}

Double-checking. This is the response from the API:

configurable and checkpoint_id fields at the top-level are deprecated.


Switching all zap files to enabled only content

Switching all zap files to enabled only content
JIRA: ZAPP-1113

This PR is dependent on https://github.com/project-chip/zap/pull/1153

Regarding the regen diff failure in .mattet files I see that robotic vacuum cleaner does not have stop and start incoming commands enabled.

Similarly the log source app does not have incoming RetrieveLogsResponse command enabled.
So the output being generated into the .matter files is correct now.


Add props protection for article front matter props

{
    prop && (render something)
}

This issue is probably going to be fixed by #190


gateway,http,lavalink: use rustls for default

Switch out the gateway, http, and lavalink crates' default TLS feature from being native to rustls.
See #124 for justification.
Closes #313.

Addressed comments and rebased


Update Get-SPTimerJob.md

Fixed example format to include "PS C:>".

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/Get-SPTimerJob.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


annotations disappeared from  publication pages

You might be aware....

Thanks, I hadn't noticed that.  It's fixed now.


🐞 Bug : The pagination bar overflows on my mobile and I can not scroll to page 1 on the bar

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
The pagination bar overflows on my mobile and I am not able to scroll to page 1's link on the bar .
https://github.com/CircuitVerse/CircuitVerse/assets/122573982/f767be6a-4984-402e-8a86-56b6ec05e616
Steps To Reproduce

Go to circuitverse's website on mobile and scroll down to the bottom to see the pagination bar.

Expected Behavior
The bar shouldn't overflow and user should be able to scroll to any of the page links.
Screenshots
No response
Device Information [optional]
- OS:
- Browser:
- version:

Additional context
No response
Are you working on this issue?
Yes

@tanmoysrt @fillingtothemomo, please assign me this issue


Did some mappings in RedstoneWireBlock

I feel like a better name could be used here but getReceivedPower makes the most sense, perhaps a change should be made to the method im world to be more clear about its purpose which is to find the highest power on all horizontal directions

Hmm, I doubt the rest of these methods may just be lambdas. Anyways look great, ready to go


Bevy-native World Inspector

I've put together a very rough prototype for an entity/world inspector:

There is currently an egui-based world inspector crate, but what I'd like to see is an officially-supported world inspector that ships as part of Bevy that can be enabled via a plugin.
My purpose in filing this ticket is to start a discussion and gather feedback about:

What features should it have?
What should it look like? (mock screens and so on).

The inspector will most likely be implemented on top of BSN, so the technologies for building it are not quite ready yet. However, I consider the world-inspector project to be kind of a like a dress-rehearsal for the Bevy editor: a much simpler project, one that can be completed relatively quickly, but which shares many of the same underlying technologies (such as picking, ui templates, preferences, reflection-based editing, and so on) and which will have a similar look and feel.
That being said, there will be some important differences between the world inspector and the editor: primarily, the inspector will function "in-game" and inspect the Bevy World directly, it will not rely on any kind of remote protocol. This means that the data types being inspected will be quite different.
This is also something that I feel could benefit from many contributors rather than being a solo project, as there are many different possible ways that the world inspector could be extended.

Some feature requests for you:

set components to show up with a standard name in the inspector (e.g. Player, Monster...)
defaults to grouping entities of the same kind together (based on the standard name property above)
search by name
search by "matches query"
different views: "scene" (physical stuff), "systems" (one-shot systems, observers), resources, etc...
save changes made in the inspector back to the underlying scene asset (very hard but soo good)

Here's some more:

Draggable / resizable / Hideable (possibly showable via configurable hotkey)
Position / Size persists via preferences
Possibly tree expansion persists
Show entities, resources, and assets.
Real-time updates as things change.

pinning entities
hiding entities
deleting entities (waaay easier than adding components or spawning entities)
resetting component / resource values to default
alert coloring for NaN values

Make sure you have some way of filtering out the UI entities generated by the inspector. Otherwise you have the inspector, which generates UI entities, which then need new entries in the inspector tree, which generates more UI entities, etc... I may or may not have ran into this in my own crate.

Make sure you have some way of filtering out the UI entities generated by the inspector. Otherwise you have the inspector, which generates UI entities, which then need new entries in the inspector tree, which generates more UI entities, etc... I may or may not have ran into this in my own crate.

Yep! Ran into that problem already. It's especially a problem with observers and one-shot systems, both of which create entities that show up in the top-level query unless filtered out.

Oh yeah that too, ECS features that create entities under the hood.


Iterator as fp

Major updates :

Refactor optimization iterators to make a distinction between fixed-point iterate and estimate of the minimizer. This enables to rewrite all optimization algorithm as fixed-point algorithms, and to use them in the DEQ framework.
The dictionary iterated has typically the form {"iterate" : (x,z) , "estimate" : x, "cost" : F}.
The iterate variable can be either a tuple ( ADMM, CP), either a single tensor (all the other implemented iterators)
The link between the iterate and the estimate is given by the 'get_estiamte_from_iterate' function for each optim_iterator.
Each optim iterator has its own initialization function 'init_algo'.

Minor updates :

Allow str to be passed as directory name in demo dataset loader
Change name 'F_fn' to 'cost_fn'
Anderson acceleration in utils

Checks to be done before submitting your PR

[x] python3 -m pytest tests/ runs successfully.
[x] black . runs successfully.
[x] make html runs successfully (in the docs/ directory).
[x] Updated docstrings related to the changes (as applicable).
[ ] Added an entry to the CHANGELOG.rst.

Hi Samuel, I have one naive question regarding memory:
Is it possible to avoid storing the 'estimate' entry in the dictionary? If we have the get_estimate_from_iterate() function, can we call it only at the end, and avoiding the 'estimate' at all iterations?

@tachella the reason is that it avoids computing the estimate various times. The estimate is calculated when computing metrics and checking convergence. I am happy to discuss further the necessity to have it there or not.

@tachella the reason is that it avoids computing the estimate various times. The estimate is calculated when computing the cost, computing metrics and checking convergence. I am happy to discuss further the necessity to have it there or not.


Passing filename directly in example code

Your sample tool expects the filename to be passed with -i.
I think this could be made simpler by just accepting a filename, e.g.
ds_storeviewer [path_to]/.DS_Store
Also in case no parameter is given at all you could just try if .DS_Store exists in the current directory with its original filename and parse that.
Furthermore I'd suggest to have the example code as a file itself and not as part of the readme.

Hi @hannob ,
thanks for the suggestions! I've opened a PR which should fix the issues.
Do you mind reviewing it?


Generated .gradle file invalid, parseInt takes wrong argument

Expected Behaviour
Gradle build should work.
Actual Behaviour
Crash in:
platforms/android/phonegap-plugin-barcodescanner/appname-barcodescanner.gradle' line: 3
Works when concatenating what looks like to be an array now;
if (cdvMinSdkVersion == null || Integer.parseInt('' + cdvMinSdkVersion) < minSdk ) {
seems to work.
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Remove android platform and re-add it completely.
Platform and Version (eg. Android 5.0 or iOS 9.2.1)
Android 7.1.2
(Android) What device vendor (e.g. Samsung, HTC, Sony...)
OnePlus
Cordova CLI version and cordova platform version
7.0.1
Installed platforms:
android 6.2.3
ios 4.4.0
Available platforms:
blackberry10 ~3.8.0 (deprecated)
browser ~4.1.0
osx ~4.0.1
webos ~3.7.0
Plugin version
phonegap-plugin-barcodescanner 6.0.8 "BarcodeScanner"
Sample Code that illustrates the problem
Logs taken while reproducing problem
FAILURE: Build failed with an exception.

Where:
Script '/Users/<>/Documents/_git/<>/platforms/android/phonegap-plugin-barcodescanner/<>-barcodescanner.gradle' line: 3

What went wrong:
A problem occurred evaluating script.

No signature of method: static java.lang.Integer.parseInt() is applicable for argument types: (java.lang.Integer) values: [16]
Possible solutions: parseInt(java.lang.String), parseInt(java.lang.String, int), print(java.lang.Object), print(java.io.PrintWriter)

Same issue! Anyone who fixed it?

same issue too :(

The empty string concatenation trick makes the app compile, but it might just be a quickfix to a problem further up the chain somewhere. For my Ionic app the file to be edited is in platforms/android/phonegap-plugin-barcodescanner/starter-barcodescanner.gradle

Hi, I fixed that error modifying the code in 'phonegap-plugin-barcodescanner-master\src\android\barcodescanner.gradle'
if (cdvMinSdkVersion == null || Integer.parseInt(cdvMinSdkVersion) < minSdk ) {
ext.cdvMinSdkVersion = minSdk;
}
for this:
if (cdvMinSdkVersion == null) {
ext.cdvMinSdkVersion = minSdk;
}
else{
int num = cdvMinSdkVersion as Integer
if(num < minSdk ){
ext.cdvMinSdkVersion = minSdk;
}
}

@zaubara thanks, I just pushed a fix.


Bitcode is not enabled for real device iOS builds

Hi,
First of all I'd like to thank you for creating this awesome library, kudos! 👍 👍
When building for my actual phone on iOS I'm getting an error that bitcode is not enabled in libFirestack.a. I checked the firestack project and it is indeed disabled there. Is this on purpose and if so what dependency requires that bitcode is not enabled.
I'm currently stuck with my build on this as I really don't want to disable the bitcode option.

best regards,
Hein

Hein,
Thanks for the note. You're the second to ask for this (thanks for making the issue). I disabled it previously as bit-code caused a build error previously. I don't recall the specific reason why I had it disabled, but I will investigate and report back.

Awesome! If I can be of any assistance let know.
Cheers, Hein

Btw, quick other question. I've integrated Firebase Crash reporting in my App. Complete with console.log interception and correct callstacks (both iOS and Android). Would you be interested in having this code to the firestack codebase?

Hein,
Absolutely! I've been meaning to put that on the feature list!

Alright cool. It's really busy at the moment, but I'll to create a pull request for it anytime soon.

Hein,
Let me know if you want some help on how to integrate it.

Yeah, well most of it is pretty straightforward to integrate. The only tricky thing is that when building the bundle, it also needs to generate sourcemaps. I've modified my scripts for it, but not sure how that would need to be done automatically when installing the firestack lib (or using react-native link). I'll have a closer look when I have more time.

And yeah, having it in a separate module such as crash would definitely also make sense to me. 👍

Btw, I was using the storage API's today and noticed the examples in the README are out of date.
It says 'firestack.uploadFilebut it should befirestack.storage.uploadFile`. But you're probably already aware of this :)

Oh yes! Can you make a PR with that update?

Okay, I recall why bit-code needed to be disabled. Firestack is built as a dynamic library, which needs to be linked against static libraries (React). Until we find a way to dynamically link Firestack to React, we can't enable bitcode.
Any suggestions?

As of now, I can't enable bitcode due:

bitcode and the undefined flag are opposites (for obvious reasons, but we cannot build a library that cannot find it's symbols, but cannot build a dynamic library without using -undefined flag (yet).
Setting the build to a static library does not allow our app to find the Firebase libraries
Setting the build to a dynamic library does not allow our app to use bitcode

I'm going to mark this as wontfix for now, until we can figure out a different build mechanism.

I think I fixed the bitcode issue. I pushed the latest update to the feature/bitcode branch, if you're interested in trying it out in your app.


Adding ability to refresh counter every x minutes/hours

Hi,
I would like to propose a little enhancement : is it possible to add an auto-refresh of all counters (like when I do a "counter list" in the console) in a regular time basis (every x minutes or hours) ?
I have for example counters on SQL Server on databases (counter instance = *), so each time I create a new db, I have to refresh the counters to get the new db metrics.
Thanks for your great work !

This is a great idea. It is also needed if you want to monitor processes on the machine.

This feature is completed, but yet not pushed. It will be available from version 1.0.11. Then the instances will be refreshed on every read.

Refreshing on every read could perhaps be a problem for large amount of counters with relatively high frequencies (in my tests I got about 850 counters with most of them every 5 secondes and I see it cousumes some cpu resources).
Not sure the best option would be (every x read, not more than once a minute, ...).

I was considering every x reads since it would be very easy to implement. I can add that to the config.

From version 1.0.11 it is possible to set the attribute named RefreshInstanceInterval on CounterGroup level.


spiffs headers missing in repository?

Hi,
I just started playing around with ESP32 systems.
When I tried to build the 'blink' example, I noticed that obviously to header files are missing in the repository (branch master) at this time:

spiffs.h
spiffs_nucleus.h

Cheers,
Enrik

Hi Enrik,
Maybe your clone of ESP-IDF repository is missing spiffs submodule?
This spiffs component including submodule has been added just in last couple of days.
On GitHub it is visible as components/spiffs/ @ 794f047
If this is the case then run git submodule update --initt inside your local clone of ESP-IDF repository and it should be added.

Hi Krzysztof,
Thanks for your response.
My initial checkout / build run was just after spiffs had been added. Also, I can't see the mentioned header files at https://github.com/espressif/esp-idf/tree/dd87deb2781a1eb2d70122816d5061199b059812/components/spiffs/include
Can you please double check?
Thanks,
Enrik

Hi again :smile:
The point it that this header is in another location.
It is inside the submodule,, see https://github.com/pellepl/spiffs/tree/794f0478d2aa9c978c3844da6e97f14239a1e061/src
Check if you have the whole submodule on your PC.
If not, then use command I desribed above to get it.
Krzysztof

Thanks, after the submodule update --init, all files are available.