The authenticator "authenticator:oauth2" rejected to restore the session - invalidating…

I have been debugging this all day and still have no clue.
I am using the OAuth2PasswordGrant as authenticator and Oauth2 as authorizer. I can successfully log in with authenticate(), it has the following response:
{
"data: {"access_token":"d3f63eb6f5f38ce292a2b61bd339d02014950d58927c2bf06a6385be125f08d9"}
}

and the localstorage has the content:
key: ember_simple_auth:session
value: {"authenticated":{"authenticator":"authenticator:oauth2","data":{"access_token":"d3f63eb6f5f38ce292a2b61bd339d02014950d58927c2bf06a6385be125f08d9"}}}

All seems legit, however once I refresh the page, an error log shows in web console then it redirect me back to login page.
The authenticator "authenticator:oauth2" rejected to restore the session - invalidating…

at internal-session.js:78
The environment is
DEBUG: Ember: 2.4.5
Ember Data: 2.4.3
jQuery: 2.2.3
Ember Simple Auth: 1.1.0-beta.4

Really appreciate it if anyone can help, thanks in advance.

The expected response is
{
  "access_token":"d3f63eb6f5f38ce292a2b61bd339d02014950d58927c2bf06a6385be125f08d9"
}

instead of
{
"data: {"access_token":"d3f63eb6f5f38ce292a2b61bd339d02014950d58927c2bf06a6385be125f08d9"}
}

@marcoow THANKS for point that out, after updating the backend API it works like a charm.
This response format seems quite important however I didn't find it anywhere from the documentation.
Maybe it would be better to put it in the readme. Just a suggestion, thanks for the help.

The exact response is actually specified in the OAuth 2.0 spec. We're working sth. that will validate responses on initial authentication already so that problems like yours could not occur anymore.

@ugoa - https://tools.ietf.org/html/rfc6749#section-4.1.4
@marcoow - may be worth mentioning relevant parts of the OAuth2 spec in documentation somewhere, if this is a common question you get

@mike-north: yeah, might be good to have that in the API docs. The problem is also addressed by #957.


Fix/test path pattern

Summary
This PR fixes #8226.
Jest currently does a regex match on the testPathPattern based on the absolute path of the file under test. On macos, for any project running jest, if you run jest Users, the whole test suite will be ran since /Users/some/absolute/path/ is being run against /Users/i. In essence, any string which is part of the absolute path to the the test file will cause this issue.
Test plan
An integration with this scenario has been added.

Codecov Report

Merging #8243 into master will decrease coverage by 0.03%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #8243      +/-   ##
==========================================
- Coverage   62.28%   62.24%   -0.04%
==========================================
  Files         265      265
  Lines       10573    10579       +6
  Branches     2572     2573       +1
==========================================
  Hits         6585     6585
- Misses       3398     3404       +6
  Partials      590      590

Impacted Files
Coverage Δ

packages/jest-core/src/SearchSource.ts
54.73% <0%> (-3.7%)
:arrow_down:

Continue to review full report at Codecov.

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

I broke the build on windows. I think I'm doing something wrong with the path seperators. :(

Have you thought about the use-case for handling home directories? In some tools, when I copy a path I'll get ~/jest and in others /Users/scotthovestadt/jest.
If we're going to do this we should probably also expand the home directory ~ to make sure it works properly too.

Closing this since I don't have a windows machine and have a hard time verifying that this PR works on windows.


allow Background to have a Description

If you have a description on your Background: section, for example:
Feature: Sales

  Background: already completed a sale
    Given a $100 microwave was sold on 2015-11-03
    And today is 2015-11-18

When you run this through gherkinfmt, it succeeds but the output has incorrectly had the 'already completed a sale' description silently removed.

https://github.com/muhqu/gherkinfmt/issues/4

fixed


Error on zts_server.sql: max key length is 3072 bytes

issue
Try to run zts_server.sql in mariadb:latest  and got following error.
/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/zts_server.sql
ERROR 1071 (42000) at line 23: Specified key was too long; max key length is 3072 bytes

run commands:
https://github.com/WindzCUHK/athenz/blob/dockerize.v2/docker/db/zts/Dockerfile
https://github.com/WindzCUHK/athenz/blob/dockerize.v2/Makefile#L18-L22
https://github.com/WindzCUHK/athenz/blob/dockerize.v2/docker/db/zts/zts-db.cnf
reason
https://github.com/yahoo/athenz/blob/master/servers/zts/schema/zts_server.sql#L34
question

Is zts_server.sql expected to work on default DB setting?
Following updates is made. Is it recommended?
https://github.com/WindzCUHK/athenz/blob/dockerize.v2/servers/zts/schema/zts_server.sql#L23-L37
https://github.com/WindzCUHK/athenz/blob/dockerize.v2/docker/db/zts/zts-db.cnf#L3-L5
To have the latest schema, should I apply zts_server.sql and then all SQL files in updates folder? Or, the SQL files in updates folder is only for upgrading from old schema version?

other concerns
In https://dev.mysql.com/doc/refman/8.0/en/innodb-restrictions.html,
The index key prefix length limit is 3072 bytes for InnoDB tables that use DYNAMIC or COMPRESSED row format.

We've tested the zts_server.sql on standard MySQL and Amazon Aurora servers. If you're using a different database server that fails to import the schema, you can make the necessary changes for your environment in your local copy.

I guess that up to your environment and db server you're using.

No, zts_server.sql always contains the latest full schema. If you have an earlier version of the schema already loaded and running in production, then you just need to apply the updates based on their dates.

@havetisyan
The same problem occurs for the standard MySQL docker image with default settings.
Is there any extra settings to setup standard MySQL?
FROM mysql:latest

COPY zts_server.sql /docker-entrypoint-initdb.d/

ENTRYPOINT ["docker-entrypoint.sh"]

CMD ["mysqld"]

cd ${ATHENZ_ROOT}/servers/zts/schema; docker build -t athenz-mysql-db -f ./Dockerfile .
docker run -d --network=host --name athenz-mysql-db athenz-mysql-db
Initializing database
2019-06-07T07:05:22.252584Z 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2019-06-07T07:05:22.252661Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.16) initializing of server in progress as process 30
2019-06-07T07:05:25.173243Z 5 [Warning] [MY-010453] [Server] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
2019-06-07T07:05:27.107856Z 0 [System] [MY-013170] [Server] /usr/sbin/mysqld (mysqld 8.0.16) initializing of server has completed
Database initialized
MySQL init process in progress...
MySQL init process in progress...
2019-06-07T07:05:29.229559Z 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2019-06-07T07:05:29.229670Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.16) starting as process 81
2019-06-07T07:05:29.950514Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2019-06-07T07:05:29.951396Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/var/run/mysqld' in the path is accessible to all OS users. Consider choosing a different directory.
2019-06-07T07:05:29.982477Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.16'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  MySQL Community Server - GPL.
2019-06-07T07:05:30.041050Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock'
Warning: Unable to load '/usr/share/zoneinfo/iso3166.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/zone.tab' as time zone. Skipping it.
Warning: Unable to load '/usr/share/zoneinfo/zone1970.tab' as time zone. Skipping it.

/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/zts_server.sql
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 1071 (42000) at line 23: Specified key was too long; max key length is 3072 bytes

@WindzCUHK
I was able to reproduce this with latest mysql 8.x servers. I'm not so sure if we want to change the charset to latin1 nor introduce those other settings. It's probably much simpler to reduce the size of the columns - for example, we're never going to have a provider service name that is 512 bytes long so there is no point of keeping it as such. I'll make the changes. Thanks for the report.

@havetisyan
Thank you for the reply. Tested in the docker branch. The PR works.


fix kubeconfig serialization

Partially addresses https://github.com/GoogleCloudPlatform/kubernetes/issues/5625.
This updates kubectl config view to produce the output based on the serialization format instead of the in memory copy.
I attempted to do this before, but I failed to handle the different templates that already existed and that resulted in e2e failures.  This time I've update the templates in the scripts (see the update scripts with correct templates commit).  I'm running e2e now, but the individual formats were equivalent when I tested them.  See https://gist.github.com/deads2k/c294a882c9358ea7679f for how I located them and what the equivalence was.

LGTM, provided e2e is passing. It's unfortunate that this makes kubectl config view -o template even harder to use; the template was tricky to read before, it's now practically inscrutable. Still useful for scripting, but pretty user-unfriendly.

Rebased to get vagrant e2e working again.
I got most of them passing on vagrant.  I get the same success/failures on master against vagrant.
Summarizing 4 Failures:

[Fail] Services [It] should be able to create a functioning external load balancer
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:282

[Fail] Services [It] should correctly serve identically named services in different namespaces on different external IP addresses
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/service.go:373

[Fail] kubectl guestbook [It] should create and stop a working application
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/util.go:304

[Fail] Shell [It] tests that services.sh passes
/go/src/github.com/GoogleCloudPlatform/kubernetes/_output/dockerized/go/src/github.com/GoogleCloudPlatform/kubernetes/test/e2e/shell.go:67

Ran 32 of 37 Specs in 822.676 seconds
FAIL! -- 28 Passed | 4 Failed | 0 Pending | 5 Skipped F0407 09:05:55.975617    9536 driver.go:112] At least one test failed


Feature Request: Support showing XCTAttachments in Xcode

https://developer.apple.com/documentation/xctest/activities_and_attachments/adding_attachments_to_tests_activities_and_issues
XCTest has a feature were you can show attachments in the test log. If I am not mistaken, this is not supported yet.

This seems to work just fine for us, we use attachments via the swift-snapshot-testing framework:

Please let me know if this is still an issue. Per Luis's comment, I'm going to close this.


showing old db.json, but not updated one

I have created my fork and updated my db.json.
but its not reflecting the updated db.json from my forked server
https://github.com/seetpalsingh/json_erver/blob/master/db.json
https://my-json-server.typicode.com/seetpalsingh/json_erver

never mind!
it took a bit time to reflect.


Link to the install guide pdf in the readme installation section is broken (404 error)

It works yesterday but it's broken now!

Updated for new version number in install guide name.


[DO NOT MERGE] Test doc-builder with skipped installation feature

This PR is just for testing that we can build PR docs with changes made on the skip-install-for-real branch of doc-builder.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Fix in https://github.com/huggingface/doc-builder/pull/162 works as expected (docs build), closing this


API URL fixes

RE: https://github.com/Azure/azure-sdk-for-python/issues/19131
A GitHub issue pointed out some of the API links in this article were broken. This PR fixes.

Docs Build status updates of commit 49442a7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/latest/containerinstance.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/preview/mixed-reality.md
:warning:Warning
View (azure-python-preview)
Details

docs-ref-services/latest/mixed-reality.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/legacy/mixed-reality.md
:warning:Warning
View (azure-python-previous)
Details

docs-ref-services/latest/cognitive-services.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/preview/cognitive-services.md
:warning:Warning
View (azure-python-preview)
Details

docs-ref-services/legacy/cognitive-services.md
:warning:Warning
View (azure-python-previous)
Details

docs-ref-services/preview/network.md
:warning:Warning
View (azure-python-preview)
Details

docs-ref-services/latest/network.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/legacy/network.md
:warning:Warning
View (azure-python-previous)
Details

docs-ref-services/latest/containerinstance.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.

docs-ref-services/preview/mixed-reality.md

Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'mixed-reality'.
Line 20, Column 3: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/spatial-anchors/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 21, Column 3: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/remote-rendering/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/latest/mixed-reality.md

Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'mixed-reality'.
Line 20, Column 3: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/spatial-anchors/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 21, Column 3: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/remote-rendering/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/legacy/mixed-reality.md

Line 11, Column 13: [Warning-ms-service-subservice-invalid] Invalid value for 'ms.service': 'mixed-reality'.
Line 20, Column 3: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/spatial-anchors/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 21, Column 3: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/remote-rendering/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/latest/cognitive-services.md

Line 28, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/computer-vision/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 66, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/face/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 82, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/bing-web-search-api/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 96, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/bing-image-search-api/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 173, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/text-analytics/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 202, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/spell-check/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/preview/cognitive-services.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 31, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/computer-vision/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 69, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/face/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 85, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/bing-web-search-api/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 99, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/bing-image-search-api/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 176, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/text-analytics/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 191, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/spell-check/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/legacy/cognitive-services.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 31, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/computer-vision/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 69, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/face/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 85, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/bing-web-search-api/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 99, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/bing-image-search-api/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 176, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/text-analytics/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 191, Column 1: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/services/cognitive-services/spell-check/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

docs-ref-services/preview/network.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 78, Column 3: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/resources/samples/network-python-manage-loadbalancer/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 80, Column 10: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/resources/samples/?platform=python&term=virtual%20network' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 6, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'sttramer' is not a valid Microsoft alias.

docs-ref-services/latest/network.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 78, Column 3: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/resources/samples/network-python-manage-loadbalancer/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 80, Column 10: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/resources/samples/?platform=python&term=virtual%20network' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 6, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'sttramer' is not a valid Microsoft alias.

docs-ref-services/legacy/network.md

Line 2, Column 1: [Warning-ms-prod-and-service] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 12, Column 16: [Warning-ms-prod-technology-invalid] Invalid value for 'ms.technology': 'azure' is not valid with 'ms.prod' value 'azure'.
Line 78, Column 3: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/resources/samples/network-python-manage-loadbalancer/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 80, Column 10: [Warning-hard-coded-locale] Link 'https://azure.microsoft.com/en-us/resources/samples/?platform=python&term=virtual%20network' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 6, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'sttramer' is not a valid Microsoft alias.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Apologies for the holdup here. Checked the review site, everything confirmed! Thanks!


NoDecodeDelegateForThisImageFormat `JPEG' @ error/constitute.c/ReadImage/50

Can anybody help with the following error?
NoDecodeDelegateForThisImageFormat `JPEG' @ error/constitute.c/ReadImage/50
  9

I'm not sure what kind of library I'm missing, this is my docker file
FROM php:7.1-fpm-alpine

# intl, zip, soap
RUN apk add --update --no-cache libintl icu icu-dev libxml2-dev \
    && docker-php-ext-install intl zip soap

# mysqli, pdo, pdo_mysql
RUN docker-php-ext-install mysqli pdo pdo_mysql

# mcrypt, gd, iconv
RUN apk add --update --no-cache freetype-dev libjpeg-turbo-dev libmcrypt-dev libpng-dev \
    && docker-php-ext-install iconv mcrypt \
    && docker-php-ext-configure gd --with-freetype-dir=/usr/include/ --with-jpeg-dir=/usr/include/ \
    && docker-php-ext-install gd

# gmp, bcmath
RUN apk add --update --no-cache gmp gmp-dev \
    && docker-php-ext-install gmp bcmath

# redis, apcu
RUN docker-php-source extract \
    && apk add --no-cache --virtual .phpize-deps-configure $PHPIZE_DEPS \
    && pecl install redis \
    && pecl install apcu \
    && docker-php-ext-enable redis apcu \
    && apk del .phpize-deps-configure \
    && docker-php-source delete

# imagick
RUN apk add --update --no-cache autoconf g++ imagemagick-dev libtool make pcre-dev \
    && pecl install imagick \
    && docker-php-ext-enable imagick \
    && apk del autoconf g++ libtool make pcre-dev

# git client, mysql-client
RUN apk add --update --no-cache git mysql-client

# pcntl
RUN docker-php-ext-install pcntl

RUN sed -i -e 's/listen.*/listen = <IP_ADDRESS>:9000/' /usr/local/etc/php-fpm.conf

RUN echo "expose_php=0" > /usr/local/etc/php/php.ini

CMD ["php-fpm"]

That's an imagick error. You need to make sure you have the proper "delegates" built in. Open up a command line and type convert -version  and make sure jpeg is listed.

@cdowdy convert -version says `sh: convert: not found´

ok, I ended up using another base image for PHP that is not based on alpine. the rest of the dockerfile logic remained the same

For other who end up here, I was having the exact same problem (well, different line number in the error). My Dockerfile was pretty much identical for anything related to imagick.
My problem was that I was missing imagemagick itself. After adding apk add for imagemagick, problem was fixed and php -r 'print_r(Imagick::queryFormats());' list was no longer empty, it had 226 keys including JPEG etc.

Using alpine image docker i just added this to my image and rebuild docker image.
RUN set -ex \     && apk add --no-cache --virtual .phpize-deps $PHPIZE_DEPS imagemagick-dev libtool \     && export CFLAGS="$PHP_CFLAGS" CPPFLAGS="$PHP_CPPFLAGS" LDFLAGS="$PHP_LDFLAGS" \     && pecl install imagick-3.4.3 \     && docker-php-ext-enable imagick \     && apk add --no-cache --virtual .imagick-runtime-deps imagemagick \     && apk del .phpize-deps

@julitroalves just wanted to let you know: your lines saved my problem 👍

❓ a question to all: I use https://github.com/docker-slim/docker-slim to tiny my PHP image. the fantastic thing is: the size shrinks from 500MB to 100MB BUT that´s only because a lot of things gets deleted.
the base-image shows me every image format Imagick::queryFormats() : but the tiny image doesn´t show anything, so I am sure, there are some files somewhere, that must not be deleted. does anybody has an idea where these files are ? because docker-slim supports the --include-path option, to keep some folders (or files) from seeing deleted. thanks for any help!!

Closing as the issue seems to be resolved and isn't directly related Glide's code.


[Feature Request] on Table components, you can add similar to this header style options.

Existing Component
是
Component Name
Table
Description
如图

Sorry, we have no plan to support this.


Non-standard packaging of model.pt under code/

Conventionally, the actual model artefacts e.g. yolov8l.pt would be packaged directly under the model.tar.gz root and outside of the code/ subfolder - which should contain only the inference code module.
This is important because (AFAIK) re-creating PyTorchModels with a different source_dir argument will "re-pack" the source artifact to replace the contents of code/ - generating a new final model.tar.gz for deployment. Deviating from this pattern is confusing for users who start from this sample and then try to deploy a model trained on SageMaker (where the starting point will likely be a model.tar.gz with a .pt file in the root)
Additionally, the model_dir passed to the model_fn points to this extracted root folder, so a more typical model loading function might look like:
def model_fn(model_dir):
    print("Executing model_fn from inference.py ...")
    env = os.environ
    model = YOLO(os.path.join(model_dir, env['YOLOV8_MODEL']))
    return model

I'd recommend refactoring this sample to pull yolov8l.pt up to the root level of model.tar.gz... and maybe even demonstrate how an initial "raw" model.tar.gz containing only the model is "re-packed" to include the inference code module - when calling PyTorchModel(source_dir="code", entry_point="inference.py", ....)

Bump, this is very important...

Could anyone explain what is the value of model_dir? And why in the original source code, the path is YOLO("/opt/ml/model/code/" + env['YOLOV8_MODEL'])


Update the quickstarts documentation to reflect their refactoring

update the school timetabling docs to match the quickstart
add a vehicle routing QS docs

@ge0ffrey feel free to take this if you get to it sooner than me.

VRP documentation moved to https://github.com/TimefoldAI/timefold-solver/issues/145.


Enabled the game 'run and jump' to pause and resume

PR Description 📜
Enhanced the game by adding a 'stop and pause' button to stop and resume the game and it updates the score from where it stopped.
Fixes #3301

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added a video for website preview in assets/images

Video demo
https://github.com/kunjgit/GameZone/assets/136987759/40659e8e-de76-4d3e-91d7-3d372de1a216

Thank you @Roshr2211 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Thank you  @Roshr2211 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Profiling smoke test

This builds on top of #273.
This makes a smoke test that fires up spring petclinic with the profiling agent enabled and ensures that JFR files are generated. It should be the foundational work for more thorough testing down the road.
In order to test, we also needed a way to configure the output directory for JFR files, so this changeset also includes that.
The smoketest has to build a spring petclinic rest image because the one in dockerhub is 2 years old and doesn't have a java 8 version with JFR.  Because of that, it's slower than I would prefer...so I'm inclined to file an issue to address that at a later time (maybe we can publish a base image like we do elsewhere).

The smoketest has to build a spring petclinic rest image because the one in dockerhub is 2 years old and doesn't have a java 8 version with JFR. Because of that, it's slower than I would prefer...so I'm inclined to file an issue to address that at a later time (maybe we can publish a base image like we do elsewhere).

You could add a separate project that published the image to GHCR, similar to smoke-tests in the upstream project.
Or, alternatively, just add a separate GHA job for profiler tests and exclude them from the main build - it won't make them run faster but should mitigate the issue a bit.

Ready for another look.  I think since this is not yet hooked up to automation I will create an issue to track that and also an issue to build/publish a base image.


adds authentication for registering tasks, workflows, and launch plans

This is generalized in https://github.com/lyft/flytekit/pull/52 - the main auth pr into which it was merged will itself be merged in the coming days.

Closing because this is solved by the merge of https://github.com/lyft/flytekit/pull/52 . Thank you for the contribution!


Support .NET Core

Support .NET Core by adjusting the UdpClient constructor used and using Dns.GetGetHostAddressesAsync() instead.
Requires a further commit to update the nuspec to correctly declare the package as supporting .NET Core before being merged.

Looks like the .NET Portability Analyzer didn't find everything, so there's some more changes required.

Well, it builds. The dependencies for .NETStandard1.6 might need reducing, and the AppVeyor build doesn't append the build number to the package version yet.
The biggest job left appears to be sorting the tests out.

Loving your work 👍
Me & @JosephWoodward will hopefully soon be coming up to FPH on a friday to hack on some dotnet core things in the afternoon, including JustSaying with @AnthonySteele, wanna join us? I've yet to sort out the details.

@stuart-lang Yeah sure, that sounds good! I've resolved all your feedback. Just a Travis CI build and fixing the tests left now I think.

@martincostello are you still waiting on the travis build, or are you happy with this?

@stuart-lang As well as a Travis build to verify it works there, also the tests need reworking still as the dependencies don't support .NET Core and I wasn't sure what to do about that as it's a non-trivial task.

FYI I've had issues with this code running in .NET Core, so there's some more discussion needed about exactly what we want to do to support it. In my case in a separate fork I switched to using UdpClient.ctor() and sending the packets using SendTo(byte[], IPEndpoint).

@martincostello I'll try to help. So what happens when you call it?

A SocketException is thrown (socket error 10049 I think). The constructor seems to suggest a local endpoint is required, not a remote one, which is why it throws. The SendTo() method wants a remote one, and that works fine. I can show you the fork version tomorrow.

Cool. Is it newer than this: https://github.com/martincostello/JustEat.StatsD/tree/Support-DotNet-Core

Yeah, I've effectively forked it internally within the consumer at the moment. I'll switch back to this once we get the PR how we want it and merged.

Cool, I'll take a look tomorrow 👍

Hello guys! Do you still plan to merge this?

@RTodorov Hi, we're still to agree exactly how to migrate the test suite as well as changes to APIs used for .NET Core support. Once that's agreed plus I've got time to fix up the PR with the agreed changes we'll hopefully get it merged in short-order. Sorry it's been taking so long.

I've done some work fixing this up today, but the test dependencies are a bit of a mess due to the dependency on JustBehave.  I tried just targeting .NET Framework 4.5.1 in the tests, but the NuGet dependencies didn't seem to want to restore.
Any opinions on the best way to proceed? For example, we could re-write the tests to just be vanilla NUnit tests without the need for JustBehave and its dependency chain.

Regarding the test project, just bump it to net452 (from net451) for now, then you'll be able to restore all the packages. I'd like to separate out the AutoFixture dependency in JustBehave, or move that piece out into a separate nuget, that way we could move these without a big refactor.

Here's a set of dependencies that work for the test project:
  "dependencies": {
    "JustEat.StatsD": "1.1.0-*",
    "AutoFixture": "3.50.2",
    "AutoFixture.AutoFakeItEasy": "3.50.2",
    "FakeItEasy": "1.25.3",
    "JustBehave": "<IP_ADDRESS>",
    "NLog": "5.0.0-beta03",
    "NUnit": "3.5.0",
    "Shouldly": "2.6.0",
    "dotnet-test-nunit": "3.4.0-beta-3"
  },

There are then a couple of minor code changes to make to get them to run and pass.

Thanks @slang25! Tests restored in c386c6b8e8756ae8247f0df5851f2f9bb69d5b98 and running successfully in the AppVeyor CI from 03bb34fd489ebd970fc99e217030be97090ffa47 with .NET Framework 4.5.2.
I think now we just need to try out the latest package from AppVeyor in a .NET Framework and .NET Core feature and check that it works OK functionally, then we should be good to merge.

Tests OK with .NET Core, just need to investigate an error on the full Framework with:
iisexpress.exe Error: 0 : General Exception when sending metric data to statsD :- Message : One or more errors occurred., Inner Exception System.Net.Sockets.SocketException (0x80004005): No such host is known
   at System.Net.Dns.HostResolutionEndHelper(IAsyncResult asyncResult)
   at System.Net.Dns.EndGetHostAddresses(IAsyncResult asyncResult)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization), StackTrace    at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at System.Threading.Tasks.Task`1.get_Result()
   at JustEat.StatsD.EndpointLookups.DnsEndpointProvider.GetIPEndPoint(String hostName, Int32 port)
   at JustEat.StatsD.StatsDUdpClient.Send(IEnumerable`1 metrics).

That error was actually caused by a copy-paste configuration error on my part in the end. Sigh
Metrics successfully being published to StatsD from both an application targeting ,NET Core and .NET Framework 4.5.2 using 1.1.0-beta-0073.

Nice, shall I merge, then we can get it on nuget.org as a beta?

Yeah, pushing a beta version to NuGet.org for some wider pre-release testing would be good before we go all-in and push 1.1.0.

@RTodorov We've published a beta of the NuGet package that supports .NET Core if you'd like to try it out.

Thanks @martincostello, I'll definitely check it out! Thanks for the good work!


QCT want to develop manageiq want to support with red hat

hi guys,
i am Quanta Cloud Technology, QCT engineer, we want to develop manageiq source code,
we have cooperation with red hat. do you have CICD enviroment or auto build script can share us.
Can you tell us contact window ?
Best Regards,
Jimmy Wang
(QCT)

Welcome!

we want to develop manageiq source code

What are you looking to develop specifically?  E.g add a new provider type, enhance the UI, etc...?

YES,
1.we want to change the ui style and ux more suitable to user use(Framwork). support hardware management UI.
2. and want to support redfish function(based hardware management include server, switch, storage ex: JGX MFX ). also can coontorll Physical machine(server).

Bare Metal provisioning Tools.(openstack , ceph, resource Scaling)

4.NFVI monitoring.

ceph  monitoring  management

6.VNF on  bearing

Okay check out the https://github.com/ManageIQ/manageiq-providers-redfish repo

Using manageiq-ui-classic 0.1.0 from https://github.com/ManageIQ/manageiq-ui-classic (at hammer-1@a6c9b41)
Bundle updated!
Gems in the groups qpid, test, metric_fu and development were not installed.
Copying /home/manageiqgrafana/manageIQ/manageiq-providers-redfish/spec/manageiq/certs/v2_key from template...
Copying /home/manageiqgrafana/manageIQ/manageiq-providers-redfish/spec/manageiq/config/cable.yml from template...
Copying /home/manageiqgrafana/manageIQ/manageiq-providers-redfish/spec/manageiq/config/database.yml from template...
== Resetting tests ==
rails aborted!
NameError: uninitialized constant RSpec
lib/tasks_private/spec.rake:7:in <top (required)>' /home/manageiqgrafana/manageIQ/manageiq-providers-redfish/Rakefile:14:in load'
/home/manageiqgrafana/manageIQ/manageiq-providers-redfish/Rakefile:14:in block in <top (required)>' /home/manageiqgrafana/manageIQ/manageiq-providers-redfish/Rakefile:14:in <top (required)>'
bin/rails:12:in require' bin/rails:12:in '
(See full trace by running task with --trace)
== Command ["bin/rails app:test:vmdb:setup"] failed in /home/manageiqgrafana/manageIQ/manageiq-providers-redfish ==

bin/update
will get same error message


Incurring an error (can't find Ruby) when executing the Deploy the new manifest to create a BOSH Director step

Hello,
I have reached the "Deploy the new manifest to create a BOSH Director" step in this document:
https://github.com/cloudfoundry-incubator/bosh-google-cpi-release/tree/master/docs/concourse
but when executing the following command:
bosh-init deploy manifest.yml
I get the following output with an error message that Ruby can't be found:
[jamesweaver@bosh-bastion-concourse google-bosh-director]$ bosh-init deploy manifest.yml
Deployment manifest: '/home/jamesweaver/google-bosh-director/manifest.yml'
Deployment state: '/home/jamesweaver/google-bosh-director/manifest-state.json'

Started validating
  Downloading release 'bosh'... Skipped [Found in local cache] (00:00:00)
  Validating release 'bosh'... Finished (00:00:02)
  Downloading release 'bosh-google-cpi'... Skipped [Found in local cache] (00:00:00)
  Validating release 'bosh-google-cpi'... Finished (00:00:02)
  Validating cpi release... Finished (00:00:00)
  Validating deployment manifest... Finished (00:00:00)
  Downloading stemcell... Skipped [Found in local cache] (00:00:00)
  Validating stemcell... Finished (00:00:00)
Finished validating (00:00:04)

Started installing CPI
  Compiling package 'golang/b7c20853a73ad56fad8d60b980503e22d3ac7f43'... Finished (00:00:00)
  Compiling package 'bosh-google-cpi/2334a22dc4536f3bd86a8cd97e0127a5dfb86249'... Finished (00:00:00)
  Installing packages... Finished (00:00:03)
  Rendering job templates... Failed (00:00:00)
Failed installing CPI (00:00:03)

Command 'deploy' failed:
  Installing CPI:
    Rendering and uploading Jobs:
      Rendering job templates for installation:
        Rendering templates for job 'google_cpi/134a472ce3b5764dcaf2de5636b34c8d1560286d':
          Rendering template src: bin/cpi.erb, dst: bin/cpi:
            Rendering template src: /home/jamesweaver/.bosh_init/installations/fc7d9664-f590-4a5c-6260-f634546f32da/tmp/bosh-init-release880157659/extracted_jobs/google_cpi/templates/bin/cpi.erb, dst: /home/jamesweaver/.bosh_init/installations/fc7d9664-f590-4a5c-6260-f634546f32da/tmp/rendered-jobs940263743/bin/cpi:
              Running ruby to render templates:
                Starting command 'ruby /home/jamesweaver/.bosh_init/installations/fc7d9664-f590-4a5c-6260-f634546f32da/tmp/erb-renderer682624914/erb-render.rb /home/jamesweaver/.bosh_init/installations/fc7d9664-f590-4a5c-6260-f634546f32da/tmp/erb-renderer682624914/erb-context.json /home/jamesweaver/.bosh_init/installations/fc7d9664-f590-4a5c-6260-f634546f32da/tmp/bosh-init-release880157659/extracted_jobs/google_cpi/templates/bin/cpi.erb /home/jamesweaver/.bosh_init/installations/fc7d9664-f590-4a5c-6260-f634546f32da/tmp/rendered-jobs940263743/bin/cpi':
                  exec: "ruby": executable file not found in $PATH

I tried which ruby to find where the ruby executable is located but it results in the following:
/usr/bin/which: no ruby in (/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/jamesweaver/bin)
Any ideas on how to proceed?
Thanks,
James Weaver

Hi @JavaFXpert - any luck getting concourse installed?

Jeff,
Thanks for checking up. I made it farther thanks to your advice, but got stuck on the deploy step. I’ll forward an email that contains relevant info.
Regards,
James (Jim) Weaver

On Feb 12, 2018, at 12:52 PM, Jeff Johnson<EMAIL_ADDRESS>wrote:
Hi @JavaFXpert - any luck getting concourse installed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Jeff,
Here is the issues page that contains information on where I'm stuck.
https://github.com/cloudfoundry/bosh-bootloader/issues/233
Thanks,
James Weaver
On Mon, Feb 12, 2018, at 12:52 PM, Jeff Johnson wrote:

Hi @JavaFXpert[1] - any luck getting concourse installed?

— You are receiving this because you were mentioned. Reply to this
email directly, view it on GitHub[2], or mute the thread[3].>

Links:

https://github.com/javafxpert
https://github.com/cloudfoundry-incubator/bosh-google-cpi-release/issues/245#issuecomment-365004961
https://github.com/notifications/unsubscribe-auth/AJee2rEvdTGqsrzgfcYFO7U-3STTpqOhks5tUHpVgaJpZM4RjoTe

Closing as the bbl issue was eventually resolved


Update DB.php

Fix 'SQLSTATE[HY093]: Invalid parameter number' PDO error which caused of multiple parameters usage in one query.

Thanks for your contribution!
What version of MySQL are you using, I have never encountered this issue.

I'm using lumen framework. MySQL version: 5.1.73 (this error came from the pdo plugin itself, not mysql).

why u dont merge it ?

Hi, sorry for the epic delay...
A cleaner solution in my view, is to simply rename the fields to created_date and updated_date respectively.
Also, your ON DUPLICATE KEY section saves the wrong value to updated_at, as it simply puts the value of created_at into the updated_at field, instead of the current timestamp.
If you could change it accordingly and do the same for all other instances of duplicate :date tokens in other queries, I'll happily merge 😃

@no-nevis Shall I go ahead and make the changes and merge?

Also, your ON DUPLICATE KEY section saves the wrong value to updated_at, as it simply puts the value of created_at into the updated_at field, instead of the current timestamp.
Fixed.

A cleaner solution in my view, is to simply rename the fields to created_date and updated_date respectively.
The problem isn't only dates, but the other placeholders that used twice.

Hi @no-nevis
I have taken the liberty to rebase your PR properly, to prevent the duplicate commits that snuck in.
Also, I've added another commit that renames the placeholders to make it more obvious and cleaner.
There is 1 query left that has duplicate (or rather triplicate) placeholders here:
https://github.com/no-nevis/core/blob/patch-1/src/DB.php#L1104
Is this one an issue for you too? Do you get the same error?

Thanks @no-nevis 😃👍

Delete


Update PHP version in readme

Hey @pascalbaljet
just noticed that the PHP in the readme doesn't match with the version in the composer.json. This fix updates the readme to PHP7.4 (as in the composer.json).
Cheers,
Peter

Thanks!


Refactor in preparation for kernel updates

The main point here is to break up DeltaPerformer so it isn't responsible for processing the update manifest and applying the update operations to the partition. In the third and final PR after this one now smaller DeltaPerformer will be instantiated multiple times, once for the partition and once for the kernel. This is in contrast to how  DeltaPerformer used to work where it had to have if/else statements everywhere to handle writing out to both in a single instance.

largely mechanical stuff, lgtm


Wrong prometheus metrics name

According to Prometheus doc, Metrics "should have a (single-word) application prefix relevant to the domain the metric belongs to." and I therefore suggest to rename the prometheus metrics to ouroboros_{existing name} to comply with that.
I see it happens in ouroboros/pyouroboros/dataexporters.py  and can do it myself if yopu can confirm that there's no other file or code involved.
Also intrigued as I see in that file only 3 metrics

'containers_updated',
'containers_being_monitored'
'all_containers_updated'

But a lot more are exposed on my endpoint ? Including some with names conflicting with my current prometheus setup which is kind of why I'm opening this issue
root@6fad16c8355b:/var/www/html# curl http://ouroboros:3579
# HELP python_gc_objects_collected_total Objects collected during gc
# TYPE python_gc_objects_collected_total counter
python_gc_objects_collected_total{generation="0"} 11345.0
python_gc_objects_collected_total{generation="1"} 2501.0
python_gc_objects_collected_total{generation="2"} 16.0
# HELP python_gc_objects_uncollectable_total Uncollectable object found during GC
# TYPE python_gc_objects_uncollectable_total counter
python_gc_objects_uncollectable_total{generation="0"} 0.0
python_gc_objects_uncollectable_total{generation="1"} 0.0
python_gc_objects_uncollectable_total{generation="2"} 0.0
# HELP python_gc_collections_total Number of times this generation was collected
# TYPE python_gc_collections_total counter
python_gc_collections_total{generation="0"} 125.0
python_gc_collections_total{generation="1"} 11.0
python_gc_collections_total{generation="2"} 1.0
# HELP python_info Python platform information
# TYPE python_info gauge
python_info{implementation="CPython",major="3",minor="7",patchlevel="2",version="3.7.2"} 1.0
# HELP process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE process_virtual_memory_bytes gauge
process_virtual_memory_bytes 4.6063616e+07
# HELP process_resident_memory_bytes Resident memory size in bytes.
# TYPE process_resident_memory_bytes gauge
process_resident_memory_bytes 3.8150144e+07
# HELP process_start_time_seconds Start time of the process since unix epoch in seconds.
# TYPE process_start_time_seconds gauge
process_start_time_seconds 1.56534268334e+09
# HELP process_cpu_seconds_total Total user and system CPU time spent in seconds.
# TYPE process_cpu_seconds_total counter
process_cpu_seconds_total 1.5
# HELP process_open_fds Number of open file descriptors.
# TYPE process_open_fds gauge
process_open_fds 31.0
# HELP process_max_fds Maximum number of open file descriptors.
# TYPE process_max_fds gauge
process_max_fds 1.048576e+06
# HELP containers_updated_total Count of containers updated
# TYPE containers_updated_total counter
containers_updated_total{container="xxx",socket="unix://var/run/docker.sock"} 1.0
# TYPE containers_updated_created gauge
containers_updated_created{container="xxx",socket="unix://var/run/docker.sock"} 1.565342739176655e+09
# HELP containers_being_monitored Gauge of containers being monitored
# TYPE containers_being_monitored gauge
containers_being_monitored{socket="unix://var/run/docker.sock"} 32.0
# HELP all_containers_updated Count of total updated
# TYPE all_containers_updated gauge
all_containers_updated{socket="unix://var/run/docker.sock"} 1.0
root@6fad16c8355b:/var/www/html# curl http://ouroboros:3579
# HELP python_gc_objects_collected_total Objects collected during gc
# TYPE python_gc_objects_collected_total counter
python_gc_objects_collected_total{generation="0"} 11345.0
python_gc_objects_collected_total{generation="1"} 2501.0
python_gc_objects_collected_total{generation="2"} 16.0
# HELP python_gc_objects_uncollectable_total Uncollectable object found during GC
# TYPE python_gc_objects_uncollectable_total counter
python_gc_objects_uncollectable_total{generation="0"} 0.0
python_gc_objects_uncollectable_total{generation="1"} 0.0
python_gc_objects_uncollectable_total{generation="2"} 0.0
# HELP python_gc_collections_total Number of times this generation was collected
# TYPE python_gc_collections_total counter
python_gc_collections_total{generation="0"} 125.0
python_gc_collections_total{generation="1"} 11.0
python_gc_collections_total{generation="2"} 1.0
# HELP python_info Python platform information
# TYPE python_info gauge
python_info{implementation="CPython",major="3",minor="7",patchlevel="2",version="3.7.2"} 1.0
# HELP process_virtual_memory_bytes Virtual memory size in bytes.
# TYPE process_virtual_memory_bytes gauge
process_virtual_memory_bytes 4.6063616e+07
# HELP process_resident_memory_bytes Resident memory size in bytes.
# TYPE process_resident_memory_bytes gauge
process_resident_memory_bytes 3.805184e+07
# HELP process_start_time_seconds Start time of the process since unix epoch in seconds.
# TYPE process_start_time_seconds gauge
process_start_time_seconds 1.56534268334e+09
# HELP process_cpu_seconds_total Total user and system CPU time spent in seconds.
# TYPE process_cpu_seconds_total counter
process_cpu_seconds_total 1.6800000000000002
# HELP process_open_fds Number of open file descriptors.
# TYPE process_open_fds gauge
process_open_fds 31.0
# HELP process_max_fds Maximum number of open file descriptors.
# TYPE process_max_fds gauge
process_max_fds 1.048576e+06
# HELP containers_updated_total Count of containers updated
# TYPE containers_updated_total counter
containers_updated_total{container="xxx",socket="unix://var/run/docker.sock"} 1.0
# TYPE containers_updated_created gauge
containers_updated_created{container="xxx",socket="unix://var/run/docker.sock"} 1.565342739176655e+09
# HELP containers_being_monitored Gauge of containers being monitored
# TYPE containers_being_monitored gauge
containers_being_monitored{socket="unix://var/run/docker.sock"} 32.0
# HELP all_containers_updated Count of total updated
# TYPE all_containers_updated gauge
all_containers_updated{socket="unix://var/run/docker.sock"} 1.0

@ytzelf  ouroboros/pyouroboros/dataexporters.py is the only location. I'm cool with it if you want to make a PR, but I ask that you also keep the existing metrics to avoid breaking other consumers.
The other metrics added are output by the prometheus client library by default.


Update to Tcl 8.6

Also tcllib to 1.21, tclx to 8.4.4. Thanks to @neverpanic for doing most of the work.

Awesome, thanks guys!


VSCode-ESLint doesn't respect a local moduleResolver

I'm working on something to make ESLint able to resolve Deno modules. I've written a deno-resolver.js that is imported into my .eslintrc.js:
module.exports = {
	...,
	overrides: [
		{
			files: [`*.ts`],
			parser: `@typescript-eslint/parser`,
			parserOptions: {
				moduleResolver: __dirname + `/deno-resolver.js`,
				project: [`./tsconfig.json`]
			},
		},
	],
};

It works in that npx eslint . completes without any warnings or errors. However, the VSCode extension does not appear to respect the modules imported with this custom resolver:

Why doesn't the ESLint extension have the same result as me running npx eslint . in my CLI?
Repo: https://github.com/RobertAKARobin/eslint-import-debug

This problem comes from the TS language server and not ESLint (see the error code ts(2691))

Closing the issue since. Please report it to the TypeScript team.


Hyper-V commands missing

No information about:
Add-VMGpuPartitionAdapter

Get-VMGpuPartitionAdapter

Remove-VMGpuPartitionAdapter

@Ammar-AlDabbagh Thank you for your feedback.
The below links take you to the documents you are looking for
https://learn.microsoft.com/en-us/powershell/module/hyper-v/add-vmgpupartitionadapter?view=windowsserver2022-ps
https://learn.microsoft.com/en-us/powershell/module/hyper-v/get-vmgpupartitionadapter?view=windowsserver2022-ps
https://learn.microsoft.com/en-us/powershell/module/hyper-v/remove-vmgpupartitionadapter?view=windowsserver2022-ps
Hope this helps!
Thanks
Sri

Thanks. I hope it's fine to ask this under this issue, but ever since I'd added the GPU partition to a VM, I could never get the system to fully revert. Though everything works as intended, even after using Remove-VMGpuPartitionAdapter and fully uninstalling Hyper-V, task manager still displays that the GPU VRAM is split.

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Could not reset the runtime

I'm having this error when executing the soft_reset function.
Could not reset the runtime: Runtime("ext:rustyscript/rustyscript.js:53: Uncaught TypeError: Cannot read properties of undefined (reading 'global_backup')")

Unfortunately the soft_reset and reset functions are currency not working due to changes in deno
What's your usecase for it?

I have created a work around for it. Thanks!


Are there issues with Catalina?

I just ran AppStoreExtract on the AppStore for the first time on Catalina.  It appeared to process correctly, but at the end it created a cryptic file name.dmg file and a pkg.plist file.  This seemed odd as this has never happened before... usually the file name reflects the app and the revision and only one file is normally created.  I had not yet tried to execute the dmg, but I thought I would ask if anything needs to be addressed for Catalina.

Hi ClayStudio
Yes, I saw that as well but was not yet able to resolve:
It looks like Apple has changed the way how the package information is delivered: the script tries to extract the app name, this fails under Catalina. The package itself is complete and usable, it just has a cryptic name.
I will continue to search for a new way to get the right naming back.

An update on this problem: I was not able to find the new way of getting the version/name of the package. But I found, that my script is still picking up the right data if the download/installation of the AppStore is not done manually but by using the mas-cli (https://github.com/mas-cli/mas) while my script runs. Hope that help ease the situation a bit.

I had just upgraded my last Mojave system to Catalina and I had forgot about this issue.  Today I tried to capture a download update from the AppStore and I was reminded about the issue when the script didn’t complete normally.
I have two questions… can we manually rename the file before we tell your script to?  Can you tell me where the temporary file is saved to so I can manually copy it?
The other question is regarding your advice to use mas-cli…. Is there a complete howto on installing the software and what we are supposed to install?  Not quite sure what I would need to do you use that option.
Any help is appreciated.
Jim
On Nov 18, 2019, at 3:09 PM, Max Schlapfer<EMAIL_ADDRESS>wrote:
An update on this problem: I was not able to find the new way of getting the version/name of the package. But I found, that my script is still picking up the right data if the download/installation of the AppStore is not done manually but by using the mas-cli (https://github.com/mas-cli/mas https://github.com/mas-cli/mas) while my script runs. Hope that help ease the situation a bit.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/maxschlapfer/MacAdminHelpers/issues/15?email_source=notifications&email_token=ANPSE7ZTLTG2H2G6URBEGPDQULZBJA5CNFSM4JFNUZ6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEELX6VA#issuecomment-555188052, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANPSE7ZAX24UBNXQE3Y64XTQULZBJANCNFSM4JFNUZ6A.

Just tried it for the first time after upgrading to Catalina: didn't work… only printed *.dmg and *.pkg instead of the full name, and therefore exited with error.
[Side-note: I'm using the same script as the one here, except for two additional detox commands on the pkg and the final dmg.]
I do have the mas CLI installed via Homebrew, so I will try this approach next time.

PS: works fine when installing with mas.


Backcalls in macros get incorrectly compiled

When defining a macro that 'returns' a backcall, it will not produce the expected code.
The given Yuescript code:
macro backcall = (fn) -> "() <- #{fn}()"

do
    $backcall async_fn
    print()

    () <- async_fn()
    print()

The above will compile to the following Lua code:
do
    async_fn(function() end)
    print(); --- Unrelated sidenote: Why the semicolon? Did you add it in the compiler for testing purposes and forgot to remove it?
    async_fn(function()
        return print()
    end)
end

I would expect the macro to produce the same code as the written-out version below it.

Just in the case that a more real-world example is useful: I stumbled across this issue when using this macro:
--- The code
---
--- ```yuescript
--- $await output_stream::write("foo", "bar")
--- ```
---
--- becomes
---
--- ```yuescript
--- (_, __async_result) <- output_stream::write_async("foo", "bar", nil)
--- output_stream::write_finish(__async_result)
--- ```
macro await = (call) ->
    object, method, args = call::match([[([a-zA-Z_][a-zA-Z0-9_]*)::([a-zA-Z_][a-zA-Z0-9_]*)%((.*)%)]])

    "
(_, __async_result) <- #{object}::#{method}_async(#{args}, nil)
#{object}::#{method}_finish(__async_result)
"

It's intended for working with Gio, a library for asynchronous IO https://docs.gtk.org/gio/method.OutputStream.write_async.html
Each successive $await call is intended to become nested in the previous backcall. However, what happens instead is that only the #{object}::#{method}_finish(__async_result) gets nested, then the block ends.

The two problems you mentioned is currently intended. The macro expanded in the middle of a code block, will be treated as a do block without an extra variable scoping. So that your code is currently expanded as:
do
  do -- without variable scoping
    () <- async_fn()
  print()

  () <- async_fn()
  print()

I think it is the problem caused by the compiler implemetation that macros are expanded while translating each line of statement. I think this implementation should be changed to expand macros before translating any code to Lua code.
And the problem of the redundant semicolon is that Yuescript is adding semicolon to reduce the ambiguity caused by Lua multiline expressions.
-- the valid code in Lua
func()
(args)()
-- is the same as
func()(args)()
-- to make them two lines of statements you can make use a semicolon
func();
(args)()

Currently Yuescript is blindly adding semicolon when it sees a new line started with a left parenthe. Maybe it should check and add semicolons after all codes translated to Lua.

It is the problem caused by the compiler implemetation that macros are expanded while translating each line of statement. I think this implementation should be changed to expanding macros before translating any code to Lua code.

I agree. Macros getting evaluated and expanded before compilation would be both more intuitive and more useful, I think. I personally only use them when a function would be too limiting (which is rather rare in Yuescript), and having them produce their own isolated blocks severely limits their usefulness for me. Additionally, I think it should be outlined in the documentation when exactly macros get evaluated and expanded, especially if the current behavior were to be kept.

I think it is better to explicitly write the Yuescript statement that affect the rest codes in a scope, like global *, local * and backcall statement <- func. And I made a new commit c98c6053635ddfca7aab15b268b0f2c1fcc0c6ef trying to make backcall syntax work with macro syntax. Now you can implement your use case this way.
macro await = (call, body) ->
  object, method, args = call::match([[([a-zA-Z_][a-zA-Z0-9_]*)\([a-zA-Z_][a-zA-Z0-9_]*)%((.*)%)]])
  return "
(_, __async_result) <- #{object}::#{method}_async(#{args}, nil)
#{object}::#{method}_finish(__async_result)
#{body::sub(5)\gsub '\n\t', '\n'}
"

do
  <- $await output_stream::write("foo", "bar")
  print 123
  if cond
    func 456

compiles to:
do
  return output_stream:write_async("foo", "bar", nil, function(_, __async_result)
    output_stream:write_finish(__async_result)
    print(123)
    if cond then
      return func(456)
    end
  end)
end

In this new macro version, the expressions passed as macro function arguments are being parsed and reformatted to code strings, instead of in the formar implementation they are just copy-pasted as pure text. In this manner the backcall function can be passed as code of normal function.
<- $func
  print 123

now works the same as
$func ->
  print 123

I like the idea of automatically re-formatting the code. But I'd actually take that further: Similarly to object::method() now becomes object\method(), I think other ambiguities should also be covered by this. For example, the != operator, which is mentioned in the very same block as the :: alias for method calling, should probably be translated to ~=. Otherwise, it seems kind of weird to have this specific case get rewritten behind the scenes, but not others. I'm not sure yet which things I would / would not have converted, but I think a good rule of thumb would be anything that's just a slightly different way to write the same thing. That would include parenthesis-less functions / function calls, bracket-less tables (seems to already be implemented), any syntax aliases (as previously mentioned, that would be :: / \ and != / ~=) and similar small things.


[Bug]: Recent Finder Files not working

Checklist

[X] I have updated to the latest version of this workflow.
[X] I am using Alfred 5 or later.

Alfred version
5.5.1 (2273)
macOS version
Sonoma 14.6.1
Bug Description
Results never appear when using the rec command.
Relevant Screenshot
No response
To Reproduce
When I run the rec command, the debugger shows the below and no results appear. (I have installed ripgrep using the specified command.) Thanks in advance for any help you can offer – it's a great idea for a workflow! 🙂
Debugging Log
[16:36:57.370] Quick File Access[Script Filter] Queuing argument '(null)'

Workflow Configuration

Do you have ripgrep installed?

Just in case, I added some logging and a potential fix for an edge case I found, so you might try version 1.0.3 and run the command again:
https://github.com/chrisgrieser/alfred-quick-file-access/releases/download/1.0.3/alfred-quick-file-access.alfredworkflow

Hi Chris! Thanks for a quick response. I've updated to 1.0.3, and find I still have the same problem. When I run which -a rg I get:
mark@Marks-Laptop ~ %  which -a rg
/opt/homebrew/bin/rg

I added some logging to 1.0.3, so please run the command again and copy the debugging log again, which should now include some more information

Hi! Afraid the debugger appears to output the same way with 1.0.3 (checked plist to confirm I was on this version):
[17:04:47.132] Quick File Access[Script Filter] Queuing argument '(null)'

Front Finder window, download folder and trash work. Recent files and also tag don’t work – but then again, I haven’t set up a tag. Thanks again.

tbh, I do not have any idea why this does not work for you then. Queuing argument '(null)' as output should not be possible, it should either throw an error or a log message.

Hmm, OK, thanks for looking into it! I’m no developer, but will let you know what the issue is if do happen to figure out what’s up on my side…

Hi Chris,
I feel a little silly – I happened to notice that it is working after all; it's just very slow. Perhaps the number of recently modified files?
[12:03:08.699] Quick File Access[Script Filter] Queuing argument '(null)'
[12:03:33.868] Quick File Access[Script Filter] Script with argv '(null)' finished
[12:03:33.873] STDERR: Quick File Access[Script Filter] KEYWORD: rec
SHELL COMMAND
export PATH=/usr/local/lib:/usr/local/bin:/opt/homebrew/bin/:$PATH ; cd "/Users/mark" && rg --no-config --files --binary --sortr=modified --ignore-file="/Users/mark/Library/Application Support/Alfred/Alfred.alfredpreferences/workflows/user.workflow.6B8455D0-F4C7-426C-95D0-FCC9942990B3/scripts/home-icloud-ignore-file"

Aha!
Yes, the number of files could be an issue. You could try to lower the value in the settings, but if you have a large home directory, it might be slow regardless.
How large of a home directory do you have?

Large, it seems! 20GB or so. I will try to exclude a few folders to see if that speeds things up… Thanks!

@chrisgrieser Do you have any performance tips? My home folder is apparently ~550GB, with the majority of that space going to Pictures and Movies (Though my library folder is about 100GB). The rec keyword takes ~11 seconds for me.

It's not that much the size of the folder, but rather the number of files in them. If you have many, many files in there, there is unfortunately little this workflow can do.
One thing you might consider is arching (compressing as zip) directories you don't actively use. This not only reduces file size, but also the number of files, and as a side-benefit, can also speed up other things (backup operations, Spotlight/Alfred in general.)


profile perf fixes

@keybase/react-hackers some small changes as i'm fixing up stuff

[x] plumb thumbnail through so we don't do redirects we don't need
[x] load smaller sizes for avatars

:+1:


[BEAM-13925] Give pr bot write permissions on pr update

Right now, the PR bot fails on pr-update events if the pr author doesn't have the right permissions. This gives all authors the correct permissions and pins the repo we checkout to master so that users can't do something malicious by changing the script we execute.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @youngoli - this is another one that wasn't caught by my test repo since it only affects people without repo permissions.


Publish hex docs for recent versions

It would be great to publish the docs for the most recent version released on hex :)

Need help with that @robconery ?

Ugh probably :) I'll happily pop you on commit if you want to help :)


Add Flipper Skylanders Keys Repo

As said into discussions, here is my PR for adding "Flipper Skylanders" Repository.
Thanks! :)

I'm moving the link to the Notes & References section since it's more of a how-to than a universal dump.

Basically its to get a dictionnary for nfc dictionnary attack, but as im adding "how" and some ressources and that can growth i agree ^^ did i close the pr and leave it in your hand?

I'll take care of closing in once I merge it with others.

Merged with latest commit.

Thanks! :)

Reopening so I can mark this as merged.


Optimize system_files table performance

This is in reference to this discussion: https://github.com/wintercms/winter/discussions/208
This PR will drop the single column indexes and convert them into a composite index for improved performance and convert the attachment_id column to bigint if the database column only contains numeric values.
Feel free to suggest any changes/improvements because this is my first attempt at this type of a change and want this change to be as safe as possible.

Wasn't sure if there was really a way to write tests to be able to seed some test data before running the migration.
If there is, I'd be happy to try and implement some tests to make sure this goes as smoothly as possible.

https://wintercms.com/docs/database/structure#seeder-structure

@ericp-mrel does the composite index make that much difference? I was under the impression that there wouldn't be much difference between a composite index, or the separate indexes. I figured that only changing the VARCHAR to an integer column would suffice.

@bennothommo In my limited testing it didn't make a ton of difference, but changing VARCHAR to int obviously made the biggest difference. I can remove the index changes if you'd rather not switch to a composite one.

@ericp-mrel let's do that, if you don't mind. Just keeps the potential points of failure to a minimum.

@bennothommo I'm fine with changing the index as well, it did result in a performance increase prior to the id column type change so theoretically it will still help even with the varchar to bigint change. @ericp-mrel perhaps you could do a performance test for the difference between the index changed and unchanged (both using bigint attachment_id columns)?

Also, it looks like my other comment on the subject never posted, but is there a way we can use a DB query to determine if the columns can be changed rather than doing that in PHP, especially with the is_numeric() function which would return true for some forms of data that can't be reliably converted

@LukeTowers I had this problem a couple of years ago with a project - my understanding at the time was that the different database server types had different ways of handling this, so there might not be a query that can be accurately run across all our supported types.
That being said, things might've changed in the last couple of years since.

I tried to find out if there was a way to run a query to determine if there are non-int values in a column, but I couldn't really find anything. I then thought about if a single query could even work for all database engines, because I know some databases handle types differently and I don't have any experience with Postgres or MSSQL and I wanted to make this as reliable as possible which is why I settled on handling this in PHP.
I am open to handling this with a SQL query if it is possible and if anyone knows of a reliable way to do this across all database engines.

Sidenote: I didn't noticed that Sam rollbacked my previous PR that fixed the keyType on PostgreSQL installations: https://github.com/octobercms/library/pull/502
I didn't tested yet but this PR should fix the bug Sam re-introduced as we now will be more consistent about the keyType and value both saved as integers into the database

I would definitely delay this to 1.2.1 personally.

@bennothommo what was left on this to get it merged?

@LukeTowers sorry for the delay on getting back to you on this one.
On reviewing it, I think this PR has kinda gone in two directions. Originally, it was to change the indexes in the system_files table to a composite index for apparently better performance. I'm not too keen on this as I'm not sure of its effect on other database types and I haven't seen any hard numbers to determine its performance benefit.
However, there is also a fix to change the attachment IDs to a bigint column if the table only contains numbers. I think this is needed because some strict SQL servers (like PostgreSQL or MySQL with some SQL modes in play) will type the column as a string column and will reject integer values outright, as opposed to coercing them to strings. This part of the PR I believe is needed to fix the linked issues.

@bennothommo are you interested in resubmitting the relevant part of the PR that you want to keep?
As an aside, @ericp-mrel did provide hard performance numbers here: https://github.com/wintercms/winter/discussions/208#discussioncomment-889912 and they were fairly convincing in favour of this PR in its entirety.

Fair enough, so it does have a performance benefit (for MySQL), but we'd need to see if that's the same with the other database types too.
I can certainly make a PR for the bigint change.

Ping @bennothommo 😉


How many build-in Filters do we have in jsonType feature

In the document, I could not find a list of build-in filters. I saw url, date and empty if-blocks in the code, are they filters?
One more thing, do we have anything like json/object filter, just like what we have with array, to detect whether the value part is a valid json object?

Nowadays filters are documented here: https://codeception.com/docs/modules/REST#seeResponseMatchesJsonType
@Naktibalda @TavoNiievez I guess this issue can be closed?


impliment upsert for SQLite

discuss with #1854.
This pr include breaking change that pg::upsert move to diesel::upsert.
We can use upsert with SQLite from SQLite version 3.24.0.
https://www.sqlite.org/releaselog/3_24_0.html
Postgres's doc abount on conflict
Sqlite's doc about on conflict

@joelgallant Honestly, we haven't done extensive testing on that. Given that all the databases we support are generally backwards compatible in their wire protocol, I believe we suspect virtually every version of PG and MySQL in use today. We do of course support features that are only available in newer versions of those libraries, and if you're using those features (which you would have to explicitly do), you will need to be on a version that supports it. AFAIK the only backend which we have a meaningful version requirement on is SQLite, because we use a function that's only present in newer versions. I honestly can't remember what function it is or what version it was added in, but I know we didn't work with the version of sqlite that shipped with macOS a few years ago.
If you want to do some more extensive testing to figure out what our version support is, I would certainly love to document that. It's valuable to do, but just not something we've prioritized.

@weiznich @sgrif
Do you know what is version of sqlite on travis ?
I think that that sqlite version is not support upsert.

@weiznich

Do not remove unrelated tests and remove that impls for SupportsDefaultKeyword and SupportsReturningClause for sqlite because both are not supported on sqlite and may lead to invalid sql.

I'm sorry, I was variously misunderstanding.
I've fixed it.

@weiznich
Failed tests on travis are success on my desktop.
I think that sqlite3 running on the travis is not support upsert version.

@weiznich
Failed tests on travis are success on my desktop.
I think that sqlite3 running on the travis is not support upsert version.

@weiznich
Thank you so match for your polite review!
I'll fix that today or tomorrow.
After fix it, should I rebase and clean commit logs ?

@sgrif Would you review this PR?

[memo]
in travisci
$ sqlite3 --version
3.8.2 2013-12-06 14:53:30 27392118af4c38c5203a04b8013e1afdb1cebd0d

@weiznich @sgrif
Python depends on libsqlite3-0, so we should build python from source in order to using latest sqlite3. :(

Wouldn't it be easier to run tests with libsqlite3-sys? I'm not familiar with Diesels Travis setup, so perhaps there's a good reason not to, but just throwing it out there?

@weiznich @sgrif
I've pass the CI.
Would you review this PR?

@weiznich I've fixed.
Can I ignore azure pipelines failure?

@h-michael Yes azure pipeline could be ignored. It is just enabled but missing the corresponding pipeline file. (Just started to get #1889 working…)

@Eijebong @killercup @sgrif
Would you review this PR?

@weiznich
Fix and update CHANGELOG.md.

@weiznich
Sorry for late reply.
I've see all insert statement codebase. But I don't know how to implement add WHERE true in such case.
Would you help me?

I would love to see this merged at some point.
Right now I have a hard time finding a purely diesel way to achieve a database agnostic REPLACE / ON DUPLICATE KEY UPDATE. Postgres does not support REPLACE and thus replace_into will not be supported without an emulation of REPLACE on postgres, however ON DUPLICATE KEY UPDATE seems to be supported by PostgreSQL, SQLite and MySQL as well.

@Skeen This will be merged as soon as the issues pointed out above are fixed. So if someone really need this, feel free to submit a updated version of this as new PR.

Ok, I will restart this PR.

@h-michael will you have time to work on this?

@theduke I've restarted now :)

@JohnTitor
This PR have to solve these comments https://github.com/diesel-rs/diesel/pull/1884#issuecomment-454443616, https://github.com/diesel-rs/diesel/pull/1884#issuecomment-454794947, https://github.com/diesel-rs/diesel/pull/1884#issuecomment-454797372.
But if there is an ON CONFLICT DO NOTHING statement and there is no WHERE clause for the SELECT clause, we have no idea how to write WHERE 1 = 1 after the SELECT clause.
Do you have any idea?

Make those code not compiling for sqlite. (This will need a compile-fail test) and we try to fix that after merging this PR.

I agree with @weiznich 's suggestion, it's one of the solutions to merge this.

@h-michael I've found some time to figure out how to handle the missing where clause cases on sqlite. https://github.com/diesel-rs/diesel/pull/1884/commits/fad61d1f0458d0901856a03a59d7668f67f1cd9d implements a solution for that by disallowing plain select statements without where clause and just patching a where clause in for boxed select statements. I'm not sure if that's a good idea or if we better just patch the query for all variants. (Asking @diesel-rs/reviewers here)
I would like to have the code reordered a bit before finally merging it. All SQL construction stuff (so everything related to QueryFragment and so on) should belong to diesel::query_builder::upsert, everything related to the query construction dsl traits can be left in diesel::upsert.
(Yes I know, CI is failing for beta + nightly, that's because of rustc regressions…)

@weiznich
I'm sorry to have left the PR for a long time.
Thanks for implementing my shortfall.
Is there anything I can help?

No worries. A final test + review would be a great help, otherwise I think that this PR is mostly finished.

@weiznich Thank you for completing this PR.

Any estimates when this is going to be released? :)

@kpcyrd I've already written in quite a lot of places that the next feature release is estimated to be released when it's done. I will not give any clearer timeline.
Additionally considering that we run diesel in our free time, please consider what you are asking for.


FIDO2's HMAC not working

Fido2's HMAC challenge-response is not working at the moment. Most probably due to use of the outdated fido2 libraries API.

report: https://github.com/Nitrokey/nitrokey-3-firmware/issues/281#issuecomment-1579204555

this is fixed by #410 - fido2 challenge-response works now after fido2 make-credential


The tab order in the Combo dialog is invalid.

The tab order in the combo dialog is invalid: the group combo should be in second.

The tab order is still invalid in the combo dialog

Hi. Thank you for reporting. For some reason, the snippet editor control is last in the the tab order list. I'll try to fix that ASAP.


Failed to get Manifest for - pulsar-client-2.9.1.jar

For some reason I keep getting this error when try: mvn install package
with next dependency:

org.apache.pulsar
pulsar-client
2.9.1

Error:
Error assembling JAR: Failed to get Manifest for - pulsar-client-2.9.1.jar. Please verify if jar file is valid, the MANIFEST.MF should be first or second entry in the jar file. Use Command - jar tf <Jar_File_Path> to verify.

I remember that 2.9.1 is a yanked version. It should work well if you use any current maintained versions.


typo in ucp ldap config

Signed-off-by: Trapier Marshall<EMAIL_ADDRESS>

since it's not easy to see:

[...] making a separate LDAP query for each member. as opposed to first [...]

changed to:

[...] making a separate LDAP query for each member, as opposed to first [...]


How to improve the voice conversion quality ?

I have trained chinese data(140 utterances) by  WORLD vocoder ,it can work but the pitch seems not good enough.
Could any one give me some suggestion ? Thanks so much !
By the way I use default configuration as bellows and I choose some synthesis voice here(https://drive.google.com/drive/u/0/folders/17DQcTxa3-dFVk-HFEExx3LCN1175KWes)  :
hidden_layer_size  : [512, 512]
hidden_layer_type  : [ 'TANH' ,'TANH']
model_file_name: feed_forward_2_tanh

Did you try the s2 recipe of voice conversion which is with Magphase Vocoder, it should work better in that scenario. I have tried with default settings on the arctic dataset which is provided and it works perfectly fine with 50 utterances and six layers.

@vivek-sethia thanks your suggestion , I had try Magphase Vocoder but the voice conversion reslut is not good , and I have changed the default settings with four layers[512 ,512 ,512 ,512 ] and learning-rate change to 0.01 beacuse I thought that DEMO data(300 utterances) is more than my chinese data(140 utterances) .Could I listen your sythesis voice to understand whether my work is right or not ? Thanks you so much!


Addressed safety issues

No review needed.

coverage: 25.088%. remained the same
when pulling 226d0ea9f7fd4a6330d8e48d098b8058e1c85a63 on andy/safety-2024-08-18
into b6527c0b492a8f1204bdca8cbf0e0ed64bd6a3bd on master.


Move Swate manual to Knowledge Base

Mostly a 1:1 move from the (to become) Dev Docs https://nfdi4plants.github.io/Swate-docs/index.html to here

added all docs
adapted sidebar to align somewhat to that of arc commander (room for improvement)
added images and adapted relative links to images
adapted cross-links (between individual doc markdowns)
left a page on "installation" linking to this new source (just in case as this was referenced a lot)
tested locally

Before approval, please clone and test locally.
Especially cross-links and images. I am aware of a few incorrect links (that were already incorrect in the source).

Also, while going over it, I found many things that could be structured into smaller pieces for better overview. Will do so after this PR.

The changes are all valid. I also found a few typos. But can we merge / move first and then go in small pieces from there?


carousel elements blur after transition

Hi there,
On translate3d math to coordinates should be rounded to 0. If translate3d gets values like x.5 then elements in carousel gets blurred.
So I added coordinate.toFixed(0) to fix this error in this section:
Line: 1324 / owl.carousel.js
if (this.support3d) {
this.dom.$stage.css({
transform: 'translate3d(' + coordinate + 'px' + ',0px, 0px)',
transition: (this.speed() / 1000) + 's'
});
}

I can't seem to find this line of code anymore, which makes sense, as this issue is more than three weeks old and we've recently released a new version.
Can you do me a favor and try to reproduce this issue on that new release? I'll reopen this thread if it persists.


Add pre-commit to dev dependencies

Closes #46.

The repo could do with adding pre-commit setup steps in a CONTRIBUTING.md file


Center of VideoNode seems to be incorrect

Hi. When I create VideoNode it shows with top-right offset, I looked at the code:
    public Renderable makePlane(float width, float height, Material material) {
        return PlaneFactory.makePlane(
                new Vector3(width, height, 0.0f),
                new Vector3(width, height, 0.0f),
                material
        );
    }

the second parameter new Vector3(width, height, 0.0f) is plane center, so that center of plane shifted by size of a video.
It's necessary to have center right in the real center of video to be able to rotate node around it.

Thx, It will be solved with this PR https://github.com/SceneView/sceneform-android/pull/217

Thank you! Hope it will be merged soon. :)

Fixed in #2386c772f9ca9a9e0b5c9cc1f64606d9acee8da4


Device injection

I just realised that i was commenting on a closed issue so I deleted my comment and created this instead.
I am wondering about device injection. I realise that injection on the device is very experimental but it is also extremely cool and useful so I really want to get it working. For me what is happening is that it never connects, in fact nothing is outputtet to the console at all.
I did mange to get device injection to work using the HotReloading project, but I prefer this way for ease of use and because I'm having issues with hot refreshing collectionView cells with the HotReloading project which seems to work out of the box using this. It was my understanding that this project and the HotReloading project connects to the InjectionIII app the same way which is way I'm confused why device reloading works with HotReloading but not with Inject....

Hi, The HotReloading project is effectively a Swift Package of the contents of the iOSInjection.bundle on the file system that Inject would normally load. As this is not available on the device you use HotReloading instead to compile it into your app.

Oh ok. Thank you for the clarification, I guess I  should see if I can somehow merge the device reloading from the hotreload project with the convenience of this project...

You should be able to use Inject with HotReloading as readily as you can with using the bundle. Let me know if you can't!

Cool. I will try this tomorrow. Will let you know. I dont need to remove the code that loads the bundle from the inject code?

No, it tests to see if HotReloading is already present: https://github.com/krzysztofzablocki/Inject/blob/main/Sources/Inject/Inject.swift#L33

Just testet it out, it does seem to refresh but changes to collection view cells does not seem to update and changes to the collectionview it self causes a completely black screen. Not sure whats going on here.

Hi, it sounds like you're trying to do something quite ambitious. Try it in the simulator first before you venture into device injection. "injection on the device is very experimental"

You are right. It might be a bit to ambitious. I will stick with the simulator for now which seems to be working very well.


Billing percentage should not show up in invoice create screen for which invoice is already created

When we create a new invoice, the system shows all the billings for that client. Even the ones that are already attached to an invoice.
Ideally, the system should only show those billings who are not attached to any invoice.

From my verbal communication with @rathorevaibhav what I understood regarding this issue is:

We can create multiple bills for a stage of project.

We can then create invoice for each bill separately, right from the billings.

Once we create an invoice, the billing % for that bill gets locked, see picture below.

But, we can also create an invoice for a billing by going through Finance > Invoices > Create Invoice

When creating an invoice from here (last step's location) a drop-down asks us to select the billing % for which we want to create an invoice.

This drop-down should not give an option to select the billing % for which an invoice already exist.

@rathorevaibhav this one requires some knowledge of VueJS. So it might take a week or so. Not sure about the estimate.

@Satendra-SR assigning this to you. If @abhishek-pokhriyal prefers, you can take help from him on whatever he has researched in this.

#460
@rathorevaibhav
I tried this one and I think it works fine.
but one thing I noticed that both create invoice and edit invoice are using same Vue template.
So how can we deal with this? We will not able to select invoice % that are already created in edit invoice also.

@Satendra-SR I believe we're sorted on the areas of doubts based on our discussion. Just to summarize:
Consider the following billings for a project stage:
Billing%     InvoiceID
50%           1
20%           -
30%           -

There is an invoice for 50% billing and other billings don't have any invoice yet.

We need to put a check in the Vue template to see if the current page is create or edit invoice.
Next, in the create page, only 20% and 30% billings should show up in the select option (as they don't have any invoice).
In the edit page of invoiceID 1, 50% billing selection should show up by default. If the user adds a new project, then he should have ability to select only 20% and 30%.

I have completed the above. The system is only showing those billings who are not attached to an invoice.
but the system is also showing those stages which do not have any empty billing. it should not be shown up there. I tried it but it creates a bulky code and uses 3 for loops which is not a good practice as the code should be optimized.
I talked with @rathorevaibhav  and he suggested me for code refactoring. so I'm putting it on hold and will try to refactor it.

@Satendra-SR if you're done with the "not showing existing billings", I think we can ship it and target the "stages without empty billings" in a separate PR. Thoughts?


Failed to process incoming DLC message: No order to mark as Filled

At the moment, if we can't find an order in Filling we stop everything. In case of https://github.com/get10101/meta/issues/355 that got the protocol stuck again, because the position was not deleted and the last message was also not sent back to the user.
Now the state is broke and has to be cleaned up.
I propose we do not stop the process in case we can't find an order in Filling but rather print a warning as this is not a super critical thing.

This has already been fixed.

Reopening this ticket as this is still happening and causing issues. related to https://github.com/get10101/10101/issues/2361


chore: [release-1.4] bump @backstage/plugin-scaffolder-node

Description

For 1.4
Recreated patches for @backstage/plugin-scaffolder-node based on v1.32.6
Bumped @backstage/plugin-scaffolder-node versions to fix CVE: https://nvd.nist.gov/vuln/detail/CVE-2024-53983

Which issue(s) does this PR fix

Fixes #?

PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

/test e2e-tests

/test e2e-tests

/retest

/retest

/lgtm


Replace walletConnect v1 and firebase crachlytics with pod version #5977

Closes #5977

after #5693

BTW, in the commit message: "crachlytics" -> "crashlytics"
so we can find it when looking in history :)


Make patches ERLs

Make it so patches do not (or will not? I dunno. Is that a good idea?) have to be a part of the main elfldr executable.
One folder structure idea i have (or wait until #2 is done and allow arbitrary loads?)
 ssx/
    patches/
      stdpatches.erl # elfldr shipped file
    gamehooks/
     my_gamehook.erl

I may make this "will not", as this allows for a space saving. Elfldr can handle loading the elf, erls, and any codehook ERLs, wherehas the patch ERLs can be loaded on a per-game basis, saving memory

Needs work on allocator probing, which should in theory destroy the current "no malloc" ban. Tbf, this is only needed for games which use their own allocator (E.g: SSX, which uses the REAL scheme.. on top of, apparently, dlmalloc? wow.


Recursive load of saveplace

After updating to try the new private module implementation, I ran into a recursive load error when initializing.  This also occurs for me from a fresh install.  Log messages are below.  Git bisect points to commit 0150f78e87ca0a56473c36ab234ab9d23cd77c40, which defers the loading of saveplace (and others).  A simple revert of the commit runs into another error.  I'm happy to try any suggestions for a fix.
Thanks again.
Log after first bad commit:
Doom initialized
Loading package vi-tilde-fringe...
Configuring package vi-tilde-fringe...done (0.009s)
Loading package vi-tilde-fringe...done (0.028s)
Loading package shackle...
Configuring package shackle...done (0.010s)
Loading package shackle...done (0.047s)
Loading package smartparens...
file-symlink-p: Recursive load: "/usr/local/homebrew/Cellar/emacs-plus/25.2-rc2/share/emacs/25.2/lisp/saveplace.elc", "/usr/local/homebrew/Cellar/emacs-plus/25.2-rc2/share/emacs/25.2/lisp/saveplace.elc", "/usr/local/homebrew/Cellar/emacs-plus/25.2-rc2/share/emacs/25.2/lisp/saveplace.elc", "/usr/local/homebrew/Cellar/emacs-plus/25.2-rc2/share/emacs/25.2/lisp/saveplace.elc", "/usr/local/homebrew/Cellar/emacs-plus/25.2-rc2/share/emacs/25.2/lisp/saveplace.elc", "/Users/cthachuk/.emacs.d/.local/packages/elpa/smartparens-20170604.1126/smartparens.elc", "/Users/cthachuk/.emacs.d/core/core-editor.el", "/Users/cthachuk/.emacs.d/core/core.el", "/Users/cthachuk/.emacs.d/init.el"

Error in log after reverting bad commit: Symbol's function definition is void: doom-themes-visual-bell-config

Sorry about that. I was a tad overzealous about deferring those packages, especially when the benefits were so meager. The issue should be fixed now. Feel free to reopen this if that isn't the case.