invite codes for the cloud social provider

Still prototyping...this makes the cloud social provider accept invite codes. An invite code encodes a server's address and credentials and, when shared, grants access to the server. I guess at some point we could make these URLs?
This in-progress pull request makes the cloud setup script output an invite code when it's done:
https://github.com/uProxy/uproxy-docker/compare/trevj-social-cloud?expand=1
Tested on my workstation and on a Digital Ocean provider.

:+1: for this change, except I think we should move the code from inviteUser to acceptUserInvitation.  In most cases (all networks except GitHub), inviteUser doesn't take any args but returns an Object which is then encoded as part of uProxy's invite URL.  Then this same data is typically passed as JSON to acceptUserInvitation (basically what you have inviteUser doing here).
Also from a UX perspective, I think adding a server corresponds more to accepting an invite that you received (unless you are deploying a new one).  inviteUser seems more like you already own a server and want to permission friends to use it (so you'd want to generate an invite URL to send to your friend)

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from the review on Reviewable.io

As discussed, let's keep the inviteUser approach as-is until we have a better idea on how deploying and inviting users will work in the new invitation flow world.
Thanks!


Requirements

Please provide requirements YAML or text file.

All the code was generated based on HRNet, please have a look on its requirements.

Which exactly commit of HRNet?


nmake fatal error, 32-bit time_t

Thomas Hruska points out the following issue in this post to openssl-users:
https://mta.openssl.org/pipermail/openssl-users/2018-September/008757.html
        cl  /Z7 /Fdapp.pdb /Gs0 /GF /Gy /MD /W3 /wd4090 /nologo /O2 /WX /I "include" -D"OPENSSL_SYS_WIN32" -D"WIN32_LEAN_AND_MEAN" -D"UNICODE" -D"_UNICODE" -D"_CRT_SECURE_NO_DEPRECATE" -D"_WINSOCK_DEPRECATED_NO_WARNINGS" -D"OPENSSL_USE_APPLINK" -D"NDEBUG" -D_USE_32BIT_TIME_T -D_USING_V110_SDK71_ -D_WINSOCK_DEPRECATED_NO_WARNINGS /Zs /showIncludes "test\ct_test.c" 2>&1 > test\ct_test.d
NMAKE : fatal error U1077: 'cl' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\bin\HostX86\x86\nmake.exe"' : return code '0x2'
Stop.

test\ct_test.c(503): error C2220: warning treated as error - no 'object' file generated
test\ct_test.c(503): warning C4244: 'initializing': conversion from 'uint64_t' to 'const time_t', possible loss of data

Probably triggered by the usage of:
-D_USE_32BIT_TIME_T

I use that define for 32-bit builds on my 64-bit hardware as per this old post:
https://groups.google.com/forum/#!topic/mailing.openssl.users/AGuOi4yEY9A
Casting to time_t appears to correct the issue and the build completes successfully:
    const time_t default_time = (time_t)CT_POLICY_EVAL_CTX_get_time(ct_policy_ctx) /
                                1000;

@vdukhovni adds the following:

Since the CT time value is in "ms" since epoch, you really don't want
to down-convert that to 32 bit before the division.  You'll need
some parentheses:
https://en.cppreference.com/w/c/language/operator_precedence
type cast has higher precedence than division, but you need to
divide first, then cast.

A quick PR with the cast and requisite parentheses should sail through approvals pretty quickly...


20.0.0/super tomcat

I'm sorry. I'd appreciate it if you could let me know so that I don't make this mistake in the future.


Add support for tagged template strings [WIP]

This PR adds support for compiling tagged template strings to function calls.  I've verified the original implementation within the rescript-compiler repo before moving the code over to the syntax repo.  Running the tests pointed out a few issues so I had to make changes and have yet to retest it in the rescript-compiler repo.  There's still some work to do on this, in particular:

[ ] add tests that verify the parse tree (these should show that tagged templates get parsed as Pexp_apply nodes with the appropriate attribute)
[ ] add location data to parsed nodes when available
[ ] remove commented out code (I left it in for now since I want to be able to easily reference it for to help with the previous bullet point)
[ ] figure out why there's an extra carriage return in the printer out

cc @tsnobip

Huge if true 🤯

I'll try to work on it in the coming days to make some progress :)

I've added location data so I'll push those changes this evening.  I'll also try to get some tests for the parse tree generated from tagged templates.

@tsnobip thanks for the style suggestions.  I'll make those changes this evening as well.

I see you are compiling tagged template to function calls, why not compile to es6 tagged template syntax? (The reason is that this helps with some GraphQL tooling that will pick out these template literals out of the code).

@jfrolich updating the code generate requires changes to rescript-compiler.  I was planning to do a separate PR for that, but having to make changes in separate repos isn't the greatest so I'm going to merge this repo into the compiler repo and then recreate this PR afterwards.

I've created https://github.com/rescript-lang/rescript-compiler/pull/5347 to merge the syntax repo into rescript-compiler.  I'll work on re-creating this PR on top of that change over the weekend.

Closing this in preference of https://github.com/kevinbarabash/rescript-compiler/pull/2.


Cluster Provisioning v2: Generic Drivers (Cluster & Node) - Cluster Driver List Enablement Page

Already exists in 2.6.0.


Proxy-pallet: Design flow for users deletion

Should we allow users' deletion from Proxy website?
One deletion per extrinsic call?
Multiple deletions per extrinsic call?
Use a different extrinsic or combine this flow with users_registration extrinsic?

@DaniPoot @AugustoLara

Should we allow users' deletion from Proxy website? Yes, removing them from the platform.
One deletion per extrinsic call? Yes, one is enough to be safe.
Multiple deletions per extrinsic call?
Use a different extrinsic or combine this flow with users_registration extrinsic? whatever makes sense technically
An admin can be deleted from Proxy UI? yes, only by another Proxy Admin.
An administrator can delete another administrator? yes, only by another Proxy Admin.
If any of the above complicates the technical implementation, let go with whatever makes sense technically

I updated validations & workflow.
Backend done.
@tlacloc


feat(spanish-translate): complete the spanish translation

I've completed the Spanish translation.

Motivation and Context:
The Spanish translation was incomplete.
I've used the official Bitcoin qt Spanish translation to keep terms as uniform as possible.
https://github.com/bitcoin/bitcoin/blob/master/src/qt/locale/bitcoin_es_ES.ts

Types of changes:
Manual translation of es-ES.json language file.

Checklist:

[x] My code follows the code style of this project.
[ ] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[x] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage increased (+0.01%) to 19.116% when pulling 3e2e58c074b76501467edeee1c79ff8904014bc4 on thedon-chris:feat/full-spanish-trans into 977151baf33a86927ad23b29cbe411d71eca6661 on LN-Zap:next.

Sure!

@mrfelton I've completed your requested changes and force pushed


Send sms update

Update the call to send_message so that it checks the response data in a vaguely sensible manner.

Setting as do-not-merge to match other PRs. Leaving to @marklewin to merge!


Octant should not return a namespace for non-namespaced resources in its response.

Octant's content response returns a namespace even for non-namespaced resources.
It does not work well for features such as #2580 which rely on the api response to set page title and breadcrumb values.
What did you expect to happen:
Content response for non-namespaced resources should not return a namespace.
Environment:

Octant version (use octant version): 0.21.0

blocks #2580

Addressed by https://github.com/xtreme-vikram-yadav/octant/commit/acc92278ac734b67556ca62d160b0995f113cb8d


clustering movie data from imdb issue #153

#153
[clustering movie data from imdb issue]
Description
1.We scrape IMDb data including movie titles, ratings, and summaries using BeautifulSoup
2.We use TF-IDF vectorization to convert the movie summaries into numerical feature vectors.
3.We apply K-means clustering to group the movies into clusters based on their summaries.
4.We use PCA for dimensionality reduction to visualize the clusters in a 2D space.
Type of PR

[ ] Bug fix
[X] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Checklist:

[X] I have performed a self-review of my code
[X] I have read and followed the Contribution Guidelines.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have commented my code, particularly in hard-to-understand areas.

Co-authored-by: Mercia Jeno<EMAIL_ADDRESS>Co-authored-by: Bhakti Kalyankasture<EMAIL_ADDRESS>

@sanjay-kv Can you merge it.
attaching link: https://github.com/Recode-Hive/Scrape-ML/pull/108


opentelemetry-cpp: init at 1.12.0

Build with support for:

in memory
otlp http
otlp grpc
zipkin
prometheus
elasticsearch

Things done

Built on platform(s)

[X] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Interesting library that should certainly be included in nixpkgs.

@tobim thank you for your fast and thorough review !

Result of nixpkgs-review pr 262139 run on x86_64-linux 1

2 packages built:

opentelemetry-cpp
opentelemetry-cpp.dev

Result of nixpkgs-review pr 262139 run on aarch64-linux 1

2 packages built:

opentelemetry-cpp
opentelemetry-cpp.dev

Result of nixpkgs-review pr 262139 run on aarch64-darwin 1

2 packages built:

opentelemetry-cpp
opentelemetry-cpp.dev

You could enable most of the unit tests, see https://github.com/panicgh/nixpkgs/commit/d22827c52242e217b35b02bdf307dbc659056529.
I tried other ways to disable the tests than a patch, e.g. GTEST_FILTER or passing it to ctests (ARGS="-E pattern"), but it appears that they are always overwritten.

You could enable most of the unit tests, see panicgh@d22827c.
I tried other ways to disable the tests than a patch, e.g. GTEST_FILTER or passing it to ctests (ARGS="-E pattern"), but it appears that they are always overwritten.

Thank you, I thought the tests were actually running.
I have included your change.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1250

Result of nixpkgs-review pr 262139 run on x86_64-linux 1

2 packages built:

opentelemetry-cpp
opentelemetry-cpp.dev

It seems the singleton.SingletonTest.Uniqueness test fails on darwin on ofborg. Not sure what it does, but can it be reported upstream and disabled here in the meanwhile?

According to ofborg, the singleton.SingletonTest.Uniqueness fails because of a segfault. I could not find the cause on a quick glance, but I agree that we can probably ignore it for the moment.
You may cherry-pick a fixup commit from https://github.com/panicgh/nixpkgs/commit/cd2847810c746295e363ddcbfd725864b0bb963d and squash it into your branch. It adds another patch to disable the singleton.SingletonTest.Uniqueness test.
I hope that we can get this package merged, finally.

Thank you, almost there :crossed_fingers:


Fjk22 patch 1

Save data where users looked - A script that allows to save data where the user has looked using Pupil in a Unity Application

@FJK22 Thank you for contribution!


Error: Failed getting S3 bucket: NotFound: Not Found

I have created a S3 bucket manually.
Than i copy and pased the ARN to the tfvar file.
When i am running terraform plan i am getting following error:
Error: Failed getting S3 bucket: NotFound: Not Found
status code: 404, request id: 83949CCE5CC278B4, host id: jl0I7e49Xqsjw8A3kXlcFUVOldaATVtmAxPWZHvrBAukrE5/AQFpmO/qkKAdlOp3CGzeEWs1Gwo= Bucket: "lab-XXXXXX-nonprod-automation-codepipeline-artifacts"
Than i have tried to create the S§ bucket with the name: lab-XXXXXX-nonprod-automation-codepipeline-artifacts
It solved the terraform plan problem, but by terraform apply i get the following error:
aws_s3_bucket.codepipeline: Creating...
Error: Error creating S3 bucket: BucketAlreadyOwnedByYou: Your previous request to create the named bucket succeeded and you already own it.
status code: 409, request id: E0EF8B23DC4D7EEF, host id: +296QI1KcTiD06C7qzSB6BV5lmxlQBRSprr4kKkkBPD3JegZOHE4a4eYrZvKe1hPq/FjbRzYiIg=
Any ideas?

Can't be reproduced.
/stale


fix withCityHidden, withZipCodeHidden and withStreetHidden options

Hi there. Found a bug with hiding zip code, street and city views. Fixed

I support @Null45 request. It's important features.

@Null45 many thanks for your contribution!


CppAD module missing?

After updating from 2.4.4 to 2.4.6, CMake cannot find CppAD. After some digging, I see
SET(CMAKE_MODULE_PATH "${CMAKE_SOURCE_DIR}/cmake/find-external/CppAD/" ${CMAKE_MODULE_PATH}) added to the CMakeLists but the find-external/CppAD directory does not exist. I guess that might be the issue?

nvm I see a fix in devel


Intructions for local build

Hi!
I am trying to locally build RustyHermit.
Are there instructions for that?
I tried "make" but failed to build.
mincheol@mir3:~/libhermit-rs$ make
Build libhermit
Finished dev [optimized + debuginfo] target(s) in 0.02s
make arch=x86_64 release=0 -C tests
make[1]: Entering directory '/home/mincheol/libhermit-rs/tests'
Compiling nodrop v0.1.13
Compiling lazy_static v1.4.0
Compiling cfg-if v0.1.9
Compiling scopeguard v1.0.0
Compiling fnv v1.0.6
Compiling either v1.5.2
Compiling itoa v0.4.4
Compiling libc v0.2.62
Compiling byteorder v1.3.2
Compiling memoffset v0.5.1
error[E0463]: can't find crate for core
|
= note: the x86_64-unknown-hermit target may not be installed
error[E0463]: can't find crate for core
|
= note: the x86_64-unknown-hermit target may not be installed
error: aborting due to previous error
For more information about this error, try rustc --explain E0463.
error: aborting due to previous error
For more information about this error, try rustc --explain E0463.
error: Could not compile cfg-if.
warning: build failed, waiting for other jobs to finish...
error[E0463]: can't find crate for core
|
= note: the x86_64-unknown-hermit target may not be installed
error[E0463]: can't find crate for core
|
= note: the x86_64-unknown-hermit target may not be installed
error: aborting due to previous error
For more information about this error, try rustc --explain E0463.
error: aborting due to previous error
error[E0463]: can't find crate for core
|
= note: the x86_64-unknown-hermit target may not be installed
For more information about this error, try rustc --explain E0463.
error: aborting due to previous error
For more information about this error, try rustc --explain E0463.
error: Could not compile nodrop.
warning: build failed, waiting for other jobs to finish...
error: Could not compile either.
warning: build failed, waiting for other jobs to finish...
error[E0463]: can't find crate for core
|
= note: the x86_64-unknown-hermit target may not be installed
error[E0463]: can't find crate for core
|
= note: the x86_64-unknown-hermit target may not be installed
error: aborting due to previous error
error: aborting due to previous error
For more information about this error, try rustc --explain E0463.
For more information about this error, try rustc --explain E0463.
error: Could not compile libc.
warning: build failed, waiting for other jobs to finish...
error: Could not compile lazy_static.
warning: build failed, waiting for other jobs to finish...
error: Could not compile scopeguard.
warning: build failed, waiting for other jobs to finish...
error: Could not compile memoffset.
warning: build failed, waiting for other jobs to finish...
error[E0463]: can't find crate for std
|
= note: the x86_64-unknown-hermit target may not be installed
error: aborting due to previous error
For more information about this error, try rustc --explain E0463.
error[E0463]: can't find crate for std
|
= note: the x86_64-unknown-hermit target may not be installed
error: Could not compile fnv.
warning: build failed, waiting for other jobs to finish...
error: aborting due to previous error
For more information about this error, try rustc --explain E0463.
error: Could not compile itoa.
warning: build failed, waiting for other jobs to finish...
error[E0463]: can't find crate for std
|
= note: the x86_64-unknown-hermit target may not be installed
error: aborting due to previous error
For more information about this error, try rustc --explain E0463.
error: Could not compile byteorder.
To learn more, run the command again with --verbose.
 A documentation is missing to build the Rust compiler independent from the Docker container.
In principle, you need the Rust toolchain with our extensions. You find our version at https://github.com/hermitcore/rust. Please checkout the current version and switch to the branch hermit:

git clone git@github.com:hermitcore/rust.git
cd rust
git checkout hermit

To build the toolchain, you need the configuration file config.toml in the root directory of the repository. A template config.toml.example is part of the repository. However, I would start with my version, which already enable the support of RustHermit. You have only to change the installation path (see variable prefix in config.toml).
Afterwards you are able to build the toolchain with following command ./x.py install. This will take a while. I would expect at least 45 minutes. Afterwards you have to set the environment variable XARGO_RUST_SRC to /installation_path/lib/rustlib/src/rust/src/. Please replace installation_path to the location, where you install the toolchain.
Afterwards, the makefile should in the libhermit-rs repository should work. :-)
The docker container contains a prebuild version. You could also use this version to build our examples.

Thanks!
However, I got some linking issues when I did "make" on libhermit-rs.
The linker can't find sys_netread(), sys_netwrite(), sys_network_init(), and sys_is_polling().
I tried to find where those functions are defined, but I can't find them.
Can you give me tips?

Please, pull the repository. I think that you aren’t working on the latest version of libhermit-rs.

Am 02.09.2019 um 20:24 schrieb Mincheol Sung<EMAIL_ADDRESS>Thanks!
However, I got some linking issues when I did "make" on libhermit-rs.
The linker can't find sys_netread(), sys_netwrite(), sys_network_init(), and sys_is_polling().
I tried to find where those functions are defined, but I can't find them.
Can you give me tips?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks! I can now play with the test application (hctests).


Consider best ways of presenting examples for multi-language project

With the R bindings, OpenDP is becoming increasingly multilingual. Maintaining documentation in parallel for different languages will be hard. Some projects let you tab between examples in different languages, so the narrative portions don't need to be duplicated for different languages. Examples:

h20.ai
polars

Possible roadmap:

Decide if this is a concern.
If it is, review different tools that support this style of documentation.
Looking at what different tools support, ask if this is something we want to use for all docs. (Are there examples of multi-lingual doc tools that can show graphical output?)
File a new issue for implementation, when path is clear.

See also:

#971

Notebooks are also more difficult to:

internationalize
give code snips in multiple programming languages (like https://docs.h2o.ai/h2o/latest-stable/h2o-docs/cross-validation.html)

Might still be worth it (there may be solutions here), but should consider these tradeoffs before converting.

Originally posted by @Shoeboxam in https://github.com/opendp/opendp/issues/971#issuecomment-1789109372

Filed a new issue that duplicates this one:

#1052

It has more useful info, so I'll close this.


Refresh token

Related Issues
Fix #589

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Description

Screenshots/Recordings

Added tests?

[x] Yes
[ ] No, because they aren't needed

Added to documentation?

[ ] README
[ ] Documentation
[ ] No Documentation Needed

When this will be released?


Use built-in adapter functionality for datatypes

This is a:

[ ] documentation update
[ ] bug fix with no breaking changes
[x] new functionality
[x] a breaking change ??? (maybe???)

All pull requests from community contributors should target the main branch (default).
Description & motivation
Follow-up to TODOs left from #577. Experiment with using api.Column.translate_type for our existing type_* macros.
Feels good:

This is code defined within the adapter plugin, and already used for internal purposes.
For the most part, it "just works" as a drop-in replacement. There are a few gaps in the core / adapter methods where we could encode slightly more of this logic.
We can preserve dispatch on all legacy dbt_utils macros, so that a project / package maintainer can still intervene / override if needed.

What feels less good:

We had some explicit behaviors here previously, that are now implicit. Do they still work as before?
What's the right interface for package authors to access this functionality? Do they want to call {{ api.Column.translate_type('string') }}, {{ get_data_type('string') }}, or {{ type_string() }}?
Within dbt-core: We should aim to reconcile / consolidate the agate type conversion methods with Column class type translation.

Checklist

[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)

[x] BigQuery
[x] Postgres
[x] Redshift
[x] 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_utils.type_* macros instead of explicit datatypes (e.g. dbt_utils.type_timestamp() instead of TIMESTAMP — hah!

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

This turned out awesome! 💪

We had some explicit behaviors here previously, that are now implicit. Do they still work as before?

Is there anything we can do to make this feel more good? e.g., like adding in some kind of unit testing?

What's the right interface for package authors to access this functionality? Do they want to call {{ api.Column.translate_type('string') }}, {{ get_data_type('string') }}, or {{ type_string() }}?

It seems like package authors will be able to use any of those 3 no matter what, right? But we are just try to choose which of those we want to encourage?
Will the package authors have a variable in hand (like my_value = 'string')? If so, then either of these options make sense:

{{ get_data_type('string') }}
{{ api.Column.translate_type('string') }}

Otherwise, this is nice and pithy:

{{ type_string() }}

Is there anything we can do to make this feel more good? e.g., like adding in some kind of unit testing?

Definitely! I'll look into how we might do this

But we are just try to choose which of those we want to encourage?

Correct! Which of these do we want to encourage, in a world where they actually all do the same thing? Just a question of the right syntactic sugar to sprinkle in.

I've added tests for these data types, using both:

new (redefined) type_* macros
previous type_* macro definitions, manually readded in each Legacy test case

Two hesitations with the current implementation:

I'm doing a "more lenient" comparison for Postgres type__string(). Previously this returned varchar, now it returns text. Those are true aliases within Postgres, but (for some complex reasons) dbt doesn't perfectly map between them today. (Related: https://github.com/dbt-labs/dbt-core/issues/5238) I opted to make the test xfail, rather than truly pass or truly fail.
What should type_timestamp do on BigQuery? The most straightforward answer is, return a timestamp, and that's what it does today. But on other databases, timestamp means (by default) timestamp without time zone. On BigQuery that's datetime, whereas timestamp always means timestamp with time zone. Other macros (e.g. dateadd) return datetime values on BigQuery. I was able to get this working and these tests passing as is, and I think it's simplest for everyone if timestamp just means timestamp. But I also think we might do well to encourage folks to use more-precise types (datetime, timestampntz, timestamptz) that have clear and consistent analogues across databases.

All of the actual changes for this PR are happening in this repo only, for now. Things we could do in core/plugins to make the code here slightly cleaner:

Move the "syntactic sugar" of get_data_type(x) into dbt-core — it's just a wrapper for api.Column.translate_type(x), which is already there
Update the BigQueryColumn.numeric_type function to never return parametrized numeric types. They're technically supported on BQ, but a real nightmare to use.

I removed cross_db_utils/base_cross_db_macro.py and cross_db_utils/fixture_cross_db_macro.py because I realized they were unused. Not exactly related to this PR, though, so I can kick out that change if preferred.

Looks great to me!
@jtcohen6 Do these sound like the right next steps?

Merge https://github.com/dbt-labs/dbt-core/pull/5428 (you)
Update requirements.txt in this PR (you or me)
Merge this PR (me)
Open PR to resolve docs.getdbt.com #1644 (me), review (you), merge (me)


Company Page - Contact permission is not given then also contact and position display in company page

Describe the bug
https://www.berrycast.com/conversations/1476652c-a54a-522a-b127-4d9934f4061e

https://www.berrycast.com/conversations/f633efff-2853-506f-8002-0df39b36814a


time: plumb in time-source rather than calling time(nullptr)

in server/server.cc, start_time_ is initialized with time(nullptr) -- we should use TimeSource, there and elsewhere.

Hi @jmarantz ,
I'd like to take it !

Great! Looking forward to helping out with reviews.

Cross referencing an earlier attempt at this: https://github.com/envoyproxy/envoy/pull/7166

still working on it

@jmarantz @dichen16  @derekargueta
Should this issue be closed now that the PR has been merged, or is there more to do on it?

yes thanks!

There's still 3 other cases of time(nullptr);
https://github.com/envoyproxy/envoy/blob/4b69ef3d2da17f1239ae76367fc217c84118ef2d/source/server/server.cc#L60
https://github.com/envoyproxy/envoy/blob/4b69ef3d2da17f1239ae76367fc217c84118ef2d/source/server/server.cc#L193
https://github.com/envoyproxy/envoy/blob/c5f4302325223765b660f0f366ce25bf8570e7a5/test/common/router/router_upstream_log_test.cc#L313 (this one's just a test, but using TimeSource can help make it more accurate and not rely on a generous 300 second window for the test expectation)

I was thinking a nice follow-up after fixing these is to add a time(nullptr) check to check_format.py


Add timestamp to availability tests.

What
This makes it much easier to correlate any failures with CF logs etc.
How to review
Code review. Run availability tests and verify output looks good.
Who can review
Anyone but myself (and probably @dcarley whose commit I lifted this from)

Closing for further refinements.

I've reworked this to use (mostly) constant-width formatting for the output.

Works well:
2017-01-23 11:26:45.84 UTC: Duration:   45.30s, Requests:   454, Non 200 Requests:   0, Success Rate: 100.00%
2017-01-23 11:26:50.86 UTC: Duration:   50.30s, Requests:   504, Non 200 Requests:   0, Success Rate: 100.00%
2017-01-23 11:26:55.88 UTC: Duration:   55.30s, Requests:   554, Non 200 Requests:   0, Success Rate: 100.00%
2017-01-23 11:27:00.96 UTC: Duration:   60.40s, Requests:   605, Non 200 Requests:   0, Success Rate: 100.00%

Thanks for the improvement, merging.


Error using custom environment

I have created a custom environment using gym interface. In my agent code when I run
from stable_baselines import ...
from VAV_Env import VAVenv

env = DummyVecEnv([lambda : VAVenv])

I get an error
AttributeError: 'NoneType' object has no attribute 'shape'

My env code looks like
# -*- coding: utf-8 -*-
"""
Created on Tue Oct 22 22:55:45 2019

@author: VenkateshChinni
"""

import gym
from gym import spaces

import rom_vav_150mm_polyreg as rom
import numpy as np
import random

class VAVenv(gym.Env):

    def __init__(self):
        # Zone temperature set point and limits
        self.temp_sp = 24
        self.temp_sp_max = 24.5
        self.temp_sp_min = 23.7

        # no; of hours in an episode and time interval for each step
        self.MAXSTEPS = 11
        self.time_interval = 5./60. #in hrs

        # constants
        self.zone_volume = 775

        # action bounds
        self.cfm_min = 50
        self.cfm_max = 550

        # state bounds
        # time, volume, load, sat, rat
        self.low_state = np.array([1,self.zone_volume,0.3,12,21])
        self.high_state = np.array([11,self.zone_volume,1,20,26])

        # continuous actions space
        self.action_space = spaces.Box(low = self.cfm_min, high = self.cfm_max, shape=(1,), dtype=np.float32)

        # continuous state space
        self.observation_space = spaces.Box(low=self.low_state, high=self.high_state, dtype=np.float32)

        self.reset()

    def step(self,action):
        pass

    def reset(self):
        self.state = np.array(0,self.zone_volume,0.5,np.random.uniform(low=12,high=20),
                              np.random.uniform(low = 21,high = 26))
        return np.array(self.state)

Traceback (most recent call last):

  File "<ipython-input-5-b7cef7282748>", line 1, in <module>
    env = DummyVecEnv([lambda : VAVenv])

  File "C:\Users\VenkateshChinni\.conda\envs\py36\lib\site-packages\stable_baselines\common\vec_env\dummy_vec_env.py", line 23, in __init__
    self.keys, shapes, dtypes = obs_space_info(obs_space)

  File "C:\Users\VenkateshChinni\.conda\envs\py36\lib\site-packages\stable_baselines\common\vec_env\util.py", line 71, in obs_space_info
    shapes[key] = box.shape

AttributeError: 'NoneType' object has no attribute 'shape'

Hello, the problem come from the instantiation of your env, you forgot the ().
This will work:
env = DummyVecEnv([lambda : VAVenv()])

Then I get error:
    env = DummyVecEnv([lambda : env()])
TypeError: 'SimEnv' object is not callable

@Ricahrd-Li Please follow the examples in documentations (you need to pass a function that creates an environment to DummyVecEnv, not an environment). I also recommend moving on to using stable-baselines3.


Extra | on filter produces ugly error message

Created a template with body {{ "failure" || upcase }}.
This produced the following error:
IndexError: list index out of range
   File "liquid/environment.py", line 294, in from_string
    parse_tree = self.parse(source)
  File "liquid/environment.py", line 262, in parse
    parse_tree = parser.parse(TokenStream(token_iter))
  File "liquid/parse.py", line 117, in parse
    statements.append(self.parse_statement(stream))
  File "liquid/parse.py", line 135, in parse_statement
    node = tag.get_node(stream)
  File "liquid/tag.py", line 32, in get_node
    return self.parse(stream)
  File "liquid/builtin/tags/assign_tag.py", line 73, in parse
    expr = self.env.parse_filtered_expression_value(expression)
  File "liquid/expressions/filtered/parse.py", line 164, in parse
    filters = [parse_filter(_tokens) for _tokens in split_at_pipe(parts[1])]
  File "liquid/expressions/filtered/parse.py", line 164, in <listcomp>
    filters = [parse_filter(_tokens) for _tokens in split_at_pipe(parts[1])]
  File "liquid/expressions/filtered/parse.py", line 130, in parse_filter
    name = tokens[0][2]

Suggest instead trapping the IndexError and if we can't identify the typo easily, at least provide something more actionable (e.g. the line number of the template where the issue occurred).

Hi @mikestack-tuono,
That should indeed have raised a LiquidSyntaxError. An oversight on my part. Thanks for letting me know.
This particular bug has been fixed in Python Liquid version 1.1.7. More generally, future "unexpected" parsing errors will be caught and raised as a Python Liquid Error with a message of "unexpected liquid parsing error" and its __cause__ set to the offending exception.


Wrong Picture for Dorimon Pre-Release

The Alt art is taken the slot of the pre-release stamped card

Should be fixed in the next update, sorry for the trouble :)


GPU code generation: User-specified block/thread/warp location

@kylosus

Heya, what's the status of this PR?

@BenWeber42 Ready for review


[libtcod] Update to 1.22.1

Describe the pull request

What does your PR fix?
Updates to the latest version.  Adds the png and zlib features, default on.
In addition default features were missing from the previous port and are now added (I likely got confused by looking at the libtcod project manifest instead of the port manifest.)

Which triplets are supported/not supported?
Yes.

Yes

All features are tested successfully in the following triplet:

x86-windows
x64-windows
x64-windows-static

Thank you!


update hostnames and ports

this commit gets the hostname info from the backend that now displays info from public or vpc endpoints, depending on the service setup.
Issues
Use "closes #XX" to have the issue closed when this merged.
Related PRs
Any related PRs from other repos or branches
Checklist

[ ] Well formatted git commit message (see these guidelines)
[ ] Unit test coverage of new code
[ ] Document new features to the main README

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Probably should remove cloud-backend from CODEOWNERS, it's a bit too broad for reviews

without VPC
Current example:
# setup ###########################
terraform {
  required_providers {
    timescale = {
      source  = "registry.terraform.io/providers/timescale"
      version = "~> 1.0"
    }
  }
}

provider "timescale" {
  project_id = var.ts_project_id
  access_key = var.ts_access_key
  secret_key = var.ts_secret_key
}

variable "ts_project_id" {
  type    = string
  default = "xo62e6nobm"
}

variable "ts_access_key" {
  type = string
}

variable "ts_secret_key" {
  type = string
}

# resources ################################
## main service
resource "timescale_service" "tf-test" {
  name                      = "tf-test"
  milli_cpu                 = 500
  memory_gb                 = 2
  region_code               = "us-west-2"
  connection_pooler_enabled = true
  enable_ha_replica         = true
}

# outputs ##################
## host connection info
output "host_addr" {
  value       = timescale_service.tf-test.hostname
  description = "Service Host Address"
}

output "host_port" {
  value       = timescale_service.tf-test.port
  description = "Service Host port"
}

## ha-replica connection info
output "replica_addr" {
  value       = timescale_service.tf-test.replica_hostname
  description = "Service Replica Host Address"
}

output "replica_port" {
  value       = timescale_service.tf-test.replica_port
  description = "Service Replica Host port"
}

## pooler connection info
output "pooler_addr" {
  value       = timescale_service.tf-test.pooler_hostname
  description = "Service Pooler Host Address"
}

output "pooler_port" {
  value       = timescale_service.tf-test.pooler_port
  description = "Service Pooler Host port"
}

It displays:
❯ terraform output
host_addr = "prd2y48ymp.xo62e6nobm.tsdb.cloud.timescale.com"
host_port = 31688
pooler_addr = "prd2y48ymp.xo62e6nobm.tsdb.cloud.timescale.com"
pooler_port = 30456
replica_addr = "prd2y48ymp-repl.xo62e6nobm.tsdb.cloud.timescale.com"
replica_port = 39701

with VPC
# setup ###########################
terraform {
  required_providers {
    timescale = {
      source  = "registry.terraform.io/providers/timescale"
      version = "~> 1.0"
    }
  }
}

provider "timescale" {
  project_id = var.ts_project_id
  access_key = var.ts_access_key
  secret_key = var.ts_secret_key
}

variable "ts_project_id" {
  type    = string
  default = "xo62e6nobm"
}

variable "ts_access_key" {
  type = string
}

variable "ts_secret_key" {
  type = string
}

# resources ################################
## main service
resource "timescale_service" "tf-test" {
  name                      = "tf-test"
  milli_cpu                 = 500
  memory_gb                 = 2
  region_code               = "us-west-2"
  connection_pooler_enabled = true
  enable_ha_replica         = true
  vpc_id                    = timescale_vpcs.vpc-diff-network.id
}

resource "timescale_vpcs" "vpc-diff-network" {
  name        = "vpc-diff-network"
  cidr        = "<IP_ADDRESS>/24"
  region_code = "us-west-2"

  lifecycle {
    prevent_destroy = true
  }
}

# outputs ##################
## host connection info
output "host_addr" {
  value       = timescale_service.tf-test.hostname
  description = "Service Host Address"
}

output "host_port" {
  value       = timescale_service.tf-test.port
  description = "Service Host port"
}

## ha-replica connection info
output "replica_addr" {
  value       = timescale_service.tf-test.replica_hostname
  description = "Service Replica Host Address"
}

output "replica_port" {
  value       = timescale_service.tf-test.replica_port
  description = "Service Replica Host port"
}

## pooler connection info
output "pooler_addr" {
  value       = timescale_service.tf-test.pooler_hostname
  description = "Service Pooler Host Address"
}

output "pooler_port" {
  value       = timescale_service.tf-test.pooler_port
  description = "Service Pooler Host port"
}

❯ terraform output
host_addr = "prd2y48ymp.xo62e6nobm.vpc.tsdb.forge.timescale.com"
host_port = 5432
pooler_addr = "prd2y48ymp-pooler.xo62e6nobm.vpc.tsdb.forge.timescale.com"
pooler_port = 5432
replica_addr = "prd2y48ymp-repl.xo62e6nobm.vpc.tsdb.forge.timescale.com"
replica_port = 5432


Added files via upload

@jstephens-concordia There are several files in the request, along with file.zip. It must not be there. Please remove file.zip and make pull request again.  I have to close this request without merging. Thank you for your understanding.


point intersection fails with some cells due to 0 length edges

I have a triangular cell near a corner of a generated diagram, unfortunately it thinks it has 4 edges so the point intersection test does not work correctly
cells[0].halfedges.forEach( he => {
  console.log(
    he.getStartpoint().x,
    he.getStartpoint().y,
    he.getEndpoint().x,
    he.getEndpoint().y,
  )
})

512 0 562.01 0
562.01 63.26 578.06 63.26
578.06 0 578.068 0
512 0 512 0

I fixed to 2dp for clarity here, I havent done anything funky, just fed a list of sites into the generator.
I could prune before running the test but figured that should probably be a core function, and I'm not sure if just pruning zero length edges is going to break something else.

My apologies, I was shuffling some edge vertices which creates these "bad" vertices.


update release-2.4 branch to go 1.18

Signed-off-by: Ray Harris<EMAIL_ADDRESS>

/lgtm

/lgtm


Tracking: scale in Meta Service

This a tracking issues for scale ability in Meta Service, steps as follow:

[ ] support frontend/backend evict/join in meta, all worker should have one state in Starting/Ready/Evicted.
[x] support source/table/mview node init in new compute node.
[ ] support actor reschedule in stream manager, including actor move/expanding/reduction.
[ ] support fragment sharing in stream manager, including fragment search/match/config change etc.
[ ] ...

Replaced by #3750.


v1.15 Backports 2024-02-16

[ ] #30732 (@YutaroHayakawa)

Once this PR is merged, a GitHub action will update the labels of these PRs:
 30732

/test-backport-1.15

Marking this ready to merge for tophat to check :eyes:


UI: Add support for k8s 1.13 on EKS

UI fixes are needed for https://github.com/rancher/rancher/issues/20992

Somewhat related: https://github.com/rancher/rancher/issues/20759

Version: master-head (6/26/19)
Validated new UI option to pick 1.13 k8s version for EKS, new regions, allowed instance type values, etc. Validated amazonElasticContainerServiceConfig. Smoke tested creating various EKS clusters including older k8s versions (make sure 1.12 creates 1.12, 1.11 creates 1.11, etc).
Validated that UI shows correct k8s version for the cluster and nodes.
HTTP looks good, API looks good, compare to AWS console looks good, all checks passed. I was not able to test all regions as our account does not have access to them all (cannot fully test those) but the PR looks good to me.
I also did some spot checks to ensure AMI id's are correct for each k8s version (for regions I have access to via aws console).
Regions:

Allowed values for instances too large to fit in screenshot but looks correct.
UI does not pick latest as default, but this is a separate issue tracked in #20759


Avoid deserializing jobs just for counts

Problem
To render the counts per queue on the waiting page, we fetch all jobs in that resque, deserializing them, then count them per queue, basically throwing out all the job data, which we don't need.  This is super slow
Solution
Stop doing that and instead just fetch the counts, which is already supported by the backend.

This leaves the "get waiting jobs" stuff around.  I don't think it's being used, but I only want to do one thing at a time.


Added 8-bit Quantization support to OneHot.

This is to solve issue #27765.

@alanchiao Could you PTAL and approve.

@alanchiao , could you please review the PR and provide feedback. This is kind of important PR for me.
Regards
Amit

Looking at it now

Looking at it now

@alanchiao , thank you so much for your time on the PR, can you please provide your feedback for the same. I would like to see this PR though with your help  and would put in the required effort to do so.
Regards
Amit

@alanchiao , thanks for spending time on the PR and providing the feedback, the idea here is that if we want to convert and run the ner_model.pb to tflite we need to quantize one_hot operator, this is basically used for word embedding problems, and in this case for Chinese entity recognition,
I have checked the graph of the above model as well and the on_val and off_val are 1 and 0 respectively, the output of one_hot is directed to mat_mul which again will not have any problems with the quantized output which we have suggested in this PR.
I hope you are satisfied with the above explanation and would approve the PR.
Awaiting your reply.
Regards
Amit

@alanchiao , i have updated the code with support for quantization from tools and updated kernel registry with updated version for one_hot kernel.
Regards
Amit

@alanchiao , any update from your side, could you please review the code and provide your feedback
Regards
Amit

@alanchiao , can you pls spend some time on the PR and provide your feedback.
Regards
Amit

Can one of the admins verify this patch?

@amitsrivastava78 Could you please resolve the conflicts? Thanks!

It has been 15 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.


Optimize validate progress

For #4793.

Pull Request Test Coverage Report for Build 2132

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 59.937%

Totals

Change from base Build 1095:
0.07%

Covered Lines:
12561

Relevant Lines:
20957

💛  - Coveralls


Interlocked class is marked unscriptable.

You cannot use the Interlocked class because of this error:
Bridge.Contract.EmitterException: Type System.Threading.Interlocked is marked as not usable from script
   at Bridge.Contract.BridgeTypes.ToJsName(IType type, IEmitter emitter, Boolean asDefinition, Boolean excludens, Boolean isAlias, Boolean skipMethodTypeParam, Boolean removeScope, Boolean nomodule, Boolean ignoreLiteralName, Boolean ignoreVirtual)
   at Bridge.Translator.MemberReferenceBlock.WriteSimpleTarget(ResolveResult resolveResult)
   at Bridge.Translator.MemberReferenceBlock.VisitMemberReferenceExpression()
   at Bridge.Translator.MemberReferenceBlock.EmitConversionExpression()
   at Bridge.Translator.ConversionBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.VisitMemberReferenceExpression(MemberReferenceExpression memberReferenceExpression)
   at ICSharpCode.NRefactory.CSharp.MemberReferenceExpression.AcceptVisitor(IAstVisitor visitor)
   at Bridge.Translator.InvocationBlock.VisitInvocationExpression()
   at Bridge.Translator.InvocationBlock.EmitConversionExpression()
   at Bridge.Translator.ConversionBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.VisitInvocationExpression(InvocationExpression invocationExpression)
   at ICSharpCode.NRefactory.CSharp.InvocationExpression.AcceptVisitor(IAstVisitor visitor)
   at Bridge.Translator.ExpressionListBlock.EmitExpressionList(IEnumerable`1 expressions, Expression paramArg)
   at Bridge.Translator.ExpressionListBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.InvocationBlock.VisitInvocationExpression()
   at Bridge.Translator.InvocationBlock.EmitConversionExpression()
   at Bridge.Translator.ConversionBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.VisitInvocationExpression(InvocationExpression invocationExpression)
   at ICSharpCode.NRefactory.CSharp.InvocationExpression.AcceptVisitor(IAstVisitor visitor)
   at Bridge.Translator.ExpressionBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.VisitExpressionStatement(ExpressionStatement expressionStatement)
   at ICSharpCode.NRefactory.CSharp.ExpressionStatement.AcceptVisitor(IAstVisitor visitor)
   at Bridge.Translator.Block.<>c__DisplayClass51_0.<DoEmitBlock>b__0(AstNode child)
   at System.Collections.Generic.List`1.ForEach(Action`1 action)
   at Bridge.Translator.Block.DoEmitBlock()
   at Bridge.Translator.Block.EmitBlock()
   at Bridge.Translator.Block.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.VisitBlockStatement(BlockStatement blockStatement)
   at ICSharpCode.NRefactory.CSharp.BlockStatement.AcceptVisitor(IAstVisitor visitor)
   at Bridge.Translator.VisitorMethodBlock.VisitMethodDeclaration(MethodDeclaration methodDeclaration)
   at Bridge.Translator.VisitorMethodBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.VisitMethodDeclaration(MethodDeclaration methodDeclaration)
   at Bridge.Translator.MethodBlock.EmitMethodsGroup(List`1 group)
   at Bridge.Translator.MethodBlock.EmitMethods(Dictionary`2 methods, Dictionary`2 properties, Dictionary`2 operators)
   at Bridge.Translator.MethodBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.ClassBlock.EmitStaticBlock()
   at Bridge.Translator.ClassBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.EmitBlock.DoEmit()
   at Bridge.Translator.AbstractEmitterBlock.Emit()
   at Bridge.Translator.Emitter.Emit()
   at Bridge.Translator.Translator.Translate()
   at Bridge.Build.BridgeCompilerTask.Execute()	JSILTests.Testing

Maybe it is because of nature of single threaded JS....
Can it be wrapped in some way to avoid build error?

I think it would be best if it's simply implemented with regular non-atomic operations for the sake of compatibility. JavaScript is single-threaded so it would never be a problem.


add a switch to set PrettyFormat with function SaveConfigData and SaveConfigFile

sometimes force change '=' to ' = ' will make the program‘s config don't work, such as the database Nebula Graph. So we need add a parameter to decide whether we use PrettyFormat.

https://github.com/unknwon/goconfig/pull/52


Cache library modules in buildDependencyModules

extractMavenDependencyInfo(library) is a fixed value within a request context. Cache their value across all targets in a request. This makes a substantial improvement when a large number of targets are queried.

the change looks good to me.
could you please also attach a small benchmark to indicate the improvement?

the change looks good to me. could you please also attach a small benchmark to indicate the improvement?

Let me know if this change makes sense as a benchmark.


Enhancement: Configure passport-jwt strategy for authentication using external JWT tokens

Discovery:
In the current authentication mechanism, LibreChat does not handle external JWT tokens, limiting the integration with third-party identity providers. The system lacks the ability to validate and authenticate users via JWT tokens issued by external services, which inhibits the ability to onboard users who are authenticated elsewhere.
Problem Definition:
The absence of support for external JWT tokens in LibreChat prevents authentication for users whose details are managed outside of the system. We need to implement a mechanism that intercepts incoming requests with JWT tokens, validates them, and grants access accordingly.
Motivations:
By configuring the passport-jwt strategy, we will:

Enable external JWT token validation, supporting third-party authentication providers.
Seamlessly integrate new users into the system via JWT tokens, improving flexibility and scalability of the authentication process.
Allow the platform to handle external user data more securely and efficiently.

Proposed Solution:

Install passport-jwt:
Add the required dependency for passport-jwt to the project.

Configure JWT options:
Define the extraction method for the JWT token (e.g., from the Authorization header) and configure the token verification with a secret or public key.

Implement JWT Strategy:
Implement the passport-jwt strategy to intercept requests, extract the JWT token, and validate it using the secret key. The strategy should handle cases where the JWT token is valid or invalid.

Handle Authenticated Users:
On successful validation, retrieve the associated user details from the database or create a new user if they do not exist in the system. This step ensures that external users are dynamically added to the database when authenticated through external JWT tokens.

Middleware Integration:
Integrate the passport-jwt strategy into the middleware of the application, ensuring that all protected routes use JWT validation.

Definition of Done:

[ ] passport-jwt is installed and correctly configured.
[ ] JWT tokens are extracted and validated using the configured strategy.
[ ] Authenticated users are either retrieved from the database or created dynamically.
[ ] The middleware is integrated to intercept requests and validate JWT tokens for protected routes.
[ ] Tests are performed to validate the correct operation of JWT authentication.

Additional Information:

Security Considerations: Ensure that secret keys for JWT validation are securely stored using environment variables or a secrets manager to prevent exposure.
Logging: Add logging at critical points in the JWT validation process to monitor failed and successful authentication attempts.

@tomasvalererealms said,
"#time 4h
Preparing the environment and working with the login/logout process trying to determine the correct controllers, headers and payloads"

@tomasvalererealms said, "I've been recreating the process of setting the JWT tokens and generating a full conversation through the rest API, I'm now creating a custom conversationId but I'm facing a blocker adding the chat title that (seems) to be mandatory."

#time 4h

#time 4


[Support]: The #     # for a failed transformer should have the proper yaml depth

What operating system are you using?

[X] Linux
[ ] macOS
[ ] Windows

What version of the tool are you using?
gh version 2.20.2 (2022-11-15)
gh actions-importer	github/gh-actions-importer	v1.0.1
actions-importer/cli	v1.0.14396
What happened?
https://github.com/actions/importer-labs/blob/173902d5bb22386408f0e4a0759ba31083d2d1c1/gitlab/5-custom-transformers.md?plain=1#L37-L51
Relevant log output
jobs:
  plan:
    runs-on: ubuntu-latest
    timeout-minutes: 60
    env:
      PLAN: plan.cache
      PLAN_JSON: plan.json
    steps:
    - uses: actions/checkout@v2
      with:
        fetch-depth: 20
        lfs: true
    - run: terraform plan -out=$PLAN
    - run: terraform show --json $PLAN | convert_report > $PLAN_JSON
#     # 'artifacts.terraform' was not transformed because there is no suitable equivalent in GitHub Actions

I understand that yaml will ignore the line entirely and this won't actually result in a later job being treated as not a child of jobs, but there's no particularly good reason not to have the first # have an indentation that corresponds to its depth in the yaml tree -- it's a lot easier to reason through if it did.

### Code of Conduct

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

Thanks for opening this issue! The location of these comment markers is intentional so that commented out sections of yaml will be aligned correctly if they were to be uncommented via keyboard shortcuts (i.e command + /).


Update ResponseStrings.uk-UA.json

Added new lines. Edited.

No dude. You need to edit strings on poeditor.


v2.19.0 introduced a breaking change

Describe the bug
QueryExecutor.beginExclusive was added in v2.19.0 which is a breaking change in a non-major release.
class SentryQueryExecutor extends QueryExecutor {
      ^^^^^^^^^^^^^^^^^^^
../../../../../.pub-cache/hosted/pub.dev/drift-2.19.0/lib/src/runtime/executor/executor.dart:62:17: Context: 'QueryExecutor.beginExclusive' is defined here.
  QueryExecutor beginExclusive();
                ^^^^^^^^^^^^^^
../../drift/lib/src/sentry_transaction_executor.dart:8:7: Error: The non-abstract class 'SentryTransactionExecutor' is missing implementations for these members:
 - QueryExecutor.beginExclusive
Try to either
 - provide an implementation,
 - inherit an implementation from a superclass or mixin,
 - mark the class as abstract, or
 - provide a 'noSuchMethod' implementation.

I added a fix in the sentry repo: https://github.com/getsentry/sentry-dart/pull/2162

Sorry about the breakage! I've considered this when making the change, but as the docs of QueryExecutor mention:

This is an internal api of drift, which can break often. If you want to implement custom database backends, consider using the new backends API.

QueryExecutor is kind of internal in the sense that it's not meant to be implemented directly. So I didn't consider this to be breaking, but obviously I should do a better job pointing that out, as the docstring is not really all that visible. I will also keep this in mind for further changes.
For sentry, which I assume is wrapping an existing implementation to add instrumentation, I suggest using the QueryInterceptor class instead. Ideally that should also make the implementation a bit simpler since you don't need to add different classes for transactions and so on. But the fix adding beginExclusive works too of course.

@simolus3 all good!
iirc you've added the interceptor after we've talked about the drift integration so we didn't have that option back then but I'll deprecate the current api soon in favour of using the interceptor


rust: enhance tests to compare rtmr

Most cases passed except on case "test_replay_cc_eventlog_with_invalid_input" failed which is the known issue that will be resolved after these 2 patches be merged:

Add bound check in cc-trusted-api https://github.com/cc-api/cc-trusted-api/pull/108
Pass the parameter for bound check in cc-trusted-vmsdk https://github.com/cc-api/cc-trusted-vmsdk/pull/19

So this change can be safely merged as it is independent from others.


Status topics have not removed

I created some connectors and deleted them, but topics that created for connector status has remained and I cannot delete them.
I tried to delete topics from zookeepers and remove kafka log directories but topics created again.
This is my connector config:
{
"name": "ALL",
"config": {
"connector.class": "io.streamthoughts.kafka.connect.filepulse.source.FilePulseSourceConnector",
"task.reader.class": "io.streamthoughts.kafka.connect.filepulse.reader.XMLFileInputReader",
"tasks.max": "1",
"fs.scan.directory.path": "/data/ALLRecieved/",
"fs.scan.interval.ms": "10000",
"xpath.expression": "//BuyData",
"offset.strategy": "name",
"internal.kafka.reporter.topic": "online.data.status",
"fs.cleanup.policy.class": "io.streamthoughts.kafka.connect.filepulse.clean.LogCleanupPolicy",
"fs.scan.filters": "io.streamthoughts.kafka.connect.filepulse.scanner.local.filter.RegexFileListFilter",
"topic": "online.data",
"internal.kafka.reporter.bootstrap.servers": "kafka-1:9092,kafka-2:9092,kafka-3:9092",
"file.filter.regex.pattern": ".*.xml$"
}
}

Hi @AzamAhmadloo, which topics are you talking about exactly? Topics -config, -offset and -status are automatically created by Kafka Connect framework. Which version of the connector are you using ?

Thanks for your reply.
Every created connector has two topics, one for data and another one for status that the topics are specifying in connector config. And these are my example topics:
"internal.kafka.reporter.topic": "online.data.status",
"topic": "online.data",
I'm using confluent-6.1.1 for kafka connect service.
I removed connectors and try to remove related topics. Data topic ( in my sample online.data) deleted successfully but the other one which was for connector status has remained ( in my sample online.data.status ).
I can't find the relation between remaining topics and connectors. Also I try to remove topics from zookeeper and kafka logis manually, but they created again after a short time.


Multiple Subs - Speaker names have different numbers of indices. - program execution has stopped!

Multiple Sub measurements from Audyssey are labeled:
SW10-SW15, SW20-SW25
When the titleIndices are being built, I'm guessing this means that key SW has the value [10, ..., 20, ...] instead of having two keys for SW1 and SW2.

Subwoofer name in the ady file is already SW1, only adding indices from 0
to number of pic positions to each detected channel.
Sent from Gmail Mobile
On Wed 3. Apr 2024 at 04:16, David Campbell @.***>
wrote:

Multiple Sub measurements from Audyssey are labeled:
SW10-SW15, SW20-SW25
When the titleIndices are being built, I'm guessing this means that key SW
has the value [10, ..., 20, ...] instead of SW1 and SW2.
—
Reply to this email directly, view it on GitHub
https://github.com/ObsessiveCompulsiveAudiophile/AudysseyOne/issues/11,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACLH4TDGPWUICXE6XKGUPQ3Y3NJ5JAVCNFSM6AAAAABFULVI7CVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDCNZQGU4DEOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Line 530 of v1-2:
const titleKey = title.replace(/\d+/g, '')
The title SW10 is getting shortened to SW isn’t it?
On Tue, Apr 2, 2024 at 11:32 PM Serkan Gür @.***> wrote:

Subwoofer name in the ady file is already SW1, only adding indices from 0
to number of pic positions to each detected channel.
Sent from Gmail Mobile
On Wed 3. Apr 2024 at 04:16, David Campbell @.***>
wrote:

Multiple Sub measurements from Audyssey are labeled:
SW10-SW15, SW20-SW25
When the titleIndices are being built, I'm guessing this means that key
SW
has the value [10, ..., 20, ...] instead of SW1 and SW2.
—
Reply to this email directly, view it on GitHub
https://github.com/ObsessiveCompulsiveAudiophile/AudysseyOne/issues/11,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ACLH4TDGPWUICXE6XKGUPQ3Y3NJ5JAVCNFSM6AAAAABFULVI7CVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDCNZQGU4DEOI>

.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
https://github.com/ObsessiveCompulsiveAudiophile/AudysseyOne/issues/11#issuecomment-2033511162,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATMEXMNOT6CZB7NQLXFJIDY3OA5PAVCNFSM6AAAAABFULVI7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZTGUYTCMJWGI
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

Yes, that line removes all digits from the name.
On Wed, 3 Apr 2024 at 15:28, David Campbell @.***>
wrote:

Line 530 of v1-2:
const titleKey = title.replace(/\d+/g, '')
The title SW10 is getting shortened to SW isn’t it?
On Tue, Apr 2, 2024 at 11:32 PM Serkan Gür @.***> wrote:

Subwoofer name in the ady file is already SW1, only adding indices from
0
to number of pic positions to each detected channel.
Sent from Gmail Mobile
On Wed 3. Apr 2024 at 04:16, David Campbell @.***>
wrote:

Multiple Sub measurements from Audyssey are labeled:
SW10-SW15, SW20-SW25
When the titleIndices are being built, I'm guessing this means that
key
SW
has the value [10, ..., 20, ...] instead of SW1 and SW2.
—
Reply to this email directly, view it on GitHub
<
https://github.com/ObsessiveCompulsiveAudiophile/AudysseyOne/issues/11>,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/ACLH4TDGPWUICXE6XKGUPQ3Y3NJ5JAVCNFSM6AAAAABFULVI7CVHI2DSMVQWIX3LMV43ASLTON2WKOZSGIZDCNZQGU4DEOI>

.
You are receiving this because you are subscribed to this
thread.Message
ID: @.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/ObsessiveCompulsiveAudiophile/AudysseyOne/issues/11#issuecomment-2033511162>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AATMEXMNOT6CZB7NQLXFJIDY3OA5PAVCNFSM6AAAAABFULVI7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZTGUYTCMJWGI>

.
You are receiving this because you authored the thread.Message ID:
@.***
com>

—
Reply to this email directly, view it on GitHub
https://github.com/ObsessiveCompulsiveAudiophile/AudysseyOne/issues/11#issuecomment-2034464926,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACLH4TDCIBKEHODCAEAYGXTY3PYWVAVCNFSM6AAAAABFULVI7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZUGQ3DIOJSGY
.
You are receiving this because you commented.Message ID:
@.***
com>

I'm also having this problem.  The zip from Audyssey One for my .ady with two subs generates measurements SW10-17 and SW20-27 (eight measurements each).  I get the same error as above.  If I delete SW20-21, the process continues.  Is this workflow not compatible with multiple subs?


Thanks; announcing an application; feature request

Hi @torshind
Just wanted to say thanks for creating this library!
I discovered it this morning and basically had to stop everything and build a linux client, specifically tailored to dmenu users like myself.
I now have a 1password experience on linux that is exactly the way I want (modeled after passmenu which I loved, but never really migrated to because of lack of mobile, windows, and mac support). It actually goes a step further and not only can it manage the pasteboard but it can use xdotool to input directly into the focused application -- so I don't need a browser extension and can use it at terminal password prompts, etc.
It can be found here https://github.com/kfatehi/1passmenu
I just wish I could use it to create new logins and generate passwords too! If you add support for that I'll be sure to extend 1passmenu

Hi @kfatehi
Thanks for your interest! :)
The project was on standby for someone who's interested in developing some front end.
No ETA because the work to do is really huge! I'll hope that I'll find some spare time to continue it...

Hi @kfatehi
I've update the code with a lot of fixes and item creation support.
New items and folder are created only in the local database, syncing isn't supported at the moment. I think (hope) that the interface for reading/writing should be pretty stable now. To learn the new way to get decrypted overview and data and to create new items, you ca refer to the main.cpp test source.
Next steps are syncing support and password generation.
Bye!

@torshind Great! Thank you for the update. I've also been adding features to 1passmenu such as fuzzy-matching X11 window title and an "autologin" feature which types the username, , password,  sequence typical of logins.
Next time I work on it I'll use the new version and test.


wrong type of datapoints after upgrade

I'm sorry, but after updating to v1.1.1, the same log entries sometimes appear again.I stopped the adapter and deleted all data points on the objects. The v1.1.1. installed via GitHub Link over it and restarted the adapter 2x. What did 1 wrong?`

synology.0
2021-08-09 11:48:00.704
info
(30961) State value to set for "synology.0.DiskStationManager.vol_info.volume_1.used_size" has to be type "number" but received type "string"

synology.0
2021-08-09 11:48:00.654
info
(30961) State value to set for "synology.0.DiskStationManager.vol_info.volume_1.total_size" has to be type "number" but received type "string"

synology.0
2021-08-09 11:48:00.653
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_4.capacity" has to be type "number" but received type "string"

synology.0
2021-08-09 11:48:00.648
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_4.ebox_order" has to be type "string" but received type "number"

synology.0
2021-08-09 11:48:00.646
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_3.capacity" has to be type "number" but received type "string"

synology.0
2021-08-09 11:48:00.645
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_3.ebox_order" has to be type "string" but received type "number"

synology.0
2021-08-09 11:48:00.640
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_2.capacity" has to be type "number" but received type "string"

synology.0
2021-08-09 11:48:00.639
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_2.ebox_order" has to be type "string" but received type "number"

synology.0
2021-08-09 11:48:00.631
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_1.capacity" has to be type "number" but received type "string"

synology.0
2021-08-09 11:48:00.630
info
(30961) State value to set for "synology.0.DiskStationManager.hdd_info.sata_drive_1.ebox_order" has to be type "string" but received type "number"

synology.0
2021-08-09 11:48:00.624
info
(30961) State value to set for "synology.0.DiskStationManager.info.upgrade_ready" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:48:00.623
info
(30961) State value to set for "synology.0.DiskStationManager.info.is_system_crashed" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:48:00.621
info
(30961) State value to set for "synology.0.DiskStationManager.info.memory_size" has to be type "string" but received type "number"

synology.0
2021-08-09 11:47:42.968
info
(30961) State value to set for "synology.0.FileStation.info.uid" has to be type "string" but received type "number"

synology.0
2021-08-09 11:47:42.966
info
(30961) State value to set for "synology.0.FileStation.info.support_virtual.enable_remote_mount" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.964
info
(30961) State value to set for "synology.0.FileStation.info.support_virtual.enable_iso_mount" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.963
info
(30961) State value to set for "synology.0.FileStation.info.support_vfs" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.962
info
(30961) State value to set for "synology.0.FileStation.info.support_sharing" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.961
info
(30961) State value to set for "synology.0.FileStation.info.support_file_request" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.959
info
(30961) State value to set for "synology.0.FileStation.info.items.2" has to be type "string" but received type "object"

synology.0
2021-08-09 11:47:42.958
info
(30961) State value to set for "synology.0.FileStation.info.items.1" has to be type "string" but received type "object"

synology.0
2021-08-09 11:47:42.925
info
(30961) State value to set for "synology.0.FileStation.info.items.0" has to be type "string" but received type "object"

synology.0
2021-08-09 11:47:42.918
info
(30961) State value to set for "synology.0.FileStation.info.is_manager" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.916
info
(30961) State value to set for "synology.0.FileStation.info.enable_list_usergrp" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:42.914
info
(30961) State value to set for "synology.0.DiskStationManager.info.temperature_warn" has to be type "string" but received type "boolean"

synology.0
2021-08-09 11:47:41.584
info
(30961) DSM 6

synology.0
2021-08-09 11:47:36.166
info
(30961) Connecting to Synology <IP_ADDRESS>:5000

synology.0
2021-08-09 11:47:36.060
info
(30961) starting. Version 1.1.1 in /opt/iobroker/node_modules/iobroker.synology, node: v12.22.2, js-controller: 3.3.15

synology.0
2021-08-09 11:47:12.205
info
(24661) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

Same here!

fixed in next version 1.1.2

Hi,
with V1.1.3 i have the following log entries.
2021-08-24 19:56:53.230 - info: synology.0 (3011) starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.synology, node: v12.22.5, js-controller: 3.3.15
2021-08-24 19:56:53.281 - info: synology.0 (3011) Connecting to Synology <IP_ADDRESS>:5001
2021-08-24 19:56:57.436 - info: synology.0 (3011) DSM 1
2021-08-24 19:56:58.960 - info: synology.0 (3011) State value to set for "synology.0.DiskStationManager.info.temperature_warn" has to be type "string" but received type "boolean"
2021-08-24 19:56:58.962 - info: synology.0 (3011) State value to set for "synology.0.DiskStationManager.info.uptime" has to be type "string" but received type "number"
2021-08-24 19:56:58.964 - info: synology.0 (3011) State value to set for "synology.0.FileStation.info.enable_list_usergrp" has to be type "string" but received type "boolean"
2021-08-24 19:56:58.966 - info: synology.0 (3011) State value to set for "synology.0.FileStation.info.is_manager" has to be type "string" but received type "boolean"
2021-08-24 19:56:58.968 - info: synology.0 (3011) State value to set for "synology.0.FileStation.info.items.0" has to be type "string" but received type "object"
2021-08-24 19:56:58.969 - info: synology.0 (3011) State value to set for "synology.0.FileStation.info.items.1" has to be type "string" but received type "object"
2021-08-24 19:56:58.971 - info: synology.0 (3011) State value to set for "synology.0.FileStation.info.items.2" has to be type "string" but received type "object"
2021-08-24 19:56:58.973 - info: synology.0 (3011) State value to set for "synology.0.FileStation.info.support_file_request" has to be type "string" but received type "boolean"
2021-08-24 19:56:58.975 - info: synology.0 (3011) State value to set for "synology.0.FileStation.info.support_sharing" has to be type "string" but received type "boolean"
2021-08-24 19:56:58.993 - info: synology.0 (3011) State value to set for "synology.0.FileStation.info.support_vfs" has to be type "string" but received type "boolean"
2021-08-24 19:56:58.994 - info: synology.0 (3011) State value to set for "synology.0.FileStation.info.support_virtual.enable_iso_mount" has to be type "string" but received type "boolean"
2021-08-24 19:56:58.996 - info: synology.0 (3011) State value to set for "synology.0.FileStation.info.support_virtual.enable_remote_mount" has to be type "string" but received type "boolean"
2021-08-24 19:56:59.006 - info: synology.0 (3011) State value to set for "synology.0.FileStation.info.uid" has to be type "string" but received type "number"

Many thanks

Update:
After stopping the Adapter, delete object tree and restart adapter the following entries are in the log.
2021-08-24 20:08:00.181 - info: synology.0 (21416) starting. Version 1.1.3 in /opt/iobroker/node_modules/iobroker.synology, node: v12.22.5, js-controller: 3.3.15
2021-08-24 20:08:00.222 - info: synology.0 (21416) Connecting to Synology <IP_ADDRESS>:5001
2021-08-24 20:08:03.709 - info: synology.0 (21416) DSM 1
2021-08-24 20:08:05.281 - warn: synology.0 (21416) State "synology.0.DiskStationManager.info.codepage" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.285 - warn: synology.0 (21416) State "synology.0.DiskStationManager.info.model" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.288 - warn: synology.0 (21416) State "synology.0.DiskStationManager.info.ram" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.292 - warn: synology.0 (21416) State "synology.0.DiskStationManager.info.serial" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.296 - warn: synology.0 (21416) State "synology.0.DiskStationManager.info.temperature" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.298 - warn: synology.0 (21416) State "synology.0.DiskStationManager.info.temperature_warn" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.300 - warn: synology.0 (21416) State "synology.0.DiskStationManager.info.time" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.302 - warn: synology.0 (21416) State "synology.0.DiskStationManager.info.uptime" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.305 - warn: synology.0 (21416) State "synology.0.DiskStationManager.info.version" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.307 - warn: synology.0 (21416) State "synology.0.DiskStationManager.info.version_string" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.309 - warn: synology.0 (21416) State "synology.0.FileStation.info.enable_list_usergrp" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.311 - warn: synology.0 (21416) State "synology.0.FileStation.info.hostname" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.314 - warn: synology.0 (21416) State "synology.0.FileStation.info.is_manager" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.315 - warn: synology.0 (21416) State "synology.0.FileStation.info.items.0" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.317 - warn: synology.0 (21416) State "synology.0.FileStation.info.items.1" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.320 - warn: synology.0 (21416) State "synology.0.FileStation.info.items.2" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.322 - warn: synology.0 (21416) State "synology.0.FileStation.info.support_file_request" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.324 - warn: synology.0 (21416) State "synology.0.FileStation.info.support_sharing" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.326 - warn: synology.0 (21416) State "synology.0.FileStation.info.support_vfs" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.329 - warn: synology.0 (21416) State "synology.0.FileStation.info.support_virtual.enable_iso_mount" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.331 - warn: synology.0 (21416) State "synology.0.FileStation.info.support_virtual.enable_remote_mount" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.333 - warn: synology.0 (21416) State "synology.0.FileStation.info.support_virtual_protocol.0" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.336 - warn: synology.0 (21416) State "synology.0.FileStation.info.support_virtual_protocol.1" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.338 - warn: synology.0 (21416) State "synology.0.FileStation.info.support_virtual_protocol.2" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.339 - warn: synology.0 (21416) State "synology.0.FileStation.info.system_codepage" has no existing object, this might lead to an error in future versions
2021-08-24 20:08:05.366 - warn: synology.0 (21416) State "synology.0.FileStation.info.uid" has no existing object, this might lead to an error in future versions

@MeisterTR ?
@MMeinhardt1 For the future: adding posts to a closed issue normally makes NO sense. The way is to open an enw issue

Hi, i have the same, after update to 1.1.3 there are 99 warn infos of this error
`

synology.0
2021-09-16 17:00:39.747
warn
State "synology.0.FileStation.sharing.list" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.746
warn
State  "synology.0.DiskStationManager.vol_info.volume_1.desc" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.744
warn
State  "synology.0.DiskStationManager.vol_info.volume_1.used" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.742
warn
State  "synology.0.DiskStationManager.vol_info.volume_1.used_size" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.740
warn
State  "synology.0.DiskStationManager.vol_info.volume_1.total_size" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.721
warn
State  "synology.0.DiskStationManager.vol_info.volume_1.status" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.720
warn
State  "synology.0.DiskStationManager.vol_info.volume_1.name" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.718
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_2.capacity" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.700
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_2.storage_pool" has  no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.699
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_2.temperature" has  no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.698
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_2.ebox_order" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.696
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_2.overview_status"  has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.693
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_2.model" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.692
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_2.diskno" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.683
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_1.capacity" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.653
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_1.storage_pool" has  no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.653
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_1.temperature" has  no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.652
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_1.ebox_order" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.642
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_1.overview_status"  has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.607
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_1.model" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.606
warn
State  "synology.0.DiskStationManager.hdd_info.sata_drive_1.diskno" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.605
warn
State "synology.0.DiskStationManager.info.upgrade_ready" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.604
warn
State  "synology.0.DiskStationManager.info.is_system_crashed" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.603
warn
State "synology.0.DiskStationManager.info.memory_size" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.602
warn
State "synology.0.DiskStationManager.info.memory_usage" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:39.601
warn
State "synology.0.DiskStationManager.info.cpu_load" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.608
warn
State "synology.0.VideoStation.info.version_string" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.514
warn
State "synology.0.VideoStation.info.version" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.513
warn
State  "synology.0.VideoStation.info.transcoding_capability.transcode" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.512
warn
State   "synology.0.VideoStation.info.transcoding_capability.software_transcode"  has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.456
warn
State  "synology.0.VideoStation.info.transcoding_capability.remux" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.455
warn
State   "synology.0.VideoStation.info.transcoding_capability.hardware_transcode"  has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.454
warn
State   "synology.0.VideoStation.info.transcoding_capability.fhd_hardware_transcode"  has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.453
warn
State  "synology.0.VideoStation.info.transcoding_capability.dtv_transcode" has  no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.452
warn
State "synology.0.VideoStation.info.timezone_offset" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.451
warn
State "synology.0.VideoStation.info.timezone" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.451
warn
State "synology.0.VideoStation.info.privilege.sharing" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.450
warn
State "synology.0.VideoStation.info.privilege.renderer" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.449
warn
State  "synology.0.VideoStation.info.privilege.offline_conversion" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.448
warn
State "synology.0.VideoStation.info.privilege.dtv" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.447
warn
State  "synology.0.VideoStation.info.is_subtitle_search_enabled" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.446
warn
State "synology.0.VideoStation.info.is_manager" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.443
warn
State "synology.0.VideoStation.info.is_dtv_enabled" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.442
warn
State "synology.0.AudioStation.info.version_string" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.441
warn
State "synology.0.AudioStation.info.version" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.440
warn
State  "synology.0.AudioStation.info.transcode_capability.1" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.439
warn
State  "synology.0.AudioStation.info.transcode_capability.0" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.438
warn
State  "synology.0.AudioStation.info.support_virtual_library" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.437
warn
State "synology.0.AudioStation.info.support_usb" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.418
warn
State "synology.0.AudioStation.info.support_bluetooth" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.417
warn
State "synology.0.AudioStation.info.sid" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.416
warn
State  "synology.0.AudioStation.info.settings.transcode_to_mp3" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.415
warn
State  "synology.0.AudioStation.info.settings.prefer_using_html5" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.414
warn
State  "synology.0.AudioStation.info.settings.enable_download" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.413
warn
State  "synology.0.AudioStation.info.settings.disable_upnp" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.412
warn
State  "synology.0.AudioStation.info.settings.audio_show_virtual_library" has  no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.411
warn
State "synology.0.AudioStation.info.serial_number" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.409
warn
State "synology.0.AudioStation.info.same_subnet" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.409
warn
State "synology.0.AudioStation.info.remote_controller" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.408
warn
State  "synology.0.AudioStation.info.privilege.upnp_browse" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.407
warn
State "synology.0.AudioStation.info.privilege.tag_edit" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.406
warn
State "synology.0.AudioStation.info.privilege.sharing" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.405
warn
State  "synology.0.AudioStation.info.privilege.remote_player" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.390
warn
State  "synology.0.AudioStation.info.privilege.playlist_edit" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.371
warn
State "synology.0.AudioStation.info.playing_queue_max" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.370
warn
State "synology.0.AudioStation.info.is_manager" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.368
warn
State "synology.0.AudioStation.info.has_music_share" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.367
warn
State "synology.0.AudioStation.info.enable_user_home" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.366
warn
State  "synology.0.AudioStation.info.enable_personal_library" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.365
warn
State "synology.0.AudioStation.info.enable_equalizer" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.363
warn
State  "synology.0.AudioStation.info.dsd_decode_capability" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.362
warn
State  "synology.0.AudioStation.info.browse_personal_library" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.361
warn
State "synology.0.DownloadStation.info.version_string" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.360
warn
State "synology.0.DownloadStation.info.version" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.359
warn
State "synology.0.DownloadStation.info.is_manager" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.358
warn
State "synology.0.FileStation.info.uid" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.357
warn
State "synology.0.FileStation.info.system_codepage" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.356
warn
State  "synology.0.FileStation.info.support_virtual_protocol.2" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.350
warn
State  "synology.0.FileStation.info.support_virtual_protocol.1" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.348
warn
State  "synology.0.FileStation.info.support_virtual_protocol.0" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.347
warn
State  "synology.0.FileStation.info.support_virtual.enable_remote_mount" has  no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.346
warn
State  "synology.0.FileStation.info.support_virtual.enable_iso_mount" has no  existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.345
warn
State "synology.0.FileStation.info.support_vfs" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.344
warn
State "synology.0.FileStation.info.support_sharing" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.343
warn
State "synology.0.FileStation.info.support_file_request" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.341
warn
State "synology.0.FileStation.info.items.1" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.340
warn
State "synology.0.FileStation.info.items.0" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.339
warn
State "synology.0.FileStation.info.is_manager" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.338
warn
State "synology.0.FileStation.info.hostname" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.337
warn
State "synology.0.FileStation.info.enable_list_usergrp" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.335
warn
State "synology.0.DiskStationManager.info.version_string" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.334
warn
State "synology.0.DiskStationManager.info.version" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.333
warn
State "synology.0.DiskStationManager.info.uptime" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.331
warn
State "synology.0.DiskStationManager.info.time" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.330
warn
State  "synology.0.DiskStationManager.info.temperature_warn" has no existing  object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.329
warn
State "synology.0.DiskStationManager.info.temperature" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.328
warn
State "synology.0.DiskStationManager.info.serial" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.326
warn
State "synology.0.DiskStationManager.info.ram" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.325
warn
State "synology.0.DiskStationManager.info.model" has no existing object, this might lead to an error in future versions

synology.0
2021-09-16 17:00:35.323
warn
State "synology.0.DiskStationManager.info.codepage" has no existing object, this might lead to an error in future versions

`
I have cleared the full synology objects tree, but after i start the instances of synology the same errors are coming.

fixed in 2.0.1


Tasks cleanup

Little cleanup + new feature for portusctl

I don't know how to feel about removing the lib/tasks/portus_user.rake file. Recently there's been an issue in which the user had to use this rake task in order to get Portus up & running again (he was migrating from 1.0.1). I say let's keep this task around for some time at least. Maybe you could add a note to remove it in the near future?
Moreover, you should update the wiki about the set_admin -> make_admin rename once this gets merged ;)
Besides this, it looks good to me :+1:

I don't know how to feel about removing the lib/tasks/portus_user.rake file. Recently there's been an issue in which the user had to use this rake task in order to get Portus up & running again (he was migrating from 1.0.1). I say let's keep this task around for some time at least. Maybe you could add a note to remove it in the near future?

This has not been deleted, it has been moved into a single file containing all the tasks defined under the portus's namespace.
The task is now called: portus:create_api_account, which IMHO makes everything more clear.

@flavio I'm blind... Ok, then just ignore that comment :)

No worries. Thanks for the reminder about the wiki, I'll take care of that.

I updated the wiki section about set_admin.


Womanium Final Assignment -

Uploaded assignment submission - Hein Zay Yar Oo 6.12
PR Description

Some notes

[ ] Please make sure that you placed the files in an appropriate folder

[ ] And that the files have indicative names.

[ ] Please note that Classiq runs automatic code linting, which may minorly alter some files.

[ ] If you're familiar with pre-commit, you may run pre-commit install, and then at each commit, your files will be altered in a similar way

Good job!
Score: 8/10.


PowerToys Run: If Windows dialogue window is open, Run will open but fail to take proper focus.

Environment
Windows build number: Microsoft Windows [Version 10.0.19041.388]
PowerToys version: v0.19.1
PowerToy module for which you are reporting the bug (if applicable): Run

Steps to reproduce
Open the start menu, action center, or any sort of dialogue connected to the taskbar, and press the shortcut to open PT Run.
Expected behavior
On open, current focused window to either close or become unfocused, and for PT Run to take keyboard and window focus.
Actual behavior
PT Run will open, but it will fail to take keyboard focus and will either send keyboard to the previously opened window or not send it anywhere. You have to then click on the run prompt to regain focus then type your search or press escape to close.

Tracked in #4897