Genesis block has invalid hash

I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request
Current behavior:
the SHA-256 Hash of genesis block is invalid.
Expected behavior:
Genesis block hash must be valid
Steps to reproduce:

Create BlockData from current Block.Genesis block
Get blockData hash by SHA256 HashProvider

Other notes:

We must provide different hash for Genesis block for each of HashProvider.

With refactoring from #10 we have GenesisBlockFactory, so this issue isn't relevant anymore.


Gadget SDK - Logging Module

Logging
We should keep using tracing crate and its ecosystem, we could build a thin wrapper around it to make the logging follow a conventional scheme.
And since the shell manager is going to run these gadgets internally, it can wrap its stdout and stderr with a custom logger that appends the blueprint ID to the beginning of each line.

@Tjemmmic I've started this in #166, if you want to add to it that's the place.


civo: 1.0.32 -> 1.0.35

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/civo/cli/releases.
meta.description for civo is: "CLI for interacting with Civo resources"
meta.homepage for civo is: "https://github.com/civo/cli"
meta.changelog for civo is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.33 with grep in /nix/store/6ndlz409bf454kbwlf38ikdb0qwr4a69-civo-1.0.33
found 1.0.33 in filename of file in /nix/store/6ndlz409bf454kbwlf38ikdb0qwr4a69-civo-1.0.33

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
civo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6ndlz409bf454kbwlf38ikdb0qwr4a69-civo-1.0.33 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A civo https://github.com/r-ryantm/nixpkgs/archive/bf2befa1add7d28c3daa574bf3765cc9debd8dce.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6ndlz409bf454kbwlf38ikdb0qwr4a69-civo-1.0.33
ls -la /nix/store/6ndlz409bf454kbwlf38ikdb0qwr4a69-civo-1.0.33/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

civo

Maintainer pings
cc @berryp for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/civo/cli/releases.
meta.description for civo is: "CLI for interacting with Civo resources"
meta.homepage for civo is: "https://github.com/civo/cli"
meta.changelog for civo is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.35 with grep in /nix/store/1m4wy6q9c3623wycbq5h7mg61211b1z1-civo-1.0.35
found 1.0.35 in filename of file in /nix/store/1m4wy6q9c3623wycbq5h7mg61211b1z1-civo-1.0.35

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
civo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1m4wy6q9c3623wycbq5h7mg61211b1z1-civo-1.0.35 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A civo https://github.com/r-ryantm/nixpkgs/archive/5df930a76861269f7d5a8e7f6024638816dce3fe.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1m4wy6q9c3623wycbq5h7mg61211b1z1-civo-1.0.35
ls -la /nix/store/1m4wy6q9c3623wycbq5h7mg61211b1z1-civo-1.0.35/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

civo

Maintainer pings
cc @berryp for testing.

Result of nixpkgs-review pr 190120 run on x86_64-darwin 1

1 package built:

civo

Does https://github.com/civo/cli/commit/94a0f292be7ae0875de4753b8debeca00f15207e requires an update to the ldflags?

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/civo/cli/releases.
meta.description for civo is: "CLI for interacting with Civo resources"
meta.homepage for civo is: "https://github.com/civo/cli"
meta.changelog for civo is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.37 with grep in /nix/store/kb0jf5q89acprdhsf5vnyrg5x12rwajs-civo-1.0.37
found 1.0.37 in filename of file in /nix/store/kb0jf5q89acprdhsf5vnyrg5x12rwajs-civo-1.0.37

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
civo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kb0jf5q89acprdhsf5vnyrg5x12rwajs-civo-1.0.37 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A civo https://github.com/r-ryantm/nixpkgs/archive/48bdb2a4c55cfff74a5995f669424fc8d068324e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kb0jf5q89acprdhsf5vnyrg5x12rwajs-civo-1.0.37
ls -la /nix/store/kb0jf5q89acprdhsf5vnyrg5x12rwajs-civo-1.0.37/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

civo

Maintainer pings
cc @berryp for testing.

@berryp Does https://github.com/civo/cli/commit/94a0f292be7ae0875de4753b8debeca00f15207e requires an update to the ldflags?

@bobby285271 you're right, it does. Not sure how to proceed with an auto-generated PR where changes are required, but I'll look into it.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/civo/versions.
meta.description for civo is: "CLI for interacting with Civo resources"
meta.homepage for civo is: "https://github.com/civo/cli"
meta.changelog for civo is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.38 with grep in /nix/store/a6nnn889vn0kk6wlwy9zp9qvv3qz5b47-civo-1.0.38
found 1.0.38 in filename of file in /nix/store/a6nnn889vn0kk6wlwy9zp9qvv3qz5b47-civo-1.0.38

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
civo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/a6nnn889vn0kk6wlwy9zp9qvv3qz5b47-civo-1.0.38 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A civo https://github.com/r-ryantm/nixpkgs/archive/1c108c8c8671d10cb1d76814a9ce49407db2baa7.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/a6nnn889vn0kk6wlwy9zp9qvv3qz5b47-civo-1.0.38
ls -la /nix/store/a6nnn889vn0kk6wlwy9zp9qvv3qz5b47-civo-1.0.38/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

civo

Maintainer pings
cc @berryp for testing.

Please feel free to open a new PR for the changes

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/civo/cli/releases.
meta.description for civo is: "CLI for interacting with Civo resources"
meta.homepage for civo is: "https://github.com/civo/cli"
meta.changelog for civo is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.39 with grep in /nix/store/qpqwb42zc0igzy7bzispnk7b7bm68p6b-civo-1.0.39
found 1.0.39 in filename of file in /nix/store/qpqwb42zc0igzy7bzispnk7b7bm68p6b-civo-1.0.39

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
civo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qpqwb42zc0igzy7bzispnk7b7bm68p6b-civo-1.0.39 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A civo https://github.com/r-ryantm/nixpkgs/archive/2176c14354648bf3505d4a67ef373afa4b56f9bb.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qpqwb42zc0igzy7bzispnk7b7bm68p6b-civo-1.0.39
ls -la /nix/store/qpqwb42zc0igzy7bzispnk7b7bm68p6b-civo-1.0.39/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

civo

Maintainer pings
cc @berryp for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/civo/versions.
meta.description for civo is: "CLI for interacting with Civo resources"
meta.homepage for civo is: "https://github.com/civo/cli"
meta.changelog for civo is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.40 with grep in /nix/store/wbjb5hxk1pwiy7xkfn6xvgdlcnkkl4mg-civo-1.0.40
found 1.0.40 in filename of file in /nix/store/wbjb5hxk1pwiy7xkfn6xvgdlcnkkl4mg-civo-1.0.40

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
civo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wbjb5hxk1pwiy7xkfn6xvgdlcnkkl4mg-civo-1.0.40 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A civo https://github.com/r-ryantm/nixpkgs/archive/69d3bc4b6861cd716426fb1c7f8baa238343a155.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wbjb5hxk1pwiy7xkfn6xvgdlcnkkl4mg-civo-1.0.40
ls -la /nix/store/wbjb5hxk1pwiy7xkfn6xvgdlcnkkl4mg-civo-1.0.40/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

civo

Maintainer pings
cc @berryp for testing.

@marsam thanks for taking care of this! I recently had surgery so didn't have the opportunity.

Don't mention it :). Wishing you a speedy recovery!


feat: prepare logic to edit content via Stelace Dashboard

Stelace Dashboard and the template can communicate via
postMessage to select an entry to be edited.
This will enable in-context editor where the editing content
is previewed in live.

Thanks for the review. Here are the changes.

As discussed on slack you may need to replace X-Frame-Options header with something like Content-Security-Policy: frame-ancestors 'self' stelace.com localhost:* in netlify toml to allow iframes from dashboard. Localhost should probably not be allowed in production but only in dev and deploy preview branches so the instruction must be repeated in netlify.toml.

It seems we need frame-src in CSP header as well on stelace.com(/dashboard) to load other websites in iframe: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-src.

You're right. I changed the commit message.


Start 1.2.2

No review needed.

Coverage remained the same at 32.564% when pulling a765647cfb8f495d8868a4ae978f5e34355f8ba0 on start_1.2.2 into 710366f5e7094b378cfc7b224be35bb94efbfeb3 on stable_1.2.


ValidationError: duration is expected but was missing

Bug description
Hi all,
I'm getting this error

I think is related to #246 . Maybe the changes hasn't been published in a new version? I'm using 3.0.0
Expected behaviour
Not breaking when doing a request with the getTask method.
Is reproducible
Yes/No
To reproduce
It's the same problem that was in #245, and that was fixed in #246. I think it just hasn't been published.

Steps taken to try to reproduce

Screenshots

Version information:

Package version:

Additional information

v3.0.1 has been released which addresses this issue.


page.screenshot.type not respected

When taking a screenshot, even though the type is specified as "png", puppeteer uses the file extension of the output file to determine the mime type.
Environment

Windows 7
Puppeteer NPM version 0.13.0
Node version 7.10.0

Steps to reproduce
Create a basic screenshot script such as this (example.js):
(async () => {
	const puppeteer = require('puppeteer');
	const browser = await puppeteer.launch();
	const page = await browser.newPage();
	await page.goto("https://google.co.uk/", {waitUntil: "load"});
	await page.screenshot({
		path: "C:/img.tmp",
		type: "png"
	});
	await browser.close();
})();

Run the script on the command line:
$ node example.js
What is the expected result?
The program should take a PNG screenshot of https://google.co.uk/ and save it to "C:/img.tmp".
What happens instead?
(node:65264) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id:2): Assertion error: Unsupported screenshot mime type: application/octet-stream
It seems to be trying to determine the output type from the file extension regardless of the type setting. This may prevent usage of output targets like /dev/stdout.

https://github.com/GoogleChrome/puppeteer/blob/2becd156d0b25ad3fe4f7b91101b32aead70bd96/lib/Page.js#L615-L629
Puppeteer tries to deduce the mimetype from the file passed in options.path even if the type is specified with the option.type. This is problematic when the filename passed in options.path already exists and is empty (for example, a temp file created by another process which is calling the screenshot script).

I've created a PR that addresses this : https://github.com/GoogleChrome/puppeteer/pull/1526


Issues with repositories after upgrading to 0.10.1

Hi
I have a repository in my config:
[[tool.poetry.source]]
name = "myrepo"
url = "http://reposerver.local/pypi/packages"

In version 0.9.0 everything worked fine, but after upgrade, poetry cannot find correct files. It tries to get file https://reposerver.local/pypi/packages/helper-0.0.92.tar.gz instead of
https://reposerver.local/pypi/packages/helper/helper-0.0.92.tar.gz (as was in previous version).

Do you mean for hosting repository? nginx.

No, I meant the application itself you are using to host the packages (like devpi or pyshop).

Only nginx

29 мая 2018 г., в 19:16, Sébastien Eustace<EMAIL_ADDRESS>написал(а):
No, I meant the application itself you are using to host the packages (like devpi or pyshop).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Are the packages links in https://reposerver.local/pypi/packages/helper/ relative or absolute?

I've also hit an issue where it says:
± % poetry lock
Updating dependencies
Resolving dependencies... (0.8s)

[BadZipfile]
File is not a zip file

lock

This is using our private repo (artifactory), that seems to give relative paths. This seems different from official pypi which gives absolute paths.

Are the packages links in https://reposerver.local/pypi/packages/helper/ relative or absolute?

Links are relative there in the source code of that page.


enhance warning/debug info

Give user better instructions on why the No meta data is found happens

Codecov Report

Merging #11 into master will decrease coverage by 0.18%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
- Coverage   87.55%   87.36%   -0.19%
==========================================
  Files           9        9
  Lines         474      475       +1
  Branches       87       87
==========================================
  Hits          415      415
- Misses         59       60       +1

Impacted Files
Coverage Δ

lib/executor.js
67% <0%> (-0.68%)
:arrow_down:

Continue to review full report at Codecov.

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

👍 !


Add basic chanperf tracking

Added in FW 10: https://developer.roku.com/docs/developer-program/debugging/debugging-channels.md#scenegraph-debug-server-port-8080-commands
I will be starting this today. First pass is just focused on adding the tracking and using a native VS code view. Long term it would be great to graph this over time in some sort of web view but we can do that in its own pass.

https://github.com/rokucommunity/roku-debug/pull/30


[WIP] PHPUnit support

I am trying to create a pull request to add PHPUnit support but at the moment I am having trouble getting my tests to pass as Expect exists('g:test#last_command') == 1 is failing. Is there something else I need to do to hook it in?

In test#php#phpunit#test_file you used the 'test\.php$' regex, so vim-test doesn't recognize NormalTest.php as a PHPUnit test file (because of the capital T). If you change the regexp to '\v(t|T)est\.php$', it should work.

Even after that fix still having issues with the tests failing

-------- Testing a Vim plugin
spec/phpunit_spec.vim .. 1/?
not ok 1 - PHPUnit runs file tests instead of nearest tests
Expected exists('g:test#last_command') == 1
Actual value: 0
Expected value: 1
not ok 2 - PHPUnit runs file tests
Expected exists('g:test#last_command') == 1
Actual value: 0
Expected value: 1
not ok 3 - PHPUnit runs test suites
Expected exists('g:test#last_command') == 1
Actual value: 0
Expected value: 1
spec/phpunit_spec.vim .. Failed 3/4 subtests

Sorry for the slow responses :). in plugin/test.vim you also need to add PHPUnit to the list in the g:test#runners variable. Adding the following line should do it:
  \ 'PHP':        ['PHPUnit'],

Also, after making it work, you can add it to the list of frameworks in the README.

Excellent! Ready for merging?

I think so, I've tested it out on a project and it's working fine for me.

Awesome, thank you so much for contributing! :heart:


About FBX resource import？

Consult the resource pipeline documentation
Known problems:
-Skeletons and animations scaled from centimeters to meters (* 0.01). This is only required for FBX files. If we want to support other formats this has to be changed.
-See: AssetPipeline.cpp - line: 392 & 537 & 546
-Boris (Unreal Paragon asset) rotated 90 degrees on x axis after putting it through the animation pipeline. Blender also doesn’t import model correctly. Rotating the model in either Maya or Blender causes severe problems in the animation.
The bone file generated by fbx2ozz is correct。
AssetPipelineCmd.exe generated skeletal  rotated 90 degrees on x axis ?
How should fbx be exported or how to set it correctly, I use
		AssimpImporter        importer;
		AssimpImporter::Model model = {};
		if (!importer.ImportModel(fullPath.c_str(), &model))
			return false;

The fbx model is magnified n times, The FBX in the example is correct, how should the FBX model be derived

I want to use the application provided by the fbx2ozz.exe ozz engine to generate bones and animations, use The-Forge Engine AssimpImporter code to import skins, do not need AssetPipelineCmd.exe, is it ok?

The version of Assimp we used while this unit test was written had an issue that caused all meshes to be 100x larger than intended and rotated on the x-axis. This is because in the FBX the mesh is stored in centimeters instead of meters and because most modelling tools use a different coordinate system. We added a workaround for this behaviour in the AssetPipeline. If the scale of your model is incorrect, try exporting it in meters using your favourite modeling tool. Our model is only a couple of units(meters) tall. Make sure yours is the about the same.
We used to use animations and skeletons exported through fbx2ozz.exe internally for testing purposes. I can't think if any reason why they wouldn't work now.

Hi.
Thanks for the reply.
I used the example  simpleTest\riggedMesh.fbx, simpleTest\twistShift.fbx bones and animations to test, import the animation into max, and then export the FBX file, whether it is Y axis or Z axis up, the animation is always put down 90 degrees, but Maya import and then export That's right, I think it's a good resource to handle this piece of code.
I hope to improve the code of this piece.

Any more questions or can we close this issue?

MM_Big.zip
AssetPipelineCmd  ， If you import this model, what are the steps and specifications?

JL.zip
AssimpPipeline Create Runtime Animation There seems to be some problems

The AssetPipeline requires you to seperate your bind pose mesh with skeleton and the animations into seperate files. For example:
Examples_3/Unit_Tests/UnitTestResources/Animation/fbx/simpleTest contains riggedMesh.fbx. This FBX file contains only the mesh and the skeleton in bind pose.
Examples_3/Unit_Tests/UnitTestResources/Animation/fbx/simpleTest/animations contains two files. Each only contains an animated skeleton. No triangle data is stored in this file.
Our animation middleware has the same requirement. It expects the bind pose and animation seperetly.
If seperating the model from the animation doesn't fix your issue, please send us the code and the assets in FBX format so we can evaluate the problem.

riggedMesh.zip

Please create two fbx files. One containing only the mesh and the skeleton in bindpose and one with only the animation. Look at the assets in the Examples_3/Unit_Tests/UnitTestResources/Animation/fbx/simpleTest directory if you need an example.

Hello,  @timoconffx
I am doing this.  One containing only the mesh and the skeleton in bindpose and one with only the animation.
Exported with maya,  Validate raw animation failure.
Exported with max,  There will be such an error. As shown above.
why?
One containing only the mesh and the skeleton in bindpose and one with only the animation.
Same FBX，  What's the difference?

@myluoxz
The zip file you send us contains only one fbx file. This FBX contains both the mesh and the animation. They should be in seperate files. We can't help you if we don't have the files.
FBX files are tricky. There are often problems when importing FBX files, just because all exporters seem to export them differently. A mesh exporter from Blender might work fine. That same mesh exported from Maya might not. We primarily use Blender. You could try exporting the mesh using Blender instead.

LuoxzTest.zip

LuoxzTest-3dsMax.zip

@myluoxz
You can fix the problem by freezing/applying the transform of your meshes before exporting.
The body and hair mesh both reference "Bip01 Head" and a couple of other bones. The bone offset matrices are stored in mesh local space. Because your meshes are split the bone offset matrix of "Bip01 Head" is different for the body than it is for the hair. Currently the last bone offset that is written to the boneOffsetMatrices vector is taken even if a matrix has already been assigned. Because of this the body was using the bone offset matrix of the hair. This is what is causing the stretching. The problem can be fixed by freezing/applying the transform of your meshes before exporting. Effectively making them use the same local space.
Thank you for helping us figure out this problem. We will try to include a more permanent fix for this problem in our next release.

thank you very much， @timoconffx
Solve the problem by freezing/applying the transformation of the grid before exporting.
Is this step done in blender? Still doing it in 3DS Max?
I am not familiar with Blender, ask, in which menu to set the freeze and apply grid transformation, please give a detailed step?

@myluoxz
In the next release of the Forge your issue has been fixed.
For now here are the steps to freeze the transform in Blender:

Open RiggedMesh.fbx in Blender.
Right click the body mesh to select it.
Press Ctrl+A while your cursor is over the viewport to open the apply menu.
Select Location.
Press Ctrl+A again.
Select Rotation & Scale.
Right click in the hair mesh to select it.
Repeat steps 3 to 6.

@timoconffx
Thank you very much, it has been perfect for it to work, I look forward to the next version, thank you!!

This should be fixed. Please let us know.

@myluoxz can you confirm it works for you? In that case, I would close this issue.


docker pull from private registry before login

RancherOS Version: (v1.5.3)
Where are you running RancherOS? (bare-metal)
we using gcr.io as private docker registry, everything is ok when we use ros service start SERVICE
but when we do fresh start there is an authorization issue on login screen
i wrote auth key in cloud config like
rancher:
registry_auths:
https://grc.io:
auth: our key
also i`m using write_files to write auth key in .docker/
**write_files:

path: /home/rancher/.docker/config.json
permissions: "0644"
owner: rancher
content: |
{"auths":{"gcr.io":{"auth": "some key"}},"wqHttpHeaders": {"User-Agent": "Docker-Client/18.09.2 (linux)"}}**

I reproduce the issue and it looks like the ros startup did not load the ~/.docker/config.json config. We can start ros service via rc.local
Because the ros service requires root privileges, the private registries should be configured in the /root/.docker/ directory.
The following is a complete example:
#cloud-config
write_files:
  - path: /root/.docker/config.json
    permissions: "0755"
    owner: rancher
    content: |
      {
        "auths": {
          "https://gcr.io/": {
            "auth": "some keys"
            "email"<EMAIL_ADDRESS>          }
        }
      }
  - path: /home/rancher/.docker/config.json
    permissions: "0755"
    owner: rancher
    content: |
      {
        "auths": {
          "https://gcr.io/": {
            "auth": "some keys"
            "email"<EMAIL_ADDRESS>          }
        }
      }
  - path: /etc/rc.local
    permissions: "0755"
    owner: root
    content: |
      #!/bin/bash
      ros s up myservice


Apply default configuration from widget definition

I had to add this line to enable apply widget's default config. It was not working as appears in documentation.

Could you post an not working example? Because the clock-widget uses a default config and it works.


Improve the header

Is your feature request related to a problem? Please describe.
The text in the header and its placement does not look. Also there is hello written above select your location which is not needed.
Describe the solution you'd like
Remove the hello text placed above select the location. Improve the text positioning and text font basically making changes in css.
Describe alternatives you've considered
No response
Additional context
No response

Thanks for opening the issue! go ahead @Aakash441 🚀
I would suggest you take care of the CSS as we have recently merged a PR handling the responsiveness of the header.


Multiple groupby operations in succession for a dataframe generated in-memory fails with ValueError('Length Mismatch')

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 20.04
Modin version (modin.__version__): 0.13.2
Python version: Python 3.8.10
Code we can use to reproduce:

import modin.pandas as pd
from faker import Faker

# Column Label -> Faker Format Mapping
base_artifact_schema= {
    "Pqt4j__isbn10": "isbn10",
    "lrVJa__ean8": "ean8",
    "goWHd__ssn": "ssn",
    "HjYM3__ipv4_network_class": "ipv4_network_class",
    "wvamF__postalcode_plus4": "postalcode_plus4",
    "LqReR__last_name_female": "last_name_female",
    "fESWJ__pyint": "pyint",
    "oGXTu__pyint": "pyint",
    "l8lea__chrome": "chrome",
    "EtC7T__uri": "uri"
}

#Stripped down version of randomized table generator for bug reproduction
def generate_table(num_rows=100, schema=None):
    faker = Faker()

    series_list = []
    label_list = []

    for label, column in schema.items():
        series_list.append(pd.Series((faker.format(column) for _ in range(num_rows))))
        label_list.append(label)

    return pd.concat(series_list, axis=1, keys=label_list)

# The following code operates on the generated, in-memory version of the dataframe artifact_0
# The second groupby fails with "ValueError('Length mismatch: Expected axis has 0 elements, new values have 3 elements')"
artifact_0 = generate_table(num_rows=1000, schema=base_artifact_schema)
artifact_1 = artifact_0[["HjYM3__ipv4_network_class", "fESWJ__pyint","oGXTu__pyint"]].groupby("HjYM3__ipv4_network_class").count().reset_index()
artifact_2 = artifact_1[["HjYM3__ipv4_network_class", "fESWJ__pyint","oGXTu__pyint"]].groupby("HjYM3__ipv4_network_class").sum().reset_index()
print(artifact_2)

Describe the problem
A dataframe generated in memory using pd.concat() with a list of pd.Series objects cannot perform these two groupby operations in succession, failing with a ValueError('Length mismatch: Expected axis has 0 elements, new values have 3 elements').
If the dataframe is written out to CSV and re-loaded, the operation succeeds:
# The following version, which writes the dataframe to disk and reloads it, succeeeds
artifact_0.to_csv('/tmp/artifact_0.csv')
artifact_0 = pd.read_csv('/tmp/artifact_0.csv',  index_col=0)
artifact_1 = artifact_0[["HjYM3__ipv4_network_class", "fESWJ__pyint","oGXTu__pyint"]].groupby("HjYM3__ipv4_network_class").count().reset_index()
artifact_2 = artifact_1[["HjYM3__ipv4_network_class", "fESWJ__pyint","oGXTu__pyint"]].groupby("HjYM3__ipv4_network_class").sum().reset_index()
print(artifact_2)

Source code / logs
Exact traceback attached: Traceback
Virtual Environment: pip freeze output

@suhailrehman thank you for the detailed report. I'm unable to use your code to reproduce the bug on my computer, because I don't have base_artifact_schema. Could you please send a snippet to generate that as well?

@mvashishtha sorry for the variable mismatch. It should be fixed now (edited in place)

@suhailrehman thank you. I can reproduce the bug now on the latest Modin source. I'll do some triage now and if I can't make a quick fix, we'll try to fix the bug as soon as possible.

@modin This looks like a bug with lazy metadata propagation. If I remove this condition so that groupby_reduce always operates on an updated index, I can fix the bug. I guess we need to fix that condition.


[Feature] Add Warp 10 as a storage option

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion
[ ] Bug
[ ] Requirement
[X ] Feature or performance improvement

Question

What do you want to know?

Bug

Which version of SkyWalking, OS and JRE?

Which company or project?

What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.

Requirement or improvement
Support Warp 10 as the storage backend for metrics

Proposal, design, and pull request are welcome. New storage implementation is open to 3rd part.


Update discover-and-assess-using-private-endpoints.md

Updated note before the steps to download the appliance that OVA and VHDs are not available for download. It was not explicitly written that the OVA or VHD appliances wouldn't be supplied.

@pingvishal-msft
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Updated the initial commit by moving the sentence "Projects with private endpoints do not offer the ability to download OVA or VHD templates." to the beginning of the note. It seems to help with prefacing the note's overall message.

The proposed changes are live. https://learn.microsoft.com/en-us/azure/migrate/discover-and-assess-using-private-endpoints#download-the-appliance-installer-file Please close this PR.

Molish (Azure Migrate Product Group)

Updated patch-2 with changes from main to resolve the conflict.

Closing this PR because the changes are now live: https://github.com/MicrosoftDocs/azure-docs/pull/117999#issuecomment-1876447979.
Thanks for your contribution!


[feat] polymorphic prop

Describe the problem
We have a custom element that can dynamically act like a dom element, for example:
<VisuallyHidden as='button'>Submit</VisuallyHidden>

We want to run eslint-react's DOM related rules against it as well.
Describe the solution you'd like
I noticed the additionalComponents config, but currently seems like there is no way to set the as dynamically based on the selector (like in regular expression). But even if we do have a way, the polymorphicPropName like in eslint-plugin-jsx-a11y would be so much easier to understand and use. Reference: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y#configurations
{
  "settings": {
    "jsx-a11y": {
      "polymorphicPropName": "as"
    }
  }
}

Alternatives considered
No response
Additional context
No response

Nice suggestion, it will be supported in the next version!


centos stream 9 to rocky 9 migration failure with cannot install the best update candidate for package kernel-devel-matched-5.14.0-474.el9.x86_64

FWIW, I am migrating my various centos stream 9 hosts to rocky 9 and have hit this error twice today
...
Complete!
Last metadata expiration check: 0:02:15 ago on Wed Jul 10 12:54:37 2024.
No package fwupdate* installed.
Error:
 Problem 1: cannot install the best update candidate for package kernel-devel-matched-5.14.0-474.el9.x86_64
  - nothing provides kernel-core = 5.14.0-427.24.1.el9_4 needed by kernel-devel-matched-5.14.0-427.24.1.el9_4.x86_64 from appstream
 Problem 2: problem with installed package kernel-devel-matched-5.14.0-474.el9.x86_64
  - kernel-devel-matched-5.14.0-474.el9.x86_64 from @System  does not belong to a distupgrade repository
  - nothing provides kernel-core = 5.14.0-427.24.1.el9_4 needed by kernel-devel-matched-5.14.0-427.24.1.el9_4.x86_64 from appstream
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Error during distro-sync.

An error occurred while we were attempting to convert your system to Rocky Linux. Your system may be unstable. Script will now exit to prevent possible damage.

Can you show your full migrate2rocky.log file please?

Sure, here it is.
migrate2rocky.log.txt

Do you have kernel* excluded?  This appears to be the root of the problem.
Other items of note from the log:
centos-stream-release seems to be mis-detected as centos-release-automotive.  Ultimately this does not appear to be causing any issues but it's something to look into and fix.
distro-sync appears to complete and only then errors out.  This can be problematic.
migrate2rocky9 is looking for a package that matches fwupdate*.  This is a relic from migrate2rocky and doesn't appear to be causing any harm, but that should be removed because there are no fwupdate* packages in EL9.

Do you have kernel* excluded? This appears to be the root of the problem.

I do not believe so.  I should mention that for the two systems that have failed, they both are using openzfs. I did have 1 openzfs system succeed though.  I have completed about 15 systems so far, so only two failures isn't too bad :)  I have got a couple of ZFS hosts yet to go, so I'll see if I can increase the debugging on the failing dnf command and get you something more to go on here.

I tried another ZFS CS9 box now and got the same failure.  I instrumented the distro-sync dnf commands with a -v, but the output does not look that exciting to me :(
migrate2rocky.log.txt

This seems like a problem to me, running from the host broken with the last comment
# dnf whatprovides  kernel-devel-matched
Last metadata expiration check: 0:20:14 ago on Thu 11 Jul 2024 08:23:47 AM CDT.
kernel-devel-matched-5.14.0-427.22.1.el9_4.x86_64 : Meta package to install matching core and devel packages for a given kernel
Repo        : appstream
Matched from:
Provide    : kernel-devel-matched = 5.14.0-427.22.1.el9_4

kernel-devel-matched-5.14.0-474.el9.x86_64 : Meta package to install matching core and devel packages for a given kernel
Repo        : @System
Matched from:
Provide    : kernel-devel-matched = 5.14.0-474.el9

So there's no 5.14.0-427.24.1 there, but only 5.14.0-427.22.1 ???  but on a host I manually repaired
dnf list kernel-devel-matched-5.14.0-427.24.1.el9_4.x86_64
Last metadata expiration check: 1:10:46 ago on Thu 11 Jul 2024 07:27:19 AM CDT.
Installed Packages
kernel-devel-matched.x86_64    5.14.0-427.24.1.el9_4   @appstream

Sorry to microblog here, so I run dnf clean all and now 24 appears available
# dnf clean all
182 files removed
# dnf whatprovides  kernel-devel-matched
dell-system-update_independent                                                                                293 kB/s | 142 kB     00:00
dell-system-update_dependent                                                                                406 kB/s | 272 kB     00:00
Extra Packages for Enterprise Linux 9 - x86_64                                                                                21 MB/s |  22 MB     00:01
Extra Packages for Enterprise Linux 9 openh264 (From Cisco) - x86_64                                                                                4.5 kB/s | 2.5 kB     00:00
Rocky Linux 9 - BaseOS                                                                                4.8 MB/s | 2.3 MB     00:00
Rocky Linux 9 - AppStream                                                                                12 MB/s | 7.9 MB     00:00
Rocky Linux 9 - CRB                                                                                5.2 MB/s | 2.4 MB     00:00
Rocky Linux 9 - Extras                                                                                51 kB/s |  15 kB     00:00
ZFS on Linux for EL9 - dkms                                                                                191 kB/s | 107 kB     00:00
kernel-devel-matched-5.14.0-427.24.1.el9_4.x86_64 : Meta package to install matching core and devel packages for a given kernel
Repo        : appstream
Matched from:
Provide    : kernel-devel-matched = 5.14.0-427.24.1.el9_4

kernel-devel-matched-5.14.0-474.el9.x86_64 : Meta package to install matching core and devel packages for a given kernel
Repo        : @System
Matched from:
Provide    : kernel-devel-matched = 5.14.0-474.el9

So ZFS may be a red herring, the next system (sans ZFS) I tried worked without issue and got kernel 5.14.0-427.24.1, but this system does not have kernel-devel installed.  I may just be getting unlucky here with mirrors not being fully synced.


Performance Improvement of Assessment Aggregator Flink Job

…link Job.

These changes are no longer required hence closing this.


v1.2.130 breaks "this" context in the backbone model

Describe the bug
Version 1.2.130 breaks backbone models in our application with the following error:
backbone.js:1102 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'idAttribute')
    at CardCollection.modelId (backbone.js:1102:1)
    at CardCollection.get (backbone.js:997:1)

the issue happens on this line:
    modelId: function(attrs) {
     // this.model is undefined in this context
      return attrs[this.model.prototype.idAttribute || 'id'];
    },

On version 1.2.129, this works fine.
Input code
No response
Config
{
  "test": ".jsx?$",
  "sourceMaps": true,
  "inlineSourcesContent": true,
  "jsc": {
    "parser": {
      "syntax": "ecmascript",
      "jsx": true,
      "decorators": false,
      "dynamicImport": true
    },
    "transform": {
      "react": {
        "throwIfNamespace": true,
        "refresh": true,
        "useBuiltins": false,
        "runtime": "automatic"
      }
    },
    "target": "es2015"
  },
  "module": {
    "type": "commonjs",
    "strict": false,
    "strictMode": true,
    "lazy": false,
    "noInterop": false,
    "ignoreDynamic": true
  }
}

Playground link
No response
Expected behavior
same as in 1.2.129 version
Actual behavior
No response
Version
1.2.130
Additional context
No response

Same problem here, crucial.
class Previewer extends React.Component {
  dummy = false

  componentDidUpdate (prevProps, prevState, snapshot) {
    this.initialize()
  }

  initialize = async () => {

  }

  loadObject = async () => {
    // Breaks, no access to this anymore....
    if (this.dummy) {
      ...
    }
  }
}

when I downgraded to 1.2.129, the code mentioned by me above started to work but I noticed some other parts of APP are still broken (issue a bit more similar as by @mikevercoelen - async function, this not accessible). Had to downgrade back to 1.2.125

this sounds like some regressions around recent changes in https://github.com/swc-project/swc/issues/2716 ?

Same problem here, crucial.
class Previewer extends React.Component {
  dummy = false

  componentDidUpdate (prevProps, prevState, snapshot) {
    this.initialize()
  }

  initialize = async () => {

  }

  loadObject = async () => {
    // Breaks, no access to this anymore....
    if (this.dummy) {
      ...
    }
  }
}

This compiles to
var _this = this;
this.loadObject = _asyncToGenerator(function*() {
     // Breaks, no access to this anymore....
     if (_this.dummy) {
     }
})

which seems fine

Can you share more input code?
I can't create a test from the info you wrote

Closing as the author did not provide enough information to debug.


Gobblin metrics refactor

A POC for refactoring of gobblin-metrics to decrease external dependencies. No significant code changes

Created a new library gobblin-metrics-modules/gobblin-metrics-base which contains the basic APIs/implementations for gobblin-metrics
Moved some common testing classes to gobblin.metrics.testing
Created a new library gobblin-metrics-modules/gobblin-metrics-influxdb which contains the InfluxDB reporter
Created a new library gobblin-metrics-modules/gobblin-metrics-graphite which contains the Graphite reporter
Created a new library gobblin-metrics-modules/gobblin-metrics-hadoop which contains the Hadoop counters reporter
Created a new library gobblin-metrics-modules/gobblin-metrics-kafka which contains the Kafka reporter
The previous gobblin-metrics library now depends on all of the above for backwards compatibility reasons. It also contains GobblinMetrics and GobblinMetricsRegistry which have explicit dependency on the different reporters. Removing that dependency will require some code refactoring.

Subsequent steps (other PRs):

Refactor GobblinMetrics to auto-discover reporters and move it to gobblin-metrics-base. At that point the gobblin-metrics library should be marked as deprecated.
Refactor gobblin-distribution to have 3 flavors: minimal (pre-defined reporters), standard (e.g. Kafka reporter and Hadoop counters reporter), full (all reporters), custom (user-specified reporters)

@abti @ibuenros @pcadabam This is a follow-up on our discussion about separating external dependencies. What do you think?

Superseded by https://github.com/linkedin/gobblin/pull/1442/files


Add workshop notes

Proposed changes
Add a few brief notes about how to run through the workshop.
Checklist (replace [ ] with [x] to check off)

[x] Notebook created using the DEA-notebooks template
[x] Remove any unused Python packages from Load packages
[x] Remove any unused/empty code cells
[x] Remove any guidance cells (e.g. General advice)
[x] Ensure that all code cells follow the PEP8 standard for code. The jupyterlab_code_formatter tool can be used to format code cells to a consistent style: select each code cell, then click Edit and then one of the Apply X Formatter options (YAPF or Black are recommended).
[x] Include relevant tags in the final notebook cell (refer to the DEA Tags Index, and re-use tags if possible)
[x] Clear all outputs, run notebook from start to finish, and save the notebook in the state where all cells have been sequentially evaluated
[x] Test notebook on both the NCI and DEA Sandbox (flag if not working as part of PR and ask for help to solve if needed)
[x] If applicable, update the Notebook currently compatible with the NCI|DEA Sandbox environment only line below the notebook title to reflect the environments the notebook is compatible with

This looks good! Please "squash and merge" because the git history on this branch is a bit odd.

Yeah I think this branch derived from stable rather than develop - shouldn't be a major problem if it's squashed!

Nah, I'll fix it. Hang on.

Ok, clean commits now :-)


nsc-events-nextjs-01-119-modify-frontend-port

Relates to user story #119
This pr creates an example .env with the proper environment variables and values. The frontend .env variable for the url is set to http://localhost:3001. The MONGO_URI is just an example of a value but one would need to capture that connection string value after creating a database instance or if one already exists, you can just grab that connection string and add it as the MONGO_URI value. Here is a quick demonstration of the steps https://youtu.be/Ye28mc1Ipy8

I just noticed that the .env file is just helping us for now, but later we might not need it because we will fetch API endpoints from the backend to capture data.

I just noticed that the .env file is just helping us for now, but later we might not need it because we will fetch API endpoints from the backend to capture data.

Yeah, we should make a note to make sure to remove this with the release version of the app


Add stars to full catalog decoder

Thanks @wangchv for working on this. It's a little hard to review because of the rebasing I was saying ( I think you will need to copy the new code to a different branch and start over the PR).
From what I gathered in the diff, it looks like you are in the right track. You just need to remove my original classes and replace with yours. Let's talk more about exactly what changes to make in our meeting


Iterated relaxation for integer variables

Which should have the unit "count"

Not going in initial release

superseded by #414


Does not work with docker

When i save that content to a file:
´´´
version: "3"
services:
app:
image: 'jc21/nginx-proxy-manager:latest'
restart: always
ports:
# Public HTTP Port:
- '80:80'
# Public HTTPS Port:
- '443:443'
# Admin Web Port:
- '81:81'
environment:
# These are the settings to access your db
DB_MYSQL_HOST: "db"
DB_MYSQL_PORT: 3306
DB_MYSQL_USER: "npm"
DB_MYSQL_PASSWORD: "npm"
DB_MYSQL_NAME: "npm"
# If you would rather use Sqlite uncomment this
# and remove all DB_MYSQL_* lines above
# DB_SQLITE_FILE: "/data/database.sqlite"
# Uncomment this if IPv6 is not enabled on your host
# DISABLE_IPV6: 'true'
volumes:
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
depends_on:
- db
db:
image: 'jc21/mariadb-aria:latest'
restart: always
environment:
MYSQL_ROOT_PASSWORD: 'npm'
MYSQL_DATABASE: 'npm'
MYSQL_USER: 'npm'
MYSQL_PASSWORD: 'npm'
volumes:
- ./data/mysql:/var/lib/mysql
´´´
Then save it in an file called ´docker-compose´ then run ´docker docker-compose up -d´ it does not work: Get that errors:
´´´
root@nginx-proxy-manager-debian10:~# docker ./docker-compose up -d
unknown shorthand flag: 'd' in -d
See 'docker --help'.
Usage:  docker [OPTIONS] COMMAND
A self-sufficient runtime for containers
Options:
--config string      Location of client config files (default "/root/.docker")
-c, --context string     Name of the context to use to connect to the daemon (overrides DOCKER_HOST env var and default context set with "docker context use")
-D, --debug              Enable debug mode
-H, --host list          Daemon socket(s) to connect to
-l, --log-level string   Set the logging level ("debug"|"info"|"warn"|"error"|"fatal") (default "info")
--tls                Use TLS; implied by --tlsverify
--tlscacert string   Trust certs signed only by this CA (default "/root/.docker/ca.pem")
--tlscert string     Path to TLS certificate file (default "/root/.docker/cert.pem")
--tlskey string      Path to TLS key file (default "/root/.docker/key.pem")
--tlsverify          Use TLS and verify the remote
-v, --version            Print version information and quit
Management Commands:
app*        Docker App (Docker Inc., v0.9.1-beta3)
builder     Manage builds
buildx*     Build with BuildKit (Docker Inc., v0.5.1-docker)
config      Manage Docker configs
container   Manage containers
context     Manage contexts
image       Manage images
manifest    Manage Docker image manifests and manifest lists
network     Manage networks
node        Manage Swarm nodes
plugin      Manage plugins
scan*       Docker Scan (Docker Inc., v0.7.0)
secret      Manage Docker secrets
service     Manage services
stack       Manage Docker stacks
swarm       Manage Swarm
system      Manage Docker
trust       Manage trust on Docker images
volume      Manage volumes
unknown shorthand flag: 'd' in -d
See 'docker --help'.
Usage:  docker [OPTIONS] COMMAND
A self-sufficient runtime for containers
Options:
--config string      Location of client config files (default "/root/.docker")
-c, --context string     Name of the context to use to connect to the daemon (overrides DOCKER_HOST env var and default context set with "docker context use")
-D, --debug              Enable debug mode
-H, --host list          Daemon socket(s) to connect to
-l, --log-level string   Set the logging level ("debug"|"info"|"warn"|"error"|"fatal") (default "info")
--tls                Use TLS; implied by --tlsverify
--tlscacert string   Trust certs signed only by this CA (default "/root/.docker/ca.pem")
--tlscert string     Path to TLS certificate file (default "/root/.docker/cert.pem")
--tlskey string      Path to TLS key file (default "/root/.docker/key.pem")
--tlsverify          Use TLS and verify the remote
-v, --version            Print version information and quit
Management Commands:
app*        Docker App (Docker Inc., v0.9.1-beta3)
builder     Manage builds
buildx*     Build with BuildKit (Docker Inc., v0.5.1-docker)
config      Manage Docker configs
container   Manage containers
context     Manage contexts
image       Manage images
manifest    Manage Docker image manifests and manifest lists
network     Manage networks
node        Manage Swarm nodes
plugin      Manage plugins
scan*       Docker Scan (Docker Inc., v0.7.0)
secret      Manage Docker secrets
service     Manage services
stack       Manage Docker stacks
swarm       Manage Swarm
system      Manage Docker
trust       Manage trust on Docker images
volume      Manage volumes
Commands:
attach      Attach local standard input, output, and error streams to a running container
build       Build an image from a Dockerfile
commit      Create a new image from a container's changes
cp          Copy files/folders between a container and the local filesystem
create      Create a new container
diff        Inspect changes to files or directories on a container's filesystem
events      Get real time events from the server
exec        Run a command in a running container
export      Export a container's filesystem as a tar archive
history     Show the history of an image
images      List images
import      Import the contents from a tarball to create a filesystem image
info        Display system-wide information
inspect     Return low-level information on Docker objects
kill        Kill one or more running containers
load        Load an image from a tar archive or STDIN
login       Log in to a Docker registry
logout      Log out from a Docker registry
logs        Fetch the logs of a container
pause       Pause all processes within one or more containers
port        List port mappings or a specific mapping for the container
ps          List containers
pull        Pull an image or a repository from a registry
push        Push an image or a repository to a registry
rename      Rename a container
restart     Restart one or more containers
rm          Remove one or more containers
rmi         Remove one or more images
run         Run a command in a new container
save        Save one or more images to a tar archive (streamed to STDOUT by default)
search      Search the Docker Hub for images
start       Start one or more stopped containers
stats       Display a live stream of container(s) resource usage statistics
stop        Stop one or more running containers
tag         Create a tag TARGET_IMAGE that refers to SOURCE_IMAGE
top         Display the running processes of a container
unpause     Unpause all processes within one or more containers
update      Update configuration of one or more containers
version     Show the Docker version information
wait        Block until one or more containers stop, then print their exit codes
Run 'docker COMMAND --help' for more information on a command.

If yes, file should be "docker-compose.yml", the command then is "docker-compose up -d"

Thank you very much. I installed it as described here: https://docs.docker.com/engine/install/debian/
Cite: ´apt-get install docker-ce docker-ce-cli containerd.io´
Do i also have to add the ´docker-compose´ package to the APT command.
Like that?
-> ´apt-get install docker-ce docker-ce-cli containerd.io docker-compose´

OK, now i insalled the package "docker-compose"...
Then, i have to save that lines in a file called e.g. "MY_DOCKER_FILE":
version: "3"
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: always
    ports:
      # Public HTTP Port:
      - '80:80'
      # Public HTTPS Port:
      - '443:443'
      # Admin Web Port:
      - '81:81'
    environment:
      # These are the settings to access your db
      DB_MYSQL_HOST: "db"
      DB_MYSQL_PORT: 3306
      DB_MYSQL_USER: "npm"
      DB_MYSQL_PASSWORD: "npm"
      DB_MYSQL_NAME: "npm"
      # If you would rather use Sqlite uncomment this
      # and remove all DB_MYSQL_* lines above
      # DB_SQLITE_FILE: "/data/database.sqlite"
      # Uncomment this if IPv6 is not enabled on your host
      # DISABLE_IPV6: 'true'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
    depends_on:
      - db
  db:
    image: 'jc21/mariadb-aria:latest'
    restart: always
    environment:
      MYSQL_ROOT_PASSWORD: 'npm'
      MYSQL_DATABASE: 'npm'
      MYSQL_USER: 'npm'
      MYSQL_PASSWORD: 'npm'
    volumes:
      - ./data/mysql:/var/lib/mysql

Then i have to execute that?
-> docker-compose up -d ./MY_DOCKER_FILE
Is that correctly?
Thank you very very much for your feedback.

well.. easiest is to make a folder in your home-folder, put the yml file in and then run it from there:
cd ~
mkdir npm
cd npm
nano docker-compose.yml -> fill the content as needed, save the file, exit nano
docker-compose up -d

Thank you very much, works very well!! :-)
Maybe you can add that info to https://nginxproxymanager.com/setup/ , for people they want to install your proxy manager (looks very interesting, will see it when the installation is done) but without docker knownledge (yet).

Another question HERE: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1736


[Bug] User snippets are broken after #2253

https://github.com/OmniSharp/omnisharp-roslyn/pull/2253 Breaks the user snippet experience.

I have the user snippet:
{
	"ConfigureAwait": {
		"scope": "csharp",
		"prefix": "ca",
		"body": [
			".ConfigureAwait(false);",
		],
		"description": "Adds '.ConfigureAwait(false);'"
	},
}

Behavior before 1.37.17-beta.14 (1.37.17-beta.11):

Behavior after 1.37.17-beta.14:

cc: @JoeRobich

@vchirikov I can't reproduce this behavior. One thing I noticed from your very helpful gifs was that you brought up completion with 'ctrl+space' and in the first working example you dismissed it by pressing 'escape' before typing 'ca'. In the second failing example you didn't dismiss the completion popup. Can you try again on latest with the completion popup dismissed?
The completion that I changed it wholly separate from VS Code and its snippet support. OmniSharp-Roslyn has no impact on when custom VS Code snippets are offered or how they are committed.

in the first working example you dismissed it by pressing 'escape' before typing 'ca'

I'm sorry, yep, looks like my fault, you're right
Sorry for bother you. 🙏


Added navbar

Added a navbar to the top of the page. Currently has two options: "Home", which leads to the home page and "Discord server", which leads to the osu!lv server invite link

We need a nice latvian/osu! related color scheme across the whole page!
I LOVE the base color you picked! ❤
Please do yourself a favor and Google how to generate one, as a completely white background looks REALLY out of place (a white accent tone would be cool) at the moment.
Another NECCESARY thing without which I won't approve your PR with is having rounded corners are the bottom corners of the navbar, to make it look neat!
An optional thing you can do is make the navbar span across the whole viewport - by that I mean, keep the current button location, just "extend" it with a different color, if you know what I mean.
If you don't get what I mean ask HERE and not in Discord.
If you fix all of this, mark this issue as Pending if possible and do a new commit on the same branch!
I'll get back to you when I can - I won't go easy on you. :)

We need a nice latvian/osu! related color scheme across the whole page! I LOVE the base color you picked! ❤ Please do yourself a favor and Google how to generate one, as a completely white background looks REALLY out of place (a white accent tone would be cool) at the moment. Another NECCESARY thing without which I won't approve your PR with is having rounded corners are the bottom corners of the navbar, to make it look neat!
An optional thing you can do is make the navbar span across the whole viewport - by that I mean, keep the current button location, just "extend" it with a different color, if you know what I mean. If you don't get what I mean ask HERE and not in Discord.
If you fix all of this, mark this issue as Pending if possible and do a new commit on the same branch! I'll get back to you when I can - I won't go easy on you. :)

Rounded the bottom corners of the navbar and added a darker red background colour.

Some code indentation is no bueno.
"Home" url should be relative, otherwise when testing locally link redirects to production environment.

Gonna fix both problems after merge, because YOLO

I really dislike the choice of BG color, it should be white/red-ish, something close to latvian flag colors.
Anyhow, I am going on a break for holidays, however - do not expect me to let this slide if you decide to let me be a "required" reviewer for this project.
Up to you.

I really dislike the choice of BG color, it should be white/red-ish, something close to latvian flag colors. Anyhow, I am going on a break for holidays, however - do not expect me to let this slide if you decide to let me be a "required" reviewer for this project.
Up to you.

Feel free to change the colour to whatever you feel is more appropriate yourself


Is  that any way to set the node priority  as it do in the admin api?

Issue description
the function is  like  the nginx  config:
upstream server_tomcat1 {
server <IP_ADDRESS>:9001 weight=1 max_fails=5  fail_timeout=60s;
server <IP_ADDRESS>:9010 weight=1  max_fails=5  fail_timeout=60s backup;
}
And  the apisix  admin api doc  like below:
https://apisix.apache.org/docs/apisix/admin-api
Note:
Each node can be configured with a priority. A node with low priority will only be used when all the nodes with higher priority have been tried or are unavailable.
As the default priority is 0, nodes with negative priority can be configured as a backup.
For example:
{
"uri": "/hello",
"upstream": {
"type": "roundrobin",
"nodes": [
{ "host": "<IP_ADDRESS>", "port": 1980, "weight": 2000 },
{ "host": "<IP_ADDRESS>", "port": 1981, "weight": 1, "priority": -1 }
],
"checks": {
"active": {
"http_path": "/status",
"healthy": {
"interval": 1,
"successes": 1
},
"unhealthy": {
"interval": 1,
"http_failures": 1
}
}
}
}
}
Node <IP_ADDRESS> will be used only after <IP_ADDRESS> is tried or unavailable. It can therefore act as a backup for the node <IP_ADDRESS>.
Environment

your apisix-ingress-controller version (output of apisix-ingress-controller version --long):
your Kubernetes cluster version (output of kubectl version):
if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):
v1.4.0

In fact in Kubernetes, our backends are Pods, and they don't actually make any difference.
But we do have a way to do what you need (if you really need it)
You can use subset to achieve this. Please refer to https://github.com/apache/apisix-ingress-controller/blob/master/test/e2e/features/subset.go

ok， I will try it later  thanks.

@tao12345666333 APISIX's subsets is very similar to Istio, it's a nice feature, but I wondering how to make a service's subset as a backup.
According to the docs https://github.com/apache/apisix-ingress-controller/blob/master/docs/en/latest/references/apisix_route_v2.md, it seems that only subset's weight can be modified via http[].backends[].weight, and there is no way to set subset's priority to -1.

@ryan4yin refer to https://github.com/apache/apisix-ingress-controller/tree/master/test/e2e/suite-features
The subset case


Using "q" to close the notes.

Would be awesome to have a faster way to close the notes, like pressing "q" to save and close the notes

Personally :wq is ingrained into my muscle memory so I didn't see a need to add any special window management.
That said, this plugin has gotten more attention than I thought it would so I may take the time to "pretty up" the plugin. Things like configuration and probably some better window management for the popup.

Added 'q' to quit, as well as some basic window configuration. Closing issue.


Fix performance regression.

https://github.com/flutter/flutter/pull/110230#issuecomment-1245680854

LGTM. Will need a test exemption from @Hixie

I updated the tests too. So, no exemption is needed.


Simple spacing between item when flexWrap="wrap"?

Hi, im trying have a simple wrap layout

and I need to items to be spaced apart by sa certain value lets say 8dp. I might be blind but there is no way to achieve this?
I tried to workaround with a divider which only has size
<?xml version="1.0" encoding="utf-8"?>
<shape xmlns:android="http://schemas.android.com/apk/res/android">
    <size
        android:width="8dp"
        android:height="8dp" />
</shape>

This almost works, however has a side effect (bug?) where it makes items grow in height instead of putting them on a new line
Simply putting margins on each item manually wont work for me since Im adding views programatically and simply adding margins would cause doubling of inbetween margin; so I would need to figure out my its position and adjust with half margins accordingly. I believe this is layout's responsibility.
Thanks

Did you find any solution?

Adding the items programmatically can be a little persnickety. If you can get away with just setting top and right margin on all items, then this can get you there. Android removes any margins when you add a view like, so you have to programmatically set margin after you add the item to the layout.
    tags.forEachIndexed { index, tagText ->
      val view = itemView.context.layoutInflater.inflate(R.layout.tag, null)
      view.tag.text = tagText

      // add view
      flexBoxTagLayout.addView(view)

      // set margins after the fact
      (view?.layoutParams as? ViewGroup.MarginLayoutParams)?.updateMargins(
        top = itemView.context.resources.getDimensionPixelSize(R.dimen.tag_spacing),
        right = itemView.context.resources.getDimensionPixelSize(R.dimen.tag_spacing) else 0
      )
    }

Thanks, @yehezkiell! Also you can change orientation to setOrientation(FlexboxItemDecoration.BOTH).


add strverscmp function

This code seems to originate from GNU C library which is licensed under LGPL.  Dirent uses MIT license which is incompatible.  Dirent should be re-licensed if this PR is to be accepted!

There is an alternative contained within Musl library which I think is MIT licensed

Thanks for the info!  The version in Musl library is really compact!
I decided to implement my own version of strverscmp().  It it not so compact but at least I can understand what goes on.


refactor(v2): improve regex matching code-block title

Motivation
Sort+quick code
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
I create simple benchmark:
const str = 'something include title="...."';

const oldRegex = /title=".*"/;
const newRegex = /(?<=title=").*(?=")/;

const old = (str) => str.match(oldRegex)[0].split('title=')[1].replace(/"+/g, '');
const newF = (str) => str.match(newRegex)[0];

result: two function return same value

sort str:

old x 2,411,252 ops/sec ±0.38% (90 runs sampled)
newF x 12,002,531 ops/sec ±0.44% (92 runs sampled)

long str:

old x 1,569,985 ops/sec ±0.44% (92 runs sampled)
newF x 3,442,088 ops/sec ±0.43% (91 runs sampled)

Thanks, that seems to work fine so let's merge

this was reverted because it does not work on Safari


Compile errors when building on mac

Describe the bug
I've been trying to build on mac for the past few hours, worked through a few bugs to get further in the script I'll outline below but couldn't get to a green build:
To reproduce
brew install c-ares # only thing I didn't already have it needed

git clone https://github.com/nginx/nginx.git
git clone https://github.com/nginxinc/nginx-otel.git

cd nginx
auto/configure --with-compat

cd ../nginx-otel
mkdir build && cd build
cmake -DNGX_OTEL_NGINX_BUILD_DIR=$(pwd)/../../nginx/objs ..
make

Error 1 (cmake line)
Targets not yet defined: absl::nullability, absl::prefetch, absl::common_policy_traits, absl::node_slot_policy...

To fix, I added find_package(absl CONFIG REQUIRED) to line 4 of CMakeLists.txt.
Error 2 (make line)
/tmp/nginx-otel/build/_deps/grpc-src/include/grpcpp/impl/codegen/security/auth_context.h:40:19: error: 'iterator<std::input_iterator_tag, const std::pair<grpc::string_ref, grpc::string_ref>>' is deprecated [-Werror,-Wdeprecated-declarations]

To fix, I commented out line 105 in CMakeLists.txt to disable warnings (add_compile_options(-Wall -Wtype-limits -Werror))
Error 3 unsolved (make line)
[100%] Linking CXX shared module ngx_otel_module.so
ld: Undefined symbols:
  _ngx_array_push, referenced from:
      (anonymous namespace)::initModule(ngx_conf_s*) in http_module.cpp.o
      (anonymous namespace)::initModule(ngx_conf_s*) in http_module.cpp.o
      (anonymous namespace)::addSpanAttr(ngx_conf_s*, ngx_command_s*, void*) in http_module.cpp.o
  _ngx_cached_time, referenced from:
      (anonymous namespace)::onRequestEnd(ngx_http_request_s*) in http_module.cpp.o
  _ngx_conf_log_error, referenced from:
      (anonymous namespace)::mergeLocationConf(ngx_conf_s*, void*, void*) in http_module.cpp.o
      (anonymous namespace)::setExporter(ngx_conf_s*, ngx_command_s*, void*) in http_module.cpp.o
      (anonymous namespace)::setExporter(ngx_conf_s*, ngx_command_s*, void*)::$_2::__invoke(ngx_conf_s*, ngx_command_s*, void*) in http_module.cpp.o
  _ngx_conf_parse, referenced from:
      (anonymous namespace)::setExporter(ngx_conf_s*, ngx_command_s*, void*) in http_module.cpp.o
  _ngx_conf_set_enum_slot, referenced from:
      (anonymous namespace)::gCommands in http_module.cpp.o
  _ngx_conf_set_msec_slot, referenced from:
      (anonymous namespace)::gExporterCommands in http_module.cpp.o
  _ngx_conf_set_size_slot, referenced from:
      (anonymous namespace)::gExporterCommands in http_module.cpp.o
      (anonymous namespace)::gExporterCommands in http_module.cpp.o
  _ngx_conf_set_str_slot, referenced from:
      (anonymous namespace)::gCommands in http_module.cpp.o
      (anonymous namespace)::gExporterCommands in http_module.cpp.o
  _ngx_connection_local_sockaddr, referenced from:
      (anonymous namespace)::onRequestEnd(ngx_http_request_s*) in http_module.cpp.o
  _ngx_current_msec, referenced from:
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*) in http_module.cpp.o
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*)::$_3::__invoke(ngx_event_s*) in http_module.cpp.o
  _ngx_cycle, referenced from:
      (anonymous namespace)::grpcLogHandler(gpr_log_func_args*) in http_module.cpp.o
      (anonymous namespace)::protobufLogHandler(google::protobuf::LogLevel, char const*, int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) in http_module.cpp.o
      BatchExporter::sendBatch(opentelemetry::proto::collector::trace::v1::ExportTraceServiceRequest&)::'lambda'(opentelemetry::proto::collector::trace::v1::ExportTraceServiceRequest, opentelemetry::proto::collector::trace::v1::ExportTraceServiceResponse, grpc::Status)::operator()(opentelemetry::proto::collector::trace::v1::ExportTraceServiceRequest, opentelemetry::proto::collector::trace::v1::ExportTraceServiceResponse, grpc::Status) const in http_module.cpp.o
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*)::$_3::__invoke(ngx_event_s*) in http_module.cpp.o
  _ngx_event_timer_rbtree, referenced from:
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*) in http_module.cpp.o
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*) in http_module.cpp.o
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*)::$_3::__invoke(ngx_event_s*) in http_module.cpp.o
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*)::$_3::__invoke(ngx_event_s*) in http_module.cpp.o
  _ngx_hash_find, referenced from:
      (anonymous namespace)::setHeader(ngx_http_request_s*, opentelemetry::v1::nostd::string_view, opentelemetry::v1::nostd::string_view) in http_module.cpp.o
  _ngx_hash_key, referenced from:
      (anonymous namespace)::ensureOtelCtx(ngx_http_request_s*) in http_module.cpp.o
      (anonymous namespace)::ensureOtelCtx(ngx_http_request_s*) in http_module.cpp.o
      (anonymous namespace)::setHeader(ngx_http_request_s*, opentelemetry::v1::nostd::string_view, opentelemetry::v1::nostd::string_view) in http_module.cpp.o
  _ngx_http_add_variable, referenced from:
      (anonymous namespace)::addVariables(ngx_conf_s*) in http_module.cpp.o
      (anonymous namespace)::addVariables(ngx_conf_s*) in http_module.cpp.o
      (anonymous namespace)::addVariables(ngx_conf_s*) in http_module.cpp.o
      (anonymous namespace)::addVariables(ngx_conf_s*) in http_module.cpp.o
  _ngx_http_compile_complex_value, referenced from:
      (anonymous namespace)::addSpanAttr(ngx_conf_s*, ngx_command_s*, void*) in http_module.cpp.o
  _ngx_http_complex_value, referenced from:
      (anonymous namespace)::onRequestStart(ngx_http_request_s*) in http_module.cpp.o
      (anonymous namespace)::onRequestEnd(ngx_http_request_s*) in http_module.cpp.o
      (anonymous namespace)::onRequestEnd(ngx_http_request_s*) in http_module.cpp.o
  _ngx_http_core_module, referenced from:
      (anonymous namespace)::initModule(ngx_conf_s*) in http_module.cpp.o
      (anonymous namespace)::onRequestEnd(ngx_http_request_s*) in http_module.cpp.o
      (anonymous namespace)::setHeader(ngx_http_request_s*, opentelemetry::v1::nostd::string_view, opentelemetry::v1::nostd::string_view) in http_module.cpp.o
  _ngx_http_module, referenced from:
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*) in http_module.cpp.o
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*)::$_3::__invoke(ngx_event_s*) in http_module.cpp.o
  _ngx_http_set_complex_value_slot, referenced from:
      (anonymous namespace)::gCommands in http_module.cpp.o
      (anonymous namespace)::gCommands in http_module.cpp.o
  _ngx_inet_get_port, referenced from:
      (anonymous namespace)::onRequestEnd(ngx_http_request_s*) in http_module.cpp.o
      (anonymous namespace)::onRequestEnd(ngx_http_request_s*) in http_module.cpp.o
  _ngx_list_push, referenced from:
      (anonymous namespace)::setHeader(ngx_http_request_s*, opentelemetry::v1::nostd::string_view, opentelemetry::v1::nostd::string_view) in http_module.cpp.o
  _ngx_log_error_core, referenced from:
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*) in http_module.cpp.o
      (anonymous namespace)::exitWorkerProcess(ngx_cycle_s*) in http_module.cpp.o
      (anonymous namespace)::onRequestEnd(ngx_http_request_s*) in http_module.cpp.o
      (anonymous namespace)::onRequestEnd(ngx_http_request_s*) in http_module.cpp.o
      (anonymous namespace)::grpcLogHandler(gpr_log_func_args*) in http_module.cpp.o
      (anonymous namespace)::protobufLogHandler(google::protobuf::LogLevel, char const*, int, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) in http_module.cpp.o
      BatchExporter::sendBatch(opentelemetry::proto::collector::trace::v1::ExportTraceServiceRequest&)::'lambda'(opentelemetry::proto::collector::trace::v1::ExportTraceServiceRequest, opentelemetry::proto::collector::trace::v1::ExportTraceServiceResponse, grpc::Status)::operator()(opentelemetry::proto::collector::trace::v1::ExportTraceServiceRequest, opentelemetry::proto::collector::trace::v1::ExportTraceServiceResponse, grpc::Status) const in http_module.cpp.o
      ...
  _ngx_palloc, referenced from:
      (anonymous namespace)::setHeader(ngx_http_request_s*, opentelemetry::v1::nostd::string_view, opentelemetry::v1::nostd::string_view) in http_module.cpp.o
      (anonymous namespace)::addSpanAttr(ngx_conf_s*, ngx_command_s*, void*) in http_module.cpp.o
  _ngx_pcalloc, referenced from:
      (anonymous namespace)::createMainConf(ngx_conf_s*) in http_module.cpp.o
      (anonymous namespace)::createLocationConf(ngx_conf_s*) in http_module.cpp.o
  _ngx_pnalloc, referenced from:
      long (anonymous namespace)::hexIdVar<opentelemetry::v1::trace::TraceId>(ngx_http_request_s*, ngx_variable_value_t*, unsigned long) in http_module.cpp.o
      long (anonymous namespace)::hexIdVar<opentelemetry::v1::trace::SpanId>(ngx_http_request_s*, ngx_variable_value_t*, unsigned long) in http_module.cpp.o
      (anonymous namespace)::onRequestStart(ngx_http_request_s*) in http_module.cpp.o
  _ngx_pool_cleanup_add, referenced from:
      (anonymous namespace)::ensureOtelCtx(ngx_http_request_s*) in http_module.cpp.o
  _ngx_rbtree_delete, referenced from:
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*) in http_module.cpp.o
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*)::$_3::__invoke(ngx_event_s*) in http_module.cpp.o
  _ngx_rbtree_insert, referenced from:
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*) in http_module.cpp.o
      (anonymous namespace)::initWorkerProcess(ngx_cycle_s*)::$_3::__invoke(ngx_event_s*) in http_module.cpp.o
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [ngx_otel_module.so] Error 1
make[1]: *** [CMakeFiles/ngx_otel_module.dir/all] Error 2
make: *** [all] Error 2

Wasn't able to get passed this one, any ideas?
Expected behavior
Being possible to compile on Mac.
Your environment

Version/release of this project or specific commit: aac5678defd4a704d7fff216244755a8c9d33d8d
Target deployment platform: Mac M2 Sonama 14.1

Thanks!

I'd guess that something like target_link_options(ngx_otel_module PRIVATE -undefined dynamic_lookup) could help. Though, this module was never intended to be used on Mac.

@p-pautov thankyou! This actually worked!
With my first 2 changes, and your suggestion added after the add_library(ngx_otel_module MODULE ...) around line 105, compilation succeeded and I've verified it actually works in nginx on my mac.
Shall I PR with those 3 changes to the build script?
Thanks again.

It's not very clear what is causing the first error, but I don't think we should require abseil in default build. If you have it already on the system, perhaps, you should build with "-D NGX_OTEL_FETCH_DEPS=OFF" and get all the dependencies from the system.
We have some work in progress, which might lead to removal of -Werror flag. I'll update this issue when it's done.
I wonder if you can set "dynamic_lookup" via cmake, e.g. with "-D LINK_OPTIONS=-undefined dynamic_lookup"? Though, it might be worth having it in "CMakeLists.txt" if there is demand for Mac build.
What's your use case for building the module on Mac?

Error 1:
-D NGX_OTEL_FETCH_DEPS=OFF doesn't work very well, I then get an error relating to needing opentelemetry-cpp, I had a look at installing that but looks like a more complicated solution than just adding find_package(absl CONFIG REQUIRED) in my original solution!
CMake Error at CMakeLists.txt:64 (find_package):
  By not providing "Findopentelemetry-cpp.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "opentelemetry-cpp", but CMake did not find one.

  Could not find a package configuration file provided by "opentelemetry-cpp"
  with any of the following names:

    opentelemetry-cppConfig.cmake
    opentelemetry-cpp-config.cmake

  Add the installation prefix of "opentelemetry-cpp" to CMAKE_PREFIX_PATH or
  set "opentelemetry-cpp_DIR" to a directory containing one of the above
  files.  If "opentelemetry-cpp" provides a separate development package or
  SDK, be sure it has been installed.

Error 3:
-D LINK_OPTIONS="-undefined dynamic_lookup" doesn't work either, same errors as before your previous fix!

What's your use case for building the module on Mac?

Simply dev builds, nginx used in foreground in front of upstream services during development, otlp too.
Docker isn't an option for various reasons.
https://github.com/denji/homebrew-nginx seemds to be the defacto way to get additional modules on mac nginx builds, I think for them to add nginx-otel they'd need a script like this to work.


Improve robustness of automatic installation of Python modules via Conda.jl

fixes #7
cc @pfitzseb

@pfitzseb: I finally found the rabbit in the rabbit hole. The automatic installation works now also in the case that did not work before for me. Would you mind trying again on your system?

Codecov Report

Merging #90 (8dc4c5d) into main (b92dcc2) will decrease coverage by 1.58%.
The diff coverage is 33.33%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #90      +/-   ##
==========================================
- Coverage   72.09%   70.52%   -1.58%
==========================================
  Files          17       16       -1
  Lines        1050     1011      -39
==========================================
- Hits          757      713      -44
- Misses        293      298       +5

Impacted Files
Coverage Δ

src/Commands/Keyboard.jl
73.38% <ø> (-0.40%)
:arrow_down:

src/Commands/Mouse.jl
41.66% <ø> (-4.49%)
:arrow_down:

src/shared.jl
70.00% <33.33%> (-14.75%)
:arrow_down:

... and 7 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

This works fine for me.

This works fine for me.

Thanks for testing!


Provide a meaning to "MRAA"

Hi,
as follow up from the discussion on Twitter https://twitter.com/mulpat/status/658258093709635584
It might be nice to get some more meaning into "MRAA".
"Modules" for "wRapping" "hArdware" "Abstractions" maybe?

And why MAA was renamed to MRAA +1:

Check #109. The rename from maa was because there was already a libmaa http://sourceforge.net/projects/dict/files/libmaa/libmaa-1.3.2/.
I'll leave this open so you the bike shedding can stay here, but sorry there isn't much reason behind the name... If you buy me a beer I'm happy to have lengthy discussions in persob about my disregard for project naming :)

Hm... MRAA Beer Party.... sounds good :)

Interesting to hear the very radical approach to project naming :)
I just know that Arduino was apparently based on the bar where the folks met in Ivrea: https://www.quora.com/Where-is-the-Arduino-bar
For sure, MRAA looks interesting as it provides the needed hardware abstraction layer on somewhat different components with different pins.

in the comments on this hackaday article on Arduino is the idea of "HALAL" for Arduino - hardware abstraction layer abstraction layer.... http://hackaday.com/2015/10/20/the-case-for-arduino-in-real-engineering/

This can be closed : "monkeys really are awesome"
in own @arfoll  words at #IOTWTB
http://iot.withthebest.com/


Add symbol name for narrow non-breaking space

Use symbol name sym.space.nobreak.narrow for Unicode codepoint U+202F.
Also add some test for non-breaking characters while being at it.
Closes #3197.

Thanks!


Open browser after starting server

Call webbrowser.open(...) on startup - should be able to disable this. Also need to make sure to wait until after we are listening.

What are the prerequisite required to solve this issue ?

What are the prerequisite required to solve this issue ?

Basically, you need to figure out how to integrate the webbrowser.open call into the command line interface at the right place, such that the web browser opens at the right time. You may also want to look at the main and run functions of libertem.server - that's likely the right place for integration.
As there should be an option to disable this functionality (for example, because you are running the libertem-server on a headless system, that is, one without a GUI system running), there should also be a command line option to disable this behavior.
Let me know if this clears things up for you!

Explanation is pretty clear . So when we start server by $libertem-server it should open web browser by default. There should be also option to disable it.

Closed with #580
Many thanks @twentyse7en !


Timeline inconsistent

Problem
The timeline is either not visible or takes very little space or too much. Maybe possible to let it cover the given space even if it is a short interval or a long interval?
Browser: Safari, Chrome
Analysis 1: Timeline not visible
Spread link: https://view.spreadviz.org/?output=94d05c76-0585-43f9-99d8-9e13973ebba0/f97a0171-7836-4f7c-8dc0-d4eeef938d21.json&maps=DK,FR,RU,BE,UK,PT,SE

Files: SARS-CoV-2discrete.zip
Analysis 2: Timeline takes up very little space
Spread link: https://view.spreadviz.org/?output=ddf9ff80-334a-475d-8cdd-901925a32877/f755822e-7743-4e97-ad71-d7f3303bae88.json&maps=GH,BF,GN,SL,TG

Files: chiefdom_ebola.zip
Analysis 3: Timeline takes more space than previous but still does not cover up the whole area
Spread link: https://view.spreadviz.org/?output=ddf9ff80-334a-475d-8cdd-901925a32877/b6cce491-3fc3-4725-9fd8-a0e56b5afa19.json&maps=RU,MX,US,BS,CA

Files: wnv.zip
Analysis 4: Timeline goes outside the given box
Spread link: https://view.spreadviz.org/?output=ddf9ff80-334a-475d-8cdd-901925a32877/9fe1c695-e1ff-441d-9dc0-9c23441c873b.json&maps=GH,NG,CM,BF,GN,SL,ML

@jpmonettas could we just make it occuppy the entire availiable space?

This PR (https://github.com/fbielejec/spread/pull/188) redesigns the timeline controls at the bottom. It will use the entire length to draw the timeline.
Big timelines will show like :

While very short timelines (under a year) like :

Since we are only labeling year marks, that last case when everything happens under a year will show unlabeled


Update dependencies

Summary

Description

Motivation and Context

Todos

[x] Implemented feature
[ ] Feature with pending implementation

Screenshots (if appropriate):

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Disable google places auto complete scroll

Details

Google places auto complete use VirtualizedList internally but always show maximum of 5 items. It is not scrollable on another platform except for iOS. So, we want to disable the scroll capability to make it consistent with other platforms.
Fixed Issues

$ https://github.com/Expensify/App/issues/14312
PROPOSAL: https://github.com/Expensify/App/issues/14312#issuecomment-1396451746
Tests

Go to Workspace => Connect Bank Account => Connect Manually => Enter valid information for first 2 steps.
At step 3, tap on Personal Address, type some text to make the auto complete address dropdown appears, try to scroll inside the dropdown
Verify the whole page is scrolled, not the dropdown

[x] Verify that no errors appear in the JS console

Offline tests

Go to Workspace => Connect Bank Account => Connect Manually => Enter valid information for first 2 steps.
At step 3, tap on Personal Address, type some text to make the auto complete address dropdown appears, try to scroll inside the dropdown
Verify the whole page is scrolled, not the dropdown

QA Steps

Go to Workspace => Connect Bank Account => Connect Manually => Enter valid information for first 2 steps.
At step 3, tap on Personal Address, type some text to make the auto complete address dropdown appears, try to scroll inside the dropdown
Verify the whole page is scrolled, not the dropdown

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://user-images.githubusercontent.com/50919443/214486055-b2803e66-644b-422a-8de9-6e1328320b14.mov

Mobile Web - Chrome

https://user-images.githubusercontent.com/50919443/214486074-f1081ac6-2d23-4086-a4e2-3620784a7844.mp4

Mobile Web - Safari

https://user-images.githubusercontent.com/50919443/214486088-b0272c48-3c4a-4a4d-9717-44735110bdfa.mov

Desktop

https://user-images.githubusercontent.com/50919443/214486098-50051a38-6a31-499a-96fe-ec583912dcd6.mov

iOS

https://user-images.githubusercontent.com/50919443/214486110-423aad0e-288b-4fe6-8bec-c4e4ae6088ef.mov

Android

https://user-images.githubusercontent.com/50919443/214486120-4a4d4e13-e849-474a-86f0-7d5bf004c524.mp4

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by https://github.com/luacmartins in version: 1.2.60-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


[TASK-62] Added HabitActivity Component

made habitactivity, also fixed some darkmode stuff for the header and tab

Gotta figure out a way to pass icons as props, also did not do the friends thing, me sleepy, zzzzz

Summary by CodeRabbit

New Features

Added a HabitActivity component to visualize habit tracking data in a grid format with interactive elements.
Introduced a function in mockHabitData.ts to generate mock completion data for habit tracking.

Enhancements

Updated the HabitsTab component to render a specific HabitActivity with interactive elements.
Adjusted the TabLayout component to dynamically change color schemes based on the selected theme.
Enhanced the SettingsTab background colors for improved visibility in different modes.

also fixed the border thing in settings, and changed the colors to match the dark mode figma

Notes for future:

Split into components to make code more readable and reusable
Use hooks so that it's less work to do data fetching in the future
Don't use the any type, actually define types

i was gonna replace the any, but I forgot 💀


Migrations: migrate (s)css automatically

In Version 5, some CSS classes and SCSS variables have changed.
It is therefore necessary to write migration schematics so that these classes and variables are updated automatically.

Still relevant, but not a priority.

@alizedebray if you could create a tasklist which defines in detail what to do or how to find out what to do, that would be great!

In the future, we will need to think about how we can provide migrations to non-angular projects. Not sure if this is a good place to start, but just as an info.

Closing as no longer relevant (after 2 years)


Registrator and overlay network

Hi,
Docker v1.9.1
Registrator latest version
Registrator is not identifying containers & services running on overlay network.
Please can someone confirm what needs to be done to get registrator to identify those containers running in overlay?
Thanks

I wonder if there is any interest by the project maintainers to support the service discovery of services that do not expose a port to the host and are located within their separate network (i.e. overlay or pure level 3 virtual networking)?
Looking at the source code I have the impression that Registrator would need some major rework but believe this could be worthwhile.


Documentation for clone

Am I correct if I say that the "-c" argument of "clone" should be removed?
Don't see anything in the code referring to any "-c" argument.

Yes, that is correct. It was there as a band-aid from long ago but can be ripped off now.