Make templates show up properly in VS/VS Mac

We want the templates to show up properly in VS and VS for Mac instead of being command-line only.
Here's what we want:

For future reference and for anyone else interested, these are rare and valuable resources for creating dotnet new templates beyond the existing official docs:

Template samples and info: https://github.com/sayedihashimi/template-sample
Template analyzer: https://twitter.com/sayedihashimi/status/1326622265144905731

Note: You need the latest preview version of VS for the templates to install properly or else VS could hang. The template ends up getting created, but VS hangs and doesn't let you continue. So kill and restart VS and you should be able to use the new project. The latest previews have this issue fixed.

To get them to show up in the New Project dialog you must go to Options/Environment/Preview Features and enable Show all .NET Core templates in the New project dialog:


Fix HTML script tag in core/renderer to pass W3C validation

Hello,
I found an unnecessary script tag attribute in core/renderer.js that prevent a nuxt project to pass W3C validation.
Thank you for your really nice job, nuxt is amazing ;)

Hi @oXg3n
Thanks for the PR, are you sure that the type attribute makes the HTML invalid?

Hi @Atinux,
The HTML isn't invalid but a warning is displayed from the W3C validator (https://validator.w3.org/) as you can see below

Thanks for your quick reply

Ok it's a warning, but it's even better to remove the warning. Thanks for the PR @oXg3n

No problem, I'm happy to contribute, even if it is just a simple script tag :)


unicode symbols

node.js implementation could not be used with unicode strings:
>encrypt("й",parameters).length
18

this symbol is 2-bytes long, but is treated as one byte.

It's only by accident that this accepts strings.  I should throw if the argument isn't a Buffer.


Post Redesign - Update the Flyout/Hamburger page screenshots

This ticket relies on the enable-redesign branch being merged into main.
Once the redesign for enable is pushed into main, this ticket can be picked up. In the multi-level-hamburger-menu.php page we're showing screenshots for the flyout menu / hamburger menu. We should update the screenshots to reflect the new site design.
Page: https://www.useragentman.com/enable/multi-level-hamburger-menu.php

Done as part of redesign.


Default libstdc++ ABI to match system

What
Do not force the libstdc++ ABI away from the system defaults, but leave the option available.
Why
When the OpenAssetIO build system and CI was first set up, VFX Reference Platform CY22 was the latest.  It was still CentOS 7 based and specified that the deprecated libstdc++ ABI should be used. We decided that CY22 would be our default target.
However, the closest we could get on GitHub CI was Ubuntu 20.04, which matches the CY22 GCC version (9), but defaults to the non-deprecated libstdc++ ABI.  And so, we decided to configure CMake to force the deprecated ABI, unless explicitly toggled.
However, this is not a valid default for CY23+, which specify that the non-deprecated ABI should be used.
The closest we can get to "automatically" determining whether the deprecated ABI should be used or not, is to use whatever is the system default ABI.  So if someone is building on CentOS 7, it'll be the deprecated ABI, and if someone is building on Rocky 8, it'll be the non-deprecated ABI.
With our CI on Ubuntu 20.04, such a scheme will cause us to diverge more from CY22. We could explicitly use the deprecated ABI, but probably a better option would be to upgrade to Ubuntu 22.04, which matches CY23+ and will be done in a separate issue (#812).

Tried out the changes on my fork (https://github.com/feltech/OpenAssetIO/pull/19) - it's mostly fine, but TraitGen integration tests fail, because its CMake hardcodes use of the deprecated ABI. That CI job then stops before testing other projects, but Test-CMake may have the same issue.
One possibility would be to augment the OpenAssetIO CMake config file with a variable specifying whether the deprecated libstdc++ ABI is expected or not, so that consumers can read and branch on it.


BOOST libconv cross-compile  Windows to Android fails to build (Package: libiconv:arm64-android)

Using triplet:
set(VCPKG_TARGET_ARCHITECTURE arm64)
set(VCPKG_CRT_LINKAGE static)
set(VCPKG_LIBRARY_LINKAGE static)
set(VCPKG_CMAKE_SYSTEM_NAME Android)

NDK:  android-ndk-r21e
Starting package 1/31: libiconv:arm64-android
Building package libiconv[core]:arm64-android...
-- Using C:/Dev/vcpkg/downloads/libiconv-1.16.tar.gz
-- Cleaning sources at C:/Dev/vcpkg/buildtrees/libiconv/src/1.16-de9101a181.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Dev/vcpkg/downloads/libiconv-1.16.tar.gz
-- Applying patch 0002-Config-for-MSVC.patch
-- Applying patch 0003-Add-export.patch
-- Using source at C:/Dev/vcpkg/buildtrees/libiconv/src/1.16-de9101a181.clean
-- Configuring arm64-android
-- Using msys root at C:/Dev/vcpkg/downloads/tools/msys2/aa5af7b2aa7e90e8
-- Configuring arm64-android-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:105 (message):
    Command failed: --noprofile --norc --debug -c " ./../src/1.16-de9101a181.clean/configure  --enable-extra-encodings" --without-libiconv-prefix --without-libintl-prefix --disable-silent-rules --verbose --disable-shared "--enable-static --prefix=/C/Dev/vcpkg/installed/arm64-android/debug" --bindir='${prefix}'/../tools/libiconv/debug/bin --sbindir='${prefix}'/../tools/libiconv/debug/sbin --includedir='${prefix}'/../include --datarootdir='${prefix}'/share/libiconv
    Working Directory: C:/Dev/vcpkg/buildtrees/libiconv/arm64-android-dbg
    Error code: The system cannot find the file specified
    See logs for more information:

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_make.cmake:811 (vcpkg_execute_required_process)
  ports/libiconv/portfile.cmake:28 (vcpkg_configure_make)
  scripts/ports.cmake:139 (include)

Error: Building package libiconv:arm64-android failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: libiconv:arm64-android
  Vcpkg version: 2021-05-05-e8977e69d9a3fb462d9ad42013d83a7682706659

This issue hasn’t been updated in 3 month, if it is still an issue, please reopen this issue.


Merge pull request #15 from anonymouse-cmd/patch-1

add three features in docs
just to update your version or patch-1 if you ever decide to contribute in the future!

Sure thing!


:boom: new extra_claims for arbitrary claims

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Info for compilation on Unbreakable Linux 7

If anyone runs in similar issues

First I had to follow the hints from "Issue 2: 	Package dosent compile on
Ubuntu 10.04 LTS"

Download the rcon.8 file from the SVN-repository to the src-folder.

And I had to add "%option noyywrap" to src/rcron_conf-lexer.l
Seems there was a change in flex after version 2.5.4 - at least I found some
similar issues pointing to http://www.campin.net/syslog-ng/faq.html#lex

After that "make" ran through just with a warning. Tests showed that rcon is
running smooth atm.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 3 Sep 2014 at 2:16

Hi,
Thanks for the report.
This was fixed in commit 19cf05b344b899404d3077e89d8998c1757b8121


adding helper to debug_print()

Checklist

[ #543] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

It seems that the rust_analyzer extension is not working for me in those files inside of metadata directory. In debug_utils.rs was the only file where i found the problems related to the issue.

I was searching if that function is used in the project, and i did not find it. That was the reason that i did not change the parameters in other calls.

You forgot the dependencies. Also if you add a parameter please update all the reference (I don't think there'll be any to this specific function, but just in case).
Rust analyzer may not be working properly to you because this file is behind a feature. If you tell rust-analyzer to enable the with-debug-utils feature it should work properly.

I could not found a way to config that :/

Are you using vscode? (or codium)
If so, just add this to the config:
"rust-analyzer.cargo.allFeatures": true,

Are you using vscode? (or codium) If so, just add this to the config:
"rust-analyzer.cargo.allFeatures": true,

Thanks, now is working.

@azteca1998 Hello mate. When you have time, let me know if we are done with this.

There are some more allocas that arent done on the init_block block too, look at the following files:

poseidon.rs
ec.rs

Codecov Report
Attention: Patch coverage is 85.71429% with 5 lines in your changes are missing coverage. Please review.

Project coverage is 89.74%. Comparing base (537105f) to head (6d2667e).
Report is 3 commits behind head on main.

Files
Patch %
Lines

src/metadata/debug_utils.rs
0.00%
5 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #557      +/-   ##
==========================================
- Coverage   89.74%   89.74%   -0.01%
==========================================
  Files         108      108
  Lines       34382    34398      +16
==========================================
+ Hits        30857    30870      +13
- Misses       3525     3528       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@azteca1998 @igaray i dont know if someone can help me here, i just tried to do a git rebase main from my feature branch, and i dont know if it went good tbh.

This is something that  definetly i dont get it, im getting a bunch of errors locally.


Additional options for cluster remove and attach. Clarify behavior of…

… config set core.dcos_url.
Description
https://jira.mesosphere.com/browse/DOCS-2166
Urgency

[ ] Blocker
[ ] High
[x ] Medium

Requirements

Test all commands and procedures.
Build content locally and test for formatting/links.
Add redirects to dcos-website/redirect-files.
Change all affected versions (e.g. 1.7, 1.8, 1.9, and 1.10).
See the contribution guidelines.

Moved to https://github.com/mesosphere/dcos-docs-site/pull/360.


[MISC] add motion and nirs preprint citations

preprint for now, but we should add it.
BTW @lpollonini @rob-luke how is the NIRS paper coming along? any news?

preprint for now, but we should add it.
BTW @lpollonini @rob-luke how is the NIRS paper coming along? any news?

It was submitted to Scientific Data, but due to changes in the manuscript format/headings compared to previous BIDS papers, it was kicked back. I should be able to re-organize the same content and resubmit next week.
We do have a pre-print at https://osf.io/7nmcp/, but it does not reflect yet the changes needed. I will also upload a new version as soon as it is resubmitted to Scientific Data.

thanks for reminding me of the preprint @lpollonini! I added it to this PR.
and +1 for resubmission :-) would be great to have that paper out at some point


feat(formatting): Add memory units adaptive formatter to format bytes

Add new memory units adaptive formatter to format bytes units into kB, MB, GB, etc.
SUMMARY
Memory unit (bytes) is typically formatted into kB (kilobytes), MB (megabytes), etc.
Superset formatting options don't enable adaptive formatting with proper unit naming in case of bytes values.
There are two most commonly used multi-byte unit types (according to wikipedia), this PR implements them both.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

Create a Chart, for example Table, with at least one numeric data column.
Edit the Chart, in the "Customize" tab select one of "Memory in bytes" options for formatting of your numeric column.

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[x] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[x] Introduces new feature or API
[ ] Removes existing feature or API

@villebro , sure thing, let me give it a try :) I never wrote any Javascript before, therefore happy to get some feedback :)
CI setup is very useful here.

@villebro I added unit tests and fixed some bugs on the way :) Let me know what you think!

It seems there's a linting issue with the test:

Thanks @villebro for your help merging this :)

@villebro any idea when this will be in the release?

As far as I know it didn't make the cut opportunity for 4.1, so it'd most likely be in either a 4.2 (if that happens) or 5.0.


Update luis-csharp-tutorial-build-bot-framework-sample.md

Updating the typo in the URL, because the extracted subscription key does not match the value in the URL.

@angerico-carino : Thanks for your contribution to the Azure documentation! The author, @DeniseMak, has been notified to review your proposed change.

#sign-off


The redirect_uri URL must be absolute

i have a problem with your code
https://www.facebook.com/v2.6/dialog/oauth?client_id=appid&state=appsecret&response_type=code&sdk=php-sdk-5.2.0&redirect_uri=www.mywebsite.com%2FCodeigniter%2F%2Findex.php%2Fpage&scope=public_profile%2Cpublish_actions%2Cemail

You're missing the protocol before the uri. "http://www.mywebsite.com".
But actually I don't know why it's not there since the code for that is as follows:
return $this->helper->getLoginUrl(             base_url() . $this->config->item('facebook_login_redirect_url'),             $this->config->item('facebook_permissions')         );
which should already put the protocol.

@eotg1910 As mentioned by @tonirilix the URL should be set correctly by the base_url() helper in the library. However, the base_url() set what value you have set in your configuration file. What value do you have set for $config['base_url'] in your config?
Also, what version of the library are you using. Latest v3.0.0 or the older v2?


Add cloud helpers

adds several helpers to lib/components/sdk.js intended to help with tests involving balena cloud

push to application
wait until services running
get supervisor version
execute command in container

@vipulgupta2048 this good?

@balena-ci rebase

@balena-ci I self-certify!


Update reference-deprecation.md

@samuel100 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[WIP] Move to generics

Go 1.8 has a great  feature – generics, I found it cool and fun to replace all code generated with generics.

Codecov Report

Merging #4 (33db329) into master (470f432) will increase coverage by 34.86%.
The diff coverage is 37.93%.

@@             Coverage Diff             @@
##           master       #4       +/-   ##
===========================================
+ Coverage    3.06%   37.93%   +34.86%
===========================================
  Files           3        1        -2
  Lines         326       29      -297
===========================================
+ Hits           10       11        +1
+ Misses        316       18      -298

Impacted Files
Coverage Δ

filter.go
37.93% <37.93%> (+37.93%)
:arrow_up:

Continue to review full report at Codecov.

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


EnderIO Item Cable + controlled miner = CRASH

So the EnderIO item cable crash game and server  and  my map can't load anymore ;/

there is an option in forge to delete ticking tile entities.
Go to config/forge.cfg and there is a line there
B:removeErroringTileEntities=false

change that to true.
If I am correct, that will stop these errors from happening by deleting whatever block is causing the crash.
Do you have a log of the crash so i can look into it? Either what shows up in your MC launcher, or in logs/latest.log

Here is the Crash report of the server
crash-2016-12-24_18.06.15-server.txt
Thank you

Thanks that log is exactly what i needed

Fixed in build 1.9.6 https://minecraft.curseforge.com/projects/cyclic/files/2360370
Thanks for reporting it


Error in Breaking Changes

The section Environment Information, describes that IsInvAppId has changed to IsInvoicing, but there is not a function Called IsInvoicing in the codeunit.

Error: 'Codeunit "Identity Management"' does not contain a definition for 'IsInvAppId'
Solution: Function has been moved to codeunit 457 "Environment Information", function IsInvoicing.

Thank you for reporting. Fixed now: https://github.com/microsoft/ALAppExtensions/blob/master/BREAKINGCHANGES.md#base-application


Impact Analysis - Iffah

The Impact Analysis will be under "impact analysis folder"
In case Dr can't find it. Here the Pull Request Description:
Assignment2_Iffah.docx

Ok, which part of the module/component that you use to produce the graph?


Net app API

There has been discussion and complaints that the current net_context API that applications can use is too low level and requires lot of effort from application developer to create a bug free application. Many networking operations that various applications do, are very similar and can be provided by a library. In order to address these issues I created a higher level API that applications can use.
The API consists of two parts:

Application initialization support.

The net_app_init() makes sure that we have IP address, routes etc. configured and the IP stack is ready to serve before continuing. User can supply a timeout to the function call, and also give a hint what kind of support it needs from the IP stack. It is possible to use only the net_app_init() without the connectivity support if needed.

Connectivity support

Developer can create a simple TCP/UDP server or client application with only few function calls.

Example for the TCP server:
net_app_init_server(&tcp, SOCK_STREAM, IPPROTO_TCP, NULL,
		    MY_PORT, NULL, NULL, NULL);
net_app_set_cb(&tcp, NULL, tcp_received, NULL, NULL);
net_app_wait_connection(&tcp);

Example for UDP server:
net_app_init_server(&udp, SOCK_DGRAM, IPPROTO_UDP, NULL,
		    MY_PORT, NULL, NULL, NULL);
net_app_set_cb(&udp, NULL, udp_received, pkt_sent, NULL);
net_app_wait_connection(&udp);

Example TCP client:
net_app_init_client(ctx, SOCK_STREAM, IPPROTO_TCP, NULL,
		    NULL, peer, PEER_PORT, WAIT_TIME,
		    NULL, NULL, user_data);
net_app_set_cb(ctx, tcp_connected, tcp_received, NULL, NULL);
net_app_connect(ctx, CONNECT_TIME);

Example UDP client:
net_app_init_client(ctx, SOCK_DGRAM, IPPROTO_UDP, NULL,
		    NULL, peer, PEER_PORT, WAIT_TIME,
		    NULL, NULL, user_data);
net_app_set_cb(ctx, udp_connected, udp_received, NULL, NULL);
net_app_connect(ctx, CONNECT_TIME);

So the developer needs to setup the proper callbacks that will be called in various stages of the connection flow.
I created a TLS support for TCP server in this initial pull request. The TLS  support is transparent to the application, all the encryption and decryption happens inside the net_app API. Only thing the application needs to do is to setup the TLS, and prepare the certificates for mbedtls library. With this transparent TLS support, it is possible to create for example MQTT over TLS support quite easily.
In order to try the TLS support, the net-tools project have this
https://github.com/zephyrproject-rtos/net-tools/pull/8
PR that provides stunnel configuration so that echo-client can be run in Linux side and it can communicate with zephyr echo-server sample over TLS.
This net_app API will replace the internal net_sample_app API that was used by some of the network sample applications found under samples/net  directory.
The current patchset contains these patches:

net_app core functions
conversion of echo-client and echo-server samples to use this new API
base TLS support
setting up the echo-server to use the TLS if configured so

Future plans:

create TLS TCP client support
create DTLS UDP client and server support
convert existing network samples to use this API

If we're doing this to simplify things:

Any reason to ask the user to specify both DGRAM/UDP or STREAM/TCP? Can't DGRAM/STREAM be inferred from the protocol?
I get really uneasy with functions that accepts multiple parameters of the same type; it's too easy to mix them up and difficult to know what they are from the call site.  I'd prefer more functions to set each parameter rather than a single function with a lot of parameters.

Adding this  net_app_init() is a good idea to simplify the examples.
I wonder if we could go even one step further and have this initialization happen during boot-up automatically, say, during pre-application initialization?
Something like:
SYS_INIT(net_app_init(), _SYS_INIT_LEVEL_APPLICATION, ...);

perhaps its parameters can be added as Kconfig options?
That way, it will hide this common initialization from all the examples, and the function call could be completely removed from all the net (and new socket) samples.
Looking at the new BSD socket_echo.c example (https://github.com/zephyrproject-rtos/zephyr/pull/498), the only non-standard bit of code (other than the headers) keeping it from being a portable BSD socket app is that bit of Zephyr-specific initialization code (init_net()).
Hiding the initialization could be another small step to help future porting of third party BSD socket apps and protocols to Zephyr.

@GAnthony : Right, it's about the same idea I shared on mailing list in response to the RFC behind this patch: https://lists.zephyrproject.org/pipermail/zephyr-devel/2017-June/007799.html

@pfalcon: Ah, yes, thanks for pointing that out.  I must have overlooked that part of the email thread.  In any case, I agree it would help simplify the apps to somehow hide that initialization.

New version uploaded.
Changes:

added helpers for creating TCP / UDP listeners as suggested by @lpereira and @tbursztyka
calling net_app_init() automatically as suggested by @GAnthony and @pfalcon I made the auto init optional (it is on by default) so that application developer can call net_app_init() itself if really necessary
refactored the code
supports now both client and server roles for TLS

Sent a new version. Changes:

net_app_wait_connection() renamed to net_app_listen()
changed the net_app_init() failure to print using printk() (using k_panic() seemed like overkill atm)
added mbedtls resource cleaning if TLS init fails

Getting past shippable seems to be tricky for this PR. I sent a new version:

increased RAM size for https_client running in qemu
changed back to NET_ERR() for net_app_init() as using printk() caused build errors, we can fix this later if really needed


Fatal error: Class 'Google\Auth\Cache\MemoryCacheItemPool' not found

I am starting to use GCP today and after following the instructions defined here:
composer require google/cloud-storage
then:
putenv("GOOGLE_APPLICATION_CREDENTIALS=/path/to/creds.json");
require __DIR__.'/vendor/autoload.php';
use Google\Cloud\Storage\StorageClient;

$storage = new StorageClient([
  'projectId'=>'my-project-id'
]);
var_dump($storage->buckets());

When running this i get the following error:

Fatal error: Class 'Google\Auth\Cache\MemoryCacheItemPool' not found in /place/to/vendor/google/cloud-core/RequestWrapperTrait.php on line 94

I have no idea how to solve the issue, as i am just getting started with GCP. No idea whether this is a problem with the platform or my code.
File structure appears as follows for the Google Auth:

vendor
google

auth

src
tests

the /Cache/MemoryCacheItemPool exists inside both the tests and src folder, but the above is referencing it minus the src or tests folder.
I have also ran:
composer update
and uninstalled and reinstalled the package to no effect

Thanks for the report @Devleaf-IT, a few quick questions to help get you up and running :)

What are the contents of the composer.json file in the root of your project?
What environment are you running your code under?

Hi @dwsupplee , Thanks for getting back to me.
Firstly my composer.json, quite a simple one haha!
{
    "require": {
        "google/cloud-storage": "^1.3"
    }
}

I have also tried requiring google/auth aswell on a different occasion but with the same result.
My code is running in a development environment at the moment via MAMP and CodeKit on MacOS 10.13.3. PHP Version: 5.6.32, MySQL: 5.6.38 and via an apache web server.
In the end the production version will be running on a cPanel linux machine.
A big thank you in advance for any help!

Thank you :).
Running the same snippet you provided brought up no issues on my end (on OSX running PHP 5.6 as well). I know it may not be too helpful, as this seems like a barebones project you set up - but would it be possible to upload your project folder (sans credentials) for me to take a look at? Nothing jumps out as a clear problem at the moment.

Right dwsupplee, seems like a problem on my end, only just thought of creating a new testing environment for just the google library. Seems to work in this so must be an issue with my existing project. I'll paste the code for init.php below (minus all sensitive bits) and will also demonstrate the file structure to see if there is an issue with where everything is.
Init.php

<?php

  /* START SESSION */
  session_start();

  /* DEFINE MAIN GLOBAL CONFIG */
  $GLOBALS['config'] = array(
    'url'=>'http://my.domain.co.uk',
    'debug'=>true,
    'config'=>(isset($config)) ? $config : null,
    'GCP-project_id'=>"google-project-id",
  );

  putenv("GOOGLE_APPLICATION_CREDENTIALS=".__DIR__."/json/<SENSITIVECREDS>.json");

  /* ENABLE DEBUGGING FOR DEVELOPER TESTING */
  if ($GLOBALS['config']['debug'] === true) {
    ini_set('display_errors', 1);
    ini_set('display_startup_errors', 1);
    error_reporting(E_ALL);
  }

  require __DIR__.'/../vendor/autoload.php';

  /* AUTOLOAD CLASSES WHEN REQUIRED */
  spl_autoload_register(function($class) {
    if (file_exists(__DIR__.'/classes/'.strtolower($class).'.php')) {
      require_once 'classes/'.$class.'.php';
    }
  });

// TESTING //

use Google\Cloud\Storage\StorageClient;
$projectId = 'plant-fit-app-195915';

$storage = new StorageClient([
  'projectId'=>$projectId
]);

var_dump($storage->buckets());

?>

File structure is as follows:

css
imgs
js
ss

classes
creds is also in this folder somewhere [sensitive]
init.php

vendor

google

auth
cloud-core
cloud-storage

index.php
all-other-dashboard-documents.php

Looks like CodeKit may be the issue, generated a non-compiled version of the website and all is working properly. Codekit must be removing something when it builds. Sorry for wasting your time @dwsupplee. Thanks very much for your help!

Not a waste of time at all @Devleaf-IT, glad to see things are working for you now!

Fatal error: Class 'Google\Cloud\Storage\StorageClient' not found in C:\Bitnami\wampstack-5.5.27-0\apache2\htdocs\newsbeen\test.php on line 12


Segfault on nvml.Init

nvml.Init segfaults. These are the steps to reproduce and the setup used for the test:
[exporter]$ cat main.go
package main

import (
	"github.com/NVIDIA/go-nvml/pkg/nvml"
)

func main() {
	nvml.Init()
}

[exporter]$ go build main.go

[exporter]$ ./main
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x0]

runtime stack:
runtime.throw(0x4daeb1, 0x2a)
	/path/to/Go/1.15.3/src/runtime/panic.go:1116 +0x72
runtime.sigpanic()
	/path/to/Go/1.15.3/src/runtime/signal_unix.go:704 +0x4ac

goroutine 1 [syscall]:
runtime.cgocall(0x4ae900, 0xc000144ed8, 0xc0001a8020)
	/path/to/Go/1.15.3/src/runtime/cgocall.go:133 +0x5b fp=0xc000144ea8 sp=0xc000144e70 pc=0x41049b
github.com/NVIDIA/go-nvml/pkg/nvml._Cfunc_nvmlInit_v2(0x0)
	_cgo_gotypes.go:3398 +0x49 fp=0xc000144ed8 sp=0xc000144ea8 pc=0x4a9fc9
github.com/NVIDIA/go-nvml/pkg/nvml.nvmlInit_v2(0xc0001a8020)
	/my/home/go/src/github.com/NVIDIA/go-nvml/pkg/nvml/nvml.go:32 +0x25 fp=0xc000144ef0 sp=0xc000144ed8 pc=0x4aa805
github.com/NVIDIA/go-nvml/pkg/nvml.Init(0xc00018e058)
	/my/home/go/src/github.com/NVIDIA/go-nvml/pkg/nvml/init.go:47 +0xb1 fp=0xc000144f70 sp=0xc000144ef0 pc=0x4aa091
main.main()
	/my/home/tmp/exporter/main.go:8 +0x25 fp=0xc000144f88 sp=0xc000144f70 pc=0x4abf25
runtime.main()
	/path/to/Go/1.15.3/src/runtime/proc.go:204 +0x209 fp=0xc000144fe0 sp=0xc000144f88 pc=0x442369
runtime.goexit()
	/path/to/Go/1.15.3/src/runtime/asm_amd64.s:1374 +0x1 fp=0xc000144fe8 sp=0xc000144fe0 pc=0x470c61

[exporter]$ go version
go version go1.15.3 linux/amd64

[exporter]$ readlink -f /usr/lib64/libnvidia-ml.so
/usr/lib64/libnvidia-ml.so.470.82.01

[exporter]$ uname -r
4.18.0-348.2.1.el8_5.x86_64

[exporter]$ cat /etc/redhat-release
Rocky Linux release 8.5 (Green Obsidian)

[exporter]$ nvidia-smi
Fri Jan 28 19:34:18 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 470.82.01    Driver Version: 470.82.01    CUDA Version: 11.4     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA A100-SXM...  On   | 00000000:03:00.0 Off |                    0 |
| N/A   46C    P0    66W / 400W |      0MiB / 40536MiB |      0%      Default |
|                               |                      |             Disabled |
+-------------------------------+----------------------+----------------------+
|   1  NVIDIA A100-SXM...  On   | 00000000:44:00.0 Off |                    0 |
| N/A   45C    P0    58W / 400W |      0MiB / 40536MiB |      0%      Default |
|                               |                      |             Disabled |
+-------------------------------+----------------------+----------------------+
|   2  NVIDIA A100-SXM...  On   | 00000000:84:00.0 Off |                    0 |
| N/A   44C    P0    56W / 400W |      0MiB / 40536MiB |      0%      Default |
|                               |                      |             Disabled |
+-------------------------------+----------------------+----------------------+
|   3  NVIDIA A100-SXM...  On   | 00000000:C4:00.0 Off |                    0 |
| N/A   44C    P0    64W / 400W |      0MiB / 40536MiB |      0%      Default |
|                               |                      |             Disabled |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|  No running processes found                                                 |
+-----------------------------------------------------------------------------+

It looks like it's segfaulting on the actual underyling call to nvmlInit() in the C shared library.
What happens if you compile / run this simple C program:
$ cat main.c
#include <stdio.h>

typedef int nvmlReturn_t;

nvmlReturn_t nvmlInit_v2(void);
const char* nvmlErrorString(nvmlReturn_t result);

int main(int argc, char **argv)
{
	nvmlReturn_t err = nvmlInit_v2();
	printf("Return: %s\n", nvmlErrorString(err));
}

$ gcc -o main main.c -lnvidia-ml
$ ./main
Return: Success

This works without issues and seems to pick up the same library as the dynamic linker loads in the go version:
$ cat main.c
#include <stdio.h>

typedef int nvmlReturn_t;

nvmlReturn_t nvmlInit_v2(void);
const char* nvmlErrorString(nvmlReturn_t result);

int main(int argc, char **argv)
{
	nvmlReturn_t err = nvmlInit_v2();
	printf("Return: %s\n", nvmlErrorString(err));
}

$ gcc -o main main.c -lnvidia-ml
$ ./main
Return: Success

$ ldd main | grep nvidia
	libnvidia-ml.so.1 => /usr/lib64/libnvidia-ml.so.1 (0x00007f8e902a1000)

$ LD_DEBUG=all ./main-go |& grep -E 'object=.*libnvidia-ml' | uniq
     18418:	object=/usr/lib64/libnvidia-ml.so.1 [0]

That is strange indeed.
When I do the following things work as expcted on my machine:
$ go version
go version go1.15.3 linux/amd64

$ mkdir test
$ cd test

$ cat > main.go << EOF
package main

import (
    "github.com/NVIDIA/go-nvml/pkg/nvml"
)

func main() {
    nvml.Init()
}
EOF

$ go mod init test
go: creating new go.mod: module test

$ go mod vendor
go: finding module for package github.com/NVIDIA/go-nvml/pkg/nvml
go: downloading github.com/NVIDIA/go-nvml v0.11.1-0
go: found github.com/NVIDIA/go-nvml/pkg/nvml in github.com/NVIDIA/go-nvml v0.11.1-0

$ go build main.go
$ ./main

The only difference seems to be my driver version (460.91.03) and my OS (ubuntu 20.04).

Following the mod creation you describe, I get the same version v0.11.1-0.
My intended use case is extending nvidia_gpu_prometheus_exporter  by some metrics we need but which are currently not part of its bindings, e.g. nvmlDeviceGetClockInfo.
Surprisingly Initialize seems to call nvmlInit_v2 without problems on my setup (as did the C example you proposed above).

Yeah, I'm not sure what could be causing this issue, even the following seems to work for me:
package main

import (
    "github.com/mindprince/gonvml"
    "github.com/NVIDIA/go-nvml/pkg/nvml"
)

func main() {
    nvml.Init()
    gonvml.Initialize()
}

I thought maybe there was some weird conflicts that might occur if you had both nvml implementations vendored in.
That said, if your goal is to extend this prommetheus exporter to include more metrics, let me point you at an alternative prometheus exporter, which is the "official" prometheus exporter developed by NVIDIA. It's based on the DCGM framework (rather than NVML) to gather / publish more comprehensive metrics that what you can get out of NVML alone.
https://docs.nvidia.com/datacenter/cloud-native/gpu-telemetry/dcgm-exporter.html
It may have what you are looking for already.

Thanks a lot for this pointer. I was not aware of this exporter and on first sight it looks like it might indeed be what I am looking for. I really appreciated the simplicity of the other exporter (just a go get away), but I tried this one and got a segfault, too. But this might be better suited for an issue in the according repo, right?

I'm experiencing this issue too and did a bit of digging to figure out what is going wrong.
Firstly, I found that the SIGSEGV is due to the cgo wrapper function calling a null function pointer:
objdump --disassemble=_cgo_c9378bcb7609_Cfunc_nvmlInit_v2 gpu_test_bin

0000000000ce400c <_cgo_c9378bcb7609_Cfunc_nvmlInit_v2>:
  ce400c:	55                   	push   %rbp
  ce400d:	48 89 e5             	mov    %rsp,%rbp
  ce4010:	48 83 ec 30          	sub    $0x30,%rsp
  ce4014:	48 89 7d d8          	mov    %rdi,-0x28(%rbp)
  ce4018:	48 8b 45 d8          	mov    -0x28(%rbp),%rax
  ce401c:	48 89 45 f8          	mov    %rax,-0x8(%rbp)
  ce4020:	e8 9b fd 78 ff       	callq  473dc0 <_cgo_topofstack>
  ce4025:	48 89 45 f0          	mov    %rax,-0x10(%rbp)
  ce4029:	e8 d2 bf 31 ff       	callq  0 <runtime.tlsg>
  ce402e:	89 45 ec             	mov    %eax,-0x14(%rbp)
  ce4031:	e8 8a fd 78 ff       	callq  473dc0 <_cgo_topofstack>
  ce4036:	48 2b 45 f0          	sub    -0x10(%rbp),%rax
  ce403a:	48 01 45 f8          	add    %rax,-0x8(%rbp)
  ce403e:	48 8b 45 f8          	mov    -0x8(%rbp),%rax
  ce4042:	8b 55 ec             	mov    -0x14(%rbp),%edx
  ce4045:	89 10                	mov    %edx,(%rax)
  ce4047:	90                   	nop
  ce4048:	c9                   	leaveq
  ce4049:	c3                   	retq

Note that at address ce4029 inside _cgo_7796e00b9739_Cfunc_nvmlInit_v2 that callq 0x0 is trying to call a null function pointer. I believe this should be the address of the PLT entry for nvmlInit_v2?
To test this theory I created a simple cgo program which links against libm and calls the cos() function.
So I believe the problem here is that the nvml cgo wrappers do not jump to the PLT entries for the nvml functions from libnvidia-ml.so. The next question is what part of the cgo toolchain is failing to put the PLT entries within the cgo function wrappers?
Any ideas @klueska ?

Do you have a simple reproducer program with a set of build flags?

I will try to create a simple reproducer.

FYI: The environment I initially built in is a bit peculiar. Especially it has LD_LIBRARY_PATH set. Not cleaning this properly leads to the errors I described above. With this default environment with LD_LIBRARY_PATH set I can still reproduce the error I described above but with a clean environment I cannot reproduce it. This also allowed me to build and run the DCGM exporter as proposed above.
Thanks again for the hint and sorry for the noise.

Are you able to post a full example @kthust ? We are building this in bazel with a custom toolchain, so I might have a bit of trouble trying to reproduce this in a minimal example.

The minimum example I mentioned in the previous post is the one I initially posted
[exporter]$ cat main.go
...

Since I usually do not work with go I needed some tries along the lines of go mod init example/hello and go mod tidy to download the module again, since I seem to have removed it since the last time I tested. With that out of the way I just used the commands and minimum code example from the initial post.
We are using EasyBuild at our site and since we provide a Go module it was my easiest way to have access to a build environment (or so I thought). By default we load some standard modules, like GCCcore, zlib and binutils.
I just compared the working and the broken environment and the LD_LIBRARY_PATH does not seem to be the culprit, but PATH. If it contains <base_path>/GCCcore/11.2.0/bin before /bin/ when building go build main.go, then the resulting binary segfaults (independent of the PATH when it is run).

Are you able to post the output of go build -x during the broken build and then the non-broken build so we can compare? It seems like there is an issue with one of the GCC versions which is being used.

I tested the broken and working build. Maybe the most relevant part might be -extld=gcc, which will use a different gcc with the different PATH.
The two gcc versions are
# broken
$ gcc --version | grep gcc
gcc (GCC) 11.2.0

# working
$ gcc --version | grep gcc
gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-15)

The newer version is provided via EasyBuild, the old version is from the normal system package repository.

diff
$ diff --color=always -u build_*
--- build_broken	2023-02-23 14:26:46.285456594 +0100
+++ build_working	2023-02-23 14:25:33.140953735 +0100
@@ -1,11 +1,11 @@
-WORK=/tmp/go-build3884987067
+WORK=/tmp/go-build3607589321
 mkdir -p $WORK/b001/
 cat >$WORK/b001/importcfg.link << 'EOF' # internal
-packagefile command-line-arguments=/p/home/jusers/thust1/jureca/.cache/go-build/44/441f9478f3b42d4e446f980c088b6bcd1e949b81007c85bf47bacd3fbe9705e8-d
-packagefile github.com/NVIDIA/go-nvml/pkg/nvml=/p/home/jusers/thust1/jureca/.cache/go-build/01/01ecdc3ad9a069fdd53ca056e24338a51190990fdbdcf3aafd35a581ae3a1272-d
+packagefile command-line-arguments=/p/home/jusers/thust1/jureca/.cache/go-build/a2/a2c243b73e2a11fa94ec3aecae169627c0e0503b098d0cf1de0408ed112d49d6-d
+packagefile github.com/NVIDIA/go-nvml/pkg/nvml=/p/home/jusers/thust1/jureca/.cache/go-build/7c/7cffde010d00b40264bffe70c97198685cc5a37fade349da636ca142de0a9835-d
 packagefile runtime=/p/software/jurecadc/stages/2022/software/Go/1.17.3/pkg/linux_amd64/runtime.a
 packagefile fmt=/p/software/jurecadc/stages/2022/software/Go/1.17.3/pkg/linux_amd64/fmt.a
-packagefile github.com/NVIDIA/go-nvml/pkg/dl=/p/home/jusers/thust1/jureca/.cache/go-build/bb/bb90be00d22d687f6989109015df4b87c93533e318955a4b2e347b6e6835c72c-d
+packagefile github.com/NVIDIA/go-nvml/pkg/dl=/p/home/jusers/thust1/jureca/.cache/go-build/7f/7f1d6309dc90f73ab454fae523192bb309672b7be23beca314f4b170dbd35329-d
 packagefile reflect=/p/software/jurecadc/stages/2022/software/Go/1.17.3/pkg/linux_amd64/reflect.a
 packagefile runtime/cgo=/p/software/jurecadc/stages/2022/software/Go/1.17.3/pkg/linux_amd64/runtime/cgo.a
 packagefile syscall=/p/software/jurecadc/stages/2022/software/Go/1.17.3/pkg/linux_amd64/syscall.a
@@ -43,7 +43,7 @@
 EOF
 mkdir -p $WORK/b001/exe/
 cd .
-/p/software/jurecadc/stages/2022/software/Go/1.17.3/pkg/tool/linux_amd64/link -o $WORK/b001/exe/a.out -importcfg $WORK/b001/importcfg.link -buildmode=exe -buildid=ZMjV-a_WMkEgLv_nPpG8/ExL-lxdnvv7Klww4ZTtN/Hz1ci8PgaVLHtwTjIQfg/ZMjV-a_WMkEgLv_nPpG8 -extld=gcc /p/home/jusers/thust1/jureca/.cache/go-build/44/441f9478f3b42d4e446f980c088b6bcd1e949b81007c85bf47bacd3fbe9705e8-d
+/p/software/jurecadc/stages/2022/software/Go/1.17.3/pkg/tool/linux_amd64/link -o $WORK/b001/exe/a.out -importcfg $WORK/b001/importcfg.link -buildmode=exe -buildid=twZdNdI2gQ86fClF_h-q/LoCydkskulkMYHoLu5ih/Hz1ci8PgaVLHtwTjIQfg/twZdNdI2gQ86fClF_h-q -extld=gcc /p/home/jusers/thust1/jureca/.cache/go-build/a2/a2c243b73e2a11fa94ec3aecae169627c0e0503b098d0cf1de0408ed112d49d6-d
 /p/software/jurecadc/stages/2022/software/Go/1.17.3/pkg/tool/linux_amd64/buildid -w $WORK/b001/exe/a.out # internal
 cp $WORK/b001/exe/a.out main
 rm -r $WORK/b001/

@kthust I can confirm that we are on GCC 11.2.0 as well so this appears to be an issue with the GCC version? It is unclear if this is an actual bug with GCC or if there was a behaviour change?

@klueska any chance you can try the build on GCC 11.2.0 and see if you can replicate the issue?

I have made a breakthrough. It appears that this issue is triggered when using the gnu gold linker.
Here is a simple reproducer:
package main

import "github.com/NVIDIA/go-nvml/pkg/nvml"

func main() {
	nvml.Init()
}

go build -a --ldflags '-extldflags "-fuse-ld=gold"'

Running the resulting binary will segfault. I have verified this across multiple gcc and go versions. The question now is this a bug in gnu gold, or is go-nvml relying on undocumented behaviour of gnu ld to function?
@klueska

Does it also segfault with the gold linker on a C-based NVML program, e.g. the one I specified here: https://github.com/NVIDIA/go-nvml/issues/36#issuecomment-1024535333

Also, for reference, these are the LDFLAGS and CFLAGS that we set when you build against go-nvml:
https://github.com/NVIDIA/go-nvml/blob/main/gen/nvml/nvml.yml#L35...L36
Can you try adding these flags to your go build command. Unfortunately, this is not something we can set in the library itself, but users have reported needing it to avoid unresolved symbol errors (even without the gold linker). These users weren't segfaulting, but maybe with the gold linker there is a different symptom to the same underlying issue:
go build -ldflags="-extldflags=-Wl,-z,lazy" <files>.go

passing -z lazy to ld.gold didn't fix the issue.
 go build -a --ldflags '-extldflags "-fuse-ld=gold -Wl,-z,lazy"'

Lazy binding is the default option so I wouldn't expect passing the option on the command line to make a difference
ld.gold --help | grep lazy
 -z lazy                     Mark object for lazy runtime binding (default)

Just to be clear, this issue is reproducible on a stock install of ubuntu 20/22 using this example: https://github.com/NVIDIA/go-nvml/issues/36#issuecomment-1470962928

I tested ld.gold using the latest binutils (2.40) and still got the same result where the binary segfaults.
I'm now trying to see if I can get a minimal C reproducer using ld.gold. For reference I was able to dump the temporary cgo build outputs before the compiler is invoked:
CGO_NO_SANITIZE_THREAD
void
_cgo_c813f6172e91_Cfunc_nvmlInit_v2(void *v)
{
        struct {
                nvmlReturn_t r;
                char __pad4[4];
        } __attribute__((__packed__, __gcc_struct__)) *_cgo_a = v;
        char *_cgo_stktop = _cgo_topofstack();
        __typeof__(_cgo_a->r) _cgo_r;
        _cgo_tsan_acquire();
        _cgo_r = nvmlInit_v2();
        _cgo_tsan_release();
        _cgo_a = (void*)((char*)_cgo_a + (_cgo_topofstack() - _cgo_stktop));
        _cgo_a->r = _cgo_r;
        _cgo_msan_write(&_cgo_a->r, sizeof(_cgo_a->r));
}

Which compiles to this object code before linking:
0000000000003e30 <_cgo_c813f6172e91_Cfunc_nvmlInit_v2>:
    3e30:	f3 0f 1e fa          	endbr64
    3e34:	41 54                	push   %r12
    3e36:	55                   	push   %rbp
    3e37:	53                   	push   %rbx
    3e38:	48 89 fb             	mov    %rdi,%rbx
    3e3b:	e8 00 00 00 00       	call   3e40 <_cgo_c813f6172e91_Cfunc_nvmlInit_v2+0x10>
    3e40:	49 89 c4             	mov    %rax,%r12
    3e43:	e8 00 00 00 00       	call   3e48 <_cgo_c813f6172e91_Cfunc_nvmlInit_v2+0x18>
    3e48:	89 c5                	mov    %eax,%ebp
    3e4a:	e8 00 00 00 00       	call   3e4f <_cgo_c813f6172e91_Cfunc_nvmlInit_v2+0x1f>
    3e4f:	4c 29 e0             	sub    %r12,%rax
    3e52:	89 2c 03             	mov    %ebp,(%rbx,%rax,1)
    3e55:	5b                   	pop    %rbx
    3e56:	5d                   	pop    %rbp
    3e57:	41 5c                	pop    %r12
    3e59:	c3                   	ret

Another breakthrough. I have found that gold and ld differ on how they handle unresolved symbols. When ld finds an unresolved symbol it will create a PLT entry for that symbol, whereas when gold finds an unresolved symbol it will simply set the jump address to 0x0 (as seen in earlier disassembly) which break the way go-nvml does lazy binding with dlopen.
Luckly there is a solution with gold: if you pass --weak-unresolved-symbols to gold when linking with go-nvml gold will create a plt entry for unresolved symbols and those plt entries will be filled in by dlopen and everything works. --weak-unresolved-symbols is only an option in gold and not ld so go-nvml needs to figure out if we are linking with gold or ld and pass --unresolved-symbols=ignore-in-object-files if we are using ld and --weak-unresolved-symbols if we are using gold.
Using the go reproducer we can verify that these command line options successfully create a binary with gold which doesn't segfault:
 go build -a --ldflags '-extldflags "-fuse-ld=gold -Wl,--weak-unresolved-symbols"'

Thanks for getting to the bottom of this!
However I don’t see how this can be addressed at the go-nvml layer if this flag is specific to the gold linker (so we can’t just plop it into our static setting for LDFAGS).
It would need to be applied by whoever is actually building an application that imports go-nvml and choosing to use the gold linker.

It might be possible to use go build constraints to change the LD flags based upon the linker be used?
From the cgo docs: https://pkg.go.dev/cmd/cgo
CFLAGS, CPPFLAGS, CXXFLAGS, FFLAGS and LDFLAGS may be defined with pseudo #cgo directives within these comments to tweak the behavior of the C, C++ or Fortran compiler. Values defined in multiple directives are concatenated together. The directive can include a list of build constraints limiting its effect to systems satisfying one of the constraints (see https://golang.org/pkg/go/build/#hdr-Build_Constraints for details about the constraint syntax)

Here is where we could use build constraints to change ld flags: https://github.com/NVIDIA/go-nvml/blob/main/pkg/nvml/nvml.go#L21

We already do that for the unresolved symbols flag (indirectly through our use of c-for-go under the hood, but it essentially does exactly that). I can’t imagine we could dynamically detect which linker is being used and apply different build constraints based on that though. I will take a look through the docs to see, but I’m not optimistic.
Thanks again for getting to the bottom of this. At the very least we know what flags to tell people to add themselves if they encounter this in the future.

If I get the chance I will also follow up with the binutils maintainers to see if this is expected behaviour of gold.
It would be really nice if we can handle this in go-nvml. go-nvml relies on specific behaviour of ld which breaks with gold, and users are not going to know that.

We have a dependency on go-nvml and we started hitting this segfault when we upgraded our build environment from Go 1.20 to 1.21. We don't use any linker flags in our build, just plain go build.
Is the guidance from https://github.com/NVIDIA/go-nvml/issues/36#issuecomment-1472853933 still currently the best known workaround? Any ideas on why the Go version upgrade to 1.21 would trigger this?

Can confirm that with go 1.21.1 the segfault is always triggered.
This was not the case with go 1.20.8.
On a side note, I found this bug while trying to manually compile nvidia-container-toolkit. If compiled with go 1.20.8, everything is ok, if compiled with 1.21 the following message appears when trying to run nvidia-ctk or nvidia-container-runtime:
nvidia-ctk: error while loading shared libraries: unexpected PLT reloc type 0x00

This is consistent with the earlier findings of elias-dbx about gold setting PLT entry of 0x0. No idea why it happens only with go 1.21 though

@davidepi I note that we have https://github.com/NVIDIA/nvidia-container-toolkit/issues/101 also opened against a tool that consumes go-nvml. In which environment (distribution) are you manually compiling the nvidia-container-toolkit?

I'd like to confirm that this segfault has started happening when using Go 1.21.1.
When the symbol lookup happens through dlopen and dlsym, the symbol is found. However, when calling the symbol through the generated bindings, all symbols result in 0x0.
I'm happy to provide any additional debug information as I am actively looking into this issue and trying to resolve it.

Another piece of info that might be useful:
We're not sure why yet, but on Ubuntu 20.04 this still seems to work with Go 1.21.1. However, when we run with Go 1.21.1 on Debian 11 or Ubuntu 22.04, we get the issue I mentioned above.
Also to clarify, this is happening on any symbol. I tried going into library code and forcing it to run other random symbols, and every one I tried resulted in the invalid address 0x0 panic.

@elezar fresh installation of Gentoo, which is unsupported, but I see that braydonk confirmed that happens also on Ubuntu and Debian.
As you noted in nvidia-container-toolkit, I believe this is the same problem as https://gitlab.com/nvidia/container-toolkit/container-toolkit/-/issues/17
Checking the date of that issue, it matches with the release of go 1.21 that happened a couple of days prior. However I lack information about how that package was built so I cannot be 100% sure.
I tried the same solution on that post, by downloading already existing binaries, but it segfaults when running nvidia-ctk. With these precompiled binary the problem is not when starting them without arguments but when generating the CDI spec. I just copied the compiled binaries, so I can guess it was still calling the system-provided go.

I was able to reproduce this without go-nvml at all. I opened an issue in the Go repo.

I found the reason for the issue in go1.21.x. You can see my investigation and eventual findings in the mentioned golang/go issue. I have opened a PR that seems to resolve this issue based on my findings.

Keep the gcc = gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2)


change dense rank return type to integer

@JkSelf, I see that you change rank return type to integer to be consistent with the return type of spark's rank. I also need to modify when I adapt the dense rank.

Yes. This is just a temporary solution, we need to add this function changes in sparksql folder later.


go list incorrect

using 0.6.5 the output of go list ./... is incorrect
eg.
github.com/goadapp/goad is listed as _/Users/tommaso/src/go_development/src/github.com/goadapp/goad

This is caused by using full isolation mode. A workaround is to install bindfs and use the absolute package path:
go list github.com/goadapp/goad/...

This is also described in the README now: https://github.com/GetStream/vg#relative-packages-in-commands


EC2 service discovery: reuse EC2 client instead of recreating it every time

This also caches credentials that are obtained e.g. via IRSA on AWS EKS.
Previously, every refresh cycle would request the credentials again.

I presume that the client will take care of any require token refreshing in the background?

Yep, we are using the AWS Go SDK in a couple of internal projects with IRSA and we didn't need to do any magic, it just caches the acquired credentials and re-retrieves them before they expire. See also the implementation of the WebIdentityRoleProvider here - it tells the SDK when the tokens are going to expire.

Thanks!

Yep, we are using the AWS Go SDK in a couple of internal projects with IRSA and we didn't need to do any magic,

Grand, I suspected the AWS libraries did but not all of the cloud providers do.


chore: check if documentation is building in the continuous integration on pipeline

The streamsync site build and documentation is not verified in continuous integration. I noticed that the documentation in dev currently does not build correctly.

[x] add the command alfred docs.build
[x] run the command alfred docs.build in alfred ci

Won't this take ages? Will it even run in one of the Github Actions containers?
@raaymax will probably know better than I do though

Won't this take ages? Will it even run in one of the Github Actions containers?
@raaymax will probably know better than I do though

The step is taking 5 seconds. It's already running in this PR.

I think docs build where also added in this one https://github.com/streamsync-cloud/streamsync/pull/286 but in slightly different way it was added to npm run build.

I think docs build where also added in this one #286 but in slightly different way it was added to npm run build.

I am hesitant. Documentation has it's own scope so it's logic to have dedicated build step. In same time, having everything run when executing npm run build can make sense. You don't have to think about.

My proposition would be to have npm run build to build everything and in alfred lets use separate build steps for each package? i already updated https://github.com/streamsync-cloud/streamsync/pull/286 to reflect this.

Ok, so I close this PR


if while(true) {pdo()} catch_error#0 failed with id should not be 0

[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#0 pinpoint_start start
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 add clue key:name value:PDOStatement::execute
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]this span:({"E":0,"FT":1500,"S":1657875756709,"name":"PDOStatement::execute"})
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]agent try to connect:(Tcp:<IP_ADDRESS>:9989)
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 pinpoint_end_trace Done!
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#0 pinpoint_start start
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 add clue key:name value:PDOStatement::fetchAll
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]this span:({"E":0,"FT":1500,"S":1657875756709,"name":"PDOStatement::fetchAll"})
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]agent try to connect:(Tcp:<IP_ADDRESS>:9989)
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 pinpoint_end_trace Done!
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#0 pinpoint_start start
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 add clue key:name value:PDO::prepare
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 add clue key:stp value:2101
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 add clue key:SQL value:SELECT * FROM user WHERE  name = :ThinkBind_1_2063352037_ LIMIT 1
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 add clue key:dst value:xxxx.drds.aliyuncs.com
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]this span:({"E":0,"FT":1500,"S":1657875756710,"SQL":"SELECT * FROM user WHERE  name = :ThinkBind_1_2063352037_ LIMIT 1  ","dst":"drdsgfaf45xj3003public.drds.aliyuncs.com","name":"PDO::prepare","stp":"2101"})
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]agent try to connect:(Tcp:<IP_ADDRESS>:9989)
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 pinpoint_end_trace Done!
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#0 pinpoint_start start
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 add clue key:name value:PDOStatement::execute
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]this span:({"E":0,"FT":1500,"S":1657875756709,"name":"PDOStatement::execute"})
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]agent try to connect:(Tcp:<IP_ADDRESS>:9989)
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 pinpoint_end_trace Done!
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#0 pinpoint_start start
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 add clue key:name value:PDOStatement::fetchAll
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]this span:({"E":0,"FT":1500,"S":1657875756709,"name":"PDOStatement::fetchAll"})
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]agent try to connect:(Tcp:<IP_ADDRESS>:9989)
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 pinpoint_end_trace Done!
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#0 pinpoint_start start
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 add clue key:name value:PDO::prepare
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 add clue key:stp value:2101[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 add clue key:SQL value:SELECT * FROM user WHERE  name = :ThinkBind_1_2063352037_ LIMIT 1
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 add clue key:dst value:xxx.drds.aliyuncs.com[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]this span:({"E":0,"FT":1500,"S":1657875756710,"SQL":"SELECT * FROM user WHERE  name = :ThinkBind_1_2063352037_ LIMIT 1  ","dst":"drdsgfaf45xj3003public.drds.aliyuncs.com","name":"PDO::prepare","stp":"2101"})
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]agent try to connect:(Tcp:<IP_ADDRESS>:9989)
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 pinpoint_end_trace Done!
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#0 pinpoint_start start
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 add clue key:name value:PDOStatement::execute
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]this span:({"E":1,"FT":1500,"S":1657875756710,"name":"PDOStatement::execute"})
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]agent try to connect:(Tcp:<IP_ADDRESS>:9989)
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]#256 pinpoint_end_trace Done!
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766] catch_error#0 failed with id should not be 0
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766]apm_error_cb called
[15-Jul-2022 17:02:36 Asia/Shanghai] PHP Fatal error:  Maximum execution time of 30 seconds exceeded in /var/data/www/b2c/pinpoint_test/pinpoint-c-agent/testapps/PHP/vendor/pinpoint-apm/pinpoint-php-aop/lib/Pinpoint/Plugins/Sys/PDO/ProfilerPDOStatement.php on line 45
[15-Jul-2022 17:02:36 Asia/Shanghai] [pinpoint] [20766] [20766] catch_error#0 failed with id should not be 0
how to fix~

thinkphp
how to use asynchronous on php ? （ maybe ini config or coding?）

这里while循环，是模拟递归调用。
我用的就是咱们提供的例子，改的。


Implement multiplexer

Extracted from #684
depends on #836
depends on #838
should be merged after #834
What was wrong?
In order to facilitate speaking multiple devp2p protocols, we need mechanisms for dividing the messages up by their individual protocol streams.
How was it fixed?
This is part of #684  It brings in a single component, the p2p.multiplexer.Multiplexer.  This class is intentionally not a service.  This is because it must be used outside of the service context during the handshake process to facilitate individual protocol handshakes streaming only the messages pertinent to that protocol.
This PR only introduces the class and the relevant tests for it in order to keep the PR adequately small.
To-Do

[x] Clean up commit history

[x] Add entry to the release notes

Cute Animal Picture

@carver maybe hold on the review until the dependent PR's are merged and I can rebase this.

@carver maybe hold on the review until the dependent PR's are merged and I can rebase this.

Ok, sounds good. I was :fearful: looking at the +/-

@carver I have one more piece I'll split out tomorrow but if you want to look at p2p.multiplexer.Multiplexer and the corresponding tests in tests/p2p/test_multiplexer.py those are not going to change.

@carver https://github.com/ethereum/trinity/pull/850 and then I can rebase down to my intended review target.

Alright @carver .  This is as small as it is getting without doing something like committing the p2p.abc.MultiplexerAPI class on it's own or delaying the MultiplexerPairFactory to come after this PR, neither of which seem right to me.

Okay, great. I am on it. Sorry that I didn't get it done today. I promise, first thing tomorrow.

Test failures are unrelated.


jobberd exits with code 1

Hey. I've tried compiling jobber with go 1.4.3 and go 1.5 on both Debian (wheezy) and OS X (10.11).
In every situation both binaries compile without error, the jobber client binary seems to work (can output help etc), but running jobberd always results in the process exiting with code 1 and no output.
Sorry I can't offer more help for debugging, but there is no error message.

Thank you for letting me know. I'll look into it.
Regards,
Dylan

On Oct 4, 2015, at 8:01 AM, Ian Alexander Wood<EMAIL_ADDRESS>wrote:
Hey. I've tried compiling jobber with go 1.4.3 and go 1.5 on both Debian (wheezy) and OS X (10.11).
In every situation both binaries compile without error, the jobber client binary seems to work (can output help etc), but running jobberd always results in the process exiting with code 1 and no output.
Sorry I can't offer more help for debugging, but there is no error message.
—
Reply to this email directly or view it on GitHub.

I have the same issue. Demon exits with code 1.
I am using:

CentOS 7.1.503
go version go1.4.2 linux/amd64

Build can be reproduced with this Dockerfile:
https://github.com/blacklabelops/jobber-cron/blob/master/Dockerfile

I've made some changes to the code and the Makefile should fix this.
Please also use the changes to your Dockerfile in https://github.com/blacklabelops/jobber-cron/pull/2

Solved for me.

Solved for me.


ReadMe update

Added permissions section for lookup

I'll probably rework all the perms soon but LGTM for now


Disable camel-kafka component

See:
https://issues.apache.org/jira/browse/CAMEL-10594
I think we should disable this component until a fix is available. Else there's the potential for threads to be left endlessly running and needlessly throwing exceptions.

We can comment this out in the component aggregation module

Yep - that was the plan :smiley:


Additional Placement support

Additional Placement overrides the block placement system to allow rotational blocks in all 6 sides of a cube. with DoubleSlabs installed placing a slab onto its side via A.P. causes the game to crash.

You can temporarily "fix" this by editing the config for Additional Placements to disable its slab placement function, it's the one that directly references Double Slabs in the description/tooltip. Personally I also set Double Slabs config to disable automatic placements and make it crafting only for vertical slabs.
I'd also like to ask for support for the mod though since it would be very nice to have both.


Improve TextField description for GitLab UI

Rename Base Url parameter and provide tooltip description or url link (under question mark icon - same as Private Access Token parameter)

Hello! I'm interested in working on this issue - I'm new to OSS but have Swift and a little bit of SwiftUI experience!

Hello! Sure! Go ahead 👍 If you have any questions feel free to connect me. 🙂

Hi @rarcilla! 🙂
A few days have passed since our last contact, how is it going so far with the issue? Is anything not clear enough or do you need help with something? I am in no way pushing you, you can take as much time as you need 🙂  Just wanted to get in touch to make sure everything is ok and you have enough information 👍

@DominikMilaniak Hi there, thanks so much for checking in! :) I haven't gotten around to downloading big sur beta so I haven't yet explored the codebase, but I'm planning to do so over the next couple of days. In the meantime, it'd be great if I could get more context on the issue description, specifically, what to rename the base URL parameter to, and what "same as Private Access Token parameter" means.

Hi 👋 Name of the parameter is up to you 🙂 Base Url is fine for developers but for other people could be better more general Web Address. How would you call this kind of parameter?
There is a question mark next to Private Access Token label which leads to GitLab docs covering access token. Goal is to add something similar to Base Url parameter - it can be url leading to some trustworthy docs (GitLab, GitHub) or it can be image which shows what is meant by that parameter.
I don't think that you will face any issues (project doesn't have any special setup). But we are talking about beta developer IDE so..😁

@Jakub-Vacek Got it. Thank you for clarifying! I will get started 😄

Hi!! Sorry to bother with another question.
So my project is building without errors now after following instructions from one of the issue threads, but when I try running the Pipeliner app on My Mac, its crashes immediately. However, the widget extension looks like it's running fine! Do you have any suggestions to fix this?

Sorry to hear that 😞Do you get any runtime error?

No, I don't see any runtime errors either.. not sure what I'm missing in the installation process that's causing this. I'll refork the latest version and try again. Once I get this sorted out, I would love to update the contributing page with this extra information I gathered from running into setup problems 😅

I just tested setup master on my device and it works 🤷 You read my mind! We talked about it yesterday with my colleagues😁Great idea👍

So I noticed something interesting when I edit the scheme: when I uncheck the "Debug executable" button in the Pipeliner scheme, it seems to launch the app properly (aside from a User Defaults message in the console). Is this how your scheme is setup as well, or should it be turned on at all times?

When it is checked this is what happens:

Hi 👋 I have this option checked. It almost looks like there can be bug in Xcode debug tool. 🤯 This is interesting, i would probably turn it off for now, and try google for similar issues with debug.

Hi! You're right, it was an Xcode issue! I came across a Twitter thread and found that it was specifically affecting macOS apps running Xcode 12.2 beta. I toggled "Debug Process as root" in Pipeliner's Run Scheme, and it's working now! https://developer.apple.com/forums/thread/663823
Thanks for your help! 😄


[Bug] Unable to connect to my devcontainer EC2 instance

Is there an existing issue for this?

[X] I have searched the existing issues

What projects are you seeing the problem on?
No response
Current behavior
This morning I can not connect to the EC2 instance created from the service catalog from my MBP. Yesterday I could connect fine.

I'm connected to Sage VPN.
I tried to restart the CF stack of the EC2 instance several times.

Attempting to connect with aws ssm start-session fails:
$ aws ssm start-session   --profile cnb   --document-name AWS-StartInteractiveCommand   --parameters command="sudo su - ubuntu"   --target i-08fc48e1fa296f789

An error occurred (TargetNotConnected) when calling the StartSession operation: i-08fc48e1fa296f789 is not connected.

Alternatively, the following command usually works:
ssh devcontainers-2

<hangs>

Expected behavior
I should be able to connect to the EC2 instance using either one of the following SSH profiles (they point to the same EC2 instance):

devcontainers-ssm
devcontainers-2

Anything else?
No response
Commit ID
No response
Are you developing inside the dev container?

[X] I am using the dev container

Code of Conduct

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

I tried to connect with my personal VPN client and then tried to connect to the EC2 instance and it worked. I then shutdown my personal VPN client and it still worked. Not sure what was going on but I can now access the EC2.

I noticed that I can connect to the EC2 instance using the ssm profile without being connected to Sage VPN.
Being connect to Sage VPN is still required to connect using the non-ssm profile.


Getting NaN lm_error while training the model

Getting NaN lm_error while training the model.

Hi, can you explain more about this error? When does this error occur? Does it happen randomly or happen on certain images? We have test the train code on example images as well as other face image datasets but did not find such error.

Hi, can you explain more about this error? When does this error occur? Does it happen randomly or happen on certain images? We have test the train code on example images as well as other face image datasets but did not find such error.

It is happening randomly. I am trying to train the model on the collection
of images from the various datasets mentioned in the paper.
On Mon, 4 Jan 2021, 16:38 YuDeng<EMAIL_ADDRESS>wrote:

Hi, can you explain more about this error? When does this error occur?
Does it happen randomly or happen on certain images? We have test the train
code on example images as well as other face image datasets but did not
find such error.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/Deep3DFaceReconstruction/issues/105#issuecomment-753912900,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQTWYBARTBADDBROCTPF6F3SYGOUPANCNFSM4VQPVZ4Q
.

It is happening randomly. I am trying to train the model on the collection
of images from the various datasets mentioned in the paper.
On Mon, 4 Jan 2021, 16:38 YuDeng<EMAIL_ADDRESS>wrote:

Hi, can you explain more about this error? When does this error occur?
Does it happen randomly or happen on certain images? We have test the train
code on example images as well as other face image datasets but did not
find such error.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/Deep3DFaceReconstruction/issues/105#issuecomment-753912900,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQTWYBARTBADDBROCTPF6F3SYGOUPANCNFSM4VQPVZ4Q
.

Hi,htktwr95,can you share CoarseData with me by baiduyun? thanks.

Hi,htktwr95,can you share CoarseData with me by baiduyun? thanks.

Is it really related to dataset?
I have ~200K images in my dataset. Do I have to check these images individually?
I ran the code with 5 handpicked images only  (properly illuminated + some other constraints). I am getting this error again and again!

Is it really related to dataset?
I have ~200K images in my dataset. Do I have to check these images individually?
I ran the code with 5 handpicked images only  (properly illuminated + some other constraints). I am getting this error again and again!

Hi, this error should not be related to dataset. I will check the code to see if there exists a bug to be fixed.

Hi, this error should not be related to dataset. I will check the code to see if there exists a bug to be fixed.

No, the error is due to the expression coefficients. If you regress your
model over rest of the coefficients then that problem won't occur.
So basically it's not fixed yet.
On Wed, 31 Mar 2021, 07:29 Dean, @.***> wrote:

hello,did U fixed this bug?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/Deep3DFaceReconstruction/issues/105#issuecomment-810698613,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQTWYBHI2UQJSNFBFVOFDH3TGJ6XVANCNFSM4VQPVZ4Q
.

thank you!

I have the same problem. I ran the training code on example images.

Iter: 7958; lm_loss: 2.760531 ; photo_loss: 0.079728; id_loss: 0.088676
Iter: 7959; lm_loss: 3.171836 ; photo_loss: 0.085399; id_loss: 0.094497
Iter: 7960; lm_loss: 5.258860 ; photo_loss: 0.089806; id_loss: 0.096231
Iter: 7961; lm_loss: 5.292349 ; photo_loss: 0.085974; id_loss: 0.102064
Iter: 7962; lm_loss: 4.916460 ; photo_loss: 0.092238; id_loss: 0.116507
Iter: 7963; lm_loss: 4.080110 ; photo_loss: 0.083091; id_loss: 0.102046
Iter: 7964; lm_loss: nan ; photo_loss: 0.000000; id_loss: 0.829207
Iter: 7965; lm_loss: nan ; photo_loss: 0.000000; id_loss: 0.831248
Iter: 7966; lm_loss: nan ; photo_loss: 0.000000; id_loss: 0.817078
Iter: 7967; lm_loss: nan ; photo_loss: 0.000000; id_loss: 0.849674

The error message is:
InvalidArgumentError (see above for traceback): Nan in summary histogram for: ex_coeff
Looking forward to a solution. Thanks.

I have the same problem. I ran the training code on example images.

Iter: 7958; lm_loss: 2.760531 ; photo_loss: 0.079728; id_loss: 0.088676
Iter: 7959; lm_loss: 3.171836 ; photo_loss: 0.085399; id_loss: 0.094497
Iter: 7960; lm_loss: 5.258860 ; photo_loss: 0.089806; id_loss: 0.096231
Iter: 7961; lm_loss: 5.292349 ; photo_loss: 0.085974; id_loss: 0.102064
Iter: 7962; lm_loss: 4.916460 ; photo_loss: 0.092238; id_loss: 0.116507
Iter: 7963; lm_loss: 4.080110 ; photo_loss: 0.083091; id_loss: 0.102046
Iter: 7964; lm_loss: nan ; photo_loss: 0.000000; id_loss: 0.829207
Iter: 7965; lm_loss: nan ; photo_loss: 0.000000; id_loss: 0.831248
Iter: 7966; lm_loss: nan ; photo_loss: 0.000000; id_loss: 0.817078
Iter: 7967; lm_loss: nan ; photo_loss: 0.000000; id_loss: 0.849674

The error message is:
InvalidArgumentError (see above for traceback): Nan in summary histogram for: ex_coeff
Looking forward to a solution. Thanks.

I'll try to reproduce this error on my own environment.

Hi, I follow the exact same procedure as in readme to train on example images provided in this repo for several times, but the nan error does not occur.
Following is the details of my environment:
ubuntu 16.04
conda environment python==3.6
tensorflow version==1.12.0, installed via conda install
tf_mesh_renderer branch ba27ea1798, compiled with gcc version 7.5.0 and set -D_GLIBCXX_USE_CXX11_ABI=1 as in read me.
I run three different trainings with default training settings and train up to 15k iterations, and none of them have nan error.
Could you tell me your detailed environment setting?

The details of my environment:
Windows 10
conda environment python==3.6
tensorflow-gpu==1.13.1
The tf_mesh_renderer I used has tested in Windows, it could render a 2d image correctly.
I found that the error occurs randomly. When I trained another 10k iterations (from iter 7900), the error didn't appear.

I recommend using Linux environment and tensorflow 1.12 because we have conducted all the experiments under this setting. I'm not sure if tf_mesh_renderer works correctly under windows. Although the forward rendering may seem to be correct, there might be some bugs in the backprop that lead to nan error.

I recommend using Linux environment and tensorflow 1.12 because we have conducted all the experiments under this setting. I'm not sure if tf_mesh_renderer works correctly under windows. Although the forward rendering may seem to be correct, there might be some bugs in the backprop that lead to nan error.

Thank you for your reply.
But I don't know whether @htktwr95 use the same environment as yours.

I have the same problem.  I only change a new landmark detector to give the landmark of each image.  My environment is alse python3.6 and tensorflow 1.12.   So it may be leaded by error some landmark of data, instead of environment?


19179 Added Amalgamating Businesses unit tests

Issue #: bcgov/entity#19179
This is only a subset of unit tests, but I think we can merge them in now and I'll create another PR for the others.
Description of changes:

app version = 5.6.40
added element ids
updated LEAR business duplicate check
added foreign business duplicate check
misc cleanup
added test suite (WIP)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

/gcbrun

Temporary Url for review: https://business-create-dev--pr-626-evxarflh.web.app


Upload to a shared folder fails

When I try to upload a file in a folder shared by someone else I get the message "proxying for sync ghost items is not implemented"

Sorry for this huge delay... Not quite sure how you trying to accomplish that. Could you please give some example code? Thanks


Feature request: repeat a code action on all items in the quickfix list

Let's say I move a file MyClass.cs from folder A/B/C to folder D/E/F.
Let's say I fix its namespace from A.B.C to D.E.F.
Now all references to MyClass stop compiling because they don't have using D.E.F;
It'd be cool if I could:

move MyClass.cs to its new folder & namespace
build my solution ; compilation errors would pop into the quickfix list (missing namespace errors)
do something like :cfdo OmniSharpFixUsings

I don't really know how this would work? Perhaps see if you can script something with OmniSharp#actions#codeactions#Repeat()

The best I could find right now would be to synchronously run, for instance, OmniSharpFixUsings, with a callback that says cfnext | OmniSharpFixUsings.
Is there a way to do it asynchronously?

Why not just :cfdo OmniSharpFixUsings? I haven't tried it, doesn't it work?

It does not on my computer

Ah no, because OmniSharp#actions#usings#Fix does not save the bufnr and pass it to the handler. So any fixes are going to be applied to the wrong buffers. Essentially, this use-case has never come up and that function has never been used asynchronously like this.
To make it work, you'd want to pass the bufnr() as an argument to the response handler function s:StdioFixRH, and then in the handler you'd need to switch to the correct buffer before calling OmniSharp#buffer#Update. That might work but if there are lots of buffers being updated simultaneously this could get ... messy.

@Melandel give PR #821 a go. It does what I described in the previous comment, and makes :cfdo OmniSharpFixUsings work correctly


Update Angular.js

I see some people are discussing about why isDefined(blahblah) doesn't work (blahblah is not declared). This will make it clear.

Agree with the previous comments, this clarification is not needed


sync regex -  support to change regex in app

Is your feature request related to a problem? Please describe.

if sync regex of an app changes after it was created, behaviour of sync has to be validated.
e.g first app is full synced with regex *.buzz. After some commits regex is changes to .buzz|.contacts. in this scenario should we sync contacts data < latest server commit id

related: at_tools#192

Is your feature request related to a problem? Please describe.

if sync regex of an app changes after it was created, behaviour of sync has to be validated.
e.g first app is full synced with regex *.buzz. After some commits regex is changes to .buzz|.contacts. in this scenario should we sync contacts data < latest server commit id

on #1. Tested with atmosphere pro app.
After the app is on-boarded, at the moment, the app does not update the regex during runtime. So even if the sync-regex is updated, the behaviour of the app remains same.

Is your feature request related to a problem? Please describe.

if sync regex of an app changes after it was created, behaviour of sync has to be validated.
e.g first app is full synced with regex *.buzz. After some commits regex is changes to .buzz|.contacts. in this scenario should we sync contacts data < latest server commit id

on # 1. Tested with atmosphere pro app. After the app is on-boarded, at the moment, the app does not update the regex during runtime. So even if the sync-regex is updated, the behaviour of the app remains same.

we also have to analyse what is the impact if we make the change to allow sync to read modified regex.

Updated the sync regex in between and tested using code samples and below are the observations:
After the sync regex is updated, the keys that match the updated regex criteria with the commitId higher than the local commit Id gets sync'ed. The keys that match new regex with commitId lower than the local commitId gets ignored.
For example:
Keys in wavi app before sync regex updated
sync regex = '.wavi'
@bob:key-1.wavi@alice - server commitId - 1
@bob:key-2.wavi@alice - server commitId - 2
@bob:key-3.wavi@alice - server commitId - 3

Keys in atmos app before sync regex updated
sync regex = '.atmos'
@bob:key-4.atmos@alice - server commitId - 4
@bob:key-5.atmos@alice - server commitId - 5
@bob:key-6.atmos@alice - server commitId - 6

At this point sync regex of atmos app is updated to
Keys in atmos app after sync regex updated
sync regex = '.atmos|.wavi'
@bob:key-7.atmos@alice - server commitId - 7
@bob:key-8.atmos@alice - server commitId - 8

Keys in wavi app after sync regex updated
sync regex = '.wavi'
@bob:key-9.wavi@alice - server commitId - 9
@bob:key-10.wavi@alice - server commitId - 10

Now all the above four keys gets sync'ed to atmos app. But keys (key-1.wavi, key-2.wavi, key-3.wavi) does not sync to atmos app because the local commitId of atmos is greater than keys commitId
and the keys will not be returned in sync delta.

@kalluriramkumar we have to document what are the changes required to support change in regex and create new task for implementation

Updated the sync regex in between and tested using code samples and below are the observations:
After the sync regex is updated, the keys that match the updated regex criteria with the commitId higher than the local commit Id gets sync'ed. The keys that match new regex with commitId lower than the local commitId gets ignored.
For example:
Keys in wavi app before sync regex updated
sync regex = '.wavi'
@bob:key-1.wavi@alice - server commitId - 1
@bob:key-2.wavi@alice - server commitId - 2
@bob:key-3.wavi@alice - server commitId - 3

Keys in atmos app before sync regex updated
sync regex = '.atmos'
@bob:key-4.atmos@alice - server commitId - 4
@bob:key-5.atmos@alice - server commitId - 5
@bob:key-6.atmos@alice - server commitId - 6

At this point sync regex of atmos app is updated to
Keys in atmos app after sync regex updated
sync regex = '.atmos|.wavi'
@bob:key-7.atmos@alice - server commitId - 7
@bob:key-8.atmos@alice - server commitId - 8

Keys in wavi app after sync regex updated
sync regex = '.wavi'
@bob:key-9.wavi@alice - server commitId - 9
@bob:key-10.wavi@alice - server commitId - 10

Now all the above four keys gets sync'ed to atmos app. But keys (key-1.wavi, key-2.wavi, key-3.wavi) does not sync to atmos app because the local commitId of atmos is greater than keys commitId and the keys will not be returned in sync delta.

to be clarified in architecture call. When sync regex changes should we sync old keys(commit id < local commit id - sync from local to remote , commit id < server commit id - sync from remote to local) matching new regex.

I think this is fundamentally intractable and we should actively prevent changing sync regex after its initially been set, but add a method which allows resetting of the regex makes it clear that this will trigger a full sync

I do think there is a case to be made for being able to sync a subset of the app's overall sync space.
For example:
Assume my app uses .wavi and .contact.
I would like to refresh my contact screen from remote.
Thus I only want to sync .contacts even though my app's overall sync space is (.wavi|.contact)
The app developer could be responsible for specifying a master sync space for the app.
We could implement regex subset validation to ensure that the app never goes beyond the scope of the master sync space.
Or alternatively with could use intersections on the overall sync space and attempted sync regex:
If I attempt to sync .* it will intersect with (.wavi|.contact) and my actual sync will be (.wavi|.contact)
If I attempt to sync .wavi it will intersect with (.wavi|.contact) and my actual sync will be .wavi
These thoughts may be slightly out of scope, but I needed to make note of them somewhere.

Great points Xavier
I've been thinking some more ... what if sync allowed requesting sync for multiple regexes, and allowed to start sync from a different server commit id? Could then send all of them in a combined sync request (as json) ... then adding a "new" regex would default to start from server commit id 0, but next time each would be starting from the same latest server commit id


Add EU logo_path to finders schema

European Structural and Investment funds must comply with EU legislations and they therefore need to display the EU logo.
Quote from the legislation: "the Union emblem and the reference to the Union shall be visible, when landing on the website, inside the viewing area of a digital device, without requiring a user to scroll down the page".
ticket:
https://www.pivotaltracker.com/story/show/92225774
linked to:
alphagov/finder-frontend#189
https://github.com/alphagov/specialist-publisher/pull/474

I've just rebased this onto master and fixed conflicts, edited esi-funds.json to reflect changes in https://github.com/alphagov/govuk-content-schemas/pull/51, and changed eu_logo_path to logo_path to match what's in specialist-publisher. Also squashed all the commits into one to neaten it up a bit. Thanks to @tommyp and @dsingleton for their help.

Thank you all. I'd say, let's get this merged asap we know that https://github.com/alphagov/finder-frontend/pull/189 works fine in dev environment.


Added Devdojo

added new swag data from devdojo

@Pratap2018 good work.

@Pratap2018 make sure you follow and star the repo so that you get updates about the project when you contribute for Hacktoberfest 2020


Update HOST to new API endpoint

See http://status.darksky.net/2016/09/20/forecast-api-is-now-dark-sky-api.html

Presumably it is better to use the official client: https://github.com/darkskyapp/forecast-ruby


Add warning to butter function docstring

Reference issue

Closes 8485
What does this implement/fix?

Adds warning to butter function against use of high-order narrowband IIR filter

Hi @melissawm,
hope this fulfills the documentation update for 8485.

Hello @ilayn
Can we re-run the CI since it hasn't passed and I guess they fixed the CI now and I can't restart the CI.

Since it is a docstring change, we don't need to wait for green CI on the code parts. Thank you for this fix @musteng


Locality issue with dates

Hey, I really love this theme!
I noticed that, for some reason, if I put a date like "2015-05-01" in a field, it would get rendered as the previous month ("April 2015" in this case). I tracked down the problem to the following behavior in Node (v0.12.7):
> new Date('2015-07-01').toString()
'Tue Jun 30 2015 19:00:00 GMT-0500 (CDT)'

I fixed the issue by simply passing the date string directly to moment (as in, moment(date).format(format)), which I think provides a wrapper around new Date(string) (http://momentjs.com/docs/#/parsing/string/). The problem was also resolved when I included a timezone in my dates (e.g. "2015-05-01 CDT")
I'm not sure if other people are running into the same issue, but if you get a chance I'd appreciate if you could look into this. Thanks!

Hey @benthemonkey, thanks for taking the time to report this.
I implemented your suggestion, and it seems to be working just fine. I just released the fix to npm (among other small changes) if you want to give it a try.
I think it had to do with Node/JavaScript's handling of timezones when parsing dates. Date uses the system timezone if none is specified, which is not what we want in this specific case (we want to ignore timezones, which amounts to using UTC, as moment does). Here's some debugging code for reference:
var formatDate = function(date, format) {
    date = Handlebars.escapeExpression(date || '');
    process.env.TZ = 'America/Chicago';
    console.log(date, new Date(date), moment(date).format());
    date = moment(date).format(format);
    return new Handlebars.SafeString(date);
};


Large PDF with large images causing malloc warnings

What did you do?
When generating a PDF — particularly large ones — I get consistent warnings, and sometimes crashes that I cannot find solutions for. I have been searching through the issues in this repo for some time now, and cannot find adequate solutions elsewhere. I am getting the feeling that I'm simply using the package incorrectly and could use some help.
Here is an example of the logs I'm getting:
my_app(2358,0x16d473000) malloc: can't allocate region
:*** mach_vm_map(size=41582592, flags: 100) failed (error code=3)
my_app((2358,0x16d473000) malloc: *** set a breakpoint in malloc_error_break to debug
my_app((2358,0x16d473000) malloc: can't allocate region
:*** mach_vm_map(size=6488064, flags: 100) failed (error code=3)
my_app((2358,0x16d473000) malloc: *** set a breakpoint in malloc_error_break to debug
my_app((2358,0x16d473000) malloc: can't allocate region
:*** mach_vm_map(size=8372224, flags: 100) failed (error code=3)
/// etc...

Each page in my PDF contains an image.
It looks like the memory footprint climbs well outside of what the app expects, and that's why I get the issues. My feeling is that this originates from the compression of each image in the PDF.
When I place an exception breakpoint to catch the crash, it often catches line 214 of PDFGraphics.swift, where the compression occurs.
What did you expect to happen?
Given the note in the README...

Generate PDF files directly to handle large PDF files (Details)

...I was not expecting this particular workload to cause memory issues.
What happened instead?
It seems that this only begins to happen when I approach ~200 pages in the PDF, most of which contain an image. The PDF gen works completely fine when dealing with ~100 pages.
TPPDF Environment
TPPDF version: SPM 2.3.2
Xcode version:  12.3
Swift version: 5
Demo Code / Project
Each page in my PDF corresponds to a record. The imagery for each record in the PDF comes from a Data object, originating from the Core Data store. Each core data managed object has been retrieved (non-fault) before the PDF generation begins.
For each PDF, I loop through the records and create a 2-column page for each; left column contains textual information like expense title, date, notes, etc, while the right column is an image. Each raw image can range from 600px X 900px to upwards of 2000px X 4000px at the high end - though rare.
Naturally, I use the built in compression to bring the images down to size.
for i in 0..<records {
    let record = records[i]
    let section: PDFSection = PDFSection(columnWidths: [0.36, 0.64])
    section.columnMargin = 20

    // Header
    self.document.add(text: TITLE)

    // - - Column 1 - - //
    /// Date
    self.document.add(text: DATE)
    /// Total
    self.document.add(text: EXPENSE_TOTAL)
    /// Description
    self.document.add(text: DESC)

    // - - Column 2 - - //
    /// Record snapshot /// ---> This is where the issue seems to originate from
    var recordImage: PDFImage = PDFImage(image: UIImage(data: record.imageData!)!)
    recordImage.options = [.compress]
    recordImage.sizeFit = .widthHeight
    recordImage.quality = 0.85
    section.columns[1].add(.center, image: recordImage)
    document.add(section: section)
}

It is worth noting that I have placed the PDF process in an async block, similar to what was discussed in #162.
Questions
Is there a better way to go about this? Or some way for me to tell the PDFGenerator how many images and of what size to expect? Perhaps I am missing something, or just going about this very inefficiently. Either way, some feedback would be very helpful. Thank you.

Thanks for the detailed issue report.
On first thought this seems like a memory issue in UIKit, can you please add device info such as device type, OS version, memory-usage etc.?

Happens on both devices:
Device: iPhone 7
OS: iOS 14.4
Peak Memory Usage: 368 MB

Device: iPhone 12 Pro
OS: iOS 14.3
Peak Memory Usage: 736 MB

@philprime any ideas on this?

The error malloc: can't allocate region is new to me, and I also can't see a specific issue in your sample code.
So this might be a limitation of the render algorithm, as it needs to be in-memory.
I will mark this issue as an enhancement/performance/bug issue for now, and any further investigation is appreciated

Wondering if there's been any action on this issue over the last year or so. Thank you!

Hi @rldaulton there hasn't been any work from my side.
I still believe this is memory issue with CoreGraphics which is not able to deal with the amount of data.
Regarding the mention of handling large PDF files in the README, I added that note because of the amount of elements, rather than the file size. I will consider removing that note.
If no-one else is able to help, we could consider filing a bug report with Apple, and asking CoreGraphics Engineers for feedback.

@philprime I understand, thank you


fix(utils-split): dismiss inner observable on error

ups!

Is this use case covered by a test?

Of course, our code-coverage is 100%! that means that everything is covered by tests, right?
Just kidding! I've been trying to write a test for this, but I'm having a very hard time coming up with a decent one, but you are right, I won't merge it until I can write that test. Just to be clear, the test should not pass on the current main branch and it should pass after these changes.
Thanks @rikoe !

@all-contributors please add @rikoe for review

The first commit is a test that doesn't pass on main (I made sure that the CI ran on that commit and that the test fails) and the second commit is the one that fixes the issue.


Implement missing Gemini commands

Many Gemini commands remain unimplemented after the great redesign of the code for this mount. Implement them!
Since the scope of work is large, this can be tackled incrementally, starting with the commands deemed highest priority.

Do we need PEC commands? If so, which ones in particular?

Oh, I guess seeing-things/track#98 more-or-less lays out some of the commands that are higher priority.

Yeah. Those are just ones that came immediately to mind. There are no doubt others that could be added to that list.

Closing this since the scope is too broad. Will open issues for specific subsets of commands as they are needed.


CODEX-MARKETPLACE:  RFC Feedback

Made should changes to the marketplace RFC.

Some comments that needs to be fixed.
I noticed one thing. We use the phrase "client node(s)" - eq. the role name with the term "node", but for SPs we often just leave it as "SP", which imho is not nice. I guess this was introduced by Marcin and I have missed it. Could you please go over the spec and fix "SP" to "SP node(s)"?

Updated "SP" terms to "SP node" and "SPs" to "SP nodes" except for within the diagram. Also moved definitions back in Semantics section.

Great! Thanks and LGTM now.

There were a few comments where the conversation was marked as "resolved", but the request was not actually resolved. I went through and marked the unresolved comments as "unresolved".

Hmm I think most of those are actually resolved except one.

Hmm I think most of those are actually resolved except one.

No problem. I didn't know there were upstream changes.


nullary error() behavior different from stock lua

$ lua -e 'print(1); error(); print(2)'
1
$ elune/build/linux/bin/Release/lua5.1 -e 'print(1); error(); print(2)'
1
elune/build/linux/bin/Release/lua5.1: (error object is a nil value)
stack traceback:
        [C]: in function 'error'
        (command line):1: in main chunk
        [C]: in ?

Found through the busted Lua unittest framework, which uses error() on exit.

What busted is doing is weird and isn't even supported in newer Lua versions anyway; 5.3 onwards all raise this same error. Not going to fix this unless there's an extremely compelling reason.


⚠ Bofrost.de has degraded performance

In 7275f32, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1598 ms

Resolved: Bofrost.de performance has improved in f42364f.


Help With Pop!_OS Icon

I have already recreated the icon by hand and put it into svgcleaner but I am stuck at 1,248 bytes.
If anyone knows how to make it even smaller feel free to let me know :).
https://pastebin.com/69RK3Nd8

<svg xmlns="http://www.w3.org/2000/svg" aria-label="Pop!_OS" viewBox="0 0 512 512"><rect width="512" height="512" fill="#48b9c7" rx="15%"/><path fill="#fff" d="M144 145c-20 20 12 48 40 112 33 64 47 93 66 83 18-15-13-58-17-87 121-61 5-217-90-107Zm82 72q-11 2-24-27t-8-41q5-12 23 5t19 41q1 24-15 22Zm88-25c-23 133-2 137 50 13 11-25-45-42-50-13Zm-6 120c-15-3-27 22-7 30 19 3 21-25 7-30Zm-141 47a15 15 0 1 0 0 30h175a15 15 0 1 0 0-30Z"/></svg>

I use chrome as well, strange.