[internal] Update acceptance tests to ensure randomisation

Self merging as this is required to launch the provider


fix: fixed display of link for config without aqua-server

Closes #203

Required cases for manual testing

[ ] Legacy Slack without url
[ ] Legacy Slack with url
[ ] Legacy Email with url
[ ] Legacy Email without  url

[ ] Rego Slack without url
[ ] Rego Slack with url
[ ] Rego Email with url
[ ] Rego Email without  url

[ ] Oversized message for Slack without url
[ ] Oversized message for Slack with url
[ ] Oversized message for Teams without url
[ ] Oversized message for Teams with url

for last ones you can temporary reduce hard-coded limit in outputs

I checked all cases. Everything works correctly.

I assume these are already covered as unit tests somewhere? Just curious why they need to be manual or maybe I misunderstood something.
We don't have unit tests for these outputs now. Therefore, manual testing was used.


Unable to checkout on Windows

When trying to checkout the code on a windows machine via
git clone git@github.com:confidential-containers/cloud-api-adaptor.git

it fails with
error: invalid path 'podvm/files/etc/systemd/system/multi-user.target.wants/run-kata\x2dcontainers.mount'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

Hi @RedCarsten is it possible for you to use WSL for now? I think there will be quite a few parts of this repo that won't work directly on windows

The backslash in the filename is throwing it off:
https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file

Hi @RedCarsten is it possible for you to use WSL for now? I think there will be quite a few parts of this repo that won't work directly on windows

Yes, as a workaround I can use WSL


Optimize orderStatus as storage pointer

Optimize orderStatus to be a storage pointer instead of copying to memory in order to save gas.
Motivation
orderStatus is mainly being passed around in memory whereas it can directly
be read from storage, reducing gas costs.
Additionally, by caching the storage pointer some gas can be saved.
Solution
Change
OrderStatus memory orderStatus = _orderStatus[orderHash];

to
OrderStatus storage orderStatus  = _orderStatus[orderHash];

Note: also saw that FulfillmentComponent memory targetComponent could be changed to calldata
And should probably adapt reference implementation as well..

There's a lot of potentially valuable stuff in this PR, but there are also sections that may actually increase gas (for example, _verifyOrderStatus takes orderHash as an argument and so this might actually trigger reading it from memory unless the memory declaration on the argument handles the read upfront, need to validate that). Can you break this PR up into a few smaller ones so we can evaluate each change in isolation?

Alright, focused this on only the storage optimization.
_verifyOrderStatus only uses orderHash for revert messages. Not sure what exactly you mean by "trigger reading it from memory". I also changed the parameter type to storage in _verifyOrderStatus.


Need to mention that this supports only v2 storage accounts!

please add mention that private endpoints only work on v2 accounts.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1d6cc016-6c8f-81d7-3b5b-edce932294cf
Version Independent ID: 619d6b5e-ea75-61dd-5ef4-f653f9822cb8
Content: Use private endpoints - Azure Storage
Content Source: articles/storage/common/storage-private-endpoints.md
Service: storage
Sub-service: common
GitHub Login: @santoshc
Microsoft Alias: santoshc

@javester Thanks for your question. We are checking on this and will respond to you soon.

@javester The PR has been merged. We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Support float data when saving textures with array slice remapping

Description
Whenever I save an texture from the Texture Viewer as EXR, exporting all slices, the half floats that get saved to the file do not match the values I see from the raw buffer viewer. Furthermore reopening the EXR in RenderDoc or other image applications shows that all dark colors seem to be quantized. If I try to save only a single slice then the half floats are saved properly and colors are smooth.
I also tested saving and reopening with the HDR format and the issue is also present there.
Repro steps
View a texture of type R16G16B16A16 with multiple samples/slices
Save it as an EXR or HDR file with 'Export All Slices' checked
Environment

RenderDoc build: tested in both v1.1 and c9c51b5a

Operating System: Windows 7

API: D3D11

GPU: GTX 1050 Ti

Driver Version: 398.82

Can you share a concrete repro case? I tried this on a capture I had and the EXR was saved accurately. Does it only happen on subnormal values maybe?

Scratch that, I repro'd the bug just after posting - whoops.
Saving multiple slices to a format like EXR/HDR requires manual stitching to put it into a grid, and that manual stitching code only works with RGBA8 data, so it gets quantised for that process.
I should be able to write a separate path for HDR data, but I'd suggest if you want precise results you're better off saving to DDS which natively supports arrays and can just blit out the data without processing.

Ahh, I wasn't aware that DDS would also work for this, it's even much simpler and easier to parse than the mess that is EXR. Thank you.

Yeh I'd say DDS is definitely the better format if you can use it - it supports arrays, mips, and most resource formats that APIs use including block compressed etc, and the format is simple. The main reason to go for HDR/EXR is if you need interop with other tools.

I've changed the (very simple) image processing code to upcast to RGBA 32-float data when outputting to a format that supports higher than 8bpp, that should now prevent any banding/compression issues.
I'd still recommend using DDS if you can and avoiding any of the remapping entirely, because with DDS the image data is read straight out of memory and written to disk without any change.


Angular-dragdrop doesn't work with newer jQuery Versions (3.1.0)

draganddrop.js:28 Uncaught TypeError: Cannot read property 'indexOf' of undefined

+1


Warnings when used with @vue/test-utils v2.0.0-rc.4.

Reproduction
After upgrading to<EMAIL_ADDRESS>tests pass but with warnings about RouterView and RouterLink components having already been registered.
Steps to reproduce the behavior
Dependencies:

"vue-router-mock": "0.0.2"
"@vue/test-utils": "2.0.0-rc.4"

Config (in Jest setup file):
import { config } from '@vue/test-utils';
import {
  createRouterMock,
  injectRouterMock,
  VueRouterMock,
} from 'vue-router-mock';

const router = createRouterMock();
config.plugins.VueWrapper.install(VueRouterMock);

beforeEach(() => {
  injectRouterMock(router);
});

Expected behavior
Tests pass with no warnings.
Actual behavior
Tests pass, with warnings:
    console.warn
      [Vue warn]: Component "RouterView" has already been registered in target app.

      45 |
      46 |   it('passes', async () => {
    > 47 |     const { findByText } = render(MyComponent, {
         |                            ^
      48 |       props: { id: 'test' },

      at warn (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:40:17)
      at Object.component (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:3050:21)
      at mount (node_modules/@vue/test-utils/dist/vue-test-utils.cjs.js:2326:21)
      at render (node_modules/@testing-library/vue/dist/render.js:43:38)
      at Object.<anonymous> (tests/js/components/MyComponent.test.js:47:28)

    console.warn
      [Vue warn]: Component "RouterLink" has already been registered in target app.

      45 |
      46 |   it('passes', async () => {
    > 47 |     const { findByText } = render(MyComponent, {
         |                            ^
      48 |       props: { id: 'test' },

      at warn (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:40:17)
      at Object.component (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:3050:21)
      at mount (node_modules/@vue/test-utils/dist/vue-test-utils.cjs.js:2326:21)
      at render (node_modules/@testing-library/vue/dist/render.js:43:38)
      at Object.<anonymous> (tests/js/components/MyComponent.test.js:47:28)

Probably introduced by https://github.com/vuejs/vue-test-utils-next/pull/438
Seems to still work but it shouldn't warn. I will take a look

Will be fixed in the next vue-test-utils release!


Review word Flux Patter --> Flux Pattern

Correct word in README.md

thank you, it's already fixed here #30


error with downloading brotli[core]:x86-windows

Disclaimer: English is not my first language, so I'm sorry for any mistakes
Description
While downloading any package depending on brotli vcpkg gives the following error:
`"Couldn't connect to server"
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:181 (message):

Failed to download file. If you use a proxy, please set the HTTPS_PROXY and HTTP_PROXY environment variables to "https://user:password@your-proxy-ip-address:port/". Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues
Call Stack (most recent call first):
scripts/cmake/vcpkg_find_acquire_program.cmake:438 (vcpkg_download_distfile)
scripts/cmake/vcpkg_fixup_pkgconfig.cmake:270 (vcpkg_find_acquire_program)
ports/brotli/portfile.cmake:25 (vcpkg_fixup_pkgconfig)
scripts/ports.cmake:79 (include)

Error: Building package brotli:x86-windows failed with: BUILD_FAILED

Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: brotli:x86-windows
Vcpkg version: 2020.06.15-nohash
Additionally, attach any relevant sections from the log files above.
`

Environment

OS: Windows 10 1909

To Reproduce
Steps to reproduce the behavior:
./vcpkg install brotli [or any package depending on it, in my case it was qt5]

A quick workaround is to download the files:

https://mirror.yandex.ru/mirrors/msys2/mingw/i686/mingw-w64-i686-pkg-config-0.29.2-1-any.pkg.tar.xz
https://mirror.yandex.ru/mirrors/msys2/mingw/i686/mingw-w64-i686-libwinpthread-git-<IP_ADDRESS>06.c9a21571-1-any.pkg.tar.zst

In the downloads subdirectory of the main vcpkg directory.

Duplicate to #13852.


improvement: add<EMAIL_ADDRESS>support for disableEsLint

<EMAIL_ADDRESS>no longer uses eslint-loader when building. It uses a new plugin ESLintWebpackPlugin.
This PR adds code to remove the ESLintWebpackPlugin plugin to disableEsLint to support<EMAIL_ADDRESS>The code to remove eslint-loader is not touched for backward compatibility.

@CGeorges Could this be released please.

@CGeorges Could this be released please.

Here's a workaround extracted from @Menci 's patch before this can be released.
module.exports = override(
  // ...other overrides
  disableEsLint(),
  (config) => {
    config.plugins = config.plugins.filter(
      (plugin) => plugin.constructor.name !== "ESLintWebpackPlugin",
    );
    return config;
  },
);

FYI<EMAIL_ADDRESS>now allows to directly disable the ESLint plugin.
Just add this in your .env:
DISABLE_ESLINT_PLUGIN=true

See: https://github.com/facebook/create-react-app/pull/10170


v1.2.0 executable seems to have been compiled for Mac OS instead of linux

I was trying to determine why I could only get this error message out of the container:
[dumb-init] /usr/bin/docker-volume-local-persist: Exec format error
So I downloaded the binaries myself and checked them out:
$ curl -L https://github.com/CWSpear/local-persist/releases/download/v1.2.0/local-persist-linux-amd64 -o local-persist-linux-amd64-v1.2.0
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   598    0   598    0     0   3587      0 --:--:-- --:--:-- --:--:--  3646
100 9356k  100 9356k    0     0  2000k      0  0:00:04  0:00:04 --:--:-- 2322k

$ file local-persist-linux-amd64-v1.2.0
local-persist-linux-amd64-v1.2.0: Mach-O 64-bit x86_64 executable

$ curl -L https://github.com/CWSpear/local-persist/releases/download/v1.1.0/local-persist-linux-amd64 -o local-persist-linux-amd64-v1.1.0
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   598    0   598    0     0   2742      0 --:--:-- --:--:-- --:--:--  4068
100 8203k  100 8203k    0     0  2164k      0  0:00:03  0:00:03 --:--:-- 2727k

$ file local-persist-linux-amd64-v1.1.0
local-persist-linux-amd64-v1.1.0: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped

Seems that the v1.2.0 binary won't execute under a Linux kernel.

Yes, my release script automates all this, but for some reason, wasn't setting the right environment and just built the Mac version!
I have fixed the release on GitHub, but for some reason, the Docker version is still giving me trouble. It now says it can't find /usr/bin/local-persist-linux-amd64 even tho it definitely can...

And I did check that I could execute the version on GitHub on Linux. So it's not an issue with the executable itself, but something with the Docker image.

As mentioned, the binary was fixed, and I'm updating the Docker Images, too. None of the source code has changed, but did bump to v1.2.1 just to help those that might be stuck on v1.2.0 (I did update the v1.2.0 image, too, tho).


time_zone attribute of the Site object emits Null if not set.

GET vs PUT/PATCH/POST endpoint for /api/dcim/site/ does not represent the time_zone attribute in the same fashion. GET will represent an unset time_zone as null but attempting to create/edit that field via the API it does not allow for the field to be null only "" or not part fo the payload.
Environment

Python version: 3.7
Nautobot version: develop

Steps to Reproduce

GET to /api/dcim/sites/<UUID>/
Return payload {"name": "Foo", "slug": "foo", "time_zone": null} (omitted for brevity)

Expected Behavior

GET to /api/dcim/sites/<UUID>/
Return payload {"name": "Foo", "slug": "foo", "time_zone": ""} (omitted for brevity)

Observed Behavior
The field within the database does not allow null but allows blank, this can lead to confusion in the API if attempting to POST/PUT/PATCH the same payload back to Nautobot the API will not allow {"time_zone": null}.

I am a comment. Shh


[Arith] Implement statistics counters for RewriteSimplifier

Previously, so long as RewriteSimplifier produces the same output, unit tests of its behavior would pass.  This could have severe performance regressions, such as the one resolved in https://github.com/apache/tvm/pull/14528, which caused the runtime of two test to increase from ~1.5 seconds to ~10 minutes each.
This commit implements statistics counts in RewriteSimplifier, which are exposed through both the C++ and Python APIs, and uses these to guard against the known performance regression from https://github.com/apache/tvm/pull/14528.

One thing that worth thinking about is the relation of simplification and persistence of analyzer. Since we encourage persistence of analyzer in general within a pass, so we should document in max step to encourage users to keep that in mind

Good point on the re-use of the same Analyzer instance.  I've added that in the description of SetMaximumRewriteSteps, that re-use of the same object is necessary in order to have accurate usage counters.


Cannot reuse applications in Marketplace

For example, in PHP 8.1, installing again after the first time will prompt "failed to install". And after the first use, php8.1 cannot be found in the chat list

@beforeProspective Hello!, The use of marketplace agents depends on the type of payment plan you have. If you are on the free plan, you can only have three, including the agent you've created. Additionally, the number of interactions is global, not per agent. If you've already been interacting with your agent, the number of interactions also counts towards those of the Marketplace. If none of these options apply to your situation, please contact us for support at: https://calendly.com/pilar-hidalgo.


Disable empty gzip

Problem:
Responses with no body were being needlessly gzipped. This generated confusion as empty responses had a length greater than zero.
Solution:
Gzip encoding is now only used once a response writer writes to body.
Issue:
https://github.com/rancher/rancher/issues/19553

Small test change, otherwise lgtm

lgtm even after test changes

lgtm


Deprecated(?) ._snippet_grammar member no longer available

Using nvim-snippets as part of LazyVim
Running into this error every time snippets are listed in completion.
Error executing vim.schedule lua callback: ...hare/nvim/lazy/nvim-snippets/lua/snippets/utils/init.lua:202: attempt to index field '_snippet_grammar' (a nil value)
stack traceback:
	...hare/nvim/lazy/nvim-snippets/lua/snippets/utils/init.lua:202: in function 'safe_parse'
	...hare/nvim/lazy/nvim-snippets/lua/snippets/utils/init.lua:215: in function 'expand_vars'
	...share/nvim/lazy/nvim-snippets/lua/snippets/utils/cmp.lua:79: in function 'resolve'
	...lkins/.local/share/nvim/lazy/nvim-cmp/lua/cmp/source.lua:384: in function 'resolve'
	...ilkins/.local/share/nvim/lazy/nvim-cmp/lua/cmp/entry.lua:505: in function 'resolve'
	...wilkins/.local/share/nvim/lazy/nvim-cmp/lua/cmp/view.lua:287: in function 'fn'
	.../.local/share/nvim/lazy/nvim-cmp/lua/cmp/utils/async.lua:71: in function <.../.local/share/nvim/lazy/nvim-cmp/lua/cmp/utils/async.lua:69>

I've hopefully resolved this with #30. I copied the parser logic that was being used in _snippet_grammer locally into nvim-snippets. Let me know if the issue persists and thanks for reporting it.

Why was this needed? As far as I can see, vim.lsp._snippet_grammar is still in core.
Maybe op is using an old nightly?

I was hesitant to do this to begin with since I didn't want to need to maintain a separate instance of of the same grammar. I didn't want to cause a regression in LazyVim though if there was a potential that the grammar didn't exist on on 0.10. I'm going to revert this PR then as a result. Thanks for pointing this out @folke

@garymjr  You also want to remove the vim.print statements in get_selected_text!! :)

@garymjr You also want to remove the vim.print statements in get_selected_text!! :)

Done 🤦


Updated Columns in Catalog Table

Hey, I just made a Pull Request!
Updated columns in the catalogue table view to vary columns based on entity kind. Specifically excluding columns that aren't supported by that entity kind.  Further work could be done on top of this to further tailor columns to each entity kind (e.g. Groups could show parent instead of owner, systems could have a domain column)
Fixes #10452
(I am primarily a .Net backend dev, so let me know if there are more idiomatic ways I could implement this.)
Screenshots for each entity kind:

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@afscrome Oh no, there's missing DCO signatures!

@freben I'm not sure how to fix as I think the DCO bot is giving incorrect instructions to fix - https://github.com/backstage/backstage/runs/5759862912
It's saying to run git rebase HEAD~5 --signoff, but the last 6 commits include some depenabot commits which I'm pretty sure I shouldn't be signing off myself. Also as I've done a merge, I'm pretty sure some of my unsigned commits come from before that.
Rather than merge, should I just rebase the whole branch against latest and sign that off.

@afscrome maybe run this: git rebase -i --signoff $(git merge-base -a master HEAD) and make sure that you only pick the commits that are owned by you.

Cheers @benjdlambert , looks like DCO bot is happy now.


Fixes broken e2e test after adding conntrack.

This should resolve the broken e2e test.
In my testing I found that if you manually install packages with dpkg and then try to resolve their dependencies with apt-get install -f -y and the apt-cache is empty. The apt resolver will remove the manually added packages. Presumably cause it doesn't have enough information to resolve the deps.
If we do an apt-get update before the apt-get install -f -y then the resolver should have all that's needed to correctly resolve and will install the missing bits.
There is an apt-get update in the previous for loop. This just adds one for when we are using local packages it should not add any more time to the test.

@fabriziopandini, @timstclair @neolit123

Turns out this isn't the root cause. I still think this is a good change but the real problem is fixed here:
https://github.com/kubernetes/kubernetes/pull/71629

Thanks @luxas ! I forgot about this one


Which is the "c2a6ef524401945b493f14f8b5b8aa76cc7d71a9" branch of Pangolin?

The author said that they used c2a6ef524401945b493f14f8b5b8aa76cc7d71a9 branch of Pangolin,
but on the github of Pangolin, I can only find branch names rather than ID code like c2a6ef524401945b493f14f8b5b8aa76cc7d71a9. So hope someone could tell me c2a6ef524401945b493f14f8b5b8aa76cc7d71a9 is which branch. Thanks!

Download the repo, then you can simply do git checkout <branch_code> you can also only enter the first few characters, it will autocomplete.


Rumour state fixes

I think there's a bug in the 'rumour state' where if you complete a rumour, then go deliver the item and DONT immediately get a new one, the plugin doesn't update to 'Rumour.NONE'.

Fixed in v1.1.0


Provide credit to the original dynamodb plugin writer

Provide credit to the original dynamodb plugin writer

Completed :white_check_mark:


phantom taking damage inside blocks

in 1.18.1 there is a problem that cause the phantom form to take damage when inside a blocks

It's a current incompatibility with Lithium. Lithium has added a new rule for optimizing entity suffocation checks, which currently causes Phantom (and any other origins with phasing powers) to suffocate while moving through blocks.
To disable this new optimization rule, you can set the value of the mixin.entity.collisions.suffocation field inside the lithium.properties file from your Minecraft's (or server's) config folder to false, like so:
# This is the configuration file for Lithium.
# This file exists for debugging purposes and should not be configured otherwise.
#
# You can find information on editing this file and all the available options here:
# https://github.com/jellysquid3/lithium-fabric/wiki/Configuration-File
#
# By default, this file will be empty except for this notice.
mixin.entity.collisions.suffocation=false

Duplicate of https://github.com/apace100/origins-fabric/issues/473


what about haskell implementation?

hello
sorry, maybe this question better ask in other place, but i do not know where
so i ask here
when libp2p implementation in haskell wait for?
anyway, thanks

I'm personally not aware of any Haskell implementation, but anyone is welcome to write one.

there are written "In progress..." about haskell at website
so interesting how long time needs to wait for this one :)


Add uv_translate_posix_error and uv_translate_win32_error

References #79.

@piscisaureus can you PTAL?  Other @libuv/collaborators are also welcome, of course.

@indutny see #79

@saghul I do get your point, but the commit message should describe it too (IMO), and there should be a documentation for it.

but the commit message should describe it too (IMO), and there should be a documentation for it.

Agreed! @plafer can you please take care of these?

Of course!

So this patch has now changed to: "make uv_translate_sys_error public" ?
I'm okay with that. I guess I'd personally prefer to have stable error numbers instead of using the negated platform error code on unix-ish platforms, but that seems out of scope for this discussion.
Also, I find calling the function that translates windows error codes to uv error codes uv_translate_win32_error really not a bad.

@piscisaureus

So this patch has now changed to: "make uv_translate_sys_error public" ?

Thas was the initial request in #79.

Also, I find calling the function that translates windows error codes to uv error codes uv_translate_win32_error really not a bad.

So, back in the day you suggested we need 2 functions because some Windows functions can also return POSIX style errnos.  This patch doesn't consider those, also libuv doesn't have a translation mechanism for those per se, since we prefer Win32 or NT APIs, right?
So, do you have any objections to the current implementation proposal?  I wanted to double-check with you, since you were the one who originally proposed we have 2 functions.
Thanks Bert!

If it's going to be a public API, there should probably be at least one test, just for sanity.

If it's going to be a public API, there should probably be at least one test, just for sanity.

Indeed!  A couple of tests would be nice: using a real errno and a UV errno, both on Windows an Unix.

@saghul
I do prefer to have two different functions, but I don't feel that strongly about it.
I'm also okay with just exposing uv_translate_sys_error, which is what this PR seems to do.
TL;DR ship it.

@piscisaureus Thanks for chiming in!

CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/146/

Could someone point me in the right direction as to why this might have failed on some platforms but not others?

It doesn't look like the test from this PR actually failed anywhere.

@saghul does this LGTY now?

@cjihrig Not yet, see https://github.com/libuv/libuv/pull/1060#discussion_r80433463

It looks like those are addressed now. I think comments left using GitHub's code review feature remain even after being addressed.

Is there still something missing? If so, I can fix it.

Ah, I see now. It's fixed indeed. Now, this PR mentions this API was added in 1.11.0, but we haven't released 1.10 yet. Hopefully that happens this week, so we could add this one in. Thoughts @cjihrig? I'm ok with landing it now, we can fix the version changed when merging.

Sounds like a fine plan to me. I wonder if libuv should adopt something like the REPLACEME that Node uses for setting the version added during releases.

@cjihrig Yeah, we should probably do that.

I've opened https://github.com/libuv/libuv-release-tool/issues/7, to track adding REPLACEME, but can get this landed for 1.10 after a new CI run.

CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/157/

Unrelated to this change, but that might be the greenest CI run I've seen for libuv.

LGTM again :-)
On Oct 16, 2016 20:30, "Colin Ihrig"<EMAIL_ADDRESS>wrote:

Unrelated to this change, but that might be the greenest CI run I've seen
for libuv.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/libuv/libuv/pull/1060#issuecomment-254068545, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AATYGOsxnDYQsTzbTKjCbBOW-8P1K5z8ks5q0ntTgaJpZM4KACnX
.

Thanks! Landed in f1863dae6bb27e31644307cf0905d42bd41251c9.


Fix isort

Codecov Report

Merging #32 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
+ Coverage   89.46%   89.47%   +<.01%
==========================================
  Files          93       93
  Lines       11990    11997       +7
  Branches     1085     1085
==========================================
+ Hits        10727    10734       +7
  Misses       1094     1094
  Partials      169      169

Impacted Files
Coverage Δ

openid/test/__init__.py
50% <100%> (+10%)
:arrow_up:

openid/yadis/__init__.py
60% <100%> (+4.44%)
:arrow_up:

openid/consumer/__init__.py
100% <100%> (ø)
:arrow_up:

openid/__init__.py
100% <100%> (ø)
:arrow_up:

openid/store/__init__.py
100% <100%> (ø)
:arrow_up:

openid/server/__init__.py
100% <100%> (ø)
:arrow_up:

openid/extensions/__init__.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


ERROR: yaml_cpp_vendor: No definition of [ament_cmake] for OS version [focal]

I used the following command to install ROS2 humble in r35.3.1:
./scripts/docker_build_ros.sh --distro humble --package desktop
But I got the following error at rosdep install:
Skip end-of-life distro "ardent"
Skip end-of-life distro "bouncy"
Skip end-of-life distro "crystal"
Skip end-of-life distro "dashing"
Skip end-of-life distro "eloquent"
Add distro "foxy"
Skip end-of-life distro "galactic"
Skip end-of-life distro "groovy"
Add distro "humble"
Skip end-of-life distro "hydro"
Skip end-of-life distro "indigo"
Add distro "iron"
Skip end-of-life distro "jade"
Skip end-of-life distro "kinetic"
Skip end-of-life distro "lunar"
Add distro "melodic"
Add distro "noetic"
Add distro "rolling"
updated cache in /root/.ros/rosdep/sources.cache
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
yaml_cpp_vendor: No definition of [ament_cmake] for OS version [focal]
The command '/bin/bash -c apt-get update &&     cd ${ROS_ROOT} && 	export ROSDISTRO_INDEX_URL=https://mirrors.tuna.tsinghua.edu.cn/rosdistro/index-v4.yaml &&     rosdep update &&     rosdep install -y     	  --ignore-src        --from-paths src 	  --rosdistro ${ROS_DISTRO} 	  --skip-keys "libopencv-dev libopencv-contrib-dev libopencv-imgproc-dev python-opencv python3-opencv" &&     rm -rf /var/lib/apt/lists/* &&     apt-get clean' returned a non-zero code: 1

@XujqGitHub I will be rebuilding the ROS containers for L4T R35.3.1, but for now you can use the ones for L4T R35.2.1

@dusty-nv
Thanks, I look forward to the ROS containers for L4T R35.3.1.

Hi,
@dusty-nv
I have resolved the above-mentioned issue by executing the command ./scripts/docker_build_ros.sh --distro humble --package desktop multiple times. The reason producing this issue maybe my network quality.
What's more, I'm newbie for ROS. I also noticed NVIDIA-ISAAC-ROS. I also want to know what are differences between this repository and NVIDIA-ISAAC-ROS? Can you give me some information?

@XujqGitHub the ROS/ROS2 containers for JetPack 5.1.1 (L4T R35.3.1) have now been pushed to DockerHub, including the base/pytorch/desktop images:
https://hub.docker.com/repository/docker/dustynv/ros/tags?page=1&ordering=last_updated&name=r35.3.1
I have yet to update the table with these in the readme, but will in the coming days.

that were built with CUDA enabled so that they can use GPU acceleration if you so choose

Thanks for your help. In this repo, which type of ROS image supports CUDA? desktop? or pytorch? or all of image?
What's more, other packages like Gazebo, MoveIt, ros2_control. Do I need to install these packages myself in my container?

Do the ros:*-pytorch-* images consist of ros-base (excluding ROS GUI) + PyTorch? I can't run Rviz2 by the command ros2 run rviz2 rviz2.


save format

This is just a suggestion - I've had changing thoughts on it myself.
The save format you have created is very similar to what was used by Craterstats2. But you'll note that if you want to record more than one overplot in a file, you need to deal with multiple plot structures/dictionaries.
While I still use this format for setting up the default options, I've started writing a '.cs' file together with the output of every command. This file contains the used command line options (with some line breaks to make it more readable). You can recreate any plot by typing craterstats -i plotname.cs [you may need to refer to the github code - I think it may not be in the pypi version yet] The advantage of this is that you can easily modify a complex plot without being faced with navigating a very long command line.
It might be easy for you to do it this way, too, since you're already recreating the command line.
I think, at some point, I will remove the .plt default format from my code.

I wasn't able to find a .cs file to reproduce this inside of the github repo, is there a specific folder it might be in? My only thought on this is that there might be a problem related to the filename since typically a '.cs' file if for the C# programming language. Though if you've been using it with no problems my thought can be disregarded.

There is no .cs file currently in the repo, but one should be created each
time you run a command with output. The code is in cli.main.
Unfortunately, now that I check, it looks like the argument capture is
working differently in the distributed version from my development
environment. I'm not sure how to troubleshoot that other than by releasing
potentially buggy versions through pypi. I have to think about how to do
that - let's leave this issue for now.
On Mon, 11 Nov 2024 at 18:01, Caden Tedeschi @.***>
wrote:

I wasn't able to find a .cs file to reproduce this inside of the github
repo, is there a specific folder it might be in? My only thought on this is
that there might be a problem related to the filename since typically a
'.cs' file if for the C# programming language. Though if you've been using
it with no problems my thought can be disregarded.
—
Reply to this email directly, view it on GitHub
https://github.com/LWATLINGTON02/CraterStats-Capstone/issues/30#issuecomment-2468642100,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR5ZQ2UKWZQSEGZXIDBFVZL2ADPFPAVCNFSM6AAAAABRRGM55WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRYGY2DEMJQGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Allow reseting channel specific AutoClearChanBuffer & Buffer settings

The trick is to set the value to "-" in controlpanel. Notice that
controlpanel supports wildcards, so this can be used to easily
reset all channels back to defaults if desired.

Does someone want to do the webadmin part? Some sort of reset-button.


Please allow to use the external taglib

There is already a taglib installed:
$ pkg info | grep taglib
taglib-1.11.1_2                Library for manipulating ID3 tags and Ogg comments

Repology shows that taglib is available on virtually all systems now: https://repology.org/metapackage/taglib/versions , so there should be no need to bundle it.
It's not a show-stopper, but external packages should be used when possible. Otherwise everything will bundle everything else, and there'll be hundreds of copies of the same things in the system. -)

I'll give this a shot later today! I'm going to guess it'll be fine to use the external library on FreeBSD -- this hack currently exists because certain older versions of Ubuntu had a version of the library that was incorrectly/incompletely compiled and was missing some symbols we depended on.

You should create a cmake variable, ex. USE_BUNDLED_TAGLIB, with default OFF. People who need it bundled will be able to turn it ON.

Yep, did just that. Changes are in the master branch. Should be good to go now!

Thank you!


CAST_encrypt shift overflow

I used to think this was a false positive but apparently unsigned int overshift might be undefined: https://stackoverflow.com/questions/33736337/large-bitwise-left-shift-on-unsigned-type/33736410
Stack trace from https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14351
/src/libressl/crypto/cast/c_enc.c:73:2: runtime error: shift exponent 32 is too large for 32-bit type 'unsigned int'
--
  | #0 0xb29152 in CAST_encrypt libressl/crypto/cast/c_enc.c:73:2
  | #1 0xb2aa58 in CAST_ecb_encrypt libressl/crypto/cast/c_ecb.c:71:3
  | #2 0xb073cb in cast5_ecb_cipher libressl/crypto/evp/e_cast.c:80:1
  | #3 0xb2345e in CMAC_Init libressl/crypto/cmac/cmac.c:182:8

Oh it's LibreSSL lol. sorry.


Uncaught (in promise) WalletNotSelectedError

Describe the bug
Uncaught (in promise) WalletNotSelectedError
To Reproduce
I wrapped component with context from https://github.com/solana-labs/wallet-adapter/blob/master/packages/starter/react-ui-starter/src/App.tsx
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser chrome
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
here is my code
import "./App.css";
import { WalletAdapterNetwork } from "@solana/wallet-adapter-base";
import {
  ConnectionProvider,
  WalletProvider,
} from "@solana/wallet-adapter-react";
import { UnsafeBurnerWalletAdapter } from "@solana/wallet-adapter-wallets";
import { clusterApiUrl } from<EMAIL_ADDRESS>import React, { useMemo } from "react";
import Button from "./Button";

function App() {
  const Context = ({ children }) => {
    // The network can be set to 'devnet', 'testnet', or 'mainnet-beta'.
    const network = WalletAdapterNetwork.Devnet;

    // You can also provide a custom RPC endpoint.
    const endpoint = useMemo(() => clusterApiUrl(network), [network]);

    const wallets = useMemo(
      () => [
        /**
         * Wallets that implement either of these standards will be available automatically.
         *
         *   - Solana Mobile Stack Mobile Wallet Adapter Protocol
         *     (https://github.com/solana-mobile/mobile-wallet-adapter)
         *   - Solana Wallet Standard
         *     (https://github.com/solana-labs/wallet-standard)
         *
         * If you wish to support a wallet that supports neither of those standards,
         * instantiate its legacy wallet adapter here. Common legacy adapters can be found
         * in the npm package `@solana/wallet-adapter-wallets`.
         */
        new UnsafeBurnerWalletAdapter(),
      ],
      // eslint-disable-next-line react-hooks/exhaustive-deps
      [network]
    );

    return (
      <ConnectionProvider endpoint={endpoint}>
        <WalletProvider wallets={wallets} autoConnect>
          <Button />
        </WalletProvider>
      </ConnectionProvider>
    );
  };

  return (

      <Context>
        <Button />
      </Context>

  );
}

export default App;

I'm not sure what Button does but you have to select and then connect to a wallet to use it. If you are attempting to call connect without having selected a wallet first, you'll get a WalletNotSelectedError. The recommended way to handle this is to not call connect at all, but use the autoConnect behavior that you already have enabled on WalletProvider. You still need to use a button or some other user action to call select.

You should add select and connect wallet function on Button.
Here is how.

const { select, connect } = useWallet();

const buttonClicked = async () => {
     select();
     await connect();
}

return (

      <Context>
        <Button onClick={buttonClicked} />
      </Context>

)

This is stupid, but it looks like calling await select() works even it is not documented as a promise!

select function must be async function

select function must be async function select(walletName); connect(); always returns WalletNotSelectedError just after loading page

same here, have to "connect" two times in order to work...

select function must be async function select(walletName); connect(); always returns WalletNotSelectedError just after loading page

same here, have to "connect" two times in order to work...

same problem

Solved it using this logic:
const connectWallet = async (walletName) => {
    currentWallet?.adapter.name === walletName
      ? await connect()
      : select(walletName)
  }


JXL support?

Hello, thank you for the great tool!
Is there JXL support?
I'm seeing:
> vips copy camera.jpeg camera.jxl
> ./ssimulacra camera.jpeg camera.jxl
Image file camera.jpeg has 3 channels, while
image file camera.jxl has 1 channels. Can't compare.

No, this tool uses the OpenCV image loader, which currently doesn't support jxl.


Raspberry Pi Compute Module 4

Basic information

Board URL (official): https://www.raspberrypi.com/products/compute-module-4/?variant=raspberry-pi-cm4001000
Board purchased from: PiShop.us
Board purchase date: 2021-08-05
Board specs (as tested): Wireless, 8GB, Lite - CM4108000
Board price (as tested): $75.00

Linux/system information
# output of `neofetch`
PASTE_HERE

# output of `uname -a`
PASTE_HERE

Benchmark results
CPU

Geekbench: (TODO single / TODO multi - PASTE_URL)
TODO Gflops (geerlingguy/top500-benchmark HPL result)

Power

Idle power draw (at wall): TODO W
Maximum simulated power draw (stress-ng --matrix 0): TODO W
During Geekbench multicore benchmark: TODO W
During top500 HPL benchmark: TODO W

Disk
KIOXIA XG6 M.2 NVMe SSD

Benchmark
Result

fio 1M sequential read
418 MB/s

iozone 1M random read
378 MB/s

iozone 1M random write
355 MB/s

iozone 4K random read
37.21 MB/s

iozone 4K random write
80.68 MB/s

curl https://raw.githubusercontent.com/geerlingguy/pi-cluster/master/benchmarks/disk-benchmark.sh | sudo bash
Run benchmark on any attached storage device (e.g. eMMC, microSD, NVMe, SATA) and add results under an additional heading. Download the script with curl -o disk-benchmark.sh [URL_HERE] and run sudo DEVICE_UNDER_TEST=/dev/sda DEVICE_MOUNT_PATH=/mnt/sda1 ./disk-benchmark.sh (assuming the device is sda).
Also consider running PiBenchmarks.com script.
Network
iperf3 results:

iperf3 -c $SERVER_IP: TODO Mbps
iperf3 --reverse -c $SERVER_IP: TODO Mbps
iperf3 --bidir -c $SERVER_IP: TODO Mbps

(Be sure to test all interfaces, noting any that are non-functional.)
GPU

TODO: Haven't determined standardized benchmark yet. See Issue #2.

Memory

TODO: Haven't determined standardized benchmark yet. See Issue #2.

Would be very interested to see some of these numbers if anyone could run tests, particularly curious how power draw compares to the standard Pi 4 as the CM4 datasheet says it uses slightly less.

@aspencuozzo - Ha! I completely forgot I haven't filled in all the details here. Will do so today.


Make tests asynchronous

Asynchronous, stateless tests can be run in parallel, resulting in better resource consumption and faster CI build times.

This has been resolved by 7d6c495aac86b06873fcfef6dce2c93445574db4.


Looks like the updated code requires trl>=0.9.3, which isn't compatiable with unsloth

Reminder

[X] I have read the README and searched the existing issues.

System Info

llamafactory version: 0.7.2.dev0
Platform: Linux-4.18.0-517.el8.x86_64-x86_64-with-glibc2.28
Python version: 3.9.0
PyTorch version: 2.0.0+cu117 (GPU)
Transformers version: 4.41.2
Datasets version: 2.19.2
Accelerate version: 0.30.1
PEFT version: 0.11.1
TRL version: 0.9.4
GPU type: NVIDIA L40
Bitsandbytes version: 0.43.1

Reproduction

git clone --depth 1 https://github.com/hiyouga/LLaMA-Factory.git
cd LLaMA-Factory
pip install -e .[metrics]

pip install "unsloth[cu118-torch230] @ git+https://github.com/unslothai/unsloth.git"

Yesterday everthing worked well, but today I got error:
Traceback (most recent call last):
File "/var/lib/condor/execute/slot1/dir_677837/mm_molecule/bin/llamafactory-cli", line 5, in
from llamafactory.cli import main
File "/var/lib/condor/execute/slot1/dir_677837/LLaMA-Factory/src/llamafactory/init.py", line 3, in
from .cli import VERSION
File "/var/lib/condor/execute/slot1/dir_677837/LLaMA-Factory/src/llamafactory/cli.py", line 7, in
from . import launcher
File "/var/lib/condor/execute/slot1/dir_677837/LLaMA-Factory/src/llamafactory/launcher.py", line 1, in
from llamafactory.train.tuner import run_exp
File "/var/lib/condor/execute/slot1/dir_677837/LLaMA-Factory/src/llamafactory/train/tuner.py", line 9, in
from ..hparams import get_infer_args, get_train_args
File "/var/lib/condor/execute/slot1/dir_677837/LLaMA-Factory/src/llamafactory/hparams/init.py", line 6, in
from .parser import get_eval_args, get_infer_args, get_train_args
File "/var/lib/condor/execute/slot1/dir_677837/LLaMA-Factory/src/llamafactory/hparams/parser.py", line 27, in
check_dependencies()
File "/var/lib/condor/execute/slot1/dir_677837/LLaMA-Factory/src/llamafactory/extras/misc.py", line 68, in check_dependencies
require_version("trl>=0.9.3", "To fix: pip install trl>=0.9.3")
File "/var/lib/condor/execute/slot1/dir_677837/mm_molecule/lib/python3.9/site-packages/transformers/utils/versions.py", line 111, in require_version
_compare_versions(op, got_ver, want_ver, requirement, pkg, hint)
File "/var/lib/condor/execute/slot1/dir_677837/mm_molecule/lib/python3.9/site-packages/transformers/utils/versions.py", line 44, in _compare_versions
raise ImportError(
ImportError: trl>=0.9.3 is required for a normal functioning of this module, but found trl==0.8.6.
To fix: pip install trl>=0.9.3
Even though I can install trl==0.9.4, the unsloth will override it again:
Collecting trl<0.9.0,>=0.7.9 (from unsloth[cu118-torch230]@ git+https://github.com/unslothai/unsloth.git)
Downloading trl-0.8.6-py3-none-any.whl.metadata (11 kB)
After I delete the pip install "unsloth[cu118-torch230] @ git+https://github.com/unslothai/unsloth.git", it works fine. But it also means I can't use unsloth for training.
Expected behavior
It seems that updated LLAMA-Factory code add the constraint for trl version>=0.9.3. Is it necessary?
Others
No response

fixed


Custom scalars should work without having to add @specifiedBy

Description
Currently if the schema being parsed by Apollo compiler includes custom scalar definition without the @specifiedBy directive the schema won't compile. In the GraphQL specification (revision October 2021)  they use the word SHOULD when referring to custom scalars having to add the @specifiedBy directive.

When defining a custom scalar, GraphQL services should provide a scalar specification URL via the @specifiedBy directive or the specifiedByURL introspection field. This URL must link to a human-readable specification of the data format, serialization, and coercion rules for the scalar.

My understanding is that custom scalar without including the @specifiedBy directive should work. Am I correct?
Looks like this rule has been added in https://github.com/apollographql/apollo-rs/pull/234
Steps to reproduce
scalar DateTime
type Object {
  field: DateTime
}

Expected result
It should compile
Actual result
It does not compile because it requires that DateTime to be definition to include @specifiedBy
Environment

Operating system and version: macOS 13.3.1
Shell (bash/zsh/powershell): zsh
apollo-rs crate: 0.8.0
Crate version: 0.8.0

@lrlna cool! In my particular case I ended-up working around this by injecting the @specifiedBy directive before passing the schema to ApolloCompiler, I don't control the schema's my app has to handle and that was a quick hack that worked.
Funny thing is that I found this issue with a schema that was generated from an introspection query using https://github.com/apollographql/introspector-gadget. The original schema did specify the directive for each custom scalar that introspector didn't support asking for the directive and therefore not including it in the generated schema SDL. That one was an easy fix https://github.com/apollographql/introspector-gadget/pull/9.

I believe this is fixed in apollo-compiler 1.0, now in beta. The new signature for schema validation is:
https://docs.rs/apollo-compiler/1.0.0-beta.1/apollo_compiler/schema/struct.Schema.html#method.validate
impl Schema {
    pub fn validate(&self) -> Result<Diagnostics, Diagnostics> { .. }
}

The result will be Err if there are any error-level diagnostics (meaning the schema is invalid). Result::Ok on other hand indicates that the schema is valid. It contains a set of Diagnostics that’s either empty or only has advice-level or warning-level thing like missing @specifiedBy.


Bug: Migration Problem "Incorrect table definition; there can be only one auto column and it must be defined as a key"

PHP Version
8.1
CodeIgniter4 Version
^4.0
CodeIgniter4 Installation Method
Composer (using codeigniter4/appstarter)
Which operating systems have you tested for this bug?
Windows
Which server did you use?
apache
Database
MySQL
What happened?
What I experienced:

Unable to migrate database.
In the 'id' field, I can't customize a value.

For point 2:
For point 2: I looked at 'CodeIgniter\Database\Forge' at line 362-367, there is an array containing:
'id' => [
   'type'           => 'INT',
   'constraint'     => 9,
   'auto_increment' => true,
],

Can I not customize the 'id' field value in the table?
Steps to Reproduce
1) Config File
I created 1 config file in app/Config/ExampleConfig.php
<?php

namespace Config;

use CodeIgniter\Config\BaseConfig;

class ExampleConfig extends BaseConfig
{
    /**
     * Fields of table
     *
     * @var array
     */
    public array $fields = [
        'id'            => ['type' => 'int', 'constraint' => 11, 'unsigned' => true, 'auto_increment' => true],
        'created_at'    => ['type' => 'datetime', 'null' => true],
        'updated_at'    => ['type' => 'datetime', 'null' => true],
        'deleted_at'    => ['type' => 'datetime', 'null' => true],
        'code'          => ['type' => 'varchar', 'constraint' => 255],
        'symbol'        => ['type' => 'varchar', 'constraint' => 255, 'null' => true],
        'name'          => ['type' => 'varchar', 'constraint' => 255],
    ];

    /**
     * Foreign Key
     * ---
     *
     * Example:
     * $foreignKey = [
     *  [
     *      'fieldName'     => 'example_id',
     *      'tableName'     => 'example_table',
     *      'tableField'    => 'id',
     *      'onUpdate'      => '',
     *      'onDelete'      => 'CASCADE',
     *      'fkName'        => '',
     *  ],
     * ]
     *
     * @var array
     */
    public array $foreignKey = [];
}

2) Migration File
I created 1 migration file in app/Database/Migrations/2023-05-01-231938_CreateTableExample.php
<?php

namespace App\Database\Migrations;

use CodeIgniter\Database\Migration;
use Config\ExampleConfig;

class CreateTableExample extends Migration
{
    /**
     * Constructor.
     */
    public function __construct()
    {
        parent::__construct();

        $this->config = new ExampleConfig();
        $this->DBGroup = $this->config->DBGroup;
    }

    public function up()
    {
        if (count($this->config->fields) > 0 && $this->config->table) {
            // Fields
            $this->forge->addField($this->config->fields);

            // Create Table
            $this->forge->createTable($this->config->table, true);
        }
    }

    public function down()
    {
        if ($this->config->table) {
            // drop constraints first to prevent errors
            if ($this->db->DBDriver !== 'SQLite3') { // @phpstan-ignore-line
                // Foreign Key
                foreach ($this->config->foreignKey as $foreignKey) {
                    if ($foreignKey['fieldName']) {
                        $this->forge->dropForeignKey($this->config->table, $this->config->table . '_' . $foreignKey['fieldName'] . '_foreign');
                    }
                }
            }

            // Drop Table
            $this->forge->dropTable($this->config->table, true);
        }
    }
}

3) Run Migration
php spark migrate
Expected Output
It is possible to customize a field in the config file 🤔
Anything else?
I instead get an error message:
[CodeIgniter\Database\Exceptions\DatabaseException]

Incorrect table definition; there can be only one auto column and it must be defined as a key

at SYSTEMPATH\Database\BaseConnection.php:646

^4.0 is not a exact version. It shows version range.
Please write the exact version you use.

Can I not customize the 'id' field value in the table?

Yes, you can.
The code you pointed is for:
https://codeigniter4.github.io/CodeIgniter4/dbmgmt/forge.html#creating-an-id-field
Do like this:
https://github.com/codeigniter4/shield/blob/1225c80ac08ede8d97f9bdf661e80dee6d83515a/src/Database/Migrations/2020-12-28-223112_create_auth_tables.php#L30-L43

We use GitHub issues to track BUGS and to track approved DEVELOPMENT work packages. We use our forum to provide SUPPORT and to discuss FEATURE REQUESTS.

Thanks sir..
My Allah bless u

Thanks sir.. My Allah bless u

Sorry for the wrong place to ask


Figure out a way to test precompiled code on iOS devices using test.py

@mraleph @rmacnak-google @mkustermann
The main issue is to figure out how to automate the xcode build process that is used for precompiled code.

Is there a way to build standalone for iOS?

No, and there are other missing pieces, e.g. there seem to be no adb-equivalent for iOS.

Flutter uses ios-deploy and iproxy.


[Bug] SPADE param min_neu does not work

Describe the bug
The parameter min_neu in SPADE should fix the minimal number of neurons in a pattern. This is typically used to avoid auto-patterns. In older versions of SPADE this was properly running but with the latest version. I get clearly patterns, that I don't want to get as output.
My suspection is that the generated fim.so is not working properly. Especially, it doesn't work the same way as the locally stored fim.so that we were using before.
@Kleinjohann @mdenker : do you have any idea where this problem might come from?
To Reproduce
import numpy as np
from elephant.spade import spade
from elephant.spike_train_generation import StationaryPoissonProcess
import quantities as pq

np.random.seed(0)
poisson_process = StationaryPoissonProcess(rate=20*pq.Hz, t_stop=5*pq.s)

n_spiketrains = 3
spiketrains = poisson_process.generate_n_spiketrains(
    n_spiketrains=n_spiketrains)
bin_size = 5 * pq.ms

spade_output = spade(
    spiketrains,
    bin_size=bin_size,

    # +1 to pattern length to be able to find it again
    winlen=2,
    min_spikes=n_spiketrains,
    max_spikes=n_spiketrains,

    # This should avoid to get auto-patterns.
    # But apparently it doesn't work.
    min_neu=n_spiketrains,
    spectrum='3d#')

patterns = spade_output['patterns']
print(patterns)

for pattern in patterns:
    # Check that all spiketrains contain three different neurons
    # assert len(np.unique(pattern['neurons']))==n_spiketrains
    if len(np.unique(pattern['neurons']))!=n_spiketrains:
        print(f'Found autopattern with neurons {pattern["neurons"]}')

Expected behavior
The expected output of the code snippet is:
[{'itemset': (2, 5, 1), 'windows_ids': (36, 134, 856), 'neurons': [1, 2, 0], 'lags': array([5., 5.]) * ms, 'times': array([ 180.,  670., 4280.]) * ms, 'signature': (3, 3, 1), 'pvalue': -1}]

The actual outcome now is:
[{'itemset': (4, 0, 1), 'windows_ids': (646, 775), 'neurons': [2, 0, 0], 'lags': array([0., 5.]) * ms, 'times': array([3230., 3875.]) * ms, 'signature': (3, 2, 1), 'pvalue': -1}, {'itemset': (2, 5, 1), 'windows_ids': (36, 134, 856), 'neurons': [1, 2, 0], 'lags': array([5., 5.]) * ms, 'times': array([ 180.,  670., 4280.]) * ms, 'signature': (3, 3, 1), 'pvalue': -1}]
Found autopattern with neurons [2, 0, 0]

Environment

OS (e.g., Linux): Linux
How you installed elephant (conda, pip, source): pip
Python version: 3.8.16
neo python package version:  0.12.0
elephant python package version:  0.12.0
numpy: 1.24.2

I just checked that the last elephant versions where it works properly is elephant == 0.10.0.
You can check it like this:
import numpy as np
import elephant
from elephant.spade import spade
if int(elephant.__version__[2:4]) > 10:
    NEW_POISSON = True
    from elephant.spike_train_generation import StationaryPoissonProcess
else:
    NEW_POISSON = False
    from elephant.spike_train_generation import homogeneous_poisson_process
import quantities as pq

np.random.seed(0)

n_spiketrains = 3
if NEW_POISSON:
    poisson_process = StationaryPoissonProcess(rate=20*pq.Hz, t_stop=5*pq.s)
    spiketrains = poisson_process.generate_n_spiketrains(
        n_spiketrains=n_spiketrains)
else:
    # I increased the length here to be sure. That I don't depend on the seed
    # to not find autopatterns with SPADE.
    spiketrains = [homogeneous_poisson_process(rate=20*pq.Hz, t_stop=20*pq.s)
                   for _ in range(n_spiketrains)]
bin_size = 5 * pq.ms

spade_output = spade(
    spiketrains,
    bin_size=bin_size,

    # +1 to pattern length to be able to find it again
    winlen=2,
    min_spikes=n_spiketrains,
    max_spikes=n_spiketrains,

    # This should avoid to get auto-patterns.
    # But apparently it doesn't work.
    min_neu=n_spiketrains,
    spectrum='3d#')

patterns = spade_output['patterns']
print(patterns)

for pattern in patterns:
    # Check that all spiketrains contain three different neurons
    # assert len(np.unique(pattern['neurons']))==n_spiketrains
    if len(np.unique(pattern['neurons']))!=n_spiketrains:
        print(f'Found autopattern with neurons {pattern["neurons"]}')

Following Florian Porrmann's suggestions, one needs to change the SPADE code to look like this:
(sarting form line 906)
fpgrowth_output = fim.fpgrowth(
                tracts=transactions,
                target=target,
                supp=-min_c,
                zmin=min_z,
                zmax=max_z,
                report='a',
                algo='s',
                winlen=winlen,
                min_neu=min_neu,
                threads=0,
                verbose=4)

This runs through the test.
I will make a pull request for this in the next days.

With this merge, we can close this issue: https://github.com/NeuralEnsemble/elephant/pull/575


chore: MRK-14167 Update yarn.lock

Background
We've added a new meta field pcx-content-type which will be used by Coveo Scrapper.
- In this PR we are updating Yarn.lock for the field to reflect in individual product sites
#### Screenshot

Okay, have verified that the value does not affect whether or not the page is rendered.
(sorry about the caution... but I broke all our pages last year when I made the DocSearch component mandatory).
I'd still want @pedrosousa to have a look at it if he's able to, so leaving as pending until then.

Seems to be working properly, both when using the development server and when building the final Gatsby site. Tested with a few products.
A couple of final questions:

The following folders also have yarn.lock files, but they're not being updated. Is there any particular reason for this? They should probably use the same engine version.

browser-isolation
dns
docs-engine
events
magic-firewall
magic-wan
pages
spectrum
workers

The yarn.lock file in products/api-security is the only file in that folder. Can you remove both the file and the folder, since they're not needed?

I'm also getting the following deprecation warning when running the development server and when building:
warn Deprecation warning - adding inferred resolver for field Frontmatter.pcx_content_type. In Gatsby v3, only fields with an explicit directive/extension will get a resolver.

Hey @pedrosousa,
I've updated the PR accordingly.

@younggeeks, I think this change has been merged in with another PR done by @adesege.


Question: What is "id"?

Seen here:
https://github.com/elastic/node-traceparent/blob/master/index.js#L8
and here:
https://github.com/elastic/node-traceparent/blob/master/index.js#L20
Does this correspond to W3's "span ID?"
Thanks!

Yeah, it might be a little confusing. The context.id corresponds to the parent-id  in the spec. Now that you mention it, we should maybe consider refactoring that to make it less confusing. But here's the thoughts behind it:
By default, you're viewing this from the point of the sender service. That service wants to add a header to an outgoing http request where the outgoing http request span is set to be the parent from the point of view of the receiver.
So it generates a header like this:
const header = `${version}-${traceId}-${id}-${flags}`

In header, the id part is its own span id. But the header is, of course, meant to be read by the receiver, in which case it will become the parent span id of the receiving span.
Then when the request is received, the receiver will first parse the header like so:
const parent = TraceParent.fromString(header)

Notice that the variable name I've chosen to use is parent. This function call just parsed the header, and so parent.id will contain the span id of the parent span.
Now this new service probably wants to start a child span of the parent, so it does this:
const child = parent.child()

On the child object, you now have child.parentId, which is equal to parent.id, but you also have a random new span id on child.id.
Does that make sense?

That makes perfect sense, thanks!


chore: add Rust release directory

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Since I cannot review all 2100 files (:sigh), to be sure, apart from the files .github/workflows/library_rust_tests.yml, DynamoDbEncryption/runtimes/rust/src/intercept.rs and DynamoDbEncryption/runtimes/rust/src/lib.rs, the change you made was copying the entire DynamoDBEncryption directory into releases/rust/db_esdk and run make polymorph_rust and make transpile_rust right?

Almost. I updated the files you mentioned in DynamoDbEncryption, then ran make polymorph_rust transpile_rust, and then copied the result to /releases/
Plus one other change -- I made a local copy of dafny_runtime_rust, since I can't point at the one in smithy-dafny from /releases/
Then I did cargo test and cargo run --example in the /releases/ directory, just to make sure.


Introduce Current Network Indicator

Introduce the Current Network Indicator component which signals to the user what network they are currently on, per the design file

How is it? I tried to introduce the current network indicator.

@anmode the current network indicator is the colored box you see below the block clock, that's whats needed to be implemented. No more states of this component are needed.
There's an indicator for every network except main as that is not needed.

@anmode the current network indicator is the colored box you see below the block clock, that's whats needed to be implemented. No more states of this component are needed.
There's an indicator for every network except main as that is not needed.

Ohh my bad! I got it now.
I code then nd generate pR for the same!


Subdivision corner selection blocks keep reappearing

If I make a subdivision in my claim and try to break the blocks I used to select the corners they keep reappearing if I mine them and then click a stick in the main claim, back in the subdivision and out again.

This has been fixed and will be available in next build which I plan to release tomorrow.


Add container spec with image tag and image pull policy fields

Please specify the area for this PR
registry
What does does this PR do / why we need it:
Adds a new container spec which now defines the fields to setup the individual containers in the deployed pod. This new spec currently supports image and imagePullPolicy (requested in devfile/api#730) with the scalability to add new container fields in the near future (e.g. memoryLimit).
Which issue(s) this PR fixes:
Fixes #?
fixes devfile/api#730
PR acceptance criteria:

[ ] Test Coverage

Are your changes sufficiently tested, and are any applicable test cases added or updated to cover your changes?

[ ] Gosec scans

Fix all MEDIUM and higher findings and/or annotate a finding per gosec instructions: https://github.com/securego/gosec#annotating-code to address why a finding is not a security issue

Documentation

[X] Does the registry operator documentation need to updated with your changes?

How to test changes / Special notes to the reviewer:

/retest


Fix for bugs in qa exposed by RecalculateDates

Context
We need a way to pause/defer RBD and DBDs until providers can start processing applications again. Some of the work done to achieve this, in particular https://github.com/DFE-Digital/apply-for-postgraduate-teacher-training/pull/1692, has exposed a couple of problems that led to some errors on qa.
See https://sentry.io/organizations/dfe-bat/issues/1573923287/?project=1765973&referrer=slack
I think that the reason for this error is a race condition in DeclineOfferByDefault and the CandidateMailer. The mailer assumes that there is a declined by default application choice attached to the application form that it is given. However it could (at least in theory) run before the transaction in DeclineOfferByDefault gets committed. The mailer call was changed to be async just a few days ago so this didn't matter until very recently.
It also highlighted an issue in TestApplications the offered_at status is being set to the submitted_at date due to some time errors in the logic around edit_by in this class.
Changes proposed in this pull request

[x] Change references to Time.zone.local to time in TestApplications - we should be using the fake time that TestApplications manages to spread events across a realistic date range.
[x] Move the invocation of CandidateMailer in DeclineByDefault outside the transaction so that it can't run the Sidekiq job until after the transaction has been committed.

Guidance to review

Does the theory and solution to the race condition sound plausible?
It looks like there are other dates set in TestApplications that don't set to reflect the fake timeline. e.g. DeclineByDefault sets decline_by_default_at based on the current time - it knows nothing of the fake time

Link to Trello card
https://trello.com/c/iV0jnliU/1207-ucas-rbd-dbd-date-suspension-until-20th-april
Things to check

[x] This code doesn't rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

@duncanjbrown is this one good to merge now?


Missing Rows + Count Options

I've downloaded the latest version of movieprint to my computer and it looks like the options for changing the row amount and the count amount are both missing.

Resetting it fixed it.

Good that you have been able to fix it. Depending on the previous version you had installed, there might sometimes be migration issues which resetting should take care off.


TypeError: No registered converter was able to produce a C++ rvalue of type class

I get this error, any help ?
moldata = []
for elem in smiles:
mol=Chem.MolFromSmiles(elem)
moldata.append(mol)

The issue template asks you a series of questions that make it easier for us to help.
The fact that you've either deleted those or only answered a subset of them makes it more difficult for us to help, so I'm closing this issue.
Please feel free to edit the issue description to include the requested information and reopen the issue and then we'll try to help.


Cant create deposit_address

Hello when i request get deposit_address but not work :<
i'm using microkube and blockchain daemons working normal
i tested with curl call to create new address personal_newAccount working normal

Received: {"account_id":1}
Account Load (0.5ms)  SELECT  accounts.* FROM accounts WHERE accounts.id = 1 LIMIT 1
Currency Load (0.4ms)  SELECT  currencies.* FROM currencies WHERE currencies.id = 'eth' LIMIT 1
Wallet Load (0.5ms)  SELECT  wallets.* FROM wallets WHERE wallets.status = 'active' AND wallets.kind = 100 AND wallets.currency_id = 'eth' LIMIT 1
PaymentAddress Load (0.4ms)  SELECT  payment_addresses.* FROM payment_addresses WHERE payment_addresses.account_id = 1 ORDER BY payment_addresses.id DESC LIMIT 1
Currency Load (0.3ms)  SELECT  currencies.* FROM currencies WHERE currencies.id = 'eth' LIMIT 1
Account Load (0.3ms)  SELECT  accounts.* FROM accounts WHERE accounts.id = 1 LIMIT 1
(0.4ms)  BEGIN
PaymentAddress Load (0.4ms)  SELECT  payment_addresses.* FROM payment_addresses WHERE payment_addresses.id = 1 LIMIT 1 FOR UPDATE
Member Load (0.5ms)  SELECT  members.* FROM members WHERE members.id = 1 LIMIT 1
(0.4ms)  ROLLBACK
#<Faraday::ConnectionFailed wrapped=#<Net::OpenTimeout: execution expired>>
/usr/local/lib/ruby/2.6.0/net/http.rb:947:in initialize' /usr/local/lib/ruby/2.6.0/net/http.rb:947:in open'
/usr/local/lib/ruby/2.6.0/net/http.rb:947:in block in connect' /usr/local/lib/ruby/2.6.0/timeout.rb:103:in timeout'
/usr/local/lib/ruby/2.6.0/net/http.rb:945:in connect' /usr/local/lib/ruby/2.6.0/net/http.rb:930:in do_start'
/usr/local/lib/ruby/2.6.0/net/http.rb:919:in start' /usr/local/lib/ruby/2.6.0/net/http.rb:1470:in request'
/opt/vendor/bundle/ruby/2.6.0/gems/scout_apm-2.4.24/lib/scout_apm/instruments/net_http.rb:30:in block in request_with_scout_instruments' /opt/vendor/bundle/ruby/2.6.0/gems/scout_apm-2.4.24/lib/scout_apm/tracer.rb:34:in instrument'
/opt/vendor/bundle/ruby/2.6.0/gems/scout_apm-2.4.24/lib/scout_apm/tracer.rb:44:in instrument' /opt/vendor/bundle/ruby/2.6.0/gems/scout_apm-2.4.24/lib/scout_apm/instruments/net_http.rb:29:in request_with_scout_instruments'
/opt/vendor/bundle/ruby/2.6.0/gems/faraday-0.15.4/lib/faraday/adapter/net_http.rb:87:in perform_request' /opt/vendor/bundle/ruby/2.6.0/gems/faraday-0.15.4/lib/faraday/adapter/net_http.rb:43:in block in call'
/opt/vendor/bundle/ruby/2.6.0/gems/faraday-0.15.4/lib/faraday/adapter/net_http.rb:92:in with_net_http_connection' /opt/vendor/bundle/ruby/2.6.0/gems/faraday-0.15.4/lib/faraday/adapter/net_http.rb:38:in call'
/opt/vendor/bundle/ruby/2.6.0/gems/faraday-0.15.4/lib/faraday/request/url_encoded.rb:15:in call' /opt/vendor/bundle/ruby/2.6.0/gems/faraday-0.15.4/lib/faraday/rack_builder.rb:143:in build_response'
/opt/vendor/bundle/ruby/2.6.0/gems/faraday-0.15.4/lib/faraday/connection.rb:387:in run_request' /home/app/config/initializers/faraday.rb:13:in run_request'
/opt/vendor/bundle/ruby/2.6.0/gems/faraday-0.15.4/lib/faraday/connection.rb:175:in post' /home/app/lib/peatio/wallet_client/ethereum.rb:126:in json_rpc'
/home/app/lib/peatio/wallet_client/ethereum.rb:16:in block in create_address!' /home/app/lib/peatio/wallet_client/ethereum.rb:15:in yield_self'
/home/app/lib/peatio/wallet_client/ethereum.rb:15:in create_address!' /home/app/app/services/wallet_service/ethereum.rb:12:in create_address'
/home/app/app/workers/worker/deposit_coin_address.rb:23:in block (2 levels) in process' /opt/vendor/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/locking/pessimistic.rb:72:in block in with_lock'
/opt/vendor/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/database_statements.rb:232:in block in transaction' /opt/vendor/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/transaction.rb:189:in within_new_transaction'
/opt/vendor/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/connection_adapters/abstract/database_statements.rb:232:in transaction' /opt/vendor/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/transactions.rb:211:in transaction'
/opt/vendor/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/transactions.rb:310:in transaction' /opt/vendor/bundle/ruby/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/locking/pessimistic.rb:70:in with_lock'
/home/app/app/workers/worker/deposit_coin_address.rb:19:in block in process' /home/app/app/workers/worker/deposit_coin_address.rb:18:in tap'
/home/app/app/workers/worker/deposit_coin_address.rb:18:in process' lib/daemons/amqp_daemon.rb:60:in call'
lib/daemons/amqp_daemon.rb:60:in block (2 levels) in <main>' /opt/vendor/bundle/ruby/2.6.0/gems/bunny-2.14.1/lib/bunny/consumer.rb:56:in call'
/opt/vendor/bundle/ruby/2.6.0/gems/bunny-2.14.1/lib/bunny/channel.rb:1768:in block in handle_frameset' /opt/vendor/bundle/ruby/2.6.0/gems/bunny-2.14.1/lib/bunny/consumer_work_pool.rb:108:in block (2 levels) in run_loop'
/opt/vendor/bundle/ruby/2.6.0/gems/bunny-2.14.1/lib/bunny/consumer_work_pool.rb:103:in loop' /opt/vendor/bundle/ruby/2.6.0/gems/bunny-2.14.1/lib/bunny/consumer_work_pool.rb:103:in block in run_loop'
/opt/vendor/bundle/ruby/2.6.0/gems/bunny-2.14.1/lib/bunny/consumer_work_pool.rb:102:in catch' /opt/vendor/bundle/ruby/2.6.0/gems/bunny-2.14.1/lib/bunny/consumer_work_pool.rb:102:in run_loop'

forgot change geth rpc url on wallet seed :D


feat(ui) enable sorting by STATE in process instance list view

Implements #440

@nitram509 thank you for your contribution. :tada:  I'll have a look at your PR in the next few days. :eyes:

@nitram509 note that there is an issue with the sorting (not only with the new one). On the first click, the icon (i.e. the arrow) doesn't change. :sweat_smile:


How to set Speech-to-text for BING?

Hi!
trans -engine BING -p   ru:en 'Страна мечты!' Dream country! Voice output isn't available for English
How to set Speech-to-text for BING?

Speech-to-Text for Bing has been broken for a while, I'm afraid to say...

Thank you, I get it!
Let's try to wait…
2020 Jun 23; 09:28 PM


ASE Internal - Isolated service plan is not connecting to app gateway for public internet

I have container app deployed in isolated ASE-internal subnet.. when i try to connect to my application gateway the communicate to public internet is not working...
if any documentation for isolated ase to app gateway will be helpfull

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e30dfd76-2a83-bd21-2153-85e32894014e
Version Independent ID: 9dca62e8-0aef-10eb-b2d3-2ab12087f90a
Content: Integrate ILB App Service Environment with Application Gateway - Azure
Content Source: articles/app-service/environment/integrate-with-application-gateway.md
Service: app-service
GitHub Login: @ccompy
Microsoft Alias: ccompy

@askprasanth Does This Doc give the examples you are looking for? If not, could you elaborate a bit more on what you are looking for?

@askprasanth I would have a look at the gateway required VNET integration section under this doc for some troubleshooting tips. I would also check your firewall rules as well.
Let us know what you find so we can assist you further.

Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.


No compatible version found<EMAIL_ADDRESS>

Full error segment:
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\HP Sprout\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v7.7.4
npm ERR! npm  v4.3.0
npm ERR! code ETARGET

npm ERR! notarget No compatible version found<EMAIL_ADDRESS>npm ERR! notarget Valid install targets:

Hope any body could help me out of this. I already stuck here for several hours.
Thanks.

No idea how to reproduce this, sorry. Is this still an issue for you?

@LinusBorg I changed vue to older version and also downgraded some of depends packages. And now it could work.
By the way, I tried the template(changed nothing) on my Mac book and it worked fine.

That's weird, but seems to be a windows&node/npm problem at its core.... Not sure what we can do about this :(

@LinusBorg  It's possible.  But I am not familar about this. 😞 .  Thanks for your kindly reply.


Analysis server should be able to provide information about all projects, their SDKs, etc.

A user may open a folder containing multiple projects which may require different SDKs. The server should be able to tell us all of the projects (context roots?) and some information about the SDK required for each.
I don't have exact requirements for this but this case can be used to discuss. A couple of questions:

How does the server locate SDKs that can be used? Should the editor provide a set of SDKs it knows about (which could be a combination of things from PATH and specified by the user)
Should the server provide information required for operations like "restore packages" or should the IDE know how to handle project types (for ex. Flutter has its own commands for package restore, not using pub get)
How does the editor decide which VM/analysis server snapshot to invoke initially?

Currently in Dart Code we're doing something like this (note: both SDK paths can be override explicitly by the user, and those will always take precedence over anything we find ourselves):

Check if we're in a Fuchsia tree and have a project that does not appear to be aa "vanilla flutter" project (one that has sdk: flutter in its pubspec)

If so, we use the Flutter and Dart SDKs from this trees local cache

Check all open projects to see if any are Flutter (contain sdk: flutter in pubspec).

"Open projects" currently means anything the user has explicitly opened as a WorkspaceRoot
In vNext we expect to prompt the user to automatically add any folder we found a pubspec in
In future, we would use whatever this case results in
If so, we search for Flutter SDK in .packages, then FLUTTER_ROOT then PATH and use the Dart SDK from its local cache

Otherwise we're "plain Dart" and look on PATH for the SDK. If we don't find it on PATH but we did manage to locate a Flutter SDK above, then we will fall back to the Dart SDK in its local cache

Once we have those SDKs, we use them for everything. We use them to spawn the analysis server and also execute all commands for all projects (eg. if you open a Dart CLI and Flutter project, we'll use the Dart SDK inside Flutter for everything, including things like pub get).

I don't think this is super relevant anymore. It wasn't particularly concrete, and with LSP a lot of logic that would go in the client is (or could be) in the server.
(I'm also unsure why I was expecting to ask the server about SDKs when we can only use a single SDK for an analysis server, and we need to know where the SDK is before we could start the server).


Failed to use generated tilesets using -e command with Mapbox gl js

Hi, not sure this issue should go to tippecanoe or Mapbox gl js
I was using tippecanoe -e tmp -L test:test.geojson and tried to get the pbf tilesets to work with Mapbox gl js. The generated tilesets worked for tilelive, but not Mapbox gl js, it was complaining not able to decode the pbf received. Is pbf from tippecanoe different from mvt?
Thank you.

The -e flag was an external contribution (https://github.com/mapbox/tippecanoe/pull/386) so I haven't used it myself extensively, but it has essentially the same effect as writing the tiles to .mbtiles and then extracting them to a directory with mbutil.
The only thing I can think of is that maybe tilelive is serving compressed tiles from your tmp directory and GL-JS is thinking for some reason that they would be uncompressed. But pbf and mvt ought to be synonyms.

Hi,
I was able to solve the problem just by adding a content-type header when responding to Mapbox gl js pbf requests from http sources (for instance S3).
Is pbf is gzipped by nature?
Thanks.

Great, I'm glad you got it working. Tippecanoe will always compress tiles unless you use the --no-tile-compression option. Some software (like tippecanoe-decode) will look for a compression signature and work with either compressed or uncompressed tiles, but the general expectation is that tiles will always be compressed.


Incomplete Graph Batch Instance: Missing EntityDetail DeployedDatabaseSchema and it's relationships

The graph batch instance polled by the HMS connector from data engine is described as below:
1: 2023-02-06 14:27:57.500 EST INSTANCE test_server_feb BatchInstancesEvent
EntityDetail - Database data-engine::spark.default
EntityDetail - Connection data-engine::spark.default.connection
EntityDetail -  ConnectorType data-engine::spark.default.ConnectorType
EntityDetail -  Endpoint data-engine::spark.default.Endpoint
EntityDetail -  RelationalDBSchemaType data-engine::spark.default.schemaType
Relationship - ConnectionToAsset
 : E1 Connection  : E2 Database
Relationship - ConnectionConnectorType
 : E1 Connection  : E2 ConnectorType
Relationship - ConnectionEndpoint
 : E1 Connection : E2 Endpoint
Relationship - AssetSchemaType
 : E1 Database  : E2 RelationalDBSchemaType

The above graph batch instance is missing the following entityDetails and relationships:
EntityDetail - DeployedDatabaseSchema
Relationship - AssetSchemaType
:E1 DeployedDatabaseSchema  :E2 RelationalDBSchemaType
Relationship - DataContentForDataSet
:E1 Database  :E2 DeployedDatabaseSchema

where E1 is entityProxyOne and E2 is entityProxyTwo

@ilovechai I will add a configuration parameter which when set will include a DeployedDatabaseSchema entity as you expect.

@ilovechai Awaiting your testing feedback

@davidradl The batch instance still seems to be incomplete. Below is a batch instance event from today's run:
1: 2023-02-23 10:38:38.953 EST INSTANCE testserverfeb BatchInstancesEvent
EntityDetail - Database data-engine::spark.default
EntityDetail - Connection data-engine::spark.default.connection
EntityDetail - ConnectorType data-engine::spark.default.ConnectorType
EntityDetail - Endpoint data-engine::spark.default.Endpoint
EntityDetail - DeployedDatabaseSchema data-engine::spark.default.defaultDeployedSchema.default-deployed-schema
EntityDetail - RelationalDBSchemaType data-engine::spark.default.defaultDeployedSchema.default-relational-DB-Schema-Type
Relationship - ConnectionToAsset
 : E1 Connection : E2 Database
Relationship - ConnectionConnectorType
 : E1 Connection : E2 ConnectorType
Relationship - ConnectionEndpoint
 : E1 Connection : E2 Endpoint
Relationship - AssetSchemaType
 : E1 Database : E2 DeployedDatabaseSchema
Relationship - AssetSchemaType
 : E1 DeployedDatabaseSchema : E2 RelationalDBSchemaType

I see the DeployedDataSchema and the Relationship AssetSchemaType between DeployedDatabaseSchema and RelationalDBSchemaType which is correct, but I don't see the Relationship
Relationship - DataContentForDataSet
:E1 Database  :E2 DeployedDatabaseSchema

instead I see an extra relationship
Relationship - AssetSchemaType
 : E1 Database : E2 DeployedDatabaseSchema

Ah I see - I will correct the relationship

Waiting for positive testing feedback from @ilovechai before closing

BatchInstanceEvent so far looks good to me.
1: 2023-02-24 12:38:23.793 EST INSTANCE testserverfeb BatchInstancesEvent
EntityDetail - Database data-engine::spark.default
EntityDetail - Connection data-engine::spark.default.connection
EntityDetail - ConnectorType data-engine::spark.default.ConnectorType
EntityDetail - Endpoint data-engine::spark.default.Endpoint
EntityDetail - DeployedDatabaseSchema data-engine::spark.default.defaultDeployedSchema.default-deployed-schema
EntityDetail - RelationalDBSchemaType data-engine::spark.default.defaultDeployedSchema.default-relational-DB-Schema-Type
Relationship - ConnectionToAsset
 : E1 Connection : E2 Database
Relationship - ConnectionConnectorType
 : E1 Connection : E2 ConnectorType
Relationship - ConnectionEndpoint
 : E1 Connection : E2 Endpoint
Relationship - DataContentForDataSet
 : E1 Database : E2 DeployedDatabaseSchema
Relationship - AssetSchemaType
 : E1 DeployedDatabaseSchema : E2 RelationalDBSchemaType

LGTM


Will no longer be updated to the Raku ecosystem

Hello,
Thank you for the time and effort you have put in what is now the Raku Programming Language.  The language and its ecosystem are moving forward.
This means that these distributions:

https://github.com/hoelzro/p6-algorithm-elo
https://github.com/hoelzro/p6-algorithm-lcs
https://github.com/hoelzro/p6-io-string
https://github.com/hoelzro/p6-pod-eod
https://github.com/hoelzro/p6-priorityqueue

will no longer be checked for updates by the Raku ecosystem.
This means that you will need to move your module to the zef ecosystem on the next update you make to these distributions.  Otherwise your update will simply not be seen by the ecosystem.
If you are no longer interested in maintaining these distributions, you can have these distributions moved to Raku Community Modules Adoption Center, where members of the Raku Community will take care of them.
This can be as easy as confirming that in a response to this issue.
Again, thank you for your time and efforts!
On behalf of the Raku Steering Council,
Elizabeth Mattijsen

Thanks for the notification @lizmat ! You can put all of those modules up for adoption.

Thanks for your reply!
I've given you the right to transfer these modules to raku-community-modules.  Once there, someone (probably me) will take care of them to move them to the zef ecosystem.

I've forked Algorithm::Elo, Algorithm::CLS and Pod::EOD, updated them and re-released to the zef ecosystem.  You can archive these now: transfer is no longer needed.

Thanks @lizmat ! I'll go ahead and archive those, then.


Updating MapKit to lastest version

Fixes issue reported here: https://forums.developer.apple.com/thread/107794
Chrome for Android made some changes that broke earlier versions of Apple MapKit JS, but this updated version fix it

@LukeMizuhashi Is there any way to get the latest Mapkit version merged within this repo? That would be extremely helpful, thank you very much!

I added a ver/ directory that will allow you to specify which version of Mapkit JS you'd like your build to use.
Let me know if that helps!

@LukeMizuhashi That's so awesome, thank you very much! I will immediately try the new solution.

Sorry about that! Bumped the version and thought that would update npm automatically as well. Needed to publish too, it seems. Just like the old days. :)
Should be good now.


Figure out how to do parenthesized LHS correctly

Back story (https://github.com/estree/estree/issues/194): ESTree/Acorn doesn't provide us enough information to distinguish between
fn = function () {};

and
(fn) = function () {};

causing tc39/test262 language/expressions/assignment/fn-name-lhs-cover.js to fail. As https://github.com/estree/estree/issues/194 attempts to find a solution in ESTree, we should find a way to patch Acorn so that we have this information for ourselves right now.
@devsnek assigning this to you as you've done some Acorn work recently.

Aha, Acorn provides a preserveParens option that we can use.

If this option is true, parenthesized expressions are represented by (non-standard) ParenthesizedExpression nodes that have a single expression property containing the expression inside parentheses.

Shouldn't be too hard to fix the test then.

Yes we should definitely use that option, otherwise we're missing https://tc39.github.io/ecma262/#sec-grouping-operator-runtime-semantics-evaluation


git push pre-receive hook declined

Python app fails to deploy because of declined git pre-receive hook. Other python apps seem to be fine.
Is there a way to see an error from that hook
Tailed log flynn -c sbx-qa-us-east-1 -a gitreceive log -i -f, but nothing there when git push fails
$ git remote -v | grep sbx-qa-us-east-1
sbx-qa-us-east-1	https://git.flynn-sbx-qa-us-east-1.nexus.bazaarvoice.com/pre-review-service.git (fetch)
sbx-qa-us-east-1	https://git.flynn-sbx-qa-us-east-1.nexus.bazaarvoice.com/pre-review-service.git (push)

$ git -c http.sslVerify=false push -f sbx-qa-us-east-1 HEAD:refs/heads/master
Counting objects: 203, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (120/120), done.
Writing objects: 100% (203/203), 74.30 KiB | 0 bytes/s, done.
Total 203 (delta 78), reused 188 (delta 71)
-----> Building pre-review-service...
-----> Python app detected
-----> Installing requirements with pip

-----> Discovering process types
       Procfile declares types -> web
-----> Compiled slug size is 34.04 MiB
-----> Creating release...
=====> Scaling initial release to web=1
-----> Waiting for initial web job to start...
-----> WARN: scaling initial release down to web=0 due to error
remote: ERROR: Initial web job failed to start
To https://git.flynn-sbx-qa-us-east-1.nexus.bazaarvoice.com/pre-review-service.git
 ! [remote rejected] HEAD -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.flynn-sbx-qa-us-east-1.nexus.bazaarvoice.com/pre-review-service.git'

the same issue with nodejs app on both qa-us-east-1 and prod-us-east-1

This usually means that the application failed to start. Check flynn log --init

@titanous thanks for the lead.  I didn't even think about it. Looks like the deployed app logs errors during git push.


show_network() should display connected nodes

Currently, one has to dig through the DB or iterate through every node to figure out what's connected to a network.
This is needed for times like these:
$ haas network_delete random-network
Unexpected status code: 409
Response text:
{"msg": "Network still connected to nodes", "type": "BlockedError"}

If we showed connected nodes (+ maybe the channel, NIC,  switch and port name), this would allow all sorts of configuration goodness.
Maybe we could just include the output of show_node() for each node?

Hey @xuhang57. As you are doing your query work, would you mind including this?
Thanks!

I've also notice this to be an active issue with no apparent work-around (other than guessing). This information is critical to the project_detach_node command, which is a prerequisite for project_detach_node.

This will be useful (necessary?) for the many to many project:network relation to work.
e.g. to remove a project's access to the network all nodes on that project would first need to be disconnected from the network. For this to happen it needs to be possible for the network creator to see which nodes are connected to the network.
What is the status of this? I had been planning to include it as part of #545


Upload file gives body error with UploadFile

Description
I am having issues uploading a file to a FastAPI server. I found similar issues:
#1367  and #405
However, there was no solution. The issue is that it works with small sized files, but when a file is bigger than 100Kb it does not work. It looks like the reading of the file does not finish before trying to run the other tasks like writing.
Code sample
import uvicorn
from fastapi import FastAPI, File, UploadFile
from fastapi.responses import FileResponse
import aiofiles

app = FastAPI(title='Untitled', description='doThings', version='0.0.1')

uploads = 'uploads'
uploads_dir = pathlib.Path(os.getcwd(), uploads)

@app.post('/api/upload/')
async def upload_file(file: UploadFile=File(...)):
    """
    Upload the file to be processed.
    """
    print(file)
#    async with aiofiles.open(file.file, 'rb') as fin:
#       exfile = fin.read()
    file_name = pathlib.Path(uploads_dir, file.filename)
    async with aiofiles.open(f'{file_name}', 'wb') as f:
        await f.write(await file.read())
    return {'filename': file.filename,
                    'content-type': file.content_type}

if __name__ == '__main__':
    uvicorn.run('main:app', host='<IP_ADDRESS>', port=5003, log_level='info')

Output
The error happens just when it tries to read the file. I have tried it only with the return and it does not work, neither. I have run many tests and I don't get where the error comes.
This is the output of the uvicorn server:
INFO:     Started server process [7108]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:5003 (Press CTRL+C to quit)
INFO:     <IP_ADDRESS>:52854 - "POST /api/upload HTTP/1.1" 307 Temporary Redirect
Did not find boundary character 80 at index 2
INFO:     <IP_ADDRESS>:52855 - "POST /api/upload/ HTTP/1.1" 400 Bad Request
WARNING:  Invalid HTTP request received.

And in Postman I get this error message:
{
    "detail": "There was an error parsing the body"
}

Environment
OS: Windows 10
Python: Python 3.8.6
FastApi 0.61.2
Starlette 0.13.6
Pydantic 1.7.2

What are you using to upload the file?

I made the tests with Postman v7.36.0.

@llorencs I think it's a postman bug.
I've adjusted your script a bit (added os and pathlib``modules as well as manually created the uploads` folder).

Then tested with small file in postman: worked.
Then tested big file (16mb) in postman: fail
Then tested big file (16mb) with insomnia: worked
Postman bug documented here and seems to be still valid: https://github.com/postmanlabs/postman-app-support/issues/576

Hello, following this, I have tested it directely with a requests snippet and it worked correctly. So, it can be closed.

Thanks for the help here everyone! :clap: :bow:
Thanks for reporting back and closing the issue :+1:

Sorry for commenting something totally unrelated to a closed bug, but google brought me here.
I had the same error, but did not use postman. In my case it was a kubernetes deployment. The solution was that the helm chart set the root fs to readonly.
Hope someone finds this helpful in the future.

Sorry for commenting something totally unrelated to a closed bug, but google brought me here.
I had the same error, but did not use postman. In my case it was a kubernetes deployment. The solution was that the helm chart set the root fs to readonly.
Hope someone finds this helpful in the future.

hey boun I am literally facing the same issue my fastapi is deployed on k8s working fine for small json upload file but failing for large jaon input
pls can you help me solving this issue . i am really not much aware abt helm charts


Create release for v1.3.1

With go modules being announced https://blog.golang.org/modules2019 go get will now download v1.3.0 because it is the most recent tag.
Can the lastest master be tagged with v1.3.1?

Ah hah. I missed that announcement.
Will do!  I am currently out if the country for work without my personal laptop.  So I'll have to wait until around Xmas when I am back.

Thanks @eduncan911
Enjoy your xmas.

As a workaround to this issue, the following can be added to go.mod to get the latest commit
require (
    github.com/eduncan911/podcast v0.0.0-20171210162110-10213c61cee5
)

Ah yes, getting to this soon! Was playing with GitHub actions for a new CI pipeline which would auto-tag.
Thanks for the poke

Going to close this for now.  About to make another release soon with all the changes once I verify the new code, tests, and github actions pipeline - to do it all for me going forward.
Going to also delete the develop branch as  some don't follow it.


Mention non-ascii characters also not supported. EG Aarsø will not sync to AzureAD

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 3b05a56d-f714-2d99-747e-b3150f581f38
Version Independent ID: e8924d3f-20e7-6ce2-2279-cec010e7d3f3
Content: Prepare for directory synchronization to Microsoft 365 - Microsoft 365 Enterprise
Content Source: microsoft-365/enterprise/prepare-for-directory-synchronization.md
Service: o365-administration
GitHub Login: @kelleyvice-msft
Microsoft Alias: kvice

@richard-artes Thank you for your feedback. We have added a note to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/6504
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @richard-artes Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


install_script.sh: Remove bashism

Replaced ${BASH_SOURCE[0]} by $0.

sh install_script.sh failed in Ubuntu,
because the default shell isn't bash.

Coverage remained the same at 45.213% when pulling 452688da228a11a2269eb0b663da423faa340f28 on n-riesco:patch-1 into 4d5c8b81a6e45d16788640baf4be80ba15419987 on pprzetacznik:master.

Thanks for that!


Prepare for the P3 conversion

Fixes #88

This change is

Reviewed 12 of 13 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

a discussion (no related file):
Probably missing the theme/lumo/*.styles.html step.

Comments from Reviewable

Review status: 11 of 15 files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Previously, platosha (Anton Platonov) wrote…
Probably missing the theme/lumo/*.styles.html step.

Done.

Comments from Reviewable

Reviewed 4 of 4 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Update documentation

This can be previewed here.

Coverage remained the same at 98.941% when pulling f7b173e646b30fd09081923b0afcd92dbd21986b on docs into aac4033dc18843e0aaa11a84f41b3c4193cb9a76 on master.

Coverage remained the same at 98.941% when pulling 8ff5ea62f2f84273c824ce837a1a215e21f5e96d on docs into aac4033dc18843e0aaa11a84f41b3c4193cb9a76 on master.

Coverage remained the same at 99.029% when pulling 8766c58d602447e6572b3aaf32818aa8e565e87d on docs into 7a55f71dcdb015a9d05f89b30d929c743c477eae on master.

Changes Unknown when pulling c38bf2906d2d03427dfc3d21264e6964e9ce54da on docs into ** on master**.

Coverage remained the same at 99.069% when pulling 9ab33e2ae0b40d23c7710eb0e4acef72b370fd74 on docs into bb790e790a3850c66c7f8a4bf049379bce8c320f on master.

Coverage remained the same at 99.069% when pulling 0e5cb683670e63c94d32ed0b26c1c67443349bc6 on docs into 77327961ee289620a2eca92fe6f772604fb2d64f on master.

Coverage remained the same at 99.069% when pulling 0e5cb683670e63c94d32ed0b26c1c67443349bc6 on docs into 77327961ee289620a2eca92fe6f772604fb2d64f on master.