text:
chore(deps): upgrade Ubuntu 20.04

[x] upgrade Ubuntu LTS version

Hi!
This doesn’t take into account any of the packages that install assuming
this is Ubuntu 18.04 (bionic).
The nginx/PHP/chrome(?) repositories used don’t yet have builds for 20.04
so this wouldn’t build successfully.
On Sun, Apr 26, 2020 at 15:09 Vinayak Kulkarni notifications@github.com
wrote:

upgrade Ubuntu LTS version

You can view, comment on, or merge this pull request online at:
https://github.com/shipping-docker/vessel/pull/143
Commit Summary

chore: upgrade Ubuntu 20.04

File Changes

M docker-files/docker/app/Dockerfile
https://github.com/shipping-docker/vessel/pull/143/files#diff-e4cc6ce63d9b8a9a4adbe95d927542ab
(2)

Patch Links:

https://github.com/shipping-docker/vessel/pull/143.patch
https://github.com/shipping-docker/vessel/pull/143.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/shipping-docker/vessel/pull/143, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADSDU7FGX2TJQTZN2AVFZLROSIGTANCNFSM4MRMKKWA
.

Specifically these:
https://github.com/shipping-docker/vessel/blob/master/docker-files/docker/app/Dockerfile#L17-L18
The change will be bionic -> focal when those repositories have builds for 20.04.
So, we'll need to wait a bit for those to get updated! Then we can merge in your PR after updating bionic -> focal and giving it a test.
Thanks!

I've updated the reference of php & nginx repos to point to focal (20.04) instead of bionic (18.04)

Appreciate it! When those repositories finally update with the packages for
20.04 we can test this out and merge it 👍🏻👍🏻
On Sun, Apr 26, 2020 at 16:13 Vinayak Kulkarni notifications@github.com
wrote:

I've updated the reference of php & nginx repos to point to focal (20.04)
instead of bionic (18.04)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/shipping-docker/vessel/pull/143#issuecomment-619625788,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADSDU3ERAM5GTGBUZA5MO3ROSPZNANCNFSM4MRMKKWA
.

Appreciate it! When those repositories finally update with the packages for 20.04 we can test this out and merge it 👍🏻👍🏻
…
On Sun, Apr 26, 2020 at 16:13 Vinayak Kulkarni @.***> wrote: I've updated the reference of php & nginx repos to point to focal (20.04) instead of bionic (18.04) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#143 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADSDU3ERAM5GTGBUZA5MO3ROSPZNANCNFSM4MRMKKWA .

PHP has already deps for focal, waiting for nginx focal to be added

Oh btw, #131 would've ran this automatically instead of me manually sending a PR

I think we should use the official nginx ppa instead of launchpad ppa..

Launchpad is where PPA's are hosted - the one used is the official one built by Nginx.

Looks like PHP for Focal might be ready finally, so we may be ready to try this out! 👌

Launchpad is where PPA's are hosted - the one used is the official one built by Nginx.

http://nginx.org/en/linux_packages.html#Ubuntu

Ah thanks, I see actually on another page they say they aren't maintaining
the PPA from launchpad. I'll check on that too.
Appreciate it!
On Tue, May 12, 2020 at 1:14 PM Vinayak Kulkarni notifications@github.com
wrote:

Launchpad is where PPA's are hosted - the one used is the official one
built by Nginx.
http://nginx.org/en/linux_packages.html#Ubuntu
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/shipping-docker/vessel/pull/143#issuecomment-627507899,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADSDU5BFOILGWRV5CJNSULRRGGXRANCNFSM4MRMKKWA
.

If you want, I can setup config for using the official nginx ppa instead of launchpad one in this PR?
Or shall I send a new PR for bionic, then rebase this PR and just do incremental change for focal?

Adding to this PR would be fine, thanks! Once that's setup we can run some
tests (require dev-master into a laravel project and try it out. We can
edit the local docker-compose.yml file to name the resulting image
something other than the stock name, which will tell docker-compose to
build the image even if you already have a vessel app image created
locally).
On Tue, May 12, 2020 at 9:55 PM Vinayak Kulkarni notifications@github.com
wrote:

If you want, I can setup config for using the official nginx ppa instead
of launchpad one in this PR?
Or shall I send a new PR for bionic, then rebase this PR and just do
incremental change for focal?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/shipping-docker/vessel/pull/143#issuecomment-627714083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADSDU5LGXSG7Q72PRILABDRRIDZJANCNFSM4MRMKKWA
.

I played with installing Nginx via their official repo recently - They use a different configuration file structure.
Specifically /etc/nginx/sites-enabled isn't used, it instead wants config files in /etc/nginx/conf.d.
Change to be made: https://github.com/shipping-docker/vessel/blob/master/docker-files/docker/app/Dockerfile#L46
(just making notes here, I got some work stuff keeping me busy right now)

(also the fastcgj parameters aren’t all set!) So that’s need to be back filled.
I think that’s it. I personally replaced most nginx config with H5BP’s nginx config when I tested on an AWS server recently.

Awesome!

You're free to add commits in this repo.
I am buried in work for the next few days :(

My plan right now (when I get some free time also :D )

Adjust scripts to add the default config to the /etc/nginx/conf.d directory
Add/replace the default config with H5BP's config (likely will pin to a specific release/hash)
Grab the proxy params from the PPA-installed setup to reproduce within the Nginx config

Here is the setup for fastcgi settings currently (to reproduce):
File /etc/nginx/snippets/fastcgi-php.conf:
# regex to split $uri to $fastcgi_script_name and $fastcgi_path
fastcgi_split_path_info ^(.+\.php)(/.+)$;

# Check that the PHP script exists before passing it
try_files $fastcgi_script_name =404;

# Bypass the fact that try_files resets $fastcgi_path_info
# see: http://trac.nginx.org/nginx/ticket/321
set $path_info $fastcgi_path_info;
fastcgi_param PATH_INFO $path_info;

fastcgi_index index.php;
include fastcgi.conf;

File /etc/nginx/fastcgi.conf:
fastcgi_param  SCRIPT_FILENAME    $document_root$fastcgi_script_name;
fastcgi_param  QUERY_STRING       $query_string;
fastcgi_param  REQUEST_METHOD     $request_method;
fastcgi_param  CONTENT_TYPE       $content_type;
fastcgi_param  CONTENT_LENGTH     $content_length;

fastcgi_param  SCRIPT_NAME        $fastcgi_script_name;
fastcgi_param  REQUEST_URI        $request_uri;
fastcgi_param  DOCUMENT_URI       $document_uri;
fastcgi_param  DOCUMENT_ROOT      $document_root;
fastcgi_param  SERVER_PROTOCOL    $server_protocol;
fastcgi_param  REQUEST_SCHEME     $scheme;
fastcgi_param  HTTPS              $https if_not_empty;

fastcgi_param  GATEWAY_INTERFACE  CGI/1.1;
fastcgi_param  SERVER_SOFTWARE    nginx/$nginx_version;

fastcgi_param  REMOTE_ADDR        $remote_addr;
fastcgi_param  REMOTE_PORT        $remote_port;
fastcgi_param  SERVER_ADDR        $server_addr;
fastcgi_param  SERVER_PORT        $server_port;
fastcgi_param  SERVER_NAME        $server_name;

# PHP only, required if PHP was built with --enable-force-cgi-redirect
fastcgi_param  REDIRECT_STATUS    200;

The default file fastcgi_params exists in BOTH install locations but does NOT contain fastcgi_param  SCRIPT_FILENAME    $document_root$fastcgi_script_name;, which is needed.

In our case we can likely just create a single file 'fastcgi-php.confin/etc/nginx` with the combined output:
# regex to split $uri to $fastcgi_script_name and $fastcgi_path
fastcgi_split_path_info ^(.+\.php)(/.+)$;

# Check that the PHP script exists before passing it
try_files $fastcgi_script_name =404;

# Bypass the fact that try_files resets $fastcgi_path_info
# see: http://trac.nginx.org/nginx/ticket/321
set $path_info $fastcgi_path_info;
fastcgi_param PATH_INFO $path_info;

fastcgi_index index.php;

fastcgi_param  SCRIPT_FILENAME    $document_root$fastcgi_script_name;
fastcgi_param  QUERY_STRING       $query_string;
fastcgi_param  REQUEST_METHOD     $request_method;
fastcgi_param  CONTENT_TYPE       $content_type;
fastcgi_param  CONTENT_LENGTH     $content_length;

fastcgi_param  SCRIPT_NAME        $fastcgi_script_name;
fastcgi_param  REQUEST_URI        $request_uri;
fastcgi_param  DOCUMENT_URI       $document_uri;
fastcgi_param  DOCUMENT_ROOT      $document_root;
fastcgi_param  SERVER_PROTOCOL    $server_protocol;
fastcgi_param  REQUEST_SCHEME     $scheme;
fastcgi_param  HTTPS              $https if_not_empty;

fastcgi_param  GATEWAY_INTERFACE  CGI/1.1;
fastcgi_param  SERVER_SOFTWARE    nginx/$nginx_version;

fastcgi_param  REMOTE_ADDR        $remote_addr;
fastcgi_param  REMOTE_PORT        $remote_port;
fastcgi_param  SERVER_ADDR        $server_addr;
fastcgi_param  SERVER_PORT        $server_port;
fastcgi_param  SERVER_NAME        $server_name;

# PHP only, required if PHP was built with --enable-force-cgi-redirect
fastcgi_param  REDIRECT_STATUS    200;

@fideloper : i'll be working on this over the next few days

Merged via https://github.com/shipping-docker/vessel/pull/147

authors: fideloper vinayakkulkarni

repo: shipping-docker/vessel


text:
How to get desirable results on Make3D dataset?

In the train.py, using 2.8 for apt, 40000 numbers of iterations results in low-quality predicted depth map png. Would you please give some clue on how to get desirable outputs for Make3D dataset?

Hello Cindy, I have been implementing these networks recently. Can we add a friend to communicate with each other : )

ok

my qq：479470026

email：cindy7liu@163.com

Hello, I also encountered the same problem, can I add contact information to discuss with each other? my email：455736571@qq.com

source: gharchive/issue

authors: CindyChow123 FlyFish-space cubhe

repo: shirgur/UnsupervisedDepthFromFocus

license: MIT

license_type: permissive

license_source: github-api


text:
Cgpy struct energy analysis

PR for adding some functionality needed for CG PyRosetta analysis:
Things I'm working on:

[x] Making clustering analysis work without CGModel object
[x] Ability to keep track of indices of frames when clustering (used to keep track of energies of clustered structures)
[x] Add flag that outputs trajectory of each cluster
[x] Add testing for all new functionality

Codecov Report

Merging #27 (3dd5e1a) into master (a9d7107) will decrease coverage by 0.25%.
The diff coverage is 69.69%.

Also I tried out the core_points_only=True option and got the same exact medoid structure as with using all points in the cluster (there are about 1800 total points in the cluster, and about 1600 core points). Could be just my specific helix system has a well-defined cluster center, but we should check this on other systems. The RMSD of the cluster structures to its medoid is lower when we do only consider the core points.

Looks good! We might want to just always return the original indices and labels to avoid different numbers of outputs, but not critical to change right now.
Let's test that the medoid coordinates match the medoid pdb file, and then we should be good to merge.
One other minor thing: we seem to be using 'indices' and 'indicies' interchangeably. These should all be the correct spelling 'indices' to avoid confusion

Somehow forgot how to spell indices while working on this. Should be a quick fix!

source: gharchive/pull-request

authors: codecov-io cwalker7 tlfobe


text:
Update php@8.1

Build php@8.1

:beers: @BrewTestBot has triggered a merge.

repo: shivammathur/homebrew-php


text:
Source Generator for Interfaces

[ ] Interfaces are generated from class automatically.
[ ] Interfaces are not in their own project.

Closing as CsWinRT can do this


text:
🛑 SNAP is down

In 0421ad5, SNAP (https://supplylink.iata.org) was down:

HTTP code: 503
Response time: 433 ms

Resolved: SNAP is back up in eca14c3 after 1 hour, 1 minute.

repo: shomaru/upptime


text:
[Bug]: Issue with minio storage class

Steps to reproduce
Deploy this helm chart where there is no standard storage class and let the default value for storage in minio.
What should happened?
Kubernetes should creates the PVC
What actually happened?
PVCs are in a pending state because the standard storage does not exist.
The helm should not have a default value for this, then Kubenetes would use the default storage configured on the cluster.
Relevant log output
No response
Your custom resource
No response

Resolved with https://github.com/shopware/helm-charts/pull/52

authors: renaudhager shadracnicholas

repo: shopware/helm-charts


text:
JWT key permission check always fails on Windows

PHP Version
8.1.13
Shopware Version
6.4.18.0
Expected behaviour
After a fresh install on Windows and having generated the required jwt/config/private.pem and jwt/config/public.pem files, starting the server symfony server:start -d and accessing the admin login page, both files should be correctly read from disk so the authorization server can be instantiated by the container and the whole page can function.
Actual behaviour
You get an exception:
{
	code: "0",
	status: "500",
	title: "Internal Server Error",
	detail: "User Notice: Key file "file://C:\projects\personal\project/config/jwt/public.pem" permissions are not correct, recommend changing to 600 or 660 instead of 666",
	meta: {
		// ...
	}
}

Full API Response

{
	"errors": [
		{
			"code": "0",
			"status": "500",
			"title": "Internal Server Error",
			"detail": "User Notice: Key file \u0022file://C:\\projects\\personal\\project/config/jwt/public.pem\u0022 permissions are not correct, recommend changing to 600 or 660 instead of 666",
			"meta": {
				"trace": [
					{
						"file": "C:\\projects\\personal\\project\\var\\cache\\dev_hae705bf1e4f7057c4da9d57bc278047b\\Container5V6QJWM\\Shopware_Core_KernelDevDebugContainer.php",
						"line": 22661,
						"function": "__construct",
						"class": "League\\OAuth2\\Server\\CryptKey",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\var\\cache\\dev_hae705bf1e4f7057c4da9d57bc278047b\\Container5V6QJWM\\Shopware_Core_KernelDevDebugContainer.php",
						"line": 11913,
						"function": "getApiAuthenticationListenerService",
						"class": "Container5V6QJWM\\Shopware_Core_KernelDevDebugContainer",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\symfony\\event-dispatcher\\EventDispatcher.php",
						"line": 245,
						"function": "Container5V6QJWM\\{closure}",
						"class": "Container5V6QJWM\\Shopware_Core_KernelDevDebugContainer",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\symfony\\event-dispatcher\\EventDispatcher.php",
						"line": 76,
						"function": "sortListeners",
						"class": "Symfony\\Component\\EventDispatcher\\EventDispatcher",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\shopware\\core\\Content\\Flow\\Dispatching\\FlowDispatcher.php",
						"line": 126,
						"function": "getListeners",
						"class": "Symfony\\Component\\EventDispatcher\\EventDispatcher",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\shopware\\core\\Framework\\Webhook\\WebhookDispatcher.php",
						"line": 161,
						"function": "getListeners",
						"class": "Shopware\\Core\\Content\\Flow\\Dispatching\\FlowDispatcher",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\shopware\\core\\Framework\\Event\\BusinessEventDispatcher.php",
						"line": 100,
						"function": "getListeners",
						"class": "Shopware\\Core\\Framework\\Webhook\\WebhookDispatcher",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\shopware\\core\\Framework\\Event\\NestedEventDispatcher.php",
						"line": 69,
						"function": "getListeners",
						"class": "Shopware\\Core\\Framework\\Event\\BusinessEventDispatcher",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\symfony\\event-dispatcher\\Debug\\TraceableEventDispatcher.php",
						"line": 293,
						"function": "getListeners",
						"class": "Shopware\\Core\\Framework\\Event\\NestedEventDispatcher",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\symfony\\event-dispatcher\\Debug\\TraceableEventDispatcher.php",
						"line": 148,
						"function": "preProcess",
						"class": "Symfony\\Component\\EventDispatcher\\Debug\\TraceableEventDispatcher",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\symfony\\http-kernel\\HttpKernel.php",
						"line": 139,
						"function": "dispatch",
						"class": "Symfony\\Component\\EventDispatcher\\Debug\\TraceableEventDispatcher",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\symfony\\http-kernel\\HttpKernel.php",
						"line": 75,
						"function": "handleRaw",
						"class": "Symfony\\Component\\HttpKernel\\HttpKernel",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\symfony\\http-kernel\\Kernel.php",
						"line": 202,
						"function": "handle",
						"class": "Symfony\\Component\\HttpKernel\\HttpKernel",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\symfony\\http-kernel\\HttpCache\\SubRequestHandler.php",
						"line": 86,
						"function": "handle",
						"class": "Symfony\\Component\\HttpKernel\\Kernel",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\symfony\\http-kernel\\HttpCache\\HttpCache.php",
						"line": 479,
						"function": "handle",
						"class": "Symfony\\Component\\HttpKernel\\HttpCache\\SubRequestHandler",
						"type": "::"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\symfony\\http-kernel\\HttpCache\\HttpCache.php",
						"line": 452,
						"function": "forward",
						"class": "Symfony\\Component\\HttpKernel\\HttpCache\\HttpCache",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\symfony\\http-kernel\\HttpCache\\HttpCache.php",
						"line": 346,
						"function": "fetch",
						"class": "Symfony\\Component\\HttpKernel\\HttpCache\\HttpCache",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\symfony\\http-kernel\\HttpCache\\HttpCache.php",
						"line": 224,
						"function": "lookup",
						"class": "Symfony\\Component\\HttpKernel\\HttpCache\\HttpCache",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\shopware\\core\\HttpKernel.php",
						"line": 154,
						"function": "handle",
						"class": "Symfony\\Component\\HttpKernel\\HttpCache\\HttpCache",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\shopware\\core\\HttpKernel.php",
						"line": 79,
						"function": "doHandle",
						"class": "Shopware\\Core\\HttpKernel",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\public\\index.php",
						"line": 76,
						"function": "handle",
						"class": "Shopware\\Core\\HttpKernel",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\symfony\\runtime\\Runner\\Symfony\\HttpKernelRunner.php",
						"line": 35,
						"function": "handle",
						"class": "Symfony\\Component\\HttpKernel\\HttpKernelInterface@anonymous\u0000C:\\projects\\personal\\project\\public\\index.php:66$1776",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\vendor\\autoload_runtime.php",
						"line": 29,
						"function": "run",
						"class": "Symfony\\Component\\Runtime\\Runner\\Symfony\\HttpKernelRunner",
						"type": "-\u003E"
					},
					{
						"file": "C:\\projects\\personal\\project\\public\\index.php",
						"line": 12,
						"args": [
							"C:\\projects\\personal\\project\\vendor\\autoload_runtime.php"
						],
						"function": "require_once"
					}
				],
				"file": "C:\\projects\\personal\\project\\vendor\\league\\oauth2-server\\src\\CryptKey.php",
				"line": 80
			}
		}
	]
}

How to reproduce
On a Windows 11 machine, with PHP v8.1.13, Symfony CLI v5.4.20 and Docker v20.10.21 installed, run the following commands, from this repository's README.md:
> composer create-project shopware/production:dev-flex project
> cd project
> docker compose up -d
> symfony console system:install --basic-setup --drop-database --create-database -f
> symfony server:start -d

Then, generate your secret files and remember to set the password to shopware:
> openssl genrsa -out ./config/jwt/private.pem -aes256 4096
> openssl rsa -pubout -in ./config/jwt/private.pem -out ./config/jwt/public.pem

Finally, visit localhost:8000/admin. You should be greeted with the previously mentioned error.
Further Context
This happens because League\OAuth2\Server\CryptKey::__construct by default checks for file permissions. While that is a perfectly valid idea in Linux, in Windows files don't follow a similar permission system as as such, when requested, PHP always returns 666. This can be a pain for Windows developers and packages such as laravel/passport have decided to disable it by default, by passing the false as the third parameter of the constructor. It seems to be the maintainers "recommendation" as per https://github.com/thephpleague/oauth2-server/issues/779.
Now I'm really new to Shopware (this really was my first attempt at installing it), but it seems to me that simply editing shopware\core\Framework\DependencyInjection\api.xml definitions to pass false as the last argument should work. For testing purposes, I replaced old definitions in my vendor folder with the ones below, and it worked™.
<service class="League\OAuth2\Server\CryptKey" id="shopware.private_key">
    <argument>file://%kernel.project_dir%/config/jwt/private.pem</argument>
    <argument>shopware</argument>
+    <argument>false</argument>
</service>
<service class="League\OAuth2\Server\CryptKey" id="shopware.public_key">
    <argument>file://%kernel.project_dir%/config/jwt/public.pem</argument>
+    <argument>null</argument>
+    <argument>false</argument>
</service>

Perhaps not always disabling it, but only on Windows? I think this could be done with <argument type="expression">PHP_OS_FAMILY !== 'Windows'</argument>, but I haven't tested it.
Either way, I would be happy to work on a PR to solve this issue if you could point me in the right direction.

Another approach could be to do an CompilerPass. Feel free to make a PR, but we officially don't support Windows. So I assume there are a lot of other problems

@shyim which of those approaches would you guess would be better? Just so I know where to start.

Disabling permission checks by default
Disabling permission checks on Windows only, using a <argument type="expression"> tag
Disabling permission checks on Windows only, doing a CompilePass

I understand getting this to work on Windows is gonna be a battle, but I'd like to entertain it.

Disabling permission checks on Windows only, doing a CompilePass

Sounds the best for me as expressions are on runtime

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-37857.
[created from NEXT-37857, comment 488481]

authors: rmobis shopwareBot shyim

repo: shopware/platform


text:
Wrong tax-calculation when B2B without valid vatid

The Tax calculation for B2B without valid vatID needs to be calculated based on the origin country and not based on the delivery country.
[https://europa.eu/youreurope/business/taxation/vat/cross-border-vat/index_en.htm#withintheeusellgoodsanotherbusiness-1|https://europa.eu/youreurope/business/taxation/vat/cross-border-vat/index_en.htm#withintheeusellgoodsanotherbusiness-1|smart-link]

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-39329
[created from NEXT-39329, comment 507862]

repo: shopware/shopware


text:
Disable xdebug for travis build

see https://docs.travis-ci.com/user/languages/php#Disabling-preinstalled-PHP-extensions and https://getcomposer.org/doc/articles/troubleshooting.md#xdebug-impact-on-composer

Compared to a cli command run with "xdebug" enabled a speed improvement by a factor of up to 3 is not uncommon.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-15069.
Please use this issue to track the state of your pull request.

authors: alfredbez shopwareBot


text:
FIX: NEXT-40112 - Immediately invalidate critical caches

We will use delayed cache invalidation by default starting with 6.7, however some critical object caches should be invalidated immediately as stale reads could be critical

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

authors: CLAassistant keulinho


text:
Fixed valueField comment in UPGRADE-5.2.md

Description
Please describe your pull request:

Why is it necessary?
It looks better

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-17590.
Please use this issue to track the state of your pull request.

authors: shopwareBot shyim


text:
Improve RedisTimestampTagger logic for deciding whether to wrap or not

Progress towards https://github.com/shotover/shotover-proxy/issues/535
Reenables a bunch of integration test cases, most noteworthy is test_info which would have prevented the raised issue.
I replaced the current wrapping decision logic black list with a sort of white list.
It allows any QueryType::Read or QueryType::ReadWrite command that has at least one argument.
This is currently an improvement other the previous implementation.
My reasoning for this approach is that it is not meaningful to attach a timestamp to a non-read command. Is my understanding correct here?
But I suspect its still not accurate enough, we should probably instead have a proper whitelist that specifies every command that can be compatibly wrapped by RedisTimestampTagger.
If we think a proper whitelist is the way to go, i'm happy to either do that in this PR or a follow up PR.

Oh nice!
That performance improvement must be because Write commands skip the wrapping logic.

repo: shotover/shotover-proxy


text:
Issues with gamess external basis set d2tzvp and iodine

Hello, thanks a lot for this repository and the instructions on how to use EXTBASIS.txt with gamess.
All works fine with d2tzvp except for molecules with iodine, e.g. iodomethane. The energy does not converge, keeps oscilating:
ITER EX DEM     TOTAL ENERGY        E CHANGE  DENSITY CHANGE     ORB. GRAD
   1  0  0    -2688.9031574371 -2688.9031574371  47.972062755   0.000000000
   2  1  0    -2712.8674452076   -23.9642877705 166.206976187   0.869817704
   3  2  0    -2505.6269175992   207.2405276084 165.606852333   1.502258158
   4  3  0    -2670.6303385744  -165.0034209752  65.987403521   0.866474212
   5  0  0    -2466.3695781028   204.2607604716  28.721711243   2.232559846
   6  1  0    -2713.5127307253  -247.1431526224 159.015100570   0.971159474
   7  2  0    -2505.1464430413   208.3662876839 157.638077469   1.579522623
   8  3  0    -2670.5450082936  -165.3985652522  65.781634675   0.879239380
   9  0  0    -2466.3019640269   204.2430442667  28.730265657   2.234209766
  10  1  0    -2713.5157210149  -247.2137569879 159.102230658   0.972023360
  11  2  0    -2505.1475679112   208.3681531036 157.727222664   1.579171900
  12  3  0    -2670.5457304377  -165.3981625265  65.783387844   0.879128294
  13  0  0    -2466.3025277625   204.2432026752  28.730238381   2.234197719
  14  1  0    -2713.5156762485  -247.2131484861 159.101489561   0.972018067
  15  2  0    -2505.1475500997   208.3681261488 157.726464386   1.579174814
  16  3  0    -2670.5457235111  -165.3981734114  65.783371216   0.879129344
  17  0  0    -2466.3025223706   204.2432011406  28.730238749   2.234197835
  18  1  0    -2713.5156766288  -247.2131542582 159.101496645   0.972018122
  19  2  0    -2505.1475502493   208.3681263795 157.726471635   1.579174786
  20  3  0    -2670.5457235752  -165.3981733259  65.783371371   0.879129334
  21  0  0    -2466.3025224205   204.2432011547  28.730238745   2.234197834
  22  1  0    -2713.5156766248  -247.2131542043 159.101496581   0.972018121
  23  2  0    -2505.1475502481   208.3681263767 157.726471569   1.579174786
  24  3  0    -2670.5457235745  -165.3981733264  65.783371370   0.879129334
  25  0  0    -2466.3025224199   204.2432011546  28.730238745   2.234197834
  26  1  0    -2713.5156766249  -247.2131542049 159.101496570   0.972018121
  27  2  0    -2505.1475502480   208.3681263769 157.726471558   1.579174786
  28  3  0    -2670.5457235745  -165.3981733265  65.783371369   0.879129334
  29  0  0    -2466.3025224200   204.2432011545  28.730238745   2.234197834
  30  1  0    -2713.5156766247  -247.2131542047 159.101496566   0.972018121

When checking the basis set exchange website for this atom, there is an extra ECP section:
https://www.basissetexchange.org/basis/def2-tzvp/format/gamess_us/?version=1&elements=53
I'm not sure if this is the source of the problem or if this ECP section should be included somehow. A minimal input file follows below:
 $contrl scftyp=rhf $end
 $contrl mplevl=0 $end

 $system timlim=10000 mwords=20 $end
 $contrl ISPHER=1 $END

! https://github.com/shoubhikraj/molecular-modelling/tree/main/basis-sets
 $BASIS GBASIS=d2tzvp EXTFIL=.t. $END

 $guess guess=HUCKEL $end
 $SYSTEM MWORDS=500 $END

 $DATA
http://cactus.nci.nih.gov/chemical/structure/IODOMETHANE/file?format=sdf&get3d=True
C1
I     53.0     -0.2367000000    0.0000000000    0.0000000000
C      6.0      1.9253000000    0.0000000000    0.0000000000
H      1.0      2.2886000000    0.0000000000    1.0277000000
H      1.0      2.2886000000   -0.8900000000   -0.5138000000
H      1.0      2.2886000000    0.8900000000   -0.5138000000
 $END

Any insight on this would be very much appreciated.

@rpseng Hi, glad to hear the files are useful 😄.
You guessed correctly that the problem is coming from the ECP. From what I can see in basis set exchange, all elements after Kr have ECP's. So it's not surprising that the calculation fails. Adding the $ECP group for iodine should fix your problem:
$contrl scftyp=rhf $end
 $contrl mplevl=0 $end

 $system timlim=10000 mwords=20 $end
 $contrl ISPHER=1 PP=READ $END

! https://github.com/shoubhikraj/molecular-modelling/tree/main/basis-sets
 $BASIS GBASIS=d2tzvp EXTFIL=.t. $END

 $guess guess=HUCKEL $end
 $SYSTEM MWORDS=500 $END

 $DATA
http://cactus.nci.nih.gov/chemical/structure/IODOMETHANE/file?format=sdf&get3d=True
C1
I     53.0     -0.2367000000    0.0000000000    0.0000000000
C      6.0      1.9253000000    0.0000000000    0.0000000000
H      1.0      2.2886000000    0.0000000000    1.0277000000
H      1.0      2.2886000000   -0.8900000000   -0.5138000000
H      1.0      2.2886000000    0.8900000000   -0.5138000000
 $END

 $ECP
I-ECP GEN    28    3
4     ----- f-ul potential -----
    -21.84204000      2      19.45860900
    -28.46819100      2      19.34926000
     -0.24371300      2       4.82376700
     -0.32080400      2       4.88431500
7     ----- s-f potential -----
     49.99429300      2      40.01583500
    281.02531700      2      17.42974700
     61.57332600      2       9.00548400
     21.84204000      2      19.45860900
     28.46819100      2      19.34926000
      0.24371300      2       4.82376700
      0.32080400      2       4.88431500
8     ----- p-f potential -----
     67.44284100      2      15.35546600
    134.88113700      2      14.97183300
     14.67505100      2       8.96016400
     29.37566600      2       8.25909600
     21.84204000      2      19.45860900
     28.46819100      2      19.34926000
      0.24371300      2       4.82376700
      0.32080400      2       4.88431500
10    ----- d-f potential -----
     35.43952900      2      15.06890800
     53.17605700      2      14.55532200
      9.06719500      2       6.71864700
     13.20693700      2       6.45639300
      0.08933500      2       1.19177900
      0.05238000      2       1.29115700
     21.84204000      2      19.45860900
     28.46819100      2      19.34926000
      0.24371300      2       4.82376700
      0.32080400      2       4.88431500
C-ECP NONE
H-ECP NONE
H-ECP NONE
H-ECP NONE
 $END

GAMESS's ECP input is a bit tricky in that you need to define the ECP for each atom in the exact same order they appear in $DATA, and you need to do it for all the atoms - even the ones that do not have ECP. (https://www.msg.chem.iastate.edu/gamess/GAMESS_Manual/docs-input.txt). Once you put the ECP in for Iodine, the calculation runs smoothly.

         --------------------------
                RHF SCF CALCULATION
         --------------------------

    NUCLEAR ENERGY =        60.9020337474
    MAXIT =   30     NPUNCH=    2
    EXTRAP=T  DAMP=F  SHIFT=F  RSTRCT=F  DIIS=F  DEM=F  SOSCF=T
    DENSITY MATRIX CONV=  1.00E-05
    SOSCF WILL OPTIMIZE    1394 ORBITAL ROTATIONS, SOGTOL=   0.250
    MEMORY REQUIRED FOR RHF ITERS=    126541 WORDS.

ITER EX DEM     TOTAL ENERGY        E CHANGE  DENSITY CHANGE     ORB. GRAD
  1  0  0     -325.7821902639  -325.7821902639   2.334790141   0.000000000
         ---------------START SECOND ORDER SCF---------------
  2  1  0     -336.1580140330   -10.3758237691   0.450395631   0.155375000
  3  2  0     -336.2542577709    -0.0962437380   0.126198268   0.058815788
  4  3  0     -336.2870328290    -0.0327750581   0.020510540   0.007031238
  5  4  0     -336.2875663758    -0.0005335468   0.008046922   0.003710974
  6  5  0     -336.2877495081    -0.0001831323   0.001741688   0.000532772
  7  6  0     -336.2877606451    -0.0000111370   0.000878706   0.000358150
  8  7  0     -336.2877619997    -0.0000013546   0.000318105   0.000091646
  9  8  0     -336.2877621418    -0.0000001421   0.000064803   0.000020826
 10  9  0     -336.2877621527    -0.0000000109   0.000011581   0.000005576
 11 10  0     -336.2877621532    -0.0000000005   0.000003352   0.000001168
 12 11  0     -336.2877621532    -0.0000000000   0.000000912   0.000000215

         -----------------
         DENSITY CONVERGED
         -----------------
    TIME TO FORM FOCK OPERATORS=       0.5 SECONDS (       0.0 SEC/ITER)
    TIME TO SOLVE SCF EQUATIONS=       0.0 SECONDS (       0.0 SEC/ITER)

FINAL RHF ENERGY IS     -336.2877621532 AFTER  12 ITERATIONS

Hello @shoubhikraj, thanks a lot for the prompt response!
Now I'm thinking on how I can automate this. I'm planning to update the basis set we use on this project https://github.com/lvpp/sigma, but we need to run it for about 2000 molecules. Current automation uses openbabel to create the gamess input from a .mol and an extra file with the gamess keys we use. With this per atom extra input, that will be very tricky...

authors: rpseng shoubhikraj

repo: shoubhikraj/molecular-modelling


text:
add "this"

First, feel sorry for my English.
In the closure,  the both "typeof" of "document" & "window"  are return "undefined" without "this" prefix. But they are under the variable  "this".
So ...

@JasonsCPL  thanks for your contribution. This piece of code is currently just as a temporary hack around dependencies in nodejs.

authors: JasonsCPL tivie

repo: showdownjs/showdown

license: mit

license_source: bigquery


text:
Request: Could you push a release now that you have SMP support

SPM errors out at the moment because there is not Package.swift for version 2.4.0
(I know I can use master or a specific commit to work around this - but versions are neater)

ps: thanks for a tremendously useful package :)

@ConfusedVorlon Could you please live with a master branch for now? Sorry for the inconvenience.

I certainly can. Is there a reason not to just tag 2.4.1 though? It seems like the work of a moment...

authors: ConfusedVorlon shpakovski

repo: shpakovski/MASShortcut


text:
Experimenting with a custom test file

Hi,
Thanks for this great work.
I'm trying to use one of the trained models to predict the order of N sentences that come from independent sources.  There is no ground-truth for the ordering, and I just want to obtain the predictions from the model to construct a document based on on the predicted order of sentences.
I'd appreciate your help with some difficulties that I have.
I created a a test file in this format:
id \t sentence1 \t sentence2 \t label \t index_of_sentence1_in_document \t index_of_sentence2_in_document
I set index_of_sentence1_in_document to 0, and index_of_sentence2_in_document  to 1, and I assume that this has no influence on the predictions.
Question 1: is the test file supposed to include all possible combinations of two sentences from the N sentences that I have?
After running the model, I got a results file, with the new columns of logits and prediction label, and now I'd like to use the topological sort to predict the global order of the sentences.
However, when I try to run the sort as suggested here, I get an error in line 187:
    docid, nvert, npairs = ids.split('-')
ValueError: not enough values to unpack (expected 3, got 1)

This makes sense because the ids variable is an integer, not a string with dashes that can be split into 3 parts.
Question 2: does that mean that my original test file should include a triplet in the id column?
Could you please help with this?
Thanks!

Hi,

Question 1: is the test file supposed to include all possible combinations of two sentences from the N sentences that I have?

Yes, you need to include all (N choose 2) combinations of pairs of sentences in your test file to get predictions for each pair.

Question 2: does that mean that my original test file should include a triplet in the id column?

Yes, you need to know how many pairs of sentences belong to each document. I had multiple documents in my test set, hence I used  docid, nvert, npairs to indicate the document id, number of vertices (equal to number of sentences) in the document and number of pairs (N choose 2). This was done to give an idea of how many future lines belong to the current document and should be added to the current graph (here). If you have only one document in your file then you will not need these. If you have multiple documents then yes, you need triplets in the form doc_id-nver-npairs.

Thanks.
If I have sentences from multiple documents, and I use the  docid-nvert-npairs pattern in the id column of my input tsv file, since docid, nvert and npairs are constants for the same doc,  I get that all sentences from the same doc have the same id. This means that the id column isn't unique per example. Isn't that a problem for the bert-based classifier?

I tried to continue and have two more questions:
1 - When I run the topological search on the result file, I see that it uses the values from the pos_a and pos_b columns in the graph construction (line 197 - pos_s1, pos_s2 = int(data[j][4]), int(data[j][5])). It seems like these values are used as vertices ids. Is that means that I need to use a unique pos value for every sentence from the same document? like, enumerating them from 0 to N?
2 - to get the result of the sort for each document, should I print the variable order after it is assigned a value in line 209?
        order = g.topologicalSort()

Thanks again!

This means that the id column isn't unique per example. Isn't that a problem for the bert-based classifier?

You are right. All the examples of the same doc don't have unique id. This has not been a problem fo me when I used the 2.3.0 version of transformers lib. If you are using a different version then you can check how they process the InputExample, this line.

Is that means that I need to use a unique pos value for every sentence from the same document? like, enumerating them from 0 to N?

Yes, exactly. You have to just enumerate sentences in a document and whether sentence3 will come before sentence5 would be decided by the classifier prediction. So Line 197 tells which of the two sentences was first while asking the classifier. This is because while creating the file one of the two sentences was randomly chosen to be first (here). An example to clarify this:
If you had a document (doc_id=1) with 4 sentences: s1, s2, s3, s4. Then you have 6 pairs of sentences and the input file looks like (sentence index starts from 0):
doc_id-nvert-npairs \t sentence1 \t sentences2 \t label \t pos_sentence1 \t pos_sentence2
1-4-6 \t s2 \t s1 \t 0 \t 1 \t 0  # Randomly choosing s2 to be first and asking classifier if s2 precedes s1
1-4-6 \t s1 \t s3 \t 1 \t 0 \t 2  # Randomly choosing s1 to be first and asking classifier if s1 precedes s3
1-4-6 \t s4 \t s1 \t 0 \t 3 \t 0
1-4-6 \t s2 \t s3 \t 1 \t 1 \t 2
1-4-6 \t s4 \t s2 \t 0 \t 3 \t 1
1-4-6 \t s3 \t s4 \t 1 \t 2 \t 3
If you don't have ground truth labels then you can leave them as 0. This was necessary only to calculate the metrics.

2 - to get the result of the sort for each document, should I print the variable order after it is assigned a value in line 209?

Yes, you don't have to calculate the metric. You can skip the update stats part and only print the orders after line 209.

You can use this fn to write an input file for your data. You will have to change this part to load your documents (Line 123)and have documents as a list of sentences(Line 128). You can copy and modify that function to suit your data loading.

Many thanks, I think I got the point.

authors: assaftibm shrimai


text:
Created website with html CSS

Please check. Thanks

Make sure to follow & star the repo

sir please add the hacktoberfest-accepted label to the merged PR


text:
[Plugins]: Revamp the Shuttle Secrets plugin

The current approach to Secrets is Shuttle-native.
Evolving the plugin could include support for .env files and allowing the secrets to be set as env variables in more stages of the Shuttle deployment.
Ideas are appreciated.

This issue is a part of the Product Feature Poll (all issues). React with :+1: if you want this feature. Comment if you have suggestions related to this feature.

I'm thoroughly happy with the simplicity of secrets.  It follows similar frameworks such as Cloudflare workers, except is even easier to work with.
Please don't change :(

Yeah I like the current implementation of using Secrets.toml as the main secret store. So there's no need to introduce yet another new file type to the workspace (.env).

The idea is mainly about making it easier to customize the approach, such as using a .env file if you want to

I think that having multiple ways to do this makes the feature more complicated, and makes reading other projects slightly more involved. There should really only be 2 files capable of setting secrets, one for local runs and one for deployments.
It would also be, well, difficult to differentiate between the deployment secrets and the dev secrets.  Having a .env file violates this.

and the ability to automatically load all secrets into the environment, like dotenv crates do.

Now this is great.  Definitely would want it to be a deployment flag, though.

Another improvement that is probably coming up is to have it built into the shuttle-runtime crate by default so that you don't even need to add a separate crate to use it.

This makes no difference to me.  The only reason I can see to not do this is to avoid pay the compilation cost for an unused module.  But I can't imagine the secrets module would have any real impact on compile times.

There is also room to reduce the boilerplate required when getting secrets from the SecretStore. How does this sound?

Now this is something I would be very excited for.  It's a bit annoying having to pass around secrets, or throw them into a global static variable. Would love to see this.

It would also be, well, difficult to differentiate between the deployment secrets and the dev secrets. Having a .env file violates this.

Next.js uses .env + .env.local + a few other options. Secrets[.dev].toml is an echo of that pattern.

a deployment flag

How about #[shuttle_secrets::Secrets(set_env = true)] secrets: SecretStore? They would be set at runtime (when loading the secrets) with this approach, in which case it makes sense to have it declared in the macro. A deployment flag would imply it couldn't be applied on a local run.

throw them into a global static variable

env vars are kind of like global variables :smirk:

authors: DevKAVI bavalpey jonaro00

repo: shuttle-hq/shuttle


text:
Camelcase table names in PostgreSQL are not treated properly.

Describe the bug
synth does not respect CaMelCase table names in PostgreSQL properly.
To Reproduce
Steps to reproduce the behavior:

Create a table in PostgreSQL database with the name "fooBar"
 $ psql -c 'create table "fooBar" (id integer);'

Run synth import mydb --from postgresql://...

See the error

Error: error returned from database: relation "foobar" does not exist

Caused by:
    relation "foobar" does not exist

Expected behavior
synth should support table names formatted in different cases in PostgreSQL.
Environment (please complete the following information):

OS: MacOS 13.0
PostgreSQL: 14.5 (Debian 14.5-1.pgdg110+1)

I made some changes to your PR and CI passes. People will still need to compile it themselves to use this, as I am waiting until I have fixed 1.65 compatibility to release a new update.

I made some changes to your PR and CI passes. People will still need to compile it themselves to use this, as I am waiting until I have fixed 1.65 compatibility to release a new update.

@all-contributors please add @iamwacko review.

authors: iamwacko mhorbul

repo: shuttle-hq/synth


text:
add:murilo-simio

Description
Inclusion on users list
Checklist

[x] I have read and followed the Contribution Guidelines.
[x] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

@murilo-simio Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and help us grow even further!

authors: murilo-simio shyamtawli

repo: shyamtawli/devFind


text:
Right shift key and backspace does not become delete

The key in the upper right corner of the keyboard on Planet devices is marked with a left pointing arrow with the word Del above it. Even though the arrow isn't the "proper" backspace symbol, this reasonably indicates that this button is supposed to work as backspace when pressed on its own and as delete in combination with either or both of the shift keys.
When I press the left shift key and backspace, delete works as expected, that is, the character on the right side of the cursor is erased. If I instead press the right shift key and backspace, it behaves like backspace, that is, the character on the left side of the cursor is erased, as if no shift key was pressed. When holding the device in one hand and typing with the other, this makes it unergonomic to use delete.
It doesn't seem to matter which Planet device I'm using. The behaviour consistent across the Gemini, Cosmo and Astro, on their, at the time of writing this, latest officially available Android firmwares. It doesn't seem to matter which app I'm using either. The behaviour seems to be the same wherever I can edit text.
One peculiarity is that if the cursor is at the beginning of the first line in the document or view, then, and only then, does right shift and backspace actually work as delete. That might make this issue a tad harder to notice. Were one to just type something into an empty document and go to the beginning of the line, the right shift key and backspace combination would appear to be flawless.
Pressing both shift keys and backspace also behaves like backspace and not, as expected, delete (except at the beginning of the first line). While it might be unlikely that users would want to press both shift keys, it might still be interesting from an investigative perspective. If a user holds down the left shift key and presses backspace, delete works. If the user keeps holding down the left shift key but then also holds down the right shift key, backspace becomes backspace again (except at the beginning of the first line).
I seem unable to apply labels. If I could, I'd label this issue with Astro-Slide Cosmo-Communicator Gemini-PDA Keyboard-Issue.

I'll apply Keyboard issue. Users cannot assign labels, with good reason.

This has been fixed in the latest V7 firmware

authors: Daz-Mataz shymega wikholm

repo: shymega/planet-devices


text:
Ergonomics of SiconosVector initialization

I propose that it would be good to make more use of the available ways to initialize SiconosVector throughout the code.  There is a lot of code that does things like,
SP::SiconosVector v = SP::SiconosVector(new SiconosVector(3));
v->zero();

or
v->setValue(0, 0);
v->setValue(1, 0);
v->setValue(2, 1);

There are many cases where it would be nice just to have something closer to Vector(value1, value2...).
Array initialization
I just discovered that SiconosVector actually has an initializer for a constant value, and an initializer for std::vector.  This means that currently with C++98, we can already do:
SP::SiconosVector zeroVector(new SiconosVector(3,0));

and
double a[] = {0,0,1};
SP::SiconosVector axis1(new SiconosVector(std::vector<double>(a, a+3)));

We can simplify the last one by adding SiconosVector const double* initializer with a size parameter,
double a[] = {0,0,1};
SP::SiconosVector axis1(new SiconosVector(a, 3));

or it's even possible to have a template function that infers the array size at compile time (quite clever, found on stack overflow),
template< typename T, size_t N >
SP::SiconosVector makeSiconosVectorSP( const T (&data)[N] )
{
  std::vector<T> v(data, data+N);
  return std11::make_shared<SiconosVector>(v);
}

which makes possible,
double a[] = {0,0,1};
SP::SiconosVector axis1 = makeSiconosVectorSP(a);

In fact I even found that the following two cases work:
SP::SiconosVector axis2(makeSiconosVector((double[]){0,0,1}));
SP::SiconosVector axis1(new SiconosVector((const double[]){0,0,1}, 3));

Although the latter fails without "const", and I am not sure that this is C++ standard -- however it works in both g++ and clang++ for me, with -std=c++98.  (g++ 5.4.0 and clang++ 3.8.0)
On the other hand if one extends SP::SiconosVector to a derived class, i.e.,
  class MySPSiconosVector : public std11::shared_ptr< ::SiconosVector >
  {
  public:
    template< typename T, size_t N >
    MySPSiconosVector( const T (&v)[N] )
      : std11::shared_ptr< ::SiconosVector >(
        std11::make_shared< ::SiconosVector >(v, N)) {}
  };

Then I can declare it very tersely indeed:
SP::MySPSiconosVector axis1((double[]){0,0,1});

I tried to verify that when compiled with C++11 no changes are needed to support initializer lists, because we support std::vector, so this should work,
SP::SiconosVector axis1(new SiconosVector({0.0, 0.0, 1.0}));
SP::MySPSiconosVector axis2({0.0, 0.0, 1.0});
SP::MySPSiconosVector axis2({0.0, 0.0, 1.0});

However both g++ and clang++ report ambiguity with the SiconosVector(const std::string& filename, bool b = true) constructor!  I don't know why, since they are clearly lists of doubles, but it would be really, really good to fix this for the future.
Temporarily removing the default value for the string constructor's bool for testing makes both cases work.  (Actually I had to make no changes to the Siconos codebase when I did this, but this might be because i have serialization turned off right now.)  You must provide floating point values, otherwise it infers the type wrongly.  I tested all these cases while fixing up the PrismaticJoint.cpp example, so I tested against a reference file and it did not generate errors.
To pose an actual question here, I guess I am wondering, for the examples at least, if anyone else thinks it would be good to "standardize" on a way to initialize "literal" SiconosVectors?  At the very least it would be nice to use the value initializer more instead of v->zero().  Adding the array/double* constructor would not be so impactful and might be useful.  Although a SiconosVector(const double* v, int size) constructor would be confusing in the second argument between "size, value" and "array, size"..  Perhaps it would be more consistent to have SiconosVector(int size, const double* v).
At the very least it would be cool if zero() returned the pointer to the SiconosVector, then you could do:
SP::SiconosVector v(new SiconosVector(3)->zero());

I tried adding the makeSiconosVector above as a templated constructor and that worked okay:
template< typename T, size_t N >
  SiconosVector( const T (&v)[N] ) : SiconosVector(N)
    { resize(N); for (int i=0; i<N; i++) setValue(i,v[i]); }

which makes possible in C++98:
SP::SiconosVector axis1(new SiconosVector((const double[]){0, 0, 1}));

But in fact the SP::SiconosVector v(new SiconosVector(..)) pattern is so common in Siconos that imho it would make a lot of sense to have a function for this.
Or possibly we should only add known-size array constructors to the proposed SiconosVector3/4/7 classes in #135. e.g.,
SiconosVector3(x,y,z);

Zero initialization
Another idea is to replace the "size" constructor with a boolean constructor for zero-initialization defaulting to true,
SiconosVector(unsigned row, bool zeroInitialize = true, Siconos::UBLAS_TYPE type = Siconos::DENSE);

so that by default we get zero vectors, and internally for performance we can explicitly specify not to zero the values. (Not that this is a performance bottleneck.)
In any case I think it would be good practice from a security point of view to force users to explicitly say when they don't want the vector initialized.
Unfortunately this seems to cause ambiguity with the SiconosVector(int, int) constructor, but if I put the bool after the type argument it works,
SiconosVector(unsigned row, Siconos::UBLAS_TYPE type = Siconos::DENSE, bool zeroInitialize = true);

which is not as nice but maybe okay for internal code.
I've tried these ideas and they compile without complications in both g++ and clang++.  If there is some agreement I'll make a PR for the const double* and zeroInitialize constructors, and maybe the template constructor... depending on opinions.  I am guessing that changing SP::SiconosVector to a class will be more controversial.  On the other hand adding a templated makeSiconosVectorSP() function would be really easy and useful. Or I could just add to #135.
Following this, some cleanup at least in the examples would nice, because it really takes you an extra 5 seconds to read the code when you come across something like this,
V1.setValue(2, 1);
V1.setValue(0, 3);
V1.setValue(1, 2);

I don't think this is in any way a pressing issue, but it would bring some "ergonomics" to Siconos, in my opinion.

I fixed the ambiguity with initializer lists in fd628978989fccb9a55027eb872a9945be9d3ba8, which I figure should be fairly uncontroversial.  Better to get c-dash to test it immediately.  For the other ideas I'll be more careful.

@radarsat1 Fully agree with all your proposition
Zero Initialization.
Clearly, we can initialize the vector to zero by default. It will cleanup the example but also the kernel code.
Array initialization
I am ok with your proposition.

Ok, I also got tired of the useless output from "print" in Python to I took the initiative of adding toString() for the other algebra types and added __str__() methods for SWIG.  Seems to work and not break anything so far..
I still hesitate with the double* and template initializers, they are cool but maybe aren't necessary with the ideas in #135, and with C++11 initializer lists.  (e.g., SiconosVector7 has a pre-defined size, so we can just have a constructor that takes 7 doubles.)  I do like the idea of providing dedicated shared_ptr creation functions, these could just be renamed make_shared<SiconosVector> functions in fact.
@bremond any thoughts?

I think that without c++11, even if we have fixed size vectors, the
double* and template initializer trick is interesting for all the
cases where the vector size is not 3, 4, 7 or whatever is predefined.
For bounded size arrays, the problem is that that this function
makeSiconosVectorSP works with some heap allocation and that is not
wanted, but we could have some specializations.
With c++11 and variadic template all of this may be greatly simplified.
In the end, I would like to have:
SiconosVector3 tmp = {1.0, 2.0, 3.0};
Let's switch to c++11.
Ok for the zero initialization. Maybe a global way to have NaN
initialization (for debug) ?

Let's implement that using initializer-list!
I agree that we should have a way to have an initialisation to signaling NaN for debug

Do we change something for the initialization ?

Transferred in wiki

authors: bremond radarsat1 vacary xhub

repo: siconos/siconos


text:
mysql中已有数据有办法导入吗

同步没有问题，但table中已有的数据怎么导入es呢？

初始化第一次会使用 mysqldump 导入所有数据，后面才走同步

好的，谢谢！

authors: ebsinori siddontang

repo: siddontang/go-mysql-elasticsearch


text:
Go 1.10: file_lock_test.go:43: Fatal call has possible formatting directive %s

cb568a3e5cc06256f91a2da5a87455f717eb33f4 does not pass unit tests with Go 1.10:
Testing: "/builddir/build/BUILD/go-cb568a3e5cc06256f91a2da5a87455f717eb33f4/_build/src/github.com/siddontang/go/filelock"
+ GOPATH=/builddir/build/BUILD/go-cb568a3e5cc06256f91a2da5a87455f717eb33f4/_build:/usr/share/gocode
+ go test -buildmode pie -compiler gc -ldflags '-extldflags '\''-Wl,-z,relro  '\'''
# github.com/siddontang/go/filelock
./file_lock_test.go:43: Fatal call has possible formatting directive %s
FAIL    github.com/siddontang/go/filelock [build failed]

can you send me a PR to fix it?

authors: nim-nim siddontang

repo: siddontang/go


text:
Support extraction of latitude and longitude degrees from LatLng class

Need:
Given an instantiated LatLng object, I should be able to extract the latitude and longitude in degrees.
Currently, this does not appear to be possible (please correct me if I am wrong, of course!).
Example:
I want to get the geometry of a given S2 cell's bounding box. I first convert from a cellId to a rectangle bounding box:
rb = s2sphere.Cell(s2sphere.CellId(cell_id)).get_rect_bound()

I can then get the lower coordinates via:
corner_1 = rb.lo()

If I submit just the variable, the repl will log: LatLng: 38.62134636194326,-90.20102331066352
I would like that lat and long value. Unfortunately, all values that are emitted appear to be converted to Angle objects.

This seems to already work for me:
import s2sphere as s2

v = s2.LatLng.from_degrees(10.0,20.0)
print(f"{v.lat().degrees},{v.lon().degrees}")


text:
autodetect coqtop version

Uses:

start working toward modularizing version-specific details
provide version-specific snippets/autocomplete

done:

[x] version detection
[x] version-specific xml-protocol (currently dependent coqtop version, not the protocol version)

repo: siegebell/vscoq


text:
feat: update tensorflow to 2.5.3

closes: #13
Signed-off-by: Felix Moessbauer felix.moessbauer@siemens.com

@chombourger : Please note: I did only run simple tests on amd64 to see if the build is correct. Before merging, this has to be extensively tested.

@chombourger : Please note: I did only run simple tests on amd64 to see if the build is correct. Before merging, this has to be extensively tested.

agreed. I can have our QA team run their tests and provide feedback

Works fine with meta-iot2050.

@chombourger Any news on the QA? Shall we merge this?

For the sake of IOT2050, I would welcome to move forward with this.

Same here. Our team hasn't completed their testing but we haven't seen any red herrings either

Thanks for the update. Then let's merge this, so meta-iot2050 can move forward.

authors: chombourger fmoessbauer jan-kiszka

repo: siemens/meta-coral


text:
How can I send data over Ubuntu to  Windows Hololense?

I have a question!

[ x] I searched the Wiki, open and closed issues for an answer. I tried my best to find the answer by myself without success. I believe that the discussion we will have in this issue, and the solutions we might find, will help me, and likely other community members who have a similar problem.

Here is my question:
How can I send data over WIFI to Hololense2? My Ubuntu publishes Data. Unity Subscribes this Data.
In the "play-Mode" everything is correct and it works. After succsessfull Deploy to Hololense2, i dont recive any data?
How can i slove this?

Hello @juliatum,
Do you think that this issue is related to #201, #278?
Have you tried this UWP version of ROS# fork?
I would suggest that you go over the closed issues regarding hololens, and try out the aforementioned fork. I will close this issue for the time being.

authors: berkayalpcakal juliatum

repo: siemens/ros-sharp


text:
Remove nginx-ovh and nginx-gke from ingress module

Since both nginx-ovh and nginx-gke are just simple patches of simple nginx, we will handle both of them as patches when needed.

Fixed by #76

repo: sighupio/fury-kubernetes-ingress


text:
Deploy fails for Kubernetes >= 1.22

Deployment is failing for Kubernetes 1.22 and 1.23, here's the output extract from CI:
79	+ bats -t katalog/tests/istio-operator/istio-minimal-install.sh
1s
80	1..2
1s
81	1: Install istio minimal profile
1s
82	Warning: spec.template.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution.nodeSelectorTerms[0].matchExpressions[0].key: beta.kubernetes.io/arch is deprecated since v1.14; use "kubernetes.io/arch" instead
4s
83	Warning: spec.template.spec.affinity.nodeAffinity.preferredDuringSchedulingIgnoredDuringExecution[0].preference.matchExpressions[0].key: beta.kubernetes.io/arch is deprecated since v1.14; use "kubernetes.io/arch" instead
4s
84	Warning: spec.template.spec.affinity.nodeAffinity.preferredDuringSchedulingIgnoredDuringExecution[1].preference.matchExpressions[0].key: beta.kubernetes.io/arch is deprecated since v1.14; use "kubernetes.io/arch" instead
4s
85	Warning: spec.template.spec.affinity.nodeAffinity.preferredDuringSchedulingIgnoredDuringExecution[2].preference.matchExpressions[0].key: beta.kubernetes.io/arch is deprecated since v1.14; use "kubernetes.io/arch" instead
4s
86	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
4s
87	unable to recognize "STDIN": no matches for kind "IstioOperator" in version "install.istio.io/v1alpha1"
4s
88	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
4s
89	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
4s
90	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
4s
91	# waiting... 0
6s
92	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
9s
93	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
9s
94	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
9s
95	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
9s
96	# waiting... 1
11s
97	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
14s
98	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
14s
99	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
14s
100	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
14s
101	# waiting... 2
16s
102	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
19s
103	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
19s
104	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
19s
105	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
19s
106	# waiting... 3
21s
107	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
24s
108	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
24s
109	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
24s
110	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
24s
111	# waiting... 4
26s
112	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
28s
113	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
28s
114	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
28s
115	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
28s
116	# waiting... 5
31s
117	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
33s
118	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
33s
119	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
33s
120	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
33s
121	# waiting... 6
35s
122	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
38s
123	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
38s
124	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
38s
125	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
38s
126	# waiting... 7
40s
127	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
43s
128	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
43s
129	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
43s
130	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
43s
131	# waiting... 8
45s
132	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
48s
133	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
48s
134	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
48s
135	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
48s
136	# waiting... 9
50s
137	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
53s
138	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
53s
139	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
53s
140	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
53s
141	# waiting... 10
55s
142	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
57s
143	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
57s
144	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
57s
145	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
57s
146	# waiting... 11
59s
147	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
62s
148	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
62s
149	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
62s
150	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
62s
151	# waiting... 12
64s
152	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
67s
153	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
67s
154	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
67s
155	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
67s
156	# waiting... 13
69s
157	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
72s
158	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
72s
159	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
72s
160	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
72s
161	# waiting... 14
74s
162	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
76s
163	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
76s
164	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
76s
165	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
76s
166	# waiting... 15
79s
167	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
81s
168	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
81s
169	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
81s
170	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
81s
171	# waiting... 16
83s
172	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
86s
173	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
86s
174	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
86s
175	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
86s
176	# waiting... 17
88s
177	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
91s
178	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
91s
179	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
91s
180	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
91s
181	# waiting... 18
93s
182	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
95s
183	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
95s
184	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
95s
185	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
95s
186	# waiting... 19
97s
187	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
100s
188	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
100s
189	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
100s
190	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
100s
191	# waiting... 20
102s
192	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
105s
193	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
105s
194	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
105s
195	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
105s
196	# waiting... 21
107s
197	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
110s
198	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
110s
199	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
110s
200	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
110s
201	# waiting... 22
112s
202	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
114s
203	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
114s
204	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
114s
205	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
114s
206	# waiting... 23
116s
207	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
119s
208	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
119s
209	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
119s
210	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
119s
211	# waiting... 24
121s
212	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
124s
213	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
124s
214	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
124s
215	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
124s
216	# waiting... 25
126s
217	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
129s
218	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
129s
219	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
129s
220	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
129s
221	# waiting... 26
131s
222	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
134s
223	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
134s
224	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
134s
225	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
134s
226	# waiting... 27
136s
227	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
138s
228	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
138s
229	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
138s
230	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
138s
231	# waiting... 28
140s
232	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
143s
233	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
143s
234	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
143s
235	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
143s
236	# waiting... 29
145s
237	unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
148s
238	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
148s
239	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
148s
240	unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
148s
241	not ok 1 Install istio minimal profile
148s
242	# (from function `loop_it' in file katalog/tests/istio-operator/./../helper.bash, line 28,
148s
243	#  in test file katalog/tests/istio-operator/istio-minimal-install.sh, line 15)
148s
244	#   `loop_it test 30 2' failed
148s
245	# Timeout waiting a condition

Deploy fails because istio-operator manifests use CustomResourceDefinition in version apiextensions.k8s.io/v1beta1 that is not supported anymore since Kubernetes >= 1.22.
unable to recognize "STDIN": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1"
unable to recognize "STDIN": no matches for kind "PodMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "ServiceMonitor" in version "monitoring.coreos.com/v1"
unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"
unable to recognize "STDIN": no matches for kind "MonitoringDashboard" in version "monitoring.kiali.io/v1alpha1"

I'm disabling the e2e checks in the meanwhile.

repo: sighupio/fury-kubernetes-service-mesh


text:
Add tidwall/buntdb instrumentation

This new module instruments the github.com/tidwall/buntdb package.

Please add dependabot configuration for the added modules (make gendependabot) and be sure to fix all test failures.

Codecov Report

Merging #228 (2860a50) into main (f051a59) will decrease coverage by 1.12%.
The diff coverage is 71.21%.

@@            Coverage Diff             @@
##             main     #228      +/-   ##
==========================================
- Coverage   77.12%   75.99%   -1.13%
==========================================
  Files          43       45       +2
  Lines        2037     2308     +271
==========================================
+ Hits         1571     1754     +183
- Misses        425      506      +81
- Partials       41       48       +7

Flag
Coverage Δ

Linux
75.99% <71.21%> (-0.64%)
:arrow_down:

Windows
?

macOS
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...n/github.com/tidwall/buntdb/splunkbuntdb/config.go
54.44% <54.44%> (ø)

...n/github.com/tidwall/buntdb/splunkbuntdb/buntdb.go
79.55% <79.55%> (ø)

...n/github.com/lib/pq/splunkpq/internal/connector.go
51.75% <0.00%> (-5.03%)
: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 f051a59...2860a50. Read the comment docs.

authors: MrAlias TomRoSystems codecov-commenter

repo: signalfx/splunk-otel-go


text:
tadGAN is not detecting benchmark anomaly

tdgan.zip

Orion version:
Python version:
Operating System:

Description
I am trying to use TadGAN pipeline; on 'nyc_taxi' datasets. But its not detecting the benchmark known anomalies as expected
What I Did
signal = 'nyc_taxi'
df = load_signal(signal)
orion = Orion(pipeline='tadgan')
anomalies =orion.fit_detect(df)

I get this warning error and also anomaly is not rightly detected.

error:
/usr/local/lib/python3.6/dist-packages/scipy/optimize/optimize.py:700: RuntimeWarning: invalid value encountered in subtract
  np.max(np.abs(fsim[0] - fsim[1:])) <= fatol):

Hi @JINU8, there is a bit of configuration needed for the nyc_taxi dataset that are not available in the default pipeline. You can use the hyperparameter settings to denote these changes as follows:
from orion.data import load_signal
from orion import Orion

signal = 'nyc_taxi'
df = load_signal(signal)

hyperparameter = {
    "mlprimitives.custom.timeseries_preprocessing.time_segments_aggregate#1": {
        "interval": 1800 # 30 minute level
    },
    "orion.primitives.timeseries_anomalies.find_anomalies#1": {
        "window_size_portion": 0.33,
        "window_step_size_portion": 0.1,
        "fixed_threshold": true
    }
}

orion = Orion(
    'tadgan',
    hyperparameter
)

anomalies = orion.fit_detect(df)

The randomized nature of tadgan will not guarantee that you get the exact same anomalies in each run, but they should be comparable.
To read more about the tadgan pipeline, we've written a blogpost that explains the series of transformations here.

repo: signals-dev/Orion


text:
Pass through cfg attributes to getters

While working on https://github.com/sigp/lighthouse/issues/2806 I noticed that superstruct doesn't handle cfg attributes gracefully. Previously it was applying the attribute to the fields of the variants but not to the getters, which lead to duplicate getter functions with the same name. This PR plumbs the cfg attributes through so that they apply to getters of all kinds (immutable, mutable, partial).
There are possibly more advanced interactions with cfg that we could want (like cfg only on specific variants) but I haven't thought that through in detail and I think this basic support is good enough for a lot of use-cases.

Thanks!

repo: sigp/superstruct


text:
Keep version numbers consistent across languages

This repository is eventually going to contain code to publish packages to each language ecosystem's respective package index. We need to figure out some scheme of keeping these version numbers consistent. So for instance, the v0.0.5 version of this package should be generated from the same set of Protobuf specifications regardless of whether we download it for Python, Java, etc.
Context: https://github.com/sigstore/protobuf-specs/pull/25#discussion_r1028498032

Thanks for filing! I'm going to mark as a dupe of #22 (and drop a comment over there) to keep the work in one place.

repo: sigstore/protobuf-specs


text:
Fix 'path' parameter behavior

This PR updates the ['eda', tool, 'path'] behavior to prepend the provided path to the system path and perform a search, rather than always hardcoding the provided path to the executable name.
In addition to this change, I made two tweaks to facilitate review of which executable is running:

Logging the directory used to run the exe alongside the version
Adding an entry to 'record' that stores the full path to the exe

Before:
| INFO    | job0  | syn        | 0  | Checking executable. Tool 'yosys' found with version '0.13+15'
| INFO    | job0  | syn        | 0  | Running in /home/noah/code/siliconcompiler/build/gcd/job0/syn/0
| INFO    | job0  | syn        | 0  | yosys -c /home/noah/code/siliconcompiler/siliconcompiler/tools/yosys/sc_syn.tcl
| INFO    | job0  | syn        | 0  | Finished task in 0.91s

After:
| INFO    | job0  | syn        | 0  | Tool 'yosys' found with version '0.13+15' in directory '/home/noah/eda/OpenROAD-flow-scripts/tools/install/yosys/bin'
| INFO    | job0  | syn        | 0  | Running in /home/noah/code/siliconcompiler/build/gcd/job0/syn/0
| INFO    | job0  | syn        | 0  | yosys -c /home/noah/code/siliconcompiler/siliconcompiler/tools/yosys/sc_syn.tcl
| INFO    | job0  | syn        | 0  | Finished task in 0.9s

One question I have: do we want the full path used hard coded in replay.sh? Current behavior is:
#!/bin/bash
/home/noah/eda/OpenROAD-flow-scripts/tools/install/yosys/bin/yosys -c /home/noah/code/siliconcompiler/siliconcompiler/tools/yosys/sc_syn.tcl

But I could see also changing this to
#!/bin/bash
PATH=/home/noah/eda/OpenROAD-flow-scripts/tools/install/yosys/bin/:$PATH
yosys -c /home/noah/code/siliconcompiler/siliconcompiler/tools/yosys/sc_syn.tcl

The first is more explicit/useful for exact replay, the second seems a bit more useful for experimenting with different versions (although one could always tweak the script by hand).

Great!
I would say the following more closely follows what is happening inside the task.

#!/bin/bash
PATH=/home/noah/eda/OpenROAD-flow-scripts/tools/install/yosys/bin/:$PATH
yosys -c /home/noah/code/siliconcompiler/siliconcompiler/tools/yosys/sc_syn.tcl

Sounds good! I will update the replay.sh and let you know when this is ready to merge.

Should be all set! I also took the opportunity to remove the platform-specific code for replay script generation like you asked about a while back, so it always outputs a bash-specific replay script.

authors: aolofsson nmoroze

repo: siliconcompiler/siliconcompiler


text:
Fix graph save

issue: https://github.com/siliconflow/onediff/issues/697

新的问题，用：
"""
Torch run example: python examples/text_to_image_sdxl.py
Compile to oneflow graph example: python examples/text_to_image_sdxl.py
"""
import os
import argparse

import oneflow as flow
import torch

from onediff.infer_compiler import oneflow_compile
from diffusers import StableDiffusionXLPipeline

parser = argparse.ArgumentParser()
parser.add_argument(
    "--base", type=str, default="stabilityai/stable-diffusion-xl-base-1.0"
)
parser.add_argument("--variant", type=str, default="fp16")
parser.add_argument(
    "--prompt",
    type=str,
    default="street style, detailed, raw photo, woman, face, shot on CineStill 800T",
)
parser.add_argument("--height", type=int, default=1024)
parser.add_argument("--width", type=int, default=1024)
parser.add_argument("--n_steps", type=int, default=20)
parser.add_argument("--saved_image", type=str, required=False, default="sdxl-out.png")
parser.add_argument("--seed", type=int, default=1)

args = parser.parse_args()

# Normal SDXL pipeline init.
OUTPUT_TYPE = "pil"
mydev="cuda:6"
torch.Generator(mydev).manual_seed(args.seed)

# SDXL base: StableDiffusionXLPipeline
base = StableDiffusionXLPipeline.from_pretrained(
    args.base,
    torch_dtype=torch.float16,
    variant=args.variant,
    use_safetensors=True,
)
base.to(mydev)

print("Compiling unet with oneflow.")
base.unet = oneflow_compile(base.unet)

base.unet.load_graph("./sdxl_graph.graph", mydev)

# Warmup with run
# Will do compilatioin in the first run
print("Warmup with running graphs...")
image = base(
    prompt=args.prompt,
    height=args.height,
    width=args.width,
    num_inference_steps=args.n_steps,
    output_type=OUTPUT_TYPE,
).images

print("Normal SDXL run...")
torch.manual_seed(args.seed)
image = base(
    prompt=args.prompt,
    height=args.height,
    width=args.width,
    num_inference_steps=args.n_steps,
    output_type=OUTPUT_TYPE,
).images
image[0].save(f"h{args.height}-w{args.width}-{args.saved_image}")

#base.unet.save_graph("sdxl_graph3.graph")

这种办法，换 device 加载，会报错：
Traceback (most recent call last):
  File "/data/home/yaochi/onediff/onediff_diffusers_extensions/examples/graph_save_example.py", line 57, in <module>
    image = base(
  File "/data/home/yaochi/miniconda3/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/data/home/yaochi/diffusers/src/diffusers/pipelines/stable_diffusion_xl/pipeline_stable_diffusion_xl.py", line 1236, in __call__
    latents = self.scheduler.step(noise_pred, t, latents, **extra_step_kwargs, return_dict=False)[0]
  File "/data/home/yaochi/diffusers/src/diffusers/schedulers/scheduling_euler_discrete.py", line 498, in step
    pred_original_sample = sample - sigma_hat * model_output
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:6 and cuda:0!

新的问题，用：
...
pred_original_sample = sample - sigma_hat * model_output
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:6 and cuda:0!

继续定位到，上重新加载时，
https://github.com/huggingface/diffusers/blob/main/src/diffusers/pipelines/stable_diffusion/pipeline_stable_diffusion.py#L971 产生的张量会出现在 cuda:0 上（而不是指定设备上），因此在后续设备上出错。
这个 cuda:0 的 tensor 产生的根源（python）在这里 ：
https://github.com/siliconflow/oneflow/blob/main/python/oneflow/nn/graph/graph.py#L1861

新的问题，用：
...
pred_original_sample = sample - sigma_hat * model_output
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:6 and cuda:0!

继续定位到，上重新加载时， https://github.com/huggingface/diffusers/blob/main/src/diffusers/pipelines/stable_diffusion/pipeline_stable_diffusion.py#L971 产生的张量会出现在 cuda:0 上（而不是指定设备上），因此在后续设备上出错。
这个 cuda:0 的 tensor 产生的根源（python）在这里 ： https://github.com/siliconflow/oneflow/blob/main/python/oneflow/nn/graph/graph.py#L1861

已经在 oneflow 的 pr 120 中解决

repo: siliconflow/onediff


text:
Google Page Speed Insights Suggestions

Hello,
thank you for your awesome work.
These are suggestions from Google Page Speed tool:
Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://s3.amazonaws.com/…silktide.com/cookieconsent.latest.min.js (expiration not specified)
http://s3.amazonaws.com/cc.silktide.com/dark-bottom.css (expiration not specified)
https://s3-eu-west-1.amazonaws.com/…ent.silktide.com/cookie-consent-logo.png (expiration not specified)

Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 4.7KiB (63% reduction).
Compressing http://s3.amazonaws.com/…silktide.com/cookieconsent.latest.min.js could save 2.5KiB (57% reduction).
Compressing http://s3.amazonaws.com/cc.silktide.com/dark-bottom.css could save 2.2KiB (71% reduction).

Do you think you could fix it?
Thank you so much

+1, was about to report myself. I would like to keep the ability to load the latest version, but...
Cache time should be minimum one day - i think that would be acceptable even for the cookie use case. Reference: https://developers.google.com/speed/docs/insights/LeverageBrowserCaching?hl=en
You could upload js and css files like that (assuming you use AWS cli):
aws s3 sync ${BUILD_FOLDER} ${BUCKET} --exclude "*" --include "css/*" --cache-control "max-age=604801" --content-encoding "gzip" --delete --profile YOUR_PROFILE --region REGION --acl public-read

Please note exclude/include directives could be easier in your case. The profile is the name of your AWS profile as stored in ~/.aws/config, looking like:
[profile webdeploy]
aws_access_key_id = XXX
aws_secret_access_key = XXX

(or similar)

+1

+1

This seems to be fixed now due to the CDN move.

Yes we should have addressed all of these issues since we moved Cookie Consent from AWS to CloudFlare.
Be sure to change your URL:
src="//s3.amazonaws.com/cc.silktide.com/cookieconsent.latest.min.js"
to
src="//cdnjs.cloudflare.com/ajax/libs/cookieconsent2/1.0.9/cookieconsent.min.js"
and that should fix it.

authors: DenisMir RichardHancock db012 grobmeier oliveremberton zdrav4o