Horrible Level

Not sure if it is completable.  Therefor it will tend to fall forever
Because of how the engine works it is solvable.
Two important parts are here at play:

Only visible tiles and some additional tiles around the border are getting "update ticks" and are therefor alive.
The map has no boundaries

Given that you can collect the first diamond. Then push the boulder to the right to escape between the boulders and the pets. Then walk right "out of the map", walk down and then walk left (lower than the second diamonds position.
At some point you will come close to the second diamond and it will get update ticks and therefor fall to your screen.
To complete this level you do need to know a lot, about the engine and the level haha. Else you will never find the second diamond haha
Thanks for sharing!

I can not add this level to the "official" levels in the game. But I can make a sub menu "Awesome Community levels" and add the level there.
What are your thoughts?

Thanks for the reply. Yes one of the things I noticed is that not all the
rocks fall out due to the screen size.  I got out at one point but got lost trying to
find the diamond!. The idea behind the pets is to release them and start a
"war", but you have to stay inside the pets to be protected from explosions
or enemies. OTOH if you get too close to the pets you can also get stuck
and unable to move at all. It's a lot of fun!
I am happy for you to include this as a community level. If I get some time
I will improve it a bit. I think it needs some solid border to avoid
getting lost as that is just annoying.
On Fri, 7 Dec 2018 at 07:13, Jordy Moos<EMAIL_ADDRESS>wrote:

I can not add this level to the "official" levels in the game. But I can
make a sub menu "Awesome Community levels" and add the level there.
What are your thoughts?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JordyMoos/elm-pixel-boulder-game/issues/146#issuecomment-445013857,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADXYfxc5hbL2s6LEjDNz2LQJuHPSaIlaks5u2XpNgaJpZM4ZHL8j
.

.
Hahaha nice

The idea behind the pets is to release them and start a "war", but you have to stay inside the pets to be protected from explosions or enemies.
I really like the creativity in your idea.

The reason that it currently does not work as planned is because of the "control" attached to the Enemy and Pet.
----- Technical stuff here
This is the rest of the levels configuration, which gets attached to the "scene" you create via de easy editor.
https://github.com/JordyMoos/elm-pixel-boulder-game/blob/master/src/static/levels/test/sample.json
Both the Enemy and the Pet have this "control" attached to them:
{"type": "control", "data": {
        "control": {
          "type": "walkAroundAi",
          "data": {
            "previousDirection": "left",
            "nextDirectionOffsets": [-1, 0, 1, 2]
          }
        }
}},

This walkAroundAi lets you configure the "last direction you made" and also a list of next possible directions (based on your previous direction).
What happens is this: The previous direction was Left. -1 based on left is Down. Entity should go down if possible. If not possible try the next offset (0) which means the same direction as before untill a valid movement is found or the list is empty.
(There is a minor bug here, I messed up left and right on the offsets to its inverted lol, dont laugh)
Anyways this configuration will let the try to "take the corner" or else "follow his current direction". Which works wonderful if the enemy is actually next to a wall. He will just follow the wall. But if there is nothing around him them he will walk mini circles and wont really change position much.
With this said we can tune to control of our Pet:
{"type": "control", "data": {
        "control": {
          "type": "walkAroundAi",
          "data": {
            "previousDirection": "down",
            "nextDirectionOffsets": [0]
          }
        }
}},

----- End of the technical stuff
If we change the Pets control to this then the Pet will walk down and will continue to do so "forever".
So you can place Pets above the Enemies, separated by some Dirt or something that the Player needs to remove to release "the beasts" and let them be destroyed by the Enemies.

I think it needs some solid border to avoid getting lost as that is just annoying.

Yea I agree there is no end to it which is annoying. You can use the "Strong Wall" which can not be destroyed by the explosions.
Ps. I can easily add another textarea which shows the real configuration (which then the changed pets behavior can be tuned, which I also can supply) That way you can test your level with the alternative pets behavior.
What are your thoughts?


can i have this helm stop logic.

this is a feature request first.
i want to have a stop logic, but there are only  install/uninstall.
my logic is when we execute helm stop, it will scale the pod  replicas to 0.
my case is that when we have a small cluster but we  want to use the cluster more efficiently, it can help us rapidlly recover a running helm release pod, and without losing any thing in pvc. if we use helm delete, it may loose some thing ,pvc , dynamic ingress, etc . but use helm stop, it indeed runnig no pods, and make the cpu/memory resources availiable to the ohter.
we are on dev/test env , not production, so it will not have the same cluster size with the production.

helm update ... --set replicas=0 should do what that.
Just check the values.yaml file for the replicas part so you pass the correct value/s there.

Do you mind if I work on this?

nope, go right ahead!
Do keep in mind that Helm 2 and Helm 3 development has diverged at this point so any feature development going into Helm 2 will not port over to Helm 3. If you're fine with doing doubly duty (once Helm 3 is available), then go nuts! :)

I'd suggest writing this as a plugin first to see if this works as a proof of concept. See The Helm Plugins Guide for more information on writing plugins :)

@bacongobbler thanks for feedback. You are also right on the nuts part! :)
I am a noob, so have some patience with me!

@bacongobbler PR #4457 opened and ready for review.


Set up certificate for Test Arbeidsflate

Description
Ordered for Test environment. Tracking progress here: https://github.com/Altinn/altinn-platform/issues/787
Additional Information
No response
Tasks
No response
Acceptance Criterias
No response

Currently blocked by https://github.com/Altinn/altinn-platform/issues/787


chore: replace querystring with URLSearchParams

Fixes #106
Not sure of the performance implications, but it seems nice to avoid soon-to-be deprecated APIs.

thanks, that looks very clean. :+1:
I think querystring needs to be removed from package.json and the lockfile aswell pnpm remove querystring in packages/vite-plugin-svelte should do
Performance wise it may have a small impact as its used in multiple hooks, but one less external dependency is a plus too.

Didn't notice it was part of the dependencies, I thought that was imported from Node's builtin modules. Will remove that too.

Thanks!!


Acceleration multiplier is 1+2^(n-1) instead of 2^n

Using /tick command can show this clearly.

Run command /tick freeze
Use tiab to accelerate a furnace to x4, and put any item with furnace recipe into it
Run command /tick step 66, and the item isn't cooked completely
Run command /tick step 1, and the recipe is done

From above example we can see the furnace needs 67 ticks to cook an item with x4 acceleration, which is 3 times faster instead of 4 (which should be 50 ticks).
In addition, the actual acceleration multiplier for x8, x16, x32, x64, x128, x256 is x5, x9, x17, x33, x65, x129 correspondingly.

Oh no! Thanks for getting me this info. Ill have to see where the math went wrong. :(


[SVS-20] Filter out VB.NET projects globally

Globally filtering out VB.NET projects as a supported managed project.

LGTM


Sandbox nested example not found

Describe the bug
Trying to see the code for the nested target example for either Javascript or Typescript gives the
Not Found We could not find the sandbox you're looking for. error.
Reproduction
Go to https://react-dnd.github.io/react-dnd/examples/nesting/drop-targets, click Javascript or Typescript.

In fact, this happens for all examples I have tried.

Seems like a duplicate of #1963

indeed


IDOC clear user fields

clear ATTRIBUTES-PRESP and ATTRIBUTES-PWORK
set again when deserializing

implemented in https://github.com/larshp/abapGit/commit/26446249850631b50ed948888d9426b4eacf8133, closing


Crashes for first try, then stuck at connecting

Hi there,
after changing the partition table, I got the sketch successfully uploaded to my ESP32 dev board.
However, it fails to read any miflora data. Often it crashes a few time before performing a connection, but even then nothing else happens before it goes to sleeo mode:
`Starting Flora client...
Connecting WiFi...
.....
WiFi connected
Attempting MQTT connection...connected
Forming a connection to Flora device at c4:7c:8d:66:51:40

Connected to Flora
abort() was called at PC 0x401a780f on core 1

Backtrace: 0x40095324:0x3ffdaaa0 0x40095527:0x3ffdaac0 0x401a780f:0x3ffdaae0 0x401a7856:0x3ffdab00 0x4019513b:0x3ffdab20 0x400d31b1:0x3ffdab40 0x400d1627:0x3ffdaba0 0x400d1d91:0x3ffdac70 0x401af3c6:0x3ffdacc0
Rebooting...
ets Jun  8 2016 00:22:57
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:952
load:0x40078000,len:6084
load:0x40080000,len:7936
entry 0x40080310
Starting Flora client...
Connecting WiFi...
.....
WiFi connected
Attempting MQTT connection...connected
Forming a connection to Flora device at c4:7c:8d:66:51:40
Goi`
I tried two miflora devices (that work in the official app) and also changed the sleep wait to 120.
Any ideas?

Hi,
could you provide a full stack trace of the error via the EspExceptionDecoder? Check https://github.com/me-no-dev/EspExceptionDecoder .
Thanks,
Sidddy

potentially related to #10

Now, that's interesting. I installed the exception decoder tool and connected the esp32 via USB. I checked the console and copied the adress. When I opened the tool, it asked me for the .elf file. A quick google told me that I need to compile the sketch again. Did so, uploaded ... and it's not crashing anymore?
But sadly, it's not connecting, either. It gets into sleep before retrieving any data.
SLEEP_WAIT is set to 120
I guess this is a new issue then?
Starting Flora client...
Connecting WiFi...
.....
WiFi connected
Attempting MQTT connection...connected
Forming a connection to Flora device at c4:7c:8d:66:51:40
Goi

Oh wait .. I changed the MAC Adress to the other miFlora just to be sure. Now it's crashing again.
Starting Flora client...
Connecting WiFi...
......
WiFi connected
Attempting MQTT connection...connected
Forming a connection to Flora device at c4:7c:8d:65:5a:d5

Connected to Flora
abort() was called at PC 0x401a780f on core 1

Backtrace: 0x40095324:0x3ffdaaa0 0x40095527:0x3ffdaac0 0x401a780f:0x3ffdaae0 0x401a7856:0x3ffdab00 0x4019513b:0x3ffdab20 0x400d31b1:0x3ffdab40 0x400d1627:0x3ffdaba0 0x400d1d91:0x3ffdac70 0x401af3c6:0x3ffdacc0
Rebooting...
With the decoder it says:
Decoding stack results
0x40095324: invoke_abort at /Users/ficeto/Desktop/ESP32/ESP32/esp-idf-public/components/esp32/panic.c line 140
0x40095527: abort at /Users/ficeto/Desktop/ESP32/ESP32/esp-idf-public/components/esp32/panic.c line 149
0x401a780f: __cxxabiv1::__terminate(void (*)()) at /builds/idf/crosstool-NG/.build/src/gcc-5.2.0/libstdc++-v3/libsupc++/eh_terminate.cc line 47
0x401a7856: std::terminate() at /builds/idf/crosstool-NG/.build/src/gcc-5.2.0/libstdc++-v3/libsupc++/eh_terminate.cc line 57
0x4019513b: __cxxabiv1::__cxa_throw(void*, std::type_info*, void (*)(void*)) at /builds/idf/crosstool-NG/.build/src/gcc-5.2.0/libstdc++-v3/libsupc++/eh_throw.cc line 87
0x400d31b1: BLEClient::getService(BLEUUID) at C:\Users\xfleog\AppData\Local\Arduino15\packages\esp32\hardware\esp32\1.0.0\libraries\BLE\src\BLEClient.cpp line 340
0x400d1627: getSensorData(BLEAddress, bool) at C:\Users\xfleog\Documents\Arduino\flora/flora.ino line 66
0x400d1d91: setup() at C:\Users\xfleog\Documents\Arduino\flora/flora.ino line 214
0x401af3c6: loopTask(void*) at C:\Users\xfleog\AppData\Local\Arduino15\packages\esp32\hardware\esp32\1.0.0\cores\esp32\main.cpp line 15

Seems to be related to https://github.com/nkolban/esp32-snippets/issues/419#issuecomment-373467202

Agreed. The stacktrace shows that we can's really do anything about this crash in flora, it's an issue in the BLE coding. Please open an issue over there if the problem still exists.

That's totally right. I would like to keep this issue open or add a remark to the readme for future users.
Unfortunately this project is currently not in a working state even if it's totally not your (the project owners) fault.
This fact shouldn't be hidden to your users.


The default 'basePath' value doesn't work on Windows.

I use:

django
djangorestframework
drf-spectacular

I'm trying to test my openapi scheme, but It's not working.
Exploring the source code, I found some problem.
If my schema does not have the basePath parameter, it takes the default value /.
Then RefResolver (from prance) calls to_posix before urlparse.
In fs.py file:
def to_posix(fname):
    """
    Convert a path to posix-like format.

    :param str fname: The filename to convert to posix format.
    :return: The filename in posix-like format.
    :rtype: str
    """
    import sys

    if sys.platform == "win32":  # pragma: nocover
        import os.path

        if os.path.isabs(fname):
            fname = "/" + fname
        fname = fname.replace("\\", "/")
    return fname

If you call to_posix("/") on Windows, it will return "//".
Then urlparse will not be able to parse this value. And... this happened:
prance.util.url.ResolutionError: Cannot build an absolute file URL from a fragment without a reference with path!
As a temporary solution I use:
@pytest.fixture
def open_api_client(schema_tester):
    with patch("prance.util.fs.from_posix", wraps=lambda x: x):
        with patch("prance.util.fs.to_posix", wraps=lambda x: x):
            client = OpenAPIClient(schema_tester=schema_tester)
            yield client

But it can lead to other errors.

This seems like a prance issue, no?

This is probably a feature of prance that you haven't considered. 'basePath' is your parameter and its default value doesn't work on Windows. If you think prance is the problem, create a new issue!

It's been a while since I've used this package myself, and I don't have the capacity to fix this in the short term. PRs are welcome :+1:


Create acceptanceTests for multi-key per node usage

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


Update tags to include ARM64 build

Could you please update the tag to include the recently added build for arm64.

Latest is already available: https://hub.docker.com/r/jonasvautherin/px4-gazebo-headless/tags
Isn't that enough? I was planning on just waiting until PX4 1.13.1, which will include it.

Makes sense.


[Artemis] Replace missing property with a version from SB 3.0.6

My suggestion here is that we add a ${artemis-version} property back into the camel-spring-boot root pom.xml in the  instead.     This is probably my oversight - in 3.20.1, the ${artemis-version} property doesn't exist upstream but we added it into the root pom.xml in our product branch.
@avano @croway does that sound reasonable?


Server error when submitting a PR in the LicenseXML editor

The error message does not contain any information.  No information was found in the logs.
Note: this function does work in the development environment.  It may be configuration related.

@jlovejoy I did fix a similar issue, but after pushing the changes to production, I'm still getting an error.  If you could give it a try and let me know if you see the same thing.

This was due to the repo name being set to the test repo name.
This has been patched in production and I'll create a PR to fix this in a more permanent way.
@jlovejoy - This feature should now be working.


Working demo

Hi !
Just to inform you that I get a forbidden 403 error on your working demo when uploading an image but I guess it is normal right ?
Just wanted to let you know in case it is not because some people might think your plugin is not working :)

Hey @catuss-a,
I closed my bucket because some random ppl harrassed my s3 bucket so hard :) (They sent some large files and tried to dl)
This is why plugin looks not working.

Btw you can still limit on the client but not on s3 :(
Feel free to open PR for file size limitation on plugin options.

Alright thanks!

Unauthorized Access Alert
Hello GitHub users,
We regret to inform you that your GitHub account has been accessed without authorization. In order to protect your account's security, we urge you to reset your password and revoke access to any unauthorized individuals.
To reset your password and prevent any further unauthorized access, please click on the following link. We appreciate your prompt attention to this matter.
Thank you,
Your GitHub Security Team
Users Included:

@SMotaal
@mikesposito
@NidhiKJha
@V00D00-child
@SamuelSalas
@McOso
@OGPoyraz
@weizman
@nikoferroGudahtt
@NidhiKJha
@gantunesr
@nikoferro
@andreahaku
@andrepimenta
@weizman
@rickycodes
@mikespositowachunei
@kumavis
@OGPoyraz
@callumelvidge
@SamuelSalas
@shane-t
@cortisiko
@SMotaal
@ritave
@V00D00-childdestroyersrt
@eriknson
@micaelae
@Mrtenz
@rekmarks
@Andepande
@McOso
@FrederikBolding
@matthewwalsh0


missing field error

(Same as reported via Twitter)
We're using Hubcaps to create releases: https://github.com/semantic-rs/semantic-rs/blob/9d833599126b012485cf8c083c488e7cd41ed997/src/github.rs
The code runs after tests on Travis, where it sometimes fails with
GitHub(Codec(Syntax(missing field "field", 1, 132)))

Link: https://travis-ci.org/badboy/test-project/jobs/118362428#L771
I was not able to reproduce it locally (yet). The build runs with RUST_LOG=debug, but no Hubcaps logs are shown (didn't check if there are some in the code path we're triggering).
Seems like that field field belongs to FieldErr struct, but I don't know where it comes from at the moment.
The Git tag is already pushed when that release happens.
The error does not happen everytime. Some builds run just fine.
Any idea what's causing this or how we could debug this further?

Seems like it is created here (as part of ClientError): https://github.com/softprops/hubcaps/blob/a2af9488810c256aef7509182ab9634fbaf680e2/src/lib.rs#L250
Above is a debug! line, so in theory I should see logging statements.

D'oh! Figured I should actually enable env_logger in my own crate.

Ok, figured it out now.
https://travis-ci.org/badboy/test-project/jobs/118373494#L777
The body contains:
{
  "message": "Validation Failed",
  "errors": [
    {
      "resource": "Release",
      "code": "custom",
      "message": "Published releases must have a valid tag"
    }
  ]
}

Not sure if the GitHub API is wrong (or wrong documented), but Hubcaps might need to safe-guard against that.
And regarding my problem: it's likely a race condition.

Ah, thanks for all the specific info. I think just need to make FieldError.field and Optional String. The original structure was based on the info here. I'll make that change and do a bit more testing this weekend. It looks like there are more keys in json returned that I'm deserializing. Looks like each field message can have it's own optional message as well.
I'll try to get this squared away this coming weekend.
That's for reporting and thanks for the debugging work!

I send a tweet to GitHub for clarification as to me the API description reads like there should always be a field field. No answer yet.

Yea it seems like there would be a field with a value of tag in this case. Either way I want to make hubcaps a little more fail a little more gracefully for these cases :)

Thank you!

@badboy wanted to give you a heads up I pushed a release ( 0.2.1 ) with the fix for this

Thanks again!


Very long start of dolphin

Describe the bug
I use package kdePackages.dolphin. When running dolphin from terminal, it starts very long (about 5-6 seconds to open window and about 5 seconds to render file tree), and icons doesn't render. But when I do
export QT_PLUGIN_PATH=/nix/store/x4ghagmp94ynzp5qdkdvia72g3i80awi-qtsvg-6.7.1/lib/qt-6/plugins:$QT_PLUGIN_PATH

it starts and works fine
Steps To Reproduce
Steps to reproduce the behavior:

Run dolphin from terminal
export QT_PLUGIN_PATH (see above)
Run again

Expected behavior
dolphin starts fine
Screenshots
Details

Additional context
I discovered what was missing by accident: I opened empty link from okular, and its opened fine, and then compared env from within dolphin (using embedded konsole)
Default $QT_PLUGIN_PATH:

/home/[user]/.nix-profile/lib/qt-5.15.12/plugins
/home/[user]/.nix-profile/lib/qt-6/plugins
/nix/profile/lib/qt-5.15.12/plugins
/nix/profile/lib/qt-6/plugins
/home/[user]/.local/state/nix/profile/lib/qt-5.15.12/plugins
/home/[user]/.local/state/nix/profile/lib/qt-6/plugins
/etc/profiles/per-user/[user]/lib/qt-5.15.12/plugins
/etc/profiles/per-user/[user]/lib/qt-6/plugins
/nix/var/nix/profiles/default/lib/qt-5.15.12/plugins
/nix/var/nix/profiles/default/lib/qt-6/plugins
/run/current-system/sw/lib/qt-5.15.12/plugins
/run/current-system/sw/lib/qt-6/plugins

What added when running dolphin:

/nix/store/8s65nma4p7w9g3xrg0dhcdaf30xqrwvl-dolphin-24.02.2/lib/qt-6/plugins
/nix/store/d643rzaa4ccgi6wi0rbvy6n85fb7dbmz-kio-extras-24.02.2/lib/qt-6/plugins
/nix/store/ijpkkfnwijdmz8ri58ps5kpyn5gja8vq-sonnet-6.2.0/lib/qt-6/plugins
/nix/store/4r8chci91if4dy7b1z0aa0idzc4sd8mx-baloo-widgets-24.02.2/lib/qt-6/plugins
/nix/store/pfl409khj0vcpnsdjgv9vvlj7y3kjrks-baloo-6.2.0/lib/qt-6/plugins
/nix/store/mk2vwkbg1k0lk4pnjyf1ri3cv8fzpkgy-kio-6.2.0/lib/qt-6/plugins
/nix/store/v3jhz3qyikdphx8hpwx4g7fnsr6k8174-kiconthemes-6.2.0/lib/qt-6/plugins
/nix/store/5d4k2b9lkcpdvdxb8zcwwcs5wmzf54vd-kauth-6.2.0/lib/qt-6/plugins
/nix/store/p4wvcpm0sh6mp19lii0qww95l3i18dba-kwindowsystem-6.2.0/lib/qt-6/plugins
/nix/store/8brf5yhjrq975masmiv808nwpjf1f41d-kidletime-6.2.0/lib/qt-6/plugins
/nix/store/hm64nn6i0h9j8acqfscys88ds72i5232-kfilemetadata-6.2.0/lib/qt-6/plugins
/nix/store/s2bsay385g0q1vy2a1jvv3w8g4g3pfkn-ki18n-6.2.0/lib/qt-6/plugins
/nix/store/rj6xqgzyjzw9xqa2jbv9k3wh84h25nmq-qtdeclarative-6.7.1/lib/qt-6/plugins
/nix/store/ikqvl8jq0d7vlp25d9zlbh44m4hljahc-qtbase-6.7.1/lib/qt-6/plugins

Dolphin version: 24.05.1 - from unstable. With dolphin from stable (24.02.2) behavior is the same
I also use qt5ct + kvantum
Notify maintainers

@K900
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.33, NixOS, 24.05 (Uakari), 24.05.1503.752c634c09ce`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

Installing kdePackages.qtsvg fixes the problem


Failed stuck on WebView? Can't bypass cloudfare in nhentai extension!

Source information and language
Nhentai 1.4.37
Steps to reproduce
Since yesterday,
When I try to Open nhentai extention I get can't bypass cloudflare anymore?
When I click on webview, then I click to human confirmation, it says failed no matter how many times I ty! The site gets stuck in infinite loop in cloudflare secure checking?
Expected behavior
Nhentai bypass cloudflare!
Actual behavior
Nhentai doesn't bypass cloudflare!
Aniyomi version
0.14.3-6151 preview
Android version
Android 11
Other details
Redmi note 8 pro
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version <IP_ADDRESS>
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

Refer to the Solving Cloudflare issues section at https://tachiyomi.org/help/guides/troubleshooting/#solving-cloudflare-issues. If it doesn't work, migrate to other sources or wait until they lower their protection.


Request for Collapsible Search Results

Hello, while using grug-far, I noticed that the search results display a large amount of information, making it somewhat visually cluttered. I would like to suggest adding a feature to collapse search results, allowing users to expand and collapse specific content as needed. This would greatly enhance the readability and user experience. Thank you for your hard work, and I hope you consider this suggestion!

Do you mean like adding a fold per file? like in VSCode or idea, if there are multiple results you can fold single file.
Else you can just narrow down search using file/path filters.

Do you mean like adding a fold per file? like in VSCode or idea, if there are multiple results you can fold single file.
Else you can just narrow down search using file/path filters.

yes！like vscode

I think we can do something here, although the nvim fold API is sort of garbagio 😆
Need some feedback. What do you think of the following? I think the second one, where the file name is not part of the fold looks a bit better, right?
Although I don't use folds at all so I might be wrong here and the first one is the more practical usage wise.
The idea is that you would use those with the regular fold z... keybindings and we would have an option that would control whether we auto-fold immediately on search or not.

I vote for option 2, as it is more informative, and contains at least one search query result. Would be amazing if this will work with standard z... keybindings. Less api to write this way (not an expert)?

added foldcolumn as well to make it more obvious that there are folds there:

Implemented the following options:
  -- folding related options
  folding = {
    -- whether to enable folding
    enabled = true,

    -- sets foldlevel, folds with higher level will be closed.
    -- result matche lines for each file have fold level 1
    -- set it to 0 if you would like to have the results initially collapsed
    -- See :h foldlevel
    foldlevel = 1,

    -- visual indicator of folds, see :h foldcolumn
    -- set to '0' to disable
    foldcolumn = '1',
  },

@ian-ie so for your case, just call grug-far with folding.foldlevel = 0

Thank you for your help, but as a beginner, I'm encountering an error with lazyvim when I try 'za' – it says 'not fold'. Even after executing 'set foldlevel=1', 'zm' doesn't seem to respond.

Thank you! Now it's working just as I had hoped!


Split commands from shell script in dockerfile

This pr adds 2 functions in utils/general.py:

split_shell_script()
This functions split a shell script(in string format) into 3 types
of statements: variable, command and branch(if and case).
A dictionary is used to store the infomation of the statement.
It has following keys:

type: statement type(variable, command, if or case)
content: statement sentence(eg. 'apt-get update')
name: (only for variable) variable name
value: (only for variable) variable value
(more keys will be added when we move on to parsing the branches)
returns a list of statements

parse_shell_script()
This function parse a shell script to get a command list.
First it calls split_shell_script() to get a statement list,
For command, it calls parse_command() to parse the command
and extract command name, options and words.

Works towards #682.
Signed-off-by: WangJL<EMAIL_ADDRESS>

Here are my local test output on
https://github.com/docker-library/python/blob/06d7952f07eae237666f2fd0ccf6189a5d8ee83c/3.9-rc/buster/Dockerfile.
test_statments.txt
in the test_statements.txt:
statements part are return value statements in split_shell_script()
commands part are return value commands in parse_shell_script()

And this is the output on
https://github.com/docker-library/golang/blob/69b2283d45ae89c84383d41a9b1aab4d84e5cbae/1.14/buster/Dockerfile
This dockerfile contains a if-statement and a case-statement.
Currently we are not handling branches.
test_statments-2.txt

@ForgetMe17 I wonder if we can make use of your shell script parser to parse all RUN commands. What do you think about arranging your statement dictionary like this:
# assuming each element in the list is a statement
[{"variable": {"name": "dpgkarch", "value": "$(...)"}, "content": "..."},
 {"command": {"name": "apt-get",
                       "options": ["--no-install-recommends", "-y"],
                       "words": [...]}, "content": "...."},
 {"branch": {"type": "if", "statements": [ ... ] # statements within the if ... fi block},...]

This way, you capture all the elements you are interested in within one dictionary which you can use throughout the code.
The logic looks good to me. Good job!

Thanks for your advice! I will work on rearrange my statements dictionary and move on to implement a function to parse if and case statements. I will push another commit in this pr.

In the new commit i remove 1 function in previous commit and add 3 new functions.
remove 1. parse_shell_script()
no longer need this since in this commit, i move the parsing
command function into split_shell_script().
add 1. parse_shell_variables_and_command()
given a sentence, classify the variable and command type,
and then parse it.
add 2. parse_shell_if_branch()
extract all commands in the if sentence, return a branch dictionary.
add 3. parse_shell_case_branch()
extract all commands in the case sentence, return a branch dictionary.
my local test result are:
1-14.txt for (https://github.com/docker-library/golang/blob/69b2283d45ae89c84383d41a9b1aab4d84e5cbae/1.14/buster/Dockerfile)
3-9-rc.txt for (https://github.com/docker-library/python/blob/06d7952f07eae237666f2fd0ccf6189a5d8ee83c/3.9-rc/buster/Dockerfile)

Making another PR on this issue.
Closing.


Fix the issue of multiplying base learning rate twice.

Details please see issue #3

Ah I'm sorry for not responding earlier. The lines should not be commented out, but the final multiplication should be removed.
I think another user just sent in a pull request for the same issue - so I think you're off the hook!
Thanks again!

Ha, yes the fix is just to leave out the multiplication part. Good to know it is solved.


Update docs, the hint and urgency functions do not compile on macOS

Unsure about other functions. Came across these two that failed to compile in a project.

sorry, totally overlooked this
thank you

sorry, totally overlooked this
thank you


pg1350-DR Footprint Origin Off

I was using the pg1350-R footprints until I decided to move to a matrix setup and updated them to use the pg1350-DR footprints.  When I did it, the keys all shifted up by approximately .25u.  I was able to update the footprint manually to fix this, but it might be good to fix this programmatically if you made it with a Python script.
Link to manually fixed footprint:
https://gist.github.com/Albert-IV/caa8f16e5f8a3b93db33d6508f415533
Before using pg1350-R footprints:

After changing to pg1350-DR:

This is expected behavior, and noted in the README, though maybe not with enough importance:

The center of the footprint is placed on the center of the diode to help with PCBA,

And yes, it's basically 0.25u

As for the solution, it's possible to have D variants with both shifted and unshifted origins easily, but it's the same amount of problem changing from the version where PCBA is not a concern to the one where it is.
Alternatively, we could have the origin fixed on the center of the diode regardless of the variant, but that would be a bit weird when using the non-D variants.

As someone not familiar with PCBA, why does the origin matter on the footprint?  Personally I'd think that having the origin be the middle of the switch would be really important (at least for me).  This way swapping between footprints would be somewhat reliable between libraries.

For PCBA you need to provide the center of the component to be assembled. Given that the diode is part of the switch footprint already, it'd make the most sense to use the switch itself for creating the position file.

After I started working with the PCBA files I see what you mean.  I can close this for now.


Are secure timestamps omitted intentionally?

Question
Having a quick look at the signature process I can't see any queries to secure timestamping services. Including a signed timestamp is a critical piece of functionlity for almost any scenario involving digital signatures.
There's a citition from the cosign course on Edx

Because these keys persist only long enough for signing to take place, signature verification ensures that the certificate was valid at the time of signing.

If a signature is valid it's impossible to guarantee that the key wasn't expired at the time of signing without usage of signed timestamps from third party. In other words, if I compromised an expired "keyless" key pair, what prevents me from signing another payload and claiming that the signature is valid?
Upload to transparency log can help to reveal cheating with signatures, but at the time of writing there're no checks for consistency of subsequent log entries in transparency log e.g. that an entry is older than a pervious one.
So, my questions are:

what is the protection from using expired "keyless" pairs and claiming that signatures are valid?
what is the design rationale for not including signed timestamps into signatures like it's done in MS Authenticode?

what is the protection from using expired "keyless" pairs and claiming that signatures are valid?

We use the transparency log (Rekor) inclusion proof as a timestamp. It serves the same purpose but has a different API than traditional TSA's.
I would like to add support for RFC3161 TSAs in addition.
There's some discussion here: https://blog.sigstore.dev/its-ten-o-clock-do-you-know-where-your-private-keys-are-5c869cf53234

consistency of subsequent log entries in transparency log e.g. that an entry is older than a pervious one.

Agreed, there is no monitoring that verifies monotonicity of the integrated time in Rekor. Even then, the integrated time in an entry can be mutated in the underlying database. There's also no way of adding an external or third party timestamp in our APIs, with either an RFC 3161 timestamp or other timestamping protocols.
I agree that there is room to add this data into Rekor entries in a variety of ways, to allow clients to have some external verification besides trust in Rekor and its database.

what is the protection from using expired "keyless" pairs and claiming that signatures are valid?

Right now as Dan mentioned, the protection is coming from using the integrated time of the entry as a proxy for when the signature was created (the sig is part of the entry).
See also https://github.com/sigstore/rekor/issues/824, @haydentherapper is moving the timestamper into a separate repo, where we can host a TSA.

Upload to transparency log can help to reveal cheating with signatures, but at the time of writing there're no checks for consistency of subsequent log entries in transparency log e.g. that an entry is older than a pervious one.

One more addition: Rekor supports an RFC 3161 timestamp type, which means you can upload timestamps on a cron or scheduled job to Rekor for more assurance of its integrated time. That can provide some guarantees that entries are monotonic in relation to those timestamps.

the protection is coming from using the integrated time of the entry as a proxy for when the signature was created (the sig is part of the entry)

Can you elaborate on that? I'm just trying to understand the security guarantees. Let's assume I rely only on the project tooling without additional code written and additional checks performed on my side - just using cosign sign/sign-blob, cosign verify with support for rekor checks (experimental enabled) and funcio "keyless" scheme like it's suggested in various posts, documentation and EDX course.
From my perspective the process can guarantee the following: the signatures are trusted as long as all the signing keys have never been compromised despite the expiration time.
If any of the signing key pairs used was compromised - I cannot trust the root any longer (seems weird, but I need a revokation mechanism for expired keys), because the only way to stop the attack is to remove trust from root key.
This eliminates the advantages of using fulcio and "keyless" signing scheme and gets us back to the security guarantees similar to static pub/priv key pair.
Am I right?

Walking through the signing and verification flow, focusing on where timestamps are referenced:
On signing:

Fulcio creates a short-lived certificate, associating an identity with an ephemeral public key
The certificate is uploaded to a transparency log along with the signature and artifact hash
The log returns a signed bundle which includes the inclusion timestamp and artifact hash, and this is persisted with the certificate and signature (you can also ask the log for a proof of inclusion)

On verification:

The Fulcio certificate's signature is verified from Sigstore's root of trust (shipped with Cosign), and ignoring time
The log presents the inclusion time of the entry, either from the signed bundle or requesting it from the log <-- We'll come back to this step
A verifier checks that the inclusion time is before the certificate's expiration time. If so, then the verifier knows that the certificate was valid when the artifact was signed, so we can trust the certificate, and therefore trust the ephemeral public key to verify the artifact signature.

Step (2) of verification relies on the log to give you the inclusion time. That time is currently not signed by the log, so it could be mutated by a log operator without detection, which would result in a denial of service effectively, since certificates would not be considered valid. This can be mitigated by uploading signed timestamp entries, and we're also working on solving this with other timestamp formats too.

the signatures are trusted as long as all the signing keys have never been compromised despite the expiration time.

Note that you are still correct here: the expiration time is about 10 minutes, and a compromised key that re-uses the signing cert and signs during that 10 min window would still validate. Keyless attempts to have a small enough window where compromise is feasible compared to std PKI

Thank you all for the explanation, now it's clear!

Closing because all clear!


timeline for qm9 dataset reader and basic trainer

Hi, thought you guys had a great paper just wondering what the timeline is for the future release that will contain a qm9 dataset reader and basic trainer because I would like to have a working implementation. Thank you!

+1
If I would like to benchmark my mpnn modification against your results ideally I would like to run the same training code as you.

+1  hope for releasing qm9 reader for benchmarking purposes.

+1 waiting for releasing the model using the qm9 dataset


How to push CustomEvents to Azure Application Insights using DAPR observability

What content needs to be created or modified?
Steps on how to push application telemetry events to Azure App Insights using DAPR observability
Where should the new material be placed?
https://github.com/dapr/quickstarts/blob/master/tutorials/observability/README.md

@vamseelnala closing as there is a doc for this: https://docs.dapr.io/operations/monitoring/tracing/otel-collector/open-telemetry-collector-appinsights/
If you'd like this added to the quickstarts repo, please open a new issue there - thanks!


Pulling a new container shouldn't interrupt or fail if a user loses connection to Portainer

Is your feature request related to a problem? Please describe.
Recently I was running a "recreate" task on a container in Portainer, electing to pull a new image. During this time, my connection blipped and Portainer flashed a "network error" notification as expected.  What was surprising though was that it appears the recreation task itself stopped after I lost my connection and it never recovered (i.e., the container is now in a bad state)
Describe the solution you'd like
I feel that tasks in Portainer task should be initialized in the background and should not be affected by the user being disconnected from the web UI. Not only this, the new image should be fully downloaded from the internet before the old container is taken down if that's not already done.

bump

@yllekz
I wanted to follow up on this request.  Is this still an issue?
Thanks!

Yes.

@yllekz
Can you provide the following:
[1] Environment
[2] Version
[3] Screenshots and/or vid captures
[4] Open Web Dev Tools >> Network tab >> and screenshot the Response and Requests tabs
[5] Stack code or container image
Thanks!


Typo in Tag & IndocatorTag section

In the Section for "Tag &Indicator Tags" there is a typo:
In the bullets:
tag - This will show a tag box with a colored background and border
tagindicator - Shows a tag box with a colored circle indicator
the second line should read "indicatortag" and NOT "tagindicator"
(as is confirmed later in the document)
James.

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

ID: 619c9ca0-af00-b38f-c625-6660f6b93df8
Version Independent ID: 619c9ca0-af00-b38f-c625-6660f6b93df8
Content: DetailsList control reference - Power Platform
Content Source: power-platform/guidance/creator-kit/detailslist.md
Service: power-platform
Sub-service: guidance
GitHub Login: @denise-msft
Microsoft Alias: demora

Thanks for your comment, @jh-sigmadx. This issue has been assigned to the doc author for review.


Update UcrmApi.php

Change return values for POST, PATCH and DELETE functions to return JSON response rather than VOID.

Updated code as per post to UNMS/UCRM forum.


SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted

This exception is consistently thrown as an InnerException on InitializeComponent() of the main window, when the application starts.

Is it possible that you have multiple instances of your app running? Check task manager for zombie processes.

It's possible, but I doubt it.
You can use the netstat command to find the offender.
https://stackoverflow.com/questions/6960019/how-do-i-find-which-application-is-using-up-my-port

Which port is Ammy normally trying to use?

Should be 53029

Interesting, 53029 appears not used by anything.

Is it possible that Ammy tries to connect twice in the same session?

Hmm, I don't think it should. How can I check?

You can try breaking on SocketException and inspect existing threads and their local values. To do that, open Exception Settings and check SocketException

I found that if using another app that was created using Ammy, it blocks other apps that use Ammy. Example: Xaml to Ammy converter.…

The existing solution would be to add a NO_AMMY_UPDATE compilation symbol during the build. This way the app wouldn't hog the update port.
I agree that the configurable port approach is better. But it takes much more work to implement.


Version labels in collapsable header looks like a tab

The OSS and Enterprise labels in the headers here look like they are tabs.
https://goteleport.com/docs/access-controls/sso/azuread/?scope=enterprise#make-sure-you-can-connect-to-teleport
Current States
Normal:

Hovered:

Collapsed:

Fix
A possible fix would be to invert the label background when it's not collapsed:

Closing since we're using Docusaurus-native details boxes in the new site, and these don't include edition labels.


Move async http range reader crate into rattler-networking

I preserved history -- let me know if I should squash it (or it can be squashed upon merge)

Now that I reread this code, Im wondering if it would make more sense to keep it in the library but allow passing arbitrary headers to requests? I think there is merit in keeping this functionality in its own library. Alternatively if the burden of multiple PRs to multiple repos is too high we could also just move the library itself into this repository but keep it as a seperate crate.
I apologize for steering you in the wrong direction initially, but WDYT?

Yeah we do use this crate internally in a few locations as well. I also know of some other uses in the wild. I think having this functionality (async range request streaming) as a separate crate serves more people than us. That is why we split it into its own crate in the first place anyway.
Personally I feel moving the source of the crate into this repository but as a separate crate provides us with the ability to create a single PR in the rattler repository but without tying the functionality to rattler_networking. I think that would be a good middle-ground.

You mean moving of the AuthenticatedClient? I think thats fine in this PR.


KotlinAdapter refactor

Add the requirement that Kotlin @Mod implementations must be objects,
Significantly refactor KotlinAdapter based on that assumption,
Fix INSTANCE singleton reflection for Kotlin RC (appended $ was removed after deprecation),
Added name to mcmod.info and Adapter authors.

I left other documentation to you for the rest of your cleanup, and only edited things that would be actively wrong.
Also removed the adapter metadata because I couldn't figure out why it was there.
I wrote this adapter for Thump in this commit, and everything works fine with Kotlin RC-1: https://github.com/CarrotCodes/Thump/commit/4ae1d063265a64cc2b3c2eeabf4114a84b1c18e2
Also note that you might not need to shade the Kotlin Reflect library any more - I don't need to for Thump, and removing it halves my built Jar size, but that seems beyond the scope of this change.

This looks good to me; the metadata was only required for if Forgelin was being loaded as a mod, which we're stopping doing anyways :+1:


go get vasto&chrislusf/gorocksdb fail

OS：ubuntu ，go version 1.10.4
go get github.com/chrislusf/vasto
github.com/chrislusf/gorocksdb
gopath/src/github.com/chrislusf/gorocksdb/options.go:1045:2: could not determine kind of name for C.rocksdb_options_set_allow_ingest_behind
I have successful go get&build tecbot/gorocksdb，
however I fail to go get chrislusf/gorocksdb and chrislusf/vasto

Install latest https://github.com/facebook/rocksdb

thx, go get successful！
but when run ./go.test.sh，I encounter following error:
ok      github.com/chrislusf/vasto/storage/binlog       0.092s  coverage: 82.4% of statements
ok      github.com/chrislusf/vasto/storage/codec        0.052s  coverage: 94.4% of statements
/tmp/go-build866405345/b001/rocks.test: error while loading shared libraries: librocksdb.so.5.17: cannot open shared object file: No such file or directory
FAIL    github.com/chrislusf/vasto/storage/rocks        0.011s


[Bug?]: Hydration Mismatch when using children

Duplicates

[x] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
Hello, I am getting a hydration mismatch error when attempting the following in ssr mode :
import { children } from "solid-js";

export default function App() {
  return (
    <Holder>
      <h2> Wont show </h2>
    </Holder>
  );
}

function Holder(props) {
  const _kids = children(() => props.children);
  return <h2> Will Show </h2>;
}

This could entirely be my misunderstanding. Please let me know
here is the error:

Expected behavior 🤔
I would expect the return value of Holder to render as normal
Steps to reproduce 🕹
Reproduction Link
Context 🔦
I am attempting to have the children of a component add values to a context item, then render the result with that context.
Similar to:

function List () {
  let context = createMutable({
    items: []
  })

  let _renderedChildren = children(() => (
    <ListContext.Provider value={context}>
      {localProps.children}
    </ListContext.Provider>
   ))

  return (
    <For each={context.items}>
      {(item) => <div>{item.name}</div>}
    </For>
  )
}

Your environment 🌎
No response

There is an existing issue in Solid related to this. It has to do with the eager resolution of computeds. https://github.com/solidjs/solid/issues/1977

Thanks for letting me know about the issue. I probably should've checked the Solid repo first.
Thanks for the feedback! Maybe there is a better way to accomplish my goals?
Here is an example of what I'm trying to do
_renderChildren is not used, it is just there to access the props.children, and allow those children to have access to the list context. context.items would be set by the children who use that context.

If _renderedChildren is never read then this is quite a different scenario than I was thinking. You just want to run those components in that context and have them write to your context. This sort of a synchronous effect. It probably could just be run top level without a wrapper. That being said I imagine the problem is probably downstream. Ie real DOM elements are getting rendered during that pass whereas really you want to pass back configuration. It's hard for me to see all the layers.

I don't know what to do with this one, as the behavior is by design but I don't have enough information to offer a better solution. If you want to chat about this more maybe flag me in a discussion or on discord.


Update Microsoft.Extensions.Caching.Memory dependency

We were looking at the transitive dependencies of Microsoft.ApplicationInsights.AspNetCore (v2.22.0). The PerfCounterCollector package utilizes Microsoft.Extensions.Caching.Memory (v1.0.0). This version was released in 2016. Could the reference be updated? We target .NET 8.0 so while I do not believe we would be affected by an outdated dependency, it does look like the most recent version of Microsoft.Extensions.Caching.Memory (v9.0.0) still supports the .NET 2.0 standard.
https://github.com/microsoft/ApplicationInsights-dotnet/blob/e34286b4c8175d7ea47f9227c5b981d661cac470/WEB/Src/PerformanceCollector/PerformanceCollector/Perf.csproj#L30-L33

Not only that but I ran into a jam this morning where I was getting a TypeLoadException due to this dependency issue:


Make health indicator configurable by the users

Starting point is this Stackoverflow question.
Customizing the health indicator allows users to tailor the health status to their specific use case.
Use case example:
We implemented some kind of circuit breaker which stops the binding after the processor could not process x messages in a row or y messages for a given time period in order to prevent flooding our error queues. When a binding is stopped we want to be alerted.
Our applications are monitored by Icinga using actuator/health as default monitoring endpoint and switching to another endpoint is not easily done. Therefore we want to enrich the health details by adding additional information regarding the state of the binders.

@magnusLechner After looking at this requirement a bit further, here is where we stand.
The Kafka Streams health indicator only considers KafkaStreams objects that are presently running. We can change this so that the health check will indicate the status for all. For example, let's say a processor is in the middle of a rebalance, with the current code, you will not get the status for this processor because it is not running while you checked the health. We could fix this problem, but what you are running into is completely different. In Kafka Streams binder, when a binding is stopped, the underlying KafkaStreams object is completely gone. Next time you start the same binding, a brand new KafkaStreams object will be created. Thus, from the health check perspective, while the binding is stopped, there is no associated KafkaStreams to it and you will not get a health status.
With that said, I think we can accommodate this use case by making a few changes. First of all, we will need a new property to enable health checks for any stopped KafkaStreams objects since the application started. We probably need to cache these stopped KafkaStreams. Then, when a health check is initiated, we can provide a simple DOWN status for the processor. The only thing that we need to be careful of here is that if the processor is running now, we should remove this previously stopped KafkaStreams from the internal cache so that the health check will not erroneously report this as DOWN. When opting into this feature, the overall health of your system (the top-level status on the query response) will be DOWN. You can then drill down into the JSON structure to query the details.
Please let us know what you think about this design suggestion, then we can take this further for implementation.

It looks like this will help us a lot. We assume that you should be able to clean the cache, when the binding comes back too RUNNING, based on the ID of the binding. So for us, this is the solution to go with.
If you need someone to test the changes, we can provide you with feedback :) Thanks so far.

@magnusLechner I have a PR for this issue.


Notification system

Background: This tool is a privacy preserving voluntary COVID-19 self-reporting platform for contact tracing. Users share their (encrypted) location history and test status, get a notification if you have been in proximity to higher risk locations.
Detailed explanation:
Users who opt in for the notification system, should receive emails (or other forms of notification like text) if they are found to be in a high risk area. The notification should prompt the user to visit the application website (individual reporting screen) to get details on high risk locations the user has been to
To-do's:

[ ] Assess different email notification alternatives
[ ] Implement an email notification system

How the notification system can get the list of encrypted id users with high risk? Will be an endpoint to query on the API Server? will be a query per id or a list of all infected ids?

@cmalfesi as I see there are 3 ways to do it, only the first one offers enough privacy

Notifications to be triggered by MongoDB. MongoDB knows the last time a user queries (logs-in), so we can setup a trigger (email) on MongoDB side to prompt the user to sign back in. This way user would check every time t (24 hours) to see if there are new high risk interactions. This will not leak any information. Probably the easiest way / what we want to implement first

Notification is shown on the webpage, if the user is logged in. This provides high privacy b/c the enclave directly communicates with the client, where the data can be decrypted locally. However the usability is low. I think there's value to add this as a default option (all users would have this when they login to their profile) - this is not currently possible b/c we don't have public/private key that's persistent like we do in blockchain use-cases

Email notification: This requires the backend to receive user_ID's from the enclave and then pass them to an email server. At this point there's a data leakage. Email server and the back-end knows which users are at risk. However this is much more usable than option 1. If we are building for this, then we require users to opt-in to notifications and communicate the privacy risks. This can be handled on the UI level. However even in that scenario, the data structure inside the enclave must include info about opt-in (out of scope)

@cankisagun I see and understand the option. I think it is possible a combination of the options 1 and 3. I will think about it on my side a little more and check some options and combinations of cloud services that we can use to make it secure. I will draw an architecture plan so we can discuss it better through a graphic example.

@cmalfesi a good way to communicate Option 1 can be the following:
"In the last 24 hours, X many users have submitted data to the system, log back-in to check whether you've had any high risk interactions"

@cankisagun  @ainsleys
I have researched and analyzed different user cases regarding Options 1 and 3 and here I share my vision about how we should proceed.
Analisis
Option 1
"Notifications to be triggered by MongoDB. MongoDB knows the last time a user queries (logs-in), so we can setup a trigger (email) on MongoDB side to prompt the user to sign back in. This way user would check every time t (24 hours) to see if there are new high risk interactions. This will not leak any information. Probably the easiest way / what we want to implement first"
User story

Day 1: User A load locations and result Negative
Day 1: NS does not send email
Day 2: User B load locations and result No tested
Day 2: NS does not send email
Day 3: User C load locations and result Positive
Day 3: NS send email to all users except the Positives

Negative
- We could send thousands of emails every 24hs if we have a lot of users and reports per day (spam problem)
- If there are several infected reports every day, users every day will receive an alert and have to login and check
Positive
- This provides high privacy
- Enclave is queried when the user is logged
Option 3
"Email notification: This requires the backend to receive user_ID's from the enclave and then pass them to an email server. At this point there's a data leakage. Email server and the back-end knows which users are at risk. However this is much more usable than option 1. If we are building for this, then we require users to opt-in to notifications and communicate the privacy risks. This can be handled on the UI level. However even in that scenario, the data structure inside the enclave must include info about opt-in (out of scope)"

I think this option is more secure and have better performance. Here my vision of the way to apply this is the next.

Architecture

User story
1- User sign up and sign in to the Frontend. Load the test result and locations
2- Register and validate the user and return the encrypted UserId and save the results data with UserId
3- save data of the new user and validate login
4- Enclave returns the individual report with "matches"
5- Fronted returns to the user the information of "matches"
6- Send the high risks users list to NS. Here we could implement 2 options:
- Opt 1: Once a day NS GET the list of users id against Enclave API Server
- Opt 2: Every time that Enclave receives a "positive", search "matches" and POST the list to the NS.
7- NS query the email through the user id and sends an email informing about the high risk of possible contact and ask him to login and check.
In step 6, we have to think about what is better to do, both options I think are ok.
Components description
Backend API
    Endpoints
        POST: Sign Up
        POST: Login
        GET: GetEncryptedUserId   (only return it for logged user)
        POST: ReportTestResult (GET is not available)
    Security
         - It does not share tes results information, only let save data
         - Users can login once at a time.
         - Google user only can be validated session

DB (MongoDB)
    Collections
        User
        Reports
    Security
        It's only accessible from the Backend and NS.
        DB should be built into a secure cloud service

Notification System (NS) (Private server)
    Endpoints
        GET: userEmailbyId
    Security
        - No external access allowed
        - Only could receive requests from Enclave API Server
        - We could use internal or external email service because emails will send only notifications requesting to users to login into the system, will nos share sensible information.

API Server - Enclave (It process, save and "matches" the risks by contacts and locations)

I believe we can proceed with Option 1 for the MVP, but it'll better to apply Option 2.

@cmalfesi thank you for the detailed description. Let @ainsleys and I think about this. This is a part where it's helpful to get feedback from partner apps.
I would like to highlight that for Option 3 to work, we  need to add notification information into the SGX b/c we only want opt-in users to receive email / have their information be shared with the email server


Feature: Idempotent seeds

This solves #520

Please review, @bascht or @bitboxer

It should be 'plant seed' not 'insert seed', right? My gardening skills are so bad :seedling:

Full seeds ahead, sir!

Thank you, sir!


pachctl deploy --dry-run outputs invalid json

What happened?:
pachctl deploy local --dry-run outputs invalid json.
Output snippet:
{
"kind": "ServiceAccount",
"apiVersion": "v1",
"metadata": {
"name": "pachyderm",
"namespace": "default",
"creationTimestamp": null,
"labels": {
"app": "",
"suite": "pachyderm"
}
}
}
{
"kind": "ServiceAccount",
"apiVersion": "v1",
"metadata": {
"name": "pachyderm-worker",
"namespace": "default",
"creationTimestamp": null,
"labels": {
"app": "",
"suite": "pachyderm"
}
}
}
{ ... }
What you expected to happen?:
Valid json
How to reproduce it (as minimally and precisely as possible)?:
pachctl deploy local --dry-run
Anything else we need to know?:
Tested with both pachctl deploy local and pachctl deploy microsoft, and both output invalid json. Running with --output yaml outputs valid yaml though
Environment?:

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.13", GitCommit:"37c06f456fdb4d25e402b5fbcb72cd6a77a021a9", GitTreeState:"clean", BuildDate:"2020-09-18T21:59:14Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

Pachyderm CLI and pachd server version (use pachctl version):
pachctl             1.11.0
pachd               1.11.0

Cloud provider (e.g. aws, azure, gke) or local deployment (e.g. minikube vs dockerized k8s):

OS (e.g. from /etc/os-release):

Others:

@kasperbfrank thank you for opening up this issue. You're correct, it's not one valid JSON manifest at the moment. Instead, it is a file containing multiple valid JSONs, one per component, such as ServiceAccount, ClusterRole, Service, Secret, Deployment, ...
Is this currently blocking you?

It's not blocking me, I needed to deploy a pachyderm cluster from a modified config, so I just used the yaml file format instead.

kubectl create -f .json does not work, but kubectl create -f .yaml does

I don't think I can reproduce the issue:

➜  ~ pachctl deploy local --dry-run > github.json
➜  ~ kubectl create -f github.json
serviceaccount/pachyderm created
serviceaccount/pachyderm-worker created
clusterrole.rbac.authorization.k8s.io/pachyderm created
clusterrolebinding.rbac.authorization.k8s.io/pachyderm created
role.rbac.authorization.k8s.io/pachyderm-worker created
rolebinding.rbac.authorization.k8s.io/pachyderm-worker created
deployment.apps/etcd created
service/etcd created
service/pachd created
service/pachd-peer created
deployment.apps/pachd created
service/dash created
deployment.apps/dash created
secret/pachyderm-storage-secret created

kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.0", GitCommit:"e19964183377d0ec2052d1f1fa930c4d7575bd50", GitTreeState:"clean", BuildDate:"2020-08-26T21:54:15Z", GoVersion:"go1.15", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.0", GitCommit:"e19964183377d0ec2052d1f1fa930c4d7575bd50", GitTreeState:"clean", BuildDate:"2020-08-26T14:23:04Z", GoVersion:"go1.15", Compiler:"gc", Platform:"linux/amd64"}

~ pachctl version
COMPONENT           VERSION
pachctl             1.11.7

@kasperbfrank Can you give us an output of the errors? We have not been able to recreate this problem inhouse.

can't reproduce the issue. Please reopen with more info.


Compiler: Do not import from java.lang in generated classes

FYI:
https://github.com/square/javapoet/issues/519
https://square.github.io/javapoet/1.x/javapoet/com/squareup/javapoet/JavaFile.Builder.html#skipJavaLangImports-boolean-

done.


Fixed upload avatar when category is selected

tasks:

[ ] gather feedback for my changes

informations:

q
a

Fixed tickets
fixes #1737

BC breaks
none

Documentation PR
none

This looks for me like fixing symptoms instead of the cause... Why does it work with the normal save? Isn't the same method used to gather the data from the form?

@danrot i will take a look at this a bit deeper tomorow


remove version from all screens in app .

version has been removed from all the screens  because we have about icon in menu which will tell about version of app .


UnboundLocalError: local variable 'field'

.....\forcetable\_table.py", line 227, in fields_to_records_primary_grouped
    field = field(primary_field.get_name(), [primary_item])
UnboundLocalError: local variable 'field' referenced before assignment

field class is colliding with local variable.
This errors have been common after changing case of classes.
table and record also caused similar errors within '_table.py'.

It can be fixed by changing local variable into something like field_.


In Firefox, range HTML5 element still shows the outline

Firefox 41.0.2.
Example is from guide.

Fixed by @soniabrami in #2756


TS Tutorial Services - Pt. 5 Typo, missing period

Actually, the error is in Pt. 4.  Accepting it.


add human CCDS best representative gene models to docs

This is the link: http://www.ncbi.nlm.nih.gov/CCDS/CcdsBrowse.cgi


FixUpgrade hive-catalog-shade to 2.0.2 to solve the problem that DLF cannot be used normally

Proposed changes
The exception stack encountered when using DLF is as follows:
This is because hive-catalog-sahde incorrectly renamed dlf-related packages, causing it to fail to run normally.
 java.lang.ClassCastException: class org.apache.hadoop.hive.metastore.api.NoSuchObjectException cannot be cast to class org.apache.thrift.TException

https://github.com/apache/doris-shade/pull/44

run buildall

run buildall

Oops...let's run the test later. It seems that the jar package has not completely completed the release process.

run buildall


Sanity check with travis. Fix #5

Please link travis-ci to this repo before merging the PR. Ping me if you need help.

Hi Tom, we're going to park this for now, but feel free to do this on your own branch and we can discuss it.


TT-1368 run CI for verify-saml-extensions on travis in parallel

Note: this needs a travis config change, ideally before merging
As part of a program to move PR builders to travis.
This may need to move to travis.com or to hosted travis later, for now this is a safe (the project is open source anyway and we are not using build artefacts yet) way to run tests on master and branches on travis, as a simple demonstration.
Tested here: https://travis-ci.org/swilson96/verify-saml-extensions
Before merging, we need someone with admin access to this repo to enable it in travis-ci.org. @kornysietsma is that you?

Closing, doesn't actually work on Travis for some reason, needs more work


Switch between Audio and Video calls

Hello,
It would be nice to be able to switch between audio and video calls midway in a call.
Thanks

@rajil
it is already available (check the buttons in the calll tabbar)

It's not available! There are no buttons.

There are no buttons to switch to video.


add documentdb and lambda triggers samples

I think README.md should be written the command cdk bootstrap initially.
cd ../cdk
mvn compile
cdk bootstrap
cdk deploy <-- I failed this command if skipped cdk bootstrap


moment-format outputFormat does not support Ember.SafeString

I'm trying to use a string from ember-i18n as my outputFormat on moment-format but it does not like it and moment throws an error a.match is not a function.
// locales/en/translations.js
date_format: 'DD-MM-YYYY'

// component.js
import { translationMacro as t } from 'ember-i18n';
....
testDate: moment(),
dateFormat: t('components.date_format')

//template.hbs
{{moment-format testDate dateFormat}} // Throws error

{{moment-format testDate (t 'components.date_format') // Throws error

Date format is {{dateFormat}} // Displays  'DD-MM-YYYY' as a string properly

According to ember-i18n:

Note that i18n.t returns an instance of Ember.SafeString, which is perfect for emitting to HTMLBars template"

Apparently moment-format does not support a SafeString as it just tries to pass that object into moment to render it. I think a simple check to see if the property is an instance of EmberSafeString would suffice.

<EMAIL_ADDRESS>

I recommend creating a helper to unwrap your SafeString, or create a t-helper that returns just a string..  Otherwise, I'd need to support unwrapping all attributes and params because of ember-i18n.  In ember-intl I handle this differently by only returning a safeString for {{format-html}}, the normal t helper returns a string.


Contained elements are never fully adopted and always match :unresolved

Commit 8697b40f67e1275defaf57648ed6bec9fd0e0160 which was used to close issue #231 causes issues with contained custom elements.
Contained custom elements are never fully adopted even when the containing element is finally adopted. This means that contained elements will always be matched by the :unresolved CSS pseudo-property.
In https://codepen.io/depeele/pen/QBdZyo using lit-html:v0.10.0 the contained test-item is considered resolved in the final document.
In https://codepen.io/depeele/pen/PBWyzB using lit-html:v0.10.1 but otherwise the same code,  test-item is not considered resolved in the final document.

Turns out, the WebComponents standards committee decided to rename :unresolved to :not(:defined) (w3c/webcomponents issue 418).
See https://codepen.io/depeele/pen/gjGPRy using lit-html:v0.10.1 which uses the new pseudo-property.


Fix bug due to Promise.then race condition and shallow buffer copy

Hi,
I found in our integration tests that sometimes line 300 in client.js
return self.protocol.read(responseBuffer).ProduceResponse().result.topics;
threw an error that it was reading past the end of the buffer.
After exploring, I eventually worked out the problem: when multiple promises get resolved closely together, sometimes the .then of an earlier resolve executes after later resolves have been called. Since Buffer.slice is shallow copy, the "late" .then receives data from a different message.
My fix is to deep-copy the buffer (rather than try to enforce .then execution order). Hopefully this is a good approach!

Thanks for pointing at the bug and its reason! However I would like to find a different solution, copying every message seems to be not the best approach.

But of course making a copy can be the only solution. I'll check.

Ahh.. Would this by why sometimes under high concurrency I might have been getting those deserialization errors when using compression? This is an interesting problem with some scary consequences.

Hi Steve,
That's totally the symptom i saw that lead me to finding the bug!
--
David Mack
CTO and Co-founder, SketchDeck.com
On September 12, 2016 at 3:01:54 AM, Steve Gray<EMAIL_ADDRESS>wrote:

Ahh.. Would this by why sometimes under high concurrency I might have been
getting those deserialization errors when using compression? This is an
interesting problem with some scary consequences.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/oleksiyk/kafka/pull/111#issuecomment-246303022, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGpBZVIomYh1vHNKg0Jk810vE9xArcreks5qpSMSgaJpZM4J2Yiq
.

+1 I've been seeing this too. Super-keen to get a fix. If this isn't the PR, is there an issue to follow to see progress on this bug.

I'm going to try to force the correct order in the queue.

Hello!
I do not believe that commit 7dabcf2 fixes this bug. I could be wrong though!
I just experienced this bug in the 3.0 branch, which I believe benefits from that commit's change. It failed my integration tests, which send 200 messages then test that all are received. Putting a buffer copy, as per this PR, fixed the issue.
The bug does not come from out-of-order responses from Kafka, but from interleaved Promise resolution. Therefore using correlationIds in the queue does not solve it. I actually attempted that in my first PR draft, but it didn't solve the problem.
As far as I know, the promise standard has no requirements about when the .then of the promise gets executed upon resolution. When two queue promises have their .thens executed out-of-order with respect to the data coming back from Kafka, they run into the issue that .slice on a Buffer is a shallow copy and at least one .then receives the wrong information.

When two queue promises

But there is no queue now.

Sorry, I mean "when two promises".
Basically, I do not believe you can mix asynchronous execution with .slice, as slice has global state (since it's a shallow copy) and promises allow for out-of-order execution of the .then handlers

You are right. I don't see any other solution but to copy a buffer. Will do.


Setting Props for Component in ComponentHost

Describe the bug
Is there a way to set properties for a component that is integrated into a XAML page via ComponentHost?
Here is my component:
partial class MyComponent : Component
{
    [Prop]
    string _message;

    public override VisualNode Render()
     => StackLayout(
            Label()
                .Text(_message)
...
        );
}

This is the way the ComponentHost is setup, it's then added to the Content of a XAML ContentPage
var componentHost = new ComponentHost
{
    Component = typeof(MyComponent)
//how to set Message here?
};

I found that the only way to set the Component is via Type.

Currently is not possible, ComponentHost is considered a root component so it should not be intended to receive props.
One thing you can do, though, is use dependency injection (i.e. common services) to share info between the container app and the hosted MauiReactor component.

thank you for the info - i will implement it via DI then


ENH: add aspect radio to limits dialog

enhancement according to issue #138

In this section there is a test for airborne radar. Can you change:
if (radar.metadata['platform_type'] == 'aircraft_tail' or
    radar.metadata['platform_type'] == 'aircraft'):

to:
if 'aircraft' in radar.metadata['platform_type']:

see new commit to the airborne change.

The changes look good. Last thing is that I feel the other limits are pretty self-explanatory. But the aspect ratio may not be to people. Should we add a help button that pops up a window like we do in other areas?

@stechma2 See the image below. Would you know how to use this?

what would be the help text. If it is not too long it could be a tool tip.

Oh, that's a great idea! Thoughts for tooltips:
Data Min: "Minimum data value to display"
Data Max: "Maximum data value to display"
X Min: "Minimum X-axis value"
X Max: "Maximum X-axis value"
Y Min: "Minimum Y-axis value"
Y Max: "Maximum Y-axis value"
Aspect Ratio: "Y-to-X size display ratio, also accepts auto and equal"

@nguy I would know how to use that, though I think adding the tooltips would be very useful (I like the ones you suggested). Also, glad to see the file being recognized as airborne now with the auto-scaling applied. Thanks for these changes!

I also like the suggestion. May be we could change X and Y for "horizontal" and "vertical", as to avoid confusion with the x and y direction in grid.

just uploaded a commit with tooltips

Nice changes. I think this is ready for merge. Agreed?

@gamaanderson Can you make one more additional change I was just made aware of by a user?
In the README, under the install section. artview is mispelled as artivew. Since this will likely be merged soon.

done, also rolled the micro version, as this has a functionality change (was that procedure correct?)
I'm ok with merging.


env.list example

File: engine/reference/commandline/run.md
I think that in env.list file the value "denis" is missing for env var "USER".
In addition "denis" could be "Denis"
Regards
Andrea
cat env.list
VAR1=value1
VAR2=value2
USER <-- here is missing the value
$ docker run --env-file env.list ubuntu env | grep VAR
VAR1=value1
VAR2=value2
USER=denis

Thanks for sharing the issue.  As this issue is old, some additional context may have been added to that topic. The example with no value is showing what happens when a value is not assigned.
If the issue is still applicable, please help create an issue in the upstream source repo at https://github.com/docker/cli/tree/master/docs/reference/commandline


Extract license when unavailable

Currently, gimie only retrieves the license from the GitHub API.
The GitLab API does not provide license at all, and the GitHub API license detection is lacking and will return NOASSERTION when:

the license is in a different file (e.g. LICENSE.md)
multiple licenses are found in the repo
the license is slightly different (e.g. added copyright notice)
the license is not one of the most popular licenses

For cases when gimie fails to retrieve a license from the Git provider, it would be preferable to extract it locally. The process could look as follows:
graph TD;
    query[Send API request to git provider] -->check[license in response?];
    check -->|yes| return[Success];
    check -->|no| clone[Clone repository];
    clone --> extract[Locally extract license];
    extract --> add[Add to graph];
    add --> return

This would add considerable overhead only in cases when license cannot be determined from the provider. This approach could also be applied to other attributes that may be missing from the API but present in the repo.

Gitlab blobs? for accessing the tree (?)
We want to use our existing license extractor and matcher on the tree structure - without cloning the repository.
IF this is fast, we can make it default and bypass the API's.

I will give a try for this - specifically for the GitHub variant first. If that works, I'll move to GitLab.

WIP

Pre-requisite in #70
implementation in #68


distutils -> setuptools

Fixes the "Unknown distribution option: 'install_requires'" error while running make install.
distribute is deprecated according to http://pythonhosted.org/distribute/:
Distribute is a deprecated fork of the Setuptools project.

Since the Setuptools 0.7 release, Setuptools and Distribute have merged and
Distribute is no longer being maintained. All ongoing effort should reference the
Setuptools project and the Setuptools documentation.

Thanks for submitting a patch!
Can I ask which OS/platform/distribution you've tested this on?
I'm concerned that if I merge this patch in, it might be the case that older systems will no longer be able to install the python API correctly (I'm not sure yet if that is the case or now).

I tested this on Mac OS High Sierra with Python 3.7.

I also successfully installed it on Ubuntu 18.04.1 LTS with this patch. Python version 3.6.7.

Hmm, I also need to maintain support for older distributions.
What if we instead did:
try:
   from setuptools import setup
except ImportError as e:
   from distutils.core import setup

(As seen here: https://stackoverflow.com/a/25359853)

Yeah that seems reasonable. 👍


Helm Chart

We've started work on a Helm Chart based off the manifests here.
So far it works with a few changes for standard token and api locations but doesn't persist the database or load the topology automatically. I thought I'd raise a ticket early for tracking and inputs but the addition of etcd and daemonset features to Heketi should let us wrap this up and push it upstream.
https://github.com/AcalephStorage/charts/tree/glusterfs/incubator/glusterfs

This is awesome, thanks @hunter.  We are trying to get as many things into Kubernetes primitives as possible (daemonsets, configmaps, etc.) - some of that work is happening here https://github.com/gluster/gluster-kubernetes/pull/38

Hi @hunter I have been looking at Helm, but, afaict, there is not step process.  It would be great for Heml to support a step process.
It looks like it would be more successful to have a Job which runs gkdeploy.
Also https://github.com/heketi/heketi/pull/622 will make configuration much easier.

I'm not entirely convinced there needs to be step process in Helm.
The main things that are missing from this helm chart are importing the topology and persisting heketi.db. I've not had time to implement but both of those could be handled by init-containers which would also remove the need for a deploy-heketi resource. The downside is that it will only be supported in environments with alpha (1.3) or beta (1.4/1.5) extensions enabled.
Helm also does have install/upgrade hooks. These can trigger one off actions but I don't really see a need to make it helm specific when init-containers exist.

@hunter Init container could work well.  This is something @ant31 is also working on.

this is awesome @hunter! i would like to try this with our project: https://github.com/att-comdev/openstack-helm, because I know our users are going to want other storage options (we're currently using Ceph PVC's for Kubernetes). we would love to collaborate with you and the gluster team on this!

Heketi topology could be installed as a post-install or post-upgrade hook in helm:
https://github.com/kubernetes/helm/blob/master/docs/charts_hooks.md
In the future maybe it would also make sense to use node labels for dynamically configure heketi (and create something like etcd-operator), see #46
@hunter How about also introducing an endpoint as a part of helm chart?

Hmm. Probably more appropriate than endpoint is storage class:
apiVersion: storage.k8s.io/v1beta1
kind: StorageClass
metadata:
  name: slow
provisioner: kubernetes.io/glusterfs
parameters:
  resturl: "http://<IP_ADDRESS>:8081"
  restauthenabled: "true"
  restuser: "admin"
  secretNamespace: "default"
  secretName: "heketi-secret"


Nested async call Tree is not fully exposed

Hello,
Would it be possible to support a call tree for nested async calls as shown below?
(aysnc call in async call)

Currently the call tree is not fully exposed but just showing first async call only like below capture.

When testing with the latest version, 0.9.0 agent, it seems that this feature is not supported.
(envionment1 : nextjs + trpc module, node 18.18.2)
(envionment2 : nextjs + axios module, node 16.20.0)
Is it possible to develop and support this feature in the future?
I would appreciate your response.
Thank you.

@rornfdlek
When the NodeJS runtime run with await promise , The NodeJS runtimes returns promise value of parent function In parent pending state. and then runs other async function.
The case you shared is one that I have not tested. I'll try to validate it in v1.0 and improve it so that it can be traced properly if it is traceable.
Thank you for your excellent task

Hello, thank you for your kind response.
Could you please let me know approximately when v1.0 will be released?
I'd like to prepare for it and follow up as soon as possible upon confirmation of the schedule.
Thank you for your understanding.


Fill in the Step-by-Step Guide in our docs.

"The Step-by-Step Guide to Building an ML Accelerator" section of our documentation was just marked as TODO. This PR fills in this section of our docs with an overview of:

Making a project
Profiling the software
Doing simple software optimizations
Creating a SIMD MAC instruction in the reader's choice of nMigen or Verilog

By the end of the tutorial, inference with the pdti8 model is sped up from 183,087,673 cycles to 85,771,518 cycles.
I'd welcome suggestions for changes to the content or explanations!

LGTM. Thanks so much for putting this together.

Thanks for the great feedback Alan! I've implemented all the desired changes :).


Noisy logging.error: "Bad state for purpose"

When debugging aborted pipelines, we tend to look to error logs with path:pipeline on the console.
In this search, you will find errors like the following:
Pipeline ID "23377674aae54a8b883cb75636a8fcf6" in bad state for purpose "abort": "aborted"
This specific message seems to me to be a bit verbose, as I'd expect this to be an okay situation.

There are perhaps 2 points of discussion worth having here:

The obvious, why is an aborted pipeline being triggered for abortion?
The more helpful, can we disable this particular log from emitting?

If the community finds it appropriate, I've tackled item 2 in #51 and its ready to be merged.
If not, we can keep the change to our fork at github.com/Loudr/appengine-pipelines . :beers:

1 is inevitable. (Duplication / inconsistency / errors)
2. Sounds good.


Create a log file for use in cloud environments

Hey @alex-page, can you please provide a bit more information about the details for this issue?

This is for debugging and seeing when furnace fails or dies. However i'm not sure how this would work when we rebuild our instance every time we deploy on circle. Unless it's just a log file for the current instance.

Closing this issue, if we have problems in the future I will re open this and we can figure out a way to log anything useful then.


Please stop the permanent "'mysql' extension is recommended" suggestion box

Someone mentioned this a year ago in issue #63624.
I use postgres.  If there was an extension I liked I would use it but I haven't seen one that I like yet.  But that's not really the point.
The point is that many/most suggestion boxes fade away but the mysql extension suggestion stays until dismissed.  This is very annoying.  Please make it auto dismiss.

this was fixed a while ago, please let me know if its still an issue.


user query Result type additions and some refactoring +comments

Contributions: We are not currently taking public contributions - see our contributions policy. However, we are accepting issues and we do want your feedback.

Description
Adds a result type to user interest queries. The result type is for client non auth actors because we assume clients only want to know about actors
Also refactors a little bit.
Tests
?
Documentation
lots of little in code comments
Primary reviewers
@m-samiec @MatthewSandfordImprobable

drive by make frequency editable because it is now supported


Decide whether to keep connect_eight() structure linking

In the structure detection part of the cell detection code, there are two implementations of connections to merge structures together. Currently the default and only used one is connect_four(), which assumes two pixels are connected if they are directly next to each other (ie. in a plane, one pixel 'touches' four other ones).
There is also a connect_eight() bit of code, which is not tested, and I don't think a user can use:
https://github.com/brainglobe/cellfinder-core/blob/f1188dfc8563a78c98713b260313c3a396a4bf62/src/cellfinder_core/detect/filters/volume/structure_detection.pyx#L177
This assumes two pixels are connected if they are next to each other, or their corners are touching (ie. in a plane, one pixel 'touches' eight others).
It would be good to decide if connect_eight() is worth keeping around - if so, we should add tests for it, and think about exposing it as an option for users. If not, I'd advocate for removing it to reduce the maintenance burden.

I would also advocate for its removal - fits in with the current efforts to reduce the maintenance burden - we can always dig it back up if we find a use case for it in the future. Any objections @adamltyson ?


Add fish shell to key binding docs

Add the missing fish shell part into the documentation for ATUIN_NOBIND.
Binding to up is pretty problematic in fish, as if you want to navigate the pager for auto-suggestions, you tend to get a bit stuck.

I don't use Fish, but this is the first time I've heard that our default bindings are problematic. I'd rather we stick to the defualts we have, but perhaps document this as an extra case?

I only recently started using fish, so don't count myself as an expert either, but I then came to potentially start an issue and  thankfully found these docs.
The up key is used for more than just history in fish, this is the problem. I would dearly love some more input from other fish users, though!
I think, so long as as it gets documented this is definitely enough. I had to figure it out, so thought I might as well share the knowledge!

Ahhh I see, thank you!
If you could open an issue explaining the problems that binding the up arrow cause with Fish then maybe we can figure out what's going on properly!
If it's definitely conflicting with some Fish behaviour then I'd be happy to change our default config to no longer bind that key :D

The documentation in this PR is still valid either way, if you don't want to bind all keys, or change the bound keys. The syntax is still different for fish. I will open an issue, but that's kind of a different matter.

Oh of course, you're right 🤦♀
Sorry, it's been a long day 🙃

Not a problem, it has indeed been a long day! - opened #419 for further discussion on the topic.


long cooldown period ?

It seems to have a long cooldown period after it trigger a reload(works perfect the first time), then after around 30s it seems to detected there are something to monitor.
It only works when there is a 1 number next to extension icon, then you change file on disk, it reloads itself,  then the 1 is gone, at this moment updating file on disk has no effect, it does not reload, after 30s, the 1 appears again, then it works again..  you just need to wait another 30s.
browser : google chrome

@oglops this is possibly fixed in 1.8.0 which has a different mechanism for detecting files to monitor.


Overworld music playing in End dimensions

Information

Server version: [23:47:21] [main/INFO]: [CHAT] This server is running Paper version git-Paper-344 (MC: 1.16.4) (Implementing API version 1.16.4-R0.1-SNAPSHOT)
[23:47:21] [main/INFO]: [CHAT] Checking version, please wait...
[23:47:30] [main/INFO]: [CHAT] Previous version: git-Paper-207 (MC: 1.16.3)
[23:47:30] [main/INFO]: [CHAT] You are running the latest version

Full output of /mv version -p: https://paste.gg/p/anonymous/52fe5514777b4192b2dafe01b147c294

Help request
Problem
Music from the music.game namespace is playing in End dimensions, with the music.end namespace not seeming to trigger and play any tracks. The bug does not occur in Nether dimensions, as tracks from the correct namespaces are played in them.
What I have tried
I have tried replicating the issue in a vanilla singleplayer world and on a server running Paper version git-Paper-344 (concurrent with the server experiencing the issue) with no external plugins. The correct music is played in both of these cases. I have tried creating a new End world on the server and seeing if the issue continues to occur - the incorrect overworld tracks were still playing. I assume this is a Multiverse issue as a result; this bug occurred on the previous version of Paper (git-Paper-207 (MC: 1.16.3)) as well as prior to the Multiverse plugins being updated.

This is most likely not a Multiverse issue. Please give Spigot a try, if it continues to happen, I'll report it to them.

Hi,
We switched over to Spigot just today and the bug is still occurring, but only in End dimensions other than world_the_end (which is the server's first/original End). That world has the normal music.end rotation playing in it, while all other Ends still have the music.game issue.
Server version: [12:41:23] [main/INFO]: [CHAT] This server is running CraftBukkit version git-Spigot-628435a-6917945 (MC: 1.16.4) (Implementing API version 1.16.4-R0.1-SNAPSHOT)
[12:41:23] [main/INFO]: [CHAT] Checking version, please wait...
[12:41:32] [main/INFO]: [CHAT] You are running the latest version
Full output of /mv version -p: https://j.mp/3rAgnWe
Please inform me if you need any other information (timings, etc.).

To add on to my previous comment, we just checked the behavior in Paper and it behaves the same as on Spigot (incorrect music in all dimensions except world_the_end).

I've reported it to Spigot here.

Closing as its not related to mv.


custom card stopped working

Home Assistant release with the issue: 0.82.0

Last working Home Assistant release (if known): 0.81.6
Operating environment (Hass.io/Docker/Windows/etc.): raspbian

Component/platform: https://github.com/dimagoltsman/ha-custom-lovelace-cards/tree/master/bernii-gauge

Description of problem:
it just shows white cards. no errors, no nothing. just shows white card.
i rolled back to 0.81.6 and it works
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

/move to home-assistant/home-assistant-polymer


Wasted layer of buffering and inneficciency

tcpRecvFn only reads one packet at a time from the pbuf (p.tot_len), passing it to Receive, which blocks on the application call to conn.Read. It gets a buffer from the pool if the packet spans multiple pbuf entries, allocating a new buffer if the packet is larger than 2KiB.
Problem 1) The buffer is held for the duration of the Read, which in practice means all the time. That buffering layer is actually unnecessary.
Problem 2) Only one packet is read, even though there may be a lot more data available. That's a missed opportunity for higher efficiency
You can fix the problem by switching the data flow from push to pull and writing directly to the application-provided buffer:

Replace the tcpConn.sndPipeWriter and tcpConn.sndPipeReader with a readCh chan []byte
In tcpRecvFn wait for a read buffer readBuf <- conn.readCh
On conn.Read(buf), pass the buffer to the channel: conn.readCh <- buf
Copy as much data as possible from the pbuf into the readBuf
Notify the reader (done channel?) and call tcp_recved.

There are possibly some concurrency nuances to handle closing and errors. The implementation of io.Pipe has some insights.
/cc: @bemasc @alalamav

If you don't want tcpRecvFn to access private members of TCPConn, then you could implement a local Reader with the logic above, and pass that Reader to the newTCPConn constructor, to be used in place of tcpConn.sndPipeReader. You could then get rid of tcpConn.Receive.

I think it's possible to avoid this buffer allocation and this copy by Receive pbufs in a loop one by one in this manner, dechaining a pbuf from a chain seems quite easy, there is pbuf_dechain function provided by lwip.

That would help remove the extra 2KiB per connection. However, each Receive call still blocks on a Read call, so we would be limiting the Reads to one pbuf, when we could have the application read as much as it can in one go if we switch from push to pull.
One thing I don't understand is how the stream or packet is split into pbufs. Is there a max pbuf size? Is it a configuration option?

To give you some more context about the problem we are having: the Outline client uses go-tun2socks to send traffic to a Shadowsocks server. Shadowsocks puts data in encrypted frames. We can accumulated as much as 16KiB in a frame, but because we don't know whether the next Read will block, we are forced to emit a frame for every Read.
Ideally, I'd give tun2socks my 16KiB buffer and it would fill it with as much available data as possible, possibly from multiple packets.
The Shadowsocks overhead is not a lot: 34 bytes per frame. But assuming a 1500 MTU - TCP/IP overhead = 1420 we are talking about sending 2.5% more bytes for every byte sent. Not bad, but that's the minimum overhead and it can be an issue if we have small pbufs. For example, that's 25% if we are reading 1.4KiB pbufs.
As I said, I don't really understand how the stream is split into pbufs. I do know that our download performance is measurably better than upload, and I suspect this is one of the reasons.

This PR would solve the blocking issue, and if tcpRecvFn is called fast enough (cgo is slow), the application would get as much data as possible. But a buffer is introduced. It's not clear to me how we could solve both problems at the same time.

One thing I don't understand is how the stream or packet is split into pbufs. Is there a max pbuf size? Is it a configuration option?

FWIW, it depends on how the pbuf is allocated and the input IP packet size, the tcpRecvFn callback function is mainly driven by packet input.

I see three issues here:

Extra intermediate buffering
Application Read blocks lwIP
Application Reads almost always return small data chunks

I implemented your idea above (If I'm understanding it right) https://github.com/eycorsican/go-tun2socks/commit/425fb2eb0eb166050d948408ecd498382bc5da82 and it should solve 1 and 2, without intermediate buffering, I don't see any chance to solve 3.


dataset "maps" unavailable

The link for "maps" dataset seems to be broken. I wonder if you could update it? Thanks!

fixed. thanks.

Thanks!