Cafe Menu's first step is frustrating

Describe the Issue
It took me an embarrassing amount of time to get this right without googling. We should not require the whole Doctype thing right off the bat imho.
If we require it, we should have a hint that is more explicit so people don't get stuck here.
For many people visiting /learn, they may skip straight to this project and we want them to have a smooth entry.

Affected Page
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-basic-css-by-building-a-cafe-menu/step-1
Your code

Expected behavior
It shouldn't be so frustrating
Screenshots
No response
System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

At a quick glance, it looks like most projects have campers build out the HTML boilplate starting with the doctype each time.
Here are some first steps from other projects
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-css-colors-by-building-a-set-of-colored-markers/step-1
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-html-forms-by-building-a-registration-form/step-1
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-the-css-box-model-by-building-a-rothko-painting/step-1
Personally, I vote to provide the HTML boilerplate for each project and have them add in the link for the styles sheet and write the code for the body.
Because normally, you would never write this on your own. You would just use the keyboard shortcuts in VS code(or whatever editor of choice) to generate that boilerplate for you. Or you would be working on project that has this setup already. So I am not really sure I see the point in having campers write it out each time. But I would love to hear from the rest of the team.
If we do decide to provide the HTML boilerplates for them, then the new first steps of the project would look like this:

Curious to hear thoughts from the rest of the team

<DOCTYPE html> is the foundation of html.
Boilerplate code this early in the certification makes it too easy, and does not instil good coding practice.
I'm for more explicit instructions, or hints.
Boilerplate code after the second or third project is okay.

Boilerplate code this early in the certification makes it too easy

That might actually be a good thing considering the activity I have seen on the forum around the first project. Campers might need an easier learning curve in the beginning.

I'm for more explicit instructions

Step 1 for the cafe menu could be changed to this essentially
As you learned in the last few steps of the Cat Photo App, there is a basic structure needed to start building your web page. Every HTML project should have a `DOCTYPE` declaration and `html` element. The `DOCTYPE` tells the browser which version of HTML the document is in. And the `html` element represents the root element which contains all other elements.

```html
<!DOCTYPE html>
<html lang="en">
<!--all other elements go here-->
</html>
```

Add the `<!DOCTYPE html>` tag, and an `html` element with a `lang` attribute of `en`.

Boilerplate code after the second or third project is okay.

I think one project to learn it (cat photo app) and one project for review(cafe menu) should suffice IMO. Because you would almost never write out a HTML boilerplate on the job. You would either join an existing project or work on a greenfield project  where you are probably using some sort of UI framework that generates the boilerplate for you.
Normally I am all for repetition for the sake of learning. But here I question how much repetition we need for boilerplate code, that you would never write out yourself anyway.

The issue I have seen most often for this step on the forum, is people not adding a closing </htm> tag. I think we could try to keep this as one step and have hints that are more granular and help guide better toward the complete boilerplate

Let's go with this update to the description and hints
# --description--

In this project, you will learn the basics of CSS(Cascading Style Sheets) by building a cafe menu. CSS is the language used to style an HTML document. It describes how HTML elements should be displayed on the screen.

As you learned in the last few steps of the Cat Photo App, there is a basic structure needed to start building your web page. Every HTML document should have a `DOCTYPE` declaration and `html` element. The `DOCTYPE` tells the browser which version of HTML the document is in. And the `html` element represents the root element which contains all other elements.

```html
<!DOCTYPE html>
<html lang="en">
<!--all other elements go here-->
</html>
```

Add the `<!DOCTYPE html>` tag, and an `html` element with a `lang` attribute of `en`.

# --hints--

You should have the `<!DOCTYPE html>` declaration.

```js
assert(code.match(/<!DOCTYPE html>/i));
```

You should have an opening `<html lang="en">` with the language set to english.

```js
assert(code.match(/<html\s+lang\s*=\s*('|")en\1\s*>/gi));
```

You should have a closing `</html>` tag.

```js
assert(code.match(/<\/html>/i));
```

This has been opened for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum
Files that need to be changed
https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/14-responsive-web-design-22/learn-basic-css-by-building-a-cafe-menu/5f33071498eb2472b87ddee4.md
Happy coding


package<EMAIL_ADDRESS>does not satisfy its siblings'

When pulling a fresh copy and doing a npm install i get the below error.
8/.nvm/versions/node/v4.5.0/bin/npm" "install"
npm ERR! node v4.5.0
npm ERR! npm  v2.15.9
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/nxb6488/git/react-redux-starter-kit/npm-debug.log

To resolve this I bumped the eslint-plugin-promise package to ^3.0.0

Fixed with https://github.com/davezuko/react-redux-starter-kit/commit/08de6a204b7b8d625c478a10d0ce1af50e490761. Thank you!


doc: fix up GKE install guide

This commit fixes the GKE install guide:

gcloud now requires to pass --zone or --region or fails. Update
the guide to use --zone to all gcloud commands that require it.
The set of pods in the cilium namespace is different now. Update the
sample list so that the reader does not get confused.
Add =true to --set nodeinit.restartPods as without specifying
=true, the Helm command fails.

Coverage increased (+0.002%) to 37.004% when pulling 0bc885651d576039656b0c108d042d63eb377da5 on pr/rolinh/doc-gke-install-1.8 into a7cddb0ecdf59128e70d8dbd748ab00a1c9544f5 on master.


Add DrawTarget adapter to perform automatic colour conversions

#440 introduces changes to make DrawTarget generic across colors. This is a useful feature, however in https://github.com/jamwaffles/embedded-graphics/pull/440#issuecomment-693431053 the point is raised that this may accidentally introduce slower automatic conversion if the wrong colour type is used.
The suggested solution is a DrawTarget adapter akin to TranslatedDrawTarget, etc, which is an opt-in target which can perform the potentially costly automatic conversion for use cases that need it.

IMO another advantage of this approach is that we can easily add different variants for color conversions that all use a similar API.
For example, e-g doesn't implement From<RgbXXX> for GrayX, because there are multiple ways of converting colors to grayscale (average of the RGB components, calculating luma, ...). We could later add specialized adapters for these conversion, in addition to the generic adapter that was suggested in the original comment and requires a From<OtherColor> impl.
A map type adapter, that takes a closure to convert from one color type to another, could also be a useful addition.


React to IntegrationTesting changes

Reaction to https://github.com/aspnet/Hosting/pull/1412.

@Tratcher are we allowed to merge this now?


Introduce a groupby attribute for correlation computation

This introduces a groupby parameter for mapping_problem.correlate() to evaluate Pearson/Spearmann correlation over groups of cells. I've also adapted tests slightly to cover this case.

Thanks for the review @giovp, incorporated all your suggestions, except for the groupby -> groups change, see comment above.

Great, thanks @selmanozleyen @giovp, merging this.

@giovp  I think the problem with linting is here for sure. I thought maybe it's a link checking error because of connection but it fails only after this branch (I rerun the checks on older PR's)

yeah I think the problem is something in the docs of the correlate method, not a linkcheck

It's from the warning. Since the -W flag is set it gives error when warning is issued. I removed the flag and it works locally https://www.sphinx-doc.org/en/master/man/sphinx-build.html


Backport mainline fixes

These commits are all from the original NihAV repo, added by the author after we made this cut-down fork.
The commits and the changes within each were trimmed to those that still make sense after our culling of 98% of the repo.
I'm assuming that our permission to relicense still holds for these parts.
They are mostly minor additions, fixes, and calming clippy.

Merging due to the fact that these are mainline changes from the original project author, and we haven't really reviewed the rest of it's code either. It also doesn't break anything.


Besu v23.7.1 does not synchronize with goerli

Description
I wanted to sync Goerli network with Besu v23.7.1, unfortunately the sync blocked 3 times on the block 0x928201 (9601537).

Frequency: Everytime with v23.7.1, tried with, X_CHECKPOINT and X_SNAP.
Logs (if a bug)

At the begining, no error:

We can see, Besu will download the pivot block 9601537 (Downloading world state from peers for pivot block 9601537).

After a few minutes, we have a lot of DNS Errors:

After ~6h of syncing, we have no more info in the logs:

And the RPC is not synced, the RPC return the same block height:
❯ curl -sX POST -H "Content-Type: application/json" https://***** --data '{"jsonrpc": "2.0", "id": 42, "method": "eth_blockNumber", "params": []}'
{"jsonrpc":"2.0","id":42,"result":"0x928201"}%

Versions (Add all that apply)

Software version: v23.7.1
Java version: 17.0.7
OS Name & Version:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.6 LTS"
NAME="Ubuntu"
VERSION="20.04.6 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.6 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

Kernel Version:

Linux devhub-rpc-server-02 5.4.0-153-generic #170-Ubuntu SMP Fri Jun 16 13:43:31 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Cloud VM, type, size: Hetzner Bare Metal
Consensus Client & Version if using Proof of Stake: Teku v23.6.1

Additional Information (Add any of the following or anything else that may be relevant)

System info - 6 CPU / 64 Go RAM / 2 To SSD NVMe

I'd also like to point out that version 23.7.1 is marked as a release on Github. However in the Besu version 23.7.1-dev-2bced4eb. What is the truth?

Hi there - thanks for the report. Can you provide logs from Teku as well?

@matkt Any thoughts on this issue? Do you think your PR https://github.com/hyperledger/besu/pull/5838 will help with this?

Hi!
Here are some logs from Teku:

(same logs at an other time)

are you did a checkpoint sync with teku ? I see 8137 remaining blocks. if your CL is not close to the head the besu sync will not work because we need to have a recent pivot block

Trying to reproduce this issue, I was able to sync Besu on Goerli with no issues with version 23.7.1.
@chichi13 What is the status from you side and had you a chance to test Karim's suggestion ?

close due to CL problem --> try a fresh checkpoint sync with Teku and see if this is able to resolve the issue.

Hey,
Sorry I didn't see your messages.
I think the problem came from the CL not being able to resync, but I haven't repeated the error since.
When I upgraded Besu to 23.4.4 everything worked normally again.


submodule naming: micc.logging

when running cli in eclipse logging and micc.logging conflict
confusing anyway
resolve by renaming micc.logging -> micc.logging_tools

fixed together with issue#2


Allow int sorting

https://github.com/oceanprotocol/oceandb-elasticsearch-driver/blob/develop/oceandb_elasticsearch_driver/plugin.py#L161
Any sort key is going to be mapped as text, and sorted as such.
Ex:   sort: [{ 'price.ocean': 'desc' }]

Fixed in #41
Sorting in the live deployment is fixed as well.


deploying live on ec2: handling video streaming port 8081

i got the demo to work on localhost, but would like to take it a step further and deploy it to a standard ec2 instance. installing was simple, but i'm a networking noob so i'm not familiar with managing ports. using http://www.lauradhamilton.com/how-to-set-up-a-nodejs-web-server-on-amazon-ec2 i got the page to load.
However, the video stream on port 8081 still needs handling. but i have no idea what needs to be done.
Does anyone know what i need to do to push the video stream to the player correctly?
i also posted the question to stackoverflow:
http://stackoverflow.com/questions/42891794/handling-multiple-ports-for-video-streaming-via-jsmpeg-on-ec2
ps: thanks for sharing such an intriguing project!

I'm not sure what the problem is, but the article seems to over-complicate things quite a bit. It's perfectly fine to allow access on port 80. No port forwarding needed. So you'll have to allow connections to your EC2 host on port 80 (for the web server), 8081 (for the incoming video stream) and 8082 (for the outgoing WebSocket connections).
Just start your Web Server on port 80: http-server -p 80.
Then start the websocket-relay: node websocket-relay yoursecret 8081 8082
Then send your video stream to your EC2 host on port 8081 and you should be able to see it in a browser.


Have a "backpack"

We should have our own backpack that people can temporarily store collections and resources in.
It should have easy "add all to collection" and "download all" buttons :package:
We can also try using the FileSystem API for more swag (API support across browsers is patchy though)

Does "backpack" feature have its own features?
I probably misunderstood, but I don't see much difference between this idea and collections. In Scratch, the difference between backpack and studio is significant, but this is OpenSprites. You still have to create a new, "special" collection just for backpack, but after that, it should be quick and easy.
PS: Is this the API you were talking about?

@Rumanti Not really, except how you see it...
Essentially, it's your own - private - collection that is hidden from view normally, and I'm assuming at the bottom right of the page(?), like Google Fonts, where you drag resources you want to download; then you press the download button to download all of them.
It's much more streamlined than just a collection.

Basically like the 'shopping cart' on Amazon, but instead of purchasing the items at the end of your spree, you download them.

Basically like the 'shopping cart' on Amazon, but instead of purchasing the items at the end of your session, you download them.

Yeah that's how I imagined it
It should also use localStorage event handlers to update across tabs :package:
And we could integrate it with the Scratch editor, pixie, and tosh :package:

I see. I feel ignorant now :P
^ btw love the idea of integrating OS with tosh, pixie, and more

And we could integrate it with the Scratch editor, pixie, and tosh

How'd we do that? Magic? :shipit:

If we use localStorage to handle it, we won't have to make a hidden collection, too :D

How'd we do that? Magic?

For Scratch we load the swf with a param for the sb2 file to open (post /collections/download with list of items, it gives you back the ID of a cached sb2, open a copy of the Scratch SWF with get /collections/download/id)
For pixie and tosh we probably need to do some modding :package:


Make to_s on OutputObject more descriptive

Currently it just returns the standard ruby to_s, which kinda sucks. I think it should probably be something like: <OutputObject identifier='Identifier'> or even <OutputObject(Identifier)>

This is needed for testing OutputObjects in specs.


Azure Monitor Agent

Hi there,
In the examples provided, how do you link the Azure Monitor Agent to a Log Analytics Workspace?  The documentation demonstrates that you can do this when using the legacy Log Analytics Agent by passing a WorkspaceId and WorkspaceKey to the agent, but doesn't demonstrate how this is achieved using the modern Azure Monitor Agent?

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

ID: baf82535-8a71-c604-5fef-a950c4a384ac
Version Independent ID: 9f1526c9-d772-3802-539a-c7b928716ff7
Content: Resource Manager template samples for agents - Azure Monitor
Content Source: articles/azure-monitor/agents/resource-manager-agent.md
Service: azure-monitor
Sub-service: agents
GitHub Login: @bwren
Microsoft Alias: bwren

@jamcguire
Thanks for your feedback! We will investigate and update as appropriate.

@jamcguire, thank you for the question. Please see Prerquisites which state that
To configure data collection for Azure Monitor Agent, you must also deploy Resource Manager template data collection rules and associations.
For Azure Monitor Agent, the association between source (VM), destination (Log Analytics) and the data to be collected (perf counter, event logs etc.) happens using the Data Collection Rule.

Hi there,
Thanks for your feedback, I've taken a look at the prerequisites now and it
leads me to this page
https://learn.microsoft.com/en-us/azure/azure-monitor/agents/resource-manager-data-collection-rules?tabs=bicep
which has an example of how to deploy an ARM template for a Data Collection
Rule.  But there is no example showing how this could be linked between a
VM and a Log Analytics Workspace.  Which would give me the equivalent
communication of the legacy agent.  Do you have an example of such a
connection please in JSON?
On Wed, Feb 15, 2023 at 6:46 AM Anurag Singh @.***>
wrote:

@jamcguire https://github.com/jamcguire, thank you for the question.
Please see Prerquisites
https://learn.microsoft.com/en-us/azure/azure-monitor/agents/resource-manager-agent?tabs=bicep#prerequisites
which state that
To configure data collection for Azure Monitor Agent, you must also
deploy Resource Manager template data collection rules and associations
https://learn.microsoft.com/en-us/azure/azure-monitor/agents/resource-manager-data-collection-rules.
For Azure Monitor Agent, the association between source (VM), destination
(Log Analytics) and the data to be collected (perf counter, event logs
etc.) happens using the Data Collection Rule
https://learn.microsoft.com/en-us/azure/azure-monitor/agents/data-collection-rule-azure-monitor-agent?tabs=portal#create-a-data-collection-rule
.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/105246#issuecomment-1430839799,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMIOLTBTLH5SCQZ37UMBFCTWXR3TJANCNFSM6AAAAAAU3WUVZU
.
You are receiving this because you were mentioned.Message ID:
@.***>

@jamcguire, thank you for the reply.
The link in your reply contains 2 sections - create the rule and create association between rule and VM.
The rule creation step is where the destination is defined.

Therefore, the overall steps is:

Create rule where "what to collect and where to store is mentioned - LA workspace"
Associate the rule with VM
Install AMA.

I hope this helps.

@jamcguire We will now proceed to close this thread as we have not heard back from you. If there are further questions regarding this matter, please tag me in your reply and reopen the issue. We will gladly continue the discussion.


Miss "Copy Direct Link to Blob Container" & "Set Public Access Level…" for one new created blob container

Storage Explorer Version: 1.8.1_20190530.1
Platform/OS: Linux Ubuntu/macOS High Sierra/Windows 10
Architecture: ia32/x64
Commit: 4359b6f0
Regression From: Previous release 1.8.1
Steps to reproduce:

Expand a non-ADLS Gen2 storage account -> Blob Containers.
Create a new blob container -> Check its context menu.

Expect Experience:
"Copy Direct Link to Blob Container" & "Set Public Access Level…" display on the context menu.

Actual Experience:
No "Copy Direct Link to Blob Container" & "Set Public Access Level…" display on the context menu.

More Info
These two actions display well after refreshing Blob Containers node

@v-xianya, can you confirm whether or not the Direct Link that which was copied as in the previous version worked or not? I found some cases where although the action was offered, the link that was put on the clipboard didn't work. So for those cases, I made the action no longer visible. I believe this is one of those cases. Thanks!

Hi @MRayermannMSFT, Thanks for your update.
We select "Copy Direct Link to Blob Container" for one new created blob container and paste the direct link to browser using the 1.8.1 release. It works well.
Could you share more info about those cases that the action no longer visible you've mentioned?

Ok so the cases I have are:

Direct link for a QA blob container that was originally from a Storage Account that was the child of a subscription. Example direct link: storageexplorer://v=1&resourcetype=Azure.BlobContainer&resourcename=1testdest100000
Direct link for a QA blob container that was originally from a Storage Account that was attached with name & key. Example direct link: storageexplorer://v=1&resourcetype=Azure.BlobContainer&resourcename=1millionblobs
Direct link for a QA blob container that was originally from a Storage Account that was attached via Connection String. Example direct link: storageexplorer://v=1&resourcetype=Azure.BlobContainer&resourcename=emptycontainer

Although all of those links open Storage Explorer, none of them result in Storage Explorer doing anything in the tree view.

Verified this issue on the build rel/1.9.0_20190626.4.
Miss "Copy Direct Link to Blob Container" for one new created blob container. So we re-open it.
More Info:
"Copy Direct Link to Blob Container" displays well for one new created file share/ queue/ table.

Fix merged into master.


Fix Grafana datasource for Jaeger.

Fixed the datasource URL for the Jaeger within Grafana configmap.

@philipz Please bump the patch version of the chart and then run "make generate-examples".


breaking change in struct ordering

Previously the struct used to be ordered like this:
-// StringFlag represents a flag that takes as string value
-type StringFlag struct {
-       Name   string
-       Value  string
-       Usage  string

Now it's ordered like this:
type StringFlag struct {
    Name        string
    Usage       string
    EnvVar      string
    FilePath    string
    Hidden      bool

This means if you had written:
x := StringFlag{"one", "two", "three"}

and updated the library version, you may have assumed the new field was added at the end, not that the fields had been rearranged.
(I say this because I did exactly that and broke clients that were deployed in the wild.)
In the future I recommend maintaining the struct order and adding new fields at the end, or requiring structs to use named parameters (there are tricks for requiring this).

@kb-equinox this all makes sense!

maintaining the struct order and adding new fields at the end

I'm wondering if there's some easy way to enforce this programmatically 🤔

You'd use a builder, or a NewXXX method that gains parameters and breaks at build time

@coilysiren @kb-equinox I am new to OSS and would like to try to contribute to this issue if it is a mere reordering of the struct fields if I understand it correctly.

While it's definitely unfortunate that real world code has had to break because of this change, I'm not sure that the assumption that struct fields will stay in order when new fields are added was ever safe to make.
From the Go 1 Compatibility Promise:

Struct literals. For the addition of features in later point releases, it may be necessary to add fields to exported structs in the API. Code that uses unkeyed struct literals (such as pkg.T{3, "x"}) to create values of these types would fail to compile after such a change. However, code that uses keyed literals (pkg.T{A: 3, B: "x"}) will continue to compile after such a change. We will update such data structures in a way that allows keyed struct literals to remain compatible, although unkeyed literals may fail to compile. (There are also more intricate cases involving nested data structures or interfaces, but they have the same resolution.) We therefore recommend that composite literals whose type is defined in a separate package should use the keyed notation.

Ref: https://golang.org/doc/go1compat
Two things here—

The recommendation by the Go authors is to not use unkeyed struct literals for types declared outside of the package. This is sound advice, and would have prevented the issue caused. There is also a vet warning related to this pattern (see: go tool vet help composites)
The Go standard library does not consider the kind of changes that were made here as part of the compatibility promise, and I don't think it's reasonable to assume that a 3rd party library should be holding itself to higher standards for backward compatibility than the standard library does.

@amoghrajesh I really appreciate the willingness to open up a contribution here. I think the challenges are that at this point, re-ordering the field names would break programs that made the same assumption in the past two years that was made as described in the original issue.
My recommendation here would actually be to take no action. Happy to discuss further if there's anything I'm missing here.

One thing you could do is eg
type StringFlag struct {
    _RequireNamedParameters struct{}
    Name        string
    Usage       string
    EnvVar      string
    FilePath    string
    Hidden      bool
}

The new field would require all callers to list the parameters instead of adding them implicitly.

I fear this may be a case of #wontfix. Please holler if you feel otherwise and would like to see action taken ❤


is this normal?

Required information

[ ] Mac model: iMac 2017 or 2019
[ ] macOS version: 10.15.7
[ ] Monitor setup: built in

Description of issue / Feature request
I am trying to reinstall this app yet it seems I am unable to delete all related files,
and com.apple.ScreenSaver.Engine.legacyScreenSaver keeps recreating itself inside of /Library/Containers
is this normal should I carry on? I have little experience with these things...

@3Dortal legacyScreenSaver is part of how modern macOS runs the "old style" (so called legacy, anything that ends with .saver instead of .appex) of screensavers, which includes all 3rd party screensavers, and most Apple's built in screensaver.
So that container will get recreated anyway, even if you don't use Aerial. See here at the bottom for more details on fully uninstalling/reinstalling : https://aerialscreensaver.github.io/installation.html

I see,
as I tried to clean everything the actual screensaver would still be there
no matter what I tried it seems its just part of macOS now I don't know exactly if its aerial or something else
I thought it might be connected guess ill need to try something else, any way thanks

I see,
as I tried to clean everything the actual screensaver would still be there
no matter what I tried it seems its just part of macOS now I don't know exactly if its aerial or something else
I thought it might be connected guess ill need to try something else, any way thanks

Ok maybe I wasn't clear but legacyScreenSaver.appex is part of macOS yes, and so is that container folder you are mentioning. If you delete it, it will be recreated next time you launch pretty much any screensaver.
What's happening is, since Catalina, macOS no longer launches screensavers like Aerial (or others) directly, they added a sandboxing mechanism and that's legacyScreenSaver.appex.
Does this make more sense ?


Added OrderInstructions message

@thehenrytsai could you remove payment instructions from quote.data.payin and quote.data.payout?
https://github.com/TBD54566975/tbdex/tree/main/specs/protocol#quote


Cannot copy an image in iPhone

Confirmed this phenomenon in Chrome and Safari
Environment

iOS: 15.5
Chrome: 102.0.5005.87
Safari

In development environment

Firefox 101.0.1 (64-bit) also gives a different kind of error.


Using an endpoint that returns the message and updating the HTML in client side

I've created a new Rest Controller that acts as a RestAPI. It returns the message "Hola estudiante" as a String inside the HttpResponse. This Controller is called from a new template that uses AXIOS (a JavaScript library) to make the GET petition. When the AXIOS function receives the response from the API, it sets the message as the content of an HTML paragraph.

PR accepted.


Test Neuropixel probe connection via GUI button without running workflow

It would be useful to have a button somewhere that tests the probe connection without running the workflow. It's a very common issue that the user has not seated the probe correctly and has to wait to run the workflow to find out.

Related to #19 and #123.


Refactor idea: type hinting

While i was going through the project files, i took notice that there is literally no use of type annotations in definitions of methods/functions. Therefore, i want to discuss your opinion on refactoring the codebase -> adding type hinting (no changes to existing docstrings, just adding type hints).
What is your opinion on this? If you would approve this i could do it myself.

The VMware team is hard at work on this! See some of the new ngclient PRs in particular 🙂 I'm sure they could use some help in this area.

i will check that out. thanks

@samuelgregorovic  I know the current work and plans are not visible as well as they should be -- sorry about that, we're trying to be better. We're very keen on static typing improvements and such (but with some caveats, see below).
In short:

There's a refactoring/rewrite effort: see the tuf/api/ directory (and tuf/ngclient/ once #1408 merges). We're hoping to make this code "the TUF source code" and deprecate the old tools over time.
the rest of the code is in what I'd describe as being in maintenance only mode -- nobody is against e.g. adding types there but the value is also a bit limited if no-one is working on that code...
there's a lot to do with the new code base though -- especially on making it more visible and accessible: tutorials, publishing docs on readthedocs, example code. But also  development like implementing various repository side tools and improving the client

If you want to discuss ideas  and happen to use slack, we're on CNCF slack: https://cloud-native.slack.com/archives/C01GT17AC5D

@jku thanks! will do


[Bug]: Text color formatting is not getting applied on Bold, Italic text of RTE

Is there an existing issue for this?

[X] I have searched the existing issues

Description
On changing text color of texts written in Bold, Italic or both are not getting changed to applied text color in RTE
Steps To Reproduce

Drag & Drop Rich text editor widget
Type anything on editor and make some words as Bold or Italic
Select all the words and change the color of the text
Observe that Bold, Italic words are still in Black color instead of Text color applied in formatting

Public Sample App
No response
Issue video log
https://www.loom.com/share/5efc96e749244442bb7f4c74659a2298
Version
Cloud / Production

Fixed in #17402 @chandannkumar can you verify and close?

This issue is fixed in #17402 (Tested & Verified)


install: Docker for Devito with OpenMP offload

This PR aims to provide a Dockerfile to install Devito with OpenMP Offload using CUDA 11.0 + Clang 13.

@italoaug do you have any plans with regards to this PR?

Is this PR still in Devito's roadmap

Would be nice to have a Dockerfile that deploys devito with openmp offloading support via clang, yeah

Superseeded in #1946


About this Repo

This repo is a hard-fork of tachiyomiorg/tachiyomi-extensions meant for reference only.
it includes all commits up to the 6. of January, 2024 (right after the removal of the MangaDex extension)
THIS REPOSITORY IS MEANT AS A ARCHIVE FOR FUTURE REFERENCE ONLY. DO NOT OPEN ISSUES OR PULL REQUESTS

for a non-archive version of this, see https://github.com/tachiyomi-extensions-org/tachiyomi-extensions


Cypress Test for gwa get

New command has been added, gwa get [operator], which retrieves a list of datasets, products or issuers from the API.
Example usage
$ gwa get datasets
$ gwa get datasets --json
$ gwa get datasets --yaml
$ gwa get issuers
$ gwa get products

The --json or --yaml return the selected format as string, so the user can pipe them to another function like writing to a file.

Hi @Jonesy  - Getting error with latest code in 'dev' branch while performing 'just build' to build CLI executable binary file. Could you please look into it?
Private Zenhub Image

Just pushed the fix, let me know if you still get any issues @nirajCITZ

@nirajCITZ added gwa get organizations to the list of possible get operations

Forgot to dd verification step for 'Verify "gwa get" for issuers'


Please link to https://qiskit.org/ecosystem/ionq/ in GitHub's About section

It is useful to have the link to the project docs on the GitHub home page for this repo.
To fix this, go to the "Code"/home page of the repo. Then click the wheel on the "about" section on the right. Set the website to https://qiskit.org/ecosystem/ionq/.

Thanks!

Bump @splch

Thanks! For some reason, the URL isn't clickable. Maybe it doesn't like the / at the end? I realize the other projects don't have that.

Ah, can try that out. I noticed the same but wasn't sure it was specific to us

Yup! Clickable now, that seems to have done the trick :)


Type Cycles can only refer to structs

IOW, when cycle points up the stack, it only refers to structs. This may be fine, but, for instance, it precludes modeling a tree as just a Set<Cycle<0>>.

Closing until there's a clear use case motivating pointing to anything other than struct


Escape markdown properly

When trying to input a backtick for example the insertion will fail.

Should be completely fixed now with:

c400f8d52e8d28fc0a56b298045ab98614ba1f60
9e874d19e56ded1832ce22fbc08d407f5d5219c7
07505a12925b2e03664416462cb2daa5bd0edb16
a1574abd9c0296913f8d6c0b4e0fa8ff118306b3


Apply struct alignment to promql package

Apply struct alignment with betteralign to the promql packages.

Hello from the bug-scrub!
To close out the discussion earlier, most of the changes are to keep pointers towards the beginning of objects, which reduces work done in the garbage-collector.
I am generally scared of a 400-line PR, but we could merge this, after fixing merge conflicts.


pagination:fix bug Pagination page number display problem

Please make sure these boxes are checked before submitting your PR, thank you!
#5852 bug fix:  no test case added(sorry, i don't know how to add test cases)

[x] Make sure you follow Element's contributing guide (中文 | English).
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

The currentPage should be 3 less than the total number of pages(pageCount) to display the NextMore button. not 2.


Add support for AngularJS

Nice Brackets plugin!
I just wish there were support for AngularJS.
There is a very good ESLint plugin for this: eslint-plugin-angular.

Thanks. Added eslint-plugin-angular to the latest version.

That was fast! Thank you.

Hey guys, how do you integrate eslint-plugin-angular?
I tried installing it within the Brackets\extensions\user\brackets-eslint directory, but the angular rules were being marked as undefined rules.
I also tried installed the plugin globally, but the same error persisted.
@hindsholm your help would be appreciated!

@kamikaz1k brackets-eslint should now pick it up from your project if you do:
npm install --save-dev eslint eslint-plugin-angular


Test against sqlite & postgres

This is built on #48, #49 (so ignore everything but the last commit). It tests against both postgres and sqlite. It adds a (currently unused) boolean settings called SEARCH which can be used to gate full text search and other features that require a db that supports needed features.
From HN (and myself!) there's a lot of demand for sqlite. Since the service currently seems to work fine with sqlite, might as well test against it until it doesn't.

I will have to ponder this one (and wait for the other PRs to merge before I can see a clean diff)!

Feel like rebasing this given all the changes in the last few days?


Grid: Relation over 2 vias produce weird results

What steps will reproduce the problem?
I have a grid with a column which has a anonymous function for its value-field. In this field, I access a relation of the given model.
Let me start by posting my needed relations for my "given" model projekt:
	public function getKooperationen() {
		return $this->hasMany( Kooperation::class, [ 'projekt_id' => 'id' ] );
	}

	public function getKooperationsPartner() {
		return $this->hasMany( Kooperationspartner::class, [ 'kooperation_id' => 'id' ] )->via( 'kooperationen' );
	}

	public function getExterneKooperationsPartner() {
		return $this->hasMany( MasterOrganisation::class, [ 'id' => 'organisation_id' ] )->via( 'kooperationsPartner' );
	}

So, the source Model is Projekt which has these relation definitions. When I call externeKooperationsPartner is will load this via kooperationsPartner and that will load via kooperationen.
So, the function for the column looks as follows:
                  'value' => function($model) {
                    $out = [];
                    $partners = $model->externeKooperationsPartner;
                          foreach ( $partners as $partner ) {
                             $out[] = $partner->name;
                    }
                    return implode("
", $out);
                 },

So, we assume, we have 3 projekt results for that whole grid. All of them have a specific MasterOrganisation::class but it is not always displayed!
The results looks like this:

But this is not true! Example: Company 19 is in ALL of these three results available! But externeKooperationsPartner offers no more data in this round.
If I go a level higher and use kooperationsPartner instead of externeKooperationsPartner:
			        'value' => function($model) {
				        $out = [];
				        $partners = $model->kooperationsPartner;
				        foreach ( $partners as $partner ) {
					        if($partner->organisation) {
						        $out[] = $partner->organisation->name;
					        }
				        }
				        return implode("
", $out);
			        },

I get:

which is the actual case (regardless of the sense that some are assigned multiple times :) ).
(if($partner->organisation) { = The ->organisation is a relation from the kooperationsPartner model which points to MasterOrganisation::class)
Am I using it wrong/Bad practice? DId I miss something?
Thanks in advance
What is the expected result?
The same result, but without my extra if($partner->organisation) {
What do you get instead?
See above
Additional info

Q
A

Yii version
<IP_ADDRESS>

PHP version
7.4.16

Operating system
Ubuntu 18.04

I guess this is because of the nature of this relation and the way Yii populates it as models. You could verify it by calling raw SQL built from the given methods and see the results. Most probably you will get duplicates, and these are removed when data is being populated as a model. The solution would be to craft the queries to meet the expectations like maybe adding specific on conditions or maybe just calling the relation tables directly instead of using via. Anyway, unless you can find something not working in Yii, we cannot really help here. I'm closing it, feel free to write here if anything new develops.


dns server

backend = redis
support A,AAAA, ALIAS, MX, ...

to deliver

build instructions
format of configuration used in redis

covered here https://github.com/threefoldtech/tf_gateway#dns-server

https://github.com/threefoldtech/tf_gateway#dns-server


Update node resolver

Node resolver was using obsolete 'resin' repository; update to use 'balenalib'.
Also included a whitespace fix for prettier so can run tests.

@klutchell , @dfunckt  This fix is simple. I rarely work in this area, so want to confirm I'm not missing any context that would affect the change. I'm scratching my head because for example the most recent tag for resin/amd64-node is 5 years ago. It seems like we would have noticed this error sooner.

@klutchell , @dfunckt This fix is simple. I rarely work in this area, so want to confirm I'm not missing any context that would affect the change. I'm scratching my head because the resin repository was deprecated 5 years ago. It seems like we would have noticed this error sooner.

We are optionally skipping that test, which is why we didn't notice it sooner. I expect that's actually WHY we are skipping that test.

I suggest we remove the .skip from this test to make sure the test is marked as required
https://github.com/balena-io-modules/balena-compose/blob/0d71e1c3820d0b992776936926bfc16b4d0d1f71/test/resolve/all.spec.ts#L312

This is the offending commit: https://github.com/balena-io-modules/resin-bundle-resolve/commit/938f5e3f168620b67f03f4a88ba12ba60ce72138

Thanks, I'll activate the test, confirm it has the expected result, and then self-approve.

I would be happy to review and approve once the test is re-enabled. No need to self-certify today :)

Reactivated the node project test. I had to update the node version to one available in the balenalib repository. Also I found that the result from querying Docker Hub might be undefined. The possibility of that error may have been the reason for skipping the test. Also, the test pretty consistently takes 40 sec., which also might be why the test was skipped.

Also I found that the result from querying Docker Hub might be undefined.

I suspect the test was skipped due to the undefined result. Does this fail the test? Do you think this is also affecting users in production (if anyone even deploys without Dockerfiles anymore)?


integration-tests container build fails, pipenv was removed from bookworm

What happened:
Build of the integration-tetst container fails with E: Unable to locate package pipenv
The package pipenv was removed from bookworm. The package is used in the integration-tests container to pin pip package versions.
https://tracker.debian.org/pkg/pipenv
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
Environment:

Tested as a workaround, to install pip and then use pip to install pipenv. This works but should probably only be a temporary fix until pipenv is back in bookworm.


docker exec does not wait on paused container

man docker-exec says:

If the container is paused, then the docker exec command will wait until the container is unpaused, and then run

But I get an error:

FATA[0000] Error response from daemon: Container distracted_lumiere is paused, unpause the container before exec

How to get the error:
$ docker run -d mongo:latest
9696a9b2d5726339a30c265e2587a11cd8fcb8f31a2419f9081583b3fb87b120
$ docker ps -a
CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS              PORTS               NAMES
9696a9b2d572        mongo:latest        "/entrypoint.sh mong   8 seconds ago       Up 7 seconds        27017/tcp           distracted_lumiere
$ docker pause distracted_lumiere
distracted_lumiere
$ docker ps -a
CONTAINER ID        IMAGE               COMMAND                CREATED             STATUS                   PORTS               NAMES
9696a9b2d572        mongo:latest        "/entrypoint.sh mong   33 seconds ago      Up 32 seconds (Paused)   27017/tcp           distracted_lumiere
$ docker exec
9696a9b2d572        distracted_lumiere
$ docker exec distracted_lumiere echo foo
FATA[0000] Error response from daemon: Container distracted_lumiere is paused, unpause the container before exec

Ubuntu 14.04
$ uname -a
Linux XXXXXXXX 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
$ docker version
Client version: 1.4.0
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 4595d4f
OS/Arch (client): linux/amd64
Server version: 1.4.0
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 4595d4f
$ docker -D info
Containers: 1
Images: 53
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Dirs: 55
Execution Driver: native-0.2
Kernel Version: 3.13.0-43-generic
Operating System: Ubuntu 14.04.1 LTS
CPUs: 4
Total Memory: 7.506 GiB
Name: XXXXXXXXXX
ID: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Debug mode (server): false
Debug mode (client): true
Fds: 17
Goroutines: 16
EventsListeners: 0
Init Path: /usr/bin/docker
Docker Root Dir: /var/lib/docker
WARNING: No swap limit support

@SvenDowideit The man pages are wrong, they should be changed as the implementation is the correct way to handle this situation.

this was fixed in #9356 and has been published.


Custom Preset + Watch Folder

Hello!
Thanks for all the work you do on this project. I was able to make the watch folder work for me (I think). However when I tried to include an argument for a custom preset and specifying the output file to be m4v, I couldn't get the watch folder to work anymore.
My arguments were:
-e AUTOMATED_CONVERSION_PRESET="My General/Plex"
-e AUTOMATED_CONVERSION_FORMAT="m4v"
Any help would be appreciated!

Did you check the container's log to see what's happening ?

Hello!
Thank you so much for responding. I was actually able to figure out what the issue was and resolve it, the watch folder is now working correctly - however, there is a new issue regarding custom presets and the watch folder. I felt like the files coming out were smaller than they should be, so I did a comparison with handbrake on my windows PC and this containerized handbrake. I created my custom preset identically to the preset used on Windows. The file was 22.5 GB. The Windows file came out to 2.76 GB, and the file that came out of the automated watch folder using the same preset was 1.94 GB. How would I go about troubleshooting this issue? I'm wondering if it's a syntax issue with defining the use of my custom preset, or if there's something else going on here.

To make sure the correct preset is used, you can look at log/hb/conversion.log, under the folder you mapped to /config.

Always nice when u post the solution to ur problem when u found it...


Position property descriptions

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Looks good @Xenulat3r, thanks for contributing to freeCodeCamp!


something error with importaddI and importadd

when the cursor is on junit or other package name not on the class,will get the error!
for example here my cursor is on springframework

then type F4

then type esc

will add this line
import cache.org.springframework;

it works well


Upgrade to Pulsar 3.0.0

Description
This PR upgrades Pulsar to 3.0.0 so as to make sure the current code works with that version and address some CVEs.
Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

No corresponding JIRA issue since it's just a dependency upgrade
Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

Agreed, I'll file a JIRA issue for this. Thanks!

thanks

/component-test pulsar


Add a license header template for new files of NetBeans modules

There are differences between current license header and existing license template for Apache 2.0. So we should have a new template for NetBeans.

Makes sense, good idea.

Exclude license-*.txt from rat, then, I'll merge this.

I think this can be merged, or should something be done still?

Merged. I've excluded license-*.txt from rat because they are user visible templates.


after update to 0.27.0 Edm.Decimal as string

Hello Hubert,
after update from 0.22.0 to 0.27.0 the type mapping is changed.
previously the type Edm.decimal was implemented as number in the typescript. in the new version it now becomes a string.
for testing purposes the repository https://github.com/bi-tm/odata2ts-test can be used, see entity HandlingUnit in file odata/ZppBdeSrvModel.ts.
in branch main with v0.27.0 : the property qty is typed as string .../main/odata/ZppBdeSrvModel.ts
in branch old with v0.22.0 : the property qty is typed as number. .../old/odata/ZppBdeSrvModel.ts
kindly
Torsten

Hi @bi-tm,
yeah that was a breaking change in the v2-to-v4-converter: here's the commit
Does it really make sense to convert Edm.Decimal to number? You could have a potential precision loss...

Ok, I've introduced this breaking change in the wake of developing the converter-ui5-v2: The V2 OData model of SAP doesn't convert Edm.Int64 or Edm.Decimal. I think I was a little helpless there...
I've found a better solution now:

by default, the converter-v2-to-v4 will transform both types to number
this is how V4 behaves anyway
I've added a bigNumberNoopConverter which overrides this behaviour and leaves the types to be string

this is used by the converter-ui5-v2

Please update @odata2ts/converter-v2-to-v4 to version 0.3.0.

@bi-tm if this works for you, then please close the ticket.
And the question from my side remains: Don't you have any concerns regarding precision loss? Or is this data type mapping just a little bit imprecise (like Edm.Double would be already enough but it's mapped to Edm.Decimal anyway)?


Inconsisten responses from scheduler

Hi,
I have setup the scheduler to identify the different phases of the day

unfortunatelly the scheduler response is

sometimes showing the right day phase
often listing all events / day-phases
often showing several events / day-phases

scheduler.json
please let me know if this is

a settings issue .. than please advise
a wrong use-case for this scheduler
or maybe a bug ;)

thanks for the help

Sorry, was a system issue and solved after a full redeploy


QIR Interop

Added functionality to compile a Qualtran Bloq to QIR
Added tests including the compilation of a QFTTextbook with 10 qubits
Added notebook showcasing how to use the Microsoft Resource Estimator with QIR generated from a QFTTextbook bloq with 20 qubits.

There is still much to do here on top of this PR. For example, right now, we don't support bloqs that allocate or deallocate new qubits. However, this PR provides working code that can convert a nontrivial bloq (QFT) and get resource estimates.

Samuel, do you know why the tests are failing? I think you need to recompile the dependencies after adding azure-quantum[qiskit] to the requirements file.

Samuel, do you know why the tests are failing? I think you need to recompile the dependencies after adding azure-quantum[qiskit] to the requirements file.

Yes, that is it. I just added it, so hopefully that check passes now.

Samuel, do you know why the tests are failing? I think you need to recompile the dependencies after adding azure-quantum[qiskit] to the requirements file.

Yes, that is it. I just added it, so hopefully that check passes now.

But actually, even after adding azure-quantum, the notebook won't run because there is not a valid "resource_id" specified. Obviously, we don't want to put in an actual resource ID here. So I think we have two options: 1) Have the code in the notebook in comments, and tell users to uncomment to run so that the notebook checker won't fail. 2) Disable the notebook checker on this notebook.

Samuel, do you know why the tests are failing? I think you need to recompile the dependencies after adding azure-quantum[qiskit] to the requirements file.

Yes, that is it. I just added it, so hopefully that check passes now.

@tanujkhattar But actually, even after adding azure-quantum, the notebook won't run because there is not a valid "resource_id" specified. Obviously, we don't want to put in an actual resource ID here. So I think we have two options: 1) Have the code in the notebook in comments, and tell users to uncomment to run so that the notebook checker won't fail. 2) Disable the notebook checker on this notebook.

We've encountered similar situations in Cirq in the past and we essentially skip testing such notebooks as part of the CI and commit them with the output stored.
@mpharrigan Do you have any thoughts here?

This is a great start, thanks a lot! I've left a round of comments but it's looking pretty good overall. I've proposed a bunch of improvements, which should hopefully make it easy to extend the conversion logic to more complicated bloqs as well.
Main feedback is that I think we can reuse a lot of the logic already implemented as part of Qualtran to Cirq conversion and then use the generated cirq objects to have a 1:1 mapping to QIR more easily since both QIR and Cirq expect a "flat list of qubits" style interface.
We can make this improvement as a follow-up PR though so this comment is not blocking. We can merge once some of the other nits are addressed.

Sounds good, I'll make the nit changes and then can focus on the restructuring of the code to use Qualtran -> Cirq functionality.

Closing this PR as it seems a Qualtran -> QIR conversion doesn't make the most sense right now. We will instead be creating a notebook showcasing how to use the open source Microsoft resource estimator with Qualtran programs.


Add "exports" to package.json for ESM module compatibility from Node

First of all, thanks for this package! This is going to be really useful for packages which rely on lodash that need to be exposed in both ESM and commonjs formats.
In order for the ESM import part to work from Node though, the package.json file needs an "exports" property (since "module" is only read by bundlers like webpack, rollup, or esbuild, but is never read by Node.js itself).
We basically want this .mjs file to work with the package:
// test.mjs
import { camelCase } from 'lodash-commonjs-es';

console.log(camelCase('hello world'));

But currently running this will give the following error:
$ node test.mjs

file:///home/test.mjs:1
import { camelCase } from 'lodash-commonjs-es';
         ^^^^^^^^^
SyntaxError: Named export 'camelCase' not found. The requested module 'lodash-commonjs-es' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'lodash-commonjs-es';
const { camelCase } = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:190:5)

Node.js v18.17.1

In order to get this to work correctly, we need "exports" in package.json (in addition to "main" and "module" for backwards compatibility), something like:
{
    "main": "dist/lodash.js",
    "types": "dist/lodash.d.ts",
    "module": "es/lodash.js",
    "exports": {
        ".": {
            "module": {
                "types": "./es/lodash.d.ts",
                "default": "./es/lodash.js"
            },
            "import": {
                "types": "./es/lodash.d.ts",
                "default": "./es/lodash.js"
            },
            "default": {
                "types": "./dist/lodash.d.ts",
                "default": "./dist/lodash.js"
            }
        }
    },
}

There's just one more trick that you need, which is to add a package.json file into the ./es directory with just one line of content:
{ "type": "module" }

And then the above test.mjs file should work :)

Created a PR :) https://github.com/iliubinskii/lodash-commonjs-es/pull/2


Shelelena/pandas improvements

Improvements in pandas DataFrame, DataFrameGroupBy and SeriesGroupBy

specify DataFrame.groupby
add DataFrameGroupBy.aggregate
adjust data type in DataFrame.__init__
add __getattr__ to get columns in DataFrame and DataFrameGroupBy
correct return type of DataFrameGroupBy.__getitem__
add some missing statistical methods to DataFrameGroupBy and SeriesGroupBy

In order to run tests, you should be able to do
./check_all.sh

(after you've installed black, mypy, flake8 and flake8-pyi)

Thanks for this

In order to run tests, you should be able to do
./check_all.sh

(after you've installed black, mypy, flake8 and flake8-pyi)

I've added changes made by black and removed np.ndarray specification. (Though it's possible to get it back later along with the Series specification)
I still get an error locally when using mypy tests:
.../env/lib/python3.8/site-packages/mypy/typeshed/stdlib/3/typing.pyi:675: error: Return type becomes "Union[bool, Any]" due to an unfollowed import
Found 1 error in 1 file (checked 3 source files)

What other dependencies do I need to avoid this?

I still get an error locally when using mypy tests:

That's an issue with the latest mypy version. You can ignore it or use mypy version 0.770. (The problem is that there is a mistake in the type stubs for the standard library. These type stubs are bundled together with mypy.)

@Shelelena I created a new release with your changes: 0.2.15. Thanks again for the PR! And thanks for fixing the existing issues as well! I really appreciate it.

@thomkeh I'm glad to be of service :)
Your library is very useful for me. I suppose I'll contribute a bit more :)

I've just read that your philosophy is not to recreate the documentation (sorry I didn't read it earlier). I think I overdid it with the groupby method. Don't you mind if I make it less verbose next time?

It's definitely completely fine if you don't include all methods and all possible arguments (only the most important ones). The task of writing type stubs for pandas is so huge that we have to accept imperfect type stubs, otherwise we will never make any progress at all. But, completely recreating the original code is also never wrong! If you're willing to do it, you're very welcome to ;)
However, there are cases where we have to deliberately deviate from the actual code. For example, a numpy ndarray can contain objects. But if we allow this, then all type checks become useless, because any value can be interpreted as object. So we made the decision to disallow objects in an ndarray.
But, yeah, it's definitely okay if you make it less verbose next time :)


Parser does not nests fail

We have this snippet
!:
%-  scan
    :*
    "\{2}"
    ;~
    (glue gaw)
    (ifix [(just '{') (just '}')] dem)
    ==
    ==

If you replace the `(just '}') -> '}' and similar for the left paren, the resulting code enters infinite loop.
!:
%-  scan
    :*
    "\{2}"
    ;~
    (glue gaw)
    (ifix ['{' '}'] dem)
    ==
    ==

I vaguely remember I reported something similar, but can't find the issue...

In general, parser interface seems very lax. I have hit infinite loop due to something as minor as adding additional argument by accident.
I do remember @cgyarvin saying something about it needing a rewrite though, so maybe treat this issue as visible and spiritual sign of this need ;-)


Support Go 1.20 in 1.17 branch

Linter is more strict now is why the test changes. Otherwise is just bumping test-only dependency
Please provide a description of this PR:

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio_release-1.17
d5a56b93536a2b2fd672fbd422a35b7e1e859479
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


docs: add interactive viewer for JSON logs to Readme

Add json-log-viewer to Bubble Tea in the Wild.

This looks so useful. Thank you for the PR!


untrustedFiles setting only working as expected from within VSCode

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.58.2 x64 System Install
OS Version: Windows 10 Professional x64 Version 1709

Steps to Reproduce:

Switch the VSCode setting security.workspace.trust.untrustedFiles to open. Leave all other settings for Workspace Trust to default.
Start VSCode. Don't open any workspaces. Instead, open an arbitrary single text file from within VSCode, e.g. by Ctrl+O. The file opens in Trusted Mode.
Close VSCode.
Open the same file as above, but directly, i.e. by double click, by context menu "Open with Code" or by Jumplist. The file opens in Restricted Mode.

Expected behavior: In step 4 above, the file should open in Trusted Mode.

@Hermjard this is not the intended behavior of the setting. When opening a new window with a file as a parameter, we can determine if the file is trusted and set the mode of the window on startup.
The setting only applies when a window is already trusted and you are opening an untrusted file in the same window.

@sbatten I think understand your approach: In the first scenario, you have first a (trusted) empty window, and from this known state, you open a single file, which then will also be trusted. Contrary to that, if you directly open a single file, you open it to VSCode in an "unknown state". Nevertheless, from a user perspective, the difference of these two ways of opening a single file are marginal, and therefore shouldn't behave differently, in my point of view.
What's more, the way, VSCode currently handles Workspace Trust, makes it at least cumbersome, to use VSCode as an ad hoc text editor and full featured code editor at the same time: Either you switch the complete Workspace Trust off, or you are confronted with the Trust Dialog everytime you double click on a readme.txt, or INI, or JSON, or CSV, or XML, or LOG etc. Also note, that there are plugins for these types of files, like Json Editor, XML, Txt Syntax, Rainbow CSV, Hex Editor, or Sort lines, to mention a few, which are mostly deactivated in restricted mode.


Package libudev was not found in the pkg-config search path.

Checklist

[X] I've looked through the issues and pull requests for similar reports

Describe your issue
Cross-compiling a binary which indirectly depends on libudev-sys v0.1.4 gives an error:
warning: profiles for the non root package will be ignored, specify profiles at the workspace root:
package:   /project/XXX/Cargo.toml
workspace: /project/Cargo.toml
   Compiling libc v0.2.147
   Compiling proc-macro2 v1.0.63
   Compiling quote v1.0.29
   Compiling memchr v2.5.0
   Compiling parking_lot_core v0.9.8
   Compiling futures-task v0.3.28
   Compiling syn v1.0.109
   Compiling nix v0.14.1
   Compiling rustix v0.38.3
   Compiling serde v1.0.164
   Compiling anyhow v1.0.71
   Compiling thiserror v1.0.40
   Compiling lock_api v0.4.10
   Compiling slab v0.4.8
   Compiling num-traits v0.2.15
   Compiling libudev-sys v0.1.4
   Compiling tokio v1.29.1
   Compiling async-trait v0.1.72
   Compiling serde_json v1.0.99
error: failed to run custom build command for `libudev-sys v0.1.4`

Caused by:
  process didn't exit successfully: `/target/release/build/libudev-sys-f4d656869383b154/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-env-changed=LIBUDEV_NO_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG_ALLOW_CROSS_aarch64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_ALLOW_CROSS_aarch64_unknown_linux_gnu
  cargo:rerun-if-env-changed=TARGET_PKG_CONFIG_ALLOW_CROSS
  cargo:rerun-if-env-changed=PKG_CONFIG_ALLOW_CROSS
  cargo:rerun-if-env-changed=PKG_CONFIG_aarch64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_aarch64_unknown_linux_gnu
  cargo:rerun-if-env-changed=TARGET_PKG_CONFIG
  cargo:rerun-if-env-changed=PKG_CONFIG
  cargo:rerun-if-env-changed=LIBUDEV_STATIC
  cargo:rerun-if-env-changed=LIBUDEV_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_STATIC
  cargo:rerun-if-env-changed=PKG_CONFIG_ALL_DYNAMIC
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH_aarch64_unknown_linux_gnu
  cargo:rerun-if-env-changed=TARGET_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_aarch64_unknown_linux_gnu
  cargo:rerun-if-env-changed=TARGET_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_aarch64_unknown_linux_gnu
  cargo:rerun-if-env-changed=TARGET_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR

  --- stderr
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: "`PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=\"1\" PKG_CONFIG_ALLOW_SYSTEM_LIBS=\"1\" PKG_CONFIG_PATH=\"/usr/lib/aarch64-linux-gnu/pkgconfig/:\" \"pkg-config\" \"--libs\" \"--cflags\" \"libudev\"` did not exit successfully: exit status: 1\nerror: could not find system library 'libudev' required by the 'libudev-sys' crate\n\n--- stderr\nPackage libudev was not found in the pkg-config search path.\nPerhaps you should add the directory containing `libudev.pc'\nto the PKG_CONFIG_PATH environment variable\nNo package 'libudev' found\n"', /cargo/registry/src/index.crates.io-6f17d22bba15001f/libudev-sys-0.1.4/build.rs:38:41
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...

What target(s) are you cross-compiling for?
aarch64-unknown-linux-gnu
Which operating system is the host (e.g computer cross is on) running?

[ ] macOS
[X] Windows
[x] Linux / BSD
[ ] other OS (specify in description)

What architecture is the host?

[X] x86_64 / AMD64
[ ] arm32
[ ] arm64 (including Mac M1)

What container engine is cross using?

[ ] docker
[X] podman
[ ] other container engine (specify in description)

cross version
0.2.5
Example
No response
Additional information / notes
No response

You need to install libudev inside the container for aarch64 using pre-exec hooks.

this should solve your issue. See also the wiki
# Cross.toml
[target.aarch64-unknown-linux-gnu]
pre-build = [
    "dpkg --add-architecture $CROSS_DEB_ARCH",
    "apt-get update && apt-get install --assume-yes ",
    "apt-get update && apt-get install -y pkg-config libudev-dev:$CROSS_DEB_ARCH"
]

Add -v to the command to see what its doing, i suspect its docker buildx that is stalling


add support Silverstripe

It would be great to see this happen. Is there anyway I can contribute to help move this along?

@jacobcarrington take a look at other Pull Requests and also take a look at https://github.com/Glavin001/atom-beautify/blob/master/docs/add-languages-and-beautifiers.md 😃

@Glavin001 thanks for pointing me in the right direction. I'll give you guys a PR or an update next week.

Disregard the previous comment.

any news on this?


[refactor][test] Move assert equals and retry to a base class

Motivation
Move assert equals and retry to a base class.
Documentation
Need to update docs?

[ ] doc-required
[x] no-need-doc
[ ] doc

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

@Demogorgon314 A better approach would be to remove retryStrategically completely, as I did in #14518

There was a similar discussion about the desire to replace retryStrategically with Awailibility in https://github.com/apache/pulsar/pull/14373#issuecomment-1055500489 .


Application of SMT for system identification with series blocks such as the Hammerstein-Wiener structure

I have a simple question: is it possible to apply your tool for surrogate models with two series blocks such as Hammerstein-Wiener structure? If so, your guidance would be much appreciated.

Actually, as far as I know, we have no experience for such use, so maybe you will tell us... :eyes:


New exception type for kie server http related errors

To allow clients to better handle the different type of errors that could be thrown while executing http requests to the Kie Server.

@mswiderski, created this to allow me to handle the different errors on the UI like unauthorized, etc. That way I can display specific messages based on the different error codes.

jenkins retest this


Uncaught ReferenceError: global is not defined

When trying to run with the latest Cloudflare Pages adapter template the wrangler cli won't start due to the following error:
service core:user:worker: Uncaught ReferenceError: global is not defined
  at oqu69tjsd1.js:57552:18 in singleton
  at oqu69tjsd1.js:57555:5 in node_modules/remix-development-tools/dist/index.cjs
  at oqu69tjsd1.js:82:50
  at oqu69tjsd1.js:62684:26
X [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.

Steps to reproduce

Start a new remix project using Cloudflare Pages adapter npx create-remix --template remix-run/remix/templates/cloudflare-pages
Install and configure RDT yarn add remix-development-tools -D
Start the project with yarn dev

Environment information
- node: 20.8.0
- yarn: 1.22.19
- remix: 2.1.0
- remix-development-tools: 3.2.2
- wrangler: 3.1.1
- windows: 11

Possible Causes
Since wrangler run in another JavaScript runtime that is not node and since the singleton function uses the global object that is not available in the Cloudflare runtime so its throws an error.
https://github.com/Code-Forge-Net/Remix-Dev-Tools/blob/50d55572cde95f6514d0f1cccb184cc01575632c/src/dev-server/singleton.ts#L6

@arielvieira Thank you so much for this report, the issue really is in the fact that RDT weren't made to run in serverless environments and the idea was to run them locally only, I plan to improve this for cloudflare by probably switching over to web standard apis instead of web sockets, also will need to figure something out for singletons as you pointed out. But this is not a straightforward process and I need to test a lot of stuff out. I am actively exploring bringing RDT to every environment without issues

@AlemTuzlak I had the same issue while upgrading to<EMAIL_ADDRESS>and using vite. I had to patch global with globalThis (same as the remember lib) and everything is working ok. BTW, I'm not using Cloudflare runtime, just plain Node.js.
/cc @arielvieira

I guess I will create a PR that resolves this issue separately, already fixed it on another PR so won't take long

But this still won't resolve the issue with cloudflare


Fix handling of larger messages in ockam_node

Currently, we don't handle messages above a certain size correctly in the rust https://github.com/ockam-network/ockam/blob/bbb2f85bbb561095497b701b50e8e005f301b518/implementations/rust/ockam/ockam_node/src/parser.rs#L17
This doesn't correctly implement the BARE variable length integer scheme described in https://www.ietf.org/archive/id/draft-devault-bare-01.txt:

Each octet of the encoded value has the most-significant bit set, except for the last octet.  The remaining bits are the integer value in 7-bit groups, least-significant first.

(Note that this means the value we can't be higher than is 127, not 255 as mentioned in the linked source, because of how the encoding works — if it were 128 or larger, the top bit would be set, meaning we would only be supposed to use the bottom 7 from this octet, and check the next one for the rest.)
It's possible this is the cause of some of the errors that we're seeing in #1624 (it seems somewhat surprising to me that we wouldn't even have "in-order for the most part in practice", but I could be mistaken or even misunderstanding what's being described). Either way, we should fix it.
It's possible this can be done by just using serde_bare. Not sure. If not, the varint scheme isn't that complex.

Sounds interesting. Can I be assigned this?


Some lineBreak rules related to ClassDeclaration MethodDefinition ignored

Many rules related to ClassDeclaration and MethodDefinition seem to be ignored. I discovered this while trying to automate this transformation:
class Awesome {

  awesomeMethod() {
    // things
  }
+
}

Some of the things I tried include:
lineBreak.before.ClassDeclarationClosing = 2
lineBreak.before.ClassDeclarationClosingBrace = 2
lineBreak.after.MethodDefinition = 2
lineBreak.after.MethodDefinitionClosing = 2
lineBreak.after.MethodDefinitionClosingBrace = 2

These are working fine (but solve unrelated problems):
lineBreak.before.ClassDeclaration = 2
lineBreak.before.MethodDefinition = 2
whiteSpace.after.MethodDefinition = 2 // Can test this by adding a semicolon after the MethodDefinition

TL;DR; the order that things are processed affects the outcome drastically, many of the supported options conflicts with each other... we should probably add support for MethodDefinitionClosingBrace
also, ClassDeclarationClosingBrace should actually be ClassClosingBrace since we use the same setting for ClassDeclaration and ClassExpression

overview of how transform works and conflicts:
the transform starts from the leaf nodes and moves down the tree - that gives us the option to undo any undesired line break/space inserted by the child elements, this is important since we actually need to add/remove line breaks before inserting any white spaces or indentation; by starting from leaf nodes we can do line breaks and white spaces in the same pass...
we also add the lineBreak.[before|after].MethodDefinition before calling the hook for MethodDefinition - this is done on purpose, to allow the hook itself to undo any conflicting change - maybe we should also change this behavior, and do the automatic line breaks after the hook.format call... But the MethodDefinition.value in this case is actually a FunctionExpression - you would need to target the FunctionExpressionClosingBrace since we don't support MethodDefinitionClosingBrace (which we probably should)
protip: best way to find supported options is to open the hooks files and look for the limit(Before|After)? calls, also use astexplorer

this will be doable on the next version of esformatter!
{
  "lineBreak": {
    "before": {
      "MethodDefinition": 3
    },
    "after": {
      "MethodDefinitionClosingBrace": 3
    }
  }
}

please note that for some weird reason the lineBreak.after.MethodDefinition still doesn't work as expected for the last MethodDefinition in the class... so I removed it from the default settings and added the lineBreak.after.MethodDefinitionClosingBrace = ">= 1" instead.


Sequential semantics of async DisposeResources

const d = new AsyncDisposableStack();
d.defer(async () => console.log(44));
d.defer(async () => console.log(43));
d.defer(() => new Promise(resolve => setTimeout(() => {
  console.log(42);
  resolve();
}, 1e4)));
await d.disposeAsync();
// only after 10 seconds: 42, 43, 44

That looks strange - why are some resources that can be disposed immediately should wait for something if it can be done in parallel? In case of errors, the tree can be built in the end. However, yes, here is stack in the name...

After rereading README, I see that this order can be helpful then some resources should be disposed in a custom order. However, in this case, it also could be helpful a container where disposing can be done in parallel.

After rereading README, I see that this order can be helpful then some resources should be disposed in a custom order. However, in this case, it also could be helpful an alternative container where disposing can be done in parallel.

In this case, I believe the core API should promote the more reliable case and match the behavior of using/async using. When working with multiple resources, these resources often have dependencies on one another. To ensure proper ordering, these dependencies likely need to be properly disposed in reverse order, and each resource should be fully disposed before the resource it depends on is disposed to avoid errors and/or deadlocks. As such, the current approach is the most reliable and safest.
Whether or not async resources can be safely disposed in parallel is an optimization decision that only the user can make.
In an effort to limit the scope of the proposal, we could consider a follow-on proposal to allow for parallel cleanup, but I don't think it meets the bar for the MVP.
A follow-on proposal or library could, for example, define a ParallelAsyncDisposableStack with a similar API to AsyncDisposableStack, except that each [Symbol.asyncDispose]() is called and passed to Promise.all() before awaiting. This might allow you to compose both serial and parallel disposal bases on your specific needs or specific optimizations:
const serial = new AsyncDisposableStack();
serial.defer(async () => console.log(44));

const parallel = serial.use(new ParallelAsyncDisposableStack());
parallel.defer(async () => console.log(43));
parallel.defer(async () => {
  await new Promise(resolve => setTimeout(resolve, 100));
  console.log(42);
});

serial.defer(async () => {
  await new Promise(resolve => setTimeout(resolve, 100));
  console.log(41);
});

await serial.disposeAsync();
// waits 100ms
// prints: 41
// prints: 43
// waits 100ms
// prints: 42
// prints: 44

I think that there can be added an option, for example,
new AsyncDisposableStack({ parallel: true });


Cluster name

Issue #199 #209 #210 , if available:
Description of changes:

Allow users to pass the cluster name
Allow users to pass the KMS Key ARN for EKS Cluster K8s Secrets
Fix for Kics Scan

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Looks good but there are a number of action warning son the PR. Should we address?

Those are the warnings that KICS reported on our repo. We have addressed all the Terraform and AWS related warnings.
The current outstanding warnings are mostly with Kuberentes and some are actual defects with KICS itself.
We don't have anything that is critical to address.


OIDC issuer should return metadata regarding its identity

Hi.
I have been reading the Solid-OIDC and Solid-OIDC Primer specifications and I don't find any information regarding the solid:oidcIssuer information that should be publicly available.
I think it would make sense to specify that a request made to the solid:oidcIssuer URI should return information on the identity of the issuer, e.g, the entity responsible for the domain, the entity responsible for hosting, contact information, privacy policy, terms & conditions, what data is necessary to create a WebID (email account,...) and so on.

OIDC defines OP metadata in https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata

Thanks for the reply @elf-pavlik
Is there a direct mapping between the terms in OP metadata spec and the ones in the Solid OIDC vocab?
I can guess a few, but it would be nice to have this mapping explicitly written, for instance in the Appendix A of the Solid-OIDC spec.

Is there a direct mapping between the terms in OP metadata spec and the ones in the Solid OIDC vocab?

Only partially, and there, the purpose was constrained by a need to represent a client identifier document as JSON-LD.
The discussion related to #199 (using the OpenID Federation specification) would potentially remove the need for this JSON-LD mapping entirely.
Is there a particular reason you need OAuth2/OpenID Connect terms explicitly defined as IRIs?

Is there a particular reason you need OAuth2/OpenID Connect terms explicitly defined as IRIs?

All entities involved in the Solid ecosystem, including identity providers, should provide at least basic information regarding their identity and contact information if they want to be compliant with data protection regulations. While is not the job of the Solid specs to describe/enforce this, at least a mention to it (maybe in the Privacy Considerations section of the specs?) should be made.

The issuer entity already has a URI. This is encoded as the iss claim in an ID Token and as the issuer property in the OpenID Metadata resource. From that URI, an OAuth2/OpenID client can discover additional data, such as the terms of use, contact information, privacy policy, etc, as per normal OIDC discovery (i.e. append .well-known/openid-configuration)
My earlier question was more centered around why expressing (for example) grant_types_supported or subject_types_supported as IRIs would be required?


Examples of Paging and Sorting for relevant endpoints.

I think an example of how one would achieve paging and sorting using this template would be beneficial to those using it.
Maybe this belongs in https://github.com/ardalis/ApiEndpoints?  Not quite sure.

Maybe something this this?
public class ListProjectRequest
{
    public const string ROUTE = "/Project";

    public string BuildRoute(int page, int pageSize)
    {
        return $"{ROUTE}?page={page}&pageSize={pageSize}";
    }

    [FromQuery(Name = "page")]
    public int Page { get; set; }

    [FromQuery(Name = "pageSize")]
    public int PageSize { get; set; } = 20;
}

This certainly isn't enough as this info needs to make it's way to a paging aware Specification

Paging seems to be relatively simple, and I've passed the above example request to an appropriate Specification.   If desired, I can build a PR that shows this to include in the template.
Turning attention to Sorting however... I'm curious as to how that would be achieved.  Having a query parameter which represents the order definition using ODATA seems to be an option however I'm unsure how to turn the ODATA representation into a LINQ expression and pass that down to the Specification.
@ardalis does the Specification framework allow for OData?  Supporting all of that ODATA allows (Select, Filter, Expand etc...) feels contrary to Specifications, but supporting the 'OrderBy' subset of the standard feels like it deserves consideration.
Supporting ODATA's orderby feature feels like a more consistent implementation rather than handcrafting bespoke sorting options into each request.
Thoughts?


ci: remove code coverage jobs

This PR is a proposal to remove the failing code coverage jobs in order to get the CI back to green.
The attempts in #6842 and #6850 to fix those jobs failed so far and for me it is not foreseeable when we will be able to fix them.

ok, let's do it until we have a real fix for this


Abnegation

Add all the definitions of  Abnegation in a file named Abnegation.json in folder 6
Refer CONTRIBUTING.md for more details on how to contribute.
Comment the words you'll be adding if you're are working on this issue to avoid conflicts.
Add reference to this issue i.e Issue # in your pull request description.

I an working on this.


[FEATURE] Settings to set tokens for message history used

This PR consists of 2 parts:

Frontend: Create UI in settings general menu to allow users to explicitly set amount of last characters used in current conversation to set how many will be used to process a new answer. Basically a little input field. Add it to the API keys dropdown too.
Backend: add parameters to /api/answer and /stream to include those limits for history of messages. Also add it to the /create api key endpoint.

Acceptance Criteria

[ ] Scenario: User can set token length for message history in settings

Given the user is in the settings general menu
When the user inputs a value for the token length
Then the token length is saved and used for processing new answers

[ ] Scenario: Backend API endpoints accept token length parameters

Given the user is using the API endpoints for answering and streaming messages
When the user includes the token length parameter in the request
Then the backend processes the request with the specified token length

[ ] Scenario: Token length is applied to API key creation

Given the user is creating a new API key
When the user inputs the desired token length
Then the API key is generated with the specified token length for message history processing

@dartpain can you assign me this issue


[ROS] Interact with ROS using ROSBridge

http://wiki.ros.org/rosbridge_suite
https://github.com/rctoris/jrosbridge
https://github.com/h2r/java_rosbridge

It is not possible to install directly on RaspberryPi.

sudo apt-get install ros-kinetic-rosbridge-server

jabrena@roshost:~$ source /opt/ros/kinetic/setup.bash
jabrena@roshost:~$ roslaunch rosbridge_server rosbridge_websocket.launch
... logging to /home/jabrena/.ros/log/2dbc16bc-6734-11e7-9502-78dd08bd5dfa/roslaunch-roshost-16350.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://roshost:41757/

SUMMARY
========

PARAMETERS
 * /rosapi/params_glob: [*]
 * /rosapi/services_glob: [*]
 * /rosapi/topics_glob: [*]
 * /rosbridge_websocket/address:
 * /rosbridge_websocket/authenticate: False
 * /rosbridge_websocket/delay_between_messages: 0
 * /rosbridge_websocket/fragment_timeout: 600
 * /rosbridge_websocket/max_message_size: None
 * /rosbridge_websocket/params_glob: [*]
 * /rosbridge_websocket/port: 9090
 * /rosbridge_websocket/retry_startup_delay: 5
 * /rosbridge_websocket/services_glob: [*]
 * /rosbridge_websocket/topics_glob: [*]
 * /rosdistro: kinetic
 * /rosversion: 1.12.7

NODES
  /
    rosapi (rosapi/rosapi_node)
    rosbridge_websocket (rosbridge_server/rosbridge_websocket)

auto-starting new master
process[master]: started with pid [16361]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 2dbc16bc-6734-11e7-9502-78dd08bd5dfa
process[rosout-1]: started with pid [16374]
started core service [/rosout]
process[rosbridge_websocket-2]: started with pid [16386]
process[rosapi-3]: started with pid [16392]
registered capabilities (classes):
 - rosbridge_library.capabilities.call_service.CallService
 - rosbridge_library.capabilities.advertise.Advertise
 - rosbridge_library.capabilities.publish.Publish
 - rosbridge_library.capabilities.subscribe.Subscribe
 - <class 'rosbridge_library.capabilities.defragmentation.Defragment'>
 - rosbridge_library.capabilities.advertise_service.AdvertiseService
 - rosbridge_library.capabilities.service_response.ServiceResponse
 - rosbridge_library.capabilities.unadvertise_service.UnadvertiseService
[INFO] [1499885950.446944]: Rosbridge WebSocket server started on port 9090


*.csproj matches more items than expected

Given a dotnet workspace/folder layout, usually intermediate output of the compiler is written in the workspace tree.
project.csproj
obj/project.csprojAssemblyReference.cache

With a query of *.csproj, it matches both the csproj and the csproj.cache.
The expected behaviour would be to either match just *.csproj, or have a way to signal end of string, like *.csproj$.

this is fixed now in the latest version (0.5.0)


Improve timezone.utc fixer to reuse existing datetime imports

This doesn't seem to work with imports that use parenthesis. This test currently fails.
def test_extend_datetime_multi_import():
    check_transformed(
        """\
        from datetime import (
            datetime, timedelta
        )
        from django.utils.timezone import utc
        do_a_thing(utc)
        """,
        """\
        from datetime import (
            datetime, timedelta, timezone
        )
        do_a_thing(timezone.utc)
        """,
        settings,
    )

>       assert fixed == dedented_after
E       AssertionError: assert 'from datetim...mezone.utc)\n' == 'from datetim...mezone.utc)\n'
E         Skipping 36 identical leading characters in diff, use -v to show
E         -  timedelta, timezone
E         - )
E         +  timedelta
E         + ), timezone
E           do_a_thing(timezone.utc)

How would we handle something like:
from datetime import timezone
print(timezone.now())
print(timezone.utc)

currently it rewritten to
from datetime import timezone
print(timezone.now())
print(timezone.utc)

what would break the timezone.now() implementation

Thank you for your checks.

This doesn't seem to work with imports that use parenthesis. This test currently fails.

Brilliant.

How would we handle something like:

You're right, the current code assumes that timezone is used only for utc, which is flawed.  I think we can simply detect any use of timezone.<not-utc as a sign to leave the import.


Renamed ide related crates

This PR will resolve issue #7526 .

Note that you'll also have to rename the directories (git mv should work) and update any other references to them (in Cargo.toml files, docs etc.).
If you have Rust installed, try making cargo check pass first, then try cargo test.

This was done in #7759


Generate docs for different versions (Version: 2.2.0)

Summary
In #889 we introduced generation and upload of doxygen docs to gh-pages.
However we are only generating and uploading develop docs atm.
There should be docs for each (new) release and for latest develop.
Release docs are generated and published for each release/x.y.z that is tagged (the tag is used as the docs version).
Motivation
It may be valuable to be able to see docs as they were for a specific released version. Not to mention having latest develop docs always up to date.
Solution
Implement a workflow that can do both develop and release docs.

After thinking some more, we decided it's not actually that useful in the current situation. So instead, let's remove any release/* mentions from relevant workflows/actions and only generate and deploy documentation on PRs merged to develop.


[feature] Zoom-in & Zoom-out

Can you add Zoom-in & Zoom-out in Editor Code ?
This feature is not present , it is tiring when watching the source-code and causes eye strain
Very very important feature  👍

@skylot I am unable to use CTRL +, CMD +, CTRL Mouse Wheel Up/Down or CMD Mouse Wheel Up/Down.
Setup:

JADX 1.4.7 (brew install jadx)
MacOS 13.4.1


PLEASE make all subsequent versions of Langchain backwards compatible!!!

Feature request
Example of what NOT to do:
https://github.com/langchain-ai/langchain/issues/12507
Langchain, PLEASE stop doing this. PLEASE make all your updates backwards compatible. As it is, if you keep making changes like moving modules around, existing scripts break with every new update of Langchain.
Motivation
It is so frustrating to have to try and guess which version of Langchain will actually work with my code.
Your contribution
Just stop moving modules around.  You cause way more harm than good when you do that, because tutorials for Langchain have to be rewritten and new versions of Langchain are not compatible with Langchain code written just a few months ago.

Responded in original issue, but this was not intentional and we'll add better testing to ensure things like this dont happen.
Thanks for flagging, and if it does happen again please let us know.


SC2262 (warning): This alias can't be defined and used in the same parsing unit.

Fix alias issue per https://github.com/gavinuhma/checksum.sh/pull/2#issuecomment-1295420677

Fixed by ae3c986eab0d811c579b03e0489d6d6cc62b2813


4-bit or higher?

Have you conducted evaluations on the effects of quantization of 4 bits or higher?

Yes, our method is generally effective.

@DD-DuDa
For the main results of the paper, have you ever done any experiments for w4_gs128?

Yeah.

@DD-DuDa
Any performance details can be shared which are not in ther paper?


[SPARK-42949][SQL] Simplify code for NAAJ

What changes were proposed in this pull request?

Reuse code of streamSideKeyGenerator() in NAAJ.
Why are the changes needed?

Reuse code and improve code readability.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Passing CI.

cc @ulysses-you @cloud-fan

lgtm

thanks, merging to master!

thanks, merging to master!


__cfduid key also used by Marketo

Platform

WebExtension (Google Chrome)

Describe the bug
Found instance where __cfduid was thought to be Cloudflare but was actually a Marketo cookie. (image attached)

Expected behavior
Determine the 'domain' string further to verify which platform is pushing that cookie.

Marketo sits behind Cloudflare.

I believe the issues has to do with 1st party and 3rd party cookies. If a cookie is being placed by another service that isn't the domain being detected, then should it be accounted for or not? For example, we could detect Marketo through JS objects or scripts, and not by the cookie being placed by an external script.

Actually, I see that based on the latest update to the code, it's now using the chrome.cookies object, and when we pass in the domain attribute that matches the hostname, it also includes subdomains.
https://developer.chrome.com/extensions/cookies#method-getAll

string
(optional) domain
Restricts the retrieved cookies to those whose domains match or are subdomains of this one.

It looks like in my latest test, the CloudFlare cookie is actually being set by a subdomain, which is a CNAME alias for a Marketo path, so this actually makes a little sense now...
Cookies on Pantheon.io
Includes subdomain, learn.pantheon.io

Pantheon subdomain
You can see the learn.pantheon.io subdomain pointed to a Marketo root landing page path.


Require at least version 3 of sprockets-rails

Please see https://github.com/fphilipe/premailer-rails/issues/211
I have required at least version 3 of sprockets-rails. Since version 3 of sprockets-rails support for version 4 of sprockets was added. The Sprockets::Manifest#find_sources method was only added in version 4 of sprockets (see this commit: https://github.com/rails/sprockets/commit/5785fd9d41f49f7763595d57908ce34e8f92e585)

Sprockets isn't a hard dependency and I'd like to keep it that way.
What was the motivation for this? Maybe we can address this differently.


drop fmt from vcpkg.json

seems like this is the only trace of fmtlib in this repo. hmmmmm

We should move runner to Ubuntu 24.04 also, because 22.04 is not relevant anymore. (I can't touch anything until tomorrow I think, though)

Thank you


Suggestion: Allow running specific plugin/rule

Some rules can be done in vue 2.7, and so I would recommend that we have them separate, so that we can have leaner PRs of changes.
Some rules are:

$nextTick()
v-deep
component options wrapped with defineComponent()

This is a good suggestion. I will add it to vue-metamorph

I added this to vue-metamorph 3.2.0, and included it in vue-upgrade-tool 1.0.28
You can now run selected plugins by passing a --plugins option with a micromatch pattern for the plugin name(s) you want to run, like this:
vue-upgrade-tool --files 'src/**/*' --plugins 'vue-nextTick' --plugins 'vue-v-deep' --plugins 'vue-defineComponent'

Fascinating, thank you @UnrefinedBrain


:( code ain't perfect enough

When trying to run this command:

I got this error:

Please help!!!

The error message is quite clear to me, especially this part

I suggest modifying your command, replace the   with

OMG!! Your a genius! It worked like a charm! Thank you su much!


Feature request:  link $out/share/applications/ of home.packages into $XDG_DATA_HOME/applications

This will allow desktop managers like gnome3 to launch applications installed by home-manager.
Maybe there's already a way?  With my limited knowledge I can't think of a way to do this other than
home.file.".local/share/applications/firefox.desktop".source = "${pkgs.firefox}/share/applications/firefox.desktop";

For each package that has a desktop entry.

Are you using NixOS or some other platform? I think these desktop entries should already be visible under NixOS. For other platforms it may be sufficient to ensure that $HOME/.nix-profile/share is added to the XDG_DATA_DIRS environment variable.
You could try adding
export XDG_DATA_DIRS=$XDG_DATA_DIRS${XDG_DATA_DIRS:+:}$HOME/.nix-profile/share

to your ~/.profile and see if that makes gnome3 find the desktop entries. If they show up then it might be worth adding this assignment as part of an option in HM.

Yeah this is 100% PEBKAC, gnome-session just needed restarting for it to find the desktop files in ~/.nix-profile/share.  Sorry for the noise!

For future humans, you can get gnome-session to reload by pressing Alt-F2 (run command dialog) and entering r.

No problems. Glad it worked out for you 😄