escaping bbox

When the face moves or under certain conditions, the bounding box randomly shrinks and grows, eventually disappearing off the screen. The face is not detected again until it reappears on the screen. This issue is more likely to occur when the face moves quickly or when there are two or more people in the webcam frame. Additionally, the smaller the bounding box and the further the detection distance, the more frequently this issue occurs. Can you help me understand why this is happening?

The reason the above problem occurred was due to my ineffective use of multi threads. The idea to solve this problem is to combine recognition and detection into 2 separate applications, and use redis to communicate. @ksh1983

2 separate applications, and use redis to communicate <<<I don't understand, can you show me an example?

you can run 2 containers for detection and recognition. And then you use redis to push frame detected from detection to recognition container

I don't think it's a multi-thread problem, so please check it. It's a video
I shot myself, and if I use cuda, it comes out more than 60fps, but in the
video, the fps comes out low due to the capture setting. If you move your
face quickly like that or if more than two people appear on the screen at
the same time, that happens.
2024년 6월 26일 (수) 오전 1:22, Vector Nguyễn @.***>님이 작성:

you can run 2 containers for detection and recognition. And then you use
redis to push frame detected from detection to recognition container
—
Reply to this email directly, view it on GitHub
https://github.com/vectornguyen76/face-recognition/issues/26#issuecomment-2189395961,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKCPASMM66AN4ZSKQMVAWETZJGKLDAVCNFSM6AAAAABJSAODZOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBZGM4TKOJWGE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Self Hosting: Fetching shared link does not work, Cannot GET /eval/

Describe the bug
The shared link produced now has the structure:
 Evaluation complete: https://promptfoo.mycorp.net/eval/eval-2024-09-12T14:50:30

however trying always returns 400 Cannot GET /eval/eval-2024-09-12T14:50:30
I am able to see the report in the UI at https://promptfoo.mycorp.net/eval/?evalId=eval-2024-09-12T14:50:30
To Reproduce
Self hosting

Build 0.86.1 docker image
run it with set envvar

PROMPTFOO_REMOTE_API_BASE_URL=https:///promptfoo.mycorp.net

System information (please complete the following information):

Promptfoo version: 0.86.1

I can clearly see there is a huge pace in versions, but I am struggling to find a combination that works for sharing the reports. Do you have any pointers how this is done?

Hi @AlexRRR, can you try the latest Dockerfile on main?  That should solve the issue, which is a UI bug in how the share ID is presented.

Thanks for the hint @typpo . However I am hitting the same problem, I've built dd0ad14 and still i get a 400 with Cannot GET /eval/eval-2024-09-13T08:00:08 but I am able to see it under /eval/?evalId=eval-2024-09-13T08%3A00%3A08
To be clear I've only set PROMPTFOO_REMOTE_API_BASE_URL:  https://promptfoo.mycorp.net as envvar, perhaps I am missing something else.
Also I found a small bug while building this commit's docker file:
26.60 **************************************************
26.60 Building next.js
26.60 **************************************************
26.78 Attention: Next.js now collects completely anonymous telemetry regarding usage.
26.78 This information is used to shape Next.js' roadmap and prioritize features.
26.78 You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
26.78 https://nextjs.org/telemetry
26.78
26.92 - info Creating an optimized production build...
63.71 thread '<unnamed>' panicked at 'internal error: entered unreachable code', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rayon-core-1.11.0/src/job.rs:230:32
63.71 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
63.73 fatal runtime error: failed to initiate panic, error 5
63.78 Aborted
64.07 cp: no such file or directory: src/web/nextui/out/*

I've just done touch src/web/nextui/out/foo  and then dockerfile worked again.

Hi @AlexRRR, we’ve just shipped 0.88.0, which includes a fix for the shared link issue you reported and the missing directory. It should now be resolved. Thanks again for bringing this to our attention, and let us know if you run into any further issues!

Thank you so much!


Add middleware to restrict concurrency

This adds middleware that will turn a request into (logically) a single-threaded request. This helps mimic some of the behavior that was seen on ASP.NET Framework where there was a concept of a request thread. Since ASP.NET Core is not tied to a specific thread, that model does not translate directly. However, by enabling this, it will limit concurrent access to items within the flow of a request.

Closing as #78 is incorporating this


fix typescript definition file.

fix error in typescript file. it needs to import 'react' to use it.

can you please cut a new release so we can use the new version with the correct typescript definition


Add a feature to customize history table name of child model

When we set history attribute with inherit=true in base model. Historical model is created for child model as well. However, there is no way to update the table_name of child models history table.
https://github.com/jazzband/django-simple-history/issues/1174

Currently in get_history_model method the history table name is returned using model._meta.object_name property.
Since, history attribute is defined in the base class, so self.table_name will reflect the value defined in base class.

Can we customize using by defining new attribute in BaseModel class e-g history_table_name ?
With this approach, make sure that this attribute is not part of the database table and is not treated as a property of the model.

Consider this approach as well:
Customize meta db table option of history model, when it is created


context deadline exceeded

Bug report
During a long running session from mongodb to elasticsearchwith tail option enabled, transporter crashes with this error: context deadline exceeded
Relevant pipeline.js:
var source = mongodb({
"uri": "mongodb://localhost:27017/view"
"timeout": "30s",
"tail": true,
// "ssl": false,
// "cacerts": ["/path/to/cert.pem"],
// "wc": 1,
// "fsync": false,
// "bulk": false,
//"collection_filters": "{"events":{}}",
// "read_preference": "Primary"
})
var sink = elasticsearch({
"uri": "http://localhost:9200/events"
"timeout": "30s", // defaults to 30s
// "aws_access_key": "ABCDEF", // used for signing requests to AWS Elasticsearch service
// "aws_access_secret": "ABCDEF" // used for signing requests to AWS Elasticsearch service
})
t.Config({"xlog_dir":"/var/log/transporter"}).Source("source", source, "/^events$/").Save("sink", sink, "/.*/")
System info:

Transporter version
VERSION
0.5.0
OS
Ubuntu 16.04.3 LTS
DB version(s)
MongoDB: v3.4.3
ElasticSearch: 5.5.2

Reproducible Steps:
Start pipeline.js on a collection with over 68M records and wait
What did you expect to happened?
Continuosly moving from MongoDB to ElasticSearch
What actually happened?
Crash

I got the same problem

this is likely due to wires taking longer than the default timeout of 5s. You can increase the write timeout in the Config function like so:
t.Config({'write_timeout': '60s', 'xlog_dir': '/var/log/transporter'})...

I got the same problem.
and I modify timeout = 3600s on pipeline.js.
But it couldn't be solved.
you guys have any solution?

I solved this by increasing the write timeout to 3600s, like so:
t.Config({'write_timeout': '3600s'})


Muzai setting not appearing after clicking icon and more

Clicking settings icon does nothing , am I missing something here ,

is user prompted for rating automatically ?
is  user prompted for donations automatically ?
is it possible to add options to automatically change wallpapers after some provided time period
?

Make sure to setup correctly https://github.com/danimahardhika/candybar-library/wiki/Setup#open-androidmanifestxml
2 3 No
4. That's what muzei do

is following senario possible :- user is allowed to request certain amount of icons for free and after that limit is reached then only show paid request options ?

Read the wiki site https://github.com/danimahardhika/candybar-library/wiki/Customization:-Basic#icon-request


Change formulae update method

brew cask update is being deprecated on 7/1/2017 so this PR preemptively changes the method we use to update formulae to the Hbc::SystemCommand.run method.
It also hides all the unnecessary output that brew update outputs to $stdout and only notifies if formulae have been updated.

I'd like to use the ohai method on line 38 but that depends on merging https://github.com/buo/homebrew-cask-upgrade/pull/32 first.

Closing in favor of https://github.com/buo/homebrew-cask-upgrade/pull/29 and the discussion therein.


[GIT PULL] Minor Build Failure Fixes

Noticed 2 minor independent build failures

Run make --trace without the configure step.
This causes make to build the target config-host.mak which
in turn invokes configure which generates an incorrect
io_uring_version.h file.
Fixed by setting MAKEFLAGS=
before generating io_uring_version.h file in the configure script

/configure && make --shuffle=2836571325
fails.
The build fails on parallel builds for me and the above command reproduces it.
Note that --shuffleoptions is available on make version >= 4.4
Target ffi_libname in src/Makefile should have an additional dependency
upon $(liburing_sobjs)

make -n also breaks but don't want to clutter this patch. If you give a go ahead, will fix it

git request-pull output:
The following changes since commit 2d3368b73b478a737b2247ef5630be56c3b176b5:

  test/io_uring_register: fix errno confusion and new error (2023-06-28 19:43:02 -0600)

are available in the Git repository at:

  https://github.com/stonebrakert6/liburing master

for you to fetch changes up to b5f3dcfe210b83700566cf68484913f8c62c9be7:

  Fixes build failure on ./configure && make --shuffle=2836571325 ./configure && make --shuffle=2836571325 fails. The build fails on parallel builds for me and above command reproduces it. Note that --shuffle options is available on make version >= 4.4 Target ffi_libname in src/Makefile should have a additional dependency upon $(liburing_sobjs) (2023-06-30 11:34:07 +0530)

----------------------------------------------------------------
stonebrakert6 (2):
      Fixes make --trace
      Fixes build failure on ./configure && make --shuffle=2836571325 ./configure && make --shuffle=2836571325 fails. The build fails on parallel builds for me and above command reproduces it. Note that --shuffle options is available on make version >= 4.4 Target ffi_libname in src/Makefile should have a additional dependency upon $(liburing_sobjs)

 configure    | 2 ++
 src/Makefile | 2 +-
 2 files changed, 3 insertions(+), 1 deletion(-)

Click to show/hide pull request guidelines
Pull Request Guidelines

To make everyone easily filter pull request from the email
notification, use [GIT PULL] as a prefix in your PR title.

[GIT PULL] Your Pull Request Title

Follow the commit message format rules below.
Follow the Linux kernel coding style (see: https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst).

Commit message format rules:

The first line is title (don't be more than 72 chars if possible).
Then an empty line.
Then a description (may be omitted for truly trivial changes).
Then an empty line again (if it has a description).
Then a Signed-off-by tag with your real name and email. For example:

Signed-off-by: Foo Bar<EMAIL_ADDRESS>
The description should be word-wrapped at 72 chars. Some things should
not be word-wrapped. They may be some kind of quoted text - long
compiler error messages, oops reports, Link, etc. (things that have a
certain specific format).
Note that all of this goes in the commit message, not in the pull
request text. The pull request text should introduce what this pull
request does, and each commit message should explain the rationale for
why that particular change was made. The git tree is canonical source
of truth, not github.
Each patch should do one thing, and one thing only. If you find yourself
writing an explanation for why a patch is fixing multiple issues, that's
a good indication that the change should be split into separate patches.
If the commit is a fix for an issue, add a Fixes tag with the issue
URL.
Don't use GitHub anonymous email like this as the commit author:
<EMAIL_ADDRESS>
Use a real email address!
Commit message example:
src/queue: don't flush SQ ring for new wait interface

If we have IORING_FEAT_EXT_ARG, then timeouts are done through the
syscall instead of by posting an internal timeout. This was done
to be both more efficient, but also to enable multi-threaded use
the wait side. If we touch the SQ state by flushing it, that isn't
safe without synchronization.

Fixes: https://github.com/axboe/liburing/issues/402
Signed-off-by: Jens Axboe<EMAIL_ADDRESS>

By submitting this pull request, I acknowledge that:

I have followed the above pull request guidelines.
I have the rights to submit this work under the same license.
I agree to a Developer Certificate of Origin (see https://developercertificate.org for more information).

 Please fix.

Done

Done

Sorry, I missed another issue in the previous review.
The commit author is also wrong, don't use your GitHub username, but your real name
as what it's written in the Signed-off-by.
The current author is:
stonebrakert6<EMAIL_ADDRESS>
You can check it using git log. And actually, the git request-pull command also
shows it.
You can configure your future commit to use the correct author this way:
git config --global user.name "Your Real Name Here"

Thank you.

Sorry for the hassle I failed to interpret all the PR guidelines correctly. Can you check now?


dynamic control over display manual panning/rotation

resolves #90
also exposes the polyfill in window, allowing advanced runtime configuration

Sorry I'm just getting to this, but I don't understand what this is for. We already have a touchpanner for the purpose of manual rotation. Please explain clearly and re-open a new PR.


ModuleNotFoundError: No module named 'spotipy'

I'm getting the same error.

Try this one pip3 install spotipy
Spotipy - https://github.com/plamere/spotipy

I'm having the same error
# python3.6 main.py -sp "https://open.spotify.com/playlist/50ayC7avUY9cRgXvQ7ZmcX"

Traceback (most recent call last):
  File "main.py", line 2, in <module>
    from spotify import Spotify
  File "/var/www/html/smd/spotify.py", line 3, in <module>
    import spotipy
ModuleNotFoundError: No module named 'spotipy'

# pip3 install -r requirements.txt

Requirement already satisfied: notify2==0.3.1 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 1))
Requirement already satisfied: spotipy==2.4.4 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 2))
Requirement already satisfied: lyricsgenius==1.4.0 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 3))
Requirement already satisfied: lxml==4.3.3 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 4))
Requirement already satisfied: mutagen==1.41.0 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 5))
Requirement already satisfied: requests==2.21.0 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 6))
Requirement already satisfied: moviepy==<IP_ADDRESS> in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 7))
Requirement already satisfied: imageio==2.3.0 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 8))
Requirement already satisfied: humanize==0.5.1 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 9))
Requirement already satisfied: pygame==1.9.6 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 10))
Requirement already satisfied: youtube_dl==2019.7.30 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 11))
Requirement already satisfied: Flask==0.12.2 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 12))
Requirement already satisfied: pytube==9.5.1 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 13))
Requirement already satisfied: PyQt5==5.13.0 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 14))
Requirement already satisfied: beautifulsoup4==4.8.0 in /usr/local/lib/python3.5/dist-packages (from -r requirements.txt (line 15))
Requirement already satisfied: idna<2.9,>=2.5 in /usr/local/lib/python3.5/dist-packages (from requests==2.21.0->-r requirements.txt (line 6))
Requirement already satisfied: chardet<3.1.0,>=3.0.2 in /usr/local/lib/python3.5/dist-packages (from requests==2.21.0->-r requirements.txt (line 6))
Requirement already satisfied: urllib3<1.25,>=1.21.1 in /usr/local/lib/python3.5/dist-packages (from requests==2.21.0->-r requirements.txt (line 6))
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.5/dist-packages (from requests==2.21.0->-r requirements.txt (line 6))
Requirement already satisfied: decorator<5.0,>=4.0.2 in /usr/local/lib/python3.5/dist-packages (from moviepy==<IP_ADDRESS>->-r requirements.txt (line 7))
Requirement already satisfied: numpy in /usr/local/lib/python3.5/dist-packages (from moviepy==<IP_ADDRESS>->-r requirements.txt (line 7))
Requirement already satisfied: tqdm<5.0,>=4.11.2 in /usr/local/lib/python3.5/dist-packages (from moviepy==<IP_ADDRESS>->-r requirements.txt (line 7))
Requirement already satisfied: pillow in /usr/local/lib/python3.5/dist-packages (from imageio==2.3.0->-r requirements.txt (line 8))
Requirement already satisfied: click>=2.0 in /usr/local/lib/python3.5/dist-packages (from Flask==0.12.2->-r requirements.txt (line 12))
Requirement already satisfied: Werkzeug>=0.7 in /usr/local/lib/python3.5/dist-packages (from Flask==0.12.2->-r requirements.txt (line 12))
Requirement already satisfied: itsdangerous>=0.21 in /usr/local/lib/python3.5/dist-packages (from Flask==0.12.2->-r requirements.txt (line 12))
Requirement already satisfied: Jinja2>=2.4 in /usr/lib/python3/dist-packages (from Flask==0.12.2->-r requirements.txt (line 12))
Requirement already satisfied: PyQt5_sip<13,>=4.19.14 in /usr/local/lib/python3.5/dist-packages (from PyQt5==5.13.0->-r requirements.txt (line 14))
Requirement already satisfied: soupsieve>=1.2 in /usr/local/lib/python3.5/dist-packages (from beautifulsoup4==4.8.0->-r requirements.txt (line 15))
Requirement already satisfied: MarkupSafe in /usr/lib/python3/dist-packages (from Jinja2>=2.4->Flask==0.12.2->-r requirements.txt (line 12))

Problem solved by installing everything again.

The problem is caused when you don't install the requirements properly. just reinstall that and it will run


Implement eviction of iroh-dns-server based on last_seen, not timestamp

Currently eviction is implemented in terms of the timestamp of the packet, in https://github.com/n0-computer/iroh/pull/2997
The timestamp is the wallclock time when the packet is signed.
This works fine for us since we create new packets every time we publish discovery information. But for pkarr in general, it is perfectly valid to have a packet that was signed some time ago and republish it - that way the publisher does not need the private key. We should change the iroh-dns-server eviction to use the receive time instead of the timestamp.
The downside of this is that somebody, anybody, could prevent a packet from being evicted by just republishing it. However, they can not prevent the packet from being replaced by a newer one. So really nothing to worry about I think.
Doing eviction based on recv time would require storing the recv time separately, so it would be a schema change. There are some things coming in pkarr v3 that would make this easier, so maybe we wait until then...
Cc @Nuhvi

You can review (try) this branch, otherwise I can publish it as v3 tonight https://github.com/pubky/pkarr/pull/78
It would work like this:
let keypair = Keypair::random();

let signed_packet = SignedPacket::builder()
    .sign(&keypair)
    .unwrap();

// Serializing/deserializing `<last_seen u64 big endian><singed_packet>`
let signed_packet =  SignedPacket::deserialize(&signed_packet.serialize()).unwrap();

// And you can get the `last_seen` and it itself is serializable as a u64 big endian too.
signed_packet.last_seen().to_bytes();


add handling for undefined input body

There's a small bug in the adapter-api and it fails when the request body is undefined (it tries to parse undefined)
I've added some tests and checks to handle request bodies that are undefined

@all-contributors please add @joeleg  for bug

@joeleg Thanks a lot for your contribution! Your change is now published under version 1.13.1.


Add some additional resource for workshop seq test 03

Hello,
Thanks for providing this excellent workshop!
I thought the learning curve / difficulty difference between 02 and 03 for the seq workshop was relatively steep. What do you think about adding these resources?

Actually, it might also be a good idea to add the TokenBuffer to the resources as well. I've handwritten the content parser now, but especially for 05, the Cursor types comes in handy.


Sorting in LaserIO gui causes entire inventory to get deleted

https://streamable.com/tcffw9
The only two mods I have installed in the video is LaserIO 1.6.8 and this mod version 1.1.0 on forge 47.2.20, minecraft version 1.20.1

[[sorting.containerOverrides]]
	containerClass = "com.direwolf20.laserio.client.screens.*"
	sortRange = ""```

i was able to disable the sorting functionality in the laserio guis by adding this to the config

Can confirm, with this mod of version 1.1.0 and LaserIO of version 1.6.8.
To reproduce this issue, sort the inventory (press the sorting button in the GUI or middle mouse button) while in the item card GUI and your inventory will get deleted (see the attached videos). Each time you press the sort button, 15 item stacks at most get deleted, like you see in the second video - from a full player inventory 15 stacks get deleted then another 15, then the last 6.
As for why this happens, I can only think of the 12 empty slots that the LaserIO filters have and some slots that the cards have in general - maybe InvTweaks tries to put the items into the ghost slots and deletes them, but again, I'm not sure. Also I've tested this with the Inventory Sorter mod but the items in that case aren't sorted and therefore aren't deleted.
https://github.com/user-attachments/assets/9b1f06fc-8c4e-4e64-97c4-b950893bae73
https://github.com/user-attachments/assets/0ad4356a-3841-460b-b01a-f971e5ff95a3

This issue is also in the LaserIO GitHub - see issue 265

This is a problem with the sorting of this mod, not with other mods. Tested it in All the mods 9: To the sky, and the sorting of this mod (both hotkey and button in inventories) deletes mine and the non-vanilla blocks inventories.


Splitting contract impls across modules leads to errors

What version are you using?
v21.5.1
What did you do?
Cargo.toml:
[package]
name = "test_modular"
version.workspace = true
authors = ["Stellar Development Foundation<EMAIL_ADDRESS>license = "Apache-2.0"
edition = "2021"
publish = false
rust-version.workspace = true

[lib]
crate-type = ["cdylib"]
doctest = false

[dependencies]
soroban-sdk = {path = "../../soroban-sdk"}

[dev-dependencies]
soroban-sdk = {path = "../../soroban-sdk", features = ["testutils"]}

src/lib.rs:
#![no_std]
use soroban_sdk::{contract, contractimpl};

mod feat1;
mod feat2;

#[contract]
pub struct Contract;

#[contractimpl]
impl Contract {
    pub fn base() -> u32 {
        0
    }
}

src/feat1.rs:
use soroban_sdk::contractimpl;

use crate::Contract;
use crate::ContractClient;

#[contractimpl]
impl Contract {
    pub fn one() -> u32 {
        1
    }
}

src/feat2.rs:
use soroban_sdk::contractimpl;

use crate::Contract;

#[contractimpl]
impl Contract {
    pub fn two() -> u32 {
        2
    }
}

What did you expect to see?
Compiled successfully, and test successfully.
What did you see instead?
$ soroban contract build
cargo rustc --manifest-path=Cargo.toml --crate-type=cdylib --target=wasm32-unknown-unknown --release
   Compiling test_modular v21.5.1 (/Users/leighmcculloch/Code/rs-soroban-sdk/tests/modular)
error[E0412]: cannot find type `ContractClient` in this scope
 --> tests/modular/src/feat1.rs:6:1
  |
6 | #[contractimpl]
  | ^^^^^^^^^^^^^^^ not found in this scope
  |
  = note: this error originates in the attribute macro `soroban_sdk::contractclient` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this struct
  |
1 + use crate::ContractClient;
  |

error[E0412]: cannot find type `ContractClient` in this scope
 --> tests/modular/src/feat2.rs:6:1
  |
6 | #[contractimpl]
  | ^^^^^^^^^^^^^^^ not found in this scope
  |
  = note: this error originates in the attribute macro `soroban_sdk::contractclient` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this struct
  |
1 + use crate::ContractClient;
  |

For more information about this error, try `rustc --explain E0412`.
error: could not compile `test_modular` (lib) due to 2 previous errors

After adding in these lines to feat1.rs and feat2.rs:
use crate::ContractClient;

Build worked fine, but cargo test failed:
❯ cargo test
   Compiling test_modular v21.5.1 (/Users/leighmcculloch/Code/rs-soroban-sdk/tests/modular)
error[E0433]: failed to resolve: use of undeclared crate or module `__Contract_fn_set_registry`
 --> tests/modular/src/feat1.rs:6:1
  |
6 | #[contractimpl]
  | ^^^^^^^^^^^^^^^ use of undeclared crate or module `__Contract_fn_set_registry`
  |
  = note: this error originates in the attribute macro `contractimpl` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this module
  |
1 + use crate::__Contract_fn_set_registry;
  |

error[E0433]: failed to resolve: use of undeclared crate or module `__Contract_fn_set_registry`
 --> tests/modular/src/feat2.rs:6:1
  |
6 | #[contractimpl]
  | ^^^^^^^^^^^^^^^ use of undeclared crate or module `__Contract_fn_set_registry`
  |
  = note: this error originates in the attribute macro `contractimpl` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this module
  |
1 + use crate::__Contract_fn_set_registry;
  |

For more information about this error, try `rustc --explain E0433`.
error: could not compile `test_modular` (lib test) due to 2 previous errors

I believe I have a fix that requires no breaking changes:

https://github.com/stellar/rs-soroban-sdk/pull/1322

I still have an issue to resolve on how to resolve the contract client. So change is still a WIP.


display token supply with decimal consideration in explorer

If a token uses decimals, the minted supply is an integer of [desired base supply] * [10^(number of decimals)]
this causes user confusion when viewing the token contract in the run explorer, as they think the total supply is much greater than the intended number.   It would be nice if the run jig explorer took token decimals into consideration when calculating the token supply for display.

The amount and supply properties are decimalized in the Explorer.
We'll do custom views for different jig types down the road, but this should work for now.


change some naming conventions

Is this done?

I assume this is safe to close seeing as we have made a complete conversion to snake_case, closing


Modify functions and tests to support HTTPS

This PR extends the function to support HTTPS.
Currently, only git@github.com:user/repo.git remote URLs are supported.  If you attempt to use add-remote or add-upstream with a remote such as https://github.com/user/repo.git, the result is an invalid URL.
I also added tests and one example to the README for HTTPS.

I'm not sure why commitlint is complaining as commit 4fa178a is not empty.

thanks!


Write a test to ensure no versioned Elixir Documentation links are in the project.

Instead of links such as https://hexdocs.pm/elixir/1.12/Enumerable.html we should instead use https://hexdocs.pm/elixir/Enumerable.html to ensure our documentation links remain up to date.
It would be great to have a test to ensure we don't include any of these.

Resolved by #281


Feature: Add visible UI indicator when Item is scanned

Add highly visible indicator when item is scanned.

Added in https://github.com/maxxonair/inventory/commit/a1ccbadf24eb1768d9e11f907b37bc2d7ff7a9c5


Reference Camel SNAPSHOT docs as 4.3.0 is not published on the website

I think for this to work we'd also need to implement https://github.com/apache/camel-quarkus/issues/5617. Given HDFS already seems to be marked as deprected, there's probably no harm in doing the change now.


nerdctl inspect --format

Doesn't seem to work
$ nerdctl image inspect --format '{{.RepoTags}}' alpine
{"Id":"sha256:021b3423115ff662225e83d7e2606475217de7b55fde83ce3447a54019a77aa2","RepoTags":["alpine:latest"],"RepoDigests":["alpine@sha256:eb3e4e175ba6d212ba1d6e04fc0782916c08e1c9d7b45892e9796141b1d379ae"],"Comment":"","Created":"2021-08-06 17:19:45.183996158 +0000 UTC","Author":"","Config":{"User":"","Env":["PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"],"Cmd":["/bin/sh"],"Volumes":null,"WorkingDir":"","Entrypoint":null,"Labels":null},"Architecture":"amd64","Os":"linux","RootFS":{"Type":"layers","Layers":["sha256:bc276c40b172b1c5467277d36db5308a203a48262d5f278766cf083947d05466"]},"Metadata":{"LastTagTime":"0001-01-01T00:00:00Z"}}


Update new-vhd.md

Corrected Example 5

@dariomws306 @get-itips @tseward
Peer review needed for this PR. Thanks.

Looks good.

ok!

I think there is no update needed here:

@tseward @get-itips Do you agree with Dario's suggestion that no changes are necessary?

@tseward @get-itips Do you agree with Dario's suggestion that no changes are necessary?

On second thoughts, yes.

@tseward @get-itips Do you agree with Dario's suggestion that no changes are necessary?

Agree

Thank you all for input. Closing.


CC Chunk (and maybe Base) have dependency on CC Entity

CC Chunk (and maybe Base) have dependency on CC Entity

Hi, recently you patched a dependency issue with CC Chunk. I've found another one, where it appears to also be dependant on the Entity module. Worlds only load if entity is present.

How do I keep doing this... Can I get a stacktrace ?

Ok, here: https://controlc.com/1412204d

Ah no, this is an unrelated bug. You just have an ancient version of cardinal-components-entity, same as #48. Easy fix is to download the full library and put it in your mods folder.

My mod only works if I add entity in Gradle, and the only cause could be my use of Trinkets API

Ah, gradle being shit again. Try something like:
modImplementation("whatever:trinket:xxx") {
    transitive = false
}


Send form errors bug

If you have errors in the send to mainchain form, errors won't correctly show in the send to sidechain form.

Fixed in #388


How to install Teams with Office 365 for Windows 10 (Endpoint Manager)

Installing Teams as part of the Office 365 for Windows 10 deployment using XML configuration in Endpoint Manager. I have a group of devices set to required for install.
As per Microsoft's article, it is recommended to use the GPO method. The MSI install (separate) requires administrative install which we obviously can't do during white glove process. So how can I do the GPO method if it doesn't even exist in Intune yet?

Use Group Policy (recommended)
Enable the Prevent Microsoft Teams from starting automatically after installation Group Policy setting. You can find this policy setting in User Configuration\Policies\Administrative Templates\Microsoft Teams. This is the recommended method because you can turn off or turn on the policy setting according to your organization's needs.

If you run the MSI manually, be sure to run it with elevated permissions. Even if you run it as an administrator, without running it with elevated permissions, the installer won't be able to configure the option to disable auto start.

https://docs.microsoft.com/en-us/microsoftteams/msi-deployment

@htu-mark thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.

Issue was related to UAC prompt being enabled in Intune Device Configuration. For some reason, Microsoft has Teams running in admin mode during install unlike when installing Office apps, Visio, Project, Adobe Reader, or any other app we have being installed.


Server Execution Error with STDERR "Error response from daemon: Container {id} is not running"

I'm doing this kata and the runner frequently gives me this error when I try to submit my code (both example and actual tests):

I also got this while doing Walk-up Stairs in Python. I only got this once for sample tests.

@jhoffner is this a feature of recently updated #runner_frame to show the details of Server Execution Error? I don't remember seeing stderr with Server Execution Error before.
#978 is similar issue showing a message about /var/run/docker.sock.

How often is this happening? We run on AWS ECS and Amazon in their infinite wisdom decided to auto-update the ECS instance's Docker version on machine start automatically.
Docker was updated from 1.12.6 to 17.03.1-ce. Recently, looks like at this moment only one instance is still running the older version. Since we use our own scheduling engine with Docker at a low level, the new version is likely causing a new edge case to pop up that the scheduler needs to account for.
If this is only happening sporadically I'll probably wait until I'm back in the office on Tuesday to dive into this.

@kazk I deployed some updates to the error reporting before I left for vacation.Though in this case it looks like its reporting STDOUT from the CLI, not the spawned process.

How often is this happening?

Not often for me. I had this once and couldn't reproduce #978.
@Voileexperiments experienced #978 frequently, but it's not happening anymore.

auto-update the ECS instance's Docker version on machine start automatically.

Is there any way to stop this? Automatically updating Docker sounds painful :(

Docker was updated from 1.12.6 to 17.03.1-ce recently.

They changed the version scheme to YY.MM and now it's released monthly for edge and quarterly for stable. I added some links to relevant releases at the end of this comment for convenience.

Since we use our own scheduling engine with Docker at a low level, the new version is likely causing a new edge case to pop up that the scheduler needs to account for.

How is this implemented?
Are you using Docker Engine API? There're versioned APIs and supposed to be backward compatible.

Though in this case it looks like its reporting STDOUT from the CLI, not the spawned process.

Yeah, looks like this one is failed because the container with that id existed, but it wasn't running.

v1.12.6 (2017-01-10)
v17.03.0-ce (2017-03-01)
v17.03.1-ce (2017-03-27)

@jhoffner I just got this again.
I was able to inspect 2 responses after the first one.
I'm not sure what workerId is (instance id?), but it was both w-6948.
{
  "type": "execution error",
  "message": "The server was unable to process the request. Please try again.",
  "stderr": "Error response from daemon: Container ddec9d7c556b5b51dea287ff53f94b1c7ddd9cbb9ad5364b8d9d60c5aaae7605 is not running\n",
  "exitCode": 1,
  "exitSignal": "",
  "setupTime": null,
  "totalTime": 476,
  "receivedAt":<PHONE_NUMBER>143,
  "responseAt":<PHONE_NUMBER>619,
  "languageVersion": "6.x",
  "workerId": "w-6948",
  "result": {
    "serverError": true,
    "completed": false,
    "output": [],
    "successMode": "assertions",
    "passed": 0,
    "failed": 0,
    "errors": 0,
    "assertions": {
      "passed": 0,
      "failed": 0,
      "hidden": {
        "passed": 0,
        "failed": 0
      }
    },
    "specs": {
      "passed": 0,
      "failed": 0,
      "hidden": {
        "passed": 0,
        "failed": 0
      }
    },
    "unweighted": {
      "passed": 0,
      "failed": 0
    },
    "weighted": {
      "passed": 0,
      "failed": 0
    },
    "timedOut": false
  },
  "token": "[TOKEN]"
}

I don't know about frequency, it's not too often. But I was able to see this few times within 15 minutes by submitting many times.

I've been getting this error ALL day, seriously. Every time I submit either a test or a final solution.

I tried again logged out (no RED) and saved network logs as HAR using Chrome DevTools, then examined this using jq, 13/61 were errors.
# def runs: .log.entries | .[] | select(.request.method == "POST" and .request.url == "https://runner.codewars.com/run");
# def rjson: .response.content.text | fromjson;

# Total Requests
# [runs] | length
61
# Errors
# [runs | rjson | select(.type == "execution error")] | length
13

# workerId of 'execution error'
# [runs | rjson | select(.type == "execution error") | .workerId] | sort | unique
[
  "w-55226",
  "w-57729",
  "w-66504",
  "w-75614",
  "w-96997"
]

# workerId of 'execution success'
# [runs | rjson | select(.type == "execution success") | .workerId] | sort | unique
[
  null, # some responses were missing `workerId`
  "w-20771",
  "w-20881",
  "w-23913",
  "w-28982",
  "w-34863",
  "w-42848",
  "w-56175",
  "w-57966",
  "w-63153",
  "w-70013",
  "w-76801",
  "w-87379"
]

@luisgc91 is there a specific kata/language you are training on? I still haven't reproduced but I can clearly see from the error logs that this is affecting about a 6th of all requests, which matches what @kazk saw from his test run. All instances are now transitioned over to the latest Docker version so its not a mixed version issue.

Are you using Docker Engine API
We are mostly using the Dockerode library. I still need to investigate which API it is targeting. In some cases the docker cli is called directly.

Is there any way to stop this? Automatically updating Docker sounds painful :(
Yes, this needs to be stopped. I haven't figured out a way yet but I haven't investigated completely.

@jhoffner

We are mostly using the Dockerode library.

Are you using version option? Dockerode's README has this:
var Docker = require('dockerode');
var docker5 = new Docker({
  // omitted
  version: 'v1.25' // required when Docker >= v1.13, https://docs.docker.com/engine/api/version-history/
});

Looks like 1.12.6 works fine without this, but 17.03.1-ce needs it?

Docker v1.13 has Engine API v1.25 which introduced the following change:

The API version is now required in all API calls. Instead of just requesting, for example, the URL /containers/json, you must now request /v1.25/containers/json.

Engine API version history (v1.25)

@jhoffner
Are you using Docker for AWS?

Stable is released quarterly and is for users that want an easier-to-maintain release pace.

If Dockerode's version option fixes this issue, auto-updates might not be as painful because versioned engine APIs are advertised as backward compatible. And automatically updating to latest stable version is good for security reasons.

Looks like this issu is only happening for Python and Javascript oddly enough. I can't find logs of any other language and when I try using Ruby I can't reproduce.

Are you using Docker for AWS?

We are using http://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-optimized_AMI.html. Though I haven't updated the underlying image in a while. I think the ecs-init package has docker updates backed in, which is what held me up from finding a quick remedy for preventing auto-updates - if I recall correctly. We create and destroy so many one-time use containers in the coarse of a day, I think auto-updates will always be a risk. I doubt Docker is stress testing our use-case, and there are already so many edge case recovery conditions coded into the custom scheduler engine to deal with odd container start/stop/exec/remove conditions and status codes.

If Dockerode's version option fixes this issue

I've added this and deployed but the issues persist.

@jhoffner I am training on Javascript. The problem persisted in almost all katas.

@jhoffner
According to the docs, ECS Optimized AMI is based on Amazon Linux AMI and applies security updates automatically on boot.
I think repo_upgrade field in /etc/cloud/cloud.cfg controls it.
To turn it off:
# /etc/cloud/cloud.cfg
# repo_upgrade: security
repo_upgrade: none

See Q: How do I disable the automatic installation of critical and important security updates on initial launch?
Maybe let them email you so you can update manually for security updates?

The Amazon ECS-optimized AMI receives regular updates for agent changes, Docker version updates, and Linux kernel security updates. You can subscribe to the AMI update Amazon SNS topic to receive notifications when a new Amazon ECS–optimized AMI is available.
Subscribing to Amazon ECS–Optimized AMI Update Notifications

Looks like this issu is only happening for Python and Javascript oddly enough. I can't find logs of any other language and when I try using Ruby I can't reproduce.

Yeah, I don't know why it's only affecting those two. I tried few other languages and couldn't reproduce either.
JavaScript is still failing. Python is failing much less than earlier.
// jq -f analyze.jq < multiply-js.har | jq '{total_count, error_count}'
{"total_count": 60, "error_count": 8}
// jq -f analyze.jq < multiply-py.har | jq '{total_count, error_count}'
{"total_count": 56, "error_count": 0}
// jq -f analyze.jq < multiply-rb.har | jq '{total_count, error_count}'
{"total_count": 62, "error_count": 0}

The error is getting worse ...
Everytime I submit either a test or an attempt, I have to try at least 5 times.
Error response from daemon: Container b4d5dfd844e5b65f2a9e085fa0199856ba373e7f1cf3097bfb813ef414388427 is not running

@luisgc91 The issue flared up around the time that you logged this issue, and stabilized back down to about 20% of the time (for JS) shortly after, according to my logs. I deployed a patch last night that seems to have reduced this issue down to less than 1% of the time. I would prefer it to be 0% of the time so I'm going to keep this open for now and continue to make improvements on this, but as of now it looks like the issue is much more manageable.

For the record, this is also happening for Haskell, not just JS or Python.

Also happened once for SQL.
Maybe the popularity of the language (the number of users submitting at the time) correlates with the frequency of this issue happening?

Yeah I've noticed that this is not specific to a language, which makes me feel better because otherwise that would make absolutely no sense.
Across all requests on avg 2.5% are timing out (for reasons not likely due to bad user code), and 2.5% are failing due to this error. 5% failure rate is not an acceptable range, it's something I'm trying to carve out some time for so that I can take a deep dive.

CW is giving a new form of error:

(It seems to only happen on this kata)

This seems to have never happened again for a few weeks.
Closing.


export 'vue2Dropzone' was not found in 'vue2-dropzone' on console.

versions:
"babel-polyfill": "^6.26.0",
"vue": "^2.6.12",
"vue2-dropzone": "^3.6.0",
...
in Dropzone.vue
import {vue2Dropzone} from 'vue2-dropzone'
import 'vue2-dropzone/dist/vue2Dropzone.min.css'
....
My client wants to support ie11 so I must use<EMAIL_ADDRESS>I installed vue2-dropzone and set and then it worked.
it's working but printed that export 'vue2Dropzone' was not found in 'vue2-dropzone'  on console.
What should I do about it?
I want to remove the error message only.....

Shouldn't it read import { vueDropzone } from 'vue2-dropzone'?


SAK-43881 Forums/Discussions: Add calendar events for opening and closing of discussion forums and topics

This PR adds the option [defaulted to On] to send discussion forums/topics' opening and closing dates to Calendar when their access is set to be date-restricted. If the option is turned off, or the date restriction overall is turned off, Calendar events created for them will go away.
https://sakaiproject.atlassian.net/browse/SAK-43881

I've made all the requested changes from the first review on the amended commit. Thanks so much @adrianfish !


Validate Chain ID on ethereum connection establishement

We expect the client to be run for a network specified with boolean
flags like --mainnet and --goerli. Another setting that is required
is an URL to the Ethereum API.
Here we want to ensure that the API URL works with the network that the
client is expected to be run against. We use Chain ID for validation.
The exception is --developer network, that we won't validate the Chain
ID as it can vary.
Depends on https://github.com/keep-network/keep-common/pull/100
Depends on https://github.com/keep-network/keep-core/pull/3200

Run the client and I didn't notice any errors. lgtm.


Dont force name param in withdraw

The name parameter is no longer mandatory according to Binance docs (https://developers.binance.com/docs/binance-trading-api/spot#withdrawuser_data) and my test.
It may only do harm if it automatically saves the withdrawal address to the address book and bloats it (the limit is 500 items and then it starts rejecting withdrawals).

Thanks @knaperek


Challenge Create an Ordered list Has an Issue

Challenge Create an Ordered List has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

CatPhotoApp

Click here for cat photos.

Things cats love:

Milk

Curd

Butter

Top 3 things cats hate

cat nip

laser pointers

lasagna

It looks like the instructions are incorrect.

Your should have an ordered list for "Top 3 things cats hate"
is missing a semicolon.

 "assert.equal($(\"ol\").prev().text(), 'Top 3 things cats hate:', 'message: Your should have an ordered list for \"Top 3 things cats hate\"');",

Link to code

For whomever picks this up,

Your should have an ordered list for "Top 3 things cats hate"

should also begin with "You" for proper grammar and to match the subsequent test message, rather than "Your".

Similar issue on this challenge: If you capitalize Things Cats Love like it says on one of the tests on the left, it will fail.

Hello guys, I am working on this issue

I have tested this issue @raisedadead  and it works for me Create an Ordered List

@raisedadead, BTW which browser have you been using. I have tested this on chrome Version 50.0.2661.94 m

@mriyaz This is reproducible on all browsers"

Your should have an ordered list for "Top 3 things cats hate"

should be

Your should have an ordered list for "Top 3 things cats hate**:**"

There is a semi colon missing. Reset the code or open the challenge with a clean link in an incognito window and use the code from the description above this should be easy enough to reproduce.
https://www.freecodecamp.com/challenges/create-an-ordered-list

@mriyaz I have update the comment above for the things to be updated while checking this challenge.

Sorry @raisedadead, I don't get any error while working on this challenge
https://www.freecodecamp.com/challenges/create-an-ordered-list

@mriyaz Thats because you are using

Top 3 things cats hate:

instead of

Top 3 things cats hate

You are using the correct code. But the instructions accidentally state to use a statement without a :

So..  should we add more versions of the test to allow people to not include the semicolon?  Or to use all caps?
Or are we sticking with a strict expectation and we just need to fix a couple typos?  Cuz I feel like I can do that for my first FCC pull request ever  =)

@jhadams82  Please go ahead with the PR. I am stuck in creating a local instance of FCC. I am coordinating with @raisedadead over this problem.


Feature request:  Display collapse toggle on hover of the line number side bar.

Currently built into Atom core is the ability to collapse code blocks via cmd - option- { for collapse & cmd - option- } for uncollapse or by hovering over the left sidebar containing the editor's line number, which displays the upside down triangle toggle.
If you could also have the ability to hover over the editors line numbers to display the collapse-code toggle for your package that would be great!

Hi, thanks for your suggestion! I'm afraid, though, that it's not possible to fold markdown using the normal Atom API methods, since the lang package does not consider markdown sections being code blocks. So, the whole markdown-folder package is really just an ugly hack searching for heading prefixes and folding each line in that section individually. That's also the reason why the normal commands for folding can't be used in this package. Normal unfolding works though.


Areas without data should be colored consistently.

We used to color "0", which should be "N/A", white.  When ZCTAs were implemented zip regions without data were colored gray.  This lead to a situation where both white and gray regions can be seen.  We need to be consistent.

Hovercards also need to reflect missing data. There's two cases ...
(1) Some (but not all) of the categories are missing data
(2) There's not data for any of the categories
Here's mocks of the corresponding hovercards ...


CameraView Rotate Picture

T
Typo
Description
Using (https://github.com/CommunityToolkit/Maui/blob/main/samples/CommunityToolkit.Maui.Sample/Pages/Views/CameraView/CameraViewPage.xaml.cs) I observe that when taking a photo with portrait orientation, it is displayed correctly. When taking a photo with landscape orientation, it is rotated. (Samsung Flip 5 Android 14 / Samsung S24 Android 14 / Samsung Galaxy A03 Core Android 13  ).
Is this working correctly? Shouldn't the photo always appear correctly?.
How to reproduce the error?
1 - Position your device in portrait and do not turn the device until further notice.
2 - Enter CameraView Page
3 - Take a photo --> the photo will be displayed correctly in the image.
4 - Put the device in landscape
5 - Take a photo --> the photo will be displayed incorrectly in the image.
Take the photo without errors.
1 - Position your device in portrait and do not turn the device until further notice.
2 - Tap CameraView Page
3 - Take a photo --> the photo will be displayed correctly in the image.
4 - Exit the CameraViewPage
5 - Put the device in landscape
6 - Enter CameraView Page
3 - Take a photo --> the photo will be displayed correctly in the image.
The problem is that when taking the photo it saves the exif horientation that the device had before entering the CameraViewPage. At least that is my conclusion.

Page URL
https://learn.microsoft.com/en-us/dotnet/communitytoolkit/maui/views/camera-view?tabs=android
Content source URL
https://github.com/MicrosoftDocs/CommunityToolkit/blob/main/docs/maui/views/camera-view.md
Document Version Independent Id
ddd38b0d-10d0-a000-b6aa-2769c945c4fd
Article author
@bijington
Metadata

ID: ddd38b0d-10d0-a000-b6aa-2769c945c4fd
Service: dotnet-communitytoolkit
Sub-service: dotnet-maui-community-toolkit

T
Typo
Description
Using (https://github.com/CommunityToolkit/Maui/blob/main/samples/CommunityToolkit.Maui.Sample/Pages/Views/CameraView/CameraViewPage.xaml.cs) I observe that when taking a photo with portrait orientation, it is displayed correctly. When taking a photo with landscape orientation, it is rotated. (Samsung Flip 5 Android 14 / Samsung S24 Android 14 / Samsung Galaxy A03 Core Android 13 ).
Is this working correctly? Shouldn't the photo always appear correctly?.
How to reproduce the error?
1 - Position your device in portrait and do not turn the device until further notice. 2 - Enter CameraView Page 3 - Take a photo --> the photo will be displayed correctly in the image. 4 - Put the device in landscape 5 - Take a photo --> the photo will be displayed incorrectly in the image.
Take the photo without errors.
1 - Position your device in portrait and do not turn the device until further notice. 2 - Tap CameraView Page 3 - Take a photo --> the photo will be displayed correctly in the image. 4 - Exit the CameraViewPage 5 - Put the device in landscape 6 - Enter CameraView Page 3 - Take a photo --> the photo will be displayed correctly in the image.
The problem is that when taking the photo it saves the exif horientation that the device had before entering the CameraViewPage. At least that is my conclusion.

Page URL
https://learn.microsoft.com/en-us/dotnet/communitytoolkit/maui/views/camera-view?tabs=android
Content source URL
https://github.com/MicrosoftDocs/CommunityToolkit/blob/main/docs/maui/views/camera-view.md
Document Version Independent Id
ddd38b0d-10d0-a000-b6aa-2769c945c4fd
Article author
@bijington
Metadata

ID: ddd38b0d-10d0-a000-b6aa-2769c945c4fd
Service: dotnet-communitytoolkit
Sub-service: dotnet-maui-community-toolkit

D

I´m sorry .  Please explain the correct place for this issue is at https://github.com/CommunityToolkit/Maui/issues/2096


Opening a floating window changes colors of separators

When a floating window is open (lazygit, telescope, Lazy), the colors of the separators change in a way that makes them stand out from the rest of the background (see example):
Normal:

With floating window:

This happens with the default configuration (called require("slimline").setup({}))

Thanks for reporting this issue.
Weird, it does not happen for me.
Does it change when you are using a different colorscheme? Is that a complete transparent scheme?
Any chance I can reproduce that somehow? I am not sure what is happening. Slimline at least does not listen to floating windows and changes highlights in any way dynamically

The fact that you can't replicate lead me to investigate further (I had tried different themes and replicated with them all). Turns out the culprit is a plugin for dimming out of focus windows.


proto: move extension-specific linking validation into extensions

Signed-off-by: Mike Schore<EMAIL_ADDRESS>Description: A couple of the proto descriptors validated during startup are specific to extensions that may be compiled out. This change only validates their presence when the extensions are used. This fixes some spurious validation failures in certain minimal build configurations.
Risk Level: Low
Testing: Ran test suite, ran server.
Docs Changes: N/A
Release Notes: N/A

I considered moving ratelimit as well, but we didn't actually run into issues with it. (Not sure if it's actually possible to fully compile our ratelimit at this point.) Also an open question whether there are any other cases that should be included. Just wanted to mention in case anyone has insight/opinions.

Not sure what we might be missing - but one thought I floated by Matt in an earlier conversation is that we could also just do dummy linking for everything instead of validation, until whatever needs to be fixed upstream for this all to work is fixed.

@goaway I think the challenge is figuring out what "everything" is here. Do you have any thoughts on how that would be computed?

Empirically, we encountered just the above two cases when building with only HttpConnMan and the Router as extensions, with a single public entrypoint.
We could possibly induce further failures by building with only a single dummy filter.
However, this really only captures the current state of the world, and further development/refactors could change things. (As an aside, the current validation setup in proto_descriptors.cc will fail fast, but requires a code change to see what actually failed, since it only returns a boolean. We could assert/panic inside that file - though perhaps the boolean return value is better for testing.)
My thought though was merely to replace the validation of each proto currently checked with a dummy ref to ensure it gets compiled in. This won't capture cases we've missed, but it won't reduce our coverage either.
If we really wanted to go all in; we could add a dummy message to any proto file we build in, and explicitly reference those messages whenever the generated header is included.

And also, thanks @htuch !

@goaway yeah, I guess it would be a bit cleaner, but I'm also wondering if we should just figure out if the suggestion in https://github.com/protocolbuffers/protobuf/issues/4221 makes sense. If we set always_link, does it work?

@htuch I was under the possible misapprehension that always_link didn't work in this case for some reason. If it does, I agree that's cleaner than dummy refs in code.

Well, not sure if it does :) The last state in that Protobuf GH issue is that we needed to try it.

I don't mind giving it a try. Can at least see if it works for the case we encountered.


Refactor RayCasterFloat::Distance

Refactor the RayCasterFloat::Distance function by decoupling the search of vertical and horizontal hit

I create this pull request because I found the original implementation of  RayCasterFloat::Distance  hard to follow. I came across a youtube video (https://www.youtube.com/watch?v=gYRrGTC7GtA) which explains raycasting in great detail and with animated figures. I rewrite this function by following the code provided in his repo (https://github.com/3DSage/OpenGL-Raycaster_v1) with few modification to suites our needs. Notice that this pull request WON'T fix any existing issue (i.e. broken wall issue caused by buffer overflow) but instead provides a cleaner representation of how raycasting works.

I've created a text-based diagram that briefly explains the coordinate system used in the RayCasterFloat::Distance() function.
Instead of creating a new function that calculates the distance between 2 points, I replaced it with a marco.

@WeiCheng14159, would you like to rebase the latest master branch and rework this pull request recently?

Working on it !

Thank @WeiCheng14159 for this effort!

You are welcome. Happy Chinese New Year !


Create Steps' conditionals handler step and made several improvements

create "Steps' conditionals handler" step
capitalized Solution_name variable per our conventions
replaced all steps' conditionals that are used multiple times with the "Steps' conditionals handler" step outputs
replaced the new created tag description with "${{ github.event.head_commit.message }}" which takes the message of the last commit
removed "Determine if signing should be applied to AppxBundle" step and instead use "${{ steps.step_conditionals_handler.outputs.is_github_release }}" as a value for the "Appx_Package_Signing_Enabled" parameter

NOTE: all new steps' conditionals are compared to a string of 'true' or 'false', because the output of a script apparently can't return a Boolean

@kulov May be use Squash Merge to remove the overall meaningless commits from the history ?


Implement breadcrumbs

Describe the problem/challenge you have
Currently when viewing say a Pod, Deployment, etc.. the only way to navigate backwards is by using your brower's back button.
Describe the solution you'd like
For a first step we could essentially just replace the first part of the view heading with a link to where you just came from, add a caret and remove the k8s community icons.
Anything else you would like to add:
In the future I think we should look into using a back button instead of a breadcrumb, as you can only go 1 level deep so imo there's not as much of a need for breadcrumbs vs back button. Another option is a permanent < > switcher that allows users to go forward and backward between views

Figma file - https://www.figma.com/file/CvMwJPlvETtFoPx43oXKUd/Breadcrumbs-and-back-button?node-id=1%3A152

We should hold on this until we figure out what we want to do with the overall navigation.

imlpemented in #834


Failed to read artifact descriptor for com.alibaba:dubbo:jar:2.6.3

Environment

Dubbo version: 2.6.3
Operating System version: Ubuntu 18.04
Java version: 10.0.1

Step to reproduce this issue

create a new project with maven pom.xml depend on dubbo 2.6.3
compile the project

Actual Result

Failed to read artifact descriptor for com.alibaba:dubbo:jar:2.6.3: Could not find artifact com.alibaba:dubbo-parent:pom:2.6.3 in central (http://central.maven.org/maven2/)

com.alibaba:dubbo-parent:pom:2.6.3 has not been deployed to http://mvnrepository.com/artifact/com.alibaba/dubbo-parent
but all of others have been deployed to http://mvnrepository.com/artifact/com.alibaba/dubbo

I have the same question. Is there any official answer?

I rolled back to version 2.5.10.
Version 2.6.2 also had the shutdown graceful problem in tomcat 8.5.23, and I had to use the following method in my listener:
ProtocolConfig.destroyAll();

@huadong The Apache community is still voting for v2.6.3, so it's not available at present. I have updated the release note: https://github.com/apache/incubator-dubbo/releases/tag/untagged-24fcb73b05663c44192a

@chickenlj Thank you!
The tag for v2.6.3 is very helpful, I can try the v2.6.3 from the source code. I think the feature which shutdown graceful is very important, for sometimes we need to use the hot reload feature of tomcat.

I have the same question.

@chickenlj I had packaged v2.6.3 from the source code. When shutdown tomcat, it logged this WARNING:

appears to have started a thread named [DubboClientReconnectTimer-thread-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
sun.misc.Unsafe.park(Native Method)
java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)

So I had to kill the tomcat process instead of executing the shutdown.sh of tomcat.
Should I do any more configurations?

@dslchd According to #1155, the netty blocks shutdown tomcat.
the conflict is :

dubbo v2.6.3 depends on netty v3.2.5,
curator-framework v2.12.0 depends on netty v3.7.0.

tomcat shutdown normally after exclude netty from curator-framework.
Maybe dubbo should explicitly close zookeeper client in the future.

@huadong Thank you for your answer.
But I'm not using dubbo v2.6.x right now, because I was using v2.6.2 and the graceful shutdown of dubbo was still a problem in tomcat, which is probably why you said it.
I'm now rolling back to v2.5.10 to solve this problem using the following solution
The code is as follows:
       ProtocolConfig.destroyAll();
           Field field = NettyClient.class.getDeclaredField("channelFactory");
           field.setAccessible(true);
           ChannelFactory channelFactory = (ChannelFactory) field.get(NettyClient.class);
           channelFactory.releaseExternalResources();
           field.setAccessible(false);

@ralf0131 Sorry! I filed a new issue #2334 for the elegant shutdown.


winget client is not discoverable in the Microsoft Store

Brief description of your issue
I opened a bug earlier  which I think got closed a little bit to quickly, as only 2 points out of the 3 have been fixed (Thank you for the fast fix! 👍🏻 👍🏻 !!)
If you try to search for 'winget' or even 'app installer' in the Microsoft store, you get only 'weird' results back.
It is impossible to find winget in the microsoft sotre EXCEPT if you use the link you guys provided.
I also tried to searched for App installer  or Windows package manager. didnt work. (It is also a bit confusing that there is absolutley no mention of winget in the details of 'App Installer'.
In other words, winget is not discovorable on the microsoft store - which according to your documentation, is the recommended way of installing it.
Steps to reproduce
open the microsoft store, and search for 'winget'
Expected behavior
We should have the winget client FIRST, then other results that are of the same 'nature'.
Actual behavior
a lot of different results get returned back. But NONE of them is the actually winget client.
Environment
windows 11

WinGet is included in the "App Installer" which is a system component. System components aren't "searchable" in the Microsoft Store:

Getting the latest version should happen automatically with the Microsoft Store (as long as it's not disabled).
You can manually trigger the update in the Microsoft Store with "Get updates".
We do need to update the documentation.