Support for arguments in dendron commands

Please Select if your Request is Either something new or an Enhancement

[x] Enhancement of an existing Feature.
[ ] Request of a new feature.

Please select the area your request applys to. (Multiple selections are Possible)

[ ] UI
[ ] Workbench
[ ] Publishing
[ ] Pods
[ ] Markdown
[ ] Hierarchy
[ ] Graph
[x] Misc (Choose this if your not sure)

Describe the solution you'd like
Something that will be really useful to unleash more workflows and avoid friction with Dendron would be the possibility of creating new shortcuts with Dendron commands that can accept arguments. This will allow for example the following.

I'm on customer1.meetings and I want to start a new date-formatted note to write during a meeting.

I hit a keyboard shortcut and a new scratch note is created under the scratch hierarchy, ending up with scratch.2021.3.15

Another thing this could be applicable is for the selection extract and selection to link features, so you can have different keybindings for each of them depending on what do you want.
Additional context
An example of the config I mean. This is a keybinding configured for the wichKey extension:
    {
      "key": "s",
      "name": "Search...",
      "type": "bindings",
      "bindings": [
        {
          "key": "T",
          "name": "Todos",
          "type": "command",
          "command": "search.action.openNewEditor",
          "args": {
            "query": "(- \\[ \\] \\w+)",
            "triggerSearch": true,
            "focusResults": true,
            "regexp": true,
            "contextLines": 0
          }
        }
      ]
    },

With this I can trigger vscode search for all my open todos, and jump directly to the results to navigate them with a single binding

Thanks for the issue. Will add it to our backlog.

This has been implemented: https://wiki.dendron.so/notes/ad270a7d-2aed-4273-8319-eb6536e38b29.html#value


Create patches for Otps tag

The OTPs spec tag is typo'd in one location as Otps. This causes problems with the code generation. Standardize the references to this tag in the spec via patches.
For example: https://github.com/equinix-labs/metal-go/blob/main/patches/spec.fetched.json/01_otps.patch

Patch addressing spec inconsistency w.r.t otps tag : https://github.com/equinix-labs/metal-java/blob/main/patches/spec.fetched.json/01-otps-case-correction.patch


Docs: Poor example to get a shell

I was looking at the LXD quickstart guide today:
https://linuxcontainers.org/lxd/getting-started-cli
The example command given in the section to get a shell inside a running container seems like a poor example to use:
https://linuxcontainers.org/lxd/getting-started-cli/#shellterminal-inside-container
Get a shell inside a container:

lxc exec instancename -- /bin/bash

Surely using:
lxc shell instancename

Instead is easier to read, understand, type and remember?

Yes and no. lxc shell is a convenience built-in alias which will only work with images that ship a working su command have have a proper PAM stack. It may also result in the environment getting reset depending on PAM settings.
As a result we never use it in our tests or documentation because it will not work with all images and its behavior as far as environment is dependent on the image.

Yes and no. lxc shell is a convenience built-in alias which will only work with images that ship a working su command have have a proper PAM stack. It may also result in the environment getting reset depending on PAM settings.
As a result we never use it in our tests or documentation because it will not work with all images and its behavior as far as environment is dependent on the image.


RigidBody Godot Crash without debug output.

Godot version: 3.2.1 stable
OS/device including version:  Arch Linux latest
Issue description: Godot game crashes without debugger even logging it.
Steps to reproduce: That's  interesting, as it happens randomly and only if i touch ground with rigid body. Sometimes the whole Godot crashes or becomes unresponsive in the same time as the game.
Minimal reproduction project: Too complicated to reproduce. But i will if i have to. First I want to know what is actually happening, or what does it mean. This is what I am getting on a terminal, but nothing on an internal debugger.
handle_crash: Program crashed with signal 8
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /usr/lib/libc.so.6(+0x3bd70) [0x7f972ca76d70] (??:0)
[2] /home/polytect/Applications/Godot/Godot_v3.2.1-stable_x11.64() [0x12e956a] (<artificial>:?)
[3] /home/polytect/Applications/Godot/Godot_v3.2.1-stable_x11.64() [0x14aa811] (<artificial>:?)
[4] /home/polytect/Applications/Godot/Godot_v3.2.1-stable_x11.64() [0x97ca77] (??:?)
[5] /home/polytect/Applications/Godot/Godot_v3.2.1-stable_x11.64() [0x233d6ff] (<artificial>:?)
[6] /home/polytect/Applications/Godot/Godot_v3.2.1-stable_x11.64() [0x2251e40] (<artificial>:?)
[7] /usr/lib/libpthread.so.0(+0x946f) [0x7f972c6ec46f] (??:0)
[8] /usr/lib/libc.so.6(clone+0x43) [0x7f972cb3a3d3] (??:0)
-- END OF BACKTRACE --

You should compile Godot, to get information on where exactly is crashing.

You should compile Godot, to get information on where exactly is crashing.

You mean compile the game, and watch for crash codes in a terminal?
Or you mean, compile Godot from source?

@polytect You can download one of the builds from this repository and run it using a debugger.
I'll upload 3.2.1 binaries soon so you can test the latest version, but the crash may be reproducible with 3.2 anyway.

@polytect You can download one of the builds from this repository and run it as usual. It should provide an helpful backtrace when it crashes.
I'll upload 3.2.1 binaries soon so you can test the latest version, but the crash may be reproducible with 3.2 anyway.

I've downloaded and tried, and the new debugger shows that it has something to do with Audio, which start to make sense. Plus I see where exactly it crashed. Thank you for the build! I am trying to find why its crashing, and hopefully a solution for that.
here is the result now:
handle_crash: Program crashed with signal 8
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /usr/lib/libc.so.6(+0x3bd70) [0x7f762b6cdd70] (??:0)
[2] AudioStreamPlaybackSample::mix(AudioFrame*, float, int) (/root/godot/scene/resources/audio_stream_sample.cpp:353 (discriminator 4))
[3] AudioStreamPlayer2D::_mix_audio() (/root/godot/scene/2d/audio_stream_player_2d.cpp:61)
[4] AudioStreamPlayer2D::_mix_audios(void*) (/root/godot/scene/2d/audio_stream_player_2d.h:81)
[5] AudioServer::_mix_step() (/root/godot/servers/audio_server.cpp:336 (discriminator 2))
[6] AudioServer::_driver_process(int, int*) (/root/godot/servers/audio_server.cpp:248)
[7] AudioDriver::audio_server_process(int, int*, bool) (/root/godot/servers/audio_server.cpp:67)
[8] AudioDriverPulseAudio::thread_func(void*) (/root/godot/drivers/pulseaudio/audio_driver_pulseaudio.cpp:350)
[9] ThreadPosix::thread_callback(void*) (/root/godot/drivers/unix/thread_posix.cpp:76)
[10] /usr/lib/libpthread.so.0(+0x946f) [0x7f762b9ae46f] (??:0)
[11] /usr/lib/libc.so.6(clone+0x43) [0x7f762b7913d3] (??:0)
-- END OF BACKTRACE --

Found the bug trace:
this is the code executed every physics frame:
## wind is AudioStreamPlayer2D
onready var wind = get_node("wind")

func proc_wind(velocity):

	wind.volume_db = -80 + clamp(velocity / 20, 0, 80)
	wind.pitch_scale = clamp(velocity / 5000, 0, 1)
	if not wind.playing:
		wind.play()

Crash Happens, when velocity reaches 0.
And as we know, 0 cant be divided.
So now it works if I modify this way:
pitch_scale
wind is AudioStreamPlayer2D
onready var wind = get_node("wind")
func proc_wind(velocity):
wind.volume_db = -80 + clamp(velocity / 20, 0, 80)
wind.pitch_scale = _clamp(clamp(velocity, 1, INF) / 5000, 0, 1)_
if not wind.playing:
	wind.play()

And it crashes the same way, as soon as you run the game, without an error if:
we add **one 0** to **5000**
## wind is AudioStreamPlayer2D
onready var wind = get_node("wind")

func proc_wind(velocity):

	wind.volume_db = -80 + clamp(velocity / 20, 0, 80)
	wind.pitch_scale = clamp(clamp(velocity, 1, INF) / **50000**, 0, 1)
	if not wind.playing:
		wind.play()

What do you think?

The only "suspicious" thing I can note here is indeed the pitch_scale being 0. And in fact, the inspector doesn't let me to set the value 0 (only lets me go to 0.01), and if I set it as 0 in GDScript, Godot spits a bunch of errors, but doesn't crash.
Just to confirm this: try changing your line to:
wind.pitch_scale = clamp(clamp(velocity, 1, INF) / 50000, 0.01, 1)

It looks like it is possible to set the pitch_scale to 0 and cause a crash: at audio_stream_sample.cpp:353, increment becomes 0, with a division by zero error. This must be the problem OP has run into.
But there is a safe-guard in audio_stream_player_2d.cpp:311 preventing this variable from becoming less than 0.0. I don't understand much how this guard works, but is this enforcing that the variable can't go below 0.0, or just warning the user?

But there is a safe-guard in audio_stream_player_2d.cpp:311 preventing this variable from becoming less than 0.0. I don't understand much how this guard works, but is this enforcing that the variable can't go below 0.0, or just warning the user?

If p_pitch_scale <= 0, it will raise an error and abort. So the pitch_scale variable will not be set to that invalid value.

If p_pitch_scale <= 0, it will raise an error and abort. So the pitch_scale variable will not be set to that invalid value.

You're right. If I try to set the pitch to 0, it won't update the value. And even if I make it a really low value (like 0.00000000000002), Godot won't crash.
@polytect can you provide a minimal project that causes the issue? I'm trying to reproduce it, but can't.

Ok I will try. I'm on it

Here you go, a minimal working project.
Polytects_Audio_bedbugs.zip

Hold SPACE to lower the pitch, and it will happen.

Big Thank you!


WPF: Redraw plots using a non-blocking background thread

This is almost exactly the same as #3373 but for WPF. Checks whether Refresh is called on a UI thread, and if not, calls asynchronous Dispatcher.BeginInvoke(Refresh).

This looks great @drolevar, thanks so much! 🚀


cvat_redis problem after upgrading to newest dev commit

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce
I am fresh in wokring with CVAT and computer science in general, so might just be a dumb mistake/hardware limitation on my end, but checking here just in case. Let me know what more info you need and i will respond shortly!
I have been using CVAT with serverless functions, not having any issues with composing. New function released with latest dev commit, so followed your "Upgrade guide" to change to a stable version, then went to upgrade to latest dev. Error as follows.

docker working fine on my old dev (month old maybe)
docker compose down
git checkout tags/v2.8.2 (to test stable version change. everything worked fine)
git checkout develop
git pull
docker compose up -d
CVAT not stable in docker desktop, cvat_redis constantly restarting
docker logs cvat_redis:

:~/cvat$ docker logs cvat_redis
1:1:C 15 Nov 2023 11:05:54.643 # oO0OoO0OoO0Oo KeyDB is starting oO0OoO0OoO0Oo
1:1:C 15 Nov 2023 11:05:54.643 # KeyDB version=6.3.4, bits=64, commit=7e7e5e57, modified=1, pid=1, just started
1:1:C 15 Nov 2023 11:05:54.643 # Configuration loaded
1:1:C 15 Nov 2023 11:05:54.643 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:1:C 15 Nov 2023 11:05:54.643 * Initializing FLASH storage provider (this may take a long time)
1:1:C 15 Nov 2023 11:05:54.646 # ERROR: Failed to initialize flash storage provider. Details to follow below.
1:1:C 15 Nov 2023 11:05:54.646 #        Invalid argument: Column families not opened: 40, 39, 38, 37, 36, 35, 34, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33
... (looping)
Expected Behavior
Expected latest dev to work without error like earlier versions always have.
Possible Solution
Full removal and fresh re-install? I don't have anything critical stored as of now.
Context
Could it be that i have to little free RAM? in that case i dont understand why it was working earlier.
:~/cvat$ top
top - 12:15:56 up 41 min,  2 users,  load average: 0.08, 0.65, 0.68
Tasks:  48 total,   1 running,  47 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.2 us,  0.6 sy,  0.0 ni, 99.0 id,  0.1 wa,  0.0 hi,  0.1 si,  0.
MiB Mem :   7826.3 total,   1469.1 free,   3154.5 used,   3202.7 buff/cache
MiB Swap:   2048.0 total,   1901.1 free,    146.9 used.   4360.7 avail Mem
Environment
1. :~/cvat$ git log -1
commit 401989d0a20794235e16aa33665bf9587c2f60df (HEAD -> develop, origin/ma/default-prefix, origin/develop, origin/HEAD)
Author: Boris Sekachev<EMAIL_ADDRESS>Date:   Tue Nov 14 18:11:12 2023 +0200

    Added new tools to join masks together and to slice a polygon/mask into two parts (#7084)
2. Docker version 24.0.6
3. No
4.
Docker Compose version v2.23.0-desktop.1
WSL version: <IP_ADDRESS>
Ubuntu 22.04.2 LTS

I assume the reason is that we have upgraded keydb to the new version and it can't load the flash created by the previous version.
Just try deleting the corresponding volume, most likely its name is cvat_cvat_cache_db using the docker volume rm cvat_cvat_cache_db command. Not that you need to stop and delete keydb container before.

I assume the reason is that we have upgraded keydb to the new version and it can't load the flash created by the previous version. Just try deleting the corresponding volume, most likely its name is cvat_cvat_cache_db using the docker volume rm cvat_cvat_cache_db command. Not that you need to stop and delete keydb container before.

Thanks for that.
I am facing the same issue right now.
That really solve my problem.

Thank you! Fixed the issue for me as well.


removeExpiredObjects deadlocks

Hi, currently removeExpiredObjects deadlocks, caused by 2 nested dispatch_sync(queue).
I think we have to move keys.forEach { self.objectForKey($0) } outside the dispatch call since objectForKey will dispatch on the queue anyway.
https://github.com/aschuch/AwesomeCache/blob/three/AwesomeCache/Cache.swift#L193

I've fixed this issue in 544b35c91e9333f61983b4b8af2d45d9d681f71f, please take a look :sparkler:


PPC 2.0: Update title length check in pre-publish checklist from 40 to 70 characters

Context
PPC 2.0
Summary

Update max title length from 40 to 70 characters (for the checklist)
Update font size for card footers to 12px to match designs and other cards

Relevant Technical Choices
There was two different font sizes in the new checklist for the footer text - I checked the designs and saw that the list elements should have a font size of 12px. Decided to update that here too.
To-do

[x] update spreadsheet of copy text

User-facing changes

Before
After

Testing Instructions

Turn on ppc 2.0 experiment
Go to editor
Make sure the title is empty or less than 10 characters
Open the checklist to see the error and the updated card styles

QA

[ ] This is a non-user-facing change and requires no QA

Reviews
Does this PR have a security-related impact?
no
Does this PR change what data or activity we track or use?
no
Does this PR have a legal-related impact?
no
Checklist

[x] This PR addresses an existing issue and I have linked this PR to it in ZenHub
[x] I have tested this code to the best of my abilities
[x] I have verified accessibility to the best of my abilities (docs)
[x] I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
[ ] This PR contains automated tests (unit, integration, and/or e2e) to verify the code works as intended (docs)
[x] I have added documentation where necessary
[x] I have added a matching Type: XYZ label to the PR

Fixes #8119

So these strings all have different font sizes? 🤔  That looks super strange to me.
In Figma the "Incorporate a brief description", "Don't exceed 70 characters" and the "Use as a representation of the story" string are all 12px. But in the screenshots above they are different.

So these strings all have different font sizes? 🤔 That looks super strange to me.
In Figma the "Incorporate a brief description", "Don't exceed 70 characters" and the "Use as a representation of the story" string are all 12px. But in the screenshots above they are different.

I updated them all to be 12px to match the designs, so now they should be consistent with the designs ✨


some fixes, still errors but less of them...

update, the person testing for me (i dont have the glove hardware) has gotten back to me saying it works!


Add google-symptoms data dip message

Summary:
Prerequisites:

[ ] Unless it is a documentation hotfix it should be merged against the dev branch
[ ] Branch is up-to-date with the branch to be merged with, i.e. dev
[ ] Build is successful
[ ] Code is cleaned up and formatted

Looks like


Migate and update to Swift 3.2

I anticipate this being the last version of Swift 3 that we support before migrating everything to Swift 4.
As Travis has committed to supporting Xcode 9 beta 5, a minor release is currently only blocked on swift.org providing Swift 3.2/4.0 binaries for our Linux build.  I've switched to using a nightly for now.

Linux build passed.  Last build with Xcode 9's passed before this.  Merging because Travis is experiencing instability with their macOS bots.


⚠ Bofrost.be has degraded performance

In 2380df3, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1053 ms

Resolved: Bofrost.be performance has improved in 191351e.


Update tflocal

Adding skip_requesting_account_id  = true

Hi @frankpengau - quick follow up, can you please provide some context around this change? Seems like this could be useful for tflocal users, but would be good to understand the rationale a bit better, and whether we should enable this always by default, or make it configurable (to be enabled via a config flag..). Thanks!

Thanks @frankpengau , that would be appreciated. Adding a configuration change like this one may potentially have quite some side effects for a large number of users, so we'd like to understand the issue better and have a reproducible test case first.. 👍  Thanks for your help!

Hi @frankpengau!
I'm closing this PR as we plan to implement config merge into terraform-local in the not too far future and that would provide the option to add this attribute.


docs: add blogpost about Keptn v2 release candidate

This PR adds the Keptn v2 RC1 blog announcement.

Need to run make markdownlint-fix to clear up a bunch of those errors

superseded by #3209


Windows Distributed Transaction Coordinator - DTC

🛑 IMPORTANT: You can get your feedback addressed faster if you use the comment section for the article in which you encountered a problem.
Impossible since the comment feature for the DTC article is disabled, and the whole article is marked as a previous version and no longer maintained.
Distributed Transaction Coordinator
Where  is the current documentation for DTC?

@Bartolomeus-649 What is the issue you are having?

@Bartolomeus-649 Is it still supported at https://docs.microsoft.com/en-us/lifecycle/products/ ?


Trouble building SWS on Mac

Rather a call for help than an actual 'issue'...
I've recently upgraded from Mountain Lion to High Sierra and now I'm having difficulties building SWS on Mac.
Apparently I can't run XCode 3.x (which is mentioned on the Wiki) anymore on High Sierra.
I've managed to integrate the 10.5 Base SDK (which is used by the SWS XCode project file) into the current XCode version. But when I try to build with the 10.5 Base SDK I get these errors:

I can build without errors changing the base SDK to latest (10.13) but obviously I don't want to permanently change the SWS project file.
Any ideas how to solve this ?

Hmm... I have a virtual machine with OSX 10.6 just for building SWS because the tools are so out of date.
Unfortunately I don't have a great answer.  Maybe someone else has been successful with newer versions of XCode?

Thanks Tim.
I'm also using a VM for Mac debug / build, so no biggie going back to earler OSX (until maybe at some point the SWS project files will be updated. :D).

I have always tried to stay in step with official Reaper compatibility - since Reaper supports OSX 10.5+ I think we're basically stuck.  It is what it is.  Soonish I will setup an auto-build that will just build latest from GitHub and drop it somewhere on the web.


serde1 vs serde feature (crates.io package vs GitHub source code)

Hi,
I notice that if using the crates dot io package, the following type of error occurs
the trait serde::ser::Serialize is not implemented for rsa::RSAPrivateKey

In this instance the Cargo.toml file is using the serde feature. For example
[dependencies]
rsa = { version = "^0.2", features = ["serde"] }

The GitHub source code [1] and config [2] choose serde over serde1. I believe that serde1 is deprecated.
If the following dependency in the Cargo.toml file is used the issue is resolved.
rsa = { version = "^0.2", features = ["serde1"] }

For example the private key can be easily serialised like this
use serde_json;
extern crate rand;
extern crate rsa;
use rand::rngs::OsRng;
use rsa::{RSAPrivateKey};
fn main() {
    let mut rng = OsRng;
    let bits = 2048;
    let key = RSAPrivateKey::new(&mut rng, bits).expect("failed to generate a key");
    let as_json_string = serde_json::to_string(&key).unwrap();
    println!("{:?}", as_json_string);
}

My main observation is that the crate is out of alignment/sync with the GitHub code, config and documentation. If the crate was updated then users would be able to use the following to enable the optional serde feature.
[dependencies]
rsa = { version = "^0.2", features = ["serde"] }

Hope this helps.
Kind regards
Tim
[1] https://github.com/RustCrypto/RSA/blob/master/src/key.rs#L51
[2] https://github.com/RustCrypto/RSA/blob/master/Cargo.toml#L59

thanks, the reason for this is that no new version has yet been published to crates.io, once that happens this will be resolved

Should be all fixed


refactor(share/shrex): cleanup shrex logs

Overview
Sort out logging level for shrex client / server logs.
DEBUG: unimportant errors, that doesn't affect logic
WARN: errors that could been induced by either party (client or server)
ERROR: node malfunction that needs operator attention
Since shrex client / server implementation propagates errors to the caller, default logging level should be set to ERROR, to reduce cognitive load on operator. Currently it is set in nodebuilder, but I would rather move default log level setting inside the package at some point.

Codecov Report

Merging #2079 (ec8351c) into main (d375373) will decrease coverage by 0.11%.
The diff coverage is 31.70%.

@@            Coverage Diff             @@
##             main    #2079      +/-   ##
==========================================
- Coverage   55.39%   55.28%   -0.11%
==========================================
  Files         207      207
  Lines       13176    13184       +8
==========================================
- Hits         7299     7289      -10
- Misses       5130     5151      +21
+ Partials      747      744       -3

Impacted Files
Coverage Δ

share/p2p/shrexeds/params.go
70.00% <ø> (ø)

share/p2p/shrexeds/client.go
52.05% <14.28%> (-1.37%)
:arrow_down:

share/p2p/shrexnd/client.go
62.50% <22.22%> (-1.06%)
:arrow_down:

share/p2p/shrexeds/server.go
59.63% <28.57%> (-2.64%)
:arrow_down:

share/p2p/shrexnd/server.go
66.40% <44.44%> (+0.26%)
:arrow_up:

logs/logs.go
90.47% <100.00%> (+1.00%)
:arrow_up:

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


Fix Java PreCommit Action correct branch to run

Found in https://github.com/apache/beam/pull/28434#issuecomment-1718278586
Also addressing https://github.com/apache/beam/pull/28075#issuecomment-1714652977

Also upload human readable test reports on failure

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @andreydevyatkin @damccorm

using a script checked that this the only one missed ./.github/actions/setup-action (by searching uses: actions/checkout and no .github/actions/setup-action)


lnd not getting new blocks from bitcoind

Background
lnd not receiving new blocks from bitcoind and falling out of sync
Your environment

version of lnd: lnd version 0.7.0-beta commit=v0.7.0-beta-rc1
which operating system (uname -a on *Nix): Linux 4.18.0-21-generic #22~18.04.1-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
version of btcd, bitcoind, or other backend: bitcoind v0.18.0
any other relevant environment details
Running Samourai Dojo Docker as backend with docker ports opened for communication between bitcoind (running in docker container) and lnd (running on host machine).

Steps to reproduce

Install Samourai Dojo v1.0 in accordance with https://github.com/Samourai-Wallet/samourai-dojo/blob/develop/doc/DOCKER_setup.md
Copy bitcoind data to Dojo bitcoind container --> https://gist.github.com/05nelsonm/96ad8da7724de3a66f44d6c2d70b361c)
Configure Dojo to work with lnd --> https://gist.github.com/05nelsonm/ef55dcc1fb3aa588c8135cd107ee5d8c
Install lnd in accordance with https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md
Run it

Expected behaviour
When new blocks are found lnd should be able to fetch them from bitcoind and not fall out of sync
Actual behaviour
lnd does not receive new blocks and then gets out of sync

So trying to reproduce the exact moment which it hangs up I think I've narrowed it down to some specific conditions. I'm still trying to get a repeatable method, but it has something to do with:
-while bitcoind and lnd are running, lock the screen on Ubuntu Desktop 18.04.
-login to the Zap Android App and access the node remotely.
-in the Zap app, switch back and forth between TX history and wallet (which will proc calls to the node for the wallet balance)
-on the phone, minimize the app (do not close out)
-after about a minute or so, go back into the app and unlock it and switch back and forth between TX history and wallet
-close the app
-wait for a while before unlocking Ubuntu (for blocks to come in)
-lnd has hung up
+I've gotten it to happen 3 or 4 times, but it's not every time... and only when Ubuntu Desktop is locked.
+Also noticed that if I was switching back and forth between TX history and the wallet in the app around the same time a new block came in, that's when it would happen
+not sure if it has something to do with the tls handshake interrupting bitcoind rpc communicating with lnd rpc, but there's something going on there.

Unable to reproduce - seems related to #3109 since both involve the use of containers.

Been running bitcoind on the host machine as opposed to inside of a Docker container, and everything has been working properly. Closing this issue and chalking it up to that.


[icons] Issues with the "CopyContent" Icon

so i was surprised to see the "copyContent" icon facing downwards, instead of "to the up and right" as i was expecting.

it just looks wrong to me, but that's okay, that might be me.
what puzzles me is that the "copyAll" icon right beside it DOES face the way i would have expected

and what's even weirder:
the "rounded" version of "copyContent" ALSO faces "my" way (aka the way i think is the only "correct" way for a copy icon)

which makes me think something went wrong with the base icon here?

Will rerun the script to pull the icons and see if it changes.

google icons faces up, but the mui icons faces down (from https://github.com/mui/material-ui/pull/35194).

but the mui icons faces down (from #35194).

:D


rename nix attribute dfeet to d-feet (the actual program name)

Describe the bug
I tried a nix run nixpkgs#d-feet (which failed) but eventually found it was dfeet.
@ktosiek any reason why not using d-feet as attribute name ?

You can set meta.mainProgram to the binary name so that it would be used with nix run.

We use d-spy as the attribute name for d-spy (#165860) so I think it should be fine to rename this as well :rofl:

ok thanks for the update and maintaining it this far.

since it is not maintained anymore, should we remove d-feet and advise people  to use d-spy instead in an alias ?


test suite results html missing python source page

Describe the bug
We should be able to see the python source for our tests via the test suite html.
Seems to be missing, here is an example blank page:
https://visit-dav.github.io/dashboard/2021-02-19-22:00/pascal_trunk_serial/operators_inverse_ghost_zone_py.html
(looked for a ticket but didn't find one about this)

The pages are actually getting generated, it's just that they essentially have no content. Here is the file for ANALYZE (databases_ANALYZE_py.html).
<title>databases/ANALYZE.py</title>

The page gets generated by HtmlPython.ColorizePython, which is located in HtmlPython.py.


Nicer label in settings

Context
Currently the icon is generic cog and label is just the extension code name:

Value and/or benefit
It would help users to navigate settings if the label and icon for this extension were more tailored. For example "jhub-apps integration" label, and icon whatever folks associate with https://github.com/nebari-dev/jhub-apps ?
Anything else?
No response

@aktech Do you know if jhub-apps has a logo that I could use here? Or should I use something else, like the Nebari logo?


some issues about vfxeditor:)

I already used the vfxeditor for a while. And I noticed some inconvenience for the programer who use this.They can be listed as follows.
1.Emitters and particles(including timelines) can not be renamed.I often get confused by the original name which name can 't presents itself after working for a long time. I wonder is this function easy to achieve？
2.Is it possible that these things can be copied and pasted ？even better with shortcut keys？
3.Sound emitter can only be chopped off from the tail, but it can not be separated and keep the latter part. Maybe there is a way to do that but I don't know it yet. If there isn't, can you make that happen? Or if there is, can you show me how to do that?
4.There are some skill effects can not be found in list but can be found by easyeye, most of them are continuous effects，including Salted Earth，Flamethrower，Doton.etc.Is it possible that these things can be added to the list？
Thank you for your working of vfxeditor and  your contributions！！！

Renaming was added in an update, sorry for not updating this issue. The new names are only preserved if you save your work as a workspace.
Copying and pasting for curve points is coming the next big update (which should be around when Endwalker releases).
I'm still looking into the sound emitter, missing VFXs, and copying and pasting things besides curve points

Renaming was added in an update, sorry for not updating this issue. The new names are only preserved if you save your work as a workspace.
Copying and pasting for curve points is coming the next big update (which should be around when Endwalker releases).
I'm still looking into the sound emitter, missing VFXs, and copying and pasting things besides curve points

what!you really do this! Thank you very much for taking my advice and realizing it！
The rest is not urgent. Just follow your rhythm. Anyway, I can achieve a lot of creativity with the current version！
Thank you again for your contribution!


NICE TO HAVE: selecting and expanding ('hiding') of nodes should be different actions

Left-Clicking a node automatically expands ('hides') the node and selects it for displaying. Perhaps clicking once could select the node while expanding can be done by double clicking?

Closed with https://github.com/quintel/etloader/commit/d5df06ebdeb9b3db97147c03eeb73892ed87b682


Add volume sync support

Volume sync support for api manager. The manifest changes were copied and pasted from api-manager repository.

@croomes I have rebased this PR to the latest.


feat(react): adds tab icons to connect ui transactions page

#3845
#3844  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gregfromstl and the rest of your teammates on  Graphite


No physics applied to RigidBody3D when TickInterpolator also active

new-game-project.zip
Netfox: 1.8.0
Godot 4.3

Attached is a minimal test project to demonstrate the issue.
Floating ball A has a StateSynchronizer and ball B has a StateSynchronizer AND TickInterpolator.
Ball A performs as expected but ball B is frozen in it's initial position.

RidigBodies don't directly support being moved the same way most other nodes do. They're expected to be driven almost exclusively by the physics engine.
So TickInterpolator which is interpolating things to fill in the gaps between ticks is probably not the right tool to use for RigidBodies.
The closest we can probably get is to sync physics state from the authoritative server and copy and apply them to the clients
This probably needs it's own dedicated Node. RegidBodySynchronizer?
It won't be able to participate in rollback either since there's no current way to run more than a single simulation per frame in Godot.

There's an implementation here of what a physics synchronizer can look like:
Copying the code to here as things tend to disappear on the Internet over time.
extends MultiplayerSynchronizer
class_name PhysicsSynchronizer
@export var sync_bstate_array : Array = \
	[0, Vector3.ZERO, Quaternion.IDENTITY, Vector3.ZERO, Vector3.ZERO]

@onready var sync_object : RigidBody3D = get_node(root_path)
@onready var body_state : PhysicsDirectBodyState3D = \
	PhysicsServer3D.body_get_direct_state( sync_object.get_rid() )

var frame : int = 0
var last_frame : int = 0

enum {
	FRAME,
	ORIGIN,
	QUAT, # the quaternion is used for an optimized rotation state
	LIN_VEL,
	ANG_VEL,
}

#copy state to array
func get_state( state, array ):
	array[ORIGIN] = state.transform.origin
	array[QUAT] = state.transform.basis.get_rotation_quaternion()
	array[LIN_VEL] = state.linear_velocity
	array[ANG_VEL] = state.angular_velocity

#copy array to state
func set_state( array, state ):
	state.transform.origin = array[ORIGIN]
	state.transform.basis = Basis( array[QUAT] )
	state.linear_velocity = array[LIN_VEL]
	state.angular_velocity = array[ANG_VEL]

func get_physics_body_info():
	# server copy for sync
	get_state( body_state, sync_bstate_array )

func set_physics_body_info():
	# client rpc set from server
	set_state( sync_bstate_array, body_state )

func _physics_process(_delta):
	if is_multiplayer_authority() and sync_object.visible:
		frame += 1
		sync_bstate_array[FRAME] = frame
		get_physics_body_info()

# make sure to wire the "synchronized" signal to this function
func _on_synchronized():
	correct_error()
	# is this necessary?
	if is_previouse_frame():
		return
	set_physics_body_info()

#  very basic network jitter reduction
func correct_error():
	var diff :Vector3= body_state.transform.origin - sync_bstate_array[ORIGIN]
#	print(name,": diff origin ", diff.length())
	# correct minor error, but snap to incoming state if too far from reality
	if diff.length() < 3.0:
		sync_bstate_array[ORIGIN] = body_state.transform.origin.lerp(sync_bstate_array[ORIGIN],0.05)

func is_previouse_frame() -> bool:
	if sync_bstate_array[FRAME] <= last_frame:
		return true
	else:
		last_frame = sync_bstate_array[FRAME]
		return false

Actually looking at the correct_error section in the code above maybe TickInterpolator can work if its set to transform.origin
A few comments in other places mention its a hack that lets you mess with the position of a RigidBody

Actually looking at the correct_error section in the code above maybe TickInterpolator can work if its set to transform.origin
A few comments in other places mention its a hack that lets you mess with the position of a RigidBody

what would be the property path of transform.origin, because my netfox gives warnings that it's an invalid path

@homhomhomhomhom

netfox gives warnings that it's an invalid path

Are you typing it like :transform.origin? It works for me.
@albertok

maybe TickInterpolator can work if its set to transform.origin

This technically fixes the issue and while there's a definite improvement over no interpolation, it is still quite jumpy and unstable.
https://github.com/user-attachments/assets/0a04cdb2-2d69-4ddf-9a42-daeb79aa3e76

There's an implementation here

Using this implementation, the physics are silky smooth on the client.
https://github.com/user-attachments/assets/6f2c8f1b-6cd3-4f0a-b30a-f05e77acb9e7


QueryBuilder Result in Array format PDO::FETCH_ASSOC

First, thank you so much for making this package, it is amazing!
It would be great to get query builder results as an associative array.
I see in vendor/illuminate/database/Connection.php:
line 102:
protected $fetchMode = PDO::FETCH_OBJ;
in file vendor/illuminate/database/Capsule/Manager.php:
line 47:
protected function setupDefaultConfiguration()
{
$this->container['config']['database.fetch'] = PDO::FETCH_OBJ;
$this->container['config']['database.default'] = 'default';
}
Is there currently an easy way to update the Illuminate container config?  What do you recommend is the best way to set the database.fetch = PDO::FETCH_ASSOC?
thanks!

I'm not entirely sure, but it seems like calling this method could work: https://github.com/illuminate/database/blob/d6731e6709c7d52e656c2c029c08a4c4e271fd23/Capsule/Manager.php#L150-L155


9.6 - 9.9

How does it determine 'if' Java, Python, PHP or .NET is being used as part of the Web App? Is it scanning the files deployed on the web app Kudu side and checking if any files match those runtime/languages?

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

ID: 5d190566-16b9-996a-43ff-430fb225a4a0
Version Independent ID: 350f0dd6-bd39-b5b6-f176-a403c7d3863c
Content: CIS Microsoft Azure Foundations Benchmark blueprint sample controls - Azure Blueprints
Content Source: articles/governance/blueprints/samples/cis-azure-1.1.0/control-mapping.md
Service: blueprints
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

Thanks for your comment. We are actively looking into it and will get back to you shortly.

#reassign:DCtheGeek

@jusso-dev Thanks for the question! The CIS blueprint sample deploys a number of Azure Policy definitions through a single initiative. The names under each control should match the name of the policy definition, which you can locate through the Portal. As an example, the "Ensure that 'Python version' is the latest, if used as a part of the Function app" deploys this policy definition. Looking at the policy definition, we can see that it's evaluating properties under Microsoft.Web/sites/config, specifically web.pythonVersion and web.linuxFxVersion for Python being configured and set to 3.6 (Windows) and 3.8 (Linux). It's not scanning the code, it's looking at the configuration of the Azure resources.  Thanks for the question!  cc / @jomolesk
@MicrosoftDocs/azure-cxp-triage #please-close


TypeScript Type Errors in generated client with Electric v0.12.1

Hi, after an evening of research, I finally tried to run electric in a minimal project, and while it now runs without issue, there seems to be a problem with the TypeScript type.
As you can see below, the prisma type generated by the electric client has a very large number of undefined types and an error in the type of liveMany().
 const { results } = useLiveQuery(db.post.liveMany())
  ^ const results: Omit<$Result.GetResult<Prisma.$PostPayload<$Extensions.DefaultArgs>, S>, “Please either choose `select` or `include`”>[] | undefined

"electric-sql": "0.12.1",

Reproduction Project https://github.com/Innei/electric-demo
npm run db:migrate
cd apps/web
npm run client:generate

Thank you!

👋 we've been working the last month on a rebuild of the Electric server over at a temporary repo https://github.com/electric-sql/electric-next/
You can read more about why we made the decision at https://next.electric-sql.com/about
We're really excited about all the new possibilities the new server brings and we hope you'll check it out soon and give us your feedback.
We're now moving the temporary repo back here. As part of that migration we're closing all the old issues and PRs. We really appreciate you taking the time to investigate and report the bug!


PY Library

Create a JavaScript & Python library that simplifies interaction with the Hydrafiles network for applications built on Hydrafiles

Hydrafiles is a lib now. Python implementation needs to be written.


Why is the QueryResult new function src/api/query.rs in influxdb2 explicitly specifying lifetimes ?

https://rust-lang.github.io/rust-clippy/master/index.html#needless_lifetimes

Seems like just code styling, I allow different code styles as long as it's pretty sensible. Using explicit lifetime vs implicit lifetime achieves the same thing.
Also since this is a question, closing this.


Fix link to XY Grid

The link to the XY Grid points here:
https://foundation.zurb.com/xy-grid.html (/xy-grid.html)
Point it to the right place:
https://foundation.zurb.com/sites/docs/xy-grid.html (./xy-grid.html)

Already fixed by https://github.com/zurb/foundation-sites/pull/10986/files. We just need to update the server to master. Poke @rafibomb


Severe performance issues of InfluxDB 0.9.6+

Right now dealing with the fact that influxdb has regressed to a point where a month of home automation and IoT data requires massive amounts of memory.
Need to find a way to back down to an older version of Influxdb as this has become so unstable and slow that it has halted all progress on the project.
https://github.com/influxdata/influxdb/issues/5429

Unfortunately this is not limited to 0.9.6 and has continued into 0.10.x
https://github.com/influxdata/influxdb/issues/5856#issuecomment-198628531
As it turns out some of the IoT data feeds create very high cardinality fields that - if used as tags - explode the memory consumption of influxdb.
I will have to revisit the various data feeds and convert many of the current tags to simple text fields to avoid this from happening. Seoul not be too difficult but it will mean that I will have to drop all of my IoT history for the 3rd time.
Hopefully this will be the last iteration.


More about Quarkus LTS strategy

This link is already documented in the second paragraph of the description, so it is not necessary to give it again.
The first paragraph was wrong though, opened #3641 to fix that.

:pray:


Suthesh/translation-workflow

Changes:

created translation workflow that gets triggered by pushing a translation tag

NOTE: This is made to work of crowdin. It can be replaced with a master version when crowdin is no longer required
Type of change

[ ] Bug fix
[x] New feature
[ ] Update feature
[ ] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[ ] Dependency update
[ ] Documentation update
[ ] Release

Hi @suthesan-deriv, I was thinking if this will block the release pipeline in case a new Landing page needs translation before being Released ?


Add documentation and description field to MRTK profiles

Describe the problem
MRTK ships with several profiles that are not clearly documented. Users don't know when to use which profiles (importing the example packages drags in quite a lot of profiles)
Describe the solution you'd like
We should document profiles that ship with official MRTK packages so users can understand when to use them.
The usage for each profile should also be reflected in the inspector with either a description field or a link to the documentation
Additionally we should clean up the existing profiles if there's any of the example ones that we actually don't need.
Additional context
follow up task from  PR #6825

This issue will be addressed in large part by #10120 .

Closing since tooltips were added when hovering over the various profiles in the Editor Inspector for the MixedRealityToolkit prefab as part of #10180.


Add Documentation for BackgroundTaskHelper

Thank you, I will merge this and add a link from the TOC as well


Multi type for properies OAS

Assume I have a JSON look like this
    {
        "key": "number",
        "value": 1
    },
    {
        "key": "website",
        "value": "google.com"
    }
]

Something.yaml
type: object
title: Something
properties:
  key:
    description: The key of something.
    type: string
  value:
    description: The value of something. (can be any type)
    type: ?
required:
  - field

How can I write type for the value which I don't have specific type

No type present means "any type".
  value:
    description: The value of something. (can be any type)


Don't use flags directly in structural Go funcs

Flagpoles should be passed in rather than used directly. Would like to avoid having an extra config object since the flags are in their own package anyhow. Is this an anti-pattern?
Support passing nil to the pkg funcs and filling in as necessary? How to handle defaults? Viper handles this via the bind that happens in the CLI, maybe modify hofmod-cli to create a DefaultFlagpole var?

closed in https://github.com/hofstadter-io/cuetils/commit/b38d044c3ca228fea60be3ffbae0f10032d6b1cd


v53 on the Quest 2 causes flashing and artifacts with foveated rendering

v53 on the Quest 2 is causing flashing pixels, tearing and stuttering with the v53 update.  Its was perfect with v51.  I can midigate it a little by turning the resolution down and it does seem to go away with FFR off but I cant run it like that.
I KNOW for a fact that the issue is realated to something thats changed in v53 since I was able to downgrade to v51 when it was on the PTC but now v53 is official and can downgrade anymore.  It happens with v54 ptc also.  These graphical issues make alxr not usable at any useful resolution.  I wish the Discord was still up so at lease i wouldnt feel like im alone with these issues :(

Please someone help or at least give it a try so I know its not just me

@Plato115 I'll have a look when I get a chance

@korejan Thank you!!!!! Reading that made my day Korejan!  Truth is you got the best software out for AR and mixed reality and we really appreciate the work you put into these releases.
If you have trouble reproducing the problem, turn up your resolution to 125 or 150 percent depending on your system power and try with FFR on then try it off.  There is some info in the v54 megathread on metas offical PTC forum posts that I dont understand in the last few pages but I know you'll know what they are talking about.  That MAY help, but again, im just an end user so this side of things is not my bag.
Again brother, THANK YOU

looks like the new server has fixed it. testing


Uniforming the tools used in each branch

Hi there!
Besides dvc, pip, and poetry, I've also noticed that some tools that are used in some branches are simply not used in others. I honestly didn't see the reason for that since there isn't an alternative being used for a replacement of them...

hydra
flake8
prefect

dvc-poetry
✅
❌
❌

dvc-pip
✅
❌
❌

prefect-poetry
❌
✅
✅

Why doesn't prefect-poetry use hydra?
Why don't dvc-poetry and dvc-pip use prefect or flake8?

I understood the reason of having dvc-poetry and dvc-pip as pip and poetry are two different strategies to manage packages, and therefore two different templates are needed. However, prefect-poetry seems unnecessary as prefect doesn't overlap the other tools' goals.
It seems that you started with one model and then you recreated it, thus abandoning some tools and adopting others. I am not sure... If PR are welcoming, I propose to adopt the same set of tools, unless they are conflicting or overlapping. Let me understand what is your idea so that I can collaborate with your project :)

Hey Rubem, thanks for bringing this up. I'm trying to keep the template lightweight, so I only want to include the most essential tools. My priorities have shifted over time, and I now believe that DVC is more important than Prefect. If you think both tools are necessary, feel free to create a separate branch that includes both.

Thank you for the feedback! Currently, I am working with other tools as well, but I am using your cookiecutter template to organize all such technologies in ready-to-use branches with a set of complementary tools. Maybe it is gonna take a while, but I will propose PRs once get acquaint with them.

Sounds good to me! Thanks for working on this. Let me know if you need any help.


SharedArrayBuffer is not defined

Expected Behavior

Actual Behavior

Reproduction Steps

Install insomnia-plugin-usage-logger plugin

Then setup the environment like this

After that send a request and it will throw error SharedArrayBuffer is not defined
Refer this URL for more
https://insomnia.rest/plugins/insomnia-plugin-usage-logger

Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
This is not the plugin issue till I can understand. This is the issue of Insomnia. Please check the issue.
Insomnia Version
Leatest
What operating system are you using?
Ubuntu
Operating System Version
Linux FA506IH 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Installation method
https://insomnia.rest/plugins/insomnia-plugin-usage-logger
Last Known Working Insomnia version
NIL

Hi @aghosh0605, thank you so much for reporting this! Also thank you for your detailed bug description.
We were able to follow your steps, and also managed to reproduce this bug. It seems we must have broken the SharedArrayBuffer functionality sometime after version 2021.7.2, which we noticed still works. Latest versions like 2022.5.1 and 2022.4.2 we do get the error:

We'll look into this as soon as possible, and we'll keep you updated here if there's a fix.

Hello @filfreire!
Are there any updates on the SharedArrayBuffer issue? I'm the author of the plugin, and I'm not sure I can get rid of that part.
Please, let me know how can I help you squash this bug. Thanks!


Feature request - Cancel zipping files into nw.exe

As for now, the nwb zipping the whole files into one directory,this is a huge problem for me when i've got more than 25 node modules included which i dont need them all on startup.
I think that in option something like: zip : false should be allowed in order to cancel the zipping of whole files into one huge one.
Thanks :)

Actually I think the best solution for this problem is to modify your workflow. The builder's task is to create the final build so I think it's not a very good feature to request "please not build that" from it :)
This is how I'm using it:
I have an app and a dist folder. My build task (I'm using generator-gulp-webapp) run some linting, compressing etc. (so it builds the HTML5, CSS, JS parts of the app), and put the builded webapp to the dist folder. After that, I've run the nwb on the dist folder, so the final .exe(win)|.app(osx) build contains only the production version of the code.

You need the node modules only for development, i need most of them for production....

@avihaymenahem then this was a misunderstanding from me. Sorry :)

@mllrsohn Can i get at least any direction so i can code it myself? :)

@avihaymenahem This option already exists for mac distribution (macZip) so you can have a look at how and where the switch is implemented by searching macZip in the code.

https://github.com/mllrsohn/node-webkit-builder/pull/193?

Is #193 what you want? How does it compare to #200?
cc @CamiloMM, @kessler, @felicienfrancois, @speedskater, @KalleV

Imho #193 is a different option. As far as i understood, #193 adds an option which allows to disable the merging of the zip file into the executable. #200 does not zip the application at all and therefore the application will not be extracted on startup.

What about addressing this with something like asar? - https://github.com/atom/asar

Released in 2.2.0. Thanks everyone!


Fixed Issue #11

Issue #11 has been fixed. If a single file is dragged into Alchemy, that file's extension is removed from the list of files it can be converted to (see image below)

I noticed the package.json and yarn.lock changed some dependencies, so please be aware of that.

Thanks for knocking that out so quickly! Much obliged

No problem, glad I could help!


How to turn off grab and slide to right & left sliding effect! And use only carousel controller buttons on the left and right!

Can you help me with this problem:

Pretty sure this isn't the right place for it. But it basically says everything you need in your console. you don't have access to the "" component when you call it. so you should check if it is registered correctly

Remove <md-*> components.


Feature/sliding min window

This PR implements the Window min-density as described in the Codaboros paper, section 3.2. The main purpose of Window min-density is to support the long fork chain selection rule.
Here's a quote from the paper that describe the intuition behind the long fork rule:
"The idea is that at any given point in time, we consider a window of slots and observe its density. As time progresses, the window shifts (by some slots) and we observe the new window density. Instead of maintaining all the window densities, we simply maintain the minimum thus far of all the window densities."
The actual implementation looks very different from the one describes in the paper because certain computation (i.e. array indexing) is very expensive to do inside snark. For efficiency reason I modify the algorithm a little bit. There is a unit test that shows the actual implementation is equivalent to the reference implementation across all inputs.
[CAUTION]:
Because the constants for the protocol has not yet decided. So I temporarily make
slots_per_sub_windows = k
sub_windows_per_window = c
Those are just some random choice.
We probably should not merge this PR until the constants are determined.

For the record, update_min_window_density adds 566 constraints. This could probably be a bit better but it's fine for now and we can optimize if need be.


Query is passed as reference in widget

I have created my own widget to display a graph:
$assessmentQuery = Assessment::find();
GraphOverTimeWidget::widget([
	'objectsQuery' => $assessmentQuery,
]);

Inside the widget I add further conditions to the query before executing it, e.g.
$this->objectsQuery
	->andWhere(['not', ['date' => NULL]]);
...
$results = $this->objectsQuery->all();

Then in the view, after calling the widget:
var_dump($assessmentQuery->createCommand()->rawSql);

I would expect this to show
"SELECT * FROM `assessment`"

but instead I get
"SELECT * FROM `assessment` WHERE (NOT (`date` IS NULL))"

If I pass a string through and change it or append to it (using .=) it doesn't affect the variable in the view
If I reassign the variable to be something else e.g. inside the widget $this->objectsQuery = User::find() it does not affect the variable in the view
I am wondering if the same happens when initialising any class properties in this way

This seems very odd and I can't find it documented anywhere so I am assuming it is a bug rather than being deliberate.

Q
A

Yii version
2.0.8

PHP version
5.6.22

Operating system
OSX El Capitan 10.11.5

http://stackoverflow.com/questions/6972860/object-copy-versus-clone-in-php


chore: 🤖 combine build-strategy tests

closes #396

Pull Request Test Coverage Report for Build 1047

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.644%

Totals

Change from base Build 612:
0.0%

Covered Lines:
635

Relevant Lines:
660

💛  - Coveralls

@theashraf Thanks for the contribution


"Compare selected" command should put the first selected tab into left side of diff editor

Repro

Holding ctrl/cmd, click on tab a.ts, then b.ts
Right click on one of the tabs and invoke "Compare selected" command
The diff editor is b.ts <-> a.ts which is counter intuitive to my selection order

Both AlexD and I struggled with this. If controversial, may be worth bringing up at standup.

closing as duplicate of https://github.com/microsoft/vscode/issues/226883


Fix accounts usage for autoscaler

What
The app and space audit event pages are erroring when they include audit events from the autoscaler. This is happening because we never anticipated this sort of actor field on an audit event:
    "actor": {
      "type": "user",
      "guid": "app_autoscaler",
      "name": ""
    },

We assumed that anything with type: user would have a UUID for a GUID. This makes complete sense, but it isn't the case for the autoscaler.
The autoscaler uses a UAA Client named app_autoscaler. It is reported with type: user even though it's a UAA Client, not a UAA user. The UUID is set to the name of the client, not a GUID.
Our views already had logic to cope with this problem. They fall back to printing out <code>{{event.actor.guid}}</code>. But the controllers try to convert GUIDs to validated user emails using https://github.com/alphagov/paas-accounts, and that code did not guard against this problem.
This PR changes the controllers so they only ask https://github.com/alphagov/paas-accounts about actors whose UUID is a valid GUID.
How to review

Deploy to a dev env I used a modified stub API to test this
[x] Check this works fine with normal events
[x] Look at events on the autoscaler's test app
[x] Look at events on the space containing the autoscaler's test app

Who can review
Not @46bit

I've tested this locally rather than in a dev env, and checked every relevant page. Here are two examples:


Added fail-fast option to CopyableDatasetRequestor (disabled by default)

Currently CopyableDatasetRequestor logs error and continue to perform distcp and makes job status success overall.
This change will have user to choose to make the job fail fast so that failure from CopyableDatasetRequestor will make the job fail immediately.

Integration test passed.

job property snippet:
gobblin.copy.CopyableDatasetRequestor.failFast=true

@ibuenros Could you take a look when you have a chance?

@ibuenros Thanks for the review and I've addressed PR comments.


Vertical collision with one way collision platform when colliding with another body to the side

Godot version:

3.2.3
OS/device including version:

Windows 10
Issue description:

There is a vertical collision as it goes up through a one way collision platform when it also collides with another body on top of the one way platform, leading to the kinematic body stopping completely instead of sliding up. In a platformer, this can lead to jumping through a one way platform, colliding with an NPC, and dropping immediately instead of sliding up the NPC collision box.

What's expected is that the body stops horizontal movement but continues sliding up, shown when you disable the one way collision platform.

Steps to reproduce:
Run the project.
Minimal reproduction project:

test_move_one_way_body_on_top.zip

Note: This not quite the same issue as #25967 and #43012, as removing the body on top of the one way platform lets the kinematic body pass through the one way platform, and removing the one way collision from the platform has the kinematic body collide as expected with the platform by sliding up instead of hugging the top of the platform.

One Way Platform Disabled
One Way Collision Removed

This should be fixed by #38471


Default systemd-boot entry not working

This is not a zectl issue : https://github.com/systemd/systemd/issues/15068
But as it is an important feature for zectl, i'm wondering if you workedaround it ?
If you reboot without beeing in front of your screen and without speedly select (and remember) the right boot env, so you get the last created boot env booted. It could be really painful if you didn't notice it...
I still don't get why i need to "activate" a bootenv after booted it ? As we select a bootenv in systemd-boot at boot, it sound like making the work twice, and being more complex without beeing useful. If i want to revert, i reboot to the previous boot env, so why activate mechanism offers more ?

Activating a boot env marks it as the default entry in the boot loader and promotes the dataset clone.

Ok thanks.
@zhimsel do you face the issue of systemd-boot not correctly boot defaultly set entry ?

I think I may have noticed it a week or so ago, but I don't remember. I can
check specifically if needed...

@zhimsel can you try and tell me if its working please ?

Sure. I'll test this later today.

@eoli3n So I just tested what I think was the issue, and it didn't occur for me. My test procedure (while booted into the default boot env):

zectl create test
zectl activate test
Confirm that loader.conf had test as the default BE
Reboot, verify that test was the actively selected bootloader entry (i.e. the default)
Select and boot into default instead
Confirm that loader.conf still had test as the default
Reboot again and verify again that test was still selected in the bootloader by default.

So it seems to have been fixed. I vaguely remember seeing it as a bug that was fixed in systemd-bootloader's bug tracker.
For reference:

zectl version: 0.1.2
systemd version: 246.6-1

¯\_(ツ)_/¯

Thanks for testing, I will try to understand what's going on here.

I also attempted @zhimsel 's test and cannot reproduce
bootctl version: systemd 246 (246.6-1-arch)

I think that my bootenv names are problematic:
pacmanhook-20200523T162905  NR      /                 2020-05-23 16:29
pacmanhook-20201121T114946          -                 2020-11-21 11:49

I will test @zhimsel procedure when i have time

related to https://github.com/johnramsden/zectl/commit/4d9139e242a472fb024bc8399e83049413904df4 and #7 ?  I'm running into this same problem on a fresh install for a new laptop.  Tried loader.conf with org.zectl-default.conf and org.zectl-default, no change in behavior with systemdboot efi default entry when I zectl activate foo. :/


Typo/additional description/range for type column

I made a couple corrections to type column, fixing a typo for datatype and adding Description/Range to match what is in sys.dm_pdw_dms_workers. Also changed execution_id column to show correct columns for the "key for this view".

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


no pointer mouse in kirkstone?

Hi guys,
I do not have the mouse pointer on a build for kirsktone.
# cog --version
0.14.1 (WPE WebKit 2.38.2)
My relevant sha1 layers are:
meta-yocto-bsp = "HEAD:d3e378397395542179a8497fbff4b610f6f7e802"
meta-oe
meta-python
meta-networking
meta-webserver = "HEAD:1f31570d0795da90083d1dbf28127c90908e30ee"
eta-freescale = "HEAD:3f5fc5810cfb7be61b487ade0a7ecfaeafa3d2aa"
meta-webkit = "HEAD:eb31f54387bfd309ec3e936b5f19febaac8045bb"
Does anyone have the same problem or is just me? Maybe I need to export some environment variable to see it?
I checked on a touch display and in the HDMI monitor without luck. I am running it on top of wayland, where the mouse works.

Assuming you are talking about the Cog FDO platform for Wayland (e.g. Weston), I think is matter of the  Weston itself. You could try with this attached file (backported recipes of wayland and weston from Poky master).
recipes-backport/
└── wayland
    ├── libinput
    │   ├── determinism.patch
    │   └── run-ptest
    ├── libinput_1.19.4.bb
    ├── mtdev_1.1.6.bb
    ├── required-distro-features.inc
    ├── wayland
    │   ├── 0001-build-Fix-strndup-detection-on-MinGW.patch
    │   ├── 0002-Do-not-hardcode-the-path-to-wayland-scanner.patch
    │   └── run-ptest
    ├── wayland_1.20.0.bb
    ├── wayland-protocols_1.27.bb
    ├── wayland-utils_1.0.0.bb
    ├── weston
    │   ├── systemd-notify.weston-start
    │   ├── weston.desktop
    │   ├── weston.png
    │   └── xwayland.weston-start
    ├── weston_11.0.0.bb
    ├── weston-init
    │   ├── init
    │   ├── weston-autologin
    │   ├── weston.env
    │   ├── weston.ini
    │   ├── weston.service
    │   ├── weston.socket
    │   └── weston-start
    └── weston-init.bb

You could add these recipes in one of your project layers:
wayland.zip

Hi Pablo,
Thanks for your replay...
The attached zip is empty, could you reattach it
"""
$ unzip -l wayland.zip
Archive:  wayland.zip
Length      Date    Time    Name

    0  2023-01-25 16:26   wayland/

    0                     1 file

"""
Regardless to that, I get all all the poky fixes you mentioned from poky master, but despite of that, the mouse still does not work on my side.
"""
project sources/poky/                           (*** NO BRANCH ***)
--     meta/recipes-graphics/wayland/files/0001-wayland-info-Fix-build-without-libdrm.patch
--     meta/recipes-graphics/wayland/libinput_1.22.0.bb
--     meta/recipes-graphics/wayland/wayland-protocols_1.31.bb
--     meta/recipes-graphics/wayland/wayland-utils_1.1.0.bb
--     meta/recipes-graphics/wayland/wayland_1.21.0.bb
-m     meta/recipes-graphics/wayland/weston-init.bb
-m     meta/recipes-graphics/wayland/weston/xwayland.weston-start
--     meta/recipes-graphics/wayland/weston_11.0.1.bb
"""
I removed all my sstate and cache files, so I did a build from scratch, but with no luck.
I still has the issue no resolved. I was looking for a solution, and in some threads people mention something about "COG_USE_WAYLAND_CURSOR".
Maybe should I try with that option?
Using xwayland I can see the cursor, but not when launching "cog" on top of it.
BR / Isaac

Here: wayland.zip
I experimented the same issue and finally I fixed by backporting the wayland and weston recipes.
To check what version of the recipes is using your bitbake environment:  `bitbake-layers  show weston wayland*

Thanks!
Finally I have it working. For that, I have applied the next patch on my recipe (https://github.com/Igalia/cog/commit/fe83f9b721f67ffa4d53c5261fc447355ebe06da)
webkit/recipes-browser/cog/cog/0002-wl-Fix-wrong-wl_shm-for-cursor.patch
webkit/recipes-browser/cog/cog_%.bbappend
I did not need to apply your attached zip file


Strings for Gulliver

Here are the strings for the Gulliver (Russian version of the Note):
    "Gulliver-ru": {
        "MODEL": "MC_GULLIVER",
        "STRING_SETTINGS": "wDNy4yMayA4nnQfzAYYqV3ih6uu363MoyfhaX9MtbCQk",
        "STRING_UPGRADE": "xzUDklMaz39aPNJAl45ca7c3hOrBQlNYZh+iZdK64fIo",
        "STRING_LOCAL": "3xRR0nR2lFLKpw5g71X5JGqc0/hZQhmJM9idyx1b"
    }

Tested just now.

Thank you for the strings! The strings are verified (with https://onyx-boox.ru/files/gulliver/update.zip) and merged.


Docs: Enterprise Self service improvement

Closes #7812
Closes #7867
Mostly re-used @itaiad200 docs and organized accordingly.

@talSofer In case you started already review added new commit that makes the TOC show sub sections


Make the helper Pod timeout configurable

...because depending on the helper Pod a different timeout may be needed.
My use case is cache-provisioner that requires the helper Pod to synchronize the volume contents with an image registry which may take more than the hardcoded timeout of 2 minutes.

Sometimes when load is high, helper pod takes > 2min to create, which cases infinite timeout when creating PV. We enlarged timeout from 2min to 4min and problem solved.

I see that this was addressed in the https://github.com/rancher/local-path-provisioner/pull/166, but it was never merged into the master. Is there any way to increase the timeout of helper pod by using master version of the provisioner? Or the only way to do this is to fork the project and edit the source code?
@daicang How you increased the timeout?


Combine all the KBPKI.GetCurrent* functions

This is cleaner, as it avoids multiple
calls, and also guarantees that all the
fields are in sync with each other.

This PR is mind-numbingly tedious, but I highlighted all the noteworthy changes.

Kicking this over to jzila, as strib is pretty overloaded.


refactor: convert RichTextEditor from class to functional component

Checklist

[x] the contributor license agreement is signed
[x] commit message follows commit guidelines
[ ] tests are included
[ ] screenshots are included showing significant UI changes
[ ] documentation is changed or added

Description of change

Convert RichTextEditor from class component to functional component.

Rerun one more time.

@PenghaiZhang Is it good? if no issue I will continue refactoring.

@PenghaiZhang Is it good? if no issue I will continue refactoring.

Hi @edalex-yinzi , you should remove the code rather than just comment it out.

Hi @edalex-yinzi , unfortunately both Codebuild and GHA failed on LoginNoticeMenuPropertiesSerial.
Your last commit was to tidy up the imports so I am not so sure...perhaps try to keep the original import order ?


Is the library alive?

Hi!
As far as I see, the library is not maintained anymore. @fasterthanlime do you still maintain this library? Because now the current library state is a little bit unclear.
Thanks in advance!

I haven't looked at it in a long while, that's for sure.
If I magically had time to take care of it again (which I probably won't), the first thing I'd do is look at its design with fresh eyes, considering the advances made in async land since it was first put together. I have no idea if it would still hold up :)


Put the variants of Ops in numeric order

For example:
https://github.com/ethereum/execution-specs/blob/5ab5c6fa4ba7243acbf7ce4abf1ad972cd1e5466/src/ethereum/cancun/vm/instructions/__init__.py#L205-L214

Sure! You'll have to make a second pull request for the forks/prague branch though.


conserver: fix cross compilation

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 352378 run on x86_64-linux 1

1 package built:

conserver

@NickCao are you planning to open a PR back to upstream regarding this?

@NickCao are you planning to open a PR back to upstream regarding this?

I'm not even sure if this should be considered a coreutils bug.

@NickCao are you planning to open a PR back to upstream regarding this?

I'm not even sure if this should be considered a coreutils bug.

Edit: or our installedl should be wrapped with --strip-program

@NickCao are you planning to open a PR back to upstream regarding this?

I'm not even sure if this should be considered a coreutils bug.

Or our install should be wrapped with --strip-program

I meant upstream to conserver

I meant upstream to conserver

Sure, to make it respect the STRIP variable.


[WFLY-19793] App client container should log java.lang.NoClassDefFoundError failures and other failures while loading the appclient main class

https://issues.redhat.com/browse/WFLY-19793
This should improve the logging of failures seen when loading the app client main class

Thanks @scottmarlow

Thanks @bstansberry!  Nice to see this change in!


No Helm repo for this chart

Is there a plan to either create a helm repo for distributing this chart or adding it to the helm official repo?

Echoing this.

Glad to see the interest in our chart :) There are some very exciting things coming along for running CircleCI jobs on your k8s cluster, including a helm chart repo. We'll be sure to keep this space updated once we have more to share!

It's exciting times @mattiwrk! We've just launched the open preview for our container job runner container-agent which is a more flexible way to run your CircleCI runner jobs in a k8s cluster. This works much closer to our cloud docker executors allowing you to specify arbitrary container images that meet our custom image requirements.
Now that we have our helm repo setup as well we'll be making the existing launch-agent chart available on there in the near future as well.


Add 3.0.0

See:
https://github.com/rspec/rspec-core/pull/2826/files
https://github.com/rspec/rspec-expectations/pull/1261
https://github.com/rspec/rspec-mocks/pull/1378
https://github.com/rspec/rspec-support/pull/470


Documentation updates, type annotation fixes, and new Table helpers

The partition info and slabinfo helpers had a couple small items that I wanted to address related to the docstrings and type annotations. I tweaked them and ensured that documentation builds successfully.
I also added two new table helpers: Table and FixedTable. Their docstrings should be self-explanatory, but the nice thing about them is that they can take care of the string formatting on your behalf, and they can also align individual columns to the left and right. By using FixedTable, you can also get output that is printed immediately, rather than all at once at the end of a loop. This is a major improvement for users, as it stinks to run a command and wait for a long time for a table to be output. To show the improvement, I moved the dentrycache helper to it, and the slabinfo helper, which can run a bit slow on heavily fragmented machines.

Additional changes added here:

Previously the vmcore test logs only got uploaded to gitlab when the test succeeded. Obviously that's less than ideal, so I've fixed that.
The recently merged slabinfo helper is great, but doesn't support the recent 5.17 change from struct page to struct slab. I've added support for that here, which helps support UEK8 and RHCK on OL9.

Thanks @biger410, unfortunately I can't merge directly so I'll need you to re-approve.


Data grid: Add color to urls

Add colors to datagrid urls. This means
.slick-cell a { color: #428bca; } to datagrid.css

No way of testing.

ok.

Passed on develop


Include support for root cause CVE tags

We previously discussed including support for CVE level tags (which can be applied to the CNA or ADP containers) that assist in identification of root cause.

Tag
Definition

Hardware Root Cause
Tag   this to a CVE if the primary root cause of the security vulnerability is   originated from the hardware component of the affected product(s).  The   intent is to facilitate Hardware Designers to learn how to prevent similar   weakness.       Even   when a hardware vulnerability can be addressed by a SW workaround, the   “Hardware Root Cause” tag should still be applied, since the focus is on how   the issue is introduced, not how it is remediated.

Software Root Cause
Tag   this to a CVE if the primary root cause of the security vulnerability is   originated from the software component of the affected product(s).  The   intent is to facilitate Software Developers to learn how to prevent similar   weakness.

This could be expanded to include other concepts such as protocol or specification root causes. Ex:

Tag
Definition

Specification   Root Cause
Tag   this to a CVE if the primary root cause of the security vulnerability is   originated from the industry specification that the affected product(s)   comply with.  The intent is to facilitate Industry Specification Groups   to learn how to prevent similar weakness.       If   the root cause of the CVE is related to inappropriate adoption of an industry   standard (e.g., use of an obsolete cryptographic algorithm) or incorrect   implementation of an industry standard (e.g., product does not implement the   error recovery flow as captured in the protocol specification) in the   affected product(s), the appropriate “Hardware Root Cause” or “Software Root   Cause” should be applied instead.

Is this tag under consideration for inclusion?

"root-cause-hardware" : Capture: physical, circuits, unchangeable -  unrelated from remedy.

Maybe this would be covered by CPE using the part field. Possibly a new property within the affected block. Could possibly be derived from the CWE. Maybe a flag under problemType to define hardware or software root cause. What is the delivered value of adding these tags and who uses them. From remediation perspective, this tag may not be useful.

Based on my understanding of what the CWE folks were looking for back when this was originally requested, CPE is not a viable solution for identifying this data.
The original intent was to be able to identify (amongst organizations that utilize them) which records appear to be rooted in hardware/software.
If there are concerns around this, we can reach back to the CWE folks for revived perspective of the value add.

Do we know who would be publishing this data? This strikes me as something that would be nice to have but quite hard to produce in a reliable manner.


[BLOCK]

Domain
List

s3-analytics-events.easybrain.com
ads

Was looking through my family's NextDNS config.
Looked the domain up, Google had nothing to say of relevance.
Did “easybrain analytics” and there isn't much of relevance, but their LinkedIn has the following:
Predictive analytics, data-driven approach, in-house systems and tools, machine learning...
I have reason to believe this URL is part of their in-house analytics and reason to believe that it's used in their own apps.
I haven't noticed any impact to their apps when I blocked the address.

There is one thing I can't read from this issue, Have you seen any hits on the record in question? and if = TRUE, where.
The reason I'm asking is if it is solely some inhouse, backend, obfuscated or proxied, it wont make much sense to add the bits to any lists :unamused:
About why it should be added, well we couldn't agree more from there own description :+1:

There is one thing I can't read from this issue, Have you seen any hits on the record in question? and if = TRUE, where.
The reason I'm asking is if it is solely some inhouse, backend, obfuscated or proxied, it wont make much sense to add the bits to any lists 😒
About why it should be added, well we couldn't agree more from there own description 👍

Is there any tool I could use to, say, check if a domain is on any popular filter/hosts list?

Is there any tool I could use to, say, check if a domain is on any popular filter/hosts list?

I know @funilrys kind a have one within his https://github.com/Ultimate-Hosts-Blacklist/Ultimate.Hosts.Blacklist project as they are working with a lot of sub lists from external sources, however i can't remember the url to the "search" function.
The the real question might be, is there a search tool, to search good qualified blacklists, as I can come up with a lot of popular, but absolutely not among what i would consider near even good sources.
PS: found the url with a little searching https://hosts.ubuntu101.co.za/app/contents

Is there any tool I could use to, say, check if a domain is on any popular filter/hosts list?

I know @funilrys kind a have one within his https://github.com/Ultimate-Hosts-Blacklist/Ultimate.Hosts.Blacklist project as they are working with a lot of sub lists from external sources, however i can't remember the url to the "search" function.
The the real question might be, is there a search tool, to search good qualified blacklists, as I can come up with a lot of popular, but absolutely not among what i would consider near even good sources.
PS: found the url with a little searching https://hosts.ubuntu101.co.za/app/contents

I happen to have noticed Steven Black likes using StevenBlack/ghosts for StevenBlack/hosts, but it's a comparison tool, not a search tool.

Hi @CyanoTex
Yes @ghost is some sort of a comparison script, while https://hosts.ubuntu101.co.za/app/contents is based solely on very lists currently being availability tested by the @Ultimate-Hosts-Blacklist project by @mitchellkrogza and @funilrys
I happens to notice your contributions on @Disconnectme too, and in relation to your previously question, I can announce that there are being worked on something of what you are requesting here https://www.mypdns.org/project/view/15/ The most basic is we are going to merge a global SQL db whit all (sub)-domains known for doing bad stuff with the availability test of @PyFunceble, this will be divided into sub headlines as

User uploaded records (hosts files)
Extraction of active domains by category
User driven categorizing /classification https://www.mypdns.org/T2686
Thin Client driven (Locked Issues)
Central maybe decentralizing the DB's

So if you have idea in a brainstorm for what you would like such a system should be able to give you for be usable, you are ab most welcome to throw in an idea, even in brainstorm format. and tag it with Matrix
Until the release of funilrys/pyfunceble version 4.0.0 there are plenty of room for even the wildest suggestions


SDK based project does not read outputpath from directory.build.props

SqlPackage or DacFx Version:
.NET Framework (Windows-only) or .NET Core:
Environment (local platform and source/target platforms):

Steps to Reproduce:

Updating old sql database proj to sdk based database proj
Defining outputpath in directory.build.props build fails. Overriding in proj file helps build succeed.

Did this occur in prior versions?  If not - which version(s) did it work in?
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build">
  <Sdk Name="Microsoft.Build.Sql" Version="0.1.9-preview" />
  <PropertyGroup>
    <Name>UADB</Name>
    <DSP>Microsoft.Data.Tools.Schema.Sql.SqlAzureV12DatabaseSchemaProvider</DSP>
    <ModelCollation>1033, CI</ModelCollation>
    <ProjectGuid>{d34-d3b-3bd0-89aa1-g87f7a}</ProjectGuid>
	<EnlistmentRoot>$(MSBuildThisFileDirectory)..\..</EnlistmentRoot>
    <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
    <OutputPath>$(EnlistmentRoot)\bin\$(Name)\$(Configuration)</OutputPath>
    <TargetDatabaseSet>True</TargetDatabaseSet>
  </PropertyGroup>
  <ItemGroup>
    <Compile Include="AssemblyInfo.cs" />
  </ItemGroup>
  <ItemGroup>
    <Reference Include="System" />
  </ItemGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.SqlServer.Dacpacs.Azure">
      <GeneratePathProperty>true</GeneratePathProperty>
      <SuppressMissingDependenciesErrors>False</SuppressMissingDependenciesErrors>
      <DatabaseVariableLiteralValue>master</DatabaseVariableLiteralValue>
    </PackageReference>
  </ItemGroup>
  <ItemGroup>
    <PreDeploy Include="Scripts\PreDeployment.sql" />
    <PostDeploy Include="Scripts\PostDeployment.sql" />
  </ItemGroup>
  <ItemGroup>
    <Folder Include="Scripts\" />
  </ItemGroup>
</Project>

Any work around to define the above OutputPath property in directory.build.props?
(DacFx/SqlPackage/SSMS/Azure Data Studio)

May be related to #117

May be related to #117

So it's still not resolved?

Not yet, I'll work on a fix for next release. It's interesting because passing it in from command line works, so it might be an ordering issue where a property is being overridden by its default.

@jthapa01 I'm having trouble reproducing the issue, can you check if I'm missing something? I set up this repo with OutputPath set in Directory.Build.props, which is honored when I call dontet build on Database1
https://github.com/zijchen/DacFxIssue278
Can you also share which .NET SDK version and OS you're using? I tested with .NET 6 and 7 on Windows, both were working.

@jthapa01 I'm having trouble reproducing the issue, can you check if I'm missing something? I set up this repo with OutputPath set in Directory.Build.props, which is honored when I call dontet build on Database1
https://github.com/zijchen/DacFxIssue278
Can you also share which .NET SDK version and OS you're using? I tested with .NET 6 and 7 on Windows, both were working.

We using msbuild to build the solution. Net6 on windows.

I'm still not able to reproduce the issue with msbuild. What version of msbuild are you using? msbuild /version
Would you mind sharing a sample repro?

I'm still not able to reproduce the issue with msbuild. What version of msbuild are you using? msbuild /version
Would you mind sharing a sample repro?

<IP_ADDRESS>04


compact code in geometries

As discussed in #617, this compacts the code in osmnx/geometries.py, such as removing unnecessary code in conditions and list comprehensions.

Coverage decreased (-0.003%) to 92.361% when pulling ff5b39f664b8a8271afa6b278a005f77d0fd250c on eumiro:compact-geometries into 8d9e6af04a380931f0426b6ac3ab8cc0d708cfff on gboeing:master.

@eumiro thanks for this proposed enhancement. I'm going to request a review from @AtelierLibre as he was the primary author of this module and this PR would greatly benefit from his expert eye.

@gboeing @eumiro I did scan through the changes before and they looked like quite specific optimisations that you might both be better placed to assess than me but I'll have a look and come back to you.

@eumiro @gboeing Thanks both. Just so I'm clear, the principal reasons for the changes are:

to remove the sum of the list comprehension in line 338 and to replace it with a not any() and sum() of a generator later on
to check for empty lists/dicts with if not lst: rather than if len(lst) == 0:
to remove a redundant if statement in line 636
to check whether the invalid_geometries_filter series has values in it with .any() instead of sum(invalid_geometries_filter) > 0

If these changes improve the code then, unless I have missed something, it seems okay to me.

@eumiro tests are failing (could you fix that?) but otherwise this looks good.


Scoped commands

oao all could have a --scope command much like lerna which isolates to specific packages.

Could you give an example of the use case?


Fix patch so that it build with the latest NXP BSP

Submitting this as requested in https://hub.mender.io/t/variscite-var-som-mx8m-nano-nxp-i-mx-8m-nano/1928/3.
I am not confident of the changes as I don't know the code, and I am experiencing problems when running the image it generates.

@gphillips-a2e I see that you are explicitly adding CONFIG_OF_LIBFDT_OVERLAY=y and  #define CONFIG_ENV_OVERWRITE.  Is that intentional?
Which version of the NXP BSP are you using? Has Variscite published a matching BSP for their bits?

@drewmoseley I think the adding of CONFIG_OF_LIBFDT_OVERLAY=y and #define CONFIG_ENV_OVERWRITE are likely copy and paste errors.

I am using version 5.4.24-2.1.0 of meta-imx, with the zeus-imx-5.4.24-var01 branch of meta-variscite-imx.  This are the versions that were configured in Variscite's manifest, so should match.

@drewmoseley
I didn't add CONFIG_OF_LIBFDT_OVERLAY=y and #define CONFIG_ENV_OVERWRITE, they just came in as extra context lines in the patch.  It gets quite confusing trying to look at the diff of a diff.

Yeah, no doubt. I have this building locally without needing your patch.  Can you share the list of your layers and the commit hashes of each as well as the original failure message?

Here is my conf/bblayers.conf file:
LCONF_VERSION = "7"

BBPATH = "${TOPDIR}"
BSPDIR := "${@os.path.abspath(os.path.dirname(d.getVar('FILE', True)) + '/../..')}"

Hunk #2 succeeded at 110 (offset 1 line).
Hunk #3 FAILED at 134.
Hunk #4 succeeded at 204 (offset 1 line).
Hunk #5 FAILED at 225.
Hunk #6 succeeded at 292 (offset 1 line).
2 out of 6 hunks FAILED -- rejects in file include/configs/imx8mn_var_som.h
Patch 0001-Switch-to-CONFIG_DISTRO_DEFAULTS-for-bootcmd.patch does not apply (enforce with -f)
ERROR: Logfile of failure stored in: /home/yocto/nano/var-fsl-yocto/build_xwayland/tmp/work/imx8mn_var_som-poky-linux/u-boot-variscite/1.0-r0/temp/log.do_patch.3556
ERROR: Task (/home/yocto/nano/var-fsl-yocto/sources/meta-variscite-imx/recipes-bsp/u-boot/u-boot-variscite.bb:do_patch) failed with exit code '1'

Here is the log file mentioned:
log.do_patch.3556.txt

OK.  I do have another patch locally that I forgot about.  I have not submitted it because I have not had a chance to re-test all the builds with the new 5.4.24 BSP.  Can you test this patch locally?

I replaced meta-mender-community with your fork and checked out 84cbcd6.  It is still creating the SD card image, but it looks like the patch worked and it compiled.

OK.  Good to hear.  But I'm hesitant to move all of meta-mender-community forward as the dart-6ul still only has a 5.4.3 BSP from Variscite. For now I suggest you just keep that patch in your local checkout.

@drewmoseley
I tried the build from yesterday, it stuck in u-boot due to a problem with the environment size.  The output is below.  Do you know what the problem is?
U-Boot SPL 2020.04-imx_v2020.04_5.4.24_2.1.0_var01+g455f3570fb (Nov 10 2020 - 18:10:24 +0000)
Normal Boot
Trying to boot from BOOTROM
image offset 0x8000, pagesize 0x200, ivt offset 0x0

U-Boot 2020.04-imx_v2020.04_5.4.24_2.1.0_var01+g455f3570fb (Nov 10 2020 - 18:10:24 +0000)

CPU:   i.MX8MNano Quad rev1.0 1500 MHz (running at 1200 MHz)
CPU:   Commercial temperature grade (0C to 95C) at 23C
Reset cause: POR
Model: Variscite VAR-SOM-MX8MN
DRAM:  1 GiB
MMC:   FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... Run CMD11 1.8V switch
*** Error - default environment is too large

*** Error - default environment is too large

In:    serial
Out:   serial
Err:   serial

 BuildInfo:
  - ATF 0645021
  - U-Boot 2020.04-imx_v2020.04_5.4.24_2.1.0_var01+g455f3570fb

Part number: VSM-MX8MN-101
Assembly: AS2006152614
Production date: 2020 Jul 02
Serial Number: f8:dc:7a:46:04:5e
env_buf [32 bytes] too small for value of "bootcmd"
Net:
Warning: ethernet@30be0000 (eth0) using random MAC address - 26:8f:1b:6f:f8:5d
eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
env_buf [32 bytes] too small for value of "bootcmd"
Hit any key to stop autoboot:  0
syntax error
Unknown command '@' - try 'help'
u-boot=>

It looks like the only difference between the patch in this pull request and the one in 84cbcd6 is that the one in the pull request keeps the addition of #define CONFIG_ENV_SIZE    SZ_8K.  The u-boot error message seems to imply this is required.

Yes, due to the changes made in the patch, we need more env space.

I tried 84cbcd6 with the environment size increased to 8K.  This boots but has the same issues as my original attempt (slow boot, memcg_kmem_cache_create_func messages, does not start GUI, cannot log in).
Do you have any other suggestions?

No clue.  Does "systemd-analyze blame" show anything of note?

I am not able to get to the point where I can run any commands.

Which DISTRO are you building with? I'll try to replicate here.

I am building Zeus 5.4.24 on Ubuntu 18.04.  The manifest is imx-5.4.24-2.1.0-var01.xml.

I tried this on a VAR-SOM-MX8M-MINI board with the imx-5.4.3-1.0.1-var01.xml manifest.  The result is the similar.  It needs MENDER_STORAGE_TOTAL_SIZE_MB increasing to create the image, it starts up to the command line instead of the GUI, and logging in via the console does not work.  The only difference is that I cannot see the memcg_kmem_cache_create_func message.

@gphillips-a2e please take a look at https://github.com/mendersoftware/meta-mender-community/pull/191.
That works for me on the core-image* builds.  If you can test the fsl-image* builds that would be helpful.  I'll close this in favor of that one.

@drewmoseley
The fsl-image-qt5 image does not work for me.  I get the same problems as I described previously.  I have not tried any other fsl-image builds.   Although core-image-full-command line worked for me core-image-weston did not.  The weston image had similar issues to fsl-image-qt5.


Dead link: https://rsinger86.github.io/usage/view_set_usage

On the page https://rsinger86.github.io/drf-access-policy/ the 'Read On' link on the bottom of that page href is:
https://rsinger86.github.io/usage/view_set_usage
whereas it ought to be:
https://rsinger86.github.io/drf-access-policy/usage/view_set_usage/

thanks for catching this!


Closes: #1

Updated validations.py Puthon script.
Fixed behavior of validate_user function in validations.py:
- added condition to allow capital letters;
- the first character was checked using a regular expression.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[+] Tests pass
[+] Appropriate changes to README are included in PR

Updated validations.py python script


Confirm filesize on transfers

This is a fix for issue #19.
We were already doing an xrootd stat beforehand to see if the file was already there, we're now doing it
again afterwards to double-check our transfer is complete by verifying the size.  So if the copy "succeeds" but
the file sizes don't match, we  flag it as a failed transfer.

Sigh Wrong repository


Avoid use of getchildren

Summary
This is deprecated in py2.7 and not available in py3

@gwarf How do we fix all this never completed tests :( ?

So @orviz reached me about the Jenkins part, we will fix it, but in the meantime I've disable dit.
Still we need to have at least the travis part working.
I will also check codacy and potentially disable it too.

travis was happy about this one. Should be restored

I'm a bit confused with the travis-ci.org vs travis-ci.com and all, and not understanding why the status was again not reaching GitHub.
I've removed the travis checks, and I'm no more allowed to add it as it seems it's lacking feedback from travis since too long.
May need to completely redo travis integration for this repo...

OK, I've randomly unticked and reticked some checkboxes here and there, and now we got the status back working...
We may want to test GitHub actions at some point to rely on one less provider for this.


(JDWP Error Code:35) Invalid slot. for

This is happening with any APK I use to decompile, when try to debug I can't get values for the virtual registers, It always show this error message (JDWP Error Code:35) Invalid slot. for vx as in the printscreen below. I'm using the latest release (1.4.6) with Java version 17.0.6. The application is running under a Qemu emulator with android-x86 image

Error persist in version 1.4.7

Could you please check the Jadx log if it shows more details e.g. a stack trace?

this is all that is showing on the terminal since it opened:
$ ./jadx-gui
INFO  - output directory: UnCrackable-Level1-run-with-root-DEBUG
INFO  - loading ...
INFO  - Loaded classes: 7, methods: 15, instructions: 373
INFO  - Can't find 'R' class in app package: owasp.mstg.uncrackable1
INFO  - App 'R' class not found, put all resources ids into : 'owasp.mstg.uncrackable1.R'
^YINFO  - Resetting disk code cache, base dir: /home/fabio/OneDrive/Estudos/TCC/UnCrackable-Level1/UnCrackable-Level1-run-with-root-DEBUG.apk.cache
WARN  - Aborting readServiceProtocol: java.net.SocketException: Socket closed
WARN  - Aborting readServiceProtocol: java.net.SocketException: Socket closed
ERROR - Debug error: (JDWP Error Code:35) Invalid slot. for p0
ERROR - Debug error: (JDWP Error Code:35) Invalid slot. for v4
ERROR - Debug error: (JDWP Error Code:35) Invalid slot. for v4
ERROR - Debug error: (JDWP Error Code:35) Invalid slot. for v4
ERROR - Debug error: (JDWP Error Code:35) Invalid slot. for v1
ERROR - Debug error: (JDWP Error Code:35) Invalid slot. for v2
ERROR - Debug error: (JDWP Error Code:35) Invalid slot. for v1
ERROR - Debug error: (JDWP Error Code:35) Invalid slot. for v1
ERROR - Debug error: (JDWP Error Code:35) Invalid slot. for v0
ERROR - Debug error: (JDWP Error Code:35) Invalid slot. for v0
ERROR - Debug error: (JDWP Error Code:35) Invalid slot. for v0
ERROR - Debug error: (JDWP Error Code:35) Invalid slot. for v0
ERROR - Debug error: (JDWP Error Code:35) Invalid slot. for v0

I found this blog post which provides a lot of background information on this specific error (the used software is JEB, but that doesn't matter of the background info): https://www.pnfsoftware.com/blog/debugging-android-apps-on-android-pie-and-above/
According to this post the error occurs because the slots have a different name since Android 9. If I understand the post correctly before Android 9 the registers were accessed using the pX notation, since Android 9 the vX notation is used.
As Android x86 is an 8.x or lower Android version this would match that there are no vX registers, but in your log there is also an entry for Invalid slot. for p0 which confuses me as it sues the pX notation which should be supported.
As workaround my recommendation would be to use an emulator with Android 9+. To my understanding it should not be affected by this problem.

yes but I'm really using Android v9.0-rc2

I've just tested with a real phone and it did work, however the are some GUI problems:

It doesn't let me resize the window of the values, so I can't see the actual values there since they are below the Debugger log window and the call stack window:

The "Copy Value" option on the right click context menu doesn't work when I click on it, however it works if I just type CTRL + C

Debugging Android apps on Android Pie and above
Update (March 2020): It looks li
ke the problem highlighted below regarding the impossibility to read locals that do not have associated DebugLocalInfo on Android P and Q was fixed in Android R (verified with the Developer Preview 1 released on Feb 19). The patch solving this issue is likely this one.

Same issue with Android-x86 9 (Pie):

switch to android-x86_64-8.1-r6.iso (Android 8.1 Oreo) :+1:
use  jadx 1.4.7 and Android Debug Bridge version 1.0.41

and

no more :no_entry: JDWP Error Code:35 :bug:
UnCrackable-Level1.apk dynamically solved :medal_sports:

by changing v0 values at first checks :pencil2:
using breakpoint to get the secret :mag_right:

Did this bug resloved when debug a apk in android 9 emulator with jadx 1.4.7？I meet this  problem too