WIP: Add pickup conversations

Initial UI work on pickup conversations.
TODO:

[x] actually fetch proper data about pickup
[x] work out where to store state of whether to show it or not
[x] add links to pickups to open side detail/conversation
[x] work out how mobile view should work
[x] fix the negative margin issue at the bottom (because of the carrot logo poking up, it makes it funny...)
[x] don't always jump to the bottom after update (e.g. reaction update should not jump to bottom, and could be annoying if you are just flicking through old messages)
[x] work out pagination/infinate scroll stuff (looks like quasar infinite scroll is only designed to work downwards...)
[ ] maybe get more info/actions in the top bar bit, it looks a bit small to me right now
[x] work out how to handle marking messages as read
[ ] put text into translation system
[x] autofocus conversation input on opening detail sidebar
[ ] consider whether an overall conversation/notification thing is needed to avoid missing messages (not in this PR)
[x] handle case where user is no longer signed up to pickup/conversation and so it should go away
[x] make route redirect to group page on desktop with the side panel open

UI looks like this for now:

Hmm, for some reason the netlify preview doesn't show anything interesting yet...

Looks great already - but lots of thoughts necessary for this! I'm happy to give some input in the next days, what do you think are the showstoppers before it can get merged to master?

Would be worth getting https://github.com/yunity/karrot-backend/pull/544 merged first - it's much simpler, and allows us to use dev backend and/or netlify preview.
I think the main usability showstopper could be missed messages - as we don't have a conversation notification overview page, new messages won't be very visible (they do get sent by email and push notification, but the desktop view wouldn't make it very apparant that there is a new message).
Otherwise, mostly details. Pagination is a bit annoying and looks like I'll need to reimplement a bunch of the quasar infinite scroll thing :/ ... also read messages, would like it a bit more automatic than the wall, but didn't work anything out yet.

I added automatic read-marking - basically, if you are not away, then we mark the most recent received as read, as they arrive. If you are away, we don't.

Oh, infinate scroll wasn't so tricky to implement, given we already have the nice cursor/status stuff implemented.

The netlify preview is working now :) - well, apart from that netlify doesn't proxy websockets yet...

Cool! Tried it out, works :)
About missed messages: not a problem right now, can add a "to catch up" page in future. Maybe as banner on the group wall as "you have new messages". Can also change the favicon (add a red dot) and add an (!) at the beginning of the browser titlebar. We can also get browser push notifications. Maybe I should write this into some issue instead of here ;)
About email notifications: would be cool if there was a hyperlink that jumps directly to the pickup conversation view. Maybe with a route parameter?

Ok, I added a mobile page for pickup conversations (well pickup detail I termed it - with a vague idea that it can be a more general detail page for different things, with or without conversations as part of them).
I think I'll try and make it so that the pickup detail link will redirect to the group page with the pickup conversation open, or something like that. I wanted to avoid having to store the side detail state in the url too. Which is maybe not ideal, but it's quite complicated to support a link parameter (as it can be on any page).

Thanks for feedback! I did the following:

made the whole pickup clickable (I left the "Open Chat" link too as I don't think people will know the click the pickups to start with, and a button looked a bit odd...) - oh, I forgot to add "Open Chat" to i18n
made the pickup detail route nested in the group/store (simplifies the action as we have the group/store ids)
changed the toolbar header thing as suggested
added breadcrumbs for group/store

The backend doesn't send out notification emails for pickup conversation messages, does it? It raises this exception: https://sentry.io/foodsaving-worldwide/backend/issues/582451427

Ah, good point. Will do a backend fix for that. At least the error message was nice and clear :)

Ready to merge?

Still needs something to toggle pickup chat notification emails.

Looks good, does it wrap nicely if there are lots of people in there? (which would be quite rare for a pickup...)

Seems to work nicely without fiddling. Not super space efficient, but ok for the purpose.

I'm done for today, seems to be overly ready for dev.karrot.world :)
@nicksellen merge as you like!


First content

This change is

Review status: 0 of 17 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

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

Comments from Reviewable


Passing traceID into DD logs.

Is your feature request related to a problem? Please describe.
It's a feature request, not a problem.
Describe the solution you'd like
We use datadog APM logs on our web frontend application and it's awesome that we can track the whole lifecycle of an error from frontend request to backend errors.
We'd love to be able to do that on our react native side as well.
Describe alternatives you've considered
I've looked through the logs and found nothing that relates to traceId.
Additional context
Add any other context or screenshots about the feature request here.

Hi @peteratdivvy, thanks for reaching out!
You can actually achieve this with automated resource tracking!
You need to specify two fields in your configuration:
// Optional: Sample tracing integrations for network calls between your app and your backend (in this example, 80% of calls to your instrumented backend are linked from the RUM view to the APM view. Default is 20%)
// You need to specify the hosts of your backends to enable tracing with these backends
config.resourceTracingSamplingRate = 80;
config.firstPartyHosts = ['example.com']; // matches 'example.com' and subdomains like 'api.example.com'

And make sure trackResources (5th argument in the DdSdkReactNativeConfiguration constructor) is set to true.
This will have the same effect as explained for browser here: https://docs.datadoghq.com/real_user_monitoring/connect_rum_and_traces/?tab=browserrum#setup-rum
Your firstPartyHosts for React Native should include the same list as allowedTracingUrls does for web, with the addition of the host of your app if you use it for your API as well (we cannot infer it in mobile SDKs).
Let me know if this helps, or if you are looking for something else :)

Engaging in some necromancy here, what about the case where I want logs emitted from my react native app to get attached to the logs view of the resource request trace? As far as I can tell the logs coming out of using DdLogs.* don't get a trace ID (or at least its not the same one as the resource I have) so I can't see logs from the mobile app before and after resource requests are being made within the trace page for that XHR request or whatever. Am I thinking about that wrong?


Disabled nodes should not have href attribute

Disabled nodes should not have any href attribute so that they will not get the cursor pointer.
I am aware of this issue #1655, and in html5, an href attribute is no longer required for an <a> to be valid, without one, it will not be styled as a link (no cursor:pointer)
According to the W3 specs:

If the a element has an href attribute, then it represents a hyperlink (a hypertext anchor) labeled by its contents.
If the a element has no href attribute, then the element represents a placeholder for where a link might otherwise have been placed, if it had been relevant, consisting of just the element’s contents.

I am currently overriding the cursor style in my css, but I wish i didn't have to. Can you make it so that disabled nodes have no href? Alternatively, they could just be created as a span or a div element, but they should not appear clickable.

Can there not be a separate option then to just remove the href?

I tend to avoid adding new options unless frequently requested - sorry. Not to mention this version still supports IE8 which I would rather not test.
You can however remove the attribute by using a mini-plugin of your own:
(function ($, undefined) {
	"use strict";
	$.jstree.plugins.nohref = function (options, parent) {
		this.redraw_node = function (obj, deep, callback, force_draw) {
			var el = parent.redraw_node.apply(this, arguments),
                              nd = el.querySelector('.jstree-disabled'); // replace this with traversal if you need to support older browsers
			if (nd.length) { nd.removeAttribute('href'); }
			return el;
		};
	}
}));
// don't forget to add "nohref" to your plugins config array


Documentation project has bad overload code

Expected behavior and actual behavior.
isCellVisible appears twice in the docs with exact same documentation.   The overload code is ignored.
Steps to reproduce the problem.
Make an overload entry.  E.g.:
    /**
     * Checks if a cell is currently visible.
     * @memberof canvasDatagrid
     * @name isCellVisible
     * @overload
     * @method
     * @returns {boolean} when true, the cell is visible, when false the cell is not currently drawn.
     * @param {number} columnIndex The column index of the cell to check.
     * @param {number} rowIndex The row index of the cell to check.
     */
    /**
     * Checks if a cell is currently visible.
     * @memberof canvasDatagrid
     * @name isCellVisible
     * @method
     * @returns {boolean} when true, the cell is visible, when false the cell is not currently drawn.
     * @param {cell} cell The cell to check for.  Alternatively you can pass an object { x: <x-pixel-value>, y: <y-pixel-value> }.
     */

Removing the second block of comment fixes this issue. I can have a PR with the change.

Thanks!!!

Thanks again for the PR @amjha!


New rule request: Shadows name from outer scope

What about catching this code smell:
def func(x: list[int]) -> list[int]:
    return sorted(x, key=lambda x: x)

(PyCharm warns "Shadows name 'x' from outer scope")
BTW, we're loving Ruff!  Amazing project.

pylint has a rule for that (#970)

Which rule exactly is that in pylint?  I can't seem to find one.

oh sorry, it's redefined-outer-name

Closing this as duplicate since it's included in both of these issues: #970 and #3040
Thanks!

Now we can't subscribe to an issue to know when it's "fixed" since those issues are wrappers for multiple rules.


NIRCam oss8.2

This PR is supposed to close JWSTSIAF-118, JWSTSIAF-77.
We changed the subarray locations and corresponding reference positions of all NIRCam module A coronographic apertures, based on CV3 data.
The changes are all in the nircam siaf aperture definition file. We have used the generate_nircam to verify that the apertures appear in the expected location in the V2,V3 plane.
@JAStansberry

Sorry...I was confused. I had already opened a PR for this....closing this one!


[eas-cli] make flags for eas build:list command more aligned with flags for rest of the commands

Why
We use --this-convention to name our flags in the rest of the EAS CLI, meanwhile eas build:list has been using flags with --thisConvention.
Let's unify it.
How
Unify flag naming convention for eas build:list. Add -p and -e aliases for --platform and --profile flags as we do for eas build.
This is not a breaking change because we still keep the aliases around.
Test Plan
test manually, tests

/changelog-entry chore Make flags for eas build:list command more aligned with flags for rest of the commands


state-surgery: use latest eoa code

Description
Quick fix for the regenesis script so that it uses the latest EOA code

Wipe the EOA storage

Need to maintain the storage slots for OVM_ETH


fixed incorrect prop

Codecov Report

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

@@           Coverage Diff           @@
##           master     #252   +/-   ##
=======================================
  Coverage   59.43%   59.43%
=======================================
  Files           4        4
  Lines         673      673
=======================================
  Hits          400      400
  Misses        215      215
  Partials       58       58

Continue to review full report at Codecov.

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


Small binary size optimization

This is a small PR that reduces the size of stripped release binaries by about ~11%. I haven't done any perf tests (I'll let the CI system do that for me), though eliminating more code should only improve performance (one would hope).
I heard about this from optimization from the min-sized-rust repository.
Some stats:

Branch
Size
Size (stripped)

main (4cc3cdba)
25234904 (25M)
15267032 (15M)

This PR
22502240 (22M)
13681880 (14M)

Nice!


Sidecar Containers

Plese add here also that you must give the same name in the "volumeMounts name" section of both the sidecar and the main container for the automatic resource sharing to work. then finally we put the name also in the volumes section to mount it in the pod.

related page: https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/

It is one of the use case of sidecar container. So it is not required to mention specifically.

/retitle Add guidance on volumeMounts naming for automatic resource sharing in "Sidecar Containers" documentation


CFamilyLexer: support unicode identifiers

Fixes #998.

I also wanted to add this change to the CHANGES file, but wasn't sure if I should touch it. For future PRs, is it ok to do so?

Sorry, missed that completely. That's removing _ from the expression, is _ contained in \w? Otherwise this seems fine to be, just surprised it's [\w$] and not [\w_$].


docker: support url in addition to registry-url/image

Mirroring is currently almost impossible as it requires the mirrored image
to have the exact same image name as the original. That is, I cannot mirror
registry.hub.docker.com/buildstream/buildstream to
myregistry.com/myproject/buildstream/buildstream

Looks good to me. I'm a bit worried if it's legal to have registry which is mounted deeper in URL (IOW first path segment is not v2)

Yeah, I don't see that when reading the spec. But the issue that led to this implementation seems to imply otherwise.

Does this silently ignore image and registry-url if url is present?
It raises a error if nether are present. but should it not also raise a error if both are?
The condition of both image and url does not cause a error as such but it does cause unexpected behaviour. usually if you provide a key that is not used then bst causes a error (node.validate_keys) so i think the extra error would follow the existing patten?

Does this silently ignore image and registry-url if url is present?
It raises a error if nether are present. but should it not also raise a error if both are?

Seems you're right. Somehow I thought the current condition would handle it.

The condition of both image and url does not cause a error as such but it does cause unexpected behaviour. usually if you provide a key that is not used then bst causes a error (node.validate_keys) so i think the extra error would follow the existing patten?

I agree.

The new version looks good to me!
I don't have permission to approve but i would if i could.


Will this module support CSV file?

This is an awesome module!
Could you put the support for CSV file on the roadmap?
Many thanks.

Yes will check this.

IOS is supported.


README: Propose GTx CS1301 as an alternate introduction course

I propose using Georgia Tech's CS1301 (Computing In Python) course as an alternate introduction course, either in lieu of MITx 6.00.1x, or sequenced before 6.00.1x.
Georgia Tech's CS1301x course is an adaptation of a 16-week on-campus course which first became available on EdX in July 2018, and is offered as a four-part sequence leading to an optional Professional Certificate. Completing this course provides an equivalent background to MIT's 6.00.1x course, but provides more instruction and extensive practice in Python coding, with over 300 short coding problems to help build confidence and muscle memory in a short period of time.
This course also provides access to a free "adaptive textbook" which tests one's understanding of the material. A non-adaptive PDF copy is made available for offline reading.
Having taken both courses, in my opinion MITx 6.00.1x provides an excellent introduction to computer science concepts but expects the user to pick up Python more or less on his own. GTx CS1301 serves as a gentler introduction, teaching the same concepts but also taking time to teach Python along the way. This may be a more attractive option for true beginners, many of which find 6.00.1x to be too much all at once.

Thanks for the suggestion!
I am not sure this is the right approach for our introduction course, for several reasons:

It is very long for an introductory course
Our introductory course should be more like a survey of many CS topics; this seems more like an introduction to programming in Python
We already have a course sequence for teaching introductory programming: How to Code
In parts 3 and 4, this course gets into objects and classes, which are way too complicated for introductory programming

At least one of the above criticisms is also relevant to MIT 6.00.1. I'm interested in looking at Stanford CS101 as an introductory course but I didn't want to suggest it until I've had a chance to try it out.

Thanks for the consideration! I know that trying to find that one perfect 101-level course is difficult, with few good solutions. My solution has been: take several :)
This particular course may or may not fit the desired objectives of OSSU, and that's not for me to decide. I just know it fit my personal ones, and as it's a newer course I've been mentioning it where and when I can.
In partial response to your comments:

This course seems to suffer from inflated estimates of effort in ways that many MOOCs do and specifically that 6.00.1 doesn't. I devoted 10 hours of effort to the entire Part 1, and 20 hours of effort to the entire Part 2. I got through the entire course in about three weeks. As it's a self-paced course, I don't know how to separate my experience from the general one; here I've deferred to the estimates on EdX, but it's my belief that they're significantly, if not grossly, inflated.

The CS1301 course teaches CS concepts in a language-agnostic fashion first, then supplements with step-by-step implementations in Python. They also explain how code syntax might differ between different languages. The course's designers made it such that they could swap out any language implementation without impacting the flow of the course, and already plan to offer it in Java in the future. (I really like CS50 as a survey of CS topics, but the homework is monolithic and I needed something I could do in small bites.)

How To Code -- noted, and I'll be looking out for that in the curriculum. That said, I specifically appreciate the emphasis that CS1301 placed on coding training, early on -- many 101 courses have you write 4 or 5 programs, but at the end there's no sense that "I'm a programmer" or "I've done some programming", just "I wrote a few programming assignments". You get little or no comfort with the language. At the end of CS1301, you won't be great, you won't know all the features of Python, but you'll have developed muscle memory and you'll be able to go immediately apply your skills to interesting problems. In my opinion, a quick win like this is huge for retaining interest in the program. It certainly helped me.

Objects -- noted.

It is a big course, but it's very modular, and the bite-size nature of both the lessons and the programming practice make it approachable.
That's about all I have. Thanks again for your consideration.

@bradleygrant thanks for the feedback! It does sound quite nice.
Before I would put this in our introduction, I would want to get feedback both from you after you take How to Code and from others who have gone through this course and all the others in Core Programming. I think for right now the best place for this would be under extras/courses.md. If you made that change to this PR I would be happy to merge it.

Thanks, I will do exactly that. Closing this PR.


Updated Nobel prizes demo to v0.26

Pull Request
What does this PR do?
Fixes #<issue_number>

PR checklist
Please check if your PR fulfills the following requirements:

[ ] Does this PR fix an existing issue?
[ ] Have you read the contributing guidelines?
[ ] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

All done, updated the MeiliSearch naming as well


Add integration with Groove

Link to service: https://www.groovehq.com/
Is there a free account option?: No. Only a 15-day free trial
Describe the solution you'd like
Being able to start a timer when working on a support ticket.

Additional context

This integration would be very interesting for us! +1
Thanks

Do you think you will work on this integration one day or not ? Just to know if we need to change our tracking time system. Just give me an update please. It's important for us and when I see the impressive number of open issues, I'm a bit worried. Thanks

Hi,
Right now there are no short-term plans to include the integration for Groove. However, there is a chance this changes in the future. We can't make any promises, though.

Thanks for the update.
When I see the number of issues/request here and the little amount of closed, I'm more and more worried to be honest.
I see some issues or integration requests waiting here since 6 years !!!


Runtime Delay Problem

When I run program uses this package, a delay occurs.
I haven't found why this problem causes yet.

Same problem occurs this program.
Does it occurs from oauth.client...?
import 'dart:io';

import 'package:oauth/client.dart' as oauth;
import 'package:http/http.dart' as http;

void main(){
	var enVars = Platform.environment;
	oauth.Tokens tokens = new oauth.Tokens(
			consumerId: enVars['CONSUMER_KEY'],
			consumerKey:  enVars['CONSUMER_SECRET'],
			userId: enVars['ACCESS_TOKEN'],
			userKey: enVars['ACCESS_TOKEN_SECRET']);
	var oauthClient = new oauth.Client(tokens);
	oauthClient.get("https://api.twitter.com/1.1/statuses/user_timeline.json").then((response){
		print(response.body);
	});
	http.get("http://sh4869.net").then((response){
		print(response.body);
	});
}

I found that It occurs from http.ioClient.


VectorImage type declaration errors

Stack:

OL v10.2.1
Typescript v5.3.3

After the update from OL 8.2 to 10.2.1, I get the error "Type 'VectorSource' is missing the following properties from type 'Feature': id_, geometryName_, style_, styleFunction_, and 13 more.ts(2344)" for a VectorImageLayer.
In my opinion I have the same effects like in the issue #15897

In which context do you get that error? Can you share the code that triggers it?

Thanks for the details, will be fixed with #16348.


📝 Add zh blog for v0.8.0

Signed-off-by: Administrator<EMAIL_ADDRESS>

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Administrator seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


epic: site 4.0.0 wave 1

I have read the CLA Document and I hereby sign the CLA

recheck cla

recheck cla

Guys, you are awesome ❤
But just in case the current version of the article in Russian most likely is temporary.
I'm planning to convert it to a batch of articles for all major updates that we are going present with the 4th release

:tada: This PR is included in version 4.0.0-beta.8 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Recent update causes home page to not work

@space-elephant The recent update you made caused everything to break. Nothing works now, the redirection, the converter on the home page, none of it.

https://gobo.cf/#p827
https://gobo.cf/#e827
https://gobo.cf/#uspace_elephant
https://gobo.cf/#s74
https://gobo.cf/#d98f
Also, there should be some way to shorten posts (https://scratch.mit.edu/discuss/post/<id>/)

fixed.


Added "ruby" cookbook for maintaining binary ruby distribution

Fixes #166

I just looked at the code quickly, overall it looks good. Did not try to run it though. Also I'm thinkin about the cookbook name. Maybe we should name it: intercity-ruby that way it wont collide with other cookbooks in the supermarket. @berkes What do you think about prefixing our cookbooks with intercity-* for above reasons?


[CI/Build] Support setting cuda extra archs(FATBIN) according to env variable

We want to build a vllm wheel package which can be used in many CUDA devices.
Previously, if we build the package in a A10 device, we cannot run it in a H20 device. There are errors like no kernel image is available for execution on the device. Therefore, we need to build difference wheels for difference CUDA devices, which is not convenient.

This PR changed the CMake file, and now we can add more CUDA archs to the wheel building command through env variables
For example, we run VLLM_CUDA_EXTRA_ARCH="89;90" python setup.py bdist_wheel, the cmake output is here:

Finally, the output wheel can run on A10, L40S, H20 GPUs.
Since this switch is controlled by env variable, it will not affect the CI building time.
BEFORE SUBMITTING, PLEASE READ THE CHECKLIST BELOW AND FILL IN THE DESCRIPTION ABOVE

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Adding or changing kernels
Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.

Make sure custom ops are registered following PyTorch guidelines: Custom C++ and CUDA Operators and The Custom Operators Manual
Custom operations that return Tensors require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.
Use torch.libary.opcheck() to test the function registration and meta-function for any registered ops.  See tests/kernels for examples.
When changing the C++ signature of an existing op, the schema must be updated to reflect the changes.
If a new custom type is needed, see the following document: Custom Class Support in PT2.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

You can set the environment variable TORCH_CUDA_ARCH_LIST to build for specific arches. For reference, you can see it being set in the Dockerfile here: https://github.com/vllm-project/vllm/blob/16b24e7dcd8da5f2ac50f149daa77288fa8c14d7/Dockerfile#L57-L58


Windows 10: cant importprivkey.KMD {"error":"couldnt import"}, abort session

I am an experienced coin user (linux), testing Windows 10 now. I have a passphrase and coins on different currencies on it. i can perfectly use it in electrum mode, exchange e.g. KMD and DASH. but it does not work  in native mode. here is the problem:
When i start BarterDEX, i can type in my passphrase and click "Log in". But then i only see the grey screen saying "Starting BarterDEX. Please wait...", forever. This is only the case when KMD is running - otherwise i can get into the dashboard and start electrum mode. So here is the console output (i shortened private keys)
...
 LP_mypubsock.-1 pullsock.-1 RPC_port.7783 mypullport.7793 mypubport.7803 pushaddr.´┐¢
userpass.(1d8....c6f8cd81f)
Start stats_rpcloop.7783
>>>>>>>>>> DEX stats <IP_ADDRESS>:7783 bind sock.1468 DEX stats API enabled at unixtime.1517615150 <<<<<<<<<
unexpected.0 tradestatus aliceid.14738278218396925952 requestid.2243294678 quoteid.3153425791
unexpected.1 tradestatus aliceid.14640991375129706497 requestid.1062482564 quoteid.441005032
unexpected.2 tradestatus aliceid.4801969722723663873 requestid.1362214882 quoteid.663890330
max rpc threads spawned and alive 0 <- 1
got.() 0 remains.1573375 of total.0
got.() 0 remains.1573375 of total.0
t0 estimated rate.(BTC) (0.00165152) -> 0.00000242 0.00000000
connected to push.(tcp://<IP_ADDRESS>:7793) pushsock.10 valid.1  | connected to sub.(tcp://<IP_ADDRESS>:7803) subsock.11 valid.1 numactive.1
2765<PHONE_NUMBER><PHONE_NUMBER>)     reserved id.2548777508409507841    KMD/REVS    1.00213532 ->   0.28466126 ( 0.28405471) | RT.0 0 n0
start remote port
Start stats_rpcloop.7782
ERROR.({"method":"enable","coin":""})
ERROR.({"method":"enable","coin":""})
ERROR.({"method":"enable","coin":""})
ERROR.({"method":"enable","coin":""})
>>>>>>>>>> DEX stats <IP_ADDRESS>:7782 bind sock.1588 DEX stats API enabled at unixtime.1517615165 <<<<<<<<<
ERROR.({"method":"enable","coin":""})
ERROR.({"method":"enable","coin":""})
ERROR.({"method":"enable","coin":""})
ERROR.({"method":"enable","coin":""})
ERROR.({"method":"enable","coin":""})
ERROR.({"method":"enable","coin":""})
ERROR.({"method":"enable","coin":""})
ERROR.({"method":"enable","coin":""})
ERROR.({"method":"enable","coin":""})
2766 (245799174<PHONE_NUMBER>)      request id.16128253018001506305   KMD/SUPERNET  14.95464252 ->   0.41000999 ( 0.02741690) | RT.0 0 n0
2767<PHONE_NUMBER><PHONE_NUMBER>)     reserved id.11363962026593812481 PIZZA/BEER  1387.78968752 ->   0.13884280 ( 0.00010005) | RT.0 0 n0
2787<PHONE_NUMBER><PHONE_NUMBER>)      connect id.2548777508409507841    KMD/REVS    1.00213532 ->   0.28466126 ( 0.28405471) | RT.0 0 n0
2794 (395188783<PHONE_NUMBER>)      connect id.5914837145683558400  CHIPS/KMD    39.20622149 ->   2.50156648 ( 0.06380534) | RT.0 0 n0
connected to push.(tcp://<IP_ADDRESS>:7793) pushsock.12 valid.1  | connected to sub.(tcp://<IP_ADDRESS>:7803) subsock.13 valid.1 numactive.3
2813<PHONE_NUMBER><PHONE_NUMBER>)     reserved id.9993247826092425222  PIZZA/BEER  1259.14818956 ->   0.12597903 ( 0.00010005) | RT.0 0 n0
2816<PHONE_NUMBER>   72005663)     reserved id.5914837145683558400  CHIPS/KMD    39.20228893 ->   2.50156648 ( 0.06381175) | RT.0 0 n0
2835 tradestatus | aliceid.10578871933071982593 RT.0 0
passhash 75ab65b78df65c92ce038....973ec21221cf27499d6f903 != G 37a8eec1ce19687d132fe290....a141d5f4133a33f0688f
userpass.(c6fa3182b336c8371c5f9....93d465ece15b548a003774f)
KMD importaddress  from UsnZMDNbwe9....Ca4tFAn9gR5ZJyeP failed, isvalid.-1
cant importprivkey.KMD RN8w....KCbnQt5gESg1 -> ({"error":"couldnt import"}), abort session

stderr:
exec error: Error: Command failed: "C:\Users\Coins\Downloads\BarterDEX-win64-x64-0.8.8-rc\BarterDEX-win64-x64\resources\app\assets\bin\win64\marketmaker.exe" "{\"gui\":\"simplegui\",\"client\":1,\"profitmargin\":0.01,\"userhome\":\"D:\\Coins\\Roaming\",\"passphrase\":\"default\"}"

Komodo seems to be fine..
PS C:\Users\Coins\Downloads\kmd_win_bins> .\komodo-cli.exe getinfo
{
  "version": 1000850,
  "protocolversion": 170002,
  "KMDversion": "0.1.1",
  "notarized": 693120,
  "notarizedhash": "0863d82bc99b885a52caeb3facd1ea0f1e2a5b0f021db37738a03db31505090e",
  "notarizedtxid": "7c2b6e759349e2e21d12598f56d83f1b8d9042a4051b33530ec6c82278abe93f",
  "notarizedtxid_height": "mempool",
  "notarized_confirms": 0,
  "walletversion": 60000,
  "balance": 1.72621981,
  "interest": 0.00000000,
  "blocks": 693150,
  "longestchain": 693150,
  "timeoffset": 0,
  "tiptime":<PHONE_NUMBER>,
  "connections": 8,
  "proxy": "",
  "difficulty": 30732502.00799247,
  "testnet": false,
  "keypoololdest":<PHONE_NUMBER>,
  "keypoolsize": 101,
  "paytxfee": 0.00000000,
  "relayfee": 0.00000100,
  "errors": ""
}

and also marketmaker exe is somehow working..
PS C:\Users\Coins\Downloads\BarterDEX-win64-x64-0.8.8-rc\BarterDEX-win64-x64\resources\app\assets\bin\win64> .\marketmak
er.exe
WSAStartup called
null return from NXT api call

Total redeemed.0

>>>>>>>>>> already processed:

>>>>>>>>>> already processed:

So the reason might be i created the seed on linux? I can create a new seed, and use it on windows in native mode without problems..

@ahgafdf  it seems last line you observe its referring d drive for coins file
d:\coins\Roaming
it should be relavent to  c drive, where all barterdex userdata info all stored
location: %appdata%\BarterDEX


Merged scenario and portfolio

Summary
Input is being made from scenario (.json), which further links to topology (.json). Internal codebase adjusted accordingly. Output is done in a simulation results file.
Implementation Notes :hammer_and_pick:
N/A
External Dependencies :four_leaf_clover:
N/A
Breaking API Changes :warning:
Scenario.json file changed (i.e., the input is modified). Portfolio has been deleted, topology, allocation policy, workload, exportModels, failureModels, are now lists.

Demo folder removed from git (deleted & untracked). Please review


Switching to ubuntu-20.04, manylinux 2_17 for abi3

I was not able to reopen the last PR, sorry for the mess.
What I've learned is that building cp37 abi wheels on higher python versions was not the greatest idea, as the wheels were bot being able to be installed when I tried RHEL-7.9 with rh-python38. Again, sorry!
With ubuntu-20.04 and manylinux 2_17 (aka 2014), it works fine. I've also tried python3.7 on Fedora and that works fine also.
Manylinux 2_17 will be EOL June 2024, so I'd propose keeping it till then, as it allows also building ppc64, i686.
To add to this, I find building ppc64 (not le) as part of the cp36 "legacy" would be just too much trouble, as manylinux-cross does not copy python from manylinux images for armv7l and ppc64 as it does for the rest and there simply is not python3.6.
Removing the workaround line, as it was fixed upstream.
The missing AF_ seems to fixed by your changes, thanks!

The missing AF_ seems to fixed by your changes, thanks!

See https://github.com/SamuelYvon/netifaces-2/issues/13 as it might impact you. I'll check over the changes shortly :)


Add support for Bluesky.app

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting a new site support request
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that none of provided URLs violate any copyrights or contain any DRM to the best of my knowledge
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and am willing to share it if required

Region
US
Example URLs

Single Video: yt-dlp https://bsky.app/profile/bsky.app/post/3l3vgf77uco2g

Provide a description that is worded well enough to be understood
Unsupported URL. As of Sep 11, 2024, Bluesky has started rolling out video support on their site.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', 'https://bsky.app/profile/bsky.app/post/3l3vgf77uco2g']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp [4d9231208]
[debug] Python 3.12.5 (CPython x86_64 64bit) - Linux-6.10.9-arch1-2-x86_64-with-glibc2.40 (OpenSSL 3.3.2 3 Sep 2024, glibc 2.40)
[debug] exe versions: ffmpeg 7.0.2 (setts), ffprobe 7.0.2
[debug] Optional libraries: Cryptodome-3.20.0, brotli-1.1.0, certifi-2024.08.30, mutagen-1.47.0, requests-2.32.3, sqlite3-3.46.1, urllib3-1.26.20, websockets-12.0
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1830 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp)
[generic] Extracting URL: https://bsky.app/profile/bsky.app/post/3l3vgf77uco2g
[generic] 3l3vgf77uco2g: Downloading webpage
WARNING: [generic] Falling back on generic information extractor
[generic] 3l3vgf77uco2g: Extracting information
[debug] Looking for embeds
ERROR: Unsupported URL: https://bsky.app/profile/bsky.app/post/3l3vgf77uco2g
Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/yt_dlp/YoutubeDL.py", line 1626, in wrapper
    return func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/yt_dlp/YoutubeDL.py", line 1761, in __extract_info
    ie_result = ie.extract(url)
                ^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/yt_dlp/extractor/common.py", line 740, in extract
    ie_result = self._real_extract(url)
                ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/yt_dlp/extractor/generic.py", line 2526, in _real_extract
    raise UnsupportedError(url)
yt_dlp.utils.UnsupportedError: Unsupported URL: https://bsky.app/profile/bsky.app/post/3l3vgf77uco2

[!NOTE]
Note for devs: all info is available at f'https://public.api.bsky.app/xrpc/app.bsky.feed.getPostThread?uri=at%3A%2F%2Fbsky.app%2Fapp.bsky.feed.post%2F{video_id}&depth=0'
Example:

{
  "thread": {
    "$type": "app.bsky.feed.defs#threadViewPost",
    "post": {
      "uri": "at://did:plc:z72i7hdynmk6r22z27h6tvur/app.bsky.feed.post/3l3wdzzedvv2y",
      "cid": "bafyreienxdczt4j4ml3gnt36cfhpy6cdfefxyvx7lmrrcryppyysn2yybi",
      "author": {
        "did": "did:plc:z72i7hdynmk6r22z27h6tvur",
        "handle": "bsky.app",
        "displayName": "Bluesky",
        "avatar": "https://cdn.bsky.app/img/avatar/plain/did:plc:z72i7hdynmk6r22z27h6tvur/bafkreihagr2cmvl2jt4mgx3sppwe2it3fwolkrbtjrhcnwjk4jdijhsoze@jpeg",
        "associated": {
          "chat": {
            "allowIncoming": "none"
          }
        },
        "labels": [],
        "createdAt": "2023-04-12T04:53:57.057Z"
      },
      "record": {
        "$type": "app.bsky.feed.post",
        "createdAt": "2024-09-12T02:02:32.974Z",
        "embed": {
          "$type": "app.bsky.embed.video",
          "alt": "Debbie Ryan giving an interview. \"I want to make history. And that's what this is.\"",
          "aspectRatio": {
            "height": 478,
            "width": 884
          },
          "video": {
            "$type": "blob",
            "ref": {
              "$link": "bafkreif2firztfyxoz6krysgmtzhlf5f66e5ettp5rdzbav3zmlzcfk66q"
            },
            "mimeType": "video/mp4",
            "size": 772495
          }
        },
        "langs": [
          "en",
          "pt"
        ],
        "text": "Bluesky, you're setting ANOTHER all-time record for activity here! Novo recorde histórico! 🤯 \n\nRight now, we're already 10% higher than our all-time peak!"
      },
      "embed": {
        "$type": "app.bsky.embed.video#view",
        "cid": "bafkreif2firztfyxoz6krysgmtzhlf5f66e5ettp5rdzbav3zmlzcfk66q",
        "playlist": "https://video.bsky.app/watch/did%3Aplc%3Az72i7hdynmk6r22z27h6tvur/bafkreif2firztfyxoz6krysgmtzhlf5f66e5ettp5rdzbav3zmlzcfk66q/playlist.m3u8",
        "thumbnail": "https://video.bsky.app/watch/did%3Aplc%3Az72i7hdynmk6r22z27h6tvur/bafkreif2firztfyxoz6krysgmtzhlf5f66e5ettp5rdzbav3zmlzcfk66q/thumbnail.jpg",
        "alt": "Debbie Ryan giving an interview. \"I want to make history. And that's what this is.\"",
        "aspectRatio": {
          "height": 478,
          "width": 884
        }
      },
      "replyCount": 543,
      "repostCount": 932,
      "likeCount": 18625,
      "quoteCount": 422,
      "indexedAt": "2024-09-12T02:02:32.974Z",
      "labels": []
    }
  }
}


Support for loading requests from older versions

We have a lot of sample requests created with an older version of REST client, and we cannot open them with 3.5. It would be great to have backward compatibility or a way to migrate files from the old format to the new one.

I broke compatibility with 2.x when I released 3.0. All 3.x files should be openable by 3.5 version.
Unfortunately, I don't have any plan of writing a 2.x migration tool as of now. But, note that the file formats used by RESTClient are plain XML--so it may be possible for you to develop a script to do this. Even more awesome if you could share the script with the community.

Hi Subash,
Really useful tool and ease of use. But as of now I am trying to use the threatconnect api with this tool. But we are unable to hit a request even with your tool.
Can u please help us in this to let us know how to send header request to the api as you would have already used the same.
We have created signature which consist of url and the scretkey with hmac256 for the same and unix timestamp.
Even in your sample code the threatconnect code is missing , if you could help in with the missing code snippet would be real help.
Thanks in advance.


fix encoding of loaded markdown and exported html

Seems reasonable but can you explain what platforms/python this is not a no-op on and/or what problems it solves?

Sorry for my lack of explanation. While running the script under Windows 10 and Python 9.5.4 I had issues with the Czech language. The markdown wasn't being loaded properly even though the file was UTF-8 encoded and afterwards the HTML was exporting incorrectly.

I don't have access to a Windows system, but I assume the problem there is that the locale is not UTF-8, the encoding of the default resume.md this repo ships.
Perhaps the "right" thing to do in the long term is to use something like chardet to infer the encoding of resume.md on disk. That would allow the user to use a different encoding (that may or may not match their locale), and get the expected behavior without having to edit the python script.
But I think the set of people who won't or can't use UTF-8 is probably pretty small these days, so hard-coding UTF-8 in the python script (i.e. your change) is the next best thing, and I'm happy to merge this.
Thank you!


Combined Test + Vaccination QR Code for 2G+

Current Implementation
When having to show test and vaccination for 2G+, the user has to separately show test and vaccination qr code. This takes more time, to show screen twice and navigate in the app.
Feature description
When an active test AND a vaccination certificate with the same name is saved in the app, the user also gets the option to view the combined QR code, which certifies both the test and the vaccination.
The scanning person will see both the validated test and the validated vaccination.
Problem and motivation
Checking both test and vaccination takes time, so a combined QR code makes it a lot faster for the scanner. This would streamline the organizational work.
Is this something you're interested in working on
No :D

This is not possible inside the EU DCC schema, each certificate can only certify one thing, either a vaccination or a test, but not both.
What could be considered is to make this a Germany only solution where a new QR code with the information of test & vaccination is created which can then be scanned by CovPassCheck.

https://github.com/ehn-dcc-development/hcert-spec/issues/111

@claravoss thanks for opening this wishlist item. It's something that we are already looking into.
A simple way to navigate between vaccination/recovery certificate and a recent test certificate is currently being implemented (see https://github.com/corona-warn-app/cwa-app-ios/pull/3938 and https://github.com/corona-warn-app/cwa-app-android/pull/4469).

This is not possible inside the EU DCC schema, each certificate can only certify one thing, either a vaccination or a test, but not both.

There are some ideas to do this while retaining EU compatibility. The unprotected COSE header can be quite useful 😉 But nothing set in stone so far...

@mlenkeit
Okay, interesting, but just to make sure, merging of vaccination & test certificates in one certificate is not possible currently, or am I mistaken here?

@Ein-Tim merging the JSON structure is currently not possible as per the EU DCC schema definition.

@mlenkeit Okay, yes, this is what I meant with my comment.
But thanks for your answer!

Here we go, something is definitely planned: https://github.com/corona-warn-app/cwa-app-android/pull/4491

Hi @mlenkeit ,
my thoughts that combining the QR codes won't be possible at all I shared here: https://github.com/Digitaler-Impfnachweis/covpass-android/issues/107#issuecomment-986045958

This is not possible inside the EU DCC schema, each certificate can only certify one thing, either a vaccination or a test, but not both.

@Ein-Tim There are some ideas to do this while retaining EU compatibility. The unprotected COSE header can be quite useful 😉 But nothing set in stone so far...

So, I'm quite curious how the unprotected COSE header may be used... The only possibility that I can think about would create QR codes of at least 1.4KB in size?
Could you share some more details?

@mlenkeit
Is there already a plan to extend the up coming '2G check-in' also for 2G+B in the near future? For mRNA vaccinated people (1/1, 2/2, 3/3) it would only be necessary to present the 3/3 DCC QR code. For J&J jabbed and mRNA boostered people, the J&J 1/1 and the 2/2 mRNA DCC QR code was necessary. I'm not completely sure how it can be achieved for the recovered ones, who got twice vaccinated after recovery. The 2nd jab should be the booster then, so in this case it could be enough to present the recovery DCC together with the 2/2 vac DCC QR code.
If this was already in the backlog, it would make many people happy... Especially if CovPassCheck would be enhanced with serial scanning of DCCs per user, like it has been implemented into Austria's GreenCheck recently.

There is no combined view but since version 2.16 there is a combined view of certificates. See the blog post: Corona-Warn-App version 2.16 shows users’ current status evidence

@claravoss (@dsarkar / @larswmh)
I recommend to close this issue now, see https://github.com/corona-warn-app/cwa-wishlist/issues/715#issuecomment-1085892580. This is probably the best that can be done currently.

I again vote for closing this issue because:

CWA now includes a combined view for certificates (Corona-Warn-App version 2.16 shows users’ current status evidence)
CovPassCheck supports serial scanning


Update chat RFC status to ACCEPTED

Per @npmccallum, this should be a place to debate and discuss specific acceptance criteria for our chat RFC.

Is this PR only for the chat program itself and not the RFC about the chat program? The RFC about the chat program needs to update the chat link for Rocket.chat.
But re: the program itself, I have accepted it FWIW.

@mbestavros Please fix this in a separate PR.

Seeing that we have consensus, the status change is approved.


🐛 Fix performance regression

Container.is_initialised is a costly operation, loading the config JSON every time.
In https://github.com/aiidateam/disk-objectstore/commit/1d7c389c353185c1923c9addb1b107c283d5f561, the config is now called on every call to loose_prefix_len, leading to a massive performance degradation.
This PR makes sure the is_initialised test is called only if the config has not already been loaded into memory.
Before:
tests/test_benchmark.py::test_loose_read
ncalls  tottime percall cumtime percall filename:lineno(function)
1       0.0022  0.0022  0.3835  0.3835  disk-objectstore/disk_objectstore/container.py:824(get_objects_content)
1001    0.0055  0.0000  0.3758  0.0004  disk-objectstore/disk_objectstore/container.py:472(_get_objects_stream_meta_generator)
1000    0.0029  0.0000  0.3058  0.0003  disk-objectstore/disk_objectstore/container.py:213(_get_loose_path_from_hashkey)
3000    0.0019  0.0000  0.2959  0.0001  disk-objectstore/disk_objectstore/container.py:380(loose_prefix_len)
3000    0.0068  0.0000  0.2940  0.0001  disk-objectstore/disk_objectstore/container.py:371(_get_repository_config)
3000    0.0315  0.0000  0.2873  0.0001  disk-objectstore/disk_objectstore/container.py:270(is_initialised)

After:
tests/test_benchmark.py::test_loose_read
ncalls  tottime percall cumtime percall filename:lineno(function)
1       0.0014  0.0014  0.0793  0.0793  disk-objectstore/disk_objectstore/container.py:824(get_objects_content)
1001    0.0034  0.0000  0.0733  0.0001  disk-objectstore/disk_objectstore/container.py:472(_get_objects_stream_meta_generator)
1000    0.0240  0.0000  0.0240  0.0000  ~:0(<built-in method io.open>)
...
3000    0.0012  0.0000  0.0017  0.0000  disk-objectstore/disk_objectstore/container.py:380(loose_prefix_len)

I've also fixed the issue with codecov initially reporting lower test converage, caused by the fact that it was being uploaded & overwritten for every matrix run (and just by luck the windows tests are loaded last, which have the full test coverage)

Thanks!
The fix is right, however the fix on the coverage is wrong.
Indeed, as you see now coverage went down because there is a very small fraction of tests that are only run on linux or on mac.
Are you sure that it does not merge?
In my experience, it does!
It's just that it will prepare a comment as soon as the first build finishes, so at the beginning it seems it didn't use the windows ones, but if you wait at the end it will update the comment and merge the results.
You can see this in the tests for commit 1d7c389  that all pass with 100% coverage.
So I suggest you remove the fix for the coverage and then we merge the actual bug fix

Are you sure that it does not merge?

Ah good, I was lead to believe otherwise lol


permissions are too open

Failed to start dae.service
warning: the following units failed: dae.service
× dae.service - dae Service
     Loaded: loaded (/etc/systemd/system/dae.service; enabled; preset: enabled)
    Drop-In: /nix/store/6ypvpgzv82cjvk5gbsii5jj5wq1r1g9g-system-units/dae.service.d
             └─overrides.conf
     Active: failed (Result: exit-code) since Thu 2024-09-19 20:05:48 CST; 277ms ago
 Invocation: 176b2296f1f54b80b8802dafe58525ab
       Docs: https://github.com/daeuniverse/dae
    Process: 111225 ExecStartPre=/nix/store/940w4mbmxrryv3bil0200ypj6h71ca0m-dae-v0.7.1/bin/dae validate -c /nix/store/zzpamv0kdgii82pabzqz61afhib8fd7r-absx.dae (code=exited, status=1/FAILURE)
         IP: 0B in, 0B out
   Mem peak: 143.1M
        CPU: 892ms

9月 19 20:05:47 absx systemd[1]: Starting dae Service...
9月 19 20:05:48 absx dae[111225]: permissions 0444 for '/nix/store/zzpamv0kdgii82pabzqz61afhib8fd7r-absx.dae' are too open; requires the file is NOT writable by the same group and NOT accessible by others; suggest 0640 or 0600
9月 19 20:05:48 absx systemd[1]: dae.service: Control process exited, code=exited, status=1/FAILURE
9月 19 20:05:48 absx systemd[1]: dae.service: Failed with result 'exit-code'.
9月 19 20:05:48 absx systemd[1]: Failed to start dae Service.
9月 19 20:05:48 absx systemd[1]: dae.service: Consumed 892ms CPU time, 143.1M memory peak.
warning: error(s) occurred while switching to the new configuration

my config:
services.dae = {
  enable = true;
  configFile = ./config/absx.dae;
  assets = with pkgs; [
    v2ray-geoip
    v2ray-domain-list-community
  ];
};

permission of configFile:
Permissions  Size User Date Modified    Git Name
.rw-r--r--   13Ki absx 2024-09-19 19:56  NM absx.dae

(change this in /etc/nixos will not affect that in /nix/store)

configFile = ./config/absx.dae;

This is an anti-pattern since it stores your dae config file into nix store with global-readable permission. Please use the absolute path string as example shows.

why it happen again when i use str ab path

why it happen again when i use str ab path

If so it might be a literally permission too open issue. exec stat /path/to/daeconfig and check if the permission met requirement.

{
  config,
  inputs,
  lib,
  pkgs,
  ...
}: {
  environment.systemPackages = with inputs.daeuniverse.packages.x86_64-linux;
    lib.optionals config.services.daed.enable [
      dae
      daed
    ];

  services.dae = {
    disableTxChecksumIpGeneric = false;
    enable = true;
    openFirewall = {
      enable = true;
      port = 12345;
    };

    configFile = "/home/solitudealma/nixos-config/nixos/_mixins/configs/dae/config.dae";
    assets = with pkgs; [v2ray-geoip v2ray-domain-list-community];
  };

  services.daed = {
    assetsPaths = with pkgs; [
      "${v2ray-geoip}/share/v2ray/geoip.dat"
      "${v2ray-domain-list-community}/share/v2ray/geosite.dat"
    ];
    configDir = "/home/solitudealma/nixos-config/nixos/_mixins/configs/dae";
    enable = true;
    openFirewall = {
      enable = true;
      port = 12345;
    };
  };

  # manual launch(geoip.dat,geosite.dat,config.dae needs to be in the same directory):
  # `wget<EMAIL_ADDRESS>  # `wget wget<EMAIL_ADDRESS>  # `dae run --disable-timestamp -c /path/to/config.dae`
}

err:

permissions 0644 for '/home/solitudealma/nixos-config/nixos/_mixins/configs/dae/config.dae' are too open; requires the file is NOT writable by the same group and NOT accessible by others; suggest 0640 or 0600

Set permission just solve this.
chmod 640 /home/solitudealma/nixos-config/nixos/_mixins/configs/dae/config.dae

Since we have no way to check the file permission at eval time. The file permission too open, as it reported at runtime.


Allow-all-traffic vs "Allow_all_traffic"

In the section that describes how to configure the SIM Policy "allow-all-policy" it says to select the service "Allow-all-traffic".
However, the service created before is called "Allow_all_traffic" so we should be using "_" instead of "-".

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

ID: 42ca6844-98b0-6ac6-d28b-9069b7b985d2
Version Independent ID: ab1b9a45-ccdb-e2ff-9159-74abd428bf00
Content: Default service and allow-all SIM policy - Azure Private 5G Core
Content Source: articles/private-5g-core/default-service-sim-policy.md
Service: private-5g-core
GitHub Login: @djrmetaswitch
Microsoft Alias: drichards

@ErnestoAzure
Thank you for bringing this to our attention.
I've delegated this to content author @djrmetaswitch, who will review it and offer their insightful opinions.

@djrmetaswitch
Could you please review add comments on this, update as appropriate.

#reassign:robswain

Hi Ernesto,
Thanks for raising this. We've pushed a fix for this and the doc should be updated later today.
#please-close


add ability to update the running image, parameters, and configuration of a given service

Background & motivation
https://github.com/kurtosis-tech/ethereum-package/issues/465
https://github.com/kurtosis-tech/ethereum-package/issues/458
There have been some requests from users of the Ethereum Package to change a service in the network when it comes to its underlying image or arguments so that they don't have to recreate the testnet
Desired behaviour
An update_service api that allows you to change image or other arguments of a given service
How important is this to you?
Nice to have; this feature would make using Kurtosis more enjoyable.
What area of the product does this pertain to?
CLI: the Command Line Interface

idempotent runs might solve for this!

Hey @h4ck3rk3y ! yep, I think enclave updating (formerly known as idempotent runs 😆 ) would solve for this - just re-throw an updated configuration at the enclave

Yep! idempotent runs / updates do solve this. Everything but the affected instructions get skipped.

Waiting for @barnabasbusa to confirm if this is enough for now; will close this if so

Currently proposed workflow is arg tweaking and re-running against the same enclave
participants:
  - el_client_type: geth
    cl_client_type: lighthouse
  - el_client_type: geth
    cl_client_type: lighthouse
  - el_client_type: geth
    cl_client_type: lighthouse
    el_client_image: "ethereum/client-go:v1.13.10"

Changing the 10 to 11 and back to 10, seems to work on my machine

Enclave edits should address this issue but I've tried running an updated config against an existing enclave and enclave edits aren't working. Something triggers entire enclave to be rerun even when changing arg to just add an additional service. Unsure if it's something in the package or a bug in enclave edit logic. I've done a deep dive for a few hours and found some potential issues but haven't root caused yet. LMK if you're seeing otherwise though @h4ck3rk3y @barnabasbusa


Custom input file after choice file nothing change.

When we choice file nothing change (we don't see filename).
https://getbootstrap.com/docs/4.0/components/forms/#file-browser
This should work this way? We need write JS to look change event and update filename inside custom-file-control?
Tested on:
Beta 4.0.0
Safari 11  and Chrome  60
MacOS 10.13

That's true no update, should we add a simple plugin which handle that ?
@mdo, @XhmikosR, @bardiharborow

Test

We have added file name update support in <b-form-file>, which is the Bootstrap-Vue implementation of Bootstrap's custom file input.  YOu might be able to make a plugin out of our file handler code:  https://github.com/bootstrap-vue/bootstrap-vue/blob/dev/lib/components/form-file.vue
Basically it places the file names (or file count, in the case of multiple) in a data-* attribute which then picks up the file name(s) via CSS content() selector.

I thought we had code for this at some stage (not in a core plugin, but as an optional extra). Where did that go?

I don't remember if we had code about that 😯

I'm preety sure the doc mentions someplace that filename update is not implemented
But it's fairly easy to put in place, here's a solution:
$('.custom-file-input').on('change', function() {     let fileName = $(this).val().split('\\').pop();     $(this).next('.custom-file-control').addClass("selected").html(fileName); });

@jplaverdure this code won't work for multiple file input.
But I agree this should be a feature, it just feels weird to use this component and not have the file name auto update.

Thanks @jplaverdure

This but still exists on v4.0.0 beta2

Closing as duplicate of #20813.

Thanks @jplaverdure
$('.custom-file-input').on('change', function() {
let fileName = $(this).val().split('\').pop();
$(this).next('.custom-file-control').addClass("selected").html(fileName);
});
This code is working on single file upload

@jplaverdure your code isn't working for me:((

@bouiboui  - line 3 should target the sibling of the input requiring update, as with multiple inputs on a page your code would update all labels with the same filename.
$('.custom-file-input').on('change', function() {
    let fileName = $(this).val().split('\\').pop();
    $(this).siblings('.custom-file-label').addClass("selected").html(fileName);
});

Absolutely, I updated my comment.

I added a few lines to the snipped so the default label text gets restored if the file is deselected.
$('.custom-file-input').on('change', function() {
    let fileName = $(this).val().split('\\').pop();
    let label = $(this).siblings('.custom-file-label');

    if (label.data('default-title') === undefined) {
        label.data('default-title', label.html());
    }

    if (fileName === '') {
        label.removeClass("selected").html(label.data('default-title'));
    } else {
        label.addClass("selected").html(fileName);
    }
});

can we do the same in javascript?

You mean, without jQuery? You can, but it will be a lot more verbose.
What's the context, why don't you want to use jQuery?

@proakshay and @bouiboui Bootstrap use this plugin to do that: https://www.npmjs.com/package/bs-custom-file-input

If i want for multiple file uploads in single page these code is not working it is working for single file upload  and it is applying for last control of file upload how can i upload multiple file uploads...

@kondagariraviteja1 you should use https://www.npmjs.com/package/bs-custom-file-input it handle multi file upload, you just have to add multiple attribute on your input file 😉


reactivate nixos-option

Motivation for this change
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

Tested using nix-build -E "with import ./nixos { configuration = {}; }; config.system.build.nixos -option"
The last revert patch could be reverted when nix will be updated in nixpkgs.

no more relevant.


why not suppport gbk charset

gbk charset is supported. But font fallback has to be done manually. You can specify a font which the desired characters in the guifont setting by separating the font names in the fallback list by a comma

gbk charset is supported. But font fallback has to be done manually. You can specify a font which the desired characters in the guifont setting by separating the font names in the fallback list by a comma

gbk charset is supported. But font fallback has to be done manually. You can specify a font which the desired characters in the guifont setting by separating the font names in the fallback list by a comma

how can i do this


implement terraform-boot for validate method

[ ] use terraform-validate method for validating terraform script.
[ ] Parse response as in the current validator method.

let me do it


How to use with Angular and Bootstrap

My app is created using Angular and Bootstrap. How can I use useraccounts:bootstrap if the app is running on Angular?

You can't use this specific resource with Angular, because this was designed for Blaze templating. Check out, https://www.meteor.com/tutorials/angular/adding-user-accounts, for more information on the matter.


REQUEST now supports POST

The experimental REQUEST function now supports any HTTP method.
This makes sense if

Your formula is idempotent, taking actions that make external state consistent with the data in your document
You have an endpoint with GET behaviour, but it actually requires a POST/PUT method

If the backend handles the POST requests, wouldn't a malicious user be able to execute commands to other services with the IP of the server? (making a security breach)

I didn't know the function were disabled by default. That solves my main concern :).

Perhaps a new flag would be the way to go, for example a separate GRIST_ENABLE_REQUEST_FUNCTION?

I wonder if there wouldn't be a way to name this function to be future-proof, in case other possibly-harmful functions would be introduce (unless you say it's much probably the only function of that sort). In that case, I would suggest to introduce a variable whose value would not be a boolean but a list of function names (GRIST_..._FUNCTIONS="request").
Though I am not sure about how to name them (GRIST_EXTRA_FUNCTIONS_USE_WITH_CAUTION="request"? GRIST_REMOTE_EXECUTION_FUNCTIONS_USE_WITH_CAUTION="request"?).

It makes no difference to me either way - will go with GRIST_ENABLE_REQUEST_FUNCTION for now and change depending on outcome of any discussion :)

At Grist Labs we are not planning on introducing several functions like this. REQUEST is a stalled project, something that got started but foundered on some complications - security questions, and concern that naive users could end up doing a LOT of requests. Glad to see it getting use.

@paulfitz this makes sense - I can't imagine a way of making REQUEST work in an environment where the users aren't trusted and could be naive and expect speed, that doesn't involve a lot of complexity. It's a killer feature though for integrating Grist with things, so thanks a lot!
This PR is now ready to be re-reviewed.
I've manually tested that GRIST_ENABLE_REQUEST_FUNCTION=1 is needed to enable REQUEST, also some simple examples of GET and POST with actual Grist.

It's a killer feature though for integrating Grist with things, so thanks a lot!

REQUEST is my baby, so thanks for saying this, it warms my heart :blush:

Ok - this PR is now ready for re-re-review.

LGTM, thanks! @paulfitz are you satisfied?

Yup, thank you both!


Scroll snapping to top on iOS

My code is:
<KeyboardAwareScrollView
             scrollEnabled={true}
             style={styles.container}
         >

const styles = StyleSheet.create({
    container: {
      marginTop: 30,
        flex: 1,

    },

Thanks!

having the same issue as well, the text input at the bottom of my view has some space between it and the keyboard but when I scroll down, it will stay snapped to the textinput

I don't understand this issue. Can you provide more codes to reproduce the issue? And a screenshot would be better.

@Swordsman-Inaction
import React from 'react';
import { StyleSheet,
        Text,
        TextInput,
        Button,
        FlatList,
        View,
        Dimensions } from 'react-native';
import { KeyboardAwareScrollView } from 'react-native-keyboard-aware-scroll-view'

export default class Chat extends React.Component {

  render() {
    return (
      <View style={{flex: 1}}>
      <KeyboardAwareScrollView
        resetScrollToCoords={{ x: 0, y: 0 }}
        contentContainerStyle={styles.containerStyle}>
      <FlatList
        style={styles.messages}
        data={[{key: 'a'}, {key: 'b'}]}
        renderItem={({item}) => <Text>{item.key}</Text>}
        />
      <View>
      <TextInput style={styles.input} placeholder="Enter a message" />
      </View>
      </KeyboardAwareScrollView>
      </View>
    );
  }
};

const styles = StyleSheet.create({
  containerStyle: {
    flex: 1,
    justifyContent: 'flex-end'
  },
  input: {
    height: 50,
    width: Dimensions.get('window').width,
    borderColor: 'red',
    borderWidth: 1,
  },
  messages: {
    flex: 1,
    width: Dimensions.get('window').width,
    borderWidth: 1,
    borderColor: 'green'
  }
});

here is the output when the app is first opened:

as you can see, there is a space between the keyboard and the TextInput since the view has snapped to the top of the screen. however after manually scrolling the view once with the keyboard open, it snaps back to the keyboard as expected:

i've been able to temporarily combat this with adding a negative extraScrollHeight but I believe this is a bug and needs to be fixed.

@amritsub In fact, it's a feature, not a bug 😝 . There is a default value for extraHeight which is 75(actually I don't know why @alvaromb ). If you don't want it, simply add extraHeight={0} to clean the default value.

@Swordsman-Inaction setting extraHeight to 0 in the FlatList above causes the bottom TextInput to not show up at all, so it made matters worse. I would like the TextInput to appear right above the Keyboard.

@amritsub  After I set extraHeight={0} to KeyboardAwareScrollView, everything works fine to me.  Also you mentioned that you added a negative extraScrollHeight, don't forget to remove that.

@Swordsman-Inaction you're right, I was actually using react-navigation which provided a nav bar at the top of the screen, which was messing up the layout. After removing the navigation, the example works like the screenshot you posted. I'll have to fiddle with react-navigation to get it to play nicely with this library. Thanks so much for your help!

My pleasure 😄


Incorrect CPU detection on Apollo Vampire Accelerators

AmigaTestKit 1.21 displays the CPU on the main page as 68060 Rev 1.
I have an Amiga 600 with MantiCore accelerator.
This is identified as a 68080 with 68882 FPU.
Relevant info...
CPU attention flags
SAGA chipset
Vampire specific version - $DFF3FC - 8bit Card Version / 8bit clock multiplier
Could this be incorporated into your next update?
Thankyou,
Alexander.

Accurate detection of modern soft cores is out of scope. Especially as current detection routine doesn't use Kickstart flags at all, and there's no docs on 080 CPU detection except via Kickstart flags.
There probably is some detection method that hits the hardware directly but I don't have any Vampires to test it out and the published documentation is pants: I don't really trust that the question of what is a 68080 isn't a moving target. And there's little community support around this sort of thing (eg there's no WinUAE emulation of Vampire for software testing).


Update group settings: Admin needs to approve new participants

An API to toggle this option.

An API to toggle this option.

Check the readme file ita there

If you mean sock.groupRequestParticipantsUpdate, that's not what I am looking for. This is for a group that is to approve new participants as far as I know where as I'm looking for the API to change a group setting to "approve new participants" = "on".

const response = await sock.groupRequestParticipantsUpdate(
<EMAIL_ADDRESS>// id group,
<EMAIL_ADDRESS><EMAIL_ADDRESS>"approve" // replace this parameter with "reject"
)
console.log(response)
Try this

Isn't this to approve new participants?

Isn't this to approve new participants?

Yes but bot need admin

Ok but that's not what I'm trying to do. I'm trying to change a group setting.

Ok but that's not what I'm trying to do. I'm trying to change a group setting.

Change it


Change wording for CrowdIn issues

See https://crowdin.com/translate/zen-community-platform/1/en-ga#336
https://crowdin.com/translate/zen-community-platform/1/en-ga#502
https://crowdin.com/translate/zen-community-platform/1/en-ga#2671
and
https://crowdin.com/translate/zen-community-platform/1/en-ga#338

Also:

https://crowdin.com/translate/zen-community-platform/1/en-de#q=Citytown
https://crowdin.com/translate/zen-community-platform/1/en-de#197

Also look at https://github.com/CoderDojo/community-platform/issues/844
https://github.com/CoderDojo/community-platform/issues/843
https://github.com/CoderDojo/community-platform/issues/842

And this! https://crowdin.com/translate/zen-community-platform/1/en-de#3361

These three entries are not translated:

"Open, come along" is not translated. It should be "Open, just show up" or vise versa.

https://crowdin.com/translate/zen-community-platform/1/en-nl#430 Could be worded better

Badges tab doesn't look to be fully added to this file.

This is not translated + should be integrated into the sentence at the "..."

This was fully merged into 934. Please close if you had a look aver it and comment anything further in 934 where it can be assigned a checkbox.


Receipt fixes

Makes it so that receipts are returned when EVM runtime errors occur (e.g. REVERT). Adds missing status, from, and to fields to the transaction receipt.

@benjamincburns Since this is a pretty substantial change (some previous transactions that were previously invalid are now valid), can you summarize the discussion from RocketChat about why this is the desired behavior, what the pros and cons are, and what use cases this support.

Go formatting issues are now fixed.

@aludvik sure thing.
To be clear, this change doesn't allow for contract state updates when transaction execution fails. It simply records the transaction execution failure in a transaction receipt which is appropriate for the transaction family.
Prior to these changes there was no way for a client which submitted its transactions via Seth's RPC interface to determine whether the transaction was executed, and what the result of that execution was.
Via the Ethereum RPC interface, the usual transaction flow looks like this:

Client submits a message call transaction to a contract address via either the eth_sendTransaction or the eth_sendRawTransaction RPC call
Server responds with RPC response containing transaction hash in the result field
Client uses the transaction hash returned by the server to poll for the result of the transaction via eth_getTransactionReceipt.
Until the transaction is mined into a block, the server always returns null in response to the client's eth_getTransactionReceipt request.
When the transaction is mined into a block, regardless of whether the transaction succeeded or failed,  the server responds to eth_getTransactionReceipt with a valid transaction receipt.
The client inspects the status field in eth_getTransactionReceipt to determine whether their transaction succeeded or failed.

If no receipt is produced when a message call to a contract address fails due to a runtime error (e.g. due to the REVERT opcode), then the client can't tell the difference between transaction failure, and the transaction never starting.

As to what use-cases this supports, I'm working on integrating the Truffle toolsuite with Sawtooth-Seth. See the blocked tickets on the commit-referenced Jira issue for more info.

Looks like I had some rust formatting issues as well - those should be fixed up now.

@benjamincburns Thanks for the response. Am I correct in understanding there are three types of validity with Ethereum transactions?

Totally valid - The transaction "object" was valid and the execution was a success
Valid but failed -  The transaction "object" was valid but the execution failed
Invalid - The transaction "object" was invalid because of something like a bad signature, bad payload, incorrect nonce.

Is that characterization accurate? Does the nonce still get updated if the transaction execution fails?

@aludvik sorry that I didn't see your question above! Yes, your characterization is accurate. The nonce gets updated in cases 1 and 2, as in these cases a transaction receipt is generated. Transaction receipts are included in block hash calculations, and as such they're stored on chain under the transaction receipt storage trie data structure.

Noticed that this branch has gone a bit stale, so I fixed up the outstanding conflicts. I've also ruthlessly culled the projects/issues I'm watching, so with any luck I won't miss future notifications on this PR!

FAIL: Missing Signed-Off Field
I suppose that's what I get for fixing conflicts with GitHub's internal tooling - will fix and force-push.

@benjamincburns Looks great.
Can you rebase on top of master (instead of adding the merge commit) and force-push?
Also, in your commit messages, can you remove the STL- from the first line? When we reference bugs (which isn't often currently), we prefer to follow https://chris.beams.io/posts/git-commit/ which is to put "Resolves: xxx" at the bottom of the commit message.

I'm not sure where this left off and it's been quite some time since the original submission. I've moved on to other projects in that time, so I think it's best if I go ahead and close.

I'm not sure where this left off and it's been quite some time since the original submission. I've moved on to other projects in that time, so I think it's best if I go ahead and close.


Add "Warn" method to DTP proxy

Thanks for building out this module @EricHripko -- it was a huge help for us.
On using it this year I notice that there is another method that we need to add to the proxy, otherwise compilation fails.

Hi @ashb 👋 Glad to hear that it came in useful for you and thank you for putting this contribution together! I imagine BuildKit added newer methods to the interface since v0.8.2, which is why it's failing to build with a newer version.

Thanks again for contributing - this change is now available via v0.2.0 🙂


[New Port Request] sqlpp11-connector-postgresql

Library name: sqlpp11-connector-postgresql
Library description: PostgreSQL connector for sqlpp11 library
Source repository URL: https://github.com/matthijs/sqlpp11-connector-postgresql
Project homepage (if different from the source repository):
Anything else that is useful to know when adding (such as optional features the library may have that should be included):

portfile.txt
CONTROL.txt
I've created the CONTROL and portfile.cmake files, it seams to works

@MarcoSpeziali, could you summit a PR for this port?

@PhoebeHui using those portfile and CONTROL files I was then unable to compile for some linking problems. So I think I made some mistakes

@MarcoSpeziali, If you'd like to continue working on it, please reopen and ping us!


Use setuptools and basic test

I added support for installation of the tool, ready to be uploaded to pypi and packaged.
I also added a basic test which needs to be extended of course.

Thank so much! I am taking look now.


Update lindera and lindera-core

Fixes https://github.com/mattico/elasticlunr-rs/issues/46
Due to the undocumented breaking change introduced in lindare-core v0.13.5^1, lindera <0.14 and lindera-core >=0.13.5 are now incompatible.

Thanks! More than just lindera have started requiring the 2021 edition.
I've decided to change the MSRV to 1.56.1 for that reason. Tested this locally and fixed CI.


save() issues

I'm testing the Python package and noticed the following for "save()":
Issues with embedded types (Note: I did not set the embedded types directly, but after I created the main instance):

Instances of embedded types with value type "array" are not correctly resolved for saving and causing an error.
The instance of linked types in instances of embedded types are integrated as embedded not linked which is not correct (example: person -> affiliation (embedded) -> organization (linked)).
Link to instances of linked types do not have to state their @type only their @id. Currently save adds the @type as well.

In the saved instance the same things hold as in issue #2 and #3.

If @context with @vocab is set the properties do not have to (should not ?) identify the vocab.
@type should not be given as a list but as a string (turning it into a list is EBRAINS KG specific and not a requirement by JSONLD).
Properties that require as value an array with 1 to N items always have to be defined as an array even if only one entry is provided (as defined by openMINDS).

General:

for saving a single file (single instance or single collection file) we may want to have the extension (".jsonld") automatically added when it is not given. Or causing an error when the extension is not given. (it currently does not complain)
saving a collection as directory should probably consider subdirectories according to schema types (instead of a purely flat list of JSONLDs)
we may want to use UUIDs for instances instead of incremental numbers (at least as option)
at one point in the past we decided to use this naming convention "http://LOCALHOST/openminds/instance/SCHEMATYPE/UUID" for @ids; I think something like this is better than just "_:000001"`(SCHEMATYPE would be written in lower camelCase here)

Special case:

we may want to consider tagging instances as "sensitive" in a collection. Those instances should be stored in a separate (sub)directory than the other instances of the collection (so that they can be relocated easily into higher protected space).

This issue was broken down to following issues
#7 , #8 , #9 , #10 , #11 , #12 , #13 , #14 , #15 , #16

Closing this, since it has been replaced with separate, more-specific issues


renderToString cannot work properly

Version
1.0.0-beta.24
Reproduction link
https://github.com/kazupon/vue-i18n-extensions/tree/moving
Steps to reproduce

git clone git@github.com:kazupon/vue-i18n-extensions.git
cd vue-i18n-extensions
git branch moving origin/moving
git checkout moving
yarn
yarn test:unit

What is expected?
pass the test in src/__tests__/repro.test.js
What is actually happening?
cannot pass the test in src/__tests__/repro.test.js:
 FAIL  src/__tests__/repro.test.js
  ● cannot work correctly

    expect(string).not.toContain(value)

    Expected string:
      ""
    Not to contain value:
      ""

      18 |     }
      19 |   })
    > 20 |   expect(str).not.toContain('')
         |                   ^
      21 | })
      22 |

      at Object.<anonymous>.it (src/__tests__/repro.test.js:20:19)

I notice renderToString  have the critical issue.
See the bellow:
https://github.com/vuejs/vue-test-utils/blob/dev/packages/server-test-utils/src/renderToString.js#L40-L46
renderedString cannot return the correctly string, depending on the implementation of the component.
Vue SSR docs have been saying renderToString(vue-server-renderer) return the Promise.
https://ssr.vuejs.org/api/#renderer-rendertostring
I think renderToStrnig API should be re-designed.
I propose the below the API.

renderToString: return the Promise
renderToString: provide the callback argument

How about handling it through the sync option?
const str = renderToString(TestComponent)

const str = await renderToString(TestComponent, {
  sync: false
})

sound good to me. 👍

Do you have an example component that won't won't render correctly?

Sorry for my late reply.
That's is here
https://github.com/kazupon/vue-i18n-extensions/commit/cc85456c74663d3af8ae9299b304b372d4c17424#diff-0a45b66d57da4b0f77d1825941f54e4b


[BugFix][Cherry-pick 2.2] Fix nullptr of _query_ctx(lazy init) when it is not initialized (#14000)

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

run starrocks_be_unittest


Vulnerability roundup 112: openjpeg-2.4.0: 1 advisory [7.8]

search, files

[ ] CVE-2021-3575 CVSSv3=7.8 (nixos-21.11, nixos-unstable)

CVE details
CVE-2021-3575
A heap-based buffer overflow was found in openjpeg in color.c:379:42 in sycc420_to_rgb when decompressing a crafted .j2k file. An attacker could use this to execute arbitrary code with the permissions of the application compiled against openjpeg.

Scanned versions: nixos-21.11: efea022d6fe; nixos-unstable: 710fed5a248.
Cc @codyopel

Upstream doesn't appear happy with a fix yet.

Fixed in 34dbaede64a094d59b04a8e76f366f4da4f396cf.


Semtantic versioning of both BinderHub as a package and the Helm chart

I had a chat with @betatim today, and I really think it's worth the effort and complexity to start version controlling both BinderHub and the Helm chart separately.
There are several reasons this can benefit us, but at this point I think the most pressing matter is to make development in this repo less coupled to the operation of mybinder.org-deploy. By having releases and changelog, we would provide mybinder.org with better information about changes that would be deployed when bumping a Helm chart version.
Is this an effort acceptable to pursue? If so, there are technical complexities to outline and resolve that can be discussed.

I think it's a good idea, though I'd start by getting a stable version of BinderHub out. We'll need to do some API development work first, mostly related to https://github.com/jupyterhub/binderhub/issues/1318
Once it's released I think looking at decoupling the Helm Chart makes sense. Or were you thinking of decoupling it now?

We've discussed this in the January team meeting, and we decided to work towards it!
@manics about decoupling helm chart and binderhub python package - I don't want to work towards that as part of getting them both versioned together initially.
Our version bumps and changelog should reflect changes to either python package or helm chart, where we should try help clarify if something is helm chart specific I think.


Blocked Accounts Being Refollowed

So I built an extensive block list in order to help cut down on the amount of spam I retweeted, however there seems to be a problem with the way the script handles retweeting blocked accounts.
http://snag.gy/jc1dF.jpg
In this screenshot you can see me retweeting speed_racer420, however I had previously blocked him in order to stop from tweeting his material. The script re-added him to my follow list despite this. Any idea why the block function isn't working?

Hi @Zen00 ,
Can you please check again that this is your case? Maybe block a user that you see has recently retweeted something that the bot is likely to retweet, and see if the bot retweets it. I double checked now, by manually blocking some users and then checking with the bot, and it did not retweet any of those tweets. They are filtered out in the search function.

I'll have to try sometime later. My app got blocked because of too much spam or something and I have to get it unblocked. ;P
Anyways, to specify some accounts that keep popping back up, speed_racer420 and sswifttgamingg.

Hi @Zen00, I fixed this sort of in 5755ca1.
Additionally, the bot can be set to auto-block other bots it detects they are bots and that takes effect immediately by adding them to the block list array. The bot currently isn't programmed to reload your block list from Twitter in the event you block people through the website, but if this is a change you think is needed, I could have the bot periodically reload the block list from Twitter to ensure that it's up-to-date while running.


https://anilist-api.readthedocs.io/ doesn't exist

Hi,
i cannot find the docs linked in the readme (https://anilist-api.readthedocs.io/),
can you help me?
Thanks :D

This is a library for API v1 which was shutdown years ago so the docs are gone and this package won't work anymore.

Ok, thanks


Deterministically handle case conflicts in pod_support dir

This adds logic to de-duplicate case conflicting paths in the pod_support dir. This comes up in cases like the Folly pod, where the pod name is Folly (and therefore we try to put a copy of the headers under a Folly custom header search path directory) but the pod has module_name = 'folly' (which causes a similar set of headers under the folly directory). These two paths are the same on macOS due to the filesystem's case insensitivity, and which one wins is based on the ordering of the set that contains the directories, which is not well defined or deterministic across machines.
This change makes handling of this deterministic so we'll always get the same casing of these header directories, which aids in remote caching.

Note that since the goal is really just determinism, there's some other approaches that could work well, namely:

Blindly always update the mapping dict, which would cause us to take the last of each canonically-equivalent path, rather than the first. This might be a bit simpler with less code.
Just add a .sorted() in there, and still create/fill case-conflicting directories, but hope/assume that because the creation order is deterministic, the outcome will be too.

Let me know if you think either of these other approach would be better!

Thanks for the PR @FuegoFro 👍. I like the idea of making this deterministic, and seems like an overall good change.
Ultimately, it doesn't seem right that this is happening though. I noticed in the upstream logic, it inserts podSpec.name as an additional search path to populate with symlinks. It can't be legitimate to naively use the podSpec.name in this capacity and is likely a bug. These symlinks are tied to the header namespace selection logic. I was hoping to audit this, and clean it up as part of adding clang headermaps. That's probably a longer term fix.
PS: for Folly, there's a few other hacks, which I'm curious to hear if you had resolved these:
new_pod_repository(
  name = "Folly",
  podspec_url = "Vendor/PodSpecs/react-0.59/third-party-podspecs/Folly.podspec",
  url = 'https://github.com/facebook/folly/archive/v2<IP_ADDRESS>.zip',
  install_script = """
    # Force folly demangler off, we don't need it and it's being incorrectly enabled causing compile errors.
    /usr/bin/sed -i '' 's/FOLLY_DETAIL_HAVE_DEMANGLE_H 1/FOLLY_DETAIL_HAVE_DEMANGLE_H 0 \/\/ PINTEREST HACK, SEE Pods.WORKSPACE/g' folly/detail/Demangle.h
    # Rename 'build' directory temporarily as its name conflicts with bazel generated BUILD file.
    # Better future solution is to update P2B to export BUILD.bazel files.
    mv build build.orig
    __INIT_REPO__
    mv BUILD BUILD.bazel
    mv build.orig build
  """,
  generate_module_map = False
)

Huh, interesting to hear that the header logic may be the issue here. In general it seems that the (at times over generous/broad) pod_support dir has led to some issues (eg when auto-generating module maps needed for Swift compilation).
Haha yeah, we have some very similar hacks for Folly. We leave our build files called BUILD, so we just removed the build/ folder. But we have a very similar
/usr/bin/sed -i "" 's#__has_include(<demangle.h>)#0#' 'folly/detail/Demangle.h'


Spelling fixes

All the typos were bothering me.

@ajavadia and @1ucian0 not sure how I dismissed your approvals, but I'm done working on this branch whenever you want to review

add [WIP] (as "work in progress") in the title when you are still working on it next time. Thank you for fixing all these typos!


Don't cycle tab position by default anymore (and a few other cleanups)

Closes #2.
I'm breaking compatibility with older ST builds here because I believe they are not worth maintaining, so I created a PC PR for this: https://github.com/wbond/package_control_channel/pull/8886
Tags are already pushed.
I chose to make behavior configurable via a command parameter because a setting would have been overkill and because you may want to have both modes simultaneously.

I've forked this repo to https://github.com/deathaxe/MoveView years ago to

add ListInputHandler for targets
create commands which align better with ST's built-in commands.

I never liked those string arguments here. Mixing them up with integers doesn't improve it.

If compatibility is not an issue and separate commands as in MoveView are not desired, the API should IMHO at least look a bit more ST like by
Move tab relative
{ "command": "move_tab", "args": {"by": -1, "cycle": false} }

Move tab to absolute position counting from first tab onwards
{ "command": "move_tab", "args": {"to": 5} }

Move tab to absolute position counting from last tab backwards
{ "command": "move_tab", "args": {"to": -5} }

If compatibility is not an issue

That is indeed the biggest question here. So far, aside from the cycling behavior, my changes are backwards compatible, but I agree that we can use this opportunity to make more changes
I suspect that most users just use the default key bindings and haven't added their own. Even then, I could provide a backwards compatibility argument which would ensure everything works exactly as before when the old position argument is used.
I'll think about it for a bit.

I attempted to utilize this branch and encountered the following error:
reloading python 3.3 plugin move_tab
Traceback (most recent call last):
  File "/opt/sublime_text/Lib/python33/sublime_plugin.py", line 308, in reload_plugin
    m = importlib.import_module(modulename)
  File "./python3.3/importlib/__init__.py", line 90, in import_module
  File "<frozen importlib._bootstrap>", line 1584, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1565, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1532, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 584, in _check_name_wrapper
  File "<frozen importlib._bootstrap>", line 1022, in load_module
  File "<frozen importlib._bootstrap>", line 1003, in load_module
  File "<frozen importlib._bootstrap>", line 560, in module_for_loader_wrapper
  File "<frozen importlib._bootstrap>", line 853, in _load_module
  File "<frozen importlib._bootstrap>", line 980, in get_code
  File "<frozen importlib._bootstrap>", line 313, in _call_with_frames_removed
  File "/home/giovanni/.config/sublime-text/Packages/move_tab.py", line 22
    if not (view := self.window.active_view()):
                 ^
SyntaxError: invalid syntax

I am uncertain why my Sublime Text editor - Build 4169, appears to be using Python 3.3. I'm on Pop!_OS 22.04 LTS. Any insights or suggestions on resolving this issue would be greatly appreciated.

It's controlled by .python-version file in root of the package.
That said, assignment expressions are of little value here.