avahi-daemon not running

I started the daemon with docker using the same command line from the readme.md. When I try to access any kind of option in the control panel I get 500 Server Error. I checked the logs and I saw this:
Unable to communicate with avahi-daemon: Daemon not running
I'm using Debian (open media vault).
Docker version 18.09.4, build d14af54
Kernel: 4.19.0-0.bpo.2-amd64
Connected printer is a Samsung SCX-4200.

When I try to access any kind of option in the control panel I get 500 Server Error.

How did you performed this?
Did you docker exec cloudprint configure open before trying to configure something?

Yes I did. Maybe it's because OMV is already running avahi on the host?.

Docker purpose is to isolate so, no matter if avahi is running or not on the host.

How are you trying to configure your container?

I first tried using a docker-compose configuration based on your docker run line:
docker run -d --privileged --restart=always -v /dev/bus/usb:/dev/bus/usb -v "$HOME/.cloudprint/":/root --name cloudprint -e CUPS_USER_ADMIN=admin -e CUPS_USER_PASSWORD=password -p 631:631 jaymoulin/google-cloudprint
version: '2'

services:
  cloudprint:
    image: jaymoulin/google-cloudprint
    container_name: cloudprint
    restart: unless-stopped
    privileged: true
    volumes:
      - /dev/bus/usb:/dev/bus/usb
      - ${CLOUDPRINT_CONFIG}/cups:/etc/cups
      - ${CLOUDPRINT_CONFIG}/credentials:/root
    environment:
      CUPS_USER_ADMIN: admin
      CUPS_USER_PASSWORD: ${CUPS_USER_PASSWORD}
    ports:
      - 631:631
    labels:
      - "traefik.docker.network=main"
      - "traefik.enable=true"
      - "traefik.basic.frontend.rule=Host:printer.${DOMAIN_URL}"
      - "traefik.basic.port=631"
      - "traefik.basic.protocol=http"
    networks:
      - main

networks:
  main:
    external: true

The image didn't start (it died exiting with code 0). So I removed the container and started using the readme line (docker run...). Image starts, control panel starts, but log shows avahi is not running.

avahi is not required. It's only a service to provide DNS but you don't need it.
If your control panel starts, then you don't have any problem :)

Yes, but I'm getting 500 server error on every page.

Cupds official documentations says it could be due to your rights (https://www.cups.org/doc/man-cupsd-logs.html)
Could you check your volumes are created with correct rights? (cups user in this docker image is root by default)

Just one volume is created:
drwxr-xr-x  2 root root 4096 May 26 13:11 .cloudprint
Rights look ok to me, owned by root and was created by the container, so container is running on root.

log shows the following:
E [26/May/2019:16:56:56 +0000] Unable to open listen socket for address [v1.::1]:631 - Address not available.
E [26/May/2019:16:58:08 +0000] Unable to communicate with avahi-daemon: Daemon not running

Do you have a cupsd already running on your host?

Do you have a cupsd already running on your host?

Nope. cupsd is not running, not even installed

You can "connect" to the container the check what you want with docker exec -ti cloudprint sh. You'll probably find logs in /var/log/cups

I did,
/var/log/cups # cat error_log
E [26/May/2019:17:08:34 +0000] Unable to open listen socket for address [v1.::1]:631 - Address not available.
E [26/May/2019:17:10:34 +0000] Unable to communicate with avahi-daemon: Daemon not running

Looks like something related to ipv6?.
https://www.linuxquestions.org/questions/slackware-14/disabling-ipv6-seems-to-break-cups-4175518566/

Your link is from 2014 and their clues are based on a previous revision (https://github.com/apple/cups/issues/4305). BTW, cupds configuration files in the docker image are set to use ipv4.
Could you try creating the container without the .cloudprint volume?

I'm sorry, but same issue :/

When I execute docker exec cloudprint configure open the container stops running, is that normal or something is not working correctly?. With the restart always flag I didn't noticed it, but now I deleted the flag and I have to manually start the container.

When I execute docker exec cloudprint configure open the container stops running, is that normal or something is not working correctly?. With the restart always flag I didn't noticed it, but now I deleted the flag and I have to manually start the container.

It's the expected behaviour as cupds needs to be restarted to handle its new configuration

Okay, now:

No volumes, not even /dev/bus/usb
No --privileged flag

Same Internal server error.

Hmm, tested the image on my VPS server running Ubuntu 16.04 LTS and it's working. Obviously I don't have a printer there but CPanel loads ok.
So It's something with my local NAS that the container doesn't like. Unfortunately there is no log.

The log on the VPS it's exactly the same as in the NAS. The mystery deepens.

Your VPS and your NAS must have different architectures and probably use different docker image. You should be able to determine this with this command : docker inspect cloudprint --format='{{index .Config.Labels.version}}'

NAS:
0.4.3-amd64
VPS:
0.4.3-amd64

Got it, using LogLevel debug the error is not obfuscated anymore.

D [26/May/2019:18:35:17 +0000] [CGI] Started /usr/lib/cups/cgi-bin/admin.cgi (PID 15)
I [26/May/2019:18:35:17 +0000] [Client 1] Started "/usr/lib/cups/cgi-bin/admin.cgi" (pid=15, file=10)
D [26/May/2019:18:35:17 +0000] [Client 1] Waiting for CGI data.
D [26/May/2019:18:35:17 +0000] [CGI] execv failed: Permission denied
D [26/May/2019:18:35:17 +0000] PID 15 (/usr/lib/cups/cgi-bin/admin.cgi) stopped with status 113 (Permission denied)
D [26/May/2019:18:35:17 +0000] [Client 1] CGI data ready to be sent.
D [26/May/2019:18:35:17 +0000] [Client 1] con->http=0x55f670144340
D [26/May/2019:18:35:17 +0000] [Client 1] cupsdWriteClient error=0, used=0, state=HTTP_STATE_GET_SEND, data_encoding=HTTP_ENCODING_LENGTH, data_remaining=2147483647, response=0(), pipe_pid=15, file=10
D [26/May/2019:18:35:17 +0000] [Client 1] Waiting for CGI data.
D [26/May/2019:18:35:17 +0000] [Client 1] cupsdSendHeader: code=500, type="text/html", auth_type=0
D [26/May/2019:18:35:17 +0000] [Client 1] Waiting for request.
D [26/May/2019:18:35:17 +0000] [Client 1] Closing because Keep-Alive is disabled.
D [26/May/2019:18:35:17 +0000] [Client 1] Closing connection.

Should resolve your issue : https://stackoverflow.com/questions/32462340/cups-permission-denied.
Seems this is not related to the image, I can't fix anything

But /usr/lib/cups/cgi-bin/admin.cgi it's inside the image and already has root ownership. Why it's giving permission denied when it has root permissions on everything

It's still giving me permission denied. Doesn't make any sense. I already did:

id -u --> 0
chown -R 0:0 /usr/lib/cups

Nothing, still error 113.

I'm giving up. Same issue with this image: https://github.com/thbe/docker-cups

Ended up installing CUPs outside Docker and using a GCP Connector image. It was not the intended solution but given that I can't make CUPs work with Docker, it's the best I cloud achieve.


Make errors more descriptive/provide descriptions

I just scanned a webproject we made and I can see a lot of errors like

this makes me think of why is the x-xss-protection header not needed? in the first place its a security header and its not obvious why I should not use them (or maybe its a more complex context here which I dont know about and needs explanation?)

@staabm For ever error, there is a documentation link that should provide all the information related to that specific test (e.g.: for x-xss-protection header not needed)

@staabm Do you think this is not obvious enough? If you have any ideas/suggestion on how we can improve it, can you open an issue in the site repository? Thanks!


bzimport improvements

There are some minor BZ import improvements - namely disabling history fetching and better handling of restricted flaw related bugs when looking for tasks. More importantly there is however on quite important change. This was probably forgotten or I do not know. Basically the reliability of the BZ import is based on rerunning any batch sync which encountered some temporary failure. However the failures were so far not categorize in any way so all were just considered persistent - even any network outages, backend downtimes etc. This slight omission results in the reliability being on the same level as it was (zero) because we just skip all the errors. This PR introduces the BZ exception categorization into recoverable and non-recoverable and stops skipping the recoverable ones - failing hard there so the batch gets rerun.

@Elkasitu all the requested changes should be hopefully incorporated. Feel free to merge this if it is OK now (and if it is possible on GitHub). I will be back at the end of July.


Do not include toplevel printer installation in the base library

It is customary to have a dedicated library for this (if ocaml and ocamlfind had better conventions no library should be needed but that's another problem).
The fact that you use the toplevel API in the library, means that it's not possible to load owl in the native toplevel ocamlnat (the native toplevel API unfortunately has a separate API, see MPR 7589).
I'd advise to follow the toplevel scheme of gg, see the files gg_top* here and the META here.
After this you have two ocamlfind packages, owl and owl.top which users can require either for having the bare library or to have owl plus its toplevel support. Bonus point, you'll get rid of these offensive Obj.magics.
/cc @mars0i
More context https://discuss.ocaml.org/t/dynamically-link-native-code-into-utop/793

Cool, Daniel, thank you very much for pointing it out, and really appreciate the detailed information you linked. I have gone through the pages, and yes I will separate the toplevel functions from the base library as you suggested.
For the discussion about the customised utop, it might make sense to make a customised one for the zoo system, since it might solve the issue of nested #zoo directives.

Thanks Liang.  (It was my attempt to use Owl in ocamlnat that led to this issue.)

OK, I see. I will split toplevel function out of the base library as Daniel suggested. Then it should work.

This has been solved. Now Zoo system will serve as Owl's customised toplevel and scripting environment. To install all the pretty printers and import Owl, you only need to
#require "owl_zoo";;

@mars0i in the end, the toplevel part is in owl_top, owl_zoo will be another component soly focussing on composing high-level services, sharing and deploying services (in future). This decision also solved a couple of issues in the example scripts.
So in case you need Owl's pretty printing in toplevel, use the following code.
#require "owl_top";;

My apologies for the inconvenience caused by the many significant changes recently, but the purpose is getting this library better and better.

I think this issue has been addressed so I am closing it. In case you spot any related issues, please reopen this one or open a new issue. Thanks for all the feedback and helps again.


Add proxy info on HTTP protocol and pairing token

Fixes #4759
The last two sentences of the second paragraph are optional, but they make the attack prevention concept utterly clear.
cc/ @shirhatti @blowdart

@guardrex,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@shirhatti  can you give this a quick review?

@shirhatti can you give this a quick review?


No histogram generated

We ran the genomescope tool on a lock terminal but cannot generate histograms. The histo file is coming out to be blank. Anyone has any idea? The query is S. lycopersicum short read sequences.

What commands did you run to generate the histo file?

We got it. Thanks for the quick response.
Sanskriti
Shyama Prasad Mukherjee Fellow
National Agri-Food Biotechnology Institute (NABI)
Sector 81, Mohali
Punjab, India
On Tue, 31 Jan 2023 at 13:12, Timothy Rhyker Ranallo-Benavidez <
@.***> wrote:

What commands did you run to generate the histo file?
—
Reply to this email directly, view it on GitHub
https://github.com/schatzlab/genomescope/issues/91#issuecomment-1410925985,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5SVB6HAPF3CPQG4HE4KM63WVFP2VANCNFSM6AAAAAAUMZOEUE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Closes #18, #28, #29

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[x] Updated relevant unit tests or have written new unit tests - See Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[x] Update to all relevant roxygen headers and examples.
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[ ] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
[ ] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[ ] Address or fix all lintr warnings and errors - lintr::lint_package()
[ ] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue so that it closes after successful merging.
[x] Address all merge conflicts and resolve appropriately.
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

@nicholas-masel this ended up a bit larger than I intended - but covered a couple different things! I added two new issues (linked) to cover the extra pieces.

@mstackhouse  This looks good so far.  I will continue to check this one, but I did add the following:

Warn user if the envsetup environment being used, does not match with a named autos environment. (We should add this to paths too).
Swapped in purrr for dplyr in our library calls for the autos tests.  This is a package import, so we avoid a warning in check().
Swapped in do.call(set_autos) within library() so it is consistent w/the rprofile() call to set_autos(), making the input objects the same.  I was surprised the objects differ with do.call() vs just calling set_autos() directly.

@nicholas-masel

Swapped in do.call(set_autos) within library() so it is consistent w/the rprofile() call to set_autos(), making the input objects the same.  I was surprised the objects differ with do.call() vs just calling set_autos() directly.

So - let me know what you think, but the reason I had to do this was because I didn't want to change the input parameter to set_autos(). The reason I'm do.call()ing it is because we list(...), which ended up giving this awkward nested structure. But - if we make set_autos() internal and just make the ... into like autos, which is then the equivalent of what list(...) should be then we avoid the do.call().
Since you suggested making set_autos() an internal function then I'm ok with simplifying the API. I didn't want to modify it before because the list structure it expects is pretty specific and made more sense as a named parameters as an exported function.
Does that sound better to you?

@nicholas-masel

Swapped in do.call(set_autos) within library() so it is consistent w/the rprofile() call to set_autos(), making the input objects the same.  I was surprised the objects differ with do.call() vs just calling set_autos() directly.

So - let me know what you think, but the reason I had to do this was because I didn't want to change the input parameter to set_autos(). The reason I'm do.call()ing it is because we list(...), which ended up giving this awkward nested structure. But - if we make set_autos() internal and just make the ... into like autos, which is then the equivalent of what list(...) should be then we avoid the do.call().
Since you suggested making set_autos() an internal function then I'm ok with simplifying the API. I didn't want to modify it before because the list structure it expects is pretty specific and made more sense as a named parameters as an exported function.
Does that sound better to you?

@mstackhouse  I'm good either way.  If we change it, I would just want to confirm the structure passed set_autos() is the same  as it was with do.call() so the checks work correctly.

@nicholas-masel ready for re-review.

@nicholas-masel we good to close? I filed an issue for the failing tests.

@nicholas-masel we good to close? I filed an issue for the failing tests.

yep, i'm good with it


Dataflow Limitations Correction - Multiple Credentials for Single Data Source

Microsoft Team,
It appears there's an issue with the Dataflows Limitations page, specifically in the Dataflow authoring section. Based on an error I'm facing, it appears dataflows cannot support multiple credentials for any single data source. The current description says this limitation only applies to gateway data sources, however, I am using a cloud-based SQL server and I cannot use multiple credentials.
Perhaps I am just missing something, so I welcome any clarification you can provide. Better yet, adding this feature would be great! No matter what, it would be ideal to ensure these instructions/limitations are accurate for the time being.
Thanks for your support!
-Anthony

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

ID: b3ec2a31-ae63-38f7-00e8-234bcedd571d
Version Independent ID: ff4d4e25-80f5-cac3-49c8-a85b7cf1c476
Content: Dataflows Limitations, restrictions and supported connectors and features - Power BI
Content Source: powerbi-docs/transform-model/dataflows/dataflows-features-limitations.md
Service: powerbi
Sub-service: pbi-dataflows
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Article has been updated, thanks.


include builds for linux 4.15 and 4.16

practically a duplicate of #121, which seems to be lost

Hi, good stuff :)
Is '-Wno-error=missing-field-initializers' needed? Maybe we can simply add missing initializers?
Can you unify comments style?
Sometimes it is
//
//

or
/* */
//

/*
 *

Weird ;)
And the last one, according to
https://github.com/DisplayLink/evdi/blob/devel/library/LICENSE
library is indeed on LGPL 2.1
but this
https://github.com/DisplayLink/evdi/blob/devel/module/LICENSE
says module is on GPL 2
but you have added LGPL to both :)

I copied this workaround from #121. The comment states that this is due to uninitialised struct fields in linux, so I am not sure whether it makes sense to initialise them. Maybe @jtdoepke might be able to provide some more details to this.
I'll see what I can do on the unification.
The last one is a copy-paste error, sorry.

@dawikur It turns out that unified comment style is not an option:

.c files are expected to start with the exact string // SPDX-License-Identifier:
.h files are expected to start with the exact string /* SPDX-License-Identifier:

Unless you want to have all multi-line comments to start with //, unified comment style seems not to be an option (yet).
PS: I don't like this either (at all)

IIRC, the uninitialized fields came from the Linux kernel, so nothing to do about it in this repo other than suppress the warning.

Really hate to be the only one bugging you guys about this, but do we have an ETA on a merge?

Come on guys, please support your product. I bought display-link specifically for Linux support.

Sorry it took so long. We have finally again 'green' build :)

I've been looking around but I can't see how to use the latest version. I installed running displaylink-driver-4.2.29.run and see nothing new running xrandr, so I assume this patch for my kernel is not yet in displaylink driver 4.2.29. How do I proceed to make use of my new StarTech toy?

You probably want to start a new issue if you didn't find what you were looking for in the existing issues like e.g. #133. This thread is most likely not related to your problem.


Earcut tessellator

This is what I see on iOS with earcut. Will update with more info, as I debug this further.

fixed with last commit

@hjanetzek do you plan to do thread local storage implementation here like you did in the https://github.com/tangrams/tangram-es/tree/exp-earcutting branch?

@tallytalwar c++'s thread_local seems not to be supported by android yet (tried with clang 3.5 and 3.6). We could enable it for other platforms though or use pthread's thread local storage. But this could go into a separate branch IMO, together with looking for other places to reduce temporary allocations during tile building.

@hjanetzek That makes sense to me. This branch is looking good, will merge!


fluid-type

So here's one I'm going to be using a lot:
Fluid-type
http://codepen.io/dbox/pen/meaMba
which I ported from here which evidently was based on some stuff @corysimmons was doing (👊cory :tada: )
Let me know if you want it in @jenius and I'll convert to stylus and get it added.
It does bring up an issue, however, that if everything is going to get post-css converted then we're creating some unnecessary conversion work... but I need it now, so I'm happy to add and share.

This is nice!

http://codepen.io/dbox/pen/mVPmBo?editors=010
got stylus version going. Will get this added.


Show the cursor position

This fixes https://github.com/thoughtbot/pick/issues/20
There are probably some edge cases here so if people could test this out that would be awesome.

Just realized I'm not sure if this is needed anymore. Headed out will close if so.


Option to add keywords or tags to encrypted email to make them searcheable locally

Expected behaviour
I would like to add some text lines to an encrypted email so that I can search and find that email.
These tags or keywords should stay locally within k9 and should be able to export/import to a text file to keep a backup and restore them later ( in case of changing phones etc.. )
users will use this feature where they still want to keep the email encrypted but ok with some metadata locally in k9 so that they can find that email later easily.
Actual behaviour
Tell us what happens instead
Steps to reproduce

Environment
K-9 Mail version:
Android version:
Account type (IMAP, POP3, WebDAV/Exchange):

Way too complicated. See #1450 for support of search in encrypted messages.


cannot import name 'spconv_utils' from 'spconv'

Hello! I am currently trying to implement SECOND with PointPillars support.
I successfully installed spconv, but when I try to python create_data.py kitti_data_prep --data_path=KITTI_DATASET_ROOT, I get the following error:
$ python create_data.py kitti_data_prep --data_path=$KITTI_DATASET_ROOT
Traceback (most recent call last):
 File "create_data.py", line 7, in
  import second.data.kitti_dataset as kitti_ds
 File "/home/../SECOND_v1-5/second.pytorch/second/data/kitti_dataset.py", line 8, in
  from second.core import box_np_ops
 File "/home/../SECOND_v1-5/second.pytorch/second/core/box_np_ops.py", line 5, in
  from spconv.utils import rbbox_iou, rbbox_intersection
 File "/home/../SparseConvNet/spconv/spconv/init.py", line 20, in
  from spconv import utils
 File "/home/../SparseConvNet/spconv/spconv/utils/init.py", line 16, in
  from spconv import spconv_utils
ImportError: cannot import name 'spconv_utils' from 'spconv' (/home/../spconv/spconv/init.py)
Any help would be appreciated!
~Hunkzer

the newest code already have pointpillars support.
please use python setup.py bdist_wheel and cd ./dist && pip install xxx.whl to install spconv.

Hi traveller59,
thank you for your answer. I had no errors or warnings when installing spconv using the steps you mentioned.
Are there some files related to 'spconv_utils', which should be generated during the installation of spconv and may be missing? I remember there is a CMakeLists.txt file located somewhere in the /src/.. directory of spconv, which refers to 'spconv_utils' and it looked like this file is responsible for creating the spconv_utils subpackage.
I will try to get it working again in a few hours, but if you have any suggestions to fix this, please let me know :)
~Hunkzer

Hi Hunkzer, kindly help me in this issue as im stuck in this error.
Iam able to do succesfully
python setup.py bdist_wheel and cd ./dist && pip install xxx.whl
But ImportError: cannot import name 'spconv_utils' from 'spconv is coming error. Kindly do the needful

Hey,
unfortunately I stopped trying to fix the error and started to work with the PointPillars implementation instead. But I will reopen this issue so this error gets some more visibility since it's not only me who is having trouble getting this to work out of the box.
Please let me know if you manage to fix the error :D

hi,
I'm also facing the same error "Importerror: cannot import name spconv_utils"
Does any of you found a solution?

i am also get this error.em, how to manage it

i am also get this error.em, how to manage it

hey! Did you solve it? I met the same problem...

I met the same problem,too

Same problem, even after python setup.py bdist_wheel and cd ./dist && pip install xxx.whl
Anyone found a fix for this?

Same issue here. Installed per instructions, in the same CONDA environment as second, still ImportError: cannot import name 'spconv_utils' from 'spconv'

I fixed this by adding:
export PYTHONPATH=/path_to_repo/spconv/spconv/:$PYTHONPATH
to my .bashrc file.

i also meet this issue, even after python setup.py bdist_wheel and cd ./dist && pip install xxx.whl

i also meet this issue, even after python setup.py bdist_wheel and cd ./dist && pip install xxx.whl
I solved this problem with downloading the master branch of spconv,
-> python setup.py bdist_wheel
-> cd ./dist && pip install --force-reinstall xxx.whl

i got the same problem. does anyone know how to fix it?
i tried below solution but still not worked

I fixed this by adding:
export PYTHONPATH=/path_to_repo/spconv/spconv/:$PYTHONPATH
to my .bashrc file.

i also meet this issue, even after python setup.py bdist_wheel and cd ./dist && pip install xxx.whl
I solved this problem with downloading the master branch of spconv,
-> python setup.py bdist_wheel
-> cd ./dist && pip install --force-reinstall xxx.whl

Hi, can you explain more about downloading the master branch? should i put the downloaded folder in certain place to make it works?

i got the same problem. does anyone know how to fix it?
i tried below solution but still not worked

I fixed this by adding:
export PYTHONPATH=/path_to_repo/spconv/spconv/:$PYTHONPATH
to my .bashrc file.

If spconv_utils.cpython-36m-x86_64-linux-gnu.so files(name of those files may vary minorly) are present  in ~/spconv/build/lib.linux-x86_64-3.6/spconv/ or whatever relatable directory. You should add that directory into $PYTHONPATH env variable. If not, stop reading this because you have some other problem :(
When path to spconv automatically added to sys.path by python, appending path I mentioned to the end of paths list wont work out. Because python finds the wrong directory first, then somehow ignores the right path coming at the end added by you. So add your path by  export PYTHONPATH="${PYTHONPATH}:/home/user/spconv/build/lib.linux-x86_64-3.6/spconv/" which will insert it as the first path in PYHTONPATH. At least this was how i solved my issue.

thanks a lot!! I solved my problem following your instructions!!!!!!! ^v^


UMA integration on Harmony

Description
We are looking to integrate UMA protocol (Universal Market Access) on Harmony. This will allow applications built on Harmony to be able to work with UMA to build synthetic financial products.
Context
UMA builds open-source infrastructure for “priceless” financial contracts. Specifically, this is two things:
Priceless financial contract templates used to create synthetic tokens
Decentralized Oracle Service used to manage and enforce contracts on UMA
Together, these two technologies enable the creation of fast, efficient, and secure derivatives.
Acceptance Criteria
To qualify as complete, application developers should be able to use UMA on Harmony to deploy any financial product that is made possible by UMA.
Here is the documentation:
https://docs.umaproject.org/build-walkthrough/build-process
https://docs.umaproject.org/developers/emp-deployment
https://github.com/UMAprotocol/launch-emp
Reward
$5000 in ONE tokens.

"To qualify as complete, application developers should be able to use UMA on Harmony to deploy any financial product that is made possible by UMA"
Does this mean

deploying a UMA smart contract or  whole protocol deployed on harmony? or
Access to the protocol . i.e building  the necessary interchain infrastructure to interact with UMA  from harmony


Cache experiment

Pull Request check list

[ ] Commit conforms to CONTRIBUTING.md?
[ ] Proper tests/regressions included?
[ ] Documentation updated?

Affected functionality

Description of change

Which issue this PR fixes

@martincapello WIP:
Added subscribe method.
Introduces the notion of nodeType cache entry.
Populates connection pool


/language/traps should warn against using [Z] to get the transpose of a list-of-lists

Every now and then, someone gets they idea that they can use [Z] to create the transpose of a list-of-lists:
my @matrix = <X Y>, <a b>, <1 2>;
my @transpose = [Z] @matrix;

say @transpose;  # [(X a 1) (Y b 2)] -- so far so good

And everything works fine... until you get an input @matrix with exactly one row (child list):
my @matrix = <X Y>,;
my @transpose = [Z] @matrix;

say @transpose;  # [(X Y)] -- not the expected transpose [(X) (Y)]

I've explained the cause of this surprising edge-case behavior, which basically ruins [Z] for variable-size inputs, in this SO answer (which should be easy to understand without also having to read the associated SO question).
I think this has all the markings of a trap:

The syntax is simple (so people will continue to "discover" it), and elegant (so they'll be happy to use it).
It's quite sensible to expect, on first sight, that it will do the right thing.
It does in fact do the right thing for most inputs, meaning that it might slip through unit tests etc.

Thus, I think the Perl 6 documentation should mention it in its "Traps to avoid" document.

FWIW, we now have this ticket: https://rt.perl.org/Ticket/Display.html?id=131686

Another interesting ticket (although maybe unrelated): https://github.com/rakudo/rakudo/issues/1210

I think this is now resolved in https://github.com/perl6/doc/commit/6519ef5399c36650c07c2aced90265aeab780922. I copied some parts of your OP here, let me know if that's a problem.


File input not working

It looks like file input isn't working.
Works:
aix -p "Write a haiku

Doesn't work:

cat ./aiinput
Write a haiku

aix -p ./aiinput
Error:

@olearycrew this is now fixed with latest release - https://github.com/projectdiscovery/aix/releases/tag/v0.0.3


Add type-level Equals for Boolean

Fixes #65

I’m wary of adding things before we have  a concrete use case for them. Is that the case here?

I don't have a good case in mind. I believe this would be required if one ever created a type-level list of booleans and wanted to find an element within that list. But I can't think of a scenario where one would want to do that at the type-level.

@kl0tl Since you originally suggested this, do you have any concrete use cases in mind?

I did not propose this class with a specific use case in mind, but I guess it would be needed to implement the characteristic function of a relation that holds either when it does or fails for all its premises (but not when it fails only for some of them). For example with type-level routes you may need this to know if all routes in a set of alternatives are either auth protected or unprotected.
Without some boolean equality we can only express the characteristic function of relations that hold when they do for all (with And) or any (with Or) of their premises. The same line of reasoning would support also adding xor and logical implication.
I’m fine waiting for concrete use cases though, this is easy enough to implement elsewhere if needed in the meantime.

We could leave this PR open until such a use case emerges and then merge this PR and make a release pretty trivially, right? However, I'm not sure I'd want an open PR on a repo that may never get merged. So, should this actually be closed instead?

I’d rather close this than leaving it open for merging at some unspecified future date, yeah. The PR will still be there if someone looks at the list of closed PRs.


Fix two small sphinx errors in the tutorials

I'll skip the CI since this does not touch code and no sphinx build is defined for Travis.
[skip ci]

thanks!


[cxx-interop][windows] support using a custom libc++ on Windows

This depends on:
https://github.com/swiftlang/swift/pull/76109
This change builds upon the support for specifying which C++ standard
library to use, by adding support for using a custom libc++ on Windows.
Even though the clang Windows driver doesn't support libc++ explicitly,
Swift can still use it by allowing users to pass in the path to libc++
using the -cxx-isystem flag.
The CxxStdlib module is prohibited to use on Windows when libc++ is
used, as it has incompatible ABI.

@swift-ci please tset

@swift-ci please test

@swift-ci please test


monad-logger-prefix doctest failure (ambiguous module conflict with purescript)

Linking dist/build/doctest/doctest ...
> /tmp/stackage-build8/monad-logger-prefix-0.1.5$ dist/build/doctest/doctest

/tmp/stackage-build8/monad-logger-prefix-0.1.5/src/Control/Monad/Logger/Prefix.hs:47:1: error:
    Ambiguous interface for ‘Control.Monad.Logger’:
      it was found in multiple packages:
      purescript-0.9.3 monad-logger-0.3.19

This test can probably be enabled again; purescript has been "abandoned" on stackage and removed from the build plan for other reasons.


Separate testnet and mainnet networks

This came up in a chat with @andrewxhill. He pointed out that allowing JOINs between testnet chains and mainnet chains might setup some bad expectations.
Is there an easy way for us to ensure all tables involved in a query are either on a testnet or on a mainnet?

Now, I think this request might imply something deeper. Making the above sounds like we want to isolate mainnet chains from tesntet chains, which feels like wanting to run in a single validator on two separate networks. Maybe this means we should recommend running two different validators, one for mainnet and one for testnet? I say this because "not mixing" testnet and mainnet tables might not only make sense for read queries, but actually for everything in the protocol.
For example, if in the future we want to provide a service where a validator tells all the tables it's running: it makes sense that it will tell both testnet and mainnet ones? Because the idea here is that you won't be able to join, so it might be odd.
Also, if we come up with other validator processes such as committing state of tables, we want to mix both testnet and mainnet worlds? Same with potential tokenomics actions?
Users can't do read-query joins if testnet and mainnet tables run in two separate validators. (Pretty obvious, but just for completeness).
Of course, this would mean that operators would have to run two validator nodes instead of one; but if both worlds are separate then sounds obvious. We could also think about a single validator syncing chains grouped in "partitions", where each "partition" would be a different SQLite database. That's almost the same as two separate validators but ran in a single process. (Kind of a multi-tier validator (separate registry, system_* tables, etc). Not sure it's worth it since it might be better not to share hardware resources between testnet and mainnets).
Now, if we keep running tables in the same validator, we could walk the AST and detect which tables are targeted after we parse the read-query. If there's at least one table in mainnet and testnet, we could make the query fail at parsing time. But my point above is mostly thinking further if we might need to have a way to make this separation not only for read-queries, but maybe for more things, so this might not be the best approach.

Good points. Total separation is the cleanest solution to the JOINs issues, and would prevent us from having to solve additional related issues in the future around table state / security and economics.

Separate validators sounds right. Image a scenario where there is a new version of the validator that we want to roll out to testnet for a period of time for testing before the mainnet upgrade. That would only be possible with this separation in place. Seems like this solves many problems at once.

I'll close this issue since all this work was split into multiple tasks that were already done, and the tail of the remaining tasks are part of https://github.com/orgs/tablelandnetwork/projects/58.


[BUG] Builds is not being filtered by tests fields

We have global filters that are not affecting the builds because it is a separated endpoints that doesn't acknowledge hardware
This is for the treeDetails page, hardwareDetails is already a single endpoint but the global filters are on #618

We are talking about global filters like hardware

Since this issue originally was talking about the commitGraph but was changed to the treeDetails page in general, there is a new issue for the commitGraph in specific: #640


Allow user to see their submitted expenses on the collective page ahead of their approvals

https://opencollective.freshdesk.com/a/tickets/119774
User story
As a user, after I submit an expense it is not easy for me to see whether it has been successfully recorded on the collective page as there is currently no visibility of the expenses pending approval. The transactions listing on the user end only gets updated once the expense is approved. This lack of visibility can result in duplicated requests being submitted, increasing the risk of overpayments, if those are not caught by the collective and host admins.
Best solution for this problem
Can we add an UI where users can view submitted requests, so they know it has indeed been submitted pending approval?
P3 high frequency, low impact

Duplicate of https://github.com/opencollective/opencollective/issues/3749


dora node packet loss

Describe the bug
The dora is V0.3.2.
I use two nodes. Node A is written in Python. Node B is written in c/c++.
Node A reads GPS data at a 20ms cycle and sends the data via a json string. Node B performs coordinate conversion by receiving data from node A, but I found that node B will lose data packets when receiving data from node A.
Here I print the seq number of the data pub by node A, the message count received by node B, and the time when the message was received. There was no packet loss at the beginning, but after running for a while, the message count received by node B was not equal to the seq value of the message.
And, the period of node B to receive data should normally be 20ms, which depends on the period of node A sending data. However, the following picture shows that the time difference between the two events is 40ms. （lower left corner）
here is the test code:
https://github.com/dora-rs/autoware.universe/blob/feature/autoware_dora/localization/ekf_localizer/test_ekf_dataflow.yml

Could you try removing the sleep here: https://github.com/dora-rs/autoware.universe/blob/db29af5314dbe4c3c9c5c79ab78e33f2a8bbd327/localization/ekf_localizer/src/gnss_ekf.cc#L65

The “EKF_fusion_pthread“” thread is the sleep of the thread that sends data and has nothing to do with data reception. Data packet loss has occurred when receiving data from other nodes in the function “int run(void *dora_context) ”.

Dora uses a default queue size of 10 for each input. If the receiver cannot keep up with the sender, dora deliberately drops some inputs (oldest first). If you set the RUST_LOG environment variable to debug you will see a "dropped X inputs because event queue was too full" in the command-line output.
You can set a custom queue size in your YAML file, e.g.: https://github.com/dora-rs/dora/blob/ea47a556a77f6c64f29ab07939d747edc8573671/examples/python-dataflow/dataflow.yml#L5-L8

As you said I set the parameter queue_size: 100, but data packet loss still exists.
I check the logs for the python node "gnss" , which is normal pub the data with 4643.

The second node  "gnss_poser" with c/c++ finally received only 4229 data_seq.

This phenomenon started to occur when receiving the 33rd data seq.

here is the xxx.yaml file:
nodes:
  - id: gnss
    operator:
      python: ../../dora-hardware/vendors/gnss/CGI_610/CGI_610_driver_dora_with_file.py  #读取文件用于测试
      #python: ../../dora-hardware/vendors/gnss/CGI_610/CGI_610_driver_dora.py
      inputs:
        tick: dora/timer/millis/20
      outputs:
        - DoraSentence
        - DoraNavSatFix
        - DoraQuaternionStamped
        - DoraTwistStamped
    env:
      DEVICE_INDEX: 0

  - id: gnss_poser  #坐标系转化
    custom:
      source: ../../sensing/gnss_poser/build/gnss_poser_core
      inputs:
        DoraNavSatFix: gnss/DoraNavSatFix
      queue_size: 100
      outputs:
        - DoraNavSatFix

  - id: gnss_rviz2  #在RVIZ2中显示转换后的轨迹 （E-N-U）
    operator:
      python: ../../sensing/gnss_poser/src/gps_to_ros2.py
      inputs:
        DoraNavSatFix: gnss_poser/DoraNavSatFix
      queue_size: 100

  - id: gnss_ekf  # c/c++节点
    custom:
      source: build/gnss_ekf
      inputs:
              DoraNavSatFix: gnss_poser/DoraNavSatFix
              DoraQuaternionStamped: gnss/DoraQuaternionStamped
      outputs:
            - DoraGnssPose
      queue_size: 100

  - id: ekf_odom_rviz2  #在rviz中显示数据
    operator:
      python: src/ekf_odom_to_ros2.py
      inputs:
          DoraGnssPose: gnss_ekf/DoraGnssPose
      queue_size: 100

Hu has also tested with 100K queue size today and can reproduce this issue.

Thanks for the details!
Could you please also share the full output of the terminal on the top left? I see that there are some error in the output, so the full content might help debugging this. Also, setting RUST_LOG=debug before dora up should expose more details in the logs, including information when events are dropped.

The error in the terminal on the upper left corner is that we did not use a real GPS sensor during debugging, but used the data in the txt file to simulate GPS data. This error is generated after the data in the txt file has been read and the node exits. Therefore, this error should not affect data loss.
The details can be found in line 26 of file CGI_610_driver_dora_with_file.py( https://github.com/dora-rs/autoware.universe/blob/feature/autoware_dora/dora-hardware/vendors/gnss/CGI_610/CGI_610_driver_dora_with_file.py)

The error in the terminal on the upper left corner is that we did not use a real GPS sensor during debugging, but used the data in the txt file to simulate GPS data. This error is generated after the data in the txt file has been read and the node exits. Therefore, this error should not affect data loss.
The details can be found in line 26 of file CGI_610_driver_dora_with_file.py( https://github.com/dora-rs/autoware.universe/blob/feature/autoware_dora/dora-hardware/vendors/gnss/CGI_610/CGI_610_driver_dora_with_file.py)

I just noticed that you added the queue_size parameter as a child of the the custom: object. It has no effect there. Instead, you need to add it as a child field to an input. For that, add another level of nesting underneath the input, specify the source mapping as a source field, and then add the queue_size as a second field. I opened a small PR for that: https://github.com/dora-rs/autoware.universe/pull/6. Please retry again with these changes.

Hello! I tested this change and the packet loss problem still exists.

here is the yaml file:
nodes:
  - id: gnss
    operator:
      python: ../../dora-hardware/vendors/gnss/CGI_610/CGI_610_driver_dora_with_file.py  #读取文件用于测试
      #python: ../../dora-hardware/vendors/gnss/CGI_610/CGI_610_driver_dora.py
      inputs:
        # tick: dora/timer/millis/20
        tick:
          source: dora/timer/millis/20
          queue_size: 1000
      # queue_size: 100
      outputs:
        - DoraSentence
        - DoraNavSatFix
        - DoraQuaternionStamped
        - DoraTwistStamped
    env:
      DEVICE_INDEX: 0

  # - id: gnss_sub  #数据格式转换 json
  #   operator:
  #     python: ../../dora-hardware/vendors/gnss/CGI_610/nmea_subscribeTopic.py
  #     inputs:
  #             DoraSentence: gnss/DoraSentence
  #             DoraNavSatFix: gnss/DoraNavSatFix
  #             DoraQuaternionStamped: gnss/DoraQuaternionStamped
  #             DoraTwistStamped: gnss/DoraTwistStamped
  #     outputs:
  #       - DoraNavSatFix
  #       - DoraQuaternionStamped

  - id: gnss_poser  #坐标系转化
    custom:
      source: ../../sensing/gnss_poser/build/gnss_poser_core
      inputs:
        DoraNavSatFix:
          source: gnss/DoraNavSatFix
          queue_size: 1000
      outputs:
        - DoraNavSatFix

  - id: gnss_rviz2  #在RVIZ2中显示转换后的轨迹 （E-N-U）
    operator:
      python: ../../sensing/gnss_poser/src/gps_to_ros2.py
      inputs:
        DoraNavSatFix:
          source: gnss_poser/DoraNavSatFix
          queue_size: 1000
##############################################################################################
  - id: gnss_ekf  # python 实现
    # custom:
    #   source: build/gnss_ekf
    operator:
      python: ../../localization/ekf_localizer/src/gnss_ekf.py
      inputs:
        DoraNavSatFix:
          source: gnss_poser/DoraNavSatFix
          queue_size: 1000
        DoraQuaternionStamped:
          source: gnss/DoraQuaternionStamped
          queue_size: 1000
        tick:
          source: dora/timer/millis/20
          queue_size: 1000
      outputs:
            - DoraGnssPose

  # - id: gnss_ekf  # c/c++节点
  #   # custom:
  #   #   source: build/gnss_ekf
  #     inputs:
  #             DoraNavSatFix: gnss_poser/DoraNavSatFix
  #             DoraQuaternionStamped: gnss/DoraQuaternionStamped
  #     outputs:
  #           - DoraGnssPose

  - id: ekf_odom_rviz2  #在rviz中显示数据
    operator:
      python: src/ekf_odom_to_ros2.py
      inputs:
        DoraGnssPose:
          source: gnss_ekf/DoraGnssPose
          queue_size: 1000

For debugging, it would be useful to have a minimal example that still triggers this issue. Could you try the following:

Remove all nodes from the dataflow that are not needed to reproduce this issue.
Remove all inputs/outputs that are not needed to reproduce this issue.
Simplify the node code as much as possible, e.g. by sending mock data.

Remove as many dependencies as possible (to make it easier to run on other machines).
Remove all code that is not relevant to this issue.

After these steps, we ideally have a very small example that we can try easily on our machines without working into the autoware build details.

The second link is the minimal example.  The link for all examples is
https://github.com/dora-rs/autoware.universe/tree/feature/autoware_dora/tools
Here are some minimal test tools helping reproduce issues.
Folder C_Python_test
It is a minimal example the one for reproduce #515 and #516. For instructions please go to folder and you will see the steps.

Folder C_node_test
It is a minimal example the one for reproduce #502. For instructions please go to folder and you will see the steps.

Here are some results 6 hours ago for #515

queue_size: 1000

First restart:
  First time: package loss 1
  Second time: package loss 0
  Third time: package loss 3
  Fourth time: package loss 0
  Fifth time: package loss 4

Second restart:
  First time: package loss 1
  Second time: package loss 43
  Third time: package loss 4
  Fourth time: package loss 4
  Fifth time: package loss 5

queue_size: 100

First restart:
  First time: package loss 2
  Second time: package loss 6
  Third time: package loss 3
  Fourth time: package loss 637
  Fifth time: package loss 3

Second restart:
  First time: package loss 193
  Second time: package loss 259
  Third time: package loss 1
  Fourth time: package loss 1
  Fifth time: package loss 4

The easiest way to reproduce issue is this minimal test example -  https://github.com/dora-rs/autoware.universe/tree/feature/autoware_dora/tools/C_Python_test.

Ok, so I tried your example and I can reproduce the dropped messages. If you spawn the coordinator and daemon manually and set RUST_LOG=debug, you see a lot of "dropped X inputs because event queue was too full" log messages. This occurs for both the noda_A/tick input (a lot) and for the node_B/input-1.
When I increase the queue_size of node_B/input-1 to 10000, all 10k messages reach the Python node:
Input Data length: 3
Received messages: 10000/10000
=======================

The reason why this happens mostly when combining a sending C node with a Python receiver is probably that Python is slower, so it cannot keep up with the inputs.

I think a change such as #533 would make it more obvious what's happening.

After further investigation, there were no packet loss and it was a problem in the C++ String with no null termination.


[Feature] (array function) support array_pushback function

Search before asking

[X] I had searched in the issues and found no similar issues.

Description
No response
Use case
No response
Related issues
https://github.com/apache/doris/issues/17176
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I'd like to try it.


Better Support for Lerna/Yarn worskapces

Is your feature request related to a problem? Please describe.
I've got detox working with my lerna/yarn workspace/monorepo, but I have to include jest in package.json in sub folder to get it working. My folder structure is:
-root folder
--package.json <- jest dependency for all 4 packages
--node_modules
---.bin
----jest <- detox can't find this executable
---packages
----mobile
-----package.json <- detox config + jest dependency
-----node_modules
------.bin
-------jest <- detox works if I add dependency to packages\mobile\packages.json
...other packages
This isn't the best I think since one has to maintain common dependency in multiple package.json files. If I only place dependency in root package.json I get 'node_modules\.bin\jest' is not recognized as an internal or external command.
Describe the solution you'd like
Solutions recommended by yarn: multi-root, custom module map, clever traversing scheme : https://classic.yarnpkg.com/blog/2018/02/15/nohoist/ (although the issue is not in hoisting...just in executables, I think solution is the same)
I think one simple solution would be to look for test-runner executable in working + 2 parent directories (so in my case we would first look for node_modules/./bin/jest in mobile folder, then packages folder and finally root folder...only then failing). I think this is the place where code would have to be changed/added: https://github.com/wix/Detox/blob/8b3a973c5d1937211436d7db4d05896e00eaa2b7/detox/local-cli/test.js#L258
Would you accept this in your code base? I was researching a bit and I couldn't find any other standard way to handle that. Maybe to prevent going outside the project folder we could compare if root was reached and abort there.
Describe alternatives you've considered
As mentioned above adding jest to dependencies in package.json in subfolder (mobile in my case), works as a workaround, however I think in general isn't the best solution since one could end up testing his packages with different versions of jest. Also hoisting is not an issue, since yarn will still add executable to node_modules.bin in the directory where jest is included (package.json).

I don't really understand the issue here as I am unfamiliar with this ecosystem, but I don't think traversing arbitrary user folders, potentially outside of the current project scope, is a good idea.

Issue is that running detox throws 'node_modules\.bin\jest' is not recognized as an internal or external command as mentioned above. Workaround is to prevent hoisting the executables in root\node_modules\.bin folder, so that they are available for detox in root\packages\mobile\node_modules\.bin. This solves the issue, but I don't like the part about adding duplicate dependencies into my root and mobile package.json (as far as I've read one should avoid it).....that's why I wanted to propose the change. I think it's the only change needed to be done to make detox fully compatible with monorepo/wrokspaces.

I wonder if there are environment variables where the real path can be deduced? Or some other metadata.

First thing that comes to my mind is that workspaces are defined in root package.json In my case:
"workspaces": {
    "packages": [
      "packages/*"
    ]
  },

Reference: https://classic.yarnpkg.com/en/docs/workspaces/#toc-how-to-use-it


feat(jsx): support create variable with type

When using useState to create a variable of type number or boolean in typescriptreact, add the type

thanks~


core method to merge a template with project

Topic
@svelte-add/core
Description
create-svelte works by copying template files into the user's project. Things like an .eslintignore, .prettierrc, etc. get copied over and just dropping them in this directory can be a little nicer than inserting their contents into a method in a .js file. It would be nice to port over the prettier, eslint, playwright, and vitest setup into this project and having that functionality be available would make it a lot easier
Describe the solution you'd like
Some features it has:

you can put +typescript or -typescript in the directory name if it should run only if you do or don't have typescript installed. It also works with any adder name, but I'm not sure that's necessarily required. Just being able to have a TypeScript and non-TypeScript version would be a great start that handles most of the cases
you can put a package.json in that directory and it will be merged into the user's package.json
you can put sub-directories like src/lib/db or src/routes/login and it will copy files over with that layout. this is less used that the other two, but can be a nice thing to have

I don't fully agree with this one yet.
There is a few things that we need to keep in mind. create-svelte is intended to be a one-off command to kickof a project. Thus, you cannot execute create-svelte on an existing project, which is one of the reasons they come a away with having template files like in +eslint+prettier, where they just assume that they can overwrite the lint command inside the package.json because it's been a new project, a nobody other than the cli should have been able to make modifications at this point.
Since our cli can be run even later on, it could already be the case that the user has already added a lint command, potentially with some completely unexpected tooling. That's why I don't think it will be safe enough to just merge files like the package.json. But I think that this would only apply for files that are modified quite frequently and do not belong to any tools we have adders for. That would mean that I think your idea could work perfectly for files like the eslint.config.js
For the mentioned eslint.config.js I could imagine having a file definition like this inside the adder definition
{
    name: () => "eslint.config.js",
    contentType: "script",
    content: ({ typescript, fromTemplate }) => {
        fromTemplate(`eslint/${typescript.installed ? "+" : "-"}/eslint.config.js`);
    },
},

As for the package.json I think we could perfectly handle that with our current tooling without any additional work.

The package.json part probably isn't the most important, but the merging is pretty minimal. Usually just dependencies and devDependencies. It's really just a nice shortcut for adding dependencies like this:
https://github.com/sveltejs/kit/blob/main/packages/create-svelte/shared/%2Bprettier/package.json
Although maybe there's concern about what to do if a user already has a different version of the package added. Should it update the always, only if newer, never? Although we'll have to answer that question either way if we have a utility method. But we could have multiple implementations of a utility method, which could be nice in forcing people to think about the behavior, but maybe we also want to have one that we recommend as the default?

As both adders we thought would require this have been implement, we can safely close this for now. If something arises in the future where this might help, we can just re-open this.


Remove after_connect and log as repository "callbacks"

It's a commit to remove after_connect https://github.com/tony612/ecto/commit/fdde818bc3028e2e82ee0fe96a41f2c05a98f6ec .
But I'm not clear about log as repository "callbacks", does it mean keeping the after_connect but just use IO.write :stderr to show warning?

Don't worry about after_connect for now because things will change once we adopt db_connection. Regarding log, it means we will no longer call a log function but we will allow folks to specify loggers: [...] in the repo configuration and we will call the ecto_query function on it passing the log entry.

@josevalim I'm trying to removing the log callback, then I met a strange error when I try to iterate loggers. I can reproduce the error with a simple snippet:
defmodule Foo do
  require Logger

  def log(msg) do
    loggers = [Logger]
    Logger.debug(msg)
    for logger <- loggers do
      IO.inspect to_string(logger)
      logger.debug(msg)
    end
  end
end

iex(2)> Foo.log("bar")
"Elixir.Logger"

19:07:59.337 [debug] bar
** (UndefinedFunctionError) undefined function Logger.debug/1
    (logger) Logger.debug("bar")
             iex:9: anonymous fn/3 in Foo.log/1
    (elixir) lib/enum.ex:1473: Enum."-reduce/3-lists^foldl/2-0-"/3
             iex:7: Foo.log/1

I have no idea what's happening. Is it a bug in Elixir or my wrong usage ?

debug is a macro, you can't call it dynamically. Please hold on though on this feature, I would like to move to db_connection before we start changing those callbacks (as after_connect relies on db_connection in the first place).

:ok_hand:

The db_connection changes for this are now in, I'm not sure what's required for this now though.

We just need to stop exposing log I the repository in favor of MFAs, like
in after_connect.
On Saturday, January 9, 2016, James Fish<EMAIL_ADDRESS>wrote:

The db_connection changes for this are now in, I'm not sure what's
required for this now though.
—
Reply to this email directly or view it on GitHub
https://github.com/elixir-lang/ecto/issues/1126#issuecomment-170252476.

--
José Valimwww.plataformatec.com.br
http://www.plataformatec.com.br/Founder and Director of R&D


Update documentation on Direct Debit mandate and payment statuses

Context
We've changed some of the status codes that are sent by the API when teams request information about Direct Debit mandates and payments. We've also removed the finished state.
Changes proposed in this pull request
Update the https://docs.payments.service.gov.uk/direct_debit/#mandate-statuses and https://docs.payments.service.gov.uk/direct_debit/#payment-statuses tables in our documentation, and clarify indemnity claims.
Guidance to review
Please check if factually correct.

@alexbishop1 I've added the error status now - could you take a look and green-tick if you're happy?


Fix zh examples for topology.kubernetes.io

Correct examples for topology.kubernetes.io in zh doc

I signed it

I signed it


admin/self_check page still warning while use current configuration

Description
the warnning details

app.ini config

nginx
client_max_body_size 512M;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Host $http_host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Real-IP $remote_addr;
requests headers

Gitea Version
1.22.4
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
docker on Qnap
Database
None

https://serverfault.com/questions/363159/nginx-proxy-pass-redirects-ignore-port
A quick search result from Google, hoop this can help you.

What's your full nginx config


BIG COMPILER BUG in Linter and Compiler

There is a huge issue with flutter linter and the compiler itself.
Assuming you want to assign a Color object to a String, it clearly shows that it is impossible and you cannot compile it as hinted below:

BUT if you introduce an inline if else then it suddenly is no problem at all:

And its no just the linter or lets call it analyzer that falls apart there, its also the compiler, leading to an app crash both on iOS and Android when running into this line of code.
We fixed our issue with that for sure, but this should not be able to compile in the first place.

Logs
[✓] Flutter (Channel stable, 2.5.1, on macOS 11.3.1 20E241 darwin-arm, locale en-US)
• Flutter version 2.5.1 at /Users/oliversonntag/SDKs/flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision ffb2ecea52 (12 days ago), 2021-09-17 15:26:33 -0400
• Engine revision b3af521a05
• Dart version 2.14.2
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
• Android SDK at /Users/oliversonntag/Library/Android/sdk
• Platform android-30, build-tools 31.0.0
• Java binary at: /Users/oliversonntag/Downloads/Android Studio.app/Contents/jre/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.5, Build version 12E262
• CocoaPods version 1.10.1
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2020.3)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
[✓] Android Studio (version 2020.3)
• Android Studio at /Users/oliversonntag/Desktop/Backup/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
[✓] Android Studio (version 2020.3)
• Android Studio at /Users/oliversonntag/Downloads/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
[✓] VS Code (version 1.60.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension can be installed from:
🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (2 available)
• sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64  • Android 12 (API 31) (emulator)
• Chrome (web)                • chrome        • web-javascript • Google Chrome 94.0.4606.61

Sounds like implicit down cast issue.
Static type of x ? color : string is Object which in pre-NNBD world can be downcast to a String, so something like this:
String s = x ? color : string;

means
String s = (x ? color : string) as String;

And blows up in runtime.
You can either disable implicit down casts via analyzer config or you can migrate to NNBD - which will also disable implicit downcasts.

(in other words this is not a bug)

@mraleph thanks for your quick reply, that seems to be the case. I didn't know that those implicit downcasts exist. I will look into it


Instant Error while trying to download any vod

Hi,
ive noticed there is a bug since a few days, i get an instant Error when im trying to download any vod regardless of Date/Streamer
Im using the 1.8.4 version
Ive tried to reinstall and also tried different save paths C/D/E

nvm sorry my fault
for whatever reason my pc readdressed my SSD that i use for the Temp folder with another drive-letter


Fix removing destroyed Container children

This PR

Fixes a bug

There were two problems with destroying Container children. I fixed them by hooking the child's DESTROY event to a new onChildDestroyed() method instead of remove().

If you destroyed a game object in an exclusive Container, the game object would (momentarily) move onto the scene display list and emit an ADDED_TO_SCENE event.

If you added a Sprite to a nonexclusive Container and stopped the scene, you would get a TypeError (evaluating 'this.anims.destroy'). This happened because the fromChild argument in the DESTROY event was misinterpreted as destroyChild in the Container's remove(), and the Container was calling the Sprite's destroy() again.

👍


Add Derrick

[Insert the URL to be listed]
https://github.com/alibaba/derrick
[Explain what the project is about and why it should be listed]
Derrick A tool to help you dockerizing App in seconds. It supports NodeJs,Java and Python. Your can simply dockerize application in seconds with a single command.

Move the entry to its alphabetical position in the list
Refactor the summary

@ringtail Nice. Thank you!


Add JDK23 For September 2023 CPU

Fixes #999
Add necessary files and logic for JDK23.
Currently in draft, until packages are available for checksum updates etc.

Refer to https://github.com/adoptium/installer/pull/1002 for suggested edits to the new debian control files

Refer to #1002 for suggested edits to the new debian control files

Thanks @theofficialgman  , I'll incorporate this change into the JDK23 release. Assuming it all works OK , I'll look to add similar updates for the other installers during the October CPU cycle.


a problem about training time

Dear Gu,
Thank you very much for your invaluable assistance in answering my previous questions.
I am currently utilizing an RTX 4070 graphics card, 32GB of RAM, and an i5-12600KF processor for my project. I have configured my gradient accumulation steps to 4. However, I have encountered a significant time constraint during training. Specifically, it has taken me approximately 4 days to complete the first epoch, reaching only 50% progress.
I am curious to know if you also experience similar training times with your setup. It would be tremendously helpful to understand if such extended training durations are common or if there are potential strategies to reduce the training time.
Thank you once again for your exceptional contributions and expertise. I am looking forward to your valuable insights and suggestions.
Best regards

In my case, it took around 12hrs to train one epoch with the SPARQL cache. It might take a bit longer (i.e., around 20 hrs) for the first epoch because many queries are not cached yet.
4 days one epoch is just way too long. Maybe it's related to your SPARQL engine? Could you check the volatile rate of your GPU? Is it 0% for most of the time?

In my case, it took around 12 hrs to train one epoch with the SPARQL cache. It might take a bit longer (i.e., around 20 hrs) for the first epoch because many queries are not cached yet. 4 days one epoch is just way too long. Maybe it's related to your SPARQL engine? Could you check the volatile rate of your GPU? Is it 0% for most of the time?

Yes, indeed, the GPU utilization during model training is consistently around 0%. I would like to inquire about how to use the SPARQL engine and how to utilize the SPARQL cache. Could you please provide some guidance on these topics? I appreciate your assistance. Thank you.

In my case, it took around 12 hrs to train one epoch with the SPARQL cache. It might take a bit longer (i.e., around 20 hrs) for the first epoch because many queries are not cached yet. 4 days one epoch is just way too long. Maybe it's related to your SPARQL engine? Could you check the volatile rate of your GPU? Is it 0% for most of the time?

I apologize for my negligence in not adjusting the path for the SPARQL cache file. I have now corrected the path, and the SPARQL cache is functioning properly. Additionally, I expect the first epoch to complete training in approximately 40 hours. However, I have noticed that the GPU utilization remains around 0% to 10%. Could you please clarify if this is normal behavior or if it could be due to my failure to utilize the SPARQL engine? I appreciate your assistance and apologize for any inconvenience caused. Thank you.

In my case, it took around 12 hrs to train one epoch with the SPARQL cache. It might take a bit longer (i.e., around 20 hrs) for the first epoch because many queries are not cached yet. 4 days one epoch is just way too long. Maybe it's related to your SPARQL engine? Could you check the volatile rate of your GPU? Is it 0% for most of the time?

I apologize for my negligence in not adjusting the path for the SPARQL cache file. I have now corrected the path, and the SPARQL cache is functioning properly. Additionally, I expect the first epoch to complete training in approximately 40 hours. However, I have noticed that the GPU utilization remains around 0% to 10%. Could you please clarify if this is normal behavior or if it could be due to my failure to utilize the SPARQL engine? I appreciate your assistance and apologize for any inconvenience caused. Thank you.

Low volatile rate basically means the process is occupied with CPU jobs (mostly executing SPARQL queries in this case), but I think you should expect the volatile rate to go up as training continues (because more queries will be cached and thus obviate the need to re-query the SPARQL endpoint).
Generally, there might be two tips to make SPARQL query execution faster: 1) set up the virtuoso endpoint on the same machine when training your model (setting up it on a remote machine might lead to some communication overhead), and 2) make sure your server have enough memory.
It's my pleasure to help. No inconvenience at all! Feel free to reach out if you have any further concerns :)

In my case, it took around 12 hrs to train one epoch with the SPARQL cache. It might take a bit longer (i.e., around 20 hrs) for the first epoch because many queries are not cached yet. 4 days one epoch is just way too long. Maybe it's related to your SPARQL engine? Could you check the volatile rate of your GPU? Is it 0% for most of the time?

I apologize for my negligence in not adjusting the path for the SPARQL cache file. I have now corrected the path, and the SPARQL cache is functioning properly. Additionally, I expect the first epoch to complete training in approximately 40 hours. However, I have noticed that the GPU utilization remains around 0% to 10%. Could you please clarify if this is normal behavior or if it could be due to my failure to utilize the SPARQL engine? I appreciate your assistance and apologize for any inconvenience caused. Thank you.

Low volatile rate basically means the process is occupied with CPU jobs (mostly executing SPARQL queries in this case), but I think you should expect the volatile rate to go up as training continues (because more queries will be cached and thus obviate the need to re-query the SPARQL endpoint).
Generally, there might be two tips to make SPARQL query execution faster: 1) set up the virtuoso endpoint on the same machine when training your model (setting up it on a remote machine might lead to some communication overhead), and 2) make sure your server have enough memory.
It's my pleasure to help. No inconvenience at all! Feel free to reach out if you have any further concerns :)

With your help, I successfully reduced the training time to one day, but the testing time is still very slow, about 10 days. I found that the testing needs to use 'bundle search' that was not used during training, which makes the testing speed very slow. May I ask if this is also a problem with 'sparql cache'

In my case, it took around 12 hrs to train one epoch with the SPARQL cache. It might take a bit longer (i.e., around 20 hrs) for the first epoch because many queries are not cached yet. 4 days one epoch is just way too long. Maybe it's related to your SPARQL engine? Could you check the volatile rate of your GPU? Is it 0% for most of the time?

I apologize for my negligence in not adjusting the path for the SPARQL cache file. I have now corrected the path, and the SPARQL cache is functioning properly. Additionally, I expect the first epoch to complete training in approximately 40 hours. However, I have noticed that the GPU utilization remains around 0% to 10%. Could you please clarify if this is normal behavior or if it could be due to my failure to utilize the SPARQL engine? I appreciate your assistance and apologize for any inconvenience caused. Thank you.

Low volatile rate basically means the process is occupied with CPU jobs (mostly executing SPARQL queries in this case), but I think you should expect the volatile rate to go up as training continues (because more queries will be cached and thus obviate the need to re-query the SPARQL endpoint).
Generally, there might be two tips to make SPARQL query execution faster: 1) set up the virtuoso endpoint on the same machine when training your model (setting up it on a remote machine might lead to some communication overhead), and 2) make sure your server have enough memory.
It's my pleasure to help. No inconvenience at all! Feel free to reach out if you have any further concerns :)

With your help, I successfully reduced the training time to one day, but the testing time is still very slow, about 10 days. I found that the testing needs to use 'beam search' that was not used during training, which makes the testing speed very slow. May I ask if this is also a problem with 'sparql cache'

In my case, it took around 12 hrs to train one epoch with the SPARQL cache. It might take a bit longer (i.e., around 20 hrs) for the first epoch because many queries are not cached yet. 4 days one epoch is just way too long. Maybe it's related to your SPARQL engine? Could you check the volatile rate of your GPU? Is it 0% for most of the time?

I apologize for my negligence in not adjusting the path for the SPARQL cache file. I have now corrected the path, and the SPARQL cache is functioning properly. Additionally, I expect the first epoch to complete training in approximately 40 hours. However, I have noticed that the GPU utilization remains around 0% to 10%. Could you please clarify if this is normal behavior or if it could be due to my failure to utilize the SPARQL engine? I appreciate your assistance and apologize for any inconvenience caused. Thank you.

Low volatile rate basically means the process is occupied with CPU jobs (mostly executing SPARQL queries in this case), but I think you should expect the volatile rate to go up as training continues (because more queries will be cached and thus obviate the need to re-query the SPARQL endpoint).
Generally, there might be two tips to make SPARQL query execution faster: 1) set up the virtuoso endpoint on the same machine when training your model (setting up it on a remote machine might lead to some communication overhead), and 2) make sure your server have enough memory.
It's my pleasure to help. No inconvenience at all! Feel free to reach out if you have any further concerns :)

When testing the model, I ran the code that was not executed during training. One particular line of code took a long time:
predictions = self._forward_beam_search(state)
which caused the model to take more than ten days to run on the test set.
I'm wondering if this code is also related to 'sparql_cache'? I'm conducting a model-agnostic experiment, and I just need to perform the final testing step. Brother, please help me out. Bringing you so much trouble,  I greatly appreciate your help!

Hi @lgxccc ,
Sorry for the late response.
In my experiments, I think it takes around 10 hrs to finish the prediction on the entire test set (i.e., ~13,000 questions) with sparql cache on. Actually, the behavior for inference is the almost the same as the behavior for validation during training, which means predictions = self._forward_beam_search(state) is also executed in validation. I'd suggest you reuse the same cache file you obtained during training, which might cover many of the SPARQL queries the model encounters during inference. Let me know if you have got it fixed!
As I've mentioned earlier, it's our pleasure to help you with using our model. Feel free to reach out if you have any further concerns.


logout + CSV encoding problem with python2

logout api end-point
Fix python2 CSV encoding with UTF

This change is

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

Comments from Reviewable


Update webfactory/ssh-agent to v0.5.3

https://github.com/webfactory/ssh-agent/releases/tag/v0.5.3

Codecov Report

Merging #35 (8ce56e6) into main (f25696e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #35   +/-   ##
=======================================
  Coverage   98.57%   98.57%
=======================================
  Files          65       65
  Lines         492      492
  Branches       30       30
=======================================
  Hits          485      485
  Misses          7        7

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 f25696e...8ce56e6. Read the comment docs.


Bug in setup.py

Users reported a fatal bug when using pip install pysal and it can be replicated locally:
mbr:~ serge$ pip install -U pysal
Downloading/unpacking pysal from https://pypi.python.org/packages/source/P/PySAL/PySAL-1.9.0.tar.gz#md5=06f1696560d39218bf5a80f0a9bdf060
  Downloading PySAL-1.9.0.tar.gz (10.8MB): 10.8MB downloaded
  Running setup.py (path:/private/var/folders/7y/72fwgkyj7z30v_vrd7w1fl380000gn/T/pip_build_serge/pysal/setup.py) egg_info for package pysal
    Traceback (most recent call last):
      File "<string>", line 17, in <module>
      File "/private/var/folders/7y/72fwgkyj7z30v_vrd7w1fl380000gn/T/pip_build_serge/pysal/setup.py", line 18, in <module>
        with open('README.md') as file:
    IOError: [Errno 2] No such file or directory: 'README.md'
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):

  File "<string>", line 17, in <module>

  File "/private/var/folders/7y/72fwgkyj7z30v_vrd7w1fl380000gn/T/pip_build_serge/pysal/setup.py", line 18, in <module>

    with open('README.md') as file:

IOError: [Errno 2] No such file or directory: 'README.md'

If I point pip to the tag on git hub I don't encounter this error:
  pysal:~ serge$ pip install -U https://github.com/pysal/pysal/archive/v1.9.tar.gz

I'm wondering if something went south in the pip setup.py  sdist upload
Last night I deleted the pypi release for 1.9 and this morning rebuilt it and uploaded. However, although 1.9 is listed when using pip install -U pysal on clean virtual machine I'm getting 1.8 not 1.9.
Thinking that removing the 1.9 and then pushing up a release with the same number might have pypi in a weird state (i.e., getting 1.8 when it shows 1.9 as latest). Thinking of doing a release 1.9.1 to fix.
Any thoughts?

the file built with python setup.py sdist which is PySAL-1.9.0.tar.gz is missing README.md

Tested 1.9.1 upload on pypi and all is well. Closing


Updated to Silex Version 2

Thanks, @pyrokar! The build seems to be broken, but apart from that it looks good. Can you have a look at that? Won't have the time to fix it myself for a few weeks.

Finished :-)

👏


InlineDependencies does not work as expected

Environment
Windows 10
$ pnpm --version
8.1.1
$ node --version
v16.18.1

Reproduction

Add inlineDependencies: true to rollup in build.config.ts
Import a library on Windows

import ms from 'ms';
console.log(ms('1d'))

unbuild

Describe the bug
Expected result: the library is inlined
Actual result: the library is not inlined in the mjs, cjs, and other builds
Additional context
My current build.config.ts solution to this issue:
import { resolve } from 'node:path'
import type { PreRenderedChunk } from 'rollup'
import terser from '@rollup/plugin-terser'
import { defineBuildConfig } from 'unbuild'

function toCamelCase(hyphenCase: string) {
  const split = hyphenCase.split('-')
  return split.map((word, i) => i > 0 ? word[0].toUpperCase() + word.slice(1) : word).join('')
}

export default defineBuildConfig({
  entries: [
    'src/index',
  ],
  alias: {
    '@': resolve(__dirname, './src'),
    '~': resolve(__dirname, './demo'),
  },
  declaration: true,
  clean: true,
  rollup: {
    resolve: {
      browser: true,
    },
    emitCJS: true,
    inlineDependencies: true,
  },
  externals: [],
  hooks: {
    // Need to monkey-patch rollup:options to get the outputs and the inline dependencies that I want
    'build:before': (ctx) => {
      // Remove all externals that are dependencies. I want them inlined.
      ctx.options.externals = ctx.options.externals.filter(name => name instanceof RegExp ? !ctx.options.dependencies.some(dep => name.test(dep)) : !ctx.options.dependencies.includes(name))
    },
    'rollup:options': (ctx, options) => {
      const getChunkFilename = (chunk: PreRenderedChunk, ext: string) => {
        if (chunk.isDynamicEntry)
          return `chunks/[name].${ext}`

        return `shared/${ctx.options.name}.[hash].${ext}`
      }

      const oldExternal = options.external
      if (typeof oldExternal === 'function') {
        options.external = (source, importer, isResolved) => {
          const unbuildExternal = oldExternal(source, importer, isResolved)
          return unbuildExternal
        }
      }

      if (Array.isArray(options.output)) {
        const baseCustomOutput = {
          ...options.output?.[0],
          sourcemap: true,
          name: toCamelCase(ctx.options.name),
        }
        options.output.push(
          {
            ...baseCustomOutput,
            chunkFileNames: (chunk: PreRenderedChunk) =>
              getChunkFilename(chunk, 'umd.js'),
            entryFileNames: '[name].umd.js',
            format: 'umd',
          },
          {
            ...baseCustomOutput,
            chunkFileNames: (chunk: PreRenderedChunk) =>
              getChunkFilename(chunk, 'js'),
            entryFileNames: '[name].js',
            format: 'iife',
          },
          {
            ...baseCustomOutput,
            chunkFileNames: (chunk: PreRenderedChunk) =>
              getChunkFilename(chunk, 'min.js'),
            entryFileNames: '[name].min.js',
            format: 'iife',
            plugins: [terser()], // because I only want one output to be minified
          },
        )
      }
    },
  },
})

Logs
No response

Hi,
I can't understand why you want to do this, can you explain more?
dependencies and peerDependecies should be marked as external
For example, You have ms package in your dependencies and also want to be inlined.
But when the User wants to install your package npm install @emendoza2/pkg the ms package code will exist two time

ms package will be added to node_modules
And it also exists/inlined in the package you created

Use devDependencies instead
Example: nuxi package
package.json - build.config


Implement Income and Spend periods chart

[x] Implement positive and nagetive stacked bar chart
[x] When hovering over the bar, show the detail data in the tooltip

Figma link
Preview

[ ] Add subtitle to annotations(Income&Output)
[ ] Move the color annotations to the bottom of the chart

Figma link
Preview


fix: flag name in documentation

Hi,
There is a small mistake in the documentation. The flag "fallback-pull-secret" has a wrong name: "fallback-image-pull-secret". Which leads to "Error: unknown flag" when copy+pasted into the flags used to run the service.
See the error here:
time="2024-07-09T12:00:36Z" level=info msg="spawning process: [/usr/local/bin/sbom-operator --dtrack-api-key=[...] --dtrack-base-url=[...] --fallback-image-pull-secret=[...] --format=cyclonedx --targets=dtrack --verbosity=debug]" app=vault-env
Error: unknown flag: --fallback-image-pull-secret
Usage:
  sbom-operator [flags]
[...]
Flags:
  -c, --config string                                 Path to the config-file.
 [...]
      --fallback-pull-secret string                   Fallback-Pull-Secret
[...]

Thanks for the finding this and this PR!!


childOutpipe should be childCommand

https://github.com/Qard/onchange/blob/1e13588218be9958d55f7a574cc855ab7685e57a/index.js#L74

Thanks! Resolved with https://github.com/Qard/onchange/commit/1e8ad66d883ded6850adc34149b41197d1b4de53.


[hotfix] [docs] fix  mistake about Sample code in Concepts & Common API

Brief change log
fix  mistake about Sample code in Concepts & Common API
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
none
Documentation
none

merging.


How do I enable MQTT for Neolink?

Cant see where I should be putting ./neolink mqtt --config=neolink.toml to enable MQTT?

@kohkohwastaken please update to 0.0.5 and select mqtt within the addon configuration.

@kohkohwastaken please keep that in mind: https://github.com/dm82m/hassio-addons/issues/10#issuecomment-1510172039


Initial transpose table (#22)

@tgrosinger it's definitely not the prettiest code (due to the need to ignore the delimiter row on both read and write being quite confusing, but I've been a bit strapped for time recently and haven't been able to dive into this code gain. It works well, so let me know what you think.
The main thing that would really help readability for this is if we could (before any computation) just remove the delimiter row flat out. If you have a decent idea of an approach to do that, I'd love to know how. Alternatively, if you wanted to make any changes in my PR, I've granted you full permissions :)

Note: happy to help with the obsidian plugin development for this as well. I assume we'll need an icon, which would really be the hardest part imo. I tested this through your advanced-tables obsidian plugin, so let me know if you'd like some help with that too.

@tgrosinger as I see that you are still active in this plugin, would you consider to take a look at this PR?
@mochsner do you still use Obsidian with the latest version and your plugin? Your repo has not received any new commit for 3 years. I'm not sure if it still works

Merged! Thank you.

@ooker777 I do still actively use, but not with my changes side-loaded, as my use case for it has gone done outside of previously company I was working at. Glad to know it sounds like it still works :smile . Hope you guys are able to get a UI option into the actual tables plugin some point soon too!

P.S. just saw the change, and congrats on the new role @tgrosinger - well deserved


Update scalajs-test-interface to 1.15.0

About this PR
📦 Updates org.scala-js:scalajs-test-interface from 1.12.0 to 1.15.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-js", artifactId = "scalajs-test-interface" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-js", artifactId = "scalajs-test-interface" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, version-scheme:semver-spec, commit-count:1

Superseded by #324.


Added the run_forever method

Added a little method that saves a couple lines of code when you want to automatically reconnect the websocket.

For future reference, also bump the version number in pyproject.toml.


Incorrect reference to workOffline in Quick Start docs

In the Quick Start section of https://cloud.spring.io/spring-cloud-contract/, workOffline is mentioned in the second-from-last code block and the paragraph of text immediately below that. However workOffline is not a valid argument to the AutoConfigureStubRunner annotation, at least for the Spring Cloud Contract version used by default in the Quick Start (2.0.0 M6).
I believe it should instead use stubsMode = StubRunnerProperties.StubsMode.LOCAL.

The property will change in 2.0.0. In the aforementioned page we reference a latest GA version. Anyways thanks for reminding about this


signinSilent throws error: End-User authentication is required

Hi,
I tried to implement silent review but got this error thrown: ``````

dup: #698


EditorResourcePicker resource name is cut off on both sides when too long

Godot version
c630c20
System information
Windows 10 x64
Issue description

This is problematic in some cases as the beginning is usually the most important part:

I didn't check if it's EditorResourcePicker issue or OptionButton in general. Maybe some default has changed.
EDIT: Looks like some clipping problem. Here's 3.x for comparison:

It's being cut only on the right.
Steps to reproduce

Add some resource with long name to a node
See that the name is cut on both sides

Minimal reproduction project
No response

Actually a duplicate of #59073


supported Azure PowerShell versions are incorrect

File: themes/default/content/registry/packages/azure-native/api-docs/resources/azurepowershellscript/_index.md
Current supported Azure PowerShell versions are: '2.7,2.8,3.0,3.1,3.2,3.3,3.4,3.5,3.6,3.7,3.8,4.1,4.2,4.3,4.4,4.5,4.6,4.7,4.8,5.0,5.1,5.2,5.3,5.4,5.5,5.6,5.7,5.8,5.9,6.0,6.1,6.2,6.3,6.4,6.5,6.6
1.7.0 as explicited in the documentation no longer works
Also: retentionInterval: "PT7D" doesn't work,  it should be PT168H

Thanks for reporting this. We automatically generate this documentation from Microsoft's API specification and examples. I've filed https://github.com/Azure/azure-rest-api-specs/issues/17137 to track this upstream


add location, line and column to PostBlit

By the way I have a question:
ParsePostblit has:
        expect(tok!"this");
        expect(tok!"(");
        expect(tok!"this");
        expect(tok!")");

but the ParsePostblit caller does already the lookup:
            if (startsWith(tok!"this", tok!"(", tok!"this", tok!")"))
                mixin(parseNodeQ!(`node.postblit`, `Postblit`));

Could the 4 expect be replaced by index += 4 ? A few branches could be avoided in this case.

Never mind the question, it's clear that the four expect are not needed. IN no other places the parser expects more than one time.


bug: fast typing impossible due to race condition / performance

Edit: The "race condition"/"poor performance" in the title is just my best guess at what's going on. I really have no idea...
'### Did you check docs and existing issues?

[X] I have read all the vscode-neovim docs
[X] I have searched the existing issues of vscode-neovim
[X] I can reproduce the issue with an empty init.vim/init.lua and no other vscode extensions (when applicable)

Neovim version (nvim -v)
0.9.2
Operating system/version
Windows 11
Describe the bug
Unable to determine if this is a vscode-neovim specific issue, code completion or combination of the two.
I have both NeoVim and code completion/intellisense/whatever via the C# extension enabled. I'm not sure exactly what's happening but when typing quickly the autocomplete UI appears and disappears and some combination of NeoVim action and autocomplete action both trigger in response to pressing return or esc or some other key.
The result is often the code I've just typed being inserted twice with some corrupt attempt at autoformatting or just random code from the autocomplete being vomited into the text editor.
I'm spending more time correcting the damaged caused than actual coding.
Because it only happens when I'm typing quickly it's difficult to figure out exactly what's going wrong. Just code vomit everywhere.
It "feels" like some kind of race condition/fight is taking place between neovim and the autocomplete, with both being triggered by the same key press (e.g., return to start a new line being hijacked by autocomplete incorrectly, or an internal buffer of neovim being dumped multiple times into the document).
Steps To Reproduce

Install VSCode
Install NeoVim
Install vscode-neovim
Install C# Dev Kit extension
Disable all but the 'C#' extension among those installed by step 4 (optional)
Try touch typing code in a C# file
Observe a combination of random code and duplicate copies of what you just typed being dumped into the editor as you type

Expected Behavior
Text I type and intentional autocomplete/snippets/whatever should be inserted into the editor. Random code and duplicate copies of what I type should not.

Not sure what's going on... vscode-neovim should really not be doing anything during insert mode. My only guess is somehow the document change sync is stepping on your typing.

I'm also seeing this. Sometimes changes made in insert mode are duplicated. I couldn't manage to find a way to reliably reproduce it though. It happens about once every five inserts.

Similar issue on my end, sometimes when exiting insert mode any added text is duplicated. On my side, it happens very frequently / most of the time.

I am having a similar issue to what is described here. I have a very repeatable case. Happens every single time I have tried. Here is a screen recording:
https://github.com/vscode-neovim/vscode-neovim/assets/286092/be1628cb-0737-46df-99cc-603a8a76a361
When I entered insert mode I started typing from 4 lines above. When I finish what I am doing, I hit ESC. It does feel like there is a race condition related to how soon I press ESC, though I have a decent window. It is as though if I wait long enough for the LSP to check and highlight everything then I can hit ESC safely. Otherwise, I get duplication.
It is very hard to make this happen if I am just inserting a single line of code then going back to Normal mode.
Hope that helps!

@d3chapma can you reproduce with empty init.vim?

Hmm... Initial test indicates no. That seems to fix it. I will try running with an empty config and see how I fair.
I had noticed that suggestion in the docs but had forgotten to do it. Thanks!

I built the app myself from master and that seemed to have fixed the issue. Maybe #1581 fixed it? I'm also using custom init.vim, with plugins

Interesting. If someone has this problem, please share your nvim config if possible. This may not be a matter of speed.

I had the same issue. It seems that my init.lua config is somehow conflicting with the Neovim extension and VSCode. Not sure how, but I managed to solve this issue by opening and checking the Neovim Clean option in VSCode user settings.
Screenshot of the relevant setting that I changed

Issues must be reproduced with empty init.lua.