Backport status 4.5 release

This list shows the current state of merged backports which will be included into the upcoming 4.5 release. These backports have been applied in sequential order as they were committed to elasticsearch.  It would be good to define for each section a goal how far we would like to go and then focus on stability.
Recovery/Translog:
93a4a267b56 bp: Use peer recovery retention leases for indices without soft-deletes
98f1921bdbf bp: Migrate peer recovery from translog to retention lease
5745e699bc3 bp: Make setting index.translog.sync_interval be dynamic
Replication:
6b9b31a296d bp: Replicate write actions before fsyncing them
Transport:
51d6d361dce bp: Remove Unused Features Field on StreamOutput
46170664f35 bp: Optimize some StreamOutput Operations
eb95549bcc5 bp: Add int indicating size of transport header
d741fdcf90e bp: Remove nodeId from BaseNodeRequest
Metadata:
02f1bf7b05b bp: Make elasticsearch-node tools custom metadata-aware
9ac478470a4 bp: Omit loading IndexMetaData when inspecting shards
Cluster:
2e6caa9c786 bp: Remove some leftover refs to minimum_master_nodes
6aac9fa40f6 bp: Cluster state from API should always have a master
485bcf78b45 bp: Omit non-masters in ClusterFormationFailureHelper
Testing:
e6eeb0a158e bp: Strengthen validateClusterFormed check
5c9b5e53fa1 bp: ESIntegTestCase always cleans up static fields
0b6d4b8c0b5 bp: Use dynamic port ranges for ExternalTestCluster
e745870ad5b bp: Wait for events in waitForRelocation
0596e89f824 bp: Remove RemoteClusterConnection.ConnectedNodes
3289b29cdfa bp: Fix port range allocation with large worker IDs
e636850999c bp: Simplify port usage in transport tests
6dd8bfb0786 bp: Some Cleanup in Test Framework
d34f8b2d31b bp: Use unique ports per test worker
4de26e71e63 bp: Enable node roles to be pluggable
206dc6ebb4e bp: Allow cluster access during node restart
28a9ba6c09e bp: Increase waiting time when check retention locks
9e80e3223a3 bp: Remove transport client from tests
aab7f2138b8 bp: Remove Tracer from MockTransportService
Others:
634d34d5bb0 bp: New setting to prevent automatically importing dangling indices
b88a9270395 bp: Enable dependent settings values to be validated
62ff8205f84 bp: Silence lint warnings in server project - part 2
fc4b503bf73 bp: Make Snapshot Metadata Javadocs Clearer

@seut @mfussenegger So far i grouped all applied backports for 4.5 into sections. My next step would be to define for each section a goal for the 4.5 release. Does this make sense to you ?


Purpose of base_weight and specular_weight?

From what I can see, both of these inputs are only used as multipliers for base_color and specular_color respectively.
If that is the case, they appear to be redundant, since the same effect could be achieved by just adjusting the color inputs instead.

I strongly disagree. Having a weight for each parameter is extremely useful, and I am posting an issue where I advocate for a weight for every parameter.
Also note that the energy conservation math applies to the weights, not to the colors.
So having a specular weight of 0 means no energy goes to the specular layer, and no attenuation of the diffuse will occur, whereas a specular weight of 1 but a black specular color creates a fully absorbing specular layer and the diffuse will be attenuated accordingly.

If the only reason for the weight is to prevent coloured transmission affecting the slab below, then there are other ways that this could be accomplished.
Having the weight parameter affect the slab below but not the colour one could have problems if the colours are not normalised.

See https://github.com/AcademySoftwareFoundation/OpenPBR/issues/145 for more discussion of the physical meaning of specular color and weight.
As described there the "energy conservation math" works, for the case of the glossy-diffuse base (which produces the primary "specular" lobe), by having the specular weight mean the presence weight of the dielectric "gloss" (or perhaps equivalently the embedding dielectric of the diffuse medium). This makes sense because when the specular weight is zero, the reflection from the diffuse base should be unaffected. The specular color tint is applied instead as a non-physical tint to the Fresnel reflection factor for rays incident from above (i.e. this is not physical absorption in the medium, it is just a non-physical tweak to the Fresnel factor).
As noted, for bulk dielectric where refraction occurs (and SSS), it doesn't seem to make sense to use this intepretation of the weight (as we don't want specular weight to kill off the refraction effects, seen from above or below, which it should if it functioned as a presence weight for the bulk dielectric). In that case, the weight would instead just be a multiplier to the color tint.

I think this issue is reasonably addressed by #157?


Conventional Commits Commit Hook

I see that conventional commits didn't pass. I am willing to let it slide but we should take the commit hook from the ubiquity-dollar repo to minimize this from happening again. I'll set it as a new issue.

I think its already done on bounty repo with latest commits. can I close the issue?

I think it's referring to how we need to support the built in GitHub messages as well. Like "merged from development" should pass.

I'll review today and verify. Not sure what happened here from my phone.


Tidy imports in the Tact codebase

We could add additional yarn rules to sort and report unused imports. For example, this configuration sorts them alphabetically and places local imports above external ones:
https://github.com/nowarp/misti/blob/f95260498be6801beb0364e16ebd8034784d436c/.eslintrc.js#L28-L52
This setup allows ESLint to automatically fix the import order and address some other warnings by running yarn eslint --fix:
https://github.com/nowarp/misti/blob/f95260498be6801beb0364e16ebd8034784d436c/package.json#L32

Sounds like a great suggestion


Configure kmp refresh interval in Ratify default helm chart

What would you like to be added?
With newly added KPM refreshInterval property, we should provide a new setting in values in default ratify helm chart (disabled default state) so customer can enable refresh without using custom chart
Anything else you would like to add?
No response
Are you willing to submit PRs to contribute to this feature?

[ ] Yes, I am willing to implement it.

Hi @shahramk64 , here is the doc describe this new value. https://github.com/ratify-project/ratify-web/pull/103/files. We can follow up later if you have any questions. thanks


fix: deps bump and react 16.8 compatibility

Hello, cool tool! :smile:
I've always been on the 'you may not need redux' side, but with hooks api I may give it a try.
So react 16.8 was released few hours ago and your package (as-is) unfortunately throws invariant violations (code-sandbox example does it too :warning: ).
But I really, really wanted to try it so here's a fix^^

Updated reducer typing, because signature changed
Added init param to match 16.8 interface, so id param in hooks unfortunately need to go to the fourth place (needs docs update)
Refactored useContext hooks from useMemo body
Deps bump to latest

Suggestions:

Change hooks signature a bit to allow undefined instead of identity (state => state) for third param?
Reuse original react typings more because there are cool overloads?

In case anyone googling for a quick fix: yarn add vadistic/reinspect#reinspect-v0.4.3-gitpkg

I've realised, that I somehow half-assed support for a usecase when somebody would actually want to make use this new init param :grimacing:
The case for inital state worked fine, but now you can properly use initalizer & initializer argument.
Those 3 cases are covered:
// this would work without assertion with added +2 overloads, but it's a bit too tricky for me this morning :)
const [] =  useReducer(myReducer, initalState, undefined as any, 'NAME')

const [] = useReducer(myReducer, initialState, state => state, 'NAME')

const init = (arg) => {
   hello: arg
}

const [] = useReducer(myReducer, 'world', init, 'NAME')

Also:

Updated typings to match reacts convention
Cut useMemo from useReducer, because I could not see how it was not completely superfluous (please review, maybe I'm missing something)

@vadistic I can do the signature overloading if you want

@troch I've managed ^^ Just shuffled them.
Also, added like 3 tests, I was halfway done with them so I thought I might commit.
Btw. I irrationally avoid function keyword, so I rarely overload this way (instead of interface overloading)  - any idea why the order of overloads mattered here? I've thought it's just simple declaration merging...

I was wondering.. would it make more sense to use a curried pattern for the useReducer/etc overloads?
eg. useReducer(myId)(normal, params, to, react)
Feels cleaner to me (though obviously a breaking change.. but then it's currently broken anyway.. so..)

Any updates on this? This is currently unusable due to the 3rd param init.

Hey @antoniojps, yes will finalise it tonight and release.

@troch Thank you for the open source work!


Added an example to connection samples

Added an example to the connections samples to show users that the ['collections'] argument is optional on connect.

Awesome!


Overlapping Entries

When two entries overlap... the entry gaining focus should be z-indexed to the top.

They should be working right, the only real problem is CSS, the buttons are floating, which the only real thing that detected as wrapped by the entry is the math-input

*.math-field, sorry

Looks good to me.


Avoid .babelrc conflict with React Native

React Native uses different babel settings

@rpominov done

Thanks, I'll release a new version with this fix later today.

@aksonov It's released.

Thanks! I've just released https://github.com/aksonov/react-native-reactive based on Calmm-JS and KefirJS as Redux replacement.


Provide arm64 images for Whereabouts

To fully support arm64 based architectures, as requested in https://github.com/vmware-tanzu/community-edition/issues/2171 we need all the images to provide arm64 arch images.
Whereabouts does not provide arm64 image

@vmware-tanzu/pkg-whereabouts-owners FYI @zhanggbj


implements voice chat service messages

Hello,
I wanted to play with the VoiceChat service messages, but telebot lacked the support, hence this PR.
The VoiceChat service messages are part of the bot API v5.1.
I'm not sure of:

is it OK to add voicechat.go or it's better to stuff those declarations in some other file?
The Duration field of the VoiceChatEnded should be a time.Duration instead of a int? (it's the number of seconds)

Cheers!

Thank you!


Install .NET 8 SDK in github actions in develop/4.1

@inforithmics I had problems building Maui in the 'Release Nugets' action with both net7 and net8. I removed net8 to release at least part of our fixes. Perhaps you can help me figure out what the problem is. I had the same build problem locally. I mostly do not understand why it does build on the server in the main dotnet.yml.


Add new OS in the system requirements

Add Windows Server 2019 in the system requirements for bcp

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

#sign-off

#sign-off


Code quality improvement

Pre-commit is running a few standard checks, further improvement could be gained from:

pylint

[x] code
[x] tests

remaining problems are ignorable

[x] (not sure if this needs to be in CI tbh, just run when looking to edit)

[ ] tryceratops
[ ] TODO: investigate flake8/other options

For example with flake8 see mcx: .github/workflows/lint.yml and Makefile

I would also suggest adding an automated check for the maintenance of full docstring coverage (#13: now achieved).


Request returns 400 error!

Please follow the guide below

Issues submitted without this template format will be ignored.
You will be asked some questions and requested to provide some information, please read them carefully and answer completely.
Put an x into all the boxes [ ] relevant to your issue (like so [x]).
Use the Preview tab to see how your issue will actually look like.

Before submitting an issue, make sure you have:

[x] Updated to the latest version
[x] Read the README and docs
[x] Searched the bugtracker for similar issues including closed ones

Purpose of your issue?

[x] Bug report (encountered problems/errors)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections requests more details for particular types of issues, you can remove any section (the contents between the triple ---) not applicable to your issue.

For a bug report, you must include the Python version used, code that will reproduce the error, and the error log/traceback.
Paste the output of python -V here: Python 3.4.2
Code:
python3 watch_user_likers_stories.py

Error/Debug Log:
Request returns 400 error!
2019-08-31 17:13:45,581 - INFO -
            Going to get your likers and watch their stories (and stories of their likers too).
            You can specify username of another user to start (by default we use you as a starting point).

Traceback (most recent call last):
  File "watch_user_likers_stories.py", line 41, in <module>
    user_to_get_likers_of = bot.user_id
  File "/usr/local/lib/python3.4/dist-packages/instabot/bot/bot.py", line 286, in user_id
    return self.api.user_id
  File "/usr/local/lib/python3.4/dist-packages/instabot/api/api.py", line 502, in user_id
    return self.cookie_dict["ds_user_id"]
KeyError: 'ds_user_id'

Describe your issue
I tried out instabot today first time. I wanted to use it to view stories of other users. When I try it I'm asked for account first and then I get the error above. I have the same problem with another example python scripts. I think the problem could be that I'm on vacation in another country now (Instagram knows where I am) and I'm trying to run the statement above from a remote server in my home country. After every run Instagram website asks me if I just tried to login in my home country (Germany):

I can commit that it was me, but after the next run of python script I see this question again.
Can anyone tell me what I'm doing wrong?
Best regards

Same here.

Same.

Same here. USA

I deleted my username and entered it again. After that it seems to work. The password was definitely right. Don't ask me what have changed. Try it also. I will close the issue.

Fixed!
Solution: Check your username and pass
Business accounts will not work for this type of login.

I had changed my profile to personal but still no luck.

Same problem here!
After trying to log in instagram detected an atypical login attempt and asked me if I tried.

This is a common problem happens to 2 out of 5 accounts, this can be fixed 90% of the time by using challenge required.


How do I rename a dlpy model?

I have successfully loaded a model that was previously saved, and I called get_model_info() to see the 'Model Name', as in the screenshot below.

I need to rename the model, but nothing I've tried so far has worked.  Can someone please provide the code needed to rename the model?  Thanks so much.

The parameter model_name is optional when creating a pre-defined model using DLPy API. Once specified, it becomes the hash key for saving/loading model attributes and parameters. Currently we don't have any function that can change the name. Closing issue.

The parameter model_name is optional when creating a pre-defined model using DLPy API. Once specified, it becomes the hash key for saving/loading model attributes and parameters. Currently we don't have any function that can change the name. Closing issue.


Slab: slab full when it's actually not

The reference count never arrives to the max reference count but still the slab returns NULL.

Freelist on the slab shrinks for some unknown reason. (Something wrong with the freelist management).


Revert ResourceRegistrar@register

The two breaking change:
https://github.com/illuminate/routing/commit/660cd7174334ce0d59dfff2ac1e846a8c5dc43ac#diff-c6855a9f8a00a1c3b95fee1c42f0ff1e
https://github.com/illuminate/routing/commit/828a5527a7b8bfb07619aa140626f8798b969f33

I think the merge is safe. It would be great if someone takes a look at this.


Roc searches for .o instead of .a in built platform when used with --build-host

With a locally built basic-webserver platform, when I try to build against it a project (in my case the https://github.com/lukewilliamboswell/roc-htmx-playground/) Roc searches for linux-x64.o instead of linux-x64.a, which was built in the platform:
roc build --build-host --suppress-build-host-warning --linker=legacy src/main.roc
🔨 Building host ...
ld: cannot find src/../../basic-webserver/platform/linux-x64.o: No such file or directory
thread 'main' panicked at crates/compiler/build/src/program.rs:1058:17:
not yet implemented: linker failed with exit code Some(1)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

The built platform files:
$ ls platform/
Command.roc
Dir.roc
EnvDecoding.roc
Env.roc
FileMetadata.roc
File.roc
Http.roc
InternalCommand.roc
InternalDateTime.roc
InternalError.roc
InternalFile.roc
InternalHttp.roc
InternalPath.roc
InternalSQL.roc
InternalTcp.roc
libapp.roc
libapp.so
linux-x64.a
linux-x64.rh
main-glue.roc
main.roc
metadata_linux-x64.rm
MultipartFormData.roc
Path.roc
PlatformTasks.roc
Sleep.roc
SplitList.roc
SQLite3.roc
Stderr.roc
Stdout.roc
Tcp.roc
Url.roc
Utc.roc

Roc version:
roc nightly pre-release, built from commit 8dbc909 on Fr 15 Nov 2024 09:02:07 UTC
Related Zulip discussion: https://roc.zulipchat.com/#narrow/channel/231634-beginners/topic/client-side.20web.20in.20Roc/near/485096172
OS:
$ lsb_release -a
LSB Version:    n/a
Distributor ID: EndeavourOS
Description:    EndeavourOS Linux
Release:        rolling
Codename:       rolling
$ uname -a
Linux zephy 6.12.1-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Fri, 22 Nov 2024 16:04:23 +0000 x86_64 GNU/Linux

The --build-host flag is for internal tests only and should not be used. The previous functionality for host rebuilding was removed in #6859, and some functionality retained behind this flag for the purpose of e2e testing internally.
The specific issue experienced here is caused by https://github.com/roc-lang/roc/blob/a9682517093f1e8cdd75572269e5acdcadbb45cf/crates/compiler/build/src/program.rs#L1095 I believe.
I propose we close this issue as the functionality for this use case is not supported.
I think roc build --linker=legacy src/main.roc (without the --build-host flag) should be working ok. Are you able to confirm this?

Confirmed. Without --build-host with the locally built platform it works fine.


view a list of reviews for a single restaurant

As a user, when viewing a single restaurant, you should be able to see reviews written about that restaurant.

Waiting for final decision on how we are going to structure our  data from the api


pointer: Reading messages in stream narrows is not updating the pointer for home view.

Issue
I've read all messages in stream narrows and when I came back to the home view the pointer has not been updated - had to manually scroll the messages to the bottom.
Expected behaviour
When reading all the unread messages in stream narrow view, the pointer in the home view should go to the bottom of the message list.
Sanity check
In the mobile app I was scrolled to the bottom on home view - it didn't update the pointer for the web app in case you were wondering :)

This is a duplicate of #1529.

(Thanks for the reminder about this though!  That's an important issue we should invest in resolving soon!)


encoding issue for example

Hi
I am trying the example.py, however got the error below. Is this a lib issue?
Traceback (most recent call last):   File "example.py", line 94, in <module>     ex.generate_corpus(article_links)   File "/home/work/.jumbo/lib/python2.7/site-packages/news_corpus_builder/news_corpus_generator.py", line 101, in generate_corpus     'category':category})   File "/home/work/.jumbo/lib/python2.7/site-packages/news_corpus_builder/news_corpus_generator.py", line 105, in _save_article     print "Saving article %s..." %(clean_article['title']) UnicodeEncodeError: 'latin-1' codec can't encode character u'\u2018' in position 39: ordinal not in range(256)

Also encountering this

First of all thank you for such an awesome tool.
if need to know three things.

can we query google news for " sentence" instead of words.
If i want to extract the creation time of news from the web page along with body and title.
If i want to extract news from specific time period ( e.g. specific date)

Thanks in advance.

Will take a look and push an update  soon.  This was not meant for Py3 will look at making it compatible with both py2.x & py3.x

can we query google news for " sentence" instead of words.
You can do that currently by using quotes "This is the sentence you would like to search "

If i want to extract the creation time of news from the web page along with body and title.
Might not be able to obtain the creation time for all news articles. But an update could be made to extract and save the article date.

Will do it once I have the extra time.  Feel free to submit a pull request

If i want to extract news from specific time period ( e.g. specific date)
However to search and get results for a specific date range we might not be able to do this with the news.google.com

Will probably have to update to using Google Web Search or another endpoint if a date parameter is not present for news.google.com


Update Font Awesome to 5.0.6

I wanted a specific icon which was only made available in v5 of FontAwesome so I went ahead and upgraded the sitewide version.
With v5 there's no longer any need to keep the binary files locally, they are all loaded remotely, so this PR deletes all the local FA assets.
In layouts/partials/header.html I load the remote CSS. In v5 the icons have been split from fa into fas (fontawesome solid) and fab (fontawesome brands). There's a shim to ease transition to v5 but I just replaced all the selectors to point to the new icons so I am NOT loading the upgrade shim. Full v4 to v5 docs are here: https://fontawesome.com/how-to-use/upgrading-from-4
I also wrote a help page on how to include icons. As a user I was not aware the theme loaded fontawesome before I really dug into the source code. It's only in English, sorry i don't speak French :)

Thank you, it's a very nice PR!
I would prefer local assets though. This kind of documentation theme can be used in private networks that do not have Internet access. So, we should avoid having assets loaded from Internet.

Ok I didn't consider offline use on private network. I'll bring assets back into local.

Loading the new CSS file, the name of which changed to fontawesome-all.min.css.
The fonts are loaded in from the path webfonts/ so rather than modify the upstream CSS I added the font files in the new path. This does mean there is now a fonts/ and webfonts.

Bump. Any possibility of getting this pushed through?

@matcornic Also bumping, it would be awesome if this PR was merged.


can't use multiple f's when function returns x

def f1(param):
    return [0, param], [0, param]
def f2(param):
    return [param, 0], [0, param]
fig, ax, slider = interactive_plot([f1, f2], param=(0,10))

lol what was I thinking with this line?
https://github.com/ianhi/mpl-interactions/blob/ef118f70a998b9d72108b4514a4d2ed9d803349a/mpl_interactions/pyplot.py#L320
I have no idea what the second term of the if is trying to accomplish

Evidently I wrote it down here: https://github.com/ianhi/mpl-interactions/issues/24#issue-667438075
and it turns out that i was doing that indexed_x craziness becuase you need to make sure you have both x and y values in order to use set_data. But I think a better solution may be to update the logic around set_data rather than restrict what's going on
def f3(param):
#     return [param, 0], [0, param]
    return [param]

will fail (you gotta look into log console to see it though)

This will rendered irrelevant by #119


test: fix flaky tests when running on CI

Part of: https://linear.app/customerio/issue/MBL-164/cdp-branch-flaky-tests-on-ci
We have been experiencing some flaky tests, only when running on our CI. After reviewing the test functions and the error messages thrown on CI, I think that the issue is because of slow performance when running the test suite on the CI. After doing some research online, others were sharing similar issues, specifically when running tests on Xcode 15.0 and 15.1. Xcode release notes also share known issues when running tests on CI and slow performance.
By updating our CI to macos 14 github action runners, we are installing Xcode 15.2 which has better test performance.

Results look promising.
This PR ran the test suite in 43 seconds. Previously when running on mac-13 runner, tests took 104 seconds.
Also, reduces the entire CI job that runs test suite from 15 min to 7 min.
Resources:

Fast: https://github.com/customerio/customerio-ios/actions/runs/8252329378/job/22571561816?pr=635
Slow: https://github.com/customerio/customerio-ios/actions/runs/8251672707/job/22569288731?pr=633

@Shahroz16 looking at the timestamps generated by fastlane, I do not believe that this is taking up more time. I do understand if the warning is a little annoying.
I created a ticket to reduce the time it takes to run the test suite. The scope of that ticket would be great for that kind of change.

@levibostian tests are still failing, is it related or different?

@Shahroz16 Different. See this comment for more context.
I also updated the ticket description to call-out these remaining flaky tests.

✓ Commit merged in pull request #636


website is down

Morning, just a heads up that https://www.steampress.io/ is down at the moment
Cheers

Thanks for letting me know! This was due to Heroku enforcing TLS on Postgres and has now been fixed

My pleasure Tim!
On Wed, Mar 31, 2021 at 5:30 AM Tim Condon @.***> wrote:

Thanks for letting me know! This was due to Heroku enforcing TLS on
Postgres and has now been fixed
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/brokenhandsio/SteamPressExample/issues/28#issuecomment-811030948,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEEBNNCPSXDFEPLMPN25DMDTGMIYBANCNFSM4ZVE5ETA
.


Projects summary endpoint

This is a WIP draft PR for implementing a "Projects Summary" web endpoint. The goal is to provide users with summary stats for one or more projects they are a member of.
So far, the stats captured here are the number of families, participants, samples, sequencing groups, and completed CRAMs, grouped by dataset AND sequencing type.
TODO:
So, in the web layer I've put each of the relevant queries into a function, but this is basically just clutter right now, the queries could exist as variables and there would be no difference.
Right now, the code iterates through the input projects and sequencing types and evaluate each of the 5 queries for all combinations of project and sequencing type, adding the result to the response array on each loop.
This seems suuper inefficient, and I think the more obvious way to do this would be to evaluate all 5 queries for all input projects & sequencing types, and then filter the results of this complete query down into distinct ProjectsSummaryInternal objects.
So, could we, upon calling the get_projects_summary(projects, sequencing_types) function, evaluate the 5 queries for all projects and seq types (with a fetch_all), then subset the results of this by dataset and seq type once we get to the main loop? This way the 5 queries would only be evaluated once each. Just not sure how to do this right now.
Additional stats to add include the number of sequencing groups in the latest ES-Index and in the latest joint-call.

Codecov Report
Attention: 114 lines in your changes are missing coverage. Please review.

Comparison is base (d5e9e84) 72.05% compared to head (f3d3530) 71.91%.
Report is 195 commits behind head on dev.

Additional details and impacted files
@@            Coverage Diff             @@
##              dev     #533      +/-   ##
==========================================
- Coverage   72.05%   71.91%   -0.15%
==========================================
  Files          90      108      +18
  Lines        7747     8858    +1111
==========================================
+ Hits         5582     6370     +788
- Misses       2165     2488     +323

Files
Coverage Δ

api/graphql/schema.py
76.56% <100.00%> (+1.48%)
:arrow_up:

api/routes/sequencing_groups.py
65.38% <100.00%> (ø)

api/settings.py
75.00% <100.00%> (+0.64%)
:arrow_up:

api/utils/openapi.py
42.85% <100.00%> (ø)

db/python/layers/participant.py
68.34% <100.00%> (+2.37%)
:arrow_up:

db/python/layers/sequencing_group.py
57.89% <ø> (ø)

db/python/tables/participant.py
55.38% <ø> (+3.84%)
:arrow_up:

db/python/tables/sequencing_group.py
67.88% <100.00%> (ø)

etl/extract/main.py
83.72% <100.00%> (ø)

etl/test/test_etl_extract.py
100.00% <100.00%> (ø)

... and 42 more

... and 15 files with indirect coverage changes

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

An implementation of the Seqr projects dashboard.

Use new ProjectAPI endpoint get_project_insights_stats(projects, sequencing_types) to retrieve counts of families, participants, samples, sequencing groups, CRAMs, the latest joint call analysis, SNV ES-Index analysis, and SV ES-Index analysis - for each dataset + sequencing type combination
Render these as rows in a table located at seqr/stats, with the option to select which projects and sequencing types to display

TODO:

Refactor the naming of the new files and classes, etc. Currently a mess of "Project Insights", "Insights Stats", "Insights Details", "Seqr Stats"... will choose one to decide on
Get information about the dataset analyses (AnnotateDataset, SNV Es-Index, SV ES-Index) more generically rather than with fixed fields in the data model
Add more of this analysis information to the mouseover tooltips - e.g. Created at timestamp, Output path
Add a "Detailed" view, which can provide sequencing group level granularity for the selected sequencing projects and types. Use Virtuoso to handle the rows without declaring explicit pagination.

Hi @illusional - once again thank you for the last round of feedback. Once again requesting a re-review from you :) 🙏
Please feel free to handball this to anyone else if it helps get it through. My goal right now is to have this in a satisfactory state to merge, allowing it to be more easily iterated on by future, smaller PRs.
Main changes since last review

Use getMyProjects instead of getSeqrProjects when fetching available projects
Seriously overhauled typing in project_insights_layer.py, now everything is very heavily typed
Removed repetitive chunks of code in the layer, and reduced nesting / indentation by defining more functions - specifically for the get_project_insights_details and get_project_insights_summary functions at the bottom of the layer
Better querying in the layer, using max timestamp and joining on analysis ID where required, so queries are much more readable. Also using GROUP_CONCAT when gathering many values in a grouping query.
Removed all references to project ID on the user-side / front-end, only project names are used now
Added "Insights" as a dropdown to Metamist webui navbar, with two options, "Summary" or "Details" which take you to /insights/summary and /insights/details respectively.
Heavily refactored frontend to remove instances of highly repetitive code, especially as relates to table headers / columns.

Now, HeaderCell.tsx defines the possible column names, as well as the list of column names specifically for both the Summary and Details tables.
These columns for each table are exported as summaryTableHeaderCellConfigs and detailsTableHeaderCellConfigs - these are then passed around and used by the other parts of the module. This means the table columns are all defined in a centralised place and reused from there, making future updates significantly easier.

Refactored ProjectAndSeqTypeSelector.tsx to make the code here less repetitive & more re-usable, now project and sequencing type selections are both instances of the same Selector component.
Refactored SummaryTable.tsx and DetailsTable.tsx

These components now contain only functions and information to render cell content, handle sorting, and handle exporting.

Refactored Summary.tsx and Details.tsx

These components now handle getting the initial data, storing the state for which filters have been applied (all stored in the selectedValues and filteredData state - no longer one state per column filter) and passing the data on to the Table components.

Added dedicated FilterData.tsx component, to handle the filtering generically. Now when users click the filters on each header, the values shown are a combination of the already-applied filters, and the available values of that column with no filtering applied. Bit hard to explain, but we don't want values in the same column to drop out of the available filters immediately after filtering on a value, otherwise we can't select multiple values to filter on.
Moved the HtmlToolTip.tsx into its own component in /web/shared/utilities/.
Created dedicated testing module for the Project Insights endpoints.

TODO in future

Add more tests!
Add endpoints to GraphQL with filtering
Improve layers logic, further reduce repetitive sections of code, optimise & generalise queries where possible
Add more columns (specifically STRipy report outlier loci and report dates in the DetailsTable, SV calling status in DetailsTable, QC report links in SummaryTable)
Generally improve UI and UX
Add new dashboards with more visualisations of the state of analyses in the various projects
Transparently display which analysis (e.g. the es-indices, the annotated dataset) each sequencing group is a part of in the DetailsTable view
Unify the Dashboards so they are accessed from the same page, with a toggle to display which dashboard table specifically, while keeping the filtering and project/seq type selection the same
Add "export to csv-tsv" button for the SummaryTable dashboard

@illusional I've brought in the auth changes and latest updates from dev and implemented them into the project_insights db layer here, as well as addressing most of the changes you outlined above.
I know there's some funky codecov stuff happening, but I am happy to have this merged this into dev if there are no urgent issues to address! Thank you very much again for your time and patience :)


Faster inference

Is there a way to run considerably faster inference for a low tradeoff in accuracy without retraining the model? For example, any parameters I can change in the experiments.conf.

You can also try setting coref_depth to 1. The effect would be similar to taking a CRF model, dropping the higher-order factors, and just using the unary potentials to make predictions.

Thanks, that was useful. Due you think the setting coarse_to_file = false is a good idea?

Probably not, the coarse to fine inference makes the model both faster and more accurate.


Paypal is not working

Hi
I am using spree 3.1 and spree_braintree_vzero 3-1-stable for payment.
I am using BraintreeVzeroDropDownUi gateway.
I have a sandbox account on Braintree but when I clicked on Paypal at payment page a new window open with message Sorry we cannot connect to PayPal. Please try again in a few minutes.
How can I fix this issue.

Please check #58

Issue solved after creating a new Braintree sandbox id with US merchant location.


Reading metadata

Is it possible to retrieve other data in mpeg-ts container? For example a KLV data stream?

Don't know if it helps for the accurate seeking?


🔄 synced file(s) with worgarside/github-config-files

synced local file(s) with worgarside/github-config-files.

This PR was created automatically by the repo-file-sync-action workflow run #6147469586

This PR is empty, closing it. :no_good:


Add PlatON coin

Description
Add PlatON Coin.
How to test
Test in the same manager as KCC was tested.
Types of changes
New feature (non-breaking change which adds functionality)
Checklist

[ ] Create pull request as draft initially, unless its complete.
[x] Add tests to cover changes as needed.
[x] Update documentation as needed.
[ ] If there is a related Issue, mention it in the description.

If you're adding a new blockchain

[x] I have read the guidelines for adding a new blockchain.

Thanks for your interest, we decided not to add PlatOn for now

Thanks for your interest, we decided not to add PlatOn for now

But why? I have clarified here(https://github.com/trustwallet/wallet-core/pull/2232#discussion_r887538653) about Slip44 ID.


Improve UX Playground

Main Changes

Allow to adjust the width and height of the panels #554.

Remove white space at page footer

Removes the StatusBar module, as the JavaScript and Problems tabs already show the errors. See the issue with StatusBar

More Responsive

Nice changes. Thanks!


Adding new field to accept datepicker display type in android

Thank you @kapilratnani !
Should I release it on npm soon? (If you need it I can release it this evening).

That would be great. Thanks. Make sure to test things at your end.
Also FYI, there is a bug in android 7.0 which prevents date picker to open in spinner mode. The issue is fixed in 7.1. Just to let you know if someone reports that it doesn't work.
https://code.google.com/p/android/issues/detail?id=222808

Released in 4.1.0 👍 @kapilratnani


Boolean Product of Matrix

🚀 Feature
(A clear and concise description of what the feature is.)
Have you read the Contributing Guidelines on Pull Requests?
Yes.

/assign


benchmark comparisons with other alternatives

Let's do a benchmark comparison with Lodash and other libraries. Let's also create examples and benchmark tests about the algorithms. I know it's a big job, but with these new benchmarks, we can better identify performance deficiencies and make performance-oriented improvements together.

@meftunca many have noticed that this repo is - unfortunately - not being maintained anymore.  What's the point of making benchmakrs then ?

@stefaanMLB What do you mean? The last update was two weeks ago. If the development has stopped, there should be a general notification.

@meftunca Lodash repo is not being maintained. What are the other alternatives?

try radashi

Over at radashi-org/radashi, we are planning on getting benchmarks set up. After that, we'd be open to adding Lodash comparison benchmarks for Radashi functions that overlap with existing Lodash functions.

Ramda.js
Underscore.js
Lazy.js
Collect.js
Snap.js

Hi @meftunca, we'll definitely try to compare Radashi against all major competitors, except for those whose philosophy is vastly different (Ramda.js and Lazy.js) and those that are seemingly antiquated (Underscore). People who never made the switch from Underscore to Lodash are not really a priority. People who prefer point-free, functional programming aren't a priority either.


Project secret rename

What Changed

Updated secret name to what we renamed it.
How to test

Run the tests, make sure the Chromatic publish and UI Tests tests complete
Change Type

[ ] maintenance
[ ] documentation
[x] patch
[ ] minor
[ ] major

@tevanoff just a heads-up, you'll need to pull main into your working branches for the Chromatic playwright CI job to work.

:rocket: PR was released in v0.0.51 :rocket:


In-app notification on iOS when application is active

Per everything that I have read, we should not be receiving an in-app pop up when a push message is received and the app is open. However, we are. The message pops up, which has a native look/feel, and has OK/Cancel buttons.
We do not have anything in the JavaScript code to alert when a push is received.

Can someone proive details on this info.plist suggestion.  I have no such file.  Suddenly out of the blue I am also getting the notification in the app when active.
Xcode shows : "Will show push notifications alert"


Fork Broadcast

Closes #93

Should the newly created mutex be locked on all TestRPC methods?
p.heightRange = heightRange is deleted (but this is fixed by #100)
A pointer to MyTopologyCache is given to SyncService, this is unsafe as it's updated concurrently in downloadManagerLoop()
The deleted TODO comment suggesting to re-implement GetAncestorTopologyAtHeights() in the block store should be reinstated (implementing in the block store this will still give great performance benefits due to fewer round trips and low-level seek optimizations)

Shared MyTopologyCache resolution
Suggested long-term fix is to move MyTopologyCache to top-level (i.e. Node or SyncManager) and make it threadsafe.  However it seems like a bit of work, so I suggest that for this ticket, we just acknowledge that it's currently racy, and put writing the fix into another ticket.
Suggested fixes
Reinstate the comment and create mutex on TestRPC methods.  p.heightRange = heightRange issue will be fixed by #100.  Another ticket should be filed for implementing shared, thread-safe MyTopologyCache (and possibly mentioned as related to #98).

The deleted TODO comment suggesting to re-implement GetAncestorTopologyAtHeights() in the block store should be reinstated (implementing in the block store this will still give great performance benefits due to fewer round trips and low-level seek optimizations)

The comment was deleted because it suggested that p2p should unbox the block to access previous in the block header. When we redesigned the block structure, I thought it was understood by all that we were doing this in part so that the header could be freely access via microservices instead of slapping an additional topology on every struct that contains a block. (See koinos/koinos-block-store#57)
And upon further review, it appears that this function is not called anywhere. So instead of restoring a comment I do not agree with, I think we should remove the method entirely.

In the interests of getting this merged, we added the thread-safe MyTopologyCache as #101 and thread-safe TestRPC as #102.


base_url is omitted in JSON and CSV views

I have a datasette deployment, using Apache2 to reverse proxy:
   ProxyPass /ged http://thor.phfactor.net:8001
   ProxyPreserveHost On

In settings.json I have
{
    "base_url": "/ged/",
    "trace_debug": 1,
    "template_debug": 1
}

and datasette works correctly. However, if you view a query and then click on the 'This data as json, CSV' both links omit the base_url prefix and are therefore 404.

base_url has been a source of so many bugs like this! I often find them quite hard to replicate, likely because I haven't made myself a good Apache mod_proxy testing environment yet.

Having a live demo running on Cloud Run that proxies through Apache and uses base_url would be incredibly useful for replicating and debugging this kind of thing. I wonder how hard it is to run Apache and mod_proxy in the same Docker container as Datasette?

This pattern looks like it can help: https://ahmet.im/blog/cloud-run-multiple-processes-easy-way/

I now have a Dockerfile in https://github.com/simonw/datasette/issues/1521#issuecomment-974388295 that I can use to run a local Apache 2 with mod_proxy to investigate this class of bugs!

Bug confirmed:

The relevant test is this one: https://github.com/simonw/datasette/blob/30255055150d7bc0affc8156adc18295495020ff/tests/test_html.py#L1608-L1649
I modified that test to add "/fixtures/facetable?sql=select+1" as one of the tested paths, and dropped in an assert False to pause it in the debugger:
    @pytest.mark.parametrize(
        "path",
        [
            "/",
            "/fixtures",
            "/fixtures/compound_three_primary_keys",
            "/fixtures/compound_three_primary_keys/a,a,a",
            "/fixtures/paginated_view",
            "/fixtures/facetable",
            "/fixtures/facetable?sql=select+1",
        ],
    )
    def test_base_url_config(app_client_base_url_prefix, path):
        client = app_client_base_url_prefix
        response = client.get("/prefix/" + path.lstrip("/"))
        soup = Soup(response.body, "html.parser")
        if path == "/fixtures/facetable?sql=select+1":
>           assert False
E           assert False

BUT... in the debugger:
(Pdb) print(soup)
...

This data as
  json,
  testall,
  testnone,
  testresponse

Those all have the correct prefix! But that's not what I'm seeing in my Dockerfile reproduction of the issue.
Something very weird is going on here.

I added template_debug in the Dockerfile:
datasette fixtures.db --setting template_debug 1 --setting base_url "/foo/bar/" -p 9000 &\n\

And then hit http://localhost:5000/foo/bar/fixtures?sql=select+*+from+compound_three_primary_keys+limit+1&_context=1 to view the template context - and it showed the bug, output edited to just show relevant keys:
{
    "edit_sql_url": "/foo/bar/fixtures?sql=select+%2A+from+compound_three_primary_keys+limit+1",
    "settings": {
        "force_https_urls": false,
        "template_debug": true,
        "trace_debug": false,
        "base_url": "/foo/bar/"
    },
    "show_hide_link": "/fixtures?sql=select+%2A+from+compound_three_primary_keys+limit+1&_context=1&_hide_sql=1",
    "show_hide_text": "hide",
    "show_hide_hidden": "",
    "renderers": {
        "json": "/fixtures.json?sql=select+*+from+compound_three_primary_keys+limit+1&_context=1"
    },
    "url_csv": "/fixtures.csv?sql=select+*+from+compound_three_primary_keys+limit+1&_context=1&_size=max",
    "url_csv_path": "/fixtures.csv",
    "base_url": "/foo/bar/"
}

This is so strange. edit_sql_url and base_url are correct, but show_hide_link and url_csv and renderers.json are not.

Here's the code that generates edit_sql_url correctly: https://github.com/simonw/datasette/blob/85849935292e500ab7a99f8fe0f9546e903baad3/datasette/views/database.py#L416-L420
And  here's the code for show_hide_link: https://github.com/simonw/datasette/blob/85849935292e500ab7a99f8fe0f9546e903baad3/datasette/views/database.py#L432-L433
And for url_csv: https://github.com/simonw/datasette/blob/85849935292e500ab7a99f8fe0f9546e903baad3/datasette/views/base.py#L600-L602

The implementations of path_with_removed_args and path_with_format:
https://github.com/simonw/datasette/blob/85849935292e500ab7a99f8fe0f9546e903baad3/datasette/utils/__init__.py#L228-L254
https://github.com/simonw/datasette/blob/85849935292e500ab7a99f8fe0f9546e903baad3/datasette/utils/__init__.py#L710-L729

In the ?_context= debug view the request looks like this:
    "request": "<datasette.utils.asgi.Request object at 0x7faf9fe06200>",

I'm going to add a repr() to it such that it's a bit more useful.

Modified my Dockerfile to do this:
RUN pip install https://github.com/simonw/datasette/archive/ff0dd4da38d48c2fa9250ecf336002c9ed724e36.zip

And now the request in that debug ?_context=1 looks like this:
    "request": "<asgi.Request method=\"GET\" url=\"http://localhost:9000/fixtures?sql=select+*+from+compound_three_primary_keys+limit+1&_context=1\">"

That explains the bug - that request doesn't maintain the original path prefix of http://localhost:5000/foo/bar/fixtures?sql= (also it's been rewritten to localhost:9000 instead of localhost:5000).

Still not clear why the tests pass but the live example fails.

Figured it out! The test is not an accurate recreation of what is happening, because it doesn't simulate a request with a path of /fixtures that has been redirected by the proxy to /prefix/fixtures.

https://docs.datasette.io/en/stable/deploying.html#apache-proxy-configuration says I should use ProxyPreserveHost.

I think what's happening here is Apache is actually making a request to /fixtures rather than making a request to /prefix/fixtures - and Datasette is replying to requests on both the prefixed and the non-prefixed paths.
This is pretty confusing! I think Datasette should ONLY reply to /prefix/fixtures instead and return a 404 for /fixtures - this would make things a whole lot easier to debug.
But shipping that change could break existing deployments. Maybe that should be a breaking change for 1.0.

In the meantime I can catch these errors by changing the test to run each path twice, once with and once without the prefix. This should accurately simulate how Apache is working here.

Thanks to #1522 I have a live demo that exhibits this bug now: https://apache-proxy-demo.datasette.io/prefix/fixtures/attraction_characteristic

In the meantime I can catch these errors by changing the test to run each path twice, once with and once without the prefix. This should accurately simulate how Apache is working here.

This worked, I managed to get the tests to fail! Here's the change I made:
diff --git a/tests/test_html.py b/tests/test_html.py
index f24165b..dbdfe59 100644
--- a/tests/test_html.py
+++ b/tests/test_html.py
@@ -1614,12 +1614,19 @@ def test_metadata_sort_desc(app_client):
         "/fixtures/compound_three_primary_keys/a,a,a",
         "/fixtures/paginated_view",
         "/fixtures/facetable",
+        "/fixtures?sql=select+1",
     ],
 )
-def test_base_url_config(app_client_base_url_prefix, path):
+@pytest.mark.parametrize("use_prefix", (True, False))
+def test_base_url_config(app_client_base_url_prefix, path, use_prefix):
     client = app_client_base_url_prefix
-    response = client.get("/prefix/" + path.lstrip("/"))
+    path_to_get = path
+    if use_prefix:
+        path_to_get = "/prefix/" + path.lstrip("/")
+    response = client.get(path_to_get)
     soup = Soup(response.body, "html.parser")
+    if path == "/fixtures?sql=select+1":
+        assert False
     for el in soup.findAll(["a", "link", "script"]):
         if "href" in el.attrs:
             href = el["href"]
@@ -1642,11 +1649,12 @@ def test_base_url_config(app_client_base_url_prefix, path):
             # If this has been made absolute it may start http://localhost/
             if href.startswith("http://localhost/"):
                 href = href[len("http://localost/") :]
-            assert href.startswith("/prefix/"), {
+            assert href.startswith("/prefix/"), json.dumps({
                 "path": path,
+                "path_to_get":  path_to_get,
                 "href_or_src": href,
                 "element_parent": str(el.parent),
-            }
+            }, indent=4, default=repr)

 def test_base_url_affects_metadata_extra_css_urls(app_client_base_url_prefix):

Adding that test found (I hope!) all of the remaining base_url bugs. There were a bunch! I think I finally get to close #838 too.

Ouch a nasty bug crept through there - https://datasette-apache-proxy-demo-j7hipcg4aq-uc.a.run.app/prefix/fixtures/compound_three_primary_keys says

500: name 'ds' is not defined

OK, i think I got all of them this time!
The latest demo is now live at https://datasette-apache-proxy-demo.fly.dev/prefix/fixtures/sortable?_facet=pk2
I'm closing this issue, but feel free to re-open it if you spot any that I missed.

I think what's happening here is Apache is actually making a request to /fixtures rather than making a request to /prefix/fixtures - and Datasette is replying to requests on both the prefixed and the non-prefixed paths.
This is pretty confusing! I think Datasette should ONLY reply to /prefix/fixtures instead and return a 404 for /fixtures - this would make things a whole lot easier to debug.
But shipping that change could break existing deployments. Maybe that should be a breaking change for 1.0.

On further thought I'm not going to do this. Having Datasette work behind a proxy the way it does right now is clearly easy for people to deploy (now that I've fixed the bugs) and I trust my improved tests to catch problems in the future.

thanks so very much for the prompt attention and fix! Plus, the animated GIF showing the bug is just extra and I love it. Interactions like this are why I love open source.


Updating release documentation to include release notes generator

What type of PR is this?
/kind documentation
What this PR does / why we need it:
I tried this process out with #1254 and it definitely simplifies things.
Does this PR introduce a user-facing change?:
NONE

/lgtm


The pipeline controller keeps refreshing logs

When we were troubleshooting a problem, we needed to check the pipeline controller logs and found that the logs were constantly refreshing and could not be viewed.
Finally, we found that there were several pipelines that were still executing the finale task, which caused the problem of constantly refreshing the logs.
These pipelines set the same pipeline and tasks timeouts.
Expected Behavior
The pipeline controller will not flush logs repeatedly.
I've provided a simple example.
apiVersion: tekton.dev/v1
kind: PipelineRun
metadata:
  name: example
spec:
  pipelineSpec:
    finally:
     - name: example-01
       taskSpec:
         steps:
         - image: alpine
           name: final-task
           script: sleep 1h
    tasks:
     - name: example-00
       taskSpec:
         steps:
         - image: alpine
           name: task
           script: echo "hello"
  timeouts:
    pipeline: 1h0m0s
    tasks: 1h0m0s

We can observe that the pipeline controller is constantly refreshing logs.
Additional Info
tekton: 0.53.0

/assign


Question about symmetric quantization settting.

Hi, thanks for your great work!
I have a question about the quantization module. In your paper,

Looks like the unsigned symmetric quantization is used in your PD-Quant framework, but the code https://github.com/hustvl/PD-Quant/blob/e12038edd0c39d09772279dba90c43ce9cb5170d/quant/quant_layer.py#L50 is asymmetric quantization.

Hi, I am sorry for this misunderstanding. The unsigned symmetric quantization we use is a kind of asymmetric quantization.  In general, symmetric quantization has signs including negative numbers, and the unsigned symmetric quantization we use here has only positive numbers.


DB file !

Thank you for sharing this script with us , but I couldn't  find  data base file ! could you please upload it .

See #2


Ignore file list

Is there a way to declare a .gatsbyignore so it will work like a .gitignore?

What is it you're trying to achieve, exactly?
Do you want to exempt files from your public folder? Why?
Probably better to stop gatsby from generating those unwanted files in the first place.

I am more interested into omitting system files like .DS_Store, thumbs.db, etc.

Might be worth adding some kind of exclude property to the config. I'm thinking an array and inside it we could either have minimatch (npm-style) or regex patterns.

At the time I replied to this ticket, I didn't realise we supportes per-object parameters with minimatch. Can we just add an ignore option to that?

Maybe? But not really a fan of that because it's supposed to only exists of values that we directly pass through to the SDK.
We'd be inserting our own arbitrary option in there.
Adding an exclude property to the config would be just as easy.

Could we make a place for object-specific settings, rather than purpose-building something just for ignoring? Then maybe in future we could move params into it? Agree that mixing/matching our config with Amazon's params is not a good plan.

Good idea!

Bump :)
For my two cents, having .DS_Stores on the server, so often readable publicly, I think is asking for trouble. In an cyber security world you really should be white listing the types of files you want, rather than blacklisting or "all", which is what we have now. Understand the risk is low, given it's a build folder, but can't be too safe.
A very short term option could be just to ignore things like .DS_Store, which I can't find any reason people would want deploying?


[FEAT]: Support more than one of the same type LLM Provider

What would you like to see?
Support more than one of the same type LLM Provider, e.g. Local AI or Generic OpenAI.
I have many "Local AI" providers but only one can be configured.

This is a duplicate of https://github.com/Mintplex-Labs/anything-llm/issues/1567 - same concept and idea. That issue is what we refer to this as so if when issue is closed then this request exists in the app


support default values in c# methods

believe this makes default values in mutaitons work
eg

        [GraphQLMutation]

        public int DefaultValueTest(int valueWithDefault = 8)
        {
            return valueWithDefault;
        }

Think this is failing due to another merge. Gets the same Reuse slot error (which seem familiar to me, something about trying to add an Expression type to graphql?)

Can we add a test/check that the schema/introspection is generating the default values too?

added in tests/code for sdl/introspection default values

added a couple more SDL default values checks which requires some form of serialisation, used a json serialiser but it's not quite right, so need another method.
eg
           schema.Query().AddField("user", new { user = new UserInputObject() { Name = "Steve" } }, (ctx, param) => ctx.Users.FirstOrDefault(), "Return a user by ID");
should become
           Assert.Contains("user(user: userInput = { name:\"Steve\"}): User", schema.ToGraphQLSchemaString());
but is currently
           Assert.Contains("user(user: userInput = { \"name\":\"Steve\"}): User", schema.ToGraphQLSchemaString());
which isn't valid SDL.
seems to work for enums, integers, booleans, and empty arrays though

My most hated test too :P Need to look at changing it some how..
Thanks though


Binary View Variadic Buffer Sizes are int64_t but variadic buffers only support int32_t

Describe the usage question you have. Please include as many useful details as  possible.
I noticed that the variadic buffer sizes exported through the C data interface for arrays that contain string/binary view data use int64_t as the size:
https://github.com/apache/arrow/blob/ee188600c511503b2973a569d7ec47b257655ebd/cpp/src/arrow/c/bridge.cc#L537
However, the implementation of binary views only use 32 bit offsets:
https://github.com/apache/arrow/blob/ee188600c511503b2973a569d7ec47b257655ebd/cpp/src/arrow/type.h#L833
Is this an intentional design decision or an oversight?
Component(s)
C++

It was brought to my attention that this is intentional and documented:
https://arrow.apache.org/docs/format/CDataInterface.html#binary-view-arrays
Thanks!


Update lexers to support many many lexers

The ./lexers file has not been updated for :four:  years :trollface:

In short, we couldn't use Elm in master:

now, we can:

Diff
Removed Lexers

Jade
Shell Session
ca65

Added Lexers

ABNF
ADL
Aheui
Ampl
Angular2
Arduino
BC
BNF
BST
BibTeX
Boogie
CAmkES
CPSA
CSS+mozpreproc
Cap'n Proto
CapDL
Clean
Component Pascal
Crmsh
Crystal
Csound Document
Csound Orchestra
Csound Score
Earl Grey
Easytrieve
Elm
EmacsLisp
Ezhil
Fish
Flatline
Forth
FortranFixed
HSAIL
HTML + Angular2
HTML+Twig
Hexdump
Isabelle
J
JCL
JSGF
JSON-LD
JSONBareObject
Javascript+mozpreproc
Juttle
Lean
LessCss
MSDOS Session
Monte
NCL
Nit
NuSMV
ODIN
PacmanConf
ParaSail
PkgConfig
PowerShell Session
Praat
Pug
QVTO
Relax-NG Compact
ResourceBundle
Roboconf Graph
Roboconf Instances
SAS
Shen
Silver
Snowball
Stata
SuperCollider
TADS 3
TAP
TASM
Tcsh Session
Termcap
Terminfo
Terraform
Thrift
TrafficScript
Transact-SQL
Turtle
Twig
TypoScript
TypoScriptCssData
TypoScriptHtmlData
VCL
VCLSnippets
WDiff
Whiley
X10
XUL+mozpreproc
Xorg
cADL
ca65 assembler
markdown
mozhashpreproc
mozpercentpreproc
xtlang

How can I update the binary data? I'll rather make automation to update it.

I did rake lexers.

🙆
I'll remove the binary from the repo. Thanks for the information.


Shadow helper not working in 5.1?

Discussed in https://github.com/twbs/bootstrap/discussions/34816

Originally posted by lowwhistler August 24, 2021
Not sure what's happening, but for me, Shadow is rendering the box black. Even the docs page has them rendered black in Chrome and Firefox?

What browser and version are you using? We need more info to investigate.
Also please don't double post with discussion. Either it's an issue or not.

I'm new to this and trying to help. I thought that's what you were supposed to do, there's a link in discussion to create an issue.
Chrome Version 92.0.4515.159 (Official Build) (64-bit)
Firefox 91.0.2 (64-bit)
Win 10 19043.1200

Same here - Firefox 91.0.2 (64-bit) macOS 11

Perhaps related issue? - no gradient

heya @lowwhistler - perhaps it's because you are using a background color on the box? Try it without bg-body and they look correct. https://codepen.io/coliff/pen/PojNPmK

@rafalkrupinski I can see the gradients in that screenshot. It's quite subtle on its own but noticeable when compared to example above without gradients.

Nice workaround but not practical for my use case. I can avoid upgrading until it's fixed

Nice workaround but not practical for my use case. I can avoid upgrading until it's fixed

What do you mean? There isn't a problem with the shadow utility classes. The examples on the site are using .bg-body which has a bug which will be fixed in the next update (I reported that issue before #34688) but there isn't a problem with the shadow classes themselves. You don't need to use .bg-body with them.

Indeed, as @coliff explained shadows are correctly rendered but .bg-body has a bug in the current release. Closing this since utilities do work and the background bug is already fixed.


engine framework design adjustment

handler register mechanism
new methods in OperatorContext:

pop_ready_tasks
num_ready_tasks
num_finished_tasks

removed methods in OperatorContext:

ready_tasks
finished_tasks

/approve
/lgtm

#4


Echo example

Make a full chat room where each incoming voice/camera is reflected out to all other connected clients.

And we have lift off!

Chat room is done, it's a good tool for more debugging and I have some issues to look into.


Add health check, functional tests, and CI

See the successful CI run: https://github.com/pinheadmz/warnet/actions/runs/6383114707/job/17323124908
This PR gets us CI testing with three big steps, detailed below:
Network health check RPCs
info reprints the warnet.__str__() output with this nice table:
--> warcli network info
Warnet:
        Temp Directory: /Users/matthewzipkin/.warnet/warnet/warnet
        Bitcoin Network: regtest
        Docker Network: warnet
        Subnet: <IP_ADDRESS>/8
        Graph: DiGraph with 12 nodes and 22 edges
Tanks:
        Index   Version                  Conf                     Netem                    IPv4
        0       25.0                                              None                     <IP_ADDRESS>
        1       25.0                                              None                     <IP_ADDRESS>
        2       25.0                                              None                     <IP_ADDRESS>
        3       25.0                                              None                     <IP_ADDRESS>
        4       25.0                                              None                     <IP_ADDRESS>
        5       25.0                                              None                     <IP_ADDRESS>
        6       25.0                                              None                     <IP_ADDRESS>
        7       25.0                                              None                     <IP_ADDRESS>
        8       25.0                                              None                     <IP_ADDRESS>
        9       25.0                                              None                     <IP_ADDRESS>
        10      25.0                                              None                     <IP_ADDRESS>
        11      vasild/bitcoin#relay_tx_                          None                     <IP_ADDRESS>

status returns a JSON object with the docker container status for each tank. This RPC can be polled until all tanks are "running". The CLI decodes the JSON response like this:
--> warcli network status
warnet_tank_000000: running
warnet_tank_000001: running
warnet_tank_000002: running
warnet_tank_000003: running
warnet_tank_000004: running
warnet_tank_000005: running
warnet_tank_000006: running
warnet_tank_000007: running
warnet_tank_000008: running
warnet_tank_000009: running
warnet_tank_000010: running
warnet_tank_000011: running

Functional tests
All the goodies are in test/. There are a few test files that can be run individually during development, example:
$ python test/scenarios_test.py

Each individual test creates a TestBase instance which runs a warnet server in a subprocess and can create a network with a unique name and temporary directory. The output of the warnet server is captured to a file in another temporary location and that file can be read from continuously during the test. This allows us to monitor the server even though its in the background. That's especially nice during long waiting periods like while docker-compose up is running. TestBase also attempts to clean up if the test fails, the warnet server crashes, user hits ctrl-C, etc.
There is also a data/ directory with a few example graphml files used in the tests. Hopefully writing new tests is self-explanatory based on the three examples I wrote so far.
CI
Pretty simple, a github action that installs dependencies and then runs the individual tests. For now each test is run as a command in the ci workflow itself ci.yml so if you add a new test you need to be sure it is executed from that file. In the future we can work in a "test runner" like Bitcoin Core that runs a list of test files.

Now running tests in parallel on ci: https://github.com/pinheadmz/warnet/actions/runs/6387282902/job/17335380750

e.g. you can filter the docker api to get results like:
 {'Id': '1c779aaac627ed3d331435c0124b0845dd41ec8bf43bcf11cb4f9c54ddc840ab',
  'Image': 'jvstein/bitcoin-prometheus-exporter',
  'Name': 'warnet_test_kl0lm1tn_prometheus_exporter_000002',
  'Status': 'running'},
 {'Id': '1e07c997d3b800a6df2e7874dbfe400434ff2e9c3291da825bc49339718fed5a',
  'Image': 'jvstein/bitcoin-prometheus-exporter',
  'Name': 'warnet_test_kl0lm1tn_prometheus_exporter_000000',
  'Status': 'running'},
 {'Id': '7a1fa45191b2b3adfdf0e81e5349f72fd0c1730f972d80847c5566b9c32d85da',
  'Image': 'warnet_test_kl0lm1tn_dnsseed',
  'Name': 'warnet_test_kl0lm1tn_dns-seed',
  'Status': 'running'},
 {'Id': '6edfd9bf0eac34806cd3659119363c93f9a34e9a18f6814e0ccfab20476749c7',
  'Image': 'jvstein/bitcoin-prometheus-exporter',
  'Name': 'warnet_test_kl0lm1tn_prometheus_exporter_000007',
  'Status': 'running'},
 {'Id': 'd4fd88e1c47a3163d818a35e13ef95dcd0eb56ec8a900420a197a1b21edfc286',
  'Image': 'jvstein/bitcoin-prometheus-exporter',
  'Name': 'warnet_test_kl0lm1tn_prometheus_exporter_000008',
  'Status': 'running'},
 {'Id': '1d0472cf353fdde6ca944287f4ebd412ed0e3a4bdcdacf2f57b4515d94ed3a8d',
  'Image': 'prom/node-exporter:latest',
  'Name': 'warnet_test_kl0lm1tn_node-exporter',
  'Status': 'running'},
 {'Id': '7f4e6c2feb2594460739de8671a360a2e742df7d9c77aa788e67b10773cdd243',
  'Image': 'jvstein/bitcoin-prometheus-exporter',
  'Name': 'warnet_test_kl0lm1tn_prometheus_exporter_000004',
  'Status': 'running'},
 {'Id': '12f5590fc72d66516326df08bfab5db651be65493391fa7a8922eb71e36037ec',
  'Image': 'jvstein/bitcoin-prometheus-exporter',
  'Name': 'warnet_test_kl0lm1tn_prometheus_exporter_000001',
  'Status': 'running'},
 {'Id': 'e691a722006ef7daff6e0622af085f8492c24328cff2fac2feed6092cf699588',
  'Image': 'warnet_test_kl0lm1tn_warnet_test_kl0lm1tn_tank_000000',
  'Name': 'warnet_test_kl0lm1tn_tank_000000',
  'Status': 'running'},
 {'Id': 'ac944b9f90e57931de356ee29c60f4536850bf65e9679b1c4dd2bab89f14759f',
  'Image': 'warnet_test_kl0lm1tn_warnet_test_kl0lm1tn_tank_000009',
  'Name': 'warnet_test_kl0lm1tn_tank_000009',
  'Status': 'running'}]

But I think what you have is pretty nice and suitable too


cname record worng.

The comments below were machine-translated
@genesisemmloh commented on Sun May 17 2020
shouldn't the registry of cname have pointed to cdndocdemo1.azureedge.com?
Why did they point it to contoso.azureedge.com?

Detalles del documento
⚠ No edite esta sección. Se requiere para la vinculación de problemas de docs.microsoft.com ➟ GitHub.

ID: b32fbbf3-178d-a0ef-7c3a-87df74a8eb16
Version Independent ID: 2475b34a-88e8-5b45-723d-ee0a62230b8a
Content: Tutorial: Adición de un dominio personalizado a un punto de conexión de Azure CDN
Content Source: articles/cdn/cdn-map-content-to-custom-domain.md
Service: azure-cdn
GitHub Login: @asudbring
Microsoft Alias: allensu

@srvbpigh commented on Sun May 17 2020
Hello, @genesisemmloh
Thank you for your feedback.
We are actively reviewing your comments and will get back to you soon.
Kind regards,
Microsoft DOCS International Team

Thank you for your detailed feedback.  We are looking into the issue, and we will respond when we have more information.

@genesisemmloh where in the example are you referring to?  contoso.azureedge.com is the DNS name of the CDN Endpoint.
If your CDN's DNS name is cdndocdemo1.azureedge.com, then that is what you should point it to.

on the assosiation of the custom Domain, the images shows endpoint name as cdndocdemo1.

@genesisemmloh where in the example are you referring to? contoso.azureedge.com is the DNS name of the CDN Endpoint.
If your CDN's DNS name is cdndocdemo1.azureedge.com, then that is what you should point it to.

hier.

@genesisemmloh Thanks for the clarification.
I have assigned the issue to the content author to evaluate and update as appropriate.

This article has recently been updated and these screenshots have been changed.
#please-close

This article has recently been updated and these screenshots have been changed.
#please-close


fix: made fixes regarding file creation permission denied

Ticket Link

Related Links

Description

I have made the fix and this should work locally
Steps to Reproduce / Test

Request

Response

Codecov Report

Merging #119 (c81e8a6) into master (7bf737c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #119   +/-   ##
=======================================
  Coverage   84.23%   84.23%
=======================================
  Files          28       28
  Lines        1104     1104
=======================================
  Hits          930      930
  Misses        123      123
  Partials       51       51

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Can't get any data from 10KTL3-X inverter.

What happened?
Tried using the stock firmware, however MQTT failed to initialise, so I had to compile the source myself with MQTT disabled.
However, even with this (and trying all three MODBUS versions) I could only get the output ReadData() NOT successful.
Flashed with same USB Cable I used to plug into the inverter, I know that it isn't faulty.
Serial and USB debugging are also disabled, as I thought that could be the issue.

Nodemcu32

Which Inverter are you using?

MOD 10KTL3-X

Log output
Opened serial web server on http://<IP_ADDRESS>:8080
Configuring WDT...
Setting up WiFiManager menu
WIFI connected...yeey :)
ShineWiFi-X (USB) found
Modbus: read Segment from 0x00 with len: 50 ...failed
ReadData() NOT successful
... (failure continues forever)

Please double check that your Nodemcu32 does use a supported usb2serial chip. See the readme for more details which chips are supported. The nodemcu32(s) I have mostly use CP21XX chips which are not supported.

Yes you are correct I have the CP2102 chip. A shame that it's not supported. Is it possible to look into adding support (I'm very happy to contribute this back to the original project if it works).


Feature request: shifting tagged lines to top of line list in tag order

Currently tagging works as intended will show a user who has pretagged lines which ones they tagged denoted with a star. When there are a lot of lines might take some sifting through would be nice if possible anyways to have said tagged lines re arranged to top of line list / first page for easier access and quicker viewing etc.

Bidding page shows preferred (tagged) lines in order of preference, followed by remaining available lines.  Optional sort order shows all.


wsl --export failed

Environment
Windows build number:Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19041.0 Microsoft Windows NT 10.0.19041.0

Distribution version: [Ubuntu Release:        20.04]
wsl2

Steps to reproduce
after run LxRunOffline move -n Ubuntu-20.04 -d F:\wsl\docker
i type wsl --export Ubuntu20.04 F:\wsl
return access Deni
Expected behavior
removed to other computer

I guess F:\wsl is a directory, but --export requires file name, so the correct command should be like this:
wsl --export Ubuntu-20.04 F:\wsl\abc.tar
Another possible reason is that you don't have permission to create F:\wsl file

I guess F:\wsl is a directory, but --export requires file name, so the correct command should be like this:
wsl --export Ubuntu-20.04 F:\wsl\abc.tar
Another possible reason is that you don't have permission to create F:\wsl file

yes! I forgot the suffix,Thanks for the trick!


Upgrade pypi-theme to 1.29

Forcing this to merge since it's just bumping the pypi-theme dependency.


FI-958: Add footer to validator app

FI-958: This PR adds a footer to the validator with links to this repo and to the issues tab. It also adds a version info modal.

FHIR Validation Service Version is empty

you need to run the validator service backend to get the validator service version
VALIDATOR_PORT=8080 ./gradlew run


GH-65: forbid start streaming on 'Detect object' switch

Video stream doesn't start on click on 'Detect object' switch
Closes: #65 #64

LGTM


the navbar is not responsive

you navbar is not responsive i want to add a hamburger icon for small screen
the un responsive navbar is making the other pages un responsive

please assign this issue to me @theashikagupta

i would like to work on this issue please assign me this issue

Assigned @AyushSharma72

hey @AyushSharma72  i have great experiance with these kind of problem. please assign it to me. I am start working on it.


Graph/table button doesn't resize nicely

For presentation/demos I get a better result by zooming in (⌘++) rather than using contrast mode.
However, when doing that the Graph/table buttons get a strange vertical alignment, with an odd surrounding border.

@2opremio did you mean to file this in the Scope project?

Crap, yes, sorry


Require user to add redis host to list of allowed listed hosts

This makes it required for users using the Redis v2 interface to add allowed_redis_hosts to their manifest specifying which hosts are allowed to be reached. This mirrors how key/value, llm, and sqlite all work.
Support is added in manifest v1 and v2 for the allowed_redis_hosts  key which defaults to the empty list. However, apps targeting the old Redis interface do not need to update their configs as only the new interface respects this configuration.
Next, we will move MySQL and PostgreSQL to do the same.
Update:
Introduce: allowed_outbound_hosts as a general way to control outbound networking. This is implemented for Redis for now, but will be introduced for MySQL, PostgreSQL, and http in future PRs.

It seems like ideally the Redis v1 interface would enforce allowed_redis_hosts if present (including disabling on allowed_redis_hosts = []), but I don't know how much extra pain that would be to implement.

I've updated this PR with the following:

If users set allowed_outbound_hosts in a manifest v1, the v1 redis interface will respect that - otherwise all hosts are allowed. V2 is deny by default.
outbound-networking has been introduced to allow for more general control than just host matching:

This mirrors the outbound http controls (and will likely replace it in the futute).
The allowed_outbound_hosts can contain url-like strings that contain a host and port (both required) and an optional scheme. The check determines whether the outgoing request has the same host and port and if the manifest included a scheme it also checks that that matches.

If the user passes a url to the implementation without scheme, the implementation will try to parse the url with the scheme that makes sense given the context. For example, if a user passes "localhost:6379" to the redis implementation, the implementation will assume that the scheme is "redis://".

Further to that timing question, are MySQL and Postgres also in scope for 2.0?

@itowlson yes - once this is merged I will do the other two. I wanted to make sure that the approach is agreed upon before doing the others.


Add a license

I'd like to package this for another distro, but need to know what the license terms are before I can do that

I don't plan adding any additional restrictions, the license is intersection of libheic's and imlib2's licences, so it's probably effectively LGPL.
Without linking to libheif it looks like 3-clause BSD.

so it's probably effectively LGPL.

I can run with that. You might want to add a license file to avoid having to repeat this conversation with other packagers.

Can we re-open this? I'm trying to package this here, at the very least having a dedicated LICENSE file would make packaging so much easier.

Can we re-open this? I'm trying to package this here, at the very least having a dedicated LICENSE file would make packaging so much easier.

Which licence file should it contain? A copy of libheic's or BSD's?

Which licence file should it contain? A copy of libheic's or BSD's?

A copy of the BSD 3 Clause license

A copy of the BSD 3 Clause license

Done. Shall I create a tag?

Done. Shall I create a tag?

Yes

Yes

Done: https://github.com/vi/imlib2-heic/releases/tag/v0.1.1

Done: https://github.com/vi/imlib2-heic/releases/tag/v0.1.1


Consider switching away from taskw / Have own fork of taskw

We've been using taskw for communicating with the Taskwarrior storage until now. However, there are bugs creeping in the taskw project and the maintainers of it are not very active fixing them or merging my PRs with the fixes e.g., see https://github.com/ralphbean/taskw/pull/160.
We should consider switching to tasklib instead, developed and maintained by the core taskwarrior team - http://tasklib.readthedocs.io/en/latest/

tasklib doesn't seem to be in active development anymore either - maybe we should fork taskw and push our own versions of the tool to PyPI.

We've now hard-forked and currently publish a new taskw-ng TW python bindings package - https://pypi.org/project/taskw-ng/. It's based on the original taskw project.


[misc][core] lazy import outlines

temp fix for https://github.com/vllm-project/vllm/issues/4193
for users who don't use guided decoding but use slurm cluster, this makes their lives eaiser.

Nice this is good fix for now! But the users will still have problem with the actually usage :(

yep this is a temp fix, because I heard many people are suffering from this problem but they don't use outlines at all.
for people who really want guided decoding and suffer from the problem, they can use --guided-decoding-backend=lm-format-enforcer :)

I'm waiting for users' confirmation to see if it works.

Tested on slurm and this pr works well for me

when will this be released? I'm unable to build from source on my HPC server

@alex2awesome you don't need to wait for the release, we have per-commit wheel released. see
https://docs.vllm.ai/en/latest/getting_started/installation.html

That's good to know!! unfortunately, after installing the nightly build, I'm still getting this error:
  File "/project/jonmay_231/spangher/Projects/conditional-information-retrieval/source_summaries/data_vllm_70b.py", line 19, in <module>
    from vllm import LLM,  SamplingParams
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/vllm/__init__.py", line 6, in <module>
    from vllm.entrypoints.llm import LLM
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/vllm/entrypoints/llm.py", line 13, in <module>
    from vllm.model_executor.guided_decoding import (
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/vllm/model_executor/guided_decoding/__init__.py", line 8, in <module>
    from vllm.model_executor.guided_decoding.outlines_decoding import (
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/vllm/model_executor/guided_decoding/outlines_decoding.py", line 15, in <module>
    from vllm.model_executor.guided_decoding.outlines_logits_processors import (
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/vllm/model_executor/guided_decoding/outlines_logits_processors.py", line 25, in <module>
    from outlines import grammars
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/outlines/__init__.py", line 2, in <module>
    import outlines.generate
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/outlines/generate/__init__.py", line 2, in <module>
    from .cfg import cfg
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/outlines/generate/cfg.py", line 3, in <module>
    from outlines.fsm.guide import CFGGuide
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/outlines/fsm/guide.py", line 109, in <module>
    def create_states_mapping(
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/outlines/caching.py", line 93, in decorator
    memory = get_cache()
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/outlines/caching.py", line 65, in get_cache
    memory["__version__"] = outlines_version
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/diskcache/core.py", line 823, in __setitem__
    self.set(key, value, retry=True)
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/diskcache/core.py", line 806, in set
    self._row_update(rowid, now, columns)
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/diskcache/core.py", line 828, in _row_update
    sql(
sqlite3.DatabaseError: database disk image is malformed```

File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/vllm/model_executor/guided_decoding/init.py", line 8, in
from vllm.model_executor.guided_decoding.outlines_decoding import (

your installation might be wrong. if you have the latest commit installed, line 8 should not be this one.
see https://github.com/vllm-project/vllm/blob/257afc37c5b3e4c6d491d105337387989b013aee/vllm/model_executor/guided_decoding/init.py#L8

Ahh thanks @youkaichao — dumb error on my part, I just copy/pasted the instructions in the docs. The right version to use for anyone coming here is:
pip install https://vllm-wheels.s3.us-west-2.amazonaws.com/nightly/vllm-${VLLM_VERSION}-cp38-abi3-manylinux1_x86_64.whl```

Hello, guys!!
I'm facing same problem as @alex2awesome, but I'm not being able to get what I can do here, because I'm running a golang app to start a docker container for vllm. So, I'm not sure how to run this pip install mentioned above, since my container drops as soon as it tries to run.
I have tried vllm 0.5.5 version, but no success.
Any suggestion?
The error message I'm getting is exactly the same as @alex2awesome posted few comments above.

Hello, guys!! I'm facing same problem as @alex2awesome, but I don't know what I can do here, because I'm running a golang app to start a docker container for vllm. So, I'm not sure how to run this pip install mentioned above, since my container drops as soon as it tries to run. I have tried vllm 0.5.5 version, but no success. Any suggestion? The error message I'm getting is exactly the same as @alex2awesome posted few comments above.
Something that might worth mention is: the problem only occurs if I run the app with my linux user... I log in with another user, everything works fine

As I understand it the fix is not yet in 0.5.5. You will have to install from source

Hi @youkaichao , has the fix been implemented with the OpenAI-compatible inference engine yet?
I've tested and am OK with loading the model in python, as in: https://docs.vllm.ai/en/latest/getting_started/quickstart.html
but when I try to launch an inference engine using:
python -m vllm.entrypoints.openai.api_server \
    --model NousResearch/Meta-Llama-3-70B-Instruct \
    --dtype float16 \
    --tensor-parallel-size $NUM_GPUS \
    --api-key token-abc123 \
    --enforce-eager &

I get the same errors:
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/vllm/model_executor/guided_decoding/outlines_decoding.py", line 15, in <module>
    from vllm.model_executor.guided_decoding.outlines_logits_processors import (
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/vllm/model_executor/guided_decoding/outlines_logits_processors.py", line 25, in <module>
    from outlines import grammars
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/outlines/__init__.py", line 2, in <module>
    import outlines.generate
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/outlines/generate/__init__.py", line 2, in <module>
    from .cfg import cfg
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/outlines/generate/cfg.py", line 3, in <module>
    from outlines.fsm.guide import CFGGuide
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/outlines/fsm/guide.py", line 109, in <module>
    def create_states_mapping(
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/outlines/caching.py", line 93, in decorator
    memory = get_cache()
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/outlines/caching.py", line 65, in get_cache
    memory["__version__"] = outlines_version
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/diskcache/core.py", line 823, in __setitem__
    self.set(key, value, retry=True)
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/diskcache/core.py", line 806, in set
    self._row_update(rowid, now, columns)
  File "/home1/spangher/miniconda3/envs/vllm-py310/lib/python3.10/site-packages/diskcache/core.py", line 828, in _row_update
    sql(
sqlite3.DatabaseError: database disk image is malformed```

@alex2awesome it should also work for the api server.
your stack trace is incomplete, and it is unclear if you use guided decoding or not.


Bug

Be clear, concise and precise in your description of the problem.
Open an issue with a descriptive title and a summary in grammatically correct,
complete sentences.
Use the template below when reporting bugs. Please, make sure that
you're running the latest stable RuboCop and that the problem you're reporting
hasn't been reported (and potentially fixed) already.
Before filing the ticket you should replace all text above the horizontal
rule with your own words.

Actual behavior
Describe here what actually happened.
Please use rubocop --debug when pasting rubocop output as it contains additional information.
Steps to reproduce the problem
This is extremely important! Providing us with a reliable way to reproduce
a problem will expedite its solution.
RuboCop version
Include the output of rubocop -V or bundle exec rubocop -V if using Bundler.
If you see extension cop versions (e.g. rubocop-performance, rubocop-rspec, and others)
output by rubocop -V, include them as well. Here's an example:
$ [bundle exec] rubocop -V
1.56.4 (using Parser <IP_ADDRESS>, rubocop-ast 1.29.0, running on ruby 3.2.2) [x86_64-linux]
  - rubocop-performance 1.18.0
  - rubocop-rspec 2.23.2

$ [bundle exec] rubocop -V
1.56.4 (using Parser <IP_ADDRESS>, rubocop-ast 1.29.0, running on ruby 3.2.2) [x86_64-linux]

rubocop-performance 1.18.0
rubocop-rspec 2.23.2


Convert TokenFunction use annotations for API documentation

User Story:
As a consumer of the report stream API, I want the token endpoints to be automatically kept in sync with the code
Description/Use Case
The endpoints in TokenFunction are automatically documented when the code is built
Risks/Impacts/Considerations
Dev Notes:
Should be able to refer to ApiKeysFunctions for example of how to add these annotations
Acceptance Criteria

[ ] all the functions in TokenFunction is documented via annotations

Hey team! Please add your planning poker estimate with Zenhub @arnejduranovic @jack-h-wang @JessicaWNava @JFU-NAVA-PBC @luis-pabon-tf @mkalish @thetaurean

This function will no longer exist with new microservice pattern. Closing.


Errors logged during runAll shutdown

Kafka didn't take kindly to being shutdown upon terminating with runAll:
[info] Stopping Kafka...
[error] i.n.u.c.D.rejectedExecution - Failed to submit a listener notification task. Event loop shut down?
java.util.concurrent.RejectedExecutionException: event executor terminated
	at io.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:800)
	at io.netty.util.concurrent.SingleThreadEventExecutor.offerTask(SingleThreadEventExecutor.java:345)
	at io.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:338)
	at io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:743)
	at io.netty.util.concurrent.DefaultPromise.safeExecute(DefaultPromise.java:767)
	at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:435)
	at io.netty.util.concurrent.DefaultPromise.setFailure(DefaultPromise.java:120)
	at io.netty.channel.DefaultChannelPromise.setFailure(DefaultChannelPromise.java:87)
	at io.netty.channel.AbstractChannelHandlerContext.safeExecute(AbstractChannelHandlerContext.java:1005)
	at io.netty.channel.AbstractChannelHandlerContext.close(AbstractChannelHandlerContext.java:614)
[error] i.n.u.c.D.rejectedExecution - Failed to submit a listener notification task. Event loop shut down?
java.util.concurrent.RejectedExecutionException: event executor terminated
	at io.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:800)
	at io.netty.util.concurrent.SingleThreadEventExecutor.offerTask(SingleThreadEventExecutor.java:345)
	at io.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:338)
	at io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:743)
	at io.netty.util.concurrent.DefaultPromise.safeExecute(DefaultPromise.java:767)
	at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:435)
	at io.netty.util.concurrent.DefaultPromise.setFailure(DefaultPromise.java:120)
	at io.netty.channel.DefaultChannelPromise.setFailure(DefaultChannelPromise.java:87)
	at io.netty.channel.AbstractChannelHandlerContext.safeExecute(AbstractChannelHandlerContext.java:1005)
	at io.netty.channel.AbstractChannelHandlerContext.close(AbstractChannelHandlerContext.java:614)
[error] i.n.u.c.D.rejectedExecution - Failed to submit a listener notification task. Event loop shut down?
java.util.concurrent.RejectedExecutionException: event executor terminated
	at io.netty.util.concurrent.SingleThreadEventExecutor.reject(SingleThreadEventExecutor.java:800)
	at io.netty.util.concurrent.SingleThreadEventExecutor.offerTask(SingleThreadEventExecutor.java:345)
	at io.netty.util.concurrent.SingleThreadEventExecutor.addTask(SingleThreadEventExecutor.java:338)
	at io.netty.util.concurrent.SingleThreadEventExecutor.execute(SingleThreadEventExecutor.java:743)
	at io.netty.util.concurrent.DefaultPromise.safeExecute(DefaultPromise.java:767)
	at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:435)
	at io.netty.util.concurrent.DefaultPromise.setFailure(DefaultPromise.java:120)
	at io.netty.channel.DefaultChannelPromise.setFailure(DefaultChannelPromise.java:87)
	at io.netty.channel.AbstractChannelHandlerContext.safeExecute(AbstractChannelHandlerContext.java:1005)
	at io.netty.channel.AbstractChannelHandlerContext.close(AbstractChannelHandlerContext.java:614)
[info] Kafka is stopped.

These messages aren't related to Kafka specifically... they just happen to be concurrently logged. I'll update the issue title accordingly.

To reproduce this, you need to create a chirp sometime before shutting down. Just starting runAll and immediately stopping won't do it.

This actually happens in the HelloWorld example as well.

When I enabled Kafka it no longer occurred (just other issues):
> runAll
[info] Starting Kafka
[info] Starting Cassandra
.SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
...............
[info] Cassandra server running at <IP_ADDRESS>:4000
[info] Service locator is running at http://localhost:8000
[info] Service gateway is running at http://localhost:9000
[warn] c.l.l.i.p.c.ServiceLocatorSessionProvider - Could not find Cassandra contact points, due to: ServiceLocator is not bound
[warn] c.l.l.i.p.c.ServiceLocatorSessionProvider - Could not find Cassandra contact points, due to: ServiceLocator is not bound
[warn] c.l.l.i.p.c.ServiceLocatorSessionProvider - Could not find Cassandra contact points, due to: ServiceLocator is not bound
[warn] a.p.c.j.CassandraJournal - Failed to connect to Cassandra and initialize. It will be retried on demand. Caused by: ServiceLocator is not bound
[warn] c.l.l.i.p.c.ServiceLocatorSessionProvider - Could not find Cassandra contact points, due to: ServiceLocator is not bound
[warn] c.l.l.i.p.c.ServiceLocatorSessionProvider - Could not find Cassandra contact points, due to: ServiceLocator is not bound
[warn] c.l.l.i.p.c.ServiceLocatorSessionProvider - Could not find Cassandra contact points, due to: ServiceLocator is not bound
[warn] a.p.c.j.CassandraJournal - Failed to connect to Cassandra and initialize. It will be retried on demand. Caused by: ServiceLocator is not bound
[info] Service activity-stream-impl listening for HTTP on 0:0:0:0:0:0:0:0:51855
[info] Service friend-impl listening for HTTP on 0:0:0:0:0:0:0:0:60399
[info] Service chirp-impl listening for HTTP on 0:0:0:0:0:0:0:0:54485
[info] Service front-end listening for HTTP on 0:0:0:0:0:0:0:0:57143
[info] Service load-test-impl listening for HTTP on 0:0:0:0:0:0:0:0:51796
[info] (Services started, press enter to stop and go back to the console...)

[info] Stopping services
[error] a.a.OneForOneStrategy - Processor actor [Actor[akka://chirp-impl-application/user/StreamSupervisor-1/flow-9-1-unknown-operation#-300295776]] terminated abruptly
akka.stream.AbruptTerminationException: Processor actor [Actor[akka://chirp-impl-application/user/StreamSupervisor-1/flow-9-1-unknown-operation#-300295776]] terminated abruptly
[error] a.a.OneForOneStrategy - Processor actor [Actor[akka://chirp-impl-application/user/StreamSupervisor-1/flow-11-1-unknown-operation#1270932970]] terminated abruptly
akka.stream.AbruptTerminationException: Processor actor [Actor[akka://chirp-impl-application/user/StreamSupervisor-1/flow-11-1-unknown-operation#1270932970]] terminated abruptly
[error] a.a.OneForOneStrategy - Processor actor [Actor[akka://chirp-impl-application/user/StreamSupervisor-1/flow-10-1-unknown-operation#1911324024]] terminated abruptly
akka.stream.AbruptTerminationException: Processor actor [Actor[akka://chirp-impl-application/user/StreamSupervisor-1/flow-10-1-unknown-operation#1911324024]] terminated abruptly
[error] a.a.OneForOneStrategy - Processor actor [Actor[akka://friend-impl-application/user/StreamSupervisor-1/flow-7-1-unknown-operation#-117257762]] terminated abruptly
akka.stream.AbruptTerminationException: Processor actor [Actor[akka://friend-impl-application/user/StreamSupervisor-1/flow-7-1-unknown-operation#-117257762]] terminated abruptly

[info] All services are stopped
[info] Stopping Kafka...
[info] Stopping Cassandra...
[info] Stopping service locator
[info] Kafka is stopped.
[info] Cassandra is stopped.
[info] All servers stopped
[success] Total time: 265 s, completed Aug 6, 2017 12:52:13 PM
>```

@jewelsjacobs it's most likely coincidental that enabling Kafka made the errors go away. This app doesn't make use of Kafka at all. The "errors" noted originally in this issue happen because of timing inconsistencies during shutdown, but they are harmless.
Were you having problems hot reloading before enabling Kafka? If you can share the details in Gitter or on the mailing list, we can help figure out what the problem was.
The errors you're seeing now are also harmless. The nature of distributed microservices is that partial failure is "normal" and Lagom is designed to be able to recover. When different components of the system are starting asynchronously, and two of them need to communicate, one won't be able to know whether the other is available without trying to talk to it. If that fails, it handles the failure and tries again later. We don't want to suppress the errors entirely (after all, maybe it will just keep failing forever) so they are logged, but it's admittedly alarming to see these errors without explanation when just getting started. We will try to make these more comprehensible in the future.

This was resolved by updating to Lagom 1.4.


Add linters

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.011%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
162

Relevant Lines:
178

💛  - Coveralls


Question: Support for CoreML / Vision?

I was hacking together a demo where I had to do portrait segmentation (Zoom like background removal) without chroma key.
I decided to use Deeplabv3 and found this project: https://github.com/jsharp83/MetalCamera which has all the parts properly setup. With a few minor changes I was able to macOS compatible as well.
This would make a great addition to PixelKit.
My use case is: remove the background from realtime video and merge it with a custom image/video.
Relevant File:
https://github.com/jsharp83/MetalCamera/blob/master/MetalCamera/Classes/CoreML/CoreMLClassifierHandler.swift

Hi, Deeplabv3 is nice, tho it’s hard to get it going in realtime, I was trying it out here: DeepLabPIX. SaliencyPIX is faster tho low res. A blur, a threshold, a channel mix and a blend might do the trick.


Can't resolve css background images

Is anyone experiencing Module build failure? I am getting the following message:
[start:webpack ] Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
[start:webpack ] ModuleBuildError: Module build failed (from ./node_modules/css-loader/dist/cjs.js):
[start:webpack ] Error: Can't resolve '/assets/static/venus-velocity-thumbnail.jpg' in '/Users/daniellee/eleventy-webpack-starter-project-20210412-wedding/src/assets/styles'
Any solutions?

Did you find a solution for this?