rexray: upgrade to v0.11.1 [Backport to 1.10]

Backport of https://github.com/dcos/dcos/pull/2882 to 1.10.
High-level description
What features does this change enable? What bugs does this change fix?
This PR bumps REX-Ray from v0.9.0 to v0.11.1. It configures REX-Ray to operate in DOCKER_LEGACY mode as the newer version of REX-Ray switched to CSI-based logic. The REX-Ray developers seem to agree as REX-Ray's master branch was recently switched to DOCKER_LEGACY by default: https://github.com/rexray/rexray/commit/6162a4c0a35255414e0fb82e18a8ed44800d5749.
This PR also improves the delete_ec2_volume.py cleanup script by adding logging and better error handling.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS-3597 Upgrade REX-Ray to v0.11.1

Related tickets (optional)
Other tickets related to this change:

DCOS-37441 Triage integration test failures for REX-Ray upgrade
DCOS_OSS-2310 REX-Ray integration test is flaky after version bump

Checklist for all PRs

[x] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here: This bump was designed to introduce no new test or flakiness. Existing tests should keep working at their current level of flakiness (sad).
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): rexray
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

This repo has @mesosphere-mergebot integration. You can interact with the following commands.
@mesosphere-mergebot override-status
@mesosphere-mergebot merge-it
@mesosphere-mergebot label [Ready For Review |Holding |Request For Comment |Ship It |Work In Progress]
@mesosphere-mergebot bump-ee

PR creators can apply one of  [Ready For Review |Work In Progress]. Owners can apply any label.

@mesosphere-mergebot bump-ee

This is failing with:
Jun 04 13:39:20 ip-10-0-1-104.us-west-2.compute.internal rexray[5837]: error: service startup failed: agent: mod start failed: invalid implied sock file: /run/docker/plugins/rexray.sock: open /run/docker/plugins/rexray.sock: no such file or directory

This was fixed but never backported to 1.11 or 1.10:
https://github.com/dcos/dcos/pull/2593/commits/0b66b574f27005c41b5eaeb2b6f2261d6b575113#diff-b4738aec95eb5d18a80de948ec4ce039R16

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee


Don't write unrequested report in check_placement

Describe the bug
In check_placement the code has:
  set file_name "failures_report.json"
  if { [info exists keys(-report_file_name) ] } {
    set file_name $keys(-report_file_name)
  }

This means failures_report.json is dumped in the working directory whenever no report is requested.
Expected Behavior
Please change this to not write anything if -report_file_name is not used.
Environment
head of master

To Reproduce
as above
Relevant log output
No response
Screenshots
No response
Additional Context
No response

@eder-matheus FYI

aside: please also make an ORFS PR to use -report_file_name

@mina1460 eta?

@maliberty
today


Can't create binary

hi,
I'm no go expert but I followed your instructions and it does not build:
`[root@localhost ~]# mkdir go
[root@localhost ~]# cd go
[root@localhost go]# git clone https://github.com/hnlq715/nginx-vts-exporter.git
Klone nach 'nginx-vts-exporter'...
remote: Counting objects: 511, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 511 (delta 0), reused 2 (delta 0), pack-reused 507
Empfange Objekte: 100% (511/511), 18.18 MiB | 585.00 KiB/s, done.
Löse Unterschiede auf: 100% (237/237), done.
[root@localhost go]# cd nginx-vts-exporter/
[root@localhost nginx-vts-exporter]# make

formatting code
can't load package: package /root/go/nginx-vts-exporter: cannot find package "/root/go/nginx-vts-exporter" in any of:
/usr/lib/golang/src//root/go/nginx-vts-exporter (from $GOROOT)
/root/go/src//root/go/nginx-vts-exporter (from $GOPATH)
make: *** [format] Fehler 1
[root@localhost nginx-vts-exporter]#
`

You should clone nginx-vts-exporter into $(GOPATH)/src :-)

thx will try it at work today

thx build runs find but still the samle like in #32


Task1: Installed Kali Linux and shared the screenshot

Hey @Kanakaraju26
PR Template is not followed. Kindly follow the template & edit it again for consideration as a valid pull request.
Thanks for contributing in OpenCode'24 ✨✨!


Runtime error issue

Describe the bug
A clear and concise question regarding your extraction. Please check FAQ section, PyRadiomics issues and PyRadiomics Slicer Discourse to check if your question has been encountered before. If so, but you still require additional help, please reference related issues.
PyRadiomics configuration
Add any customization you applied here (i.e. the content of the parameter file used)
PyRadiomics log file
If available, add section of the PyRadiomics log related to your question. For help on setting up logging, see the online documentation
To Reproduce
Steps to reproduce the behavior:
Version (please complete the following information):

OS: [e.g. iOS]
Python version: [e.g. 3.6]
PyRadiomics version [e.g. 2.2.0]

Additional context
Add any other context about your question here.

When trying to run the code, I am getting the following error:
RuntimeError: Excpetion thrown in SimpleITK LabelStatisticsImageFilter_Execute: Code\BasicFilters\SRC\sitkLabelStatisticsImageFilter.cxx:134: sitk::ERROR: Both images for LabelStatisticsImageFilter don't match type or dimension!
During handling of the above exveption, another exception occurred:
ValueError: Image/Mask datatype or size mismatch. Potential fix: enable correctMask
I have changed Force2D to True and correctMask to true but it still isn't working. Any ideas on what I should do next?

What are the errors when you enable correctMask setting?


Create documentation website to gather components and use cases

Hey @simjak, could you please somehow add some description here? I would love to work on this.


⚠ Bofrost.ch has degraded performance

In d2710ce, Bofrost.ch (https://www.bofrost.ch) experienced degraded performance:

HTTP code: 200
Response time: 2742 ms

Resolved: Bofrost.ch performance has improved in 59dd7ce after 7 minutes.


added mouse wheel zooming to the FrameGraphView

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

Codecov Report

Merging #645 into master will decrease coverage by <.01%.
The diff coverage is 13.33%.

@@            Coverage Diff             @@
##           master     #645      +/-   ##
==========================================
- Coverage   17.56%   17.56%   -0.01%
==========================================
  Files         216      216
  Lines      125122   125136      +14
  Branches    12088    12089       +1
==========================================
+ Hits        21983    21985       +2
- Misses     102274   102286      +12
  Partials      865      865

Flag
Coverage Δ

#2017
17.56% <13.33%> (-0.01%)
:arrow_down:

#Debug
17.56% <13.33%> (-0.01%)
:arrow_down:

#Release
?

Impacted Files
Coverage Δ

src/PerfView/StackViewer/StackWindow.xaml.cs
25.72% <0%> (-0.05%)
:arrow_down:

src/PerfView/StackViewer/StackWindow.xaml
100% <100%> (ø)
:arrow_up:

...rc/PerfView/StackViewer/FlameGraphDrawingCanvas.cs
16.77% <12.5%> (-0.25%)
:arrow_down:

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 50d859d...3fca2fa. Read the comment docs.

@adamsitnik

Unless Adam raises an objection today, I will merge this.

@vancem I just cloned @RomanKalachik fork and tested the zooming.
It looks very promising, however there are few things that need to be improved before we can merge it:

When Flame Graph is zoomed-in, the tooltips don't work. If I zoom in, I wan to know what I am looking at. Tooltips are a must have.
Zooming has no limit: you can zoom out to infinity. I think it would be nice to limit zoom out to 100% of the original size.

To move the Flame Graph when it's zoomed in I need to use scrollbars. It would be nice if I could just move it when my left mouse button is pressed and I am moving the mouse.

@RomanKalachik thank you for this PR! Could you please fix it so we can merge it?

@adamsitnik , Thanks for the review! Sure, I will try to fix those issue in the next couple of days.

Closing as we now have mouse wheel zooming on flamegraphs.


Refactor Repo2Docker.fetch method to not need be passed its own members as arguments

This is a tiny clean-up: Since fetch() is only called inside the
class, and two of the three arguments in that call are attributes of
self, there is no need to pass them as extra arguments.
To not break the API, the parameters in the method definition are now
set to a default of None; if these are used with their default,
they'll be set to the respective self attributes. Note that this
breaks behaviour where the self attribute is not None,
but None is explicitly passed for the respective parameter.

Notes and further food for thought:

I've put this here as a suggestion. The change may not be deemed necessary.
As the last sentence states, this may break external code. A quick search through related repositories (binder, binderhub) does not reveal any calls to fetch(). Most of the repo2docker use seems to be through its command line arguments.
Is there any use for calling fetch() with different arguments than the self attributes? If not, fetch() should probably become a private method _fetch() and have its last two parameters completely removed.

This makes sense, I wish it would have been reviewed and accepted in this projects infancy. At this point, I don't dare go for it as it is just a smaller code cleanup but could be possibly breaking for project external code as you also mention.

I've put this here as a suggestion. The change may not be deemed necessary.
As the last sentence states, this may break external code. A quick search through related repositories (binder, binderhub) does not reveal any calls to fetch(). Most of the repo2docker use seems to be through its command line arguments.
Is there any use for calling fetch() with different arguments than the self attributes? If not, fetch() should probably become a private method _fetch() and have its last two parameters completely removed.

I appreciate the thought you put into this PR, highlighting key parts of whats relevant for a person reviewing this!! I'm glad to see your still active in GitHub and open source! :heart: :tada:


Add Jax to ML image?

Jax is becoming very important / useful to us. Would it be easy to add it to the ML image?

Jax is becoming very important / useful to us. Would it be easy to add it to the ML image?

Sure, what is jax used for? I'm not sure the ML image has been actively used much recently. Previously @jhamman and @jsadler2 helped decide what packages are in there. Note that it currently is also missing many of the geoscience packages that have recently been added to pangeo-notebook. But the environment solving has been complicated in the past, so generally the fewer the packages the better it seems.
In any case, to add jax, just create a PR adding a line here:
https://github.com/pangeo-data/pangeo-docker-images/blob/7e9a10925bb5cf2574b8effd1fd9c81ecad8c6e3/ml-notebook/environment.yml#L27

@rabernat would be curious to know what you are going to use this for?
I'm guessing something related to this:
https://pymc-devs.medium.com/the-future-of-pymc3-or-theano-is-dead-long-live-theano-d8005f8a0e9b

closed by #196


Add missing condition for aborting from Tile only pattern.

The tile only pattern should not apply when there are dependent linalg
operations. The TileAndFuse should apply for those. Add this missing
condition.

Is it easy to add a test?

No, not really. Cause it isnt failing and it depends on the order in which the patterns are applied.


put-file's flags are a little confusing when adding directories recursively

Here are a few confusing things:

pachctl put-file sessions master -c -r -f ./2017-03-28 will add the files under ./2017-03-28/files.json in the commit as 2017-03-28/2017-03-28/files.json.
pachctl put-file sessions master 2017-03-28 -c -r -f ./2017-03-28 will add the files under ./2017-03-28/files.json in the commit as 2017-03-28/files.json.
pachctl put-file sessions master -c -r 2017-03-28/ just stalls there, I guess awaiting input from stdin. But tihs doesn't make sense for recursively loading directories.

I'd propose a pachctl put-dir that would do the recursive thing automatically, and would unclutter the put-file command.
pachctl put-dir [repo] [branch] localpath [dstpath]

so that:

pachctl put-dir repo master ./subdir would copy ./subdir/file.json to subdir/file.json inside the commit.
pachctl put-dir repo master ./subdir / would copy ./subdir/file.json to file.json inside the commit.
pachctl put-dir repo master ./subdir . would copy ./subdir/file.json to file.json inside the commit.
pachctl put-dir repo master ./my-subdir subdir would copy ./my-subdir/file.json to subdir/file.json inside the commit.

This is just a proposition.. but it seems to me that cluttering put-file with directory operations makes both more confusing.

pachctl put-file sessions master -c -r -f ./2017-03-28 will add the files under ./2017-03-28/files.json in the commit as 2017-03-28/2017-03-28/files.json.

Ugh, this is a silly bug, we'll fix this. The path should clearly be just: 2017-03-28/files.json

pachctl put-file sessions master 2017-03-28 -c -r -f ./2017-03-28 will add the files under ./2017-03-28/files.json in the commit as 2017-03-28/files.json.

This one seems  reasonable to me, if you explicitly a file name in a recursive call that gets appended as a prefix to all of the files it finds in the directory.

pachctl put-file sessions master -c -r 2017-03-28/ just stalls there, I guess awaiting input from stdin. But tihs doesn't make sense for recursively loading directories.

This one is admittedly a bit confusing, I think it's not too terrible to have a -r flag do nothing in the case of putting a single file, recursive linux commands like du can also be called on single files and have no effect. I think one easy thing we could do to make this less confusing is print out a message that it's waiting for input from stdin so people know what's going on.

The idea of having put-dir does seem interesting to me. It would make both commands a bit less cluttered and also probably increase the chances that the commands are implemented correctly since we've had several problems caused by how much functionality is packed into put-file. What do others think?

stale


Contact helpers

5 helpers (so far) need to be contacted with ome info regarding resbaz volunteering
we have docs on this from previous years?

What do we need helpers to do???

Virtual helpers: answer people in the comments and help facilitate/host presentations?
in-person helpers: help participants with bugs, downloads and installations to keep flow of presentation; answer logistical questions?

Contacted!


Failed to detect changes to certain options when creating a resource.

What happened?
When creating a Subnet in GCP, I created it by adding secondary IP ranges. After that, when I removed the option and applied it again, it did not detect the change.
Example
Create Subnet with Secondary IP Ranges.
subnet = compute.Subnetwork(
    name="test-subnet",
    resource_name="test-subnet",
    network=network.self_link,
    ip_cidr_range="<IP_ADDRESS>/24",
    region="asia-northeast3",
    private_ip_google_access=True,
    secondary_ip_ranges=[
        compute.SubnetworkSecondaryIpRangeArgs(
            range_name="pod-range",
            ip_cidr_range="<IP_ADDRESS>/20",
        ),
        compute.SubnetworkSecondaryIpRangeArgs(
            range_name="service-range", ip_cidr_range="<IP_ADDRESS>/24"
        ),
    ],
)

Create Subnet without Secondary IP Ranges.
subnet = compute.Subnetwork(
    name="test-subnet",
    resource_name="test-subnet",
    network=network.self_link,
    ip_cidr_range="<IP_ADDRESS>/24",
    region="asia-northeast3",
    private_ip_google_access=True,
)

Output of pulumi about
❯ pulumi about
CLI
Version      3.122.0
Go Version   go1.22.4
Go Compiler  gc
Plugins
KIND      NAME    VERSION
resource  gcp     7.32.0
language  python  unknown
Host
OS       darwin
Version  14.5
Arch     arm64
Additional context
No response
Contributing
No response

I found the cause. It seems that secondary_ip_ranges option is not tracking state because default is None. It works fine when passing empty list. But I don't know if this is the intended behavior of pulumi.
subnet = compute.Subnetwork(
    name="test-subnet",
    resource_name="test-subnet",
    network=network.self_link,
    ip_cidr_range="<IP_ADDRESS>/24",
    region="asia-northeast3",
    private_ip_google_access=True,
    secondary_ip_ranges=[],
)

Hey @byeongryul-cho, thanks for filing the issue here and glad you figured out the workaround. You are correct that the setting the value to empty is the right way to do this.
Unfortunately this is indeed working as intended even if it awkward. The technical reason for that is that the GCP tf provider, which is being used by pulumi here under the hood defines the resource as an Optional + Comptued: https://github.com/hashicorp/terraform-provider-google/blob/1b0d5f23f66a5e00ba3070e048f17d3e80001955/google/services/compute/resource_compute_subnetwork.go#L243
This means that due to a limitation in TF, when this is set to null/unset, the provider keeps the old value from state: https://github.com/pulumi/pulumi-terraform-bridge/issues/2152.
A detail here is that the TF provider has a note about this behaviour on the property and we seem to have lost it in our docs. I'll file an issue about that.


added share your game popup

added a popup for sharing your games to the feed

https://github.com/user-attachments/assets/accd82c6-aa1e-48e9-bd38-73799110cc00


Bugfixes

Fixes a couple of uninitialzed warnings and a call to a sub which doesn't exist.

Thanks!


It should be possible to give a token a nickname to show

Reported by simo on 12 Dec 2013 16:07 UTC
Some servers give out unintelligible names that are hard to distinguish.
The user should be allowed to give a nickname to be displayed instead of the UUID so he can easily recoginze the right token.
Bonus point if the background of the tile can also be changed to a themed color for even easier recognition.

Modified by npmccallum on 13 Dec 2013 14:52 UTC

Comment by npmccallum on 28 Mar 2014 17:58 UTC
Renaming support is now present here: [acd870dce4acebb629b88c19952a5ab280b7a2c3/android]
This will be included in the next release.

Modified by npmccallum on 19 Aug 2014 14:00 UTC


Failing to generate ACME certificates

Hello, currently I have a Kong API Gateway running through my single node docker swarm with a few API’s behind it, I’m totally able to reach each of the trough each route, but only through HTTP.
I have installed the ACME plugin, although it’s not clear to me how I should configure it in order to trigger the creation of the certificates for each service.
If I run:
curl http://<IP_ADDRESS>:8001/acme -d host=mydomain.com -d test_http_challenge_flow=true
It returns:
{"message":"sanity test for host mydomain.com passed"}
But, if I try
curl http://<IP_ADDRESS>:8001/acme -d host=mydomain.com
It returns:
{"message":"failed to update certificate: could not create certificate: challenge invalid: http-01: invalid: Invalid response from http:\/\/mydomain\/.well-known\/acme-challenge\/cfbSYzt39OWFm9bObeoL3T7gidAVLRmn1dm7iscz15s [myserverip]: 404"}
This is the container log:
_kong.2.u8d8srbp9lcy@vps-2c1ec9df    |  2020/12/11 15:28:38 [warn] 21#0: *5536 [lua] http-01.lua:54: serve_challenge(): no corresponding response found for YCRxFSgSzaaWlT3kohB-WzxWiVpExHRacdFNXy3xroM, client: <IP_ADDRESS>, server: kong, request: "GET /.well-known/acme-challenge/YCRxFSgSzaaWlT3kohB-WzxWiVpExHRacdFNXy3xroM HTTP/1.1", host: "mydomain.com
kong_kong.2.u8d8srbp9lcy@vps-2c1ec9df    |  <IP_ADDRESS> - - [11/Dec/2020:15:28:38 +0000] "GET /.well-known/acme-challenge/YCRxFSgSzaaWlT3kohB-WzxWiVpExHRacdFNXy3xroM HTTP/1.1" 404 27 "-" "Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org)"

@iacapuca could you share your kong/kong enterprise version and the plugin's config?

My Kong is not the enterprise one.
{   "created_at":<PHONE_NUMBER>,   "id": "ebb6e3b3-6120-47bc-b962-b83c6f69f6a2",   "tags": null,   "enabled": true,   "protocols": [     "grpc",     "grpcs",     "http",     "https"   ],   "name": "acme",   "consumer": null,   "service": null,   "route": null,   "config": {     "api_uri": "https://acme-v02.api.letsencrypt.org/directory",     "storage": "shm",     "storage_config": {       "redis": {         "auth": null,         "port": null,         "database": null,         "host": null       },       "shm": {         "shm_name": "kong"       },       "vault": {         "host": null,         "port": null,         "token": null,         "timeout": null,         "https": false,         "tls_server_name": null,         "kv_path": null,         "tls_verify": true       },       "kong": {},       "consul": {         "host": null,         "port": null,         "token": null,         "timeout": null,         "https": false,         "kv_path": null       }     },     "cert_type": "rsa",     "tos_accepted": true,     "fail_backoff_minutes": 5,     "domains": [       "mydomain.com"     ],     "renew_threshold_days": 14,     "account_email": "myemail"   } }
And this is my compose file(which I use to deploy the stack):
`
version: "3.8"
services:
kong-database:
image: postgres:9.6
environment:
- POSTGRES_USER=kong
- POSTGRES_DB=kong
- POSTGRES_PASSWORD=kong
ports:
- "5432:5432"
networks:
- kong-net
kong-migration:
image: kong:latest
depends_on:
- kong-database
environment:
- KONG_DATABASE=postgres
- KONG_PG_HOST=kong-database
- KONG_PG_USER=kong
- KONG_PG_PASSWORD=kong
command: kong migrations bootstrap
networks:
- kong-net
kong:
image: kong:latest
depends_on:
- kong-database
- kong-migration
deploy:
replicas: 3
environment:
- KONG_DATABASE=postgres
- KONG_PG_HOST=kong-database
- KONG_PG_USER=kong
- KONG_PG_PASSWORD=kong
- KONG_PROXY_ACCESS_LOG=/dev/stdout
- KONG_ADMIN_ACCESS_LOG=/dev/stdout
- KONG_PROXY_ERROR_LOG=/dev/stderr
- KONG_ADMIN_ERROR_LOG=/dev/stderr
- 'KONG_ADMIN_LISTEN=<IP_ADDRESS>:8001, <IP_ADDRESS>:8444 ssl'
- KONG_LUA_SSL_TRUSTED_CERTIFICATE=/etc/ssl/cert.pem
ports:
- "80:8000"
- "443:8443"
- '<IP_ADDRESS>:8001:8001'
- '<IP_ADDRESS>:8444:8444'
networks:
- kong-net
networks:
kong-net:
external: true
`

thanks you @iacapuca which version of kong gateway are you running?

thanks you @iacapuca which version of kong gateway are you running?

The latest one, 2.2.1

Ok, then it shouldn't have the cache bug. Are we running Kong in multiple nodes/containers? Since I saw you are using the shm storage and it won't propagate between different clusters. If so try to use kong storage.

Ok, then it shouldn't have the cache bug. Are we running Kong in multiple nodes/containers? Since I saw you are using the shm storage and it won't propagate between different clusters. If so try to use kong storage.
(I do saw a replica: 3 so i assume that's the case)

I'm so sorry, I just realized i was using shm, I have just changed to kong and it did worked just fine.
If I may ask, what would happen if I bring my Kong containers down? Would I still have some persistence of the certs after and bring them up again?

Would I still have some persistence of the certs after and bring them up again?

@iacapuca It will, with database mode the created cert are stored in Certificate and SNI entity, it will be persistent in kong's database.


[FEATURE]: PowerStore Sync / Metro for Block - CSM Replication

Describe the solution you'd like
Enable the functionality of volume replication to another PowerStore node synchronously, including ESX metro volumes, only for Block.
The feature should enable

Metro replication capabilities.
Array native metro replication.
Metro Volume and Sync replication.

Feature merged into main. Resolving issue.


Make static library

thanks for your great job, is it possible to compile a chdb static library?

It's possible theoretically without jemalloc.
With a static lib, chdb-go could be much clean.
@nmreadelf might be interested to do that.

I have had partial success build libchdb as a static library in actions but the resulting size was quite prohibitive....

and a Windows EXE possible?  not the one run in WSL.

@l1t1 sorry i'm afraid not even clickhouse supports Windows builds

A static build

this is something we are trying to do

That bundled as a JDBC driver

clickhouse-jdbc-bridge is needed to run clickhouse jdbc table function

Ideally in the end windows support

ClickHouse dose not support Windows build. So, I'm afraid it will not possible to have a chDB Windows version without WSL


[6.x] Fixed broken hash config

The minimum value supported for time is 3, and the only supported number of threads is 1. It's a bug that PHP is silently allowing our bad config, and PHP 8.1 is stricter. See https://github.com/shivammathur/php-builder/issues/8. We should additionally deprecate the threads config, since it's essentially useless from what I can see?
I think this needs a review from someone on the PHP core team who knows more about this stuff.

This can't be right. :/
https://www.php.net/manual/en/function.password-hash.php#example-983


Fixed Undefined Index

Fixed the undefined index when using SERVER_ADDR, alternative to use HTTP_HOST too
Automatically trimmed whitespaces

Thanks for taking your time to help! It's always appreciated!


Datasets

Hello,I use your model to train my own datasets.In your experience , how many pictures to be trained can I get a correct result for parsing?

Recommended to use more than 10,000 images.

Thanks for your reply！ At present，all of the datasets are labeled by myself，i can't get so many pictures by internet or open sources. So if i create more datasets by rotating pictures or changing backgroud on the basis of existed pictures，will the parsing result be badly affected？
| |
冯琬婷
|
|
<EMAIL_ADDRESS>|
签名由 网易邮箱大师 定制
On 05/26/2020 20:47, Kevin.h wrote:
Recommended to use more than 10,000 images.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Get it！Thanks for your recommendation！
| |
冯琬婷
|
|
<EMAIL_ADDRESS>|
签名由 网易邮箱大师 定制
On 05/26/2020 22:00, Kevin.h wrote:
You can pretrain the model with LIP and fine-tune on your own dataset, and data argumentation is also useful for insufficient data.
PS. for more details, you can email me in Chinese<EMAIL_ADDRESS>—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


2.4

fixes #76

:tada: This PR is included in version 2.4.0 :tada:
The release is available on:

v2.4.0
GitHub release

Your semantic-release bot :package::rocket:


Parallelizing sem_agg and sem_top_k

Addressing #61

@sidjha1 any thoughts why the Multimodality CI test is failing?

@sidjha1 any thoughts why the Multimodality CI test is failing?

The test is flaky, so I wouldn't worry about it. You can rerun the job and I think it should pass. I'd have to look a bit at the logs but I don't think it's related to your change.

Checked the logs for the multimodality test, I think its related to this PR actually
=========================== short test summary info ============================
FAILED .github/tests/multimodality_tests.py::test_topk_with_groupby_operation[gpt-4o-mini] - KeyError: 0
======== 1 failed, 3 passed, 3 skipped, 2 warnings in 75.59s (0:01:15) =========

@sidjha1 fixed the failing test which was due to a bug in this PR, but that was failing for a different reason than my earlier comment. Looks like all tests are passing now.


Update README.md

Fix typo so that the example is correct

Merged! Thank you for your contribution. Much appreciated! 👍


Safari now supports lookbehind assertions

Safari started supporting lookbehind assertions starting in version 16.4.

I've tried to create a PR to fix lib/index.js but the repo won't let me create a new branch in remote.

PRs welcome!


Add Perlotto app

Perlotto app is a wrapper around google music web service that turns it in to desktop app.
Additional features:

Multimedia keys support
Last.FM support

Cool. Kinda like https://www.googleplaymusicdesktopplayer.com/


Remove hugectr inference

Remove hugectr inference backend;
Add installation of hps_torch in merlin-torch.

Do we really want to remove that?

Do we really want to remove that?

Yes, I checked with Yingcan. Could you review it again^^

/ok to test

The copied PR is merged


Fixed bin/console calls in shopware recipe

[ x ] Bug fix: Shopware bin/console calls with default bin/php and not with {{bin/php}}
I was running the recipe with {{bin/php}} = /opt/local/bin/php8.2 but my default cli version is php7.4 the deployment stopped caused of the wrong php version by calling bin/console directly.

Awesome, thanks @dahormez! <3


[AVOCADO-206] Move CLI classes to correct directory.

Resolves #206.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/avocado-prb/164/
Test PASSed.


Content missing after a youtube embed url

All the pages using a youtube shortcode don't render content after the embedded video.

/asssign @lucperkins


Hover Effect Left

Make it known to user when left button is hovered over/off

This issue was moved to kroehl/MusicDiscoveryApp#10


Refactor the Swap example to swap arbitrary ERC-20 and swap from EVM to Bitcoin

Switched back to providing a target ZRC-20 address instead of chain ID, because a user might want to swap to a specific ZRC-20 (like USDC) on a destination chain
Used npx hardhat omnichain Swap targetToken:address recipient:address to leverage templating
Remove MinAmountOut as it doesn't contribute to the example and can be easily added (we've been using 0 as a value anyways).
Right now you need to provide a contract address of the target ZRC-20, because we need a way to convert human readable token name to a ZRC-20 address.
Added support to swap from EVM to Bitcoin

Related docs: https://github.com/zeta-chain/docs/pull/189

Testing BTC: 1c15ef97b09f1c6c8f922a791c33d6a4ae8be9bc77f6965582379d1f5b8bcca1

Testing BTC:
https://blockstream.info/testnet/tx/12c778438891f7f1166294234d3b74e6c5c16f111aeaa16e17381dfb203dcfbb

BTC swap seems to be working:
npx hardhat cctx 7dc7942a1e6c4d1532dadd1ec1c2cac1a7302ef04d4845a15935c9147a48f9b4
✓ CCTXs on ZetaChain found.

✓ 0x370f41bf277f8905d59e8ea9ebf1006d4609d4681ac0a735b21e23f0e3943971: 18332 → 7001: OutboundMined (Remote omnichain contract call completed)
✓ 0x804eb819dda20ed6dbe003ee2cb0bb8d9a97cf452bc62f82ed3e8c4355075fe7: 7001 → 5: OutboundMined

I've made a few tweaks to support swapping from EVM chains to Bitcoin by changing the expected second value in the message to bytes. Now if you want to swap EVM -> EVM you send a hex address, which will be stored as bytes. If you swap from EVM -> you send a long bech32 address encoded as ASCII bytes, it is also stored as bytes in the contract.
BTC to gETH
npx hardhat send-btc --amount 0.001 --recipient tb1qy9pqmk2pd9sv63g27jt8r657wy0d9ueeh0nqur --memo cC02751bAA435E9A5cF3bd22F96a21d7C002E15013A0c5930C028511Dc02665E7285134B6d11A5f42cD3D070aE1BD365909dD859d29F387AA96911e1

npx hardhat cctx b52b9025fd0707f9922b2f52f7dd7a944454dedcd6248443bb7bb8652cde7017
✓ CCTXs on ZetaChain found.

✓ 0x5e5f157d7255f97d13e646f9e1809bb27df82cb33855f394d9798231b44c0a82: 18332 → 7001: OutboundMined (Remote omnichain contract call completed)
✓ 0x186b582201d3abbae0d5f19aa8f2569cd579296fd731183bf4d409013cb160b3: 7001 → 5: PendingOutbound  → OutboundMined

gETH to tMATIC
npx hardhat interact --contract 0xcC02751bAA435E9A5cF3bd22F96a21d7C002E150 --amount 0.1 --target-token 0x48f80608B672DC30DC7e3dbBd0343c5F02C738Eb --recipient 0x2cD3D070aE1BD365909dD859d29F387AA96911e1 --network goerli_testnet

npx hardhat cctx 0x7ebd2bff64cbc530c145a60e4830ba2ddc536bc62cf8c5566c900143b0e08baf
✓ CCTXs on ZetaChain found.

✓ 0x5082897440218490193a724a22b7ed3f8744760956d857199e76bf2453f901b2: 5 → 7001: OutboundMined (Remote omnichain contract call completed)
✓ 0x3aebbba04cd284d2e87b9c8414f6946bdf933efad45076aba7c691e5a32895ba: 7001 → 80001: PendingOutbound  → OutboundMined

## gETH to BTC

https://zetachain-athens.blockpi.network/lcd/v1/public/zeta-chain/crosschain/inTxHashToCctx/0xe247091341c92308652b96506309a1a9066e7d69eec810a92b0717a6cda45009

https://zetachain-athens.blockpi.network/lcd/v1/public/zeta-chain/crosschain/cctx/0xac248959e2858f557956539451f4d105e45002ece23e1c19c3dcd2d8ea88e13d

https://zetachain-athens.blockpi.network/lcd/v1/public/zeta-chain/crosschain/cctx/0x1243a5ee33d8b57c0bce5e69c16a45b984a3fbf846c0f6f9fdb7ecf42e60e20f

(CCTX tracking failed for this one, need to debug the toolkit, but this is not related)

@andresaiello please, review.

can we support to swap if specified source token address and destination token address ? and the amount represents amount of source token if specified.

@magj2006 the source token address is passed in the zrc20 param of the onCrossChainCall function:
https://github.com/zeta-chain/example-contracts/blob/b145cbf94f07e1e7b6e07334c88b5ba930af014b/omnichain/swap/contracts/Swap.sol#L29
Is there a reason why we would need to pass it explicitly?

@magj2006 the source token address is passed in the zrc20 param of the onCrossChainCall function:
https://github.com/zeta-chain/example-contracts/blob/b145cbf94f07e1e7b6e07334c88b5ba930af014b/omnichain/swap/contracts/Swap.sol#L27-L32
Is there a reason why we would need to pass it explicitly?

If I want to bridge USDC on goerli to USDC on bsc_testnet, how I pass parameters?  As I understand when we use command npx hardhat interact --contract 0xcC02751bAA435E9A5cF3bd22F96a21d7C002E150 --amount 0.1 --target-token 0x07865c6e87b9f70255377e024ace6630c1eaa37f --recipient 0x2cD3D070aE1BD365909dD859d29F387AA96911e1 --network goerli_testnet, source token is gETH, which is gasCoin of goerli and amount argument indicates the number of gETH, not of UDSC.

@magj2006 that's a good point! This, however, only requires changes to the interact task, not the contract itself. The reason I didn't do it yet is mostly because I want to decide on how to tell the task which token you want to swap. I think we can do something like this:
npx hardhat interact --contract 0xcC02751bAA435E9A5cF3bd22F96a21d7C002E150 --amount 0.1 --from usdc --to geth --recipient 0x2cD3D070aE1BD365909dD859d29F387AA96911e1 --network goerli_testnet

Created an issue for this: https://github.com/zeta-chain/example-contracts/issues/97

@magj2006 that's a good point! This, however, only requires changes to the interact task, not the contract itself. The reason I didn't do it yet is mostly because I want to decide on how to tell the task which token you want to swap. I think we can do something like this:
npx hardhat interact --contract 0xcC02751bAA435E9A5cF3bd22F96a21d7C002E150 --amount 0.1 --from usdc --to geth --recipient 0x2cD3D070aE1BD365909dD859d29F387AA96911e1 --network goerli_testnet

You are right. the hard point is how to calculate gas with USDC for this situation.


no MIME Type found on mediaMessage: voice.slk  or no MIME Type found on mediaMessage: voice.silk

As shown in the error report, my silk voice file is correct and can be sent through other social software, but I can’t send it in Wechaty. What is the specific problem?

+1


Cannot save model when use CSVLogger

🐛 Bug
When I set logger to CSVLogger, the ModelCheckpoint won't dump the ckpt for me, it shows an error.
My code is pretty heavy which cannot be fully shared.  You can follow my following codes to reporduce it (I skip the dataloader part, which is irrelevant).
To Reproduce
    checkpoint_callback = ModelCheckpoint(
        dirpath="test",
        save_top_k=5,
        verbose=False,
        monitor = "val_loss",
        save_last=True,
        save_weights_only=False
    )
    logger = CSVLogger("test", version="0")
    trainer = Trainer(logger=logger, checkpoint_callback=checkpoint_callback)
    trainer.fit(model, train_data, val_data)

A abstract class of my model is listed below (this is the only part contains self.log method, which I think it might be related to this issue):
class Spectrogram_based(Conditional_Source_Separation, metaclass=ABCMeta):

    @staticmethod
    def add_model_specific_args(parent_parser):
        parser = ArgumentParser(parents=[parent_parser], add_help=False)

        parser.add_argument('--n_fft', type=int, default=2048)
        parser.add_argument('--hop_length', type=int, default=1024)
        parser.add_argument('--num_frame', type=int, default=128)
        parser.add_argument('--spec_type', type=str, default='complex')
        parser.add_argument('--spec_est_mode', type=str, default='mapping')

        parser.add_argument('--train_loss', type=str, default='spec_mse')
        parser.add_argument('--val_loss', type=str, default='raw_l1')
        parser.add_argument('--unfreeze_stft_from', type=int, default=-1)  # -1 means never.

        return Conditional_Source_Separation.add_model_specific_args(parser)

    def __init__(self, n_fft, hop_length, num_frame,
                 spec_type, spec_est_mode,
                 conditional_spec2spec,
                 optimizer, lr,
                 train_loss, val_loss, hparams=None
                 ):
        super(Spectrogram_based, self).__init__(n_fft, hop_length, num_frame,
                                                optimizer, lr, hparams)

        self.n_fft = n_fft
        self.hop_length = hop_length
        self.num_frame = num_frame

        assert spec_type in ['magnitude', 'complex']
        assert spec_est_mode in ['masking', 'mapping']
        self.magnitude_based = spec_type == 'magnitude'
        self.masking_based = spec_est_mode == 'masking'
        self.stft = fourier.multi_channeled_STFT(n_fft=n_fft, hop_length=hop_length)
        self.stft.freeze()

        self.spec2spec = conditional_spec2spec
        self.valid_estimation_dict = {}
        self.val_loss = val_loss
        self.train_loss = train_loss

        self.init_weights()

    def init_weights(self):
        init_weights_functional(self.spec2spec,
                                self.spec2spec.activation)

    def training_step(self, batch, batch_idx):
        mixture_signal, target_signal, condition = batch
        loss = self.train_loss(self, mixture_signal, condition, target_signal)
        self.log('train_loss', loss, prog_bar=False, logger=True, on_step=False, on_epoch=True,
                 reduce_fx=torch.mean)
        return loss

    # Validation Process
    def on_validation_epoch_start(self):
        for target_name in self.target_names:
            self.valid_estimation_dict[target_name] = {mixture_idx: {}
                                                       for mixture_idx
                                                       in range(14)}

    def validation_step(self, batch, batch_idx):

        mixtures, targets, mixture_ids, window_offsets, input_conditions, target_names = batch

        loss = self.val_loss(self, mixtures, input_conditions, targets)

        self.log('raw_val_loss', loss, prog_bar=False, logger=False, reduce_fx=torch.mean)

        # Result Cache
        if 0 in mixture_ids.view(-1):
            estimated_targets = self.separate(mixtures, input_conditions)[:, self.trim_length:-self.trim_length]
            targets = targets[:, self.trim_length:-self.trim_length]

            for mixture, mixture_idx, window_offset, input_condition, target_name, estimated_target \
                    in zip(mixtures, mixture_ids, window_offsets, input_conditions, target_names, estimated_targets):

                if mixture_idx == 0:
                    self.valid_estimation_dict[target_name][mixture_idx.item()][
                        window_offset.item()] = estimated_target.detach().cpu().numpy()
        return loss

    def validation_epoch_end(self, outputs: List[Any]) -> None:
        for idx in [0]:
            estimation = {}
            for target_name in self.target_names:
                estimation[target_name] = get_estimation(idx, target_name, self.valid_estimation_dict)
                if estimation[target_name] is None:
                    continue
                if estimation[target_name] is not None:
                    estimation[target_name] = estimation[target_name].astype(np.float32)

                    if self.current_epoch > 1 and isinstance(self.logger, WandbLogger):
                        track = estimation[target_name]
                        if track.shape[0] > 40 * 44100:
                            track = track[44100 * 20:44100 * 40]

                        self.logger.experiment.log({'result_sample_{}_{}'.format(self.current_epoch, target_name): [
                            wandb.Audio(track, caption='{}_{}'.format(idx, target_name), sample_rate=44100)]})

        reduced_loss = torch.stack(outputs).mean()
        self.log('val_loss', reduced_loss, prog_bar=False, logger=True, on_step=False, on_epoch=True, sync_dist=True)
        print(reduced_loss)

    @abstractmethod
    def to_spec(self, input_signal) -> torch.Tensor:
        pass

    @abstractmethod
    def separate(self, input_signal, input_condition) -> torch.Tensor:
        pass

Errors shown
Traceback (most recent call last):
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 644, in run_train
    self.train_loop.run_training_epoch()
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/training_loop.py", line 564, in run_training_epoch
    self.trainer.run_evaluation(on_epoch=True)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 758, in run_evaluation
    self.evaluation_loop.on_evaluation_end()
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/evaluation_loop.py", line 100, in on_evaluation_end
    self.trainer.call_hook('on_validation_end', *args, **kwargs)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 1101, in call_hook
    trainer_hook(*args, **kwargs)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/callback_hook.py", line 183, in on_validation_end
    callback.on_validation_end(self, self.lightning_module)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/callbacks/model_checkpoint.py", line 212, in on_validation_end
    self.save_checkpoint(trainer, pl_module)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/callbacks/model_checkpoint.py", line 259, in save_checkpoint
    self._save_top_k_checkpoints(trainer, pl_module, monitor_candidates)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/callbacks/model_checkpoint.py", line 566, in _save_top_k_checkpoints
    self._update_best_and_save(current, epoch, step, trainer, pl_module, metrics)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/callbacks/model_checkpoint.py", line 608, in _update_best_and_save
    self._save_model(filepath, trainer, pl_module)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/callbacks/model_checkpoint.py", line 335, in _save_model
    self.save_function(filepath, self.save_weights_only)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/properties.py", line 327, in save_checkpoint
    self.checkpoint_connector.save_checkpoint(filepath, weights_only)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/connectors/checkpoint_connector.py", line 408, in save_checkpoint
    atomic_save(checkpoint, filepath)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/utilities/cloud_io.py", line 63, in atomic_save
    torch.save(checkpoint, bytesbuffer)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/torch/serialization.py", line 372, in save
    _save(obj, opened_zipfile, pickle_module, pickle_protocol)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/torch/serialization.py", line 476, in _save
    pickler.dump(obj)
TypeError: cannot pickle '_csv.writer' object

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "main.py", line 59, in <module>
    trainer.train(parser.parse_args(), hp)
  File "/home/feitao/Projects/music_unmix/lasaft/lasaft/source_separation/conditioned/scripts/trainer.py", line 157, in train
    trainer.fit(model, training_dataloader, validation_dataloader)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 513, in fit
    self.dispatch()
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 553, in dispatch
    self.accelerator.start_training(self)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/accelerators/accelerator.py", line 74, in start_training
    self.training_type_plugin.start_training(trainer)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/plugins/training_type/training_type_plugin.py", line 111, in start_training
    self._results = trainer.run_train()
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/trainer.py", line 676, in run_train
    self.train_loop.on_train_end()
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/training_loop.py", line 134, in on_train_end
    self.check_checkpoint_callback(should_update=True, is_last=True)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/training_loop.py", line 164, in check_checkpoint_callback
    cb.on_validation_end(self.trainer, model)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/callbacks/model_checkpoint.py", line 212, in on_validation_end
    self.save_checkpoint(trainer, pl_module)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/callbacks/model_checkpoint.py", line 259, in save_checkpoint
    self._save_top_k_checkpoints(trainer, pl_module, monitor_candidates)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/callbacks/model_checkpoint.py", line 566, in _save_top_k_checkpoints
    self._update_best_and_save(current, epoch, step, trainer, pl_module, metrics)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/callbacks/model_checkpoint.py", line 608, in _update_best_and_save
    self._save_model(filepath, trainer, pl_module)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/callbacks/model_checkpoint.py", line 335, in _save_model
    self.save_function(filepath, self.save_weights_only)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/properties.py", line 327, in save_checkpoint
    self.checkpoint_connector.save_checkpoint(filepath, weights_only)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/trainer/connectors/checkpoint_connector.py", line 408, in save_checkpoint
    atomic_save(checkpoint, filepath)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/pytorch_lightning/utilities/cloud_io.py", line 63, in atomic_save
    torch.save(checkpoint, bytesbuffer)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/torch/serialization.py", line 372, in save
    _save(obj, opened_zipfile, pickle_module, pickle_protocol)
  File "/opt/conda/envs/lasaft/lib/python3.8/site-packages/torch/serialization.py", line 476, in _save
    pickler.dump(obj)
TypeError: cannot pickle '_csv.writer' object

Expected behavior
log to local .csv file and save .ckpt perfectly.
Environment

PyTorch Version:  1.7.1
OS (e.g., Linux): 18.04
How you installed PyTorch (conda, pip, source): pip
Build command you used (if compiling from source):
Python version: 3.8
CUDA/cuDNN version: 10.2
GPU models and configuration:
Any other relevant information:

Are you using any accelerators? Doesn't look like it from your snippet
I tried to quickly reproduce it but no luck:
def test_bug(tmpdir):
    checkpoint_callback = ModelCheckpoint(
        dirpath=tmpdir,
        monitor=None,
        save_last=True,
    )
    logger = CSVLogger("test", version="0")
    model = BoringModel()
    trainer = Trainer(default_root_dir=tmpdir, logger=logger, max_epochs=3, callbacks=checkpoint_callback)
    trainer.fit(model)
    print(os.listdir(tmpdir))

What Lightning version are you using?

I am using one GPU and my pytorch lightning version is 1.2.1.

I also can't reproduce, even if I roll back to 1.2.1 and run on 1 GPU (you did not include that in your script). Added log statements everywhere in the model. But no pickle error.

Feel free to reopen if you are still experiencing issues!


Stamps discussion

Hi,
Thank you for all of your work on this project, its amazing how fast-paced the development is.
I would like to ask a few question around the newest change - stamps.

What standard are stamps following?

We can see some stamps using the _ character which is invalid as per the original RFC and as a result, base64 will fail to decode the stamps. While there are variants allowing this, its certainly not the default option.

Can we keep the previous format for static server declaration?

The configuration file should be human readable and manually defining provider_name, address and public_key is much simpler and straight-forward compared to stamp. It seems, that the stamp structure is more complex, and generating them manually (from the previously mentioned parameters) is a bit cumbersome.

Do we need a uri (sdns://) prefix?

Its unlikely (due to the potential for adding rogue servers without the user knowing) that dnscrypt servers will end up as browser links, which you click, to add them to your static list.  And it doesn't seem to serve any purpose during stamp processing either.

I was wondering what your thoughts are on something much simpler, like base64-encoding JSON:
DNSCrypt
{
   "type":"dnscrypt",
   "address":"<IP_ADDRESS>",
   "publickey":"FFFF:::FFFF",
   "features":[
      "dnssec",
      "nolog",
      "nofilter"
   ]
}

and DoH respectively
{
   "type":"dnsohttp",
   "address":"<IP_ADDRESS>",
   "hostname": "google.com",
   "path": "/",
   "certs": [
        "EEEE",
        "FFFF"
   ],
   "features":[
      "dnssec",
      "nolog",
      "nofilter"
   ]
}

Pros

Almost every language can serialize/deserialize JSON
Human readable / modifiable
Simple structure
Easily extendable - new features can be added without changing / modifying the parser or re-adjusting the positions.

Cons

Size - this approach increases the size of each stamp a couple of times. However, we're still talking bytes, unlikely to be an actual problem
Minor performance decrease (worst case - ms) on startup

For keys and hashes, that would be binary-encoded-as-hexadecimal-encoded-as-JSON-encoded-as-base64.
Not very efficient :)

Its definitely Matryoshka-esque, still this are operations where realtime performance is not critical.
There is also BSON. Its similar to the current format (length followed by data), but its "standardized" and there are multiple libraries for almost every language/platform.

BSON is old and was never standardized. CBOR is, but the current format is super simple. Really, I don't think it's worth importing a generic parser just to parse length-prefixed byte vectors.


Relax a few unittests for double-precision reals

A loss-less roundtrip (to string <=> parse) apparently isn't guaranteed when using double-precision reals.

The issues were encountered with LDC for MSVC and ARM targets (double-precision reals).

LGTM.  But I'll defer to someone with stronger grasp of floating-point semantics.

Related: https://github.com/dlang/phobos/pull/4345
The round trip should be lossless; if it's not, why not fix it instead of relaxing the tests? Probably one or both of the conversion routines just isn't using enough decimal digits:
People generally assume that ceil(log10(pow(2.0, double.mant_dig))) == 16 is enough for a lossless round-trip, but actually ceil(log(pow(2.0, double.mant_dig - 1)) / log(10.0) + 1) == 18 are needed.

The failure of test(-double.max) is caused by a logic bug in std.conv.parse which is not platform dependant. (I can reproduce it on my AMD64 machine with DMD just by replacing real with double in a few places.)
Please give me a chance to fix the root cause rather than weakening the std.json unittest.

Please give me a chance to fix the root cause rather than weakening the std.json unittest.

;) Sure, thanks!

Unfortunately, fixing std.conv.parse turned out to be more trouble than I expected.

For decimal, getting a lossless round-trip without the use of a higher precision type seems difficult to impossible. (It should generally be within ~1 bit, though.)

The double.max problem is fixable, but it seems to me that a principled solution requires manipulating the rounding mode, which I cannot get working reliably across all three major compilers.

The whole function is kind of a mess, and should probably be re-written. I have done this, but I don't want to delay this trivial PR indefinitely waiting for it to be reviewed and merged. (Especially since I haven't even decided whether to submit my rewrite, at all.)

Given the above, I recommend that we go ahead and merge this as-is.

ping, looks like this is ready to go.

@kinke Can you please rebase onto master so that github picks up the fact that jenkins is no longer required for a merge?


Merge Sort In C

Introduction to the Sort
Time Complexity Information Of All Scenarios
Code For The Algorithm

can I work on this?

Thanks...

done please check out my pull request
Thanks.


Proxy Support

Electron version: Latest muon bootstrap
Operating system: Osx

I was able to use session.setProxy for electron before now that I am on muon I can't get the webContents portion that let me get the session before, any explanation or explanation of a fix would be greatly appreciated.

Can you include a code sample? What are you trying to get the webContents from?

in the frame component when creating the webview
this.webview = document.createElement('webview')

this.webview.getWebContents().session

used to be available

I want to use that to set my proxy, you have handlers for state deep inside the store, and I'd rather not get into that

And you don't have certain standard chrome extension support so I can't use things like
chrome.tabs // etc.

or I would just follow the chrome extension way of doing it

@carsonwright I think this has been resolved since? The extension API is now available, as well as allowing to set the partition and assigning a proxy like that?

I haven't checked but that sounds amazing! I'll try and look at it this week


Remove auth and etcd hack

With 4.8 we don't require any auth and etcd hack to add unsupported
onfig override, better to remove it from master branch which now
targeted with 4.8 side.
fixes: #374

/lgtm


ko2kegg_abundance leads to 0 keggs

I've been trying to follow your tutorial and have been struggling at the first few steps.. I've determined my issue is my table with KO abundances is converted to a kegg table with only my sample names and no kegg abundances. Could you please help me to try figure out what the issue is? I've been trying my best, but to no avail.
pred_metagenome_unstrat.tsv.gz
kegg_abundance <- ko2kegg_abundance(file = "/Picrust2/KO/pred_metagenome_unstrat.tsv")
> kegg_abundance  [1] 1B_1 1B_2 1B_3 2B_1 2B_2 2B_3 3B_1 3B_2 3B_3 4B_1 4B_2 4B_3 5B_1 5B_2 5B_3 6B_1 [17] 6B_2 6B_3 7B_1 7B_2 7B_3 8B_1 8B_2 8B_3 9B_1 9B_2 9B_3 <0 rows> (or 0-length row.names)
> str(kegg_abundance) 'data.frame':	0 obs. of  27 variables:  $ 1B_1: num   $ 1B_2: num..

Hi @ranfoxall,
I apologize for any inconvenience caused by the recent bug in the ko2kegg_abundance function. I have just fixed this issue in the latest version of ggpicrust2.
To resolve this problem, please reinstall the package using:
remotes::install_github("cafferychen777/ggpicrust2")

The function should now work correctly and return the proper KEGG pathway abundance results. If you encounter any other issues, please don't hesitate to let me know.
Thank you for bringing this to my attention and for your patience!
Best regards,
Chen

Hi Chen,
Thanks so much for solving the issue. I can now successfully run ko2kegg_abundance! I thought solving the ko2kegg problem would solve my other issue but it hasn't. I have a colleague with an older version of ggpicrust which my data/metadata work with (we tested to see whether it was my install). We have a manuscript in review that uses ggpicrust! Hopefully we will publish it soon and we can reference your very useful package!
I thought I could solve my issues by installing an older version of ggpicrust, but I can't figure out how to install the older version, so I'm still struggling to get your awesome package to work in my hands.
pred_metagenome_unstrat.tsv.gz
IMTALizzy_SampleData.txt
My new issue
KOabundance_file<-"/Users/randifoxall/Desktop/IMTA_Lizzy/IMTA16s/Picrust2/KO/pred_metagenome_unstrat.tsv" KOabundance_data <- read_delim(KOabundance_file, delim = "\t", col_names = TRUE, trim_ws = TRUE) results_data_input <- ggpicrust2(data = KOabundance_data, metadata = metadata, group = "Treatment",  pathway = "KO", daa_method = "LinDA", ko_to_kegg = TRUE, order = "pathway_class", p_values_bar = TRUE, x_lab = "pathway_name", reference="SETTLE")
and I get the error:
`Starting the ggpicrust2 analysis...
Converting KO to KEGG...
Processing provided data frame...
Loading KEGG reference data. This might take a while...
Processing 306 KEGG pathways...
|====================================================================================================| 100%
Total KO matches found: 4852
Number of non-zero pathways before filtering: 263
Removing KEGG pathways with zero abundance across all samples...
Final number of KEGG pathways: 263
Performing pathway differential abundance analysis...
Using column 'sample_name' as sample identifier
Running LinDA analysis...
Error in data.frame(feature = rownames(first_comparison), method = "LinDA",  :
arguments imply differing number of rows: 263, 1, 2
In addition: Warning message:
In MicrobiomeStat::linda(feature.dat = feature.dat, meta.dat = meta.dat,  :
Some features have less than 3 nonzero values!
They have virtually no statistical power. You may consider filtering them in the analysis!
`
I've attached my metadata and abundance files. Any suggestions or insights are very much appreciated!

Hi @ranfoxall,
Thank you for reporting this issue. I've analyzed the LinDA analysis error and identified two main causes:

Features with insufficient non-zero values
Row count mismatch in results data frame creation

Here's a step-by-step solution:

Filter low prevalence features:

# Filter out features with low prevalence
min_samples <- 3  # minimum number of non-zero samples required
keep_features <- rowSums(KOabundance_data > 0) >= min_samples
KOabundance_data_filtered <- KOabundance_data[keep_features, ]

Ensure metadata and abundance data alignment:

# Match sample names between abundance and metadata
common_samples <- intersect(colnames(KOabundance_data), metadata$sample_name)
KOabundance_data <- KOabundance_data[, common_samples]
metadata <- metadata[match(common_samples, metadata$sample_name), ]

Run analysis with modified data:

results_data_input <- ggpicrust2(
  data = KOabundance_data_filtered,  # Use filtered data
  metadata = metadata,
  group = "Treatment",
  pathway = "KO",
  daa_method = "LinDA",
  ko_to_kegg = TRUE,
  order = "pathway_class",
  p_values_bar = TRUE,
  x_lab = "pathway_name",
  reference = "SETTLE"
)

If issues persist, try these additional steps:

Verify data structure:

# Print dimensions and sample names
print(dim(KOabundance_data))
print(colnames(KOabundance_data))
print(dim(metadata))
print(metadata$sample_name)

# Check Treatment levels
print(table(metadata$Treatment))

Alternative method:

results_data_input <- ggpicrust2(
  data = KOabundance_data_filtered,
  metadata = metadata,
  group = "Treatment",
  pathway = "KO",
  daa_method = "ALDEx2",  # Alternative to LinDA
  ko_to_kegg = TRUE,
  order = "pathway_class",
  p_values_bar = TRUE,
  x_lab = "pathway_name"
)

Note: The warning about features having less than 3 nonzero values indicates sparse pathways in your dataset. The filtering step above should address this issue by removing these sparse features before analysis.
Please let me know if you need any clarification or encounter other issues!
Best regards,
Chen


Upgrade transformers version

Requires transformers-4.15.0 or greater

Unpinned version on transformer dependency in both setup.py and requirements.txt


[Question] Is it possible to reference matched ugly string in the pretty version?

I'm wondering, is it possible to reference the matched ugly string in the Pretty version?
I have two use-cases (both Ott related):

For any strings X and n, I'd like to be able to render </ X // n /> with an overline over X , and n` superscript beside it
For any greek letter followed by a number or a predetermined index variable (i.e. i, j, k, m, n), I'd like to make the number subscript

Both of these could be achieved if we could refer to parts of the matching string in the ugly version when specifying the pretty.
Is such a thing possible with this library? Is there a reference for the regular expression format used? Or is there another way to achieve the types of things I'm doing?

Sorry, that's currently not possible. And in general, not something I can support for performance reasons (vscode cannot handle too many individualized decorations).

Would something like this work for you?
{ "ugly": "\\s*//\\s*1", "pretty": "¹", "pre": "\\b", "post": "\\b"},
{ "ugly": "X", "pre": "\\b", "post": "\\s*\\s*//", "style": {"hackCSS": "border-top: 1pt solid"}},

The basic idea is that you can substitute the superscript/subscript portion without touching "X", and then separately style "X" when you detect a superscript/subscript.


fund_holdings attribute not found

Describe bug
Accessing the fund_holdings attribute fails using V 0.2.50
Simple code that reproduces your problem

import yfinance as yf

print("yfinance version", yf.__version__)

# Create a Ticker object for the fund
ticker = yf.Ticker('QQQ')

# Attempt to get the fund holdings
try:
    holdings = ticker.fund_holdings
    if holdings is not None and not holdings.empty:
        print("Fund Holdings:")
        print(holdings)
    else:
        print("Holdings data is not available for this fund.")
except Exception as e:
    print(f"An error occurred: {e}")

### Debug log

python test.py
yfinance version 0.2.50
An error occurred: 'Ticker' object has no attribute 'fund_holdings'

### Bad data proof

_No response_

### `yfinance` version

0.2.50

### Python version

3.12.5

### Operating system

Mac OS 15

Is this what you are trying to access?

When was fund_holdings a supported attribute? I quickly looked through old releases but can't find.

guess it was the wrong attribute.  This works:
ticker = yf.Ticker(symbol)

eunl = yf.Ticker(symbol)
funds_data = eunl.funds_data
if funds_data is not None:
#    dump(funds_data)
    top = funds_data.top_holdings
    if top is not None:
        dump(top)
        print("columns = ", top.columns.tolist())
        for symbol, row in top.iterrows():
            name = row['Name']
            percent = row['Holding Percent']
            print(f"{symbol} = {percent:.2%}")
else:
    print("***no top found")


Update the tableview after sorting

The table view should be updated after the user finishes dragging event in filter view. This is to synchronize the same order in both views.

Current state:
The sorting is order derived as in filter view. But the table view is different which is difficult to synchronize the visual representation.

So we want to make the table view same as in filter

What do you mean by "make the table view same as in filter"?

The table view should be same as filter view order.
It means the column should be in the order of Origin, Gender and Career status

No! This is what we don't want to have. The column order in the table should be independent of the sort order. Otherwise the user would not be able to bring them in a specific order without changing the sorting.

But it will be difficult to see the sorting effect on the table view isn't it ?

Yes, but as the user specified the hierarchy on the right he knows exactly what happens.

Ok got the point then  I will close this issue.


feat: Add Biome.js Implementation

Is your feature request related to a problem? Please describe.
No but yes. If you want a better developer experience you should use Biome instead of Prettier and ESLint. It is better in performance and is together and compativle
Describe the solution you'd like to see
An option in the CLI where you could choose between Eslint and biome and prettier and biome.
Describe alternate solutions
Use biome
Additional information
No response

nice proposal

Would also be super interested in having this and/or working on implementing it

I don't know how to write the install script but i can help with how to use it with next.js. I implemented it and it is quite easy. You can reach my repo to see it. It works pretty well, this is the link

As an update, I am actively working on this. Hopefully will have a PR soon!


Introduce a new Listener to websocket module

The current websocket service is attached to the http:Listener. So need to introduce a new listener for websocket.

Closing this as this is done.


make forloop multithreading in DotProdcutOP

summary:
1. use TaskThreadPool to run the forloop task
2. add main function to run distance_op_test

Thank you for your contribution! PyTorch and Caffe2 are now officially merged with the PyTorch 1.0 preview release. Please submit on https://github.com/pytorch/pytorch if this is still an issue over there.


Add accountability to osgi feature

This fixes the OSGi feature referring to accountability artifacts
without including them.

This PR is an artifact of e85746245c0a41012659818e9150397d002d5acf not renaming the povenance artifact in the OSGi definitions. The correct way to deal with this would have been to follow the rename in the OSGi definitions, but I didn't see that.
Note that accountability (fka. provenance) transitively includes bcprov:1.54.0 (via org.web3j:web3j-core), which is known to be incorrectly packaged and currently breaks the OSGi build. C.F: https://github.com/OpenTOSCA/container/pull/78#issuecomment-439489244


adding some rustdocs

I'm just adding what I have before we get too out of sync in forks again. I think the #![doc = include_str!("../README.md")] macro in lib.rs should work for crates.io. but you might want to double check.

I'm closing this since so much has changed


Alovelltroy/quickstart

Also added a docker-compose example to show how to dynamically add hosts without SIGHUP

Readme describes basic usage

-No ipxe payload included

I wonder if it's possible to either:

compile ipxe as part of the build
ask the wolfi folks to include the ipxe rpm.

This PR needs a second container that periodically populates the dhcp configuration.

lgtm


stage2: refactor stage2

stage2_main() was very long and plagued with spread out panics in different places. Split out functionality into separate functions, each returning an error, and panic at the top level.
While we are at it, clean up the kernel layout logic, using the MemoryRegion type and updating the loaded region at each stage. Add documentation on each step for clarity.
Finally, add a missing check in the new prepare_heap() function to verify that we did not exceed the reserved kernel region size.

Rebased on main


Neo2 layers support

I just now found out HK supports neo2 which is great news.
However, the upper neo layers are emulated via the long-press menu which is fine but can get a bit fiddly and isn't 100% complete either. (Some keybinds also wouldn't make sense as popups, e.g. arrow keys, esc, enter, insert)
There is something similar to a layer in the Fn menu, is it possible to add more of those and if so, where would you start?
Would adding the two additional mod keys pose a problem? (Other than even more screen real-estate problems of course)
cc @fahrstuhl

Sorry, I have no idea how to add layers. It's been forever that I looked at the Neo implementation in hackerskeyboard. (I think some of the alt characters are missing because they can't be displayed? I remember putting all of them into the config.

Sorry, I have no idea how to add layers. It's been forever that I looked at the Neo implementation in hackerskeyboard. (I think some of the alt characters are missing because they can't be displayed? I remember putting all of them into the config.


How to hide output in Jupyter notebook (but still continue logging) (hashtag565)

Hi there,
Is there a way to hide the output inside Jupyter notebook (encircled in green) while still maintaining the info logging capabilities (including saving the .log file) ?
![image](
Thanks!

Hi
I'm not very familiar with Jupyter but could you maybe [remove()]( the default stderr sink, before adding the file one? I guess it should prevent Jupyer from capturing and displaying the logs.
logger.remove()  hashtag Remove default 'stderr' sink (and all others, if any)
logger.add("my_log_file.log", rotation="10 MB")

Hey Delgan,
Thanks for the reply. Your solution worked! Awesome stuff. Cheers!


Generify cause and description assertThat methods

So it can be used more easily with Matcher<CharSequence>.

This fell out of #10123, since I got a warning there when using containsText.


web-frontend for social-app with GraphQL types

Motivation
This is a frontend react-app for the example social app.
Proposal
Changes:-
src/contract.rs - Added functions to handle posts, likes and comments.
src/lib.rs - introduced structs for likes and comments, also updated previous structs to handle posts with images, likes and comments.
src/state.rs - updated states to handle updated OwnPost and ReceivedPosts objects.
New:-
web-frontend - includes necessary files to show a frontend for the social app. uses server generated GraphQL types. Updated README.md for better clarification.
Test Plan
Test Case Update:-
tests/cross_chain.rs - added imageUrl field to handle the test case.
All test cases passes successfully.

This sounds really cool, thank you for the contribution! 😁
I tried to run it on my end to check it out, but I got a crypto error:
Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:79:19)
    at Object.createHash (node:crypto:139:10)
    at module.exports (/home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/webpack/lib/util/createHash.js:90:53)
    at NormalModule._initBuildHash (/home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/webpack/lib/NormalModule.js:401:16)
    at handleParseError (/home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/webpack/lib/NormalModule.js:449:10)
    at /home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/webpack/lib/NormalModule.js:481:5
    at /home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/webpack/lib/NormalModule.js:342:12
    at /home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/loader-runner/lib/LoaderRunner.js:373:3
    at iterateNormalLoaders (/home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
    at iterateNormalLoaders (/home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/loader-runner/lib/LoaderRunner.js:221:10)
    at /home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/loader-runner/lib/LoaderRunner.js:236:3
    at runSyncOrAsync (/home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/loader-runner/lib/LoaderRunner.js:130:11)
    at iterateNormalLoaders (/home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/loader-runner/lib/LoaderRunner.js:232:2)
    at Array.<anonymous> (/home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
    at Storage.finished (/home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16)
    at /home/twey/dev/linera/protocol/nirajsah/social/examples/social/web-frontend/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9

Do you know what that might be about?
I've left a few comments I spotted just scrolling through the code, but looking forward to being able to run it properly! Our tests have some feedback as well :)

are you getting this error when trying to run npm install

i have noticed some of my mistakes!
i'll make sure they won't happen again in future :)

are you getting this error when trying to run npm install?
No, it comes on npm run start.  The internet suggests it's a mismatch with my local OpenSSL, but I have quite a modern OpenSSL (3.0.14), which is recommended by Node as of a couple of years ago.  I think that one of the dependencies is relying on an old OpenSSL feature: as this thread suggests, setting NODE_OPTIONS=--openssl-legacy-provider lets me run it.  Now I get:

Failed to compile.

./src/GraphQLProvider.js
  Line 14:10:  'React' must be in scope when using JSX  react/react-in-jsx-scope

are you getting this error when trying to run npm install?

No, it comes on npm run start. The internet suggests it's a mismatch with my local OpenSSL, but I have quite a modern OpenSSL (3.0.14), which is recommended by Node as of a couple of years ago. I think that one of the dependencies is relying on an old OpenSSL feature: as this thread suggests, setting NODE_OPTIONS=--openssl-legacy-provider lets me run it. Now I get:
Failed to compile.

./src/GraphQLProvider.js
  Line 14:10:  'React' must be in scope when using JSX  react/react-in-jsx-scope

I have reproduced the issue.
    at new Hash (node:internal/crypto/hash:69:19)
    at Object.createHash (node:crypto:133:10)
    at module.exports (/Users/nirajsah/Desktop/Pro/Rust/linera-protocol/examples/social/web-frontend/node_modules/webpack/lib/util/createHash.js:90:53)
    at NormalModule._initBuildHash (/Users/nirajsah/Desktop/Pro/Rust/linera-protocol/examples/social/web-frontend/node_modules/webpack/lib/NormalModule.js:401:16)
    at /Users/nirajsah/Desktop/Pro/Rust/linera-protocol/examples/social/web-frontend/node_modules/webpack/lib/NormalModule.js:433:10
    at /Users/nirajsah/Desktop/Pro/Rust/linera-protocol/examples/social/web-frontend/node_modules/webpack/lib/NormalModule.js:308:13
    at /Users/nirajsah/Desktop/Pro/Rust/linera-protocol/examples/social/web-frontend/node_modules/loader-runner/lib/LoaderRunner.js:367:11
    at /Users/nirajsah/Desktop/Pro/Rust/linera-protocol/examples/social/web-frontend/node_modules/loader-runner/lib/LoaderRunner.js:233:18
    at context.callback (/Users/nirajsah/Desktop/Pro/Rust/linera-protocol/examples/social/web-frontend/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at /Users/nirajsah/Desktop/Pro/Rust/linera-protocol/examples/social/web-frontend/node_modules/babel-loader/lib/index.js:51:103
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'
}

Node.js v18.17.0

the issue is with npm to fix this issue you can run npm audit fix --force which solves this issue. i have tried it with other package managers and i don't see any issue there.
there shouldn't be any issues compiling. i have tried npm run build and deployed it locally. everything works fine.

./src/GraphQLProvider.js
  Line 14:10:  'React' must be in scope when using JSX  react/react-in-jsx-scope

With your help I got this working, and it looks pretty cool!

The post button seems to work, but I don't see posts appear after I've posted them — do I have to do something special to refresh the list?

This looks pretty good to me.  We could do with updating the dependencies, but I think that's true of all our example frontends, so maybe better done in bulk.  Let's commit the results of npm audit fix --force, get the lints passing, and merge it! :)

This looks pretty good to me. We could do with updating the dependencies, but I think that's true of all our example frontends, so maybe better done in bulk in another PR.

I was thinking maybe we could migrate to Bun.js runtime instead of node.js. it's fast and doesn't have dependencies issues like npm.

Just a couple of minor fixes:

npm audit fix --force seems to work to fix the dependencies, but we should commit the results
the lints are currently failing

After that I think we're good to go :)

lints are failing showing outdated README.md. i have updated it, don't know where the issue is :)

I was thinking maybe we could migrate to Bun.js runtime instead of node.js. it's fast and doesn't have dependencies issues like npm.

I'm not against it, but I think that npm here is correctly highlighting an issue that Bun must be missing, which is that react-scripts (i.e. create-react-app) is not compatible with modern TypeScript because it's been dead as a project for a few years.  Ideally we should update all our frontends to not rely on react-scripts (maybe react-scripts' eject script is sufficient here, or at least a good starting point).
I've created a separate task (https://github.com/linera-io/linera-protocol/issues/2315) to track the migration from react-scripts, and if you'd like to do that in a separate PR I'd be happy to review :)  I'm also happy to swap to Bun if you want to PR that — I do like it better.  For this one, though, let's just commit the results of npm audit fix --force so that we can get it merged.

lints are failing showing outdated README.md. i have updated it, don't know where the issue is :)

Ah, I see the problem!
Our README.mds are actually autogenerated using a tool called cargo-rdme from the Rust documentation of the root module of the library (i.e. src/lib.rs).  Instead of editing README.md directly, you have to make your changes there, and then run cargo rdme to update the README.md.

I was thinking maybe we could migrate to Bun.js runtime instead of node.js. it's fast and doesn't have dependencies issues like npm.

I'm not against it, but I think that npm here is correctly highlighting an issue that Bun must be missing, which is that react-scripts (i.e. create-react-app) is not compatible with modern TypeScript because it's been dead as a project for a few years. Ideally we should update all our frontends to not rely on react-scripts (maybe react-scripts' eject script is sufficient here, or at least a good starting point).

i use vite+bun.js so never faced any issues. 🥲

I've created a separate task (#2315) to track the migration from react-scripts, and if you'd like to do that in a separate PR I'd be happy to review :) I'm also happy to swap to Bun if you want to PR that — I do like it better. For this one, though, let's just commit the results of npm audit fix --force so that we can get it merged.

yes we should update all the frontends. i would like to do that :). fungible-apps migration to TS is done. i'll fix if there is any dependencies issues and open a PR. should i continue with react-scripts or should i switch to bun.js.

lints are failing showing outdated README.md. i have updated it, don't know where the issue is :)

Ah, I see the problem!
Our README.mds for Rust crates are actually autogenerated using a tool called cargo-rdme from the Rust documentation of the root module of the library (i.e. src/lib.rs). Instead of editing README.md directly, you have to make your changes there, and then run cargo rdme to update the README.md.

aah, i wasn't aware of that. that's really cool. i've updated it now.

We also have tests that check the commands in our READMEs are correctly executable, and it looks like your changes don't pass that test:
2024-07-31T11:27:13.0287407Z   0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
2024-07-31T11:27:13.028504Z DEBUG linera_service::node_service: Request: Request { query: "mutation {\n    post(\n        text: \"Linera Social is the new Mastodon!\"\n        image: \"https://linera.org/img/logo.svg\" # optional\n    )\n}\n", operation_name: None, variables: Variables({}), extensions: {} }
2024-07-31T11:27:14.2291932Z
2024-07-31T11:27:14.8839315Z 100   165    0     0  100   165      0    137  0:00:01  0:00:01 --:--:--   137
2024-07-31T11:27:14.8839830Z 100   285  100   120  100   165     64     88  0:00:01  0:00:01 --:--:--   153
2024-07-31T11:27:14.8840260Z 100   285  100   120  100   165     64     88  0:00:01  0:00:01 --:--:--   153
2024-07-31T11:27:14.8843286Z {"error":["Unknown argument \"image\" on field \"post\" of type \"OperationMutationRoot\". Did you mean \"imageUrl\"?"]}
2024-07-31T11:27:14.8849019Z null
2024-07-31T11:27:14.8854740Z + jobs -p
2024-07-31T11:27:14.8855937Z + xargs -r kill
2024-07-31T11:27:14.8922770Z + rm -rf /tmp/tmp.uunGnZBADG
2024-07-31T11:27:14.8946696Z thread 'test_script_in_readme_with_storage_service::social' panicked at linera-service/tests/readme_test.rs:51:5:
2024-07-31T11:27:14.8947598Z assertion failed: status.success()

I can't believe this :(
Instead of imageUrl I wrote image

Happens to the best of us!
You can run this test locally by running:
$ cargo test -p linera-service --test end_to_end_tests -- test_script_in_readme_with_storage_service::social

Looks great, thank you! :grin:


pdm: 2.10.1 -> 2.10.3

Changelog: https://github.com/pdm-project/pdm/releases/tag/2.10.3
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[x] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 268694 at 88a737ad run on aarch64-darwin 1

1 package built successfully:

pdm


DOCS-10060-database-stored-procedures-kt

Rewrote Database Stored Procedure operation examples
Added Studio steps and screenshots
Reorganized content

Closing as new PR created https://github.com/mulesoft/docs-connectors/pull/1253


docker version of v0.21.0 always stops

Describe the bug
I have newly installed docker version of memos v0.21.0 and have been anoyed by stopage of this app.This was deployed in local Ubuntu machine.
After finding this error, I also have tried to deploy same docker version in 2 different vps instances and the result are same.
I would show one of the docker logs as follows. Instance is made in Oracle Cloud Infra. free tier.
ERROR server error method=/memos.api.v2.LinkService/GetLinkMetadata error="parse "VirtualHost *:5230": first path segment in URL cannot contain colon"
2024/04/16 20:52:43 ERROR server error method=/memos.api.v2.LinkService/GetLinkMetadata error="Get "http://localhost:8080/\": dial tcp <IP_ADDRESS>:8080: connect: connection refused"
2024/04/16 20:52:43 ERROR server error method=/memos.api.v2.LinkService/GetLinkMetadata error="Get "/VirtualHost": unsupported protocol scheme """
2024/04/16 20:52:43 ERROR server error method=/memos.api.v2.LinkService/GetLinkMetadata error="parse "VirtualHost *:80": first path segment in URL cannot contain colon"
2024/04/16 20:52:43 INFO OK method=/memos.api.v2.TagService/ListTags
2024/04/16 20:52:43 ERROR server error method=/memos.api.v2.LinkService/GetLinkMetadata error="Get "/VirtualHost": unsupported protocol scheme """
I was not able to find logs relating to stoppage error in other 2 machine/instance and it is only said "memos stopped properly."
In all cases the "memos" successfully restarts after input of "docker start memos". And they occasionally stop.
Steps to reproduce

Deploy docker version to VPS instances and local machine.
All successfully start.
After some minutes or hours, they stop.

The version of Memos you're using
v0.21.0
Screenshots or additional context

I want deploy this source on Localhost, pls help me guide install it. Thank you very much.

I want deploy this source on Localhost, pls help me guide install it. Thank you very much.

I deployed it as docker application as was mentioned in this hub.

Any other information like system configuration, or is it your system or docker rebooting?

Any other information like system configuration, or is it your system or docker rebooting?

I would add information as follows:
System config. of reported trouble of after deploying Memos v0.21.0:
Case 1: Server: Oracle Cloud Infrastructure
Main memory size 1GB
HDD 50GB
OS: Ubuntu 22.04.4 LTS
Container: podman v 3.4.4
command used when deployed:
docker run -d --name memos -p 5230:5230 -v ~/.memos/:/var/opt/memos neosmemo/memos:stable
Case 2: Server: Conoha VPS
Main memory size 1GB
HDD 100GB
OS: Ubuntu 22.04.3 LTS
Container: podman v 3.4.4
command used when deployed:
	docker run -d --name memos -p 5230:5230 -v ~/.memos/:/var/opt/memos neosmemo/memos:stable

Case 3: Server: Local machine
Main memory size 32GB
Storage 1: nvme 1TB
Storage 2: HDD 5TB
OS: Ubuntu 23.10
Network: local LAN (Ethernet)
Container: podman version 4.3.1
command used when deployed:
docker run -d --name memos -p 5230:5230 -v ~/.memos/:/var/opt/memos neosmemo/memos:stable
Hope any advise on resolution.

The app deplyed in the local machine has been running without failure for at least last 2 days. So I am assuming this trouble now only applied to in the VPS instances.

@nobbywfc So I think it's possible that your machine or podman will reboot automatically. Please feel free if you have more hint.

I am happy that I share the same trouble with #3250.
I may use other docker daemon such as docker.io to see if the same trouble will happen or not.
On the other hand, I have never encountered such trouble in the older version of Memos.

Changing from podman to docker.io, the app keeping alive for 33 hours as per attached image.


add eudi wallet it to ita-button set

Hi All,
I would like add the the EUDI Wallet IT button to ita-button project.
Ita button is a style collection for italian auth buttons. Like spid-sp-access-button but without external requirements (bootstrap, jquery, ecc...)
I can use the wallet_icon.svg image?

yes you can @MdreW !

Thank you


Create schema-registry-light-client.go

Adding a field to the schemas after importing and before exporting it to the SR.
Made changes to the already existing schema-registry-light-client.go file at lines 288-303

Closing due to inactivity


[stable/concourse] Upgrade chart to support Concourse 4.0

Concourse 4.0 has been released with some breaking changes, requiring changes to the chart. I'd like to start working on this, but don't want to duplicate work in case someone else is already working on it.
@frodenas @william-tran Is this safe to work on? Should the chart support both 3.x and 4.0?
Breaking changes:

[x] Migrate CONCOURSE_BASIC_AUTH_* to CONCOURSE_ADD_LOCAL_USER, CONCOURSE_MAIN_TEAM_LOCAL_USER, and CONCOURSE_MAIN_TEAM_ALLOW_ALL_USERS (don't forget to change the NOTES.txt to match the new basic auth model)
[x] Migrate CONCOURSE_GITHUB_AUTH_* to CONCOURSE_GITHUB_* and CONCOURSE_MAIN_TEAM_GITHUB_*
[x] Migrate CONCOURSE_GITLAB_AUTH_* to CONCOURSE_GITLAB_* and CONCOURSE_MAIN_TEAM_GITLAB_*
[x] Migrate CONCOURSE_GENERIC_OAUTH_* to CONCOURSE_OAUTH_* and CONCOURSE_MAIN_TEAM_OAUTH_*

New features:

[ ] CONCOURSE_RESOURCE_TYPE_CHECKING_INTERVAL
[ ] CONCOURSE_VAULT_CACHE

New authentication modes:

[x] CloudFoundry
[x] LDAP

Pre-existing authentication modes not already in chart:

[x] OIDC

I'd be happy to help. v4 bring user based auth instead of team based!!! I can't wait to test that!

I don't think the chart should support both 3.x and 4.0, that would introduce too much complexity that we should avoid maintaining. With web and worker both supporting arbitrary env vars, at this point, I think the current version of the chart can continue to support 3.x use cases without further changes.
This breaking change gives us an opportunity to make breaking chart changes to resolve some issues with the chart as it is today:

[ ] use [web|worker].extraEnv instead of [web|worker].env
[ ] Go though the output of docker run -it concourse/concourse:4.0.0 [web|worker] --help and remove any values / env vars / command-line args no longer supported
[ ] Consider removing all values that support features that can be configured strictly through [web|worker].extraEnv.

This would set the stage for the chart only requiring updates for features that use secrets or other aspects of k8s. The Concourse team continues to add great features to concourse, and often, and I don't want the maintenance of this chart to be a drag to the adoption of a new version due to an apparent lack of support through chart values.

I don't think the chart should support both 3.x and 4.0, that would introduce too much complexity that we should avoid maintaining. With web and worker both supporting arbitrary env vars, at this point, I think the current version of the chart can continue to support 3.x use cases without further changes.
This breaking change gives us an opportunity to make breaking chart changes to resolve some issues with the chart as it is today:

[ ] use [web|worker].extraEnv instead of [web|worker].env
[ ] Go though the output of docker run -it concourse/concourse:4.0.0 [web|worker] --help and remove any values / env vars / command-line args no longer supported
[ ] Consider removing all values that support features that can be configured strictly through [web|worker].extraEnv.

This would set the stage for the chart only requiring updates for features that use secrets or other aspects of k8s. The Concourse team continues to add great features to concourse, and often, and I don't want the maintenance of this chart to be a drag to the adoption of a new version due to an apparent lack of support through chart values.

I'm on board with dropping explicit 3.x support, extraEnv -> env, and removing old arguments.
As far as relying more heavily on env, I'm personally in favor of explicitly supporting features in the chart:

The documentation for Concourse flags isn't fantastic (you have to run the binary's --help instead of referencing the website to really see everything) and as a user, I really appreciate charts that have explicit config.
Even if the documentation were better, when I'm referencing the README to understand how to use a chart, it's a huge boon to be able to use that as the primary point of reference, rather than having to cobble together config.
It's not very Concoursey to support kitchen-sink-config 😃.

I definitely understand the maintainer burden is high—it's a totally fair point—but I'd personally prefer to invest in keeping the YAML explicit. Is there a compromise where we can communicate in the README how to "early adopt" features? It's obvious if you know what you're doing, but it might be helpful to document recommendations for using env.

I've started to work on supporting 4.0 and have some decisions to make, especially with regard to the split between flags for auth providers, and flags for which users/groups can access the main team:

Main team: we can do something like concourse.mainTeamGithubUsers or concourse.mainTeam.githubUsers. I hesitate a bit to use nested values, but it feels like the right choice here.
Auth providers: we have a similar choice for flat vs nested. Because some providers have quite lengthy config (LDAP has 20 flags alone), I'm preferring to use nested flags like secrets.ldapAuth.displayName.
Auth providers: Also because there are so many flags, I would like to add feature-flags for each provider, à la secrets.ldapAuth.enabled, where the *.enabled flag is never provided to Concourse, but is just used within the Helm templates to control blocks of flags. It's extra config, but feels more conventional.
Auth providers: Auth providers are currently in secrets.*, so it's natural to put them in as secrets.ldapAuth.*, but this feels like it's overloading secrets.*, and it doesn't do a great job of communicating that all the auth providers are similar. I'm currently doing secrets.ldapAuth.*, but I think it might be nicer to extract all the provider config to authProviders.ldap.*.

What are your thoughts on these?

So i've tested with just adding web.env everything WORKED except this:
{{- if semverCompare "^3.10.x" .Values.imageTag }}
              value: "{{ template "concourse.web.fullname" . }}:{{ .Values.concourse.tsaPort}}"
          {{- else }}
              value: {{ template "concourse.web.fullname" . }}
            - name: CONCOURSE_TSA_PORT
              value: {{ .Values.concourse.tsaPort | quote }}
          {{- end }}

the semverCompare fails and my workers get the wrong tsa_host

There is an open PR for that fix: https://github.com/helm/charts/pull/6853. But I want to address other breaking chart changes while we have the chance so I'm going to hold off on merging that.

In case you're responding to my long (my apologies for the length) previous comment, I've edited in some extra questions and details.

thanks for all your work! we'll try to test auth-related changes soon
given the number of queries being done to Vault in a large deployment, CONCOURSE_VAULT_CACHE would be a really good addition to the chart

@ralekseenkov I'm generally in favor of adding explicit config for everything (though it can get burdensome!), but I think the PR to support Concourse 4.0 should just be focused on breaking changes and cleaning up new auth-model stuff. There are a lot of config options the chart doesn't explicitly support, and I think it expands the scope too much to attempt to whittle away at it here.
You can add custom env vars to web.env until the chart officially supports it, so I'd recommend doing that for now, and submitting a PR just for adding explicit support for this.

@wendorf agreed. I only mentioned CONCOURSE_VAULT_CACHE because I saw it in the description of the issue, so I was under assumption it's coming as a part of this PR. But "4.0 new features" PR sounds great too. I actually didn't know about web.env, thanks for pointing this out - will give it a try.

Whoops! I think I wrote that up so long ago now that I totally forgot.
On Mon, Aug 20, 2018, 11:01 AM Roman Alekseenkov<EMAIL_ADDRESS>wrote:

@wendorf https://github.com/wendorf agreed. I only mentioned
CONCOURSE_VAULT_CACHE because I saw it in the description of the issue, so
I was under assumption it's coming as a part of this PR. But "4.0 new
features" PR sounds great too. I actually didn't know about web.env, thanks
for pointing this out - will give it a try.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/helm/charts/issues/6873#issuecomment-414408354, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAY3LlrKjBBzu3MdG62HwYXHD25WThV8ks5uSvmEgaJpZM4VkysG
.

Bump @wendorf

We should also close this since #7804 was merged