Readme only!

Hi there, thanks for this nice script. It would be nice to have a readme only option... so when 'true' just show tags and don't let user to edit,add,remove them.

What did you have in mind for preventing editing/adding? Just not append the remove button to the list items? Would adding the readonly or disabled attribute to the input not suffice for your use case?

Probably the 'disabled' attribute it is enough however I'd preffer to don't even render de input filed. Also I'd set the the tags as  for redirecting (to the url that shows all the items with the selected tag).
Thanks

Hmm your use case seems pretty specific. I'd rather not add extra options if you can accomplish this with the available methods, especially since 2.0 will deprecate certain options for the same reason.
You could use taggle.getTags().elements to do whatever you'd like with the tags and you can use taggle.getInput() and remove the input if you'd rather it not be there.

I think what you're looking to do is just display a list of tags which wouldn't require this library at all. You can use this library to gather the tags, maybe save them to a DB, and then display them as list items. You can also, of course, take the suggestion mentioned above.

It's very common in tagging to allow or not users to add/delete tags, in my case I only allow if a user is registered within the platform therefore an option for readme only so on 'true' the script wont render the input, placeholder, etc would make things much easier, any way I've already sorted it out. Thanks and hope you add the option :)

Can you send a PR so we can see what this might look like as an implementation? Or maybe edit this fiddle here and show me what it'd look like?

I didn't change snything in your script, I've used the 'tagFormater'. No very happy about it as there is not point to render the input, close button and then remove() .


Move docs-resources to point at latest commits.

This bumps the docs-resources forward to point at the latest commits which clean up heading font sizes.

@wmat Thanks. Looks better now


v1.2.3 nacos timeout

Describe the bug
use nacos to registe and discover, first connection is ok, but restart api, connect timeout
To Reproduce
what should i do? upgrade can solve this problum?

The code is

The error is

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environments (please complete the following information):

OS: [e.g. Linux]
go-zero version [e.g. 1.2.1]
goctl version [e.g. 1.2.1, optional]

More description
Add any other context about the problem here.

pls figure out your go-zero and goctl version.
post a simply test enviroment and the error log


vendor: update zfs dependency

Signed-off-by: Stephen J Day<EMAIL_ADDRESS>

Codecov Report

Merging #2253 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2253   +/-   ##
=======================================
  Coverage   41.13%   41.13%
=======================================
  Files          66       66
  Lines        7758     7758
=======================================
  Hits         3191     3191
  Misses       4063     4063
  Partials      504      504

Flag
Coverage Δ

#windows
41.13% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM


package

Hi, as I suggested org.hotswap.plugin package for HotswapHelper, I think that it would be better to place it to org.hotswap.hotswaphelper or org.hotswap.idea.hotswaphelper. Otherwise great work!

yeah, that would be better, thanks

fixed.


new dataset

@imranyousuf we will be using this other haxby dataset (ds105) that has been processed for us. We wont be using the data set from openfmri.org
https://nipy.bic.berkeley.edu/rcsds/

ok thanks for letting me know. I will work on that and write the test for it.


Too much summary text in dataset box

I would like to limit the amount of text in the box. In the Canada Buy and Sell example below I think this is too much.
First preference: Put a word limit in the admin (max 350 characters)
Second preference: Limit text in the box to three lines and add a "... " at the end

Of those currently in the registry, I ran:
SELECT id, description_en, LENGTH(description_en) len
FROM data_registry_collection
WHERE description_en IS NOT NULL
ORDER BY len DESC;

Canada and Zambia are test data. The next longest is Australia with 255 chars: https://data-registry.datlab.eu/en/collection/19
Australia looks like. We can see how 442 characters look once added.

Australia looks fine. We can see how 442 characters look once added.

https://data-registry.datlab.eu/en/collection/77.  I think it looks fine as well.

Yes, 4 lines of text seems fine (half the length of Canada in the issue description).


Misleading error message "No contribution comment"

I made a typo in the date contained in "(Contributed by ...)", which was not detected by metamath.exe, verify markup. metamath-knife, however, detected it, but gave a misleading error message:
/target/release/metamath-knife --verify
warning: No contribution comment
--> ./set.mm:505703:5
|
505703 |     satf0 $p |- ( (/) Sat (/) ) = ( rec ( ( f e. _V |-> ( f u.
|     ----- No (Contributed by...) provided for this statement
There was a (Contributed by...), but it was erroneous...

The error message could/should be changed to "Missing or malformed contribution comment" as proposed by @tirix in https://github.com/metamath/set.mm/pull/3497


feat: Explore downloading collections as a feature.

Describe the feature

Download models from a collection url on civitai.

Additional context
Requested by AeolianTheComposer

Potentially also add feature of downloading models by creator

It be cool if it could download all of the models attached to a model page.  Not sure if it can, only played with it for a few hours.

download

It be cool if it could download all of the models attached to a model page. Not sure if it can, only played with it for a few hours.

It is possible since when the metadata is requested from the API, it lists all of the versions of a model. What could be done is by adding a --all-versions option to download all of versions


Fix for Persian locale params

Reference: http://lh.2xlibre.net/locale/fa_IR/

Do you have a colleague who can +1 these changes?

+1

+1  for this changes.

Are the numbers going to be localized with Persian digits too? If so, decimal and thousand separators should be proper Persian characters. But if that’s not the case, then these are correct values for an English number in Iranian locale and I can bless this PR with a :+1:!

+1 for these changes.

+1

@mostafah Unfortunately the current code doesn't provide localized digits. I'm thinking to work on it by patching django.utils.formats. Glibc has placed "alternate digits" in Dates section, and it has place for dual digit alternatives. Are you aware of any language which has a different symbol for 10*X + Y in place of XY?

@remohammadi That would be awesome. This may be a little off-topic here, but since you asked, it never occurred to me that any language should have such modification to the Arabic numeral system (our familiar ten-digit number system). I took a quick look around CLDR (specially this chart that shows number formatting variations) and didn’t see such a thing. But there mush be some reason for glibc to have dual-digit alternatives.

merged in f1ff9407c94c4574d100efc3d224c1f79e2fb53d, thanks.

+1

+1

Thanks all, this has been merged. No more +1s needed. :-)


Add OpenSingleDirectory and an example with all dialogs

I was only able to test this on Windows and Linux + Zenity, but I followed the documentation I could find for kdialog and Mac. Would you be able to test this out on those systems?
I added the new example since it gives you a quick way to try out everything at once. I found it handy for testing.
Great crate, by the way! I was happy to find something without any special build dependencies.

Great work! I'll test it later when I have free time.

I've tested it on macOS and KDialog, and fixed some problem. It works fine now.


More intuitive interface for checking if an attribute exists would be nice

My understanding, please correct me if I'm wrong, is that the correct what to check if an attribute exists is to see if the value is the zero-length string. This yields code such as
if (strcmp(requiresSecurityAccessAttr.value(), "read") == 0)
{
...
}

which is a bit nonintuitive to read.

Please use Discussions to ask questions. You can check if the attribute exists by simply treating it as a boolean value, eg if (requiresSecurityAccessAttr), see https://pugixml.org/docs/manual.html#dom.cpp.

I tried that but it didn't seem to work so I thought it applied only to
elements but I guess I made some kind of mistake.
Den fre 11 nov. 2022 kl 21:39 skrev Arseny Kapoulkine <
@.***>:

Please use Discussions to ask questions. You can check if the attribute
exists by simply treating it as a boolean value, eg if
(requiresSecurityAccessAttr), see
https://pugixml.org/docs/manual.html#dom.cpp.
—
Reply to this email directly, view it on GitHub
https://github.com/zeux/pugixml/issues/532#issuecomment-1312174505, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGK2BOG36EUNPWADQIZ23DTWH2VG5ANCNFSM6AAAAAAR5IU4AY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Inference error using precomputed alignments

Dear OpenFold community,
I was encountering an error when running inference using precomputed alignments.

INFO:/software/sse/manual/OpenFold/2.0.0/run_pretrained_openfold.py:Using precomputed alignments for T1050 at /proj/nsc_testing/xuan/openfold_results_2.0.0/output/alignments...
Traceback (most recent call last):
  File "/software/sse/manual/OpenFold/2.0.0/run_pretrained_openfold.py", line 470, in <module>
    main(args)
  File "/software/sse/manual/OpenFold/2.0.0/run_pretrained_openfold.py", line 279, in main
    feature_dict = generate_feature_dict(
  File "/software/sse/manual/OpenFold/2.0.0/run_pretrained_openfold.py", line 141, in generate_feature_dict
    feature_dict = data_processor.process_fasta(
  File "/software/sse/manual/OpenFold/2.0.0/openfold/data/data_pipeline.py", line 876, in process_fasta
    template_features = make_template_features(
  File "/software/sse/manual/OpenFold/2.0.0/openfold/data/data_pipeline.py", line 44, in make_template_features
    templates_result = template_featurizer.get_templates(
  File "/software/sse/manual/OpenFold/2.0.0/openfold/data/templates.py", line 1126, in get_templates
    sorted(filtered, key=lambda x: x.sum_probs, reverse=True)
TypeError: '<' not supported between instances of 'NoneType' and 'NoneType'

Has anyone experienced a similar issue, or does anyone have suggestions on how I might resolve this? Any advice or guidance would be greatly appreciated.
Thank you for your time and help.

Hello!
Maybe the fasta ID is not being parsed correctly? I had a similar issue. Try testing with this fix #485


Suggestion: Please upgrade current find feature(CRTL+F) for directory search(multi-sub directories/files search and filter feature*)

Say we opened VSCode with a directory(folder) which consists with lot of sub-directories and files and we opened a file there and we want to search  keyword within entire opened folder structure and their sub items(folders/files).
Right now VSCODE has no such feature it's only searching within current document opened and also has no filtering feature exists in notepad++:

This multi-sub directories/files search and filter feature  is really useful and necessary feature for Developers.
Thank you hope you guys pay attention on this requirement.

Search: Find in all files: Ctrl-shift-f lets you do this.

@erihanse  Got it thank you.It works for find file,but do we have any shortcut key for to do filtering stuff?

Yeah, Ctrl-shift-j :)

If you haven't already, I suggest you have a look at https://code.visualstudio.com/docs/editor/codebasics#_search-across-files, maybe you'll find other handy features in the document as well.

@erihanse  Thank you very much,That's what I really want.


[FEAT] Module initialization using lifecycle hooks

Is your feature request related to a problem? Please describe.
Modules are currently written in a pretty chaotic way where initialization does not happen in an obvious or well defined order.
Describe the solution you'd like
Extend ConduitServiceModule with a class exposing lifecycle hooks for modules to use during initialization.
Said class should provide adequate options to cover any use case in regards to initialization order.
I can think of the following core initialization steps modules generally go through:

initialization (before registering with Core)
schema registration
activation

To cover any possible use case we should cover pre-target, target and post-target hooks for every(?) given step.
Example:

pre-registerSchemas()
registerSchemas()
post-registerSchemas()

That way we get (optional) finer control over initialization while retaining the structure's self-descriptive nature.
While not strictly related to initialization, said class should probably also standardize configuration functions names (eg setConfig()).

I should probably clarify pre/post-targets a bit further.
These are definitely not going to be abstract methods, therefore modules won't really need to implement these, as opposed to say activate() or initizialize() (which are already abstract in ConduitServiceModule).
When it comes to registerSchemas(), this technically isn't required as certain modules simply don't register any schemas, but we might wish to make it abstract anyway and just re-implement it as an empty block on these edge cases.


texlive: 2020.20201009 -> 2020.20210109

Motivation for this change
Facilitate #107119 and transition to the final texlive 2020 snapshot
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build tests.texlive

@GrahamcOfBorg build tests.texlive

@veprbl May you fix the conflicts please?

@veprbl May you fix the conflicts please?


useList documentation

IssueHunt Summary

Referenced issues
This pull request has been submitted to:

#171: Missing useList in documentation

IssueHunt has been backed by the following sponsors. Become a sponsor

👍 👍


Added a configuration to allow for prefetching to keep the existing pool

Currently, switching to a viewer with a stack prefetch tools removes all existing prefetch requests.
By changing a boolean value, this is no longer the case.
Solves issue #529
config = cornerstoneTools.stackPrefetch.getConfiguration();         config.preserveExistingPool = true;
Please note that the build is currently K.O. but was before my commit.

CC: @JamesAPetts, broken build is related to a freehand change

@dannyrb , appologies for the delay, I'll check this tomorrow morning.

The build was fixed in #556, if you'd like to pull master back into your branch.

@Saucistophe can you pull + merge latest so CI picks them up for your PR?

Coverage decreased (-0.005%) to 7.239% when pulling e64fa4ee6adc4a888a76d7483ba01974db3e21fa on Saucistophe:master into eaeaef55f78a59749fc47911dbc20a4650d58a1d on cornerstonejs:master.

There you go.
The coverage decreased a bit, but hey, I increased by 1.3% last time!
I was wondering where to document the changes I made? Maybe I can add a quick note somewhere.

@Saucistophe You can put it under Unreleased in the changelog. Thanks!

Can this be merged now? :)

I'm sorry to insist, but that would be super awesome if we could test it soon, I'm changing jobs and would like to leave a clean slate to my successor. Thanks!

Thanks! Sorry, I was out for vacation.


How to prevent cache Stampede ( thundering herd) problems ?

Hello, i recently evaluate hyperf to replace my existing laravel application and i have a question that is there a way to achive the same function as example below ?
Cache::lock('foo', 10)->block(5, function () {
    // Lock acquired after waiting a maximum of 5 seconds...
});

https://laravel.com/docs/10.x/cache#managing-locks
reference: https://www.thetechplatform.com/post/how-to-prevent-cache-stampede-thundering-herd-problems

@ndinhbang you can try this component: https://github.com/friendsofhyperf/cache

@huangdijia thank you so much

You are welcome！


make jdbc driver executable without any dependency

Summary

clean up pom files by removing unnecessary dependencies
make all dependencies optional for clickhouse-jdbc
add main class to clickhouse-jdbc for testing purpose
add GraalVM configuration for building native image

Checklist
Delete items not relevant to your PR:

[ ] Unit and integration tests covering the common scenarios were added
[ ] A human-readable description of the changes was provided to include in CHANGELOG
[ ] For significant changes, documentation in https://github.com/ClickHouse/clickhouse-docs was updated with further explanations or tutorials

Query
Java Client
Java Client(native)
JDBC Driver
JDBC Driver(native)

select 500000000
200ms
10ms
330ms
28ms

select number::Int8 v from numbers(500000000)
10s
29s
15s
48s

GraalVM CE does not support PGO(profile-guided optimization), so the native binary only reduced startup time and memory footprints without C1/C2 compilation as in JIT. Would be interesting if someone with GraalVM EE to fine-tune the configuration and share the test results.
Note: upx reduced the binary file from 32.7MB to 10.8MB, without performance degradation.


Harmonize network playbook yocto

Refactor the network playbooks to be closer to Debian/CentOS one.
Also put some tasks out of the playbook cause they have nothing to do with network configuration.
See the equivalent PR on debiancentos : #593
API changes:

PTP/NTP synchronization is now configured in playbooks/seapath_setup_time_synchronization.yaml
syslog is now configured in roles/yocto/syslog
network inside VMs is not configured anymore. The user should write its own playbook if he want to do that.

There is no changes for the user if he uses the seapath_setup_main.yaml playbook.

This work will be integrated in another pull request that moves timemaster to a role.


Add documentation for extract line numbers in metrics

@shahzebsiddiqui I am not sure why URL check failed. Docs was built successful though.

@shahzebsiddiqui I am not sure why URL check failed. Docs was built successful though.

dont worry too much about the urlcheck sometimes they come and go and if its persistent issue then we need to fix it. It good practice to check the urlcheck and then navigate to website. The urlcheck has a timeout and retry limit you can take a look at https://github.com/buildtesters/buildtest/blob/devel/.github/workflows/urlchecker.yml for more details. I typically update the urls or fix them if its a known issue. Sometimes websites go down or url gets changed over time.

@Xiangs18 i was looking at the first example, i think you should update the buildspec to remove linenum_to_stderr that one is not being used for anything and is not being described in the text above. I think we had this buildspec from the regression test perspective to capture stderr as well.

fixed, this PR is ready to merge.

thanks @Xiangs18 this looks good! I will merge this in


docs(material/chips): remove unused field visible

Further, I would suggest removing the following fields as they are not modifiable within the example. As an alternative, buttons could be added to toggle the state of the fields. If you like, I would further modify the example as wished.
  selectable = true;
  removable = true;
  addOnBlur = true;


Sync releases table with tags on push and for mirrors

Fixes #2154
Not fully tested but ready for review

So, why do we need to do this? Tags and Releases are not the same thing, they should not be treated as the same thing... If we need this list it should be fetched from the GitRepo directly 🤔

@bkcsoft this is only way to efficiently implement release page paging and to have release page match github behavior. Releases and tags are actually just extenended tags so can say they are quite the same

@lafriks I think maybe @bkcsoft is right. Since user will input username and password, we can retrieves release information via github API and inserted to gitea.( maybe an checkbox option: sync releases ). And this sync function also could be a button on tags UI to publish all the tags.

@bkcsoft @lunny it's not about just migration from github it's about displaying tags that are not linked to releases in release page like github is doing:

And it does not matter if repository is migrated or tags are created from git client. Not everyone wants or need to create releases for each tag but it is useful when creating tag to see kind of release list and only if needed create release with additional info and attachments. This is especially important for mirrored repositories and they can also be mirrored from github/gitlab etc

And also this was the functionality gitea had before release page was rewritten to show only data from database (I'm not against it)

@lafriks OK. I see.

LGTM

we can retrieves release information via github API

@lunny I thought that any non-repo migration/sync would be left to third-party tools?

@bkcsoft but this is PR is not related to it in any way but otherwise I agree 3rd-party sync/migration should be external tool

@lafriks Mainly just thinking out loud 🙂

@ethantkoenig fixed and also refactored code to minimize chance of possible race conditions

@lafriks and this one.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b0f7457). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master    #2459   +/-   ##
=========================================
  Coverage          ?   26.74%
=========================================
  Files             ?       84
  Lines             ?    17043
  Branches          ?        0
=========================================
  Hits              ?     4559
  Misses            ?    11809
  Partials          ?      675

Impacted Files
Coverage Δ

models/repo.go
13.5% <0%> (ø)

models/repo_mirror.go
0.61% <0%> (ø)

models/release.go
0% <0%> (ø)

models/update.go
10.81% <0%> (ø)

Continue to review full report at Codecov.

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

@lunny I think I found bug but have to still reproduce that, do not merge yet. Would be great if someone could test it on his dev environment

@ethantkoenig fixed your suggestion
@lunny I think I fixed the bug but would appreciate if someone could test it more. At least for me it seems to work correctly now

@lafriks Found two issues.

git treats tags case sensitive, therefore using toLowerCase could drop a tag
if a tag is removed and added on a new commit sync doesn't update tag reference

But maybe there are more.

@lafriks Guess I found another one.
Creating a release with an existing tag doesn't work anymore because an existing tag is already present as release and database is complaining about unique constraint.

@lafriks Ok, I have finished my examination. Last commit definitely fixes bugs regarding release creation.
So above mentioned issues are still a problem.
As toLowerCase isn't an issue created with this PR it should be addressed separately.
But IMO tag reference update should be fixed before merging.

@lafriks I believe I found a bug.
Steps to reproduce:

Create a mirror repository of a Github repo with releases (for example, I used https://github.com/ethantkoenig/run_lambda)
Make the repository a regular, non-mirror repository
Clone the repo, and try deleting a tag (e.g. git push origin :v1.0.4)
The release count remains unchanged, and the deleted tag still shows up in the list of release. When you try to view the deleted tag, you get a 404.

LGTM

Make L-G-T-M work

I made a mistake. @lafriks


Bug Run in ./private-tangle.sh install

Bug description
Briefly describe the bug.
Docker and docker-compose version
Which version of Docker and docker-compose are you running?

Docker version:
pi@raspberrypi:~ $ docker --version
Docker version 24.0.6, build ed223bc
pi@raspberrypi:~ $ sudo apt install docker-compose
Lendo listas de pacotes... Pronto
Construindo árvore de dependências... Pronto
Lendo informação de estado... Pronto
docker-compose is already the newest version (1.25.0-1).
Os seguintes pacotes foram instalados automaticamente e já não são necessários:
libfuse2 tini
Utilize 'sudo apt autoremove' para os remover.
0 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 0 não atualizados.
pi@raspberrypi:~ $ docker-compose --version
docker-compose version 1.29.2, build unknown

Hardware specification
What hardware are you using?

Operating system:
Raspberry pi 4 Model 4 4GB

Steps To reproduce the bug
Explain how the maintainer can reproduce the bug.
Based on the provided information, here's how the bug can be reproduced:
Steps To reproduce the bug

Environment Setup:

Use a Raspberry Pi with the same OS and environment as yours.
Ensure that Python 3.9 is installed along with the required packages (urllib3, requests, docker, etc.).
Install Docker and Docker Compose on the Raspberry Pi.

Clone the Repository:

Clone the one-click-tangle repository into the home directory of the Raspberry Pi:cd ~/
git clone [repository_url] one-click-tangle

Navigate to the Hornet Private Net Directory:

Change the directory to hornet-private-net within the one-click-tangle repository:cd ~/one-click-tangle/hornet-private-net

Run the Installation Script:

Execute the private-tangle.sh script with the install argument:./private-tangle.sh install

Observe the Errors:

After running the script, you should observe the errors mentioned in your initial message, starting with the dig command not found and followed by the connection errors related to Docker.

Note: The exact reproduction might vary depending on the specific environment configurations, installed packages, and other factors. The maintainer might need to ensure that the environment closely matches yours to reproduce the bug accurately.
Expected behaviour
You expected the ./private-tangle.sh install command to successfully install and set up a private Tangle using the Hornet node software. This would involve initializing necessary configurations, starting up the required containers, and ensuring that all dependencies and services are running properly.
Actual behaviour
When you executed the ./private-tangle.sh install command, several errors occurred:
The dig command was not found, as indicated by the error message ./private-tangle.sh: linha 26: dig: comando não encontrado.
There was an issue with the Python script trying to make a connection, which resulted in a ConnectionRefusedError: [Errno 111] Connection refused.
This connection issue cascaded into multiple other errors, all stemming from the inability to establish a connection. The primary issue seems to be related to the Docker service, as indicated by the error messages related to docker/transport/unixconn.py and docker.errors.DockerException.
Errors
./private-tangle.sh: linha 26: dig: comando não encontrado: This error indicates that the dig command, which is commonly used for DNS lookup operations, is not available on your system.
ConnectionRefusedError: [Errno 111] Connection refused: This error suggests that the Python script tried to establish a connection (likely to a Docker service or container) but was unable to do so because the connection was refused.
urllib3.exceptions.ProtocolError: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused')): This error, stemming from the Python urllib3 library, further confirms the connection issue.
requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused')): This error from the Python requests library is another manifestation of the connection problem.
docker.errors.DockerException: Error while fetching server API version: ('Connection aborted.', ConnectionRefusedError(111,'Connection refused')): This error indicates that the script was unable to fetch the Docker server API version due to the connection being refused.

This is what is coming out when I try to run ./private-tangle.sh install:
pi@raspberrypi:~/one-click-tangle/hornet-private-net $ ./private-tangle.sh install
./private-tangle.sh: linha 26: dig: comando não encontrado
Setting permissions for Hornet...
Stopping containers...
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 394, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 234, in request
super(HTTPConnection, self).request(method, url, body=body, headers=headers)
File "/usr/lib/python3.9/http/client.py", line 1255, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1301, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1250, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1010, in _send_output
self.send(msg)
File "/usr/lib/python3.9/http/client.py", line 950, in send
self.connect()
File "/usr/local/lib/python3.9/dist-packages/docker/transport/unixconn.py", line 27, in connect
sock.connect(self.unix_socket)
ConnectionRefusedError: [Errno 111] Connection refused
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/dist-packages/requests/adapters.py", line 486, in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755, in urlopen
retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 532, in increment
raise six.reraise(type(error), error, _stacktrace)
File "/usr/lib/python3/dist-packages/six.py", line 718, in reraise
raise value.with_traceback(tb)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, in urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 394, in _make_request
conn.request(method, url, **httplib_request_kw)
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 234, in request
super(HTTPConnection, self).request(method, url, body=body, headers=headers)
File "/usr/lib/python3.9/http/client.py", line 1255, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1301, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1250, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/lib/python3.9/http/client.py", line 1010, in _send_output
self.send(msg)
File "/usr/lib/python3.9/http/client.py", line 950, in send
self.connect()
File "/usr/local/lib/python3.9/dist-packages/docker/transport/unixconn.py", line 27, in connect
sock.connect(self.unix_socket)
urllib3.exceptions.ProtocolError: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.9/dist-packages/docker/api/client.py", line 214, in _retrieve_server_version
return self.version(api_version=False)["ApiVersion"]
File "/usr/local/lib/python3.9/dist-packages/docker/api/daemon.py", line 181, in version
return self._result(self._get(url), json=True)
File "/usr/local/lib/python3.9/dist-packages/docker/utils/decorators.py", line 46, in inner
return f(self, *args, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/docker/api/client.py", line 237, in _get
return self.get(url, **self._set_request_timeout(kwargs))
File "/usr/local/lib/python3.9/dist-packages/requests/sessions.py", line 602, in get
return self.request("GET", url, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/requests/sessions.py", line 589, in request
resp = self.send(prep, **send_kwargs)
File "/usr/local/lib/python3.9/dist-packages/requests/sessions.py", line 703, in send
r = adapter.send(request, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/requests/adapters.py", line 501, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', ConnectionRefusedError(111, 'Connection refused'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/bin/docker-compose", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.9/dist-packages/compose/cli/main.py", line 81, in main
command_func()
File "/usr/local/lib/python3.9/dist-packages/compose/cli/main.py", line 200, in perform_command
project = project_from_options('.', options)
File "/usr/local/lib/python3.9/dist-packages/compose/cli/command.py", line 60, in project_from_options
return get_project(
File "/usr/local/lib/python3.9/dist-packages/compose/cli/command.py", line 152, in get_project
client = get_client(
File "/usr/local/lib/python3.9/dist-packages/compose/cli/docker_client.py", line 41, in get_client
client = docker_client(
File "/usr/local/lib/python3.9/dist-packages/compose/cli/docker_client.py", line 170, in docker_client
client = APIClient(use_ssh_client=not use_paramiko_ssh, **kwargs)
File "/usr/local/lib/python3.9/dist-packages/docker/api/client.py", line 197, in init
self._version = self._retrieve_server_version()
File "/usr/local/lib/python3.9/dist-packages/docker/api/client.py", line 221, in _retrieve_server_version
raise DockerException(
docker.errors.DockerException: Error while fetching server API version: ('Connection aborted.', ConnectionRefusedError(111,'Connection refused'))


Lots of typos in methods

there are a lot of typos e.g. retrive -> retrieve, cahe -> cache and so on...
this should be fixed with highest priority

Thanks for pointing it out. Some of them should be fixed in #3
But I cannot find "cahe" in the project.

no problem, you fixed that already in "retriveImageInMemoryCaheForKey" ;)
good job :)


fix: update internal certificate documents

Update internal certificate related document.
Note: This should only be merged after 5.4.2 is released.

should the note also be included in the version 5.3 page (versioned_docs/version-5.3/02.deploying/01.production/04.internal/04.internal.md)?

Yes we should...thanks for catching that!

@sunilarjun I've merged your suggestion into the branch with one question.  Feel free to let me know if you have any questions.  Thanks!

@sunilarjun I've updated the PR.  Please let me know if any change is still required.

@williamshen9999 please also take a look at the doc and let me know if you have any feedback.

@williamshen9999 please also take a look at the doc and let me know if you have any feedback.

Sure, I'm checking it now.

it looks good to me. thanks.


Fixed TypeError: Cannot read properties of undefined (reading 'website_id')

This error occurred when I deleted a website and went to the dashboard.
Here's a screenshot of the error.

I removed the console.log(), and added simple checks. If the website is undefined (which is an edge case anyway), it will simply fallback to 0

BTW, the dashboard completely breaks because of this single error and doesn't work even after restarting.

Ok, interestingly, deleting the umami.dashboard key from local storage fixed the issue for me


'str' object has no attribute 'tool_name'

When using a custom tool in version 0.11.2 it always throws this error. Downgrading to v0.11.1 works.
I have attached the code for anyone to reproduce this.
    'Page 1: Introduction - Introduce the topic of big data and its relevance in todays business world.',
'Page 2: Q&A Session - Reserve a slide for a question and answer session with the audience.',
'Page 3: Definition of Big Data - Provide a clear definition of big data and its key characteristics.',
'Page 4: Applications of Big Data - Discuss the various industries and sectors where big data is being successfully applied.',
'Page 5: Advantages of Big Data - Highlight the advantages and benefits of utilizing big data in business decision-making.',
'Page 6: Leveraging Advanced Technologies - Emphasize the importance of leveraging advanced technologies and tools to unlock the full potential of big data.',
'Page 7: Strategies for Managing Big Data - Provide strategies and best practices for effectively handling and managing big data.',
'Page 8: Challenges of Handling Big Data - Present the challenges and obstacles faced when dealing with large volumes of data.',
'Page 9: Conclusion - Summarize the key points discussed in the presentation and highlight the importance of utilizing big data in business.',
"""
slide_reorder_task = """A suggested reordering of slides to enhance the presentation's flow:

1. Page 1: Introduction - Introduce the topic of big data and its relevance in today's business world.
2. Page 3: Definition of Big Data - Provide a clear definition of big data and its key characteristics.
3. Page 4: Applications of Big Data - Discuss the various industries and sectors where big data is being successfully applied.
4. Page 5: Advantages of Big Data - Highlight the advantages and benefits of utilizing big data in business decision-making.
5. Page 10: Case Studies - Present real-world case studies showcasing the successful implementation of big data solutions in different companies and industries.
6. Page 11: Future Trends in Big Data - Explore the upcoming trends and innovations in the field of big data, including emerging technologies and their potential impact on business strategies.
7. Page 6: Leveraging Advanced Technologies - Emphasize the importance of leveraging advanced technologies and tools to unlock the full potential of big data.
8. Page 7: Strategies for Managing Big Data - Provide strategies and best practices for effectively handling and managing big data.
9. Page 8: Challenges of Handling Big Data - Present the challenges and obstacles faced when dealing with large volumes of data.
10. Page 9: Conclusion - Summarize the key points discussed in the presentation and highlight the importance of utilizing big data in business."""

from crewai import Agent, Task, Crew, Process
from textwrap import dedent

from dotenv import load_dotenv
from langchain_openai import ChatOpenAI
import PyPDF2

load_dotenv()

input_path = "demo1_test.pdf"
output_path = "output_path.pdf"

from langchain.tools import tool

@tool("Insert blank pages at the end of the pdf file")
def insert_blank_pages_last( input_path: str, output_path: str, no_of_pages: int) -> str:
    """
    Insert blank pages at the end of a PDF file.
    Args:
    input_path (str): The file path of the input PDF.
    output_path (str): The file path of the output PDF.
    no_of_pages (int): The number of blank pages to be added at the end of the PDF.

    Returns: str: A message indicating the success or failure of the operation.
    """
    with open(input_path, 'rb') as input_file:
        pdf_reader = PyPDF2.PdfReader(input_file)
        num_pages = len(pdf_reader.pages)
        pdf_writer = PyPDF2.PdfWriter()
        for page in range(num_pages):
            pdf_writer.add_page(pdf_reader.pages[page])
        for i in range(no_of_pages):
            pdf_writer.add_blank_page()
        with open(output_path, 'wb') as output_file:
            pdf_writer.write(output_file)
    return f"{no_of_pages} blank pages added to the last of the {input_path} PDF and saved in {output_path}."

def blank_page_agent(insert_blank_pages_last):
    return Agent(
        role='PDF Pages Adder',
        goal='Add a specific number of blank pages to the end of a PDF file. using the tool insert_blank_pages_last',
        backstory="Handles PDF modifications efficiently using the PDFPageAdder tool.",
        llm=ChatOpenAI(model="gpt-3.5-turbo"),
        tools=[insert_blank_pages_last],
        verbose=True
    )

def blank_page_task(blank_page_agent, result_list, reorder_slides_task, input_path, output_path) :
    return Task(
    description=f'Add the difference of no. of slides/pages in result of {str(result_list)} and {(reorder_slides_task)} blank pages to the end of the given PDF and save it. Input pdf path is {input_path} and the save pdf path is {output_path}.',
    expected_output = "Agent output",
    agent = blank_page_agent,
)

blank_page_agent = blank_page_agent(insert_blank_pages_last)
blank_page_task = blank_page_task(blank_page_agent, result_list, slide_reorder_task, input_path, output_path)

crew_blank = Crew(
    agents = [blank_page_agent],
    tasks = [blank_page_task],
    verbose=True,
    process=Process.sequential,
    # full_output=True
)

result = crew_blank.kickoff()
print(result)

getting the same error

Related issue #248


src/uidcache.js being ignored by git.

Makefile specifies a src/uidcache.js but the .gitignore project file is configured to ignore all js extension files except main.js and System.js

Oops! You're absolutely right, I'll add it.


Replace hoge.com with example.com

According to RFC2606, We should use example.com for documentation.
So, I replaced hoge.com with example.com.

@makky3939
thanks. :D
I merged.


update_service_status endpoint: add wait-for-index option

Similar to https://github.com/alphagov/digitalmarketplace-apiclient/pull/223, when attempting to implement https://trello.com/c/LABe8BKA it would be helpful to add these options to the actual api calls that the admin view in question uses in the first place.
So this adds a wait-for-index option to the update_service_status endpoint, which in turn will use the client_wait_for_response argument on SearchAPIClient's delete() or index() methods, depending on whether the service is being published or unpublished.

Few tests need updating but otherwise seems fine

Damn yeah missed a test.


⚠ Jenkins Plugins Artifactory has degraded performance

In 95d96d2, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 2493 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 9f09d7c after 3 hours, 11 minutes.


Add static typechecking with mypy

Closes #174

Failing tests are unrelated and due to a network error when downloading a dataset.


Create New Patch.md

4432176

test 1

https://pointloto1.com/uploads/front/img/casino/e098ac7f8c3b0439a072e3b8c06e4865_point-logo.png432216


Fix: Amazon.Workspacesclient remove broken install switches

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Did you mean to get rid of the UpgradeBehaviour?

Did you mean to get rid of the UpgradeBehaviour?

No, that was a mistake, great spot


Failed to install provider

Describe the bug
I am seeing an error when trying to download the latest version of the provider due to SHA-256.
Local
Error: Failed to install provider
│
│ Error while installing jfrog/artifactory v11.2.0: checksum list has no SHA-256 hash for
│ "https://github.com/jfrog/terraform-provider-artifactory/releases/download/v11.2.0/terraform-provider-artifactory_11.2.0_darwin_arm64.zip"

CI
╷
│ Error: Failed to install provider
│
│ Error while installing jfrog/artifactory v11.2.0: checksum list has no
│ SHA-256 hash for
│ "https://github.com/jfrog/terraform-provider-artifactory/releases/download/v11.2.0/terraform-provider-artifactory_11.2.0_linux_amd64.zip"
╵

I am seeing this within out CI platforms and also on my local. Pinning the version back down to v11.1.0 seems to resolve the issue and I am able to init just fine.
Requirements for and issue

[ ] A description of the bug
[ ] A fully functioning terraform snippet that can be copy&pasted (no outside files or ENV vars unless that's part of the issue). If this is not supplied, this issue will likely be closed without any effort expended.
[ ] Your version of artifactory (you can curl it at $host/artifactory/api/system/version
[ ] Your version of terraform
[ ] Your version of terraform provider

Expected behavior
I expect this providers version to also be working like v11.1.0 is.
Additional context
This is for a different provider, but looks like a similar error.

We are also observing this issue.

@activalexsimon @adoraisa We recently switched to the Terraform Registry Org beta program and I suspect it may be the issue. 11.2.0 is the first version to be published after migrating to the beta program. Nothing on our side with regards to the packaging or signing of the provider has changed.

Thanks for the feedback @alexhung!
Do you know when it will be resolved? Indeed, it seems like it is missing from https://releases.hashicorp.com/ (there is no terraform-provider-artifactory).

@kamilsimek-ecb Commented too soon!
HashiCorp has resolved the issue with this release. I've verified I can install 11.2.0 now.
They have also identified the issue on their side and are working on a fix.

@alexhung thank you! Confirming on my end that I also can install 11.2.0.
Appreciate it!


Multiplayer support ?

Hi,
Will there be multiplayer support for this package ?if yes, how will you handle the realtime playing mode, will sockets be used here ?
Regards

There is multiplayer support for this, as the library models a basic casino setup. You'd have to manage the implementation for your use-case, but everything is there to be used for it. We currently have it setup as a Telegram, (Slack? @xLink ) and IRC bot.


Multi source support

This is only a first draft to see if the general direction makes sense. Should already work for the file source while it is not implementeds for the others.
After some feedback and once agreed how we do it I will proceed implementing it for the rest of the sources

at a high level, does it break compatibility, and what does the "directory" structure look like?

No compatibility break, if ypu provide a single file it will work as before. When you provide a directory to KSM it will traverse recursively and create a source for every file using the correct parser so you can even use csv and yml at the same time. This will work also for the Github source for example, you can provide a directory in a respository and the source will pull all files inside the directory.

is there one API call at the directory level to see if the timestamp has changed, or do we have to do one API call by file discovered in that directory? I don't want to start overwhelming GitHub for example with API calls.
I guess this implementation will also be dependent on the source type, right?

I have to check better api wise but caching was already in my mind to minimize update time and load on the backend. The commit can be used to check if anything changed at all from last pull and I guess it's possible also to fetch a list of changed files via API.

Sure have a look - this can be done after the other PR, as it will take longer
—
Stephane Maarek
Book a call with us
https://www.conduktor.io/
--- original message ---
On May 26, 2021, 7:41 AM GMT+1 @.*** wrote:
I have to check better api wise but caching was already in my mind to minimize update time and load on the backend. The commit can be used to check if anything changed at all from last pull and I guess it's possible also to fetch a list of changed files via API.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
--- end of original message ---

I stabilized the current code (realized it was actually wrong) and implemented directory support only for the file source, does it make sense merging that one by itself and leave the rest supporting only single file for now? I can add some documentation for it and when I manage implement multi source for the other ones create another PR.
p.s. I also need still to add some tests for the multisource support in the File source.


Proposal: Add docs and/or attributes for basic mat-form-field styles

Bug, feature request, or proposal:
Proposal/request
What is the expected behavior?
You should be able to easily modify the style and layout of components inside the mat-form-field.
For example:

You should be able to add an attribute to mat-select that centers text for the entire component

You should be able to add an attribute to mat-form-field that removes the default underline and mat-select-arrow, leaving just the placeholder/value text.

The API should include documention/best practices for working with the embedded/hidden css selectors. Perhaps it makes sense to include examples or recipes for common use cases when you need to customize form field styles.

Screenshot of desired look:

What is the current behavior?
At the moment, you have to wade through the weeds of all the hidden CSS selectors and use :host to disable and manipulate these basic functions. You must read the source code for each component, figure out the CSS dependencies, and write selectors to target the individual pieces. For common things like centering text and removing default styles, this is time-consuming and limits the flexibility/creativity of using the component.
Or in other words, the styles are too opinionated at present, which will lead most apps to look the same and cause design fatigue down the road.
Screenshot of current defaults:

What are the steps to reproduce?
Providing a StackBlitz/Plunker (or similar) is the best way to get the team to see your issue.
Plunker starter (using on @master): https://goo.gl/DlHd6U
StackBlitz starter (using latest npm release): https://goo.gl/wwnhMV
I tried using the plunker, but the :host /deep/ {} selectors threw an error. Happy to submit plunker if there's a way around this.
What is the use-case or motivation for changing an existing behavior?
There should be style and alignment functions in the API for form fields. This would save a lot of time since these are common use cases.
I propose adding something like style="minimal" attribute that strips the mat-form-field of all defaults, leaving just the text/content. Could have other style presets (relaxed, dense, compact, center, left, right) and use current style as default.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
"@angular/material": "2.0.0-beta.12",
"@angular/core": "^4.4.5",
"typescript": "^2.3.4",
OS: macOS Sierra 10.12.6
Is there anything else we should know?
Maybe there's a better way of addressing this? Open to other ideas...

Removing underline is a very desirable feature when using select and input inside toolbar


Dedicated integrated medals area

Heyo, here is the same suggestion talked about here, MisfitMaid suggested I make a Git Issue, so here we are :)
Discord Post:
I brought this up with MisfitMaid, but here is a suggestion :).
Add an integrated 'medals area' where the different medals are shown.
Here is what I think would look nice, and what I shared with MisfitMaid:

I added this. It supports champion medals too.

Very nice :)


Replaced inflevels with keepbits.

Fixes #76

Hi @wntrsldr0x01,
Thank you for your interest in the project and this PR. I see that you have renamed inflevel to keepbits. The number of bits to keep (keepbits) and the information level (inflevel) are both describing how much data should be kept, but are two different concepts. Keepbits directly influences the number of bits that shall be kept and not rounded. The inflevel is an abstraction layer above. It describes the amount of information that should be preserve. Depending on region/variable/time the number of bits that need to be kept in order to preserve this information may vary. get_keepbit contains the function to transform from inflevel to keepbits.
The idea in #76 is to add an additional option to provide keepbits directly instead of inflevel. Thinking about this issue more, I would still keep the current behaviour and add the suggestion from #76 as an additional possibility to call bitround_along_dim.

Hello @observingClouds, from your comment I understood that keepbits has to be added rather than to be replaced with inflevel. My question is, adding keepbits alongside other variables here, is the only thing to do? Also is there a chat software that I can join for this repo?

@wntrsldr0x01, that's correct. Keepbits should be an additional option to inflevel. The function is called via https://github.com/observingClouds/xbitinfo/blob/a2e52325cbe21c615d722f8b2ac9845549ff92fd/xbitinfo/graphics.py#L8. The option to use keepbits should also be implemented there.
There is no chat client yet. We will try to set something up soon.

@observingClouds please take a look.

@wntrsldr0x01 please familiarise yourself a bit more with the principles and theory behind this project. The best way is probably to read and watch the linked resources on the README page and experiment with the code yourself. Maybe you have your own dataset you would like to test. This PR is just replacing inflevels with keepbits. As mentioned above, these are different concepts.

Hi @wntrsldr0x01,
I'm closing this PR for now as it does not fix the issue yet. Please feel free to reopen it or create an issue if there is something unclear in the documentation.


chore: Bump to Hugr v0.2

Closes #176

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.55%. Comparing base (73e29f2) to head (5e496a1).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #180   +/-   ##
=======================================
  Coverage   90.55%   90.55%
=======================================
  Files          41       41
  Lines        4595     4595
=======================================
  Hits         4161     4161
  Misses        434      434

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


error: 'Ping' was not declared in this scope

Hello,
Seems like I can't get the example to compile as I'm getting the following error message :
error: 'Ping' was not declared in this scope
Any idea ?
In the meantime, I've switched back to this library : https://github.com/marian-craciunescu/ESP32Ping

Hi,
have you got release 1.0.0 or 1.0.1 ? 1.0.0 have a compilation problem with windows ( not linux, who is sensitive case with files )

correct code in 1.0.1


Prerequisite updated

Prerequisites
If the AADJ machines are not inside corp network.you need a VPN solution or network infra in place to reach your on-prem DCs.

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


support add exception handler by decorator

Thanks for your interest @Zheaoli ! :nerd_face: :cake:
I'm not really sure it would help much having by default a single decorator that handles multiple exceptions that could have very different shapes and types.
If several exceptions are similar enough that they can be handled by the same decorator, I think those exceptions could inherit from the same base class, so that the decorator can handle that class.
So I'm gonna pass on this one, but thanks for your effort! :coffee:


Added files to My 'First feature branch

I set up my Linters and also added the needed files for the Hello Microverse project.

I have updated the Linter not running error. My linter.yml file was in the wrong folder.
Please @Qoosim can you explain a bit what you meant by this "Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR."


configure the amount of loaded keys

OS
Windows
VERSION
1.4.1
ISSUE DESCRIPTION
currently the first about 400keys are displayed when opening a database. On larger databases using the "load more" button loads another chunk. It would be great if there is a config option to load eg. 1000 or more keys automatically..

yeap, it will load 400 keys when the connection is opened, but it is only is a experience value, add some config option is a good way to adjust this

done, you can use this feature in the next update


[Bug]: Evaluated value and slash command dropdown get trimmed off on the property pane

Is there an existing issue for this?

[X] I have searched the existing issues

Description
On any events field of the property pane, switch to JS mode and observe the evaluated value and slash command dropdown get trimmed as seen in the screenshot
Steps To Reproduce

Drop any widget with an event field on to the canvas
Switch to JS mode and observe the evaluated value and the slash command dropdown getting trimmed off as seen in the screenshot

Public Sample App
No response
Version
Cloud

Sorry. I didn't see this issue.
Closing this since I'm already working on it on a separate issue #17079


Warp addressed transactions

ACP-73: Warp Addressed Transactions
Rendered
Abstract
Add a standard for Warp Addressed Transactions to enable any (blockchainID, address) pair to sign a a transaction that is executable on any destination chain. This is intended as a general standard that can be implemented by any VM on the Avalanche Network. As the first instance, this ACP proposes integrating Warp Addressed Transactions to the P-Chain to enable Subnet Driven Validator Sets as first laid out in https://github.com/avalanche-foundation/ACPs/discussions/68.
Diagram
To illustrate the full flow, we provide a sequence graph showing the issuance of a Warp Addressed Transaction from Account1 on BlockchainA to BlockchainB. Note that there are no restrictions on whether BlockchainA and BlockchainB are the same, different, on the same Subnet, or the Primary Network. They only need to agree on the standard for Warp Addressed Transactions.
To keep the diagram compact, we use the following abbreviations:

WAT - Warp Addressed Transaction
WAS - Warp Addressed Signature

flowchart TB
    A[Account1 on BlockchainA] -->|1. Call Warp with WAT Payload| B[BlockchainA]
    B -->|2. Accept Account1 Tx and Generate WAS| C[Relayer]
    C -->|3. Issue WAT to BlockchainB| D[BlockchainB]

Note: if the Warp Addressed Transaction can be issued entirely on its own, the relayer can be replaced by sending a cross-chain message over the network to the destination chain.
Motivation
Subnets are currently created and orchestrated entirely on the Avalanche P-Chain. Many Subnets may have the desire or need to maintain greater sovereignty over their validator set, reward curve, and overall tokenomics than what is available on the P-Chain.
Warp Addressed Transactions enable transferring ownership of a Subnet to a (blockchainID, address) pair, which can be an arbitary program on any chain in the Avalanche Ecosystem (ex. manage your validator set from a contract on your own chain or a contract on the C-Chain).
By transferring ownership to a Warp Derived Address, Subnets can manage their validator set against a generic API.
In the immediate term, this accomplishes two critical goals for Subnets:

Enable Token Standard PoS Subnets (ERC-20 Staking)
Enable generic validator set and tokenomics management

Further, this standard could be implemented by any VM that wants to enable Warp Addressed Transactions.

https://math.dartmouth.edu/~carlp/73talk.pdf

What is a "Warp Derived Address"? Can you add a definition to the ACP or a link to some docs?

Closing in favor of some variant of ACP-77


Add support for local time sensitive notifications

Since iOS 15, iOS has had support for Time Sensitive PNs. This PR adds support by adding an optional isTimeSensitive boolean to the NotificationRequest type.
Happy to hear what the maintainers think :)
https://www.howtogeek.com/751563/what-are-time-sensitive-notifications-on-iphone/
https://developer.apple.com/documentation/usernotifications/unnotificationinterruptionlevel/timesensitive

3 months and no response from the maintainers 😬 . Closing this PR.


Implement function to standardize_water

This implement a function to solve the problem brought up in #253 . Currently it's a separated function packmol.standardize_water that can optionally be called on a water molecule to standardize its residue/atom names and make MDTraj automatically perceive bonds. Right now I preferred this to making it all automatic and hidden inside packmol.pack_box because

It'd involve loading as a Trajectory object every molecule before invoking packmol to check if it is a water.
I'd prefer packmol.pack_box to not have unexpected side effects on the output files.

We can always integrate the two functions later if we notice significant advantages. Currently this is how it works
>>> water_traj = mdtraj.load('water.pdb')
>>> is_water = packmol.standardize_water(water_traj)
>>> packmol.pack_box([water_traj, 'benzene.pdb'], [1000, 1])

I wonder if this should eventually go into mdtraj. It would seem that it should be easy to recognize water molecules and (optionally) standardize their naming if desired.

Maybe the pack_box documentation should be updated to note the potential use case for this function, however?

Will do!

I wonder if this should eventually go into mdtraj?

I agree, I'll raise an issue on their tracker pointing to this.

Thanks, should be good to merge once tests pass.


2926: Fallback language in search function

Short description

When your app is set to e.g. English and you look for a German term that you got a letter about like "Bürgergeld", you get zero results because we only search for English results. This PR adds a fallback language (the one that we translate from, i.e. German), so in this case, if there are no results in English, we then look in German.
The feedback screens have not been updated yet, that will be a separate ticket.
Proposed changes

Also load all possible search results in the fallback language
The search stays in the app language, if there are results. If there are no results, we search through all the possible results in the fallback language.

Side effects

The behavior when following a link from the fallback language is different in web and native:

In web, you open the link in the fallback language and are then in the app in the fallback language. If you use the browser history, you can go back to the selected language
In native, you open the link in the fallback language in the inAppBrowser. When you close that, you're back in the app in the selected language.

Testing

You can switch the app to English and search for "alleinerziehend".
Resolved issues

Partially fixes: #2926

The feedback screens have not been updated yet, that will be a separate ticket.

Does this issue already exist? Could you please link it here? Thanks :)


PyLance does not appreciate @serializable.serializable_class

Inadvertantly opened this ticket half way through writing the subject.
PyLance thinks that serializable.serializable_class decorated classes are untyped.  I'm unsure if there is a proper way to resolve type based issues.  The "fix" seems to be to have one undecorated class and one decorated class that references the former: i.e. "MyThing" and "SerializableMyThing" in order to allow for casting in individual programs.
Looking forward to some insight on this.  CycloneDX-Python-Lib makes use of this library and it can be a bit cumbersome to work with classes provided by that library.  Attempting to cast falls into the same trap.

Checking in on this to see if this is a patches welcome situation or if the CycloneDX Python Lib is considering another serializer.

Hi, I am the current maintainer of CycloneDX Python Lib.
The situation is the following: I'd love to use another serializer in CycloneDX Python Lib, but I do not have the time to work on this topic at the moment.
I also gained maintainer privileges on this very library here, too.
This brings us to the situation where patches are welcome, @whardier  :-)


Remove all emojis from names of the richest list

Proposal:
Proposal written by Monkeyyy11
Is it a proposal for the website or for the bot?: bot
What is the title of your proposal?: Remove all emojis from names of the richest list
Explain your proposal more accurately (It's best to give as much information as possible, so that we can implement the proposal better): The ?richest list is buggy due to the users who have an emoji in their name: https://i.imgur.com/N6mqaK0.png
Why should we add this feature?: It would be consistent
ReportID: 168

➤ LenoxBot commented:
Approve:
good suggestion
Dadi#7808

➤ LenoxBot commented:
Approve:
not only richest, but every toplist
Profxy#5396


Fixing issue #788 where resourceGroup was not passed into environment…

…Name or set to the value of the output variable

Hi @hrboyceiii, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

Hey hrboyceiii,
current could should answer issue #788.
This PR will break the scenario where - you created an Azure Resource Group with name "azureRGName" and save it as an output variable with name "outputEnvName". You want to use it in PowerShellOnTargetMachines task by referring to it as "$(outputEnvName)".
What is the exact problem you are trying to solve?

Right now, if I specify an value for output variable, the task fails on Register-Environment in Utility.ps1 (line 383, see attached log file).  My understanding is that $outputVariable will store the machines from the resource group which I can then pass into subsequent tasks, like PowerShell on Target or Visual Studio Test Agent deployment.
Either way, when I use this task today using a hosted agent with the a value specified for output variable, it fails with the attached error.  The fix in the PR makes Register-Environment work.
How should these tasks be used??  Including @pryenugu who's helping with a similar issue (#969) with the Test Agent Deployment task.
tasklog_2.txt

@hrboyceiii
These tasks have a dependency on latest agent while using Register-Environment.
But hosted agents are not yet updated - should be updated sometime this week.
That is the reason for the failure message you are facing. Though the code changes you sent in PR fix the error message - they doesn't fix the functionality.
Thank you for the contribution.
I will get back to you once the hosted agent upgrade is done. Until then can you try with a private agent?
And regarding issue #969 - Deploy test agent task doesn't yet support consuming machine groups output by another task.

@hrboyceiii  hosted agents were upgraded last week.


Internal mask support

MRF currently supports mask via PAM, as external files.  The external mask doesn't work through caching or cloning MRFs, it is ignored.
MRF should support a mask internal to the tile, at least for the JPEG compression format, which works through caching or cloning MRFs.

Added Zen mask mechanism

MRF with JPEG compression contain the Zen extension.  The extension has been tested and seems to function as designed.  See updated documentation.


Update Kube Config directly from Java

Actually this might be not needed, since for now we use kubectl anyways for checking if the API Server started / up and running (by checking if the default namespace is present or not)

will do it for now with kubectl


Queries against Redshift very slow

System information:

macOSX 11.6 (Big Sur)
DBeaver 21.2.1

Connection specification:

Connecting to a Redshift cluster

Describe the problem you're observing:
I'm querying an external schema with a simple select; it seems like the rows are fetched quite quickly but then the client sites there for several minutes doing something. For example, in the results shown below, I don't see the results materialized for several minutes (~2 min) although it tells me it fetched rows very quickly

Running a similar query in table plus, against the same table, almost instantly returns results.
I'm noticing the same thing for "standard" Redshift table as well (i.e. they are not Glue tables mounted as an external schema).

@ConstantinoSchillebeeckx Hello, can you look what background process is happening until the table is displayed? You can enable background tasks window with Window > Show view > Other > Background tasks
Also queries from the query manager can be useful too

Here's a gif of the behavior showing both Background tasks and the Query manage

that's how I'm opening them in the GIF (e.g. "Read data in SQL editor")

@ConstantinoSchillebeeckx Sorry, I meant does it that long to open in data editor too (double-click on the table or selecting a table and pressing F4)

there is no update on the issue for a long time. If it is still actual for you - feel free to reopen it with additional info.


Import Attributes (Stage 3)

Suggestion
🔍 Search Terms
import attributes, import assertions, esnext
✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
https://github.com/tc39/proposal-import-attributes
In January 2023, Import Assertions proposal was demoted back to Stage 2 to investigate a solution for the web platform's needs. In March 2023, the proposal was renamed to Import Attributes and moved back to Stage 3 (with conditional consensus - pending spec text review).
TypeScript should support the new syntax. The most relevant change for TypeScript is that the keyword changed from assert to with.
import json from "./foo.json" with { type: "json" };

import("foo.json", { with: { type: "json" } });

export { val } from './foo.js' with { type: "javascript" };

The minimal option here is just to add the with syntax. Ideally there would also be two enhancements:

Deprecating assert: For compatibility with existing implementations, the assert keyword is still allowed by the spec until it's safe to remove it. Chrome will explore removing it.  Babel is deprecating the syntax with a plan to eventually remove it in Babel 8. TypeScript could follow something similar to the 5-release deprecation process by initially suggesting migration via warnings and quick fixes - though we recognise that the deprecation process was originally intended only for flags.
Auto-complete for static import/re-export declarations: Auto-complete seems to be only working with dynamic import() right now. This could be expanded to also work for attributes in static declarations.

📃 Motivating Example
This will be new ECMAScript syntax so motivation is to be compatible with the language. The champion group considers this to be stable, even though it just changed: this is what re-promoting to Stage 3 represents.
It sounds like this would also unblock https://github.com/microsoft/TypeScript/issues/49055#issuecomment-1485768138.
💻 Use Cases
https://github.com/tc39/proposal-import-attributes#motivation
In addition, we have an internal use case in Bloomberg to use Import Attributes as an annotation to achieve lazy-loading by deferring module evaluation.  This is an early implementation of the TC39 proposal for Deferring Module Evaluation.

This issue is raised only for awareness. At this point we are not planning to implement.

Given the Stage 3 -> 2 regression on the original proposal, we might hold off on this until it's more like Stage 3.5

Regarding the stability of the proposal, the reason we changed the proposal so much after Stage 3 was because we found problems integrating it with the web platform. We reached broad consensus on the current semantics, which mach what HTML folks needed from the proposal.
You might have noticed that this "back to stage 2 and again to 3" dance has been very quick (3->2 in January, and 2->3 [^1] in March): it's because engines were very eager to ship this proposal, and we had to solve its problems very quickly. I would expect import attributes to be available in browsers very soon.
There is only one part of the proposal around which there is uncertainty: what will happen to the assert keyword. We know that the main syntax will be with, but we don't know yet if we'll be able to completely remove assert. For this reason, while I think implementing with is completely safe and it's the best way to help the ecosystem migrate quickly, I would recommend waiting before deciding what TS should do about assert. For reference, if it will remain in the spec it will be with this disclaimer (https://github.com/tc39/proposal-import-attributes/pull/133):

A conforming implementation of ECMAScript should not implement Deprecated subclauses, unless necessary for compatibility with existing applications that already run in such implementation before the deprecation of the given language feature. All of the language features and behaviours specified within Deprecated subclauses have one or more undesirable characteristics. However, their usage in existing applications currently prevents their removal from this specification. These features are not considered part of the core ECMAScript language. Programmers should not use or assume the existence of these features and behaviours when writing new ECMAScript code.

[^1]: Technically the proposal is not at Stage 3 yet, but it will be officially at Stage 3 as soon as its spec text is reviewed. We are working quickly on this, and you can track progress at https://github.com/tc39/proposal-import-attributes/issues/137

Given that import attributes actually do influence resolution, would we have to specify more semantics based on the moduleResolution option?

Import attributes can influence module resolution, but the currently planned attributes (i.e., just type in Node.js/web) do not. The TypeScript implementation of import attributes I expect is to just add the with keyword as an alias to assert, without actually changing any semantics.
However, if for example one day Node.js implements an attribute that does affect module resolution, I would expect TS's moduleResolution: "node16" to automatically support it.
Additionally, the paths option could be extended in the future to allow mapping (specifier,attributes)->resolved instead of just specifier->resolved (it might not be a good idea, but the proposal allows it).

Although it could be useful to consider as a follow-up to have some support for with specifiers in declare module, so the following would be possible:
declare module '*' with {type: 'x-url'} {
  const url: string;
  export default url;
}

Is it required to continue to support the assertClause property?
https://github.com/microsoft/TypeScript/blob/ac55b297b755131af0388327e8115467c982c04b/src/compiler/types.ts#L3673
https://github.com/microsoft/TypeScript/blob/ac55b297b755131af0388327e8115467c982c04b/src/compiler/types.ts#L3709-L3714
https://github.com/microsoft/TypeScript/blob/ac55b297b755131af0388327e8115467c982c04b/src/compiler/types.ts#L2178
Or can the assertClause property be replaced (as a Breaking Change) by the attributes property?
export interface ImportDeclaration extends Statement {
    ...
    readonly attributes?: NodeArray<ImportAttribute>;
    // readonly attributes?: ImportAttributes; ?
}

Could someone, please clarify if this change in terminology from assertions to attributes is correct or if I have misunderstood something?

I think we could possibly mark assertClause as deprecated and add a shim that redirects to attributes for some number of TypeScript versions. Similarly, AssertClause could be an deprecated type alias to ImportAttributes.

(@rbuckton probably has opinions here though)

We'd love to support using import attributes in Bun in both the bundler and the runtime for things like:
// return a Uint8Array
import placeholderBytes from './placeholder.png' with {encoding: "binary"};

// return a data:image/png;base64, as a string
import placeholderUrl from './placeholder.png' with {encoding: "base64url"};

We have implemented parser support (through the transpiler, not in JSC) for the with keyword similarly to assert. But probably nobody will use it until other tools (TypeScript, Prettier, eslint) can parse it without reporting a syntax error. It would also be nice to be able to add types for this.

@nicolo-ribaudo can we get a clarification on the official status of the proposal? I noticed https://github.com/tc39/proposal-import-attributes/issues/137 is closed with all boxes checked, but https://github.com/tc39/ecma262/pull/3057 is still getting review activity.

Remaining review items are just editorials about spec wording, the semantics are settled :) (unless there is significant implementation feedback, like for any stage 3 proposal)

Are those review items pending stage 3, or is the proposal officially stage 3 and those review items are pending stage 4 / acceptance into the final spec?

Officially stage 3, the editors approved the current spec 👍

I think we could possibly mark assertClause as deprecated and add a shim that redirects to attributes for some number of TypeScript versions. Similarly, AssertClause could be an deprecated type alias to ImportAttributes.

We can probably just mark it as deprecated and set it for both properties until some future time where we remove it in a major release. If we want to remove it sooner we could use Object.defineProperty to attach a getter that reports a deprecation warning.

We can probably just mark it as deprecated and set it for both properties until some future time where we remove it in a major release.

@rbuckton Does that mean the implementation for assert (parser/types/tests etc.) should be preserved, and with should be added as a new feature without changing the behavior of assert? Or should assert be replaced by with (with has differences in implementation), with deprecated errors (parser/checker)/API aliases/JSDoc deprecations?

with has differences in implementation

Are you talking about the runtime implementation, or the TypeScript compiler implementation?
Until everyone has moved off of assert, we need to preserve how assert is parsed as well as also support with, though we should probably report an error when using the assert syntax. The AST node should continue to have the existing assertClause property, but marked as /** @deprecated */. The NodeFactory should be able to take either an assert clause or a with clause. We may even want to report a deprecation warning to the console when you use NodeFactory methods that produce or update an AssertClause, or when one is provided to a factory method, but only if we can find a way to do so for only custom transformations or API use (i.e., don't report from tsc or the language service when the compiler uses them regularly, since we'll report normal diagnostics in those cases).


Can't get videojs-chromecast to load

I'm not a js expert but I think I have this loaded correctly. Compiling with webpack.
import videojs from 'video.js';

require('@silvermine/videojs-chromecast')(videojs);

document.addEventListener('DOMContentLoaded', function() {

    var options = {
       controls: true,
       fluid: true,
       techOrder: [ 'chromecast', 'html5' ],
           plugins: {
            chromecast: {
                preloadWebComponents: true,
                addButtonToControlBar: true,
            },
        }
    };

    var video = videojs('livestream', options).ready(function(){
      var player = this;
      getNextSource(player);
      player.on('ended', function() {
        getNextSource(player);
      });

      player.on('error', function() {
        getNextSource(player);
      });
    });
//Rest of the file
});

Then I'm loading on page with two script calls.
<script src="/js/video.js"></script>
<script type="text/javascript" src="https://www.gstatic.com/cv/js/sender/v1/cast_sender.js?loadCastFramework=1"></script>

Video plays and everything is good but I'm not getting the chromecast button and the built in chromecast option isnt working either.
I can cast from other sites, so I know its not a local issue.
Any help would be appreciated.

Hey sory @alexhackney, but I don't see anything that jumps out at me as being wrong. Maybe one of the other developers will see something, but I don't. I'll close the issue for now, but if you're able to create a reproducible codepen, or you have additional info about errors in the console or something, leave a comment.

@alexhackney do you resolve your problem? I'm in the same truoble.. :-(

@alexhackney do you resolve your problem? I'm in the same truoble.. :-(

I did. It's all in the setup. I can share it with you later, just dont have it on this machine.

I did. It's all in the setup. I can share it with you later, just dont have it on this machine.

@alexhackney Hello Alex, I believe I'm having the same issue. Could you please share how did you manage to solve it?

I did. It's all in the setup. I can share it with you later, just dont have it on this machine.

hey @alexhackney I also have the problem, and like wkhira I still believe you got the answer to this issue, do you have it please ?


Cannot install the application in APEX 5.0.3

I tried to install the app and getting below error.
•NOT COMPATIBLE (Your export may contain calls not supported by your application version.)
Appreciate your help.

The last APEX 5.0.x compatible version was <IP_ADDRESS>: https://github.com/vincentmorneau/material-apex/releases/tag/v<IP_ADDRESS>
I suggest you upgrade to APEX 5.1 to benefits from newer features and bug fixes.


Incorrect dragged element position when window scrolled

To reproduce:

select element
scroll window (by scroll wheel or keyboard)
try to move element
result: other elements moves like if you didn't scroll
screens to reproduce:
http://joxi.ru/L210W96F8RvW0m -> http://joxi.ru/krDOqLzcEKw3QA -> http://joxi.ru/Dr863dRF4ody62

To addition, lockToContainerEdges doesn't work if you scroll window

+1

@uditalias I use Alt. Usually components that use SortableContainer or Element are wrapped in @connectToStores

For what it's worth: I'm seeing something similar with a Redux-wrapped component using react-sortable-hoc. Can try to provide more details if you're interested.

you can reproduce it here https://clauderic.github.io/react-sortable-hoc/#/basic-configuration/basic-usage?_k=62gk8p

I'm having the same issue.

Also just ran into this. @clauderic I'm willing to help out on this. Any guidance you could give on how we would need to approach solving this?

@dsvgit @uditalias @kohlmannj @Ghostavio
Got this working using the getContainer prop (alternatively use the useWindowAsScrollContainer prop) to connect it to the proper scroll container and it works exactly as it does in the demo.


扫描测试APP提示报错

报错信息
\APKDeepLens-main\app_source\com.thewalleyapp.apk\resources\AndroidManifest.xml' at line 202
截图

Hello @xiaopingDU1993 can you tell which version of jdk are you using?


restart endpoint does not need to be enabled when refresh is used by …

…default fixes gh-402
PR is resubmitted as the earlier one was polluted with other commits.

@Haybu Can you submit the fix against the 1.0.x stream so we can get it in greenwich?


FluentButton does not allow to set preventDefault for onclick event

🐛 Bug Report
How can options like preventDefault can be set for the onclick event on FluentButton?
💻 Repro or Code Sample
<button type="button" @onclick="() => {}" @onclick:preventDefault>Click</button>
This works as expected.
<FluentButton Type="ButtonType.Button" @onclick="() => {}" @onclick:preventDefault>Click</FluentButton>
Results in "error RZ10010: The component parameter 'onclick' is used two or more times for this component."
🤔 Expected Behavior
It should be possible to set these options.

The @onclick:stopPropagation and preventDefault directives only work on HTML DOM elements. See also https://learn.microsoft.com/en-us/aspnet/core/blazor/components/event-handling?view=aspnetcore-8.0#stop-event-propagation
If you would try this on a standard Blazor component, you will get the same error:
<InputText @bind-Value="@YYY" @oninput="XXX" @oninput:stopPropagation=true />
gives
RZ10010	The component parameter 'oninput' is used two or more times for this component. Parameters must be unique (case-insensitive). The component parameter 'oninput' is generated by the '@oninput:stopPropagation' directive attribute.

But is there a workaround that?
@vnbaaij

Hello @vnbaaij
I am trying to build a tree which Add Tree Node button in it.
This is my code that is currently working:
<FluentTreeView>
    @foreach (var group in _groups)
    {
        <FluentTreeItem>
            <FluentIcon Icon="Icons.Regular.Size20.Folder" Slot="start" Data="group"/>
            @group.Name
            @foreach (var item in group.items)
            {
                <FluentTreeItem Data="item" AdditionalAttributes="@(new Dictionary<string, object>() { {"parent", group} })">
                    <FluentIcon Value="@(new Icons.Regular.Size20.Check())" />
                    @item.Name
                    <FluentIcon Value="new Icons.Regular.Size20.Delete()" OnClick="() => OnDeleteitem(group, item)" />
                </FluentTreeItem>
            }
            </FluentTreeItem>
        </FluentTreeItem>
    }

    //Add item node button
    <FluentTreeItem @onclick="() => _isAddingGroup = true"> //Change the state to adding if the fluent tree item is clicked
        @if (_isAddingGroup) // If the state is adding, show the input field and buttons
        {
            <FluentTextField Placeholder="item group name" Value="@_newGroupName" ValueChanged="(newValue) => _newGroupName = newValue" Style="width:100%;" /> // Input field for the group name
            <button @onclick="AddGroup" // In the add group button I set the state of _isAddingGroup to false.
                    @onclick:stopPropagation="true">    // Stop the event from propagating to the parent node otherwise the state will be changed to adding
                <FluentIcon Icon="Icons.Regular.Size20.Add" />
            </button>
            <button @onclick="(args) => _isAddingGroup = false"
                    @onclick:stopPropagation="true">
                <FluentIcon Icon="Icons.Regular.Size20.Delete" />
            </button>
        }
        else // Else show the add group button
        {
            <FluentIcon Icon="Icons.Regular.Size20.Add" />
            @("Add group")
        }
    </FluentTreeItem>
</FluentTreeView>

I create a node with an Icon and text "+ Add group"
I save state, if the node is clicked I set the state "_isAdding = true"
Than I show the input field + Add or Dismiss button.
When one of the buttons is added I set the state to "_isAdding = false" than I display back the "+ Add group" button.
I need to stop the propogation otherwise the OnClick event on the tree is always triggerd and the state is always set to ""isAdding = true"

With the FluentButtons I can't stop the propagation.
Two questions here:

Do you have any better idea how to implement this (I am trying to skip the RenderFragment option).
If there is no better idea how can I set the CSS of the given buttons to match the FluentButton css?

Thanks for the help in advance.


feat: isomorphism between the non-divisors and units of a group with zero

From FLT

bors merge


I would like to feedback some of the confusion I have encountered with this mod.

I have been very fond of your mod since I came into contact with this game last year.
I would like to feedback some of the confusion I have encountered with this mod.
How is the BOSS health calculated? When two people are online, the level 80 ogre has more than three million health points, which seems to be an impossible challenge to complete. Another problem is that the boss's health bar only shows a small part, and you need to finish the black part of the health to show the health change. Since my native language is not English, I hope the expression did not confuse you. Thank you and look forward to your clarification.

Thank you for your comments, as you know it is a pre-release and may contain bugs.
It seems that you have found one with the boss's life.
I'll check it out and tell you something ;)
By the way, what is your native language? I am from Spain and if it is Spanish you can write to me in Spanish.

Thanks for your response, my VRising community and I really enjoyed your mod, which fleshed-up the gameplay later in the game and the poor resource acquisition of the original. Looking forward to your mod.
In addition, I am sorry that my mother tongue is Chinese, so sometimes I use a translator to express myself, hoping that the expression will not be offensive.
Praise MODDER!
------------------ 原始邮件 ------------------
发件人: @.>;
发送时间: 2024年5月16日(星期四) 晚上11:51
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [oscarpedrero/BloodyBoss] I would like to feedback some of the confusion I have encountered with this mod. (Issue #1)
Thank you for your comments, as you know it is a pre-release and may contain bugs.
It seems that you have found one with the boss's life.
I'll check it out and tell you something ;)
By the way, what is your native language? I am from Spain and if it is Spanish you can write to me in Spanish.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


The update squirrel should not be colored for release notes

The little squirrel icon that appears when there is an update it's perfect.
But it's coloured even when there is no update but just to point you to the release notes. I find this behaviour confusing.
I think it should act as follows:

Coloured when there is an update to install
Gray when it's there to point you to the release notes

This makes a lot of sense.

It should be a very simple addition, but CoffeeScript gives me headaches :)

Closed my other issue. The squirrel showing blue after installing updates bugs me too.
I think it only needs the blue state to get you to update (no gray). I'm going to read the release notes when clicking install + restart, so I wouldn't want the icon always present (less UI distraction). You can always access them from the "help" menu.

+1

Agreed with the above, the blue squirrel is distracting when it only points to release notes (which I've already read anyway).

Out of curiosity, would this squirrel be in the main Atom repo or would it be under the status-bar repo? I'm guessing the update logic is in the Atom repo, with an interface to update the status-bar?
I'm curious to try working on this. Thanks!

@bj7 Actually, the squirrel icon control is in the about package. But we don't display the release notes in Atom anymore. We link out to the latest release on GitHub in the About view. Ultimately, this Issue has been fixed.

Oh ok then. Thank you for the info!

@bj7 You're welcome! Sorry to snipe something interesting out from under you. If you need help finding something interesting to contribute with, feel free to message me on the Atom Slack.

Ok thanks!

I'm curious why does atom use squirrel? Does it mean something ? :)

@Yanpas From https://www.quora.com/GitHub-What-is-the-significance-of-the-Ship-It-squirrel by @jglovier:

Shipping is central to the work culture at GitHub. Everything in our workflow is focused around shipping early, and shipping often. We literally deploy http://github.com the website dozens of times a day. Shipping is the point of everything we do.
We also like to have fun with everything we do, so the Ship It Squirrel is just an extension of that attitude. We use the :shipit: emoji in Pull Request threads to signify support for someone's pull request when we feel it's ready to ship, or in other internal communication to indicate support for getting a feature staff shipped or into production.


Undefined method 'merge' for empty hash

# works
present :aggregations, []

# raises an <NoMethodError: undefined method `merge' for :aggregations:Symbol>
present :aggregations, {}

"Framework Trace": [
      {
        "exception_object_id":<PHONE_NUMBER>2700,
        "id": 0,
        "trace": "grape (1.2.4) lib/grape/dsl/inside_route.rb:332:in `present'"
      },
      {
        "exception_object_id":<PHONE_NUMBER>2700,
        "id": 2,
        "trace": "grape (1.2.4) lib/grape/endpoint.rb:57:in `call'"
      },
      {
        "exception_object_id":<PHONE_NUMBER>2700,
        "id": 3,
        "trace": "grape (1.2.4) lib/grape/endpoint.rb:57:in `block (2 levels) in generate_api_method'"
      },
      {
        "exception_object_id":<PHONE_NUMBER>2700,
        "id": 4,
        "trace": "activesupport (6.0.0) lib/active_support/notifications.rb:182:in `instrument'"
      },
      {
        "exception_object_id":<PHONE_NUMBER>2700,
        "id": 5,
        "trace": "grape (1.2.4) lib/grape/endpoint.rb:56:in `block in generate_api_method'"
      },
      {
        "exception_object_id":<PHONE_NUMBER>2700,
        "id": 6,
        "trace": "grape (1.2.4) lib/grape/endpoint.rb:263:in `block in run'"
      },
      {
        "exception_object_id":<PHONE_NUMBER>2700,
        "id": 7,
        "trace": "activesupport (6.0.0) lib/active_support/notifications.rb:182:in `instrument'"
      },

I've made a temp solution:
present :aggregations, search.aggregations, with: GrapeHashSerializer

# frozen_string_literal: true

class GrapeHashSerializer
  def self.represent(hash, *)
    hash
  end
end

What's the stack for this error?
Try writing a unit test in Grape?

For future searchers, the issue here is that present :x, {} treats the {} as a set of options, so instead of :x being the key and {} being the object, :x becomes the object.
Quick fix if you need to explicitly present an empty object is present :x, {}, {}.


Switching to stable chefdk release since there is a bug in chef 12.18…

… that is preventing tests
Signed-off-by: Scott Hain<EMAIL_ADDRESS>THIS PR SHOULD BE REVERTED AND SWITCHED BACK TO current once the bug in chef 12.18.x is fixed. (Will update with bug # later)

@schisamo resolved
@jaymalasinha feel free to merge this tomorrow once Seth has finished his review


Split up and test Package and PackageItem

What's the deal with Package and PackageItem

Problem
These classes are a bit of a mess. The APIs are not clear, they don't do what you think they'd do, they have implicit behaviour, they're mostly untested, and we have no confidence in changing them.
Solution
Split the class out into its own file. Test the specs as they exist.
 I'm not changing any behaviour. Just asserting the raises and skipping the tests. If the tests stop raising they'll then fail.
This lets us pull out Quantified and replace with measured as in #434. This is really just a first step in that refactor.
Note: I wrote so many tests you may have to click View Diff because the last file with 400+ lines is collapsed.
@jonathankwok @mdking @thegedge

A first step toward #427 in 2.0


Get unread messages and mentions for the current team

Summary
Adds a selector to get the unread messages and mentions for the current team only

No unit test?

@jwilander done


Label not visible in light theme

Label is not visible in light mode, but in dark it's correct
"version": "1.0.3",
Updated: Label can visible if you change your theme to dark and change again.. otherwise it's like image

Legend label can be visible if given like below, sorry for inconveniences
'legend' => [
    'labels' => [
        'colors' => '#9ca3af',
        'fontWeight' => 600,
    ],
],