Eslint not finding package.json file

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
I have been having the issue of false positive eslint warnings when it comes to dependencies and importing those in my components. This is only an issue in our JS/TS Next.js codebase.
From the error messages it seems that eslint LSP server is not picking up correct (or any at all) package.json file and thus cannot reconcile dependencies when importing them. Sublime and VScode does not have this trouble.
I cannot reproduce this issue with my other projects that use similar tech stack but are much simpler. This is perhaps related to how we have our app setup. Any insights on how to trouble-shoot this would be very helpful 🙏
Environment
Zed: v0.96.0 (preview)
OS: macOS 13.4.1
Memory: 16 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature

If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response

We have improved eslint workspace detection in Zed 0.114.2 and Zed Preview 0.115.1 , could you give it another try or provide a link to a project to test with?


Rename?

I found this program name impossible to google. I wonder if there's a better name

just wanted to say, great project! very easy to set up in CI. I had previously been trying LinkChecker and it was significantly more difficult. just for ref, here's how i found this tool, googling specifically for broken link checker in CI

I can reproduce the search results. Now that you point it out that SEO is doing fine I guess I don't care about this issue anymore.


RFC: Configurable access groups

Introduce easier overridabel compile time configuration and use it for a configurable accessgroups service.
Motivation
Configuring the access groups service needed a custom service provider factory. This needed to get copied during the build, making it hard to validate for all facilities.
This change introduces a new override config file, that can be used  for injecting advanced configuration objects that are not environment vars( but as this is merged, allows to keep most defaults easily).
Tests included/Docs Updated?

[ ] Included for each change/fix?
[ needs manual test for graphql ] Passing? (Merge will not be approved unless this is checked)
[ no ] Docs updated?
[ ] New packages used/requires npm install?
[ ] Toggle added for new features?

Needs local testing at ESS ( as I don't have a graphql endpoint available).
Set
ACCESS_GROUPS_GRAPHQL_ENABLED=true
ACCESS_GROUP_SERVICE_HANDLER=../../config/graphqlHandler

@bpedersen2 can you let me know how I can test this feature before I merge it? Thanks

It has been merged in PR #1041.
Most likely it has become obsolete and can be closed.
I will check with @Junjiequan and @bpedersen2  first

Closing as it is now part of #1041


Fix NaN values into inflow

Closes #241
Change proposed in this Pull Request
This PR aims at avoiding NaN values into the inflow.
Any NaN value would be converted into 0.0 instead before summing to the inflow.
Description

When performing the shift of the inflow dataarray, some NaN values appears hence leading to NaN values into the sum.
This has been fixed.
Motivation and Context

If NaN values remain, this may lead to issues in the usage of the tool
How Has This Been Tested?

Using pypsa-africa
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] I tested my contribution locally and it seems to work fine.
[ ] I locally ran pytest inside the repository and no unexpected problems came up.
[x] I have adjusted the docstrings in the code appropriately.
[x] I have documented the effects of my code changes in the documentation doc/.
[x] I have added newly introduced dependencies to environment.yaml file.
[x] I have added a note to release notes doc/release_notes.rst.
[x] I have used pre-commit run --all to lint/format/check my contribution

Thanks @davide-f for looking into this! Do you happen to know the reason for the NaN values? Would be good to treat the root cause rather than the symptoms.

Thanks @davide-f for looking into this! Do you happen to know the reason for the NaN values? Would be good to treat the root cause rather than the symptoms.

The reason is the intrinsic shift operation: when a time series is shifted at the beginning (or end in case of negative shifts) NaN values are created because of missing data.
This link is pretty detailed: https://towardsdatascience.com/all-the-pandas-shift-you-should-know-for-data-analysis-791c1692b5e
There is no circulation in the shift, though it may be an interesting feature

Thanks @davide-f for looking into this! Do you happen to know the reason for the NaN values? Would be good to treat the root cause rather than the symptoms.

The reason is the intrinsic shift operation: when a time series is shifted at the beginning (or end in case of negative shifts) NaN values are created because of missing data. This link is pretty detailed: https://towardsdatascience.com/all-the-pandas-shift-you-should-know-for-data-analysis-791c1692b5e There is no circulation in the shift, though it may be an interesting feature

Just checked that there is the function "roll" that performs the circular shift, shall we go for it?

Just checked that there is the function "roll" that performs the circular shift, shall we go for it?

I'd suggest yes.

Just checked that there is the function "roll" that performs the circular shift, shall we go for it?

I'd suggest yes.

Completely agree (already done), as not using it may lead to underestimate the hydro potential for a region.
Obviously, there may not be temporal correspondence (the flow of one region in 12/2012 will become available in 1/2012 when only 2012 is considered), but I'd say it is a super detail in this case.
This PR is ready


Google Picasa is retired

We should no longer refer to Google's Picasa in the following sentence as it is now retired. Also it should be by uploading photos, not but uploading photos.

You can evaluate the effectiveness of facial recognition in free software such as Google’s Picasa or the Facebook photo tagging system, but uploading photos of a variety of people and seeing if it recognises photos of the same person.

From the facial recognition section in the computer vision chapter.

Picasa is also referred to in the opening paragraph:

These days photo album systems like Picasa and Facebook can try to recognise who is in a photo using face recognition.
For example, the following photos were recognised in Picasa as being the same person, so to label the photos with people's names you only need to click one button rather than type each one in.

We should mention that Picasa is now retired, or update the image to use a different album system to recognise faces.


DataList->filter (by ID) and DataList->byIDs return different results (and generate different DB queries)

There seems to be an issue with the queries that Page::get()->filter() and Page::get()->byIDs() generate.
To reproduce:

Install SilverStripe composer create-project silverstripe/installer myproject 3.1.1
Run dev/build
Add the following code to the init() method in Page_Controller:

Debug::dump(Page::get()->filter('ID', array(1, 2, 3))->Count());
Debug::dump(Page::get()->byIDs(array(1, 2, 3))->Count());
die();

Visit home page (note count results, should both print 3)
Add a field to $db array in Page (eg "SomeField" => "Text")
Run dev/build
Refresh home page (first result should now be 0 and second will still be 3)

There appear to be two issues here:
The first line of code generates a query like this: (simplified for easier reading)
SELECT DISTINCT count(DISTINCT "SiteTree_Live"."ID") AS "0"
FROM "SiteTree_Live"
LEFT JOIN "Page_Live" ON "Page_Live"."ID" = "SiteTree_Live"."ID"
WHERE ("Page_Live"."ID" IN ('1', '2', '3'))

The issue here is the "Page_Live" in the WHERE clause, because we haven't republished any pages no records exist in Page_Live yet so we get a count of zero back.
Ideally "Page_Live" should be "SiteTree_Live" to fix this. I think the problem is somewhere in SearchFilter->getDbName but haven't been able to investigate further yet.
The query generated by the second line of code looks like this: (simplified for easier reading)
SELECT DISTINCT count(DISTINCT "SiteTree"."ID") AS "0"
FROM "SiteTree"
LEFT JOIN "Page" ON "Page"."ID" = "SiteTree"."ID"
WHERE ("SiteTree"."ID" IN (1, 2, 3))

This query is using "SiteTree" in the WHERE clause so we aren't seeing the same problem as above. The issue here is that the code is not querying the "_Live" table when I would expect it to (or at least be consistent in how it behaves).
I haven't had a chance to investigate further what a suitable fix might be.

I can't reproduce this behaviour any longer on 3.6.1 or 4.0.0-beta1. The provided steps to reproduce all show 3 and 3 for me.

3.1.1 is unsupported


Add WHATWG Commit Snapshot computed metadata

@tabatkins api.csswg.org picks this up immediately, right? We need to change our invocation of that and I wonder how we need to balance things.
cc @domenic

Duplicating the whole header to remove the need for md-warning="Commit $SHA $COMMIT_URL_BASE$SHA replaced by $LS_URL" seems like the wrong direction to me.

Hmm. I like the way it keeps things centralized, but I see what you mean. There's probably also a way of avoiding the duplication, but I can try to make that work on top of this.

OK, I:

Added back the links that I prefer to keep, since in IRC @annevk said he'd be OK with that
Inlined the logo instead of keeping it in a separate file; this removes a wrapper <p>. This has nothing to do with the rest of the PR and is just something that has been bugging me slightly. I'm happy to remove it from this PR.
Managed to get automatic warnings generated into the right place using the COMMIT-SHA. https://github.com/whatwg/whatwg.org/pull/310 is updated to take this into account. It stops using the "commit" warning type in favor of the "obsolete" warning type, because the commit warning type wants specific inputs, whereas with the "obsolete" warning type we can just use the COMMIT-SHA input alone. This feels kind of like a hack but also kind of elegant.

We should probably not merge this until all three of us are online and can sync the whatwg.org PR and discuss whether it's the best strategy. But, I'm pretty happy with it.

@domenic I checked with Tab and I can land this once we know what we want .pr-preview.json to look like. I also rebased the tests so CI will continue to pass.

OK, this is ready. It adds a new status, LS-PR, specifically for PR previews. This allows us to get a dedicated warning and h1 that talk about the PR, for example.

Update WHATWG metadata

To better account for Commit Snapshots and PR Preview.

See also https://github.com/whatwg/whatwg.org/pull/310 and https://github.com/whatwg/spec-factory/pull/5.


Add imdsv2_required flag for critical addons asg

The ML team depends on the flag imdsv2_required in one of our clusters because we still use kube2iam for an app.
We need to be able to pass this flag to the critical_addons ASG because kube2iam pod can't startup in those nodes.
This is my first PR into the module. Happy to help with the release process but will need some guidance :)

I end up removing the toleration of kube2iam daemonset for critical addons


Coda crashes when trying to stake but works as simple node

I am trying to stake again. It worked fine until I decided to do a TX. After that node is not starting stacking anymore. It starts as node, it syncs but no way to start in staking mode.
coda_crash_report_2020-02-10_20-19-39.166502.tar.gz

Closing this issue as it is stale for a long time.


Falcor is rewriting paths strangely

I'm using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>browserified together using<EMAIL_ADDRESS>on<EMAIL_ADDRESS>running on Windows 7 x64.
I have the following routes specified on the server:
user[{keys:users}].details
user[{keys:users}].auth2f.details
user[{keys:users}].auth2f.type
user[{keys:users}].appdata

I'm using the following code on the client:
var falcor = require("falcor"),
    HttpDS = require("falcor-http-datasource"),
    model  =  new falcor.Model({
        source : new HttpDS("/model.json")
    });

model.get([
    [ "user", "F613C9D2-B291-DE11-A58E-0014220D425B", "details" ],
    [ "user", "F613C9D2-B291-DE11-A58E-0014220D425B", "auth2f", "type" ],
    [ "user", "F613C9D2-B291-DE11-A58E-0014220D425B", "auth2f", "details" ],
    [ "user", "F613C9D2-B291-DE11-A58E-0014220D425B", "appdata" ]
]);

and falcor is making a request that looks like this to my server:
/model.json?paths=[[["F613C9D2-B291-DE11-A58E-0014220D425B","details","user"],["F613C9D2-B291-DE11-A58E-0014220D425B","auth2f","type","user"],["F613C9D2-B291-DE11-A58E-0014220D425B","auth2f","details","user"],["F613C9D2-B291-DE11-A58E-0014220D425B","appdata","user"]]]&method=get
broken out so they're easier to read, the paths param is
[
    [
        ["F613C9D2-B291-DE11-A58E-0014220D425B","details","user"],
        ["F613C9D2-B291-DE11-A58E-0014220D425B","auth2f","type","user"],
        ["F613C9D2-B291-DE11-A58E-0014220D425B","auth2f","details","user"],
        ["F613C9D2-B291-DE11-A58E-0014220D425B","appdata","user"]
    ]
]

... what happened? It looks like falcor tried to notice that all the paths started with user and optimize it out, but it instead did something weird.
The server unsurprisingly doesn't understand that request and returns a very strange response.

I also tried this with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>with no luck. Can't go further back right now.

Its not writing paths strangely, its doing exactly as you specified.  The problem is that you are providing an array of Paths.  Instead provide an argument list of paths.
E.g
// No
model.get([
    [ "user", "F613C9D2-B291-DE11-A58E-0014220D425B", "details" ],
    [ "user", "F613C9D2-B291-DE11-A58E-0014220D425B", "auth2f", "type" ],
    [ "user", "F613C9D2-B291-DE11-A58E-0014220D425B", "auth2f", "details" ],
    [ "user", "F613C9D2-B291-DE11-A58E-0014220D425B", "appdata" ]
]);

model.get(
    [ "user", "F613C9D2-B291-DE11-A58E-0014220D425B", "details" ],
    [ "user", "F613C9D2-B291-DE11-A58E-0014220D425B", "auth2f", "type" ],
    [ "user", "F613C9D2-B291-DE11-A58E-0014220D425B", "auth2f", "details" ],
    [ "user", "F613C9D2-B291-DE11-A58E-0014220D425B", "appdata" ]);

Quick question @tivac do you have these paths stored off in a config?  Will you have to use apply to use get?

Thanks, I feel pretty dumb. I just noticed that myself and was hoping I could close this before anyone noticed.


update setFlags params - use only one parameter for toggling state

In current verion libary we updated state application step by step. (turnScreenOn, showWhenLocked, keepScreenOn)
In this case we have a problem, when android app was killed. App can have unlock and unshown screen or shown and lock screen in the same time.
For this problem I found solution, that we need to update state our app only with one action https://stackoverflow.com/questions/53191903/how-to-show-the-incoming-call-screen-when-the-screen-is-locked/53192049#53192049

Hello! I appreciate your contribution. However, there are a few issues:

Changing params to a single boolean flag might work for you, but it reduces flexibility. What if someone needs to set only one parameter? Instead, we can do something like this:

export async function setFlags(
  params:
    | {
        turnScreenOn?: boolean;
        showWhenLocked?: boolean;
        keepScreenOn?: boolean;
      }
    | boolean
): Promise<void> {
  if (!isAndroid) throw new Error('Implemented only on Android!');
  await ActivityUtils.setFlags(
    typeof params === 'boolean'
      ? { turnScreenOn: params, showWhenLocked: params, keepScreenOn: params }
      : params
  );
}

I'm not sure how changing setTurnScreenOn and setShowWhenLocked to window flags fixes something. These two flags are deprecated since API 27 (Android 8.1): FLAG_TURN_SCREEN_ON, FLAG_SHOW_WHEN_LOCKED. But if it really fixes something for you, let's add them as boolean flags to params map. For example, windowTurnScreenOn and windowShowWhenLocked.

Sorry for long wait.
I found, that problem, that setTurnScreenOn and setShowWhenLocked were used out UiThreadUtil.runOnUiThread
After I put them inside, everything works well.
I think, All worked in my previous version because window.addFlags and window.clearFlags were inside this property despite the fact flags FLAG_TURN_SCREEN_ON and  FLAG_SHOW_WHEN_LOCKED are deprecated.
Also, I returned all changes except ActivityUtilsModule.java file

Released as v0.1.1


Unable to change mod versions in build

Suddenly I just can't change modpack versions in my builds. Sometimes a yellow box shows up and says "Unable to change modversion", sometimes nothing happens at all when the "change" button is clicked.
I don't know if I'm the one doing something wrong or if this is a bug, how can I troubleshoot it?

Can you change the modpack version in mysql?

Yes, that worked, and I was able to download the correct version with the launcher after changing it in MySQL.

I'm so sorry, I have wasted your time. When I click "change" the first time it works, but there is no message saying that it has worked. So I click again, but because it has already been changed it can't be changed again: "Unable to change modversion". My suggestion is that there should be a "Success"-message when the change works. Sorry.

Hey there,
There was a success version but people were getting annoyed with the spam.
What I'll do is modify the "Unable to change modversion" message to better clarify that the version has already been changed

OK, thanks!


Do not use panic! in Node

In node.rs, the key calls panic! conditionally. This assumes there is no such case, but since it's not 100% guaranteed we need to handle this in a different manner.

Do you have suggestions how to do it differently?
For reference, previous discussion on panicking https://github.com/petabi/review-database/issues/208#issuecomment-1942137773

@sophie-cluml and @msk,
Firstly, I would like to apologize for my late suggestion and for any inconvenience caused. In my view, it would be more effective to remove the name from the NodeSetting and place it directly within the Node. I believe that a name should be a mandatory and unique attribute for a Node, making it preferable to include it in the Node itself rather than in the as_is or to_be settings. This approach ensures that whenever a key is created, it can always be associated with a name.

By adopting this approach, modifying the name requires a distinct process beyond simply using the to_be. However, this extra step is not overly burdensome, and given the names unique significance, it warrants individual attention.

@sehkone Looks good to me.


Fix incorrect links in PPP

Fix incorrect links in PPP

Codecov Report

Merging #280 (8739226) into master (9807de3) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #280   +/-   ##
=========================================
  Coverage     69.34%   69.34%
  Complexity      727      727
=========================================
  Files           112      112
  Lines          2525     2525
  Branches        308      308
=========================================
  Hits           1751     1751
  Misses          666      666
  Partials        108      108

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


VTK9 issues with WavefrontOBJ database reader

Describe the bug
Running the obj.py test on Windows, has numerous failures with this error message:
vtkDataReader.cxx:1574   ERR| vtkPolyDataReader (00000188B08C8D80): Error reading binary bit array!

The vtkVisItOBJReader probably needs more of an update than simple compile-error fixes to work properly with VTK 9.
Helpful additional information

Did VisIt crash:  yes
Did you get wrong results:

Desktop

OS and version: all
VisIt Version: develop (3.4)

This isn't a problem with the OBJ reader. It's a problem in VTK, when vtkDataWriter writes a binary file containing a vtkBitArray, not enough values are written.
Occurs with VTK8 as well, but the error message only printed to our debug logs, it didn't show up in the terminal windows.


angular2 ngModel error

angular2 don't work correctly
demo
import {Component} from 'angular2/core';

@Component({
    selector: '#app',
    template: `
      <h1> {{ model }} </h1>
      <input [(ngModel)]="model" placeholder="model" />`
})
export class AppComponent {
  model: string = 'test';
}

Uncaught EXCEPTION: Error during evaluation of "input" ORIGINAL EXCEPTION: TypeError: this.directive_0_1.onChange is not a function ORIGINAL STACKTRACE: TypeError: this.directive_0_1.onChange is not a function at t.ChangeDetector_AppComponent_0.handleEventInternal (viewFactory_AppComponent:261:36) at t.handleEvent (http://sandbox.webpackbin.com/api/sandbox/vendors/2246156992/bundle.js:6:14620) at t.triggerEventHandlers (http://sandbox.webpackbin.com/api/sandbox/vendors/2246156992/bundle.js:8:25083) at eval (viewFactory_AppComponent:330:110) at http://sandbox.webpackbin.com/api/sandbox/vendors/2246156992/bundle.js:12:27411 at http://sandbox.webpackbin.com/api/sandbox/vendors/2246156992/bundle.js:12:20197 at t.run (http://sandbox.webpackbin.com/api/sandbox/vendors/2246156992/bundle.js:8:9270) at HTMLInputElement.i (http://sandbox.webpackbin.com/api/sandbox/vendors/2246156992/bundle.js:12:20175) at t.invokeTask (http://sandbox.webpackbin.com/api/sandbox/vendors/2246156992/bundle.js:1:7615) at t.runTask (http://sandbox.webpackbin.com/api/sandbox/vendors/2246156992/bundle.js:1:4967) ERROR CONTEXT: [object Object]

Does it work when you download the project and run it locally?

No, locally input value at least change to bounded model, but that's all.
Model don't react to input changes, don't throw error either.

Hm, strange, but then I would suggest it is an Angular2 thing. Still Beta and I have just followed stackoverflow issues to build the boilerplate. could not find anything about zone.js and reflect-metadata in the Angular2 docs. Maybe we could find some boilerplate with webpack somewhere? Where we are sure it works, then copy that into webpackbin.
I am pretty confident it is not a webpackbin problem at least, since it does not work locally either.
You want to see if you could find a working boilerplate with webpack somewhere? Then you can try creating a bin manually and put it in here, and I will update it on the service :-)

Here is working webpack configuration - ng2-webpack
On webpackbin

Yeah, the NPM extractor crashed :) I am making a fix for it now. Do not quite understand how it was able to extract the same packages twice. Did you install with different versions?
Making fix now and will check it :-)

Thanks for building the BIN btw :)

No problem, thanks for great project! :D
I update zone.js in angular2 boilerplate from 0.6.2 to 0.6.6 trying to understand this weird behaviour :P

Okay, so I got things running again now. Really great that I got to solve these things in the extract, thank you for helping out! :)
That said, there is still an error, but this is definitely related to Angular2. I searched google a bit, even found an article, http://www.bennadel.com/blog/3007-failure-using-ngmodel-with-a-custom-component-in-angular-2-beta-1.htm, where the guy wrote lots about this thing and still can not figure it out :-)

I found No value accessor for '' exception in console

https://github.com/angular/angular/issues/7823

Great @rascada , I turned off mangling and now it works :-)

Btw, I have made a change in database and make your BIN the official boilerplate. Which means the new url will be:
http://www.webpackbin.com/angular2

http://www.webpackbin.com/VJ58pxqAb
updated with angular2 final version and materialize css


avatar yoinker

What would you like to see added to Assyst?
I would like a command that gets the avatar of a user
Additional context
N/A

do -url @person


Adding a new rebus for 'bookworm'

Pull Request Test Coverage Report for Build 809

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.143%

Totals

Change from base Build 514:
0.0%

Covered Lines:
158

Relevant Lines:
180

💛  - Coveralls


Get customer location via IP

Recommendation: use geolocation browser API instead

https://developer.mozilla.org/en-US/docs/Web/API/Geolocation_API
Looks interesting


after dom change the waypoint is not working even $.waypoints('refresh') not do the work

http://jsfiddle.net/VxqNa/9/
please check this issue...

Thank you for this excellent plugin.
Sorry to bump this old thread, but the code in your earlier comment ( http://jsfiddle.net/VxqNa/11/ - I know it is really old) it is not working for 4.0.0.
Is this possible with the 4.0 version (I am not using the infinite loop plugin)?

@kricore I'm not 100% clear what you're asking. You're curious about which part of that fiddle and whether it can be done in 4.0? (Though no matter what, the answer is "yes." Waypoints hasn't lost capability since then, though the API has changed.)

I 'm sorry, I wasn't clear. I need waypoints in newly created DOM elements as well.
The code in the previous fiddle produces errors. Call be dumb, and you might be correct, but I cannot seem to find a reference for this in the documentation.

@xainpro You are not dumb. There isn't anything in the documentation on how to create waypoints on elements added dynamically because there is no one way to add elements. It always depends on what you're doing and how you're doing it.
http://jsfiddle.net/imakewebthings/VxqNa/27/
That is the previous fiddle updated to use 4.0. I hope it's a useful example. The only change I had to make to get it working again was change this, which used to refer to the element, to this.element (see http://imakewebthings.com/waypoints/api/waypoint/#element-property).

Thank you Caleb and sorry for the pestering, but the fiddle is using the 3.1.1 version.
Btw, the https://rawgit.com/imakewebthings/waypoints/4.0.0/lib/jquery.waypoints.js URL resolves to a 3.1.1 file.
With the 4.0 I keep getting: "$items.waypoint is not a function"

Ah, I did use the wrong link. http://jsfiddle.net/imakewebthings/VxqNa/28/ is using the master branch, which is 4.0.0. It still works. Can you show me your error happening on a fiddle or a link?

Thank for all the help, I got it fixed in the end. I was using two waypoints and one was firing ( a trigger() function ) like crazy. Removed that instance, switched to your code and all is good now.
Keep up the good work Caleb :)


Vue 2.0+ v-for. Getting a 'Property or method is not defined on the instance but referenced during render` error

I'm getting a 'Property or method is not defined` error:
[Vue warn]: Property or method "genre" is not defined on the instance but referenced during render. Make sure to declare reactive data properties in the data option.
(found in root instance)
[Vue warn]: Error when rendering root instance
TypeError: Cannot read property 'key' of undefined(…)

While using a v-for="(genre, $index) in formFieldData.options":

<music-genre-id></music-genre-id>

The thing is that I used to have this kind of code in VueJS <2.0 and it worked, except for the (genre, $index) in ... of course.
How can I solve this? I need the formFieldData to be part of the component as it does not belong to the parent/root instance.
FYI
If I do only:
<music-genre-id></music-genre-id>

The browser displays:
{ "key": "1", "value": "Música latina", "img": "/img/music-genres/latino.jpg" }
{ "key": "2", "value": "Pop", "img": "/img/music-genres/pop.jpg" }

But it's not getting the property on {{ genre.key }}
Here's a jsFiddle, check the console.logs to look at the error.
Chrome DevTools VUE Tab shows the <Root> instance with a child <MusicGenreId> component and the component actually displays the data:
formFieldData: {
options: [
{ "key": "1", "value": "Música latina", "img": "/img/music-genres/latino.jpg" },
{ "key": "2", "value": "Pop", "img": "/img/music-genres/pop.jpg" }
]
}

You should not put script/x-template tages inside of the element that you mount to the main instance to. Vue 2.0 will read all of its content and try to use it as a template for the main instance, and Vue's virtualDOM treats script/x-template's like normal DOM, which screws everthing up,
Simply moving the template out of the main element solved the problem.
https://jsfiddle.net/fuefb1x3/1/

Man, thanks... I spent 2 days with this and now your answer saved me. <3


[WIP] Update site for v20.1.0 release

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/d48c29d3bf225a297df8f891fb2e66fdc86c4e3a/
Edited pages:

releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f50675850cf58536c58278883c2a6dbda59b1dc0/
Edited pages:

releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/fd3ae6547526f7ff81d5ef631e82e711b8b3819b/
Edited pages:

releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/ab33a3bfbad03697226bb8d61b767ea6dd6041ff/
Edited pages:

releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/044dc459fb2991d213448bc15ecb455bb14cd625/
Edited pages:

releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

releases/v20.1.0.md, line 59 at r1 (raw file):
Previously, Amruta-Ranade (Amruta Ranade) wrote…

CockroachCloud pricing is now available on the pricing page.
Free trials of CockroachCloud are now available. Contact us to request a trial code.
CockroachCloud now supports VPC peering for clusters running on GCP. Contact us to set up a VPC peering-enabled CockroachCloud cluster.

cc @kannanlakshmi in case I missed something.

Thanks, @amruta-ranade. I'll wait for confirmation from @kannanlakshmi and then write these up.

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f1bdc5f8dc84477dcdb74593d63ba55eb1f6c4d4/
Edited pages:

releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @Amruta-Ranade, @jseldess, @lnhsingh, and @mwang1026)

releases/v20.1.0.md, line 59 at r1 (raw file):
Previously, jseldess (Jesse Seldess) wrote…
This LGTM. @Amruta-Ranade do we want to add the edit profile stuff here or do you think its not important at the top level? I am happy to defer to you here.

I don't think it qualifies as a top-level callout for the 20.1 release.

IO parts LGTM. Thanks!

I don't think we need to call out changefeed features, given that they weren't an area of focus for 20.1

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c1a31f97651290ec286fda8017054bfe2e39a68b/
Edited pages:

releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a18f035ed42fed400914cfdf1ac49c5f5f180ac1/
Edited pages:

releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e48eed08c2726f136330a4316bac35dba0e693f9/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a42f94a63753ca2a3c9ad69ca9271276b56b797f/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/5c67b57e7b925c0a2fe1675ab45b31b16adf737b/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

releases/v20.1.0.md, line 80 at r4 (raw file):
Previously, awoods187 (Andy Woods) wrote…
do we need to list this as experimental in the title?

I don't think so. If they click through, they'll see that designation clearly.

releases/v20.1.0.md, line 90 at r4 (raw file):
Previously, awoods187 (Andy Woods) wrote…
should we be calling out cc here?

We are... See the last sentence. Are you saying we shouldn't?

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/cc3ca8911ba4d2a54a790cb67d7f72d5ff5689a5/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/95f8700fcba0a82acc932459ebc66a0aed2361e2/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

releases/v20.1.0.md, line 65 at r4 (raw file):
Previously, awoods187 (Andy Woods) wrote…
i dont quite understand the order of the features. It's not alphabetical or by product area/code area. Is it roughly in importance order? i think an outside reader may be confused on this. I personally would like the things grouped in user journey areas (e.g. put schema migrations like schema changes using jobs and primary key changes together) or alphabetically.

I agree. The ordering is intuitive, so there's really no ordering! I'll try adding areas.

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c2a13a7b22c1ba7765c072da251da46f6219ade7/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/234427075a1402df2c44f022f2914709af577066/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

releases/v20.1.0.md, line 87 at r4 (raw file):
Previously, awoods187 (Andy Woods) wrote…
I'm not sure if we should have a section on newly supported tools or if we should fold it into this section as a line item. We added support for django, jooq, ponyorm, and peewee. In future releases, we are likely to have GUIs and other tools beyond just ORMs as well.

Done.

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/08f8cb2a9bbfa5045067e0f7e951256759e3adc6/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/0cf7c4e45ae9cbd9d14ed983a1539e89420355e5/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/fb72515a31f683ca03328823df76643b1315d469/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/0eb48dcc4fd81ec08dddf77d0483077b2b3c6604/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/3e16f019a0744230fa52099f73154aa87300c8a3/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/397353f301b9e7c737da092abcd7dd565719a401/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/59ae6275ad6d73f4a2c0ae47fe478a669d4fdd73/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/3169fb59e7c7a7a383885ffb34816d9008205661/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/e1a2a6901e9f730bcea23118c9c003acf4571ffd/
Edited pages:

releases/release-support-policy.md
releases/v20.1.0-beta.2.md
releases/v20.1.0.md
v20.1/upgrade-cockroach-version.md


Re-introduced the OPENVDB_DEPRECATED macros

Signed-off-by: Nick Avramoussis<EMAIL_ADDRESS>This macro controls the C++ standard [[deprecated]] attribute's behaviour.

Does this not need to be exposed in the CMake as well?

I don't think this is necessarily required. This option is not specifically designed for use when building VDB (although it can be leveraged there as well), it's designed to provide downstream projects more control with VDB's deprecations. Putting it in our CMake for the VDB build is slightly awkward as, IMO, the appropriate way to solve that is to build with -Wno-error=deprecated-declarations.

Does this not need to be exposed in the CMake as well?

I don't think this is necessarily required. This option is not specifically designed for use when building VDB (although it can be leveraged there as well), it's designed to provide downstream projects more control with VDB's deprecations. Putting it in our CMake for the VDB build is slightly awkward as, IMO, the appropriate way to solve that is to build with -Wno-error=deprecated-declarations.

Right, that makes sense.


Support the required keyword in the same way as RequiredAttribute

When using .NETs required keyword, the properties that it is used on do not get marked as required in SwaggerGen. I set up a project to reproduce the issue. When adding the RequiredAttribute to the property, the result changes to the expected behavior.
I assume that this line could fix the problem if it checked for RequiredMemberAttribute too.
Thank you for investigating!
Version: 6.5.0
C# 11/.NET 7 and up
SwashbuckleReproduction.zip

+1 this is causing a lot of problem in API communication with frontend team members

This functionality has been implemented in DotSwashbuckle v3.0.1
https://github.com/Havunen/DotSwashbuckle/commit/2871109cf24ff1643bcefc0f2f32a5eaebb66d79
https://www.nuget.org/packages/DotSwashbuckle.AspNetCore

Why did you do this? Required-keyword in C# has nothing to do with nullability. It is there to enforce initialization of properties in constructor or constructor-initializers. It is perfectly fine in C# to declare a property as a required nullable int like this: required int?

See #2879.


Julia registering

@JuliaRegistrator register()

Error while trying to register: "Pre-release version not allowed"


schema: oem is missing templates

Images that uses schema: oem will cause keg to lookup templates named oem.XXX. There are no templates available for this image type

will be fixed by SUSE-Enceladus/keg#38


POC: Fill Widgets Space Redistribution

POC to implement Ability to decide how much % of space each fill widget needs to fill when placed next to another fill widget.

When two fill widget are placed next to each other, the user gets a resize handle in between them to decide how much ratio of space they occupy
Resize handle should have 25%,50%,75% stops while resizing.
Should not wrap while distributing space.
make the space distributor handle a canvas level element.

@marks0351 is this issue supposed to close

Yes, i believe we have different hypothesis to pursue now. Let me close it.


Next.js - Navigation between pages in the pages router loses translations.

Description
I've cloned the "App router migration" example, added two basic test pages in the pages router with translations strings and links using the the link component wrapper exported from the next-intl navigation file, and deployed to a serverless environment representative of the hosting environment used at the company I work via default SST configurations for a Next.js project.
When running the application locally in development mode, there are no issues and behaviour is expected.
When building the application for production and running the built application locally, the behaviour is as expected.
However, only on the deployed version of the application when transitioning via a link between two pages from the page router, the translations are lost, and the translations keys show on the page which is transitioned to.
This does not happen when transitioning between two app router pages.
Please check the reproduction URL to observe the behavior.
Verifications

[X] I've verified that the problem I'm experiencing isn't covered in the docs.
[X] I've searched for similar, existing issues on GitHub and Stack Overflow.
[X] I've compared my app to a working example to look for differences.

Mandatory reproduction URL
https://d3gc586bjowmi6.cloudfront.net/en/about
Reproduction description
Steps to reproduce:

Open reproduction url (linked page is a pages router page)
Click on "To test2" link (another pages router page)
Observe that all translations on the new pages have become their translation keys, and the browser console reports "MISSING_MESSAGE".
Also observe that all translations are correctly in the pageProps of the page contents + prefetch of the test2 page.
Refresh the page that is incorrectly showing the translation keys.
Observe that the refreshed page shows the translation strings.

Expected behaviour
Clicking on links to go between pages should show the newly navigated page with it's translations, and not it's translation keys and browser console should not throw errors.

could be a issue parsing your messages file. I would check if they have an identical structure across languages and theres nothing wrong

Really haven't seen that behavior before! It's unfortunately a bit hard to say what's going wrong here, esp. if everything is working correctly locally.
From the currently available information, this sounds more like a deployment issue. Maybe you can try to diagnose and diff the requests for subsequent navigations between the deployed version and what you're seeing locally (headers, payload, …)?


How to Run Tests document needs amater-friendly updates

I'm beginning my journey with voxpupulii and am trying to run tests on a self-hosted RHEL 8 server.
The how to run tests  procedure makes all kinds of assumptions regarding the state of the testing machine.
On a basic RHEL 8 server, I had to install:
ruby-devel
rubygems-devel
rubygem-bundler
rubygem-rake
gcc

just to be able to run "bundle install".  Unfortunately, the 'bundle install' command failed a few seconds into its run with some not-so-helpful error messages:
/usr/share/ruby/mkmf.rb:456:in `try_do': The compiler failed to generate an executable file. (RuntimeError)
You have to install development tools first.
To see why this extension failed to compile, please check the mkmf.log which can be found here:

  /tmp/bundler20230321-30083-1k34vfjnio4r-2.5.8/extensions/x86_64-linux/2.5.0/nio4r-2.5.8/mkmf.log

extconf failed, exit code 1

and
Fetching nio4r 2.5.8
Installing nio4r 2.5.8 with native extensions
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

    current directory: /tmp/bundler20230321-52387-n7bxsonio4r-2.5.8/gems/nio4r-2.5.8/ext/nio4r
/usr/bin/ruby -r ./siteconf20230321-52387-zdzvq0.rb extconf.rb
checking for unistd.h... *** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
        --with-opt-dir
        --without-opt-dir
        --with-opt-include
        --without-opt-include=${opt-dir}/include
        --with-opt-lib
        --without-opt-lib=${opt-dir}/lib64
        --with-make-prog
        --without-make-prog
        --srcdir=.
        --curdir
        --ruby=/usr/bin/$(RUBY_BASE_NAME)
/usr/share/ruby/mkmf.rb:456:in `try_do': The compiler failed to generate an executable file. (RuntimeError)
You have to install development tools first.
        from /usr/share/ruby/mkmf.rb:590:in `try_cpp'
        from /usr/share/ruby/mkmf.rb:1098:in `block in have_header'
        from /usr/share/ruby/mkmf.rb:948:in `block in checking_for'
        from /usr/share/ruby/mkmf.rb:350:in `block (2 levels) in postpone'
        from /usr/share/ruby/mkmf.rb:320:in `open'
        from /usr/share/ruby/mkmf.rb:350:in `block in postpone'
        from /usr/share/ruby/mkmf.rb:320:in `open'
        from /usr/share/ruby/mkmf.rb:346:in `postpone'
        from /usr/share/ruby/mkmf.rb:947:in `checking_for'
        from /usr/share/ruby/mkmf.rb:1097:in `have_header'
        from extconf.rb:15:in `<main>'

To see why this extension failed to compile, please check the mkmf.log which can be found here:

  /tmp/bundler20230321-52387-n7bxsonio4r-2.5.8/extensions/x86_64-linux/2.5.0/nio4r-2.5.8/mkmf.log

extconf failed, exit code 1

Gem files will remain installed in /tmp/bundler20230321-52387-n7bxsonio4r-2.5.8/gems/nio4r-2.5.8 for inspection.
Results logged to /tmp/bundler20230321-52387-n7bxsonio4r-2.5.8/extensions/x86_64-linux/2.5.0/nio4r-2.5.8/gem_make.out

An error occurred while installing nio4r (2.5.8), and Bundler cannot continue.
Make sure that `gem install nio4r -v '2.5.8'` succeeds before bundling.

In Gemfile:
  github_changelog_generator was resolved to 1.16.4, which depends on
    async-http-faraday was resolved to 0.11.0, which depends on
      async-http was resolved to 0.59.5, which depends on
        async-io was resolved to 1.34.3, which depends on
          async was resolved to 1.31.0, which depends on
            nio4r

The file ' /tmp/bundler20230321-30083-1k34vfjnio4r-2.5.8/extensions/x86_64-linux/2.5.0/nio4r-2.5.8/mkmf.log
' doesn't even exist and of course, I'm not blaming the documentation for bundle's terrible feedback.  The error, 'You have to install development tools first.' implies to me that gcc and/or gcc++ needs to be installed.
It would be great of the documentation would describe the packages required in order to achieve a successful 'bundle install' run on various operating systems.
I'm not sure how I can help contribute to the updated documentation other than to keep trying 'bundle install' until I have the minimum packages installed on my system and then provide a pull request.

Could not create Makefile due to some reason, probably lack of necessary

I think this is the crucial line. You probably don't have make installed. Can you check if that resolves your problem?

nfiiseed@nfiv-schon-03d:~/puppet-limits$ which make
/usr/bin/make
nfiiseed@nfiv-schon-03d:~/puppet-limits$

Oh, then it's probably gcc-c++. I know some people just install the Development Tools group, but I like to be more specific.

Those are installed already, too.
nfiiseed@nfiv-schon-03d:~$ rpm -q gcc gcc-c++
gcc-8.5.0-16.el8_7.x86_64
gcc-c++-8.5.0-16.el8_7.x86_64
nfiiseed@nfiv-schon-03d:~$

Here's some more:
Ignoring bcrypt_pbkdf-1.1.0 because its extensions are not built. Try: gem pristine bcrypt_pbkdf --version 1.1.0
Ignoring ed25519-1.3.0 because its extensions are not built. Try: gem pristine ed25519 --version 1.3.0
Ignoring oga-3.4 because its extensions are not built. Try: gem pristine oga --version 3.4
Ignoring ruby-ll-2.1.2 because its extensions are not built. Try: gem pristine ruby-ll --version 2.1.2
Ignoring bcrypt_pbkdf-1.1.0 because its extensions are not built. Try: gem pristine bcrypt_pbkdf --version 1.1.0
Ignoring ed25519-1.3.0 because its extensions are not built. Try: gem pristine ed25519 --version 1.3.0
Ignoring oga-3.4 because its extensions are not built. Try: gem pristine oga --version 3.4
Ignoring ruby-ll-2.1.2 because its extensions are not built. Try: gem pristine ruby-ll --version 2.1.2
Fetching gem metadata from https://rubygems.org/.......

-- snip ---

Fetching json 2.6.3
Installing json 2.6.3 with native extensions
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

    current directory: /tmp/bundler20230321-66250-1w0a0a7json-2.6.3/gems/json-2.6.3/ext/json/ext/parser
/usr/bin/ruby -r ./siteconf20230321-66250-1h1afsl.rb extconf.rb
Ignoring bcrypt_pbkdf-1.1.0 because its extensions are not built. Try: gem pristine bcrypt_pbkdf --version 1.1.0
Ignoring ed25519-1.3.0 because its extensions are not built. Try: gem pristine ed25519 --version 1.3.0
Ignoring oga-3.4 because its extensions are not built. Try: gem pristine oga --version 3.4
Ignoring ruby-ll-2.1.2 because its extensions are not built. Try: gem pristine ruby-ll --version 2.1.2
checking for rb_enc_raise() in ruby.h... *** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
        --with-opt-dir
        --without-opt-dir
        --with-opt-include
        --without-opt-include=${opt-dir}/include
        --with-opt-lib
        --without-opt-lib=${opt-dir}/lib64
        --with-make-prog
        --without-make-prog
        --srcdir=.
        --curdir
        --ruby=/usr/bin/$(RUBY_BASE_NAME)
/usr/share/ruby/mkmf.rb:456:in `try_do': The compiler failed to generate an executable file. (RuntimeError)
You have to install development tools first.
        from /usr/share/ruby/mkmf.rb:541:in `try_link0'
        from /usr/share/ruby/mkmf.rb:559:in `try_link'
        from /usr/share/ruby/mkmf.rb:771:in `try_func'
        from /usr/share/ruby/mkmf.rb:1058:in `block in have_func'
        from /usr/share/ruby/mkmf.rb:948:in `block in checking_for'
        from /usr/share/ruby/mkmf.rb:350:in `block (2 levels) in postpone'
        from /usr/share/ruby/mkmf.rb:320:in `open'
        from /usr/share/ruby/mkmf.rb:350:in `block in postpone'
        from /usr/share/ruby/mkmf.rb:320:in `open'
        from /usr/share/ruby/mkmf.rb:346:in `postpone'
        from /usr/share/ruby/mkmf.rb:947:in `checking_for'
        from /usr/share/ruby/mkmf.rb:1057:in `have_func'
        from extconf.rb:4:in `<main>'

To see why this extension failed to compile, please check the mkmf.log which can be found here:

  /tmp/bundler20230321-66250-1w0a0a7json-2.6.3/extensions/x86_64-linux/2.5.0/json-2.6.3/mkmf.log

extconf failed, exit code 1

Gem files will remain installed in /tmp/bundler20230321-66250-1w0a0a7json-2.6.3/gems/json-2.6.3 for inspection.
Results logged to /tmp/bundler20230321-66250-1w0a0a7json-2.6.3/extensions/x86_64-linux/2.5.0/json-2.6.3/gem_make.out

An error occurred while installing json (2.6.3), and Bundler cannot continue.
Make sure that `gem install json -v '2.6.3'` succeeds before bundling.

In Gemfile:
  coveralls was resolved to 0.8.23, which depends on
    simplecov was resolved to 0.16.1, which depends on
      json
nfiiseed@nfiv-schon-03d:~/puppet-limits$

My reproducer on a minimal CentOS Stream 8 machine:
# dnf module enable ruby:2.7 -y
# dnf install ruby-devel rubygems-devel rubygem-bundler rubygem-rake gcc gcc-c++ make git -y
# git clone https://github.com/voxpupuli/puppet-systemd
# cd puppet-systemd
# bundle install

That fails on unf_ext with a similar error. Opening the error log /usr/lib64/gems/ruby/unf_ext-<IP_ADDRESS>/mkmf.log has this:
"gcc -o conftest -I/usr/include -I/usr/include/ruby/backward -I/usr/include -I.    -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fPIC conftest.c  -L. -L/usr/lib64 -L. -Wl,-z,relro  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -fstack-protector-strong -rdynamic -Wl,-export-dynamic  -m64   -lruby  -lm   -lc"
gcc: error: /usr/lib/rpm/redhat/redhat-hardened-cc1: No such file or directory
checked program was:
/* begin */
1: #include "ruby.h"
2:
3: int main(int argc, char **argv)
4: {
5:   return !!argv[argc];
6: }
/* end */

The crucial bit is /usr/lib/rpm/redhat/redhat-hardened-cc1. dnf install /usr/lib/rpm/redhat/redhat-hardened-cc1 wants to install redhat-rpm-config. Perhaps that's the missing bit for you?

The "ignoring" part may be relevant, and can point at a broken bundler path.
Where things are installed with Rubygems is honestly speaking very poor. I'd even consider it broken by default.
https://github.com/voxpupuli/modulesync_config/blob/master/moduleroot/.github/CONTRIBUTING.md.erb is a bit more complete (and https://github.com/voxpupuli/puppet-example/blob/master/.github/CONTRIBUTING.md is the rendered version). It recommends setting a bundler path.
That works, but is less efficient if you have multiple modules since you can't reuse gems between repositories. Instead, I have this in my ~/.bashrc:
# https://github.com/rubygems/rubygems/issues/4031
# https://bugzilla.redhat.com/show_bug.cgi?id=1574594
if command -v ruby > /dev/null ; then
        GEM_HOME="$(ruby -e 'print Gem.user_dir')"
        export GEM_HOME
fi

So far no luck.   Even a brand-new Ubuntu container is failing.

Trying fresh, starting a container with podman run -it --rm centos:stream8
Then:
# dnf module enable ruby:2.7 -y
# dnf install ruby-devel rubygems-devel rubygem-bundler rubygem-rake gcc gcc-c++ make git redhat-rpm-config -y
# adduser user
# su - user
$ GEM_HOME="$(ruby -e 'print Gem.user_dir')"
$ export GEM_HOME
$ git clone https://github.com/voxpupuli/puppet-systemd
$ cd puppet-systemd
$ bundle install
$ bundle exec rake -T
$ bundle exec rake release_checks

This works for me, so I wonder where the failure is for you.

So the export GEM_HOME must be the trick.  I was able to run 'bundle exec rake release_checks' and all kinds of stuff just wizzed by on my screen with a successful exit code.
Thank you so much for your help.
Shouldn't the documentation be updated to reflect these (Centos/RHEL8) steps so that others can benefit?


Markdown fix for 10-load-balancing.md

Can someone review this pull request please?

@ @

[ ]

[ ]

`

### 1.

`

Hello


PhanUndeclaredTypeProperty Property of undeclared type \PDO

I am using docker image for phan
https://github.com/cloudflare/docker-phan
One of my classes looks like this:
<?php
namespace Somenamespace\DB;

use PDO;

class PdoPdoAdapter implements PdoAdapter
{
    /** @var PDO */
    private $pdo; //!!!!!!here is phan error, line nr 9

    /**
     * @param PDO $pdo
     */
    public function __construct(PDO $pdo)
    {
        $this->pdo = $pdo;
    }

}

But when I run phan to analyze code I've got error:

src/DB/PdoPdoAdapter.php:9 PhanUndeclaredTypeProperty Property of
undeclared type \PDO

No matter if I use PDO or \PDO everywhere  I always have the same error. Is this phan's bug or mine?

In order for Phan to recognize an internal class as being defined, the corresponding extension needs to be enabled in php.ini (and the extension needs to be installed). Not sure if that's deliberate.
Add extension=pdo.so to /etc/php.ini in the docker image.
(Or invoke phar as php -d extension=pdo.so pharcommand.... pharargs...)
http://php.net/manual/en/pdo.installation.php

THank you. I was pretty sure pdo was there but you are right - there is no PDO. Could you tell me how can I run this builder mkimage-phan.bash?

Ok, I've created my own image. When I was trying to run builder from cloudfire all the time I had errors about some common constraints.
Thank you once more for info about pdo :)


EPERM error

Issue Type

[ X ] Bug
[ ] Feature Request
[ ] Question

I am getting some permission errors with systeminformation. Is this a known issue?
node: v8.2.1
systeminformation: 3.37.9

How exactly are you calling your code? Directly from command line or maybe pm2 or from within an electron app? As this is not yet a known issue, maybe this context could be helpful for determine the reason for this error.  Maybe it also would be helpful to try to call WMIC directly from commandline and see if the user can run this command. Thank you in advance.

It is within an Electron App.
Running WMIC directly on Windows CLI works fine.
My application runs fine for some time making those library requests. Suddenly i get the EPERM error and it crashes. This only happens on one server and I cannot reproduce on others.

I now encapsulated all WMIC calls in try ... catch blocks to avoid any crashing (published as version 3.41.4). Anyway the behaviour is strange ... can you test it once again with the version you have installed. What do you mean with 'runs fine for some time ... Suddenly I get the EPERM error'?

I make those calls with a frequency of 1 minute. The app runs fine for a undetermined period of time and then i get an EPERM. I will try to update the systeminformantion and see how it goes.

Closing it for now. But I will make further investigations what the reason could be.


removed the local time from the personal menu #30054

This pull request addresses the issue discussed in CZO where the local time is being displayed in the personal menu. As per the discussion, the local time feature is redundant in the personal menu and should be removed. Users can find the local time information in their user card if needed.
Removed local time display: The local time has been removed from the personal menu by modifying web/templates/personal_menu.hbs
Fixes: https://github.com/zulip/zulip/issues/30044

Screenshots and screen captures:
Before

After

Description: The only change made was removing the part where the user time was described in the personal menu file. No other parts of the file were altered as the goal was solely to remove the local time from the personal menu.
UI Change: This PR includes UI changes, as the local time display has been removed from the personal menu.

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Automated tests verify logic where appropriate.
[x] Calls out remaining decisions and concerns.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@sayamsamal Tagging you here for a quick review for my PR as you asked me in the previous PR

Thanks for the fix!

Closed due to a lot of unwanted changes.


Add pkgs messages and related

(TODO for myself: tests need fixing)

I see this PR is adding four new packages (messages and three related packages); is in possible to split this into separate PRs? That would make the review easier.

Most of them are interdependent - but I will add some more documentation and try to split it up.


Do 562 automate builds

@nirtayeb please add STAGING_DOMAIN to github action secrets and merge when ready.
https://github.com/lavanet/big-dipper-2.0-cosmos/settings/secrets/actions


jnpr.Views("...") or jnpr.View("...")

There seem to be a documentation error on your readme :
When I use jnpr.Views("..."), i get following errors:
./main.go:21:20: jnpr.Views undefined (type *junos.Junos has no field or method Views)
When I change to jnpr.View("..."), things will work, if this is an error, can you fix it ?

Thanks for catching this. Yeah, just a typo in the documentation. I'll change it :)

Ok, I have updated the documentation in the README as well as the views.go file. Let me know if you need anything else!


i18n(fr): Update guides/backend/google-firebase.mdx from #8014 (__session)

Description (required)
Update guides/backend/google-firebase.mdx from #8014 (__session)

Related issues & labels (optional)

Closes #
Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

fr
guides/backend/google-firebase.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

LGTM


Uniswap

Not sure if you can add Uniswap, but worth asking.

Uniswap is decentralized exchange (DEX) that requires a different technology than centralized exchanges to get pairs/price.
The implementation of DEX to Bitcoin Checker seems very complicated.
I think the most simple way to add Uniswap info is to use third party service - CoinGeko (https://www.coingecko.com/en/exchanges/uniswap/). But CoinGeko allows to get price for pairs with ETH only.
Would such an implementation be useful?

I think anything would be better than nothing. Thanks 😀

Uniswap will be added in the next app release.

Some coins aren't visible like:
https://www.coingecko.com/en/coins/meme
Also the second coin (ETH) is shown twice in the list.

Also, such links can't be utilized?
https://info.uniswap.org/pair/0x5DFbe95925FFeb68f7d17920Be7b313289a1a583

Some coins aren't visible like:
https://www.coingecko.com/en/coins/meme

This is strange. I don't understand why CoinGecko UI is showing information, but the API is not returning these coins. It takes time to research...

Also the second coin (ETH) is shown twice in the list.

Can you describe in more detail? Is this with all the pairs? I can't reproduce this.

Also, such links can't be utilized?
https://info.uniswap.org/pair/0x5DFbe95925FFeb68f7d17920Be7b313289a1a583

This is targeted info, but the API has a different technology that requires a lot of refactoring in the data module. This can be implemented in the future.

I think Uniswap has different lists of coins and there are two CoinGecko lists, but some coins aren't in any list and require you to input the contract address in Uniswap to make it appear. This could be why some coins aren't visible.

I will exclude Uniswap from app release to take time to fixes and research.
Thank you for operational feedback.

I think you could keep it for now while you improve it. It's not 100% but like 90% and that's better than 0%. 😃

Unstable behavior will raise questions and negative user reviews.

Now Uniswap pairs are loaded just like info.uniswap.org from thegraph.com. All previous issues will be resolved.
All changes will be included in the latest app v2.18.
P.S.
Google is slow to publish the latest app updates :(

It says only the top 500 most liquid pairs will be shown, so the example coin I sent above still won't work?

MEME coin included to the top and will be listed in the app.
You can check the top 500 Uniswap pairs yourself:

Open in browser url: https://thegraph.com/explorer/subgraph/uniswap/uniswap-v2/
Copy next query to the left window:
{pairs(first: 500, orderBy:reserveUSD, orderDirection:desc) {reserveUSD token0{symbol} token1{symbol}}}
Push execute button

The app using same API.

Great, thanks! There is also a telegram uniswap price bot; I wonder if they use thegraph.com. See https://t.me/UniSwapPriceBot. There's also dedicated bots that show trading data for specific listing pairs. See: https://unibot.network/
This is all just FYI.


Update examples link on express to the right repo.

Which problem is this PR solving?

Short description of the changes

Not gonna do all that for just updating a link on a README. Please, just fix it :-)

thx for the contribution but we cannot accept any before signing CLA, please sign it otherwise we will have to close this PR

I'm not gonna sign a CLA for adding a "-contrib" to a link.
Please, just fix it somehow.


40 out of 32 bits collected, but no seed output

I was recently end-raiding, which of course meant that i found multiple end gateways. The seedcracker, afterwards, said that it'd collected 40 out of the 32 required bits, but there was no way of actually getting the result. Am I overlooking something here?

Did you do the required steps? Like trying to find the dungeons?

@MrAppu Since I was searching for end cities on a multiplayer server, I’m pretty sure those chunks hadn’t been loaded yet, though I can find more of needed - do I need to simply go to new chunks or do the gateways have to generate there? The server in question hasn’t changed versions since it’s start

I'm having the same issue, but I had 3000 bits instead of 40. I tried to do the dungeon one, but it still didn't give me the seed. I've found some villages, a few mineshafts, tons of dungeons, and I still don't get the seed. There aren't any plugins on the server I'm trying to get the seed of. Am I doing something wrong?

The same thing happened to me, I wanted to get the end seed that was different from the overworld on the server. when I collected 40 bits process started and found the structure seed, but it just stopped at 100%. I tried again but this time I found another gateway and with 60 bit I returned to the pillars and this time it cracked the seed successfully.
I had success with only 40 bits for the end seed sometimes though.


Update friends_lobbies.md

Slight example update for Dictionary api change from .empty() to .is_empty()

This should have Godot 2/3 and 4 tabs showing different code.  But you are right for the most modern version of Godot.  Is this PR editable?


Update charts to avoid overlapping labels

Fixes #420

🗣 Description
Currently low values overlap with the dates in the x axis on line charts. This change dynamically places labels based on where they are on the chart.
💭 Motivation and context
Overlapping labels caused the values and dates to be unreadable

Coverage: 25.059% (-0.5%) from 25.555% when pulling d27e273cda46fd50ce99e664ca7c6061653a1a98 on DJ-update_charts into 31f863034674d77e978bd195bafb9a889594a31a on develop.


Added multiple returns for search! *Again

Note Searches will now ALWAYS return an array

Closing PR.
Code is outdated and shows that "This Branch has conflicts that must be resolved."
Moreover, the code that is shown will break for Binary Search.
In the next PR, please state a reason for this change so it's easier for future discussions.


Annotations filters new UI

Motivation and context

https://github.com/openvinotoolkit/cvat/issues/1418
How has this been tested?

Go to annotation page, click filter Icon on top bar right (see examples images below)

Checklist

[x] I submit my changes into the develop branch
[x] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[x] I have linked related issues (read github docs)
[x] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

@vnishukov , need to fix the problem with CI build.

Hi, I tried the patch. Mostly working fine, but several comments/questions below.
@ActiveChooN Please, try to run also this patch and left some comments about.

When I open CVAT in small windows (first screenshot), layout looks alright (except of minor issues with position of sort by selector, it is expected to be right-aligned)

But when I open CVAT in my different configuration (Full HD), something wrong with layout

I have attributes type (radio) and color (select) and I want to set equality filter on them (like on the screenshot below), but I can't because there are not option to select color attribute, only text.

I would vote for changing color to blue

Probably "Tag" is missed in possible types. (I see "Tag" in "Shapes", but "Tag" is not a shape at all)

Is comparison label with these fields valid? (the same for type and shape)

Is raw filter editor difficult to implement? (I see it was cut from the interface)

@bsekachev

Hi, I tried the patch. Mostly working fine, but several comments/questions below.
@ActiveChooN Please, try to run also this patch and left some comments about.

When I open CVAT in small windows (first screenshot), layout looks alright (except of minor issues with position of sort by selector, it is expected to be right-aligned)

But when I open CVAT in my different configuration (Full HD), something wrong with layout

I have attributes type (radio) and color (select) and I want to set equality filter on them (like on the screenshot below), but I can't because there are not option to select color attribute, only text.

I would vote for changing color to blue

Probably "Tag" is missed in possible types. (I see "Tag" in "Shapes", but "Tag" is not a shape at all)

Is comparison label with these fields valid? (the same for type and shape)

Is raw filter editor difficult to implement? (I see it was cut from the interface)

Will check top-bart alignment
As I understood query-builder allow to compare same types of fields. In our case radio will cast to text
Will change to blue
Probably yes. It was developed based on initial concept
Will doublecheck what happening here
I don't think is difficult but can we make it with separate enhancement PR?

@vnishukov Please, work with @dvkruchinin if you have difficulties with CI.

@bsekachev

@vnishukov Please, work with @dvkruchinin if you have difficulties with CI.

Root cause already defined. Will be fixed soon

Hi @vnishukov
I've just remembered about feature createObjectURL which works for objects saved on the sever.
Please, be sure it also works in new filters implementation because filters are used for this feature (serverID field to be more specific)

Coverage decreased (-0.5%) to 71.587% when pulling 84aa98498e3e33623f4caa0c2ddae29c8d1f8cc7 on annotations-filters-new-ui into f2f6463043ea78a4fc922842f1fccb22ee026541 on develop.

Is comparison label with these fields valid? (the same for type and shape)

Yes it's valid because all of these stuffs are the same type in terms of react-awesome-query library (type: select)

Yes it's valid because all of these stuffs are the same type in terms of react-awesome-query library (type: select)

From the point of view UX I am not sure that these comparisons are valid. Do you think it is?
And why do clientID and serverID for example have select type if they are numbers and cannot be changed?

Yes it's valid because all of these stuffs are the same type in terms of react-awesome-query library (type: select)

And why do clientID and serverID for example have select type if they are numbers and cannot be changed?

Well, it is number in terms of each select item, but in terms of fields config it's a single select. This is migrated from initial concept where we wanted to list all of the client and server ids in the dropbox. We actually can replace it with something like number or range of numbers, but I'm not sure if it will be clear for user how exactly he/she should populate these field(s) and with what values. What do you think about that?

Or we can get rid of clientID and serverID to be appeared in the right side of comparison as well.
I believe the last one it's a best and most logical solution.
What do you think about that?

As I understand you already done it. Agree, I do not see any cases when we need clientID, serverID at the right side of comparison (only at left).

Hi @vnishukov
I tested the patch one more time.
Navigation "Go back/next with a filter" does not work. It should navigate to the nearest frame that consist any objects (considering applied filter)
"Create object URL" does not work. It creates URL, but when I try to open it all objects are still visible and no any filters applied (at the same time filters button is blue, so apparently UI considers it to be activated)
Logic with attribute still not clear. I have attribute "color" (select) and attribute "type" (radio buttons), both possible values are string[], but the constructor  does not allow to compare them.
Possible pairs for "color" attribute: label, type, shape. Possible pairs for "type": attribute "text" (which is text)

One more possible issue found:
I have "label 1" which contains attribute "type" (radio button)
I have "label 2" which contains attribute "type" (number)
Looks like constructor doesn't work correctly in this case. It considers "type" as number attribute only. Should not we link attributes with their parent labels? Something like: "type (label 1)", "type (label 2)"?

[ ] Server ID should be removed
[ ] Client ID should be renamed to Shape ID
[ ] Shape ID should be a number (not select). Nobody will select from 1000 values. If you don't know the exact number, nothing to select.
[ ] Fix bug: add rule for "Server ID" or "Client ID", as select you will see only 1 variant (let's say "1"). Enter "2" and it will crash UI.
TypeError
(t.children || t.value).toLowerCase is not a function

TypeError: (t.children || t.value).toLowerCase is not a function
at t.filterOption (http://localhost:8080/cvat-ui.dffe796fde25f2595563.min.js:388:377502)
at http://localhost:8080/cvat-ui.dffe796fde25f2595563.min.js:24:146169
at Array.forEach ()
at y (http://localhost:8080/cvat-ui.dffe796fde25f2595563.min.js:24:145984)
at http://localhost:8080/cvat-ui.dffe796fde25f2595563.min.js:36:225400
at Object.pi [as useMemo] (http://localhost:8080/cvat-ui.dffe796fde25f2595563.min.js:348:61567)
at t.useMemo (http://localhost:8080/cvat-ui.dffe796fde25f2595563.min.js:332:5984)
at x (http://localhost:8080/cvat-ui.dffe796fde25f2595563.min.js:36:225346)
at Ko (http://localhost:8080/cvat-ui.dffe796fde25f2595563.min.js:348:57930)
at Pi (http://localhost:8080/cvat-ui.dffe796fde25f2595563.min.js:348:65886)

[ ] Should select and radio have the same type (select)? No radio is converted to string

@nmanovic

Server ID should be removed

It cannot be removed because "Create object URL" works via serverID.

@nmanovic

Server ID should be removed

It cannot be removed because "Create object URL" works via serverID.

Shape ID should be a number (not select). Nobody will select from 1000 values

It was Data Annotation Team request

@bsekachev , let's discuss it one more time. Need to understand how they are using the feature.

@nmanovic

Server ID should be removed

It cannot be removed because "Create object URL" works via serverID.

Shape ID should be a number (not select). Nobody will select from 1000 values

It was Data Annotation Team request

@bsekachev , let's discuss it one more time. Need to understand how they are using the feature.

I've already sent a letter to Andrey. Agree, that this using looks strange.

@nmanovic @ActiveChooN
Issues with this patch:

It is not clear how to implement input for Object ID that support both predefined and custom values "out-of-the-box"
Related issue: https://github.com/ukrbublik/react-awesome-query-builder/issues/191 ('select' type does not support custom values since antd does not support them)
I tried to use 'multiselect' instead of 'select' because it supports allowCustomValues configuration. Nevertheless it does not work with JsonLogic, returning false when comparison.

When we compare two attributes (like: an attribute "color" of label "car" equals to attribute "wheel color" of label "car" ), it shows also objects which are lack of these attributes because formally they are equal in this case (undefined === undefined). It is workaround-ed by adding label name with && operator to the filter expression.

~If a label/an attribute contains . in it's name filters don't work~
Good news. It was also workaround-ed by replacing all . characters by another dot-like character (internally only, no any changes for a user).


[Mention The Feature]: Parkinsons disease prediction

Is your feature request related to a problem? Please describe.
Parkinsons disease prediction using the Machine learning models
Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Additional context.
No response
Show us the magic with screenshots
No response
Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

Thank you for raising the issue.
i think this is the wrong issue that you have kept, this is for website improvements. not for tutorials
So I am closing this issue.
Please understand.
And one more thing this project is already inactive including me also due to some of my works.
Please do contribute to other projects.
I hope you understand.


handleEvent for addEventListener

According to spec, addEventListener can receive object with handleEvent function

Duplicate of https://github.com/apache/cordova-js/pull/130?

This has been implemented in #130
Please close.


add-category comment-prevenir-l-exposition-au-plomb-dans-son-logement.md

:tada: This PR is included in version 1.4.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Janitor has a hard time cleaning specific "messes".

Description
Without space cleaner, (or a crowbar) janitors can't clean grimy tiles or spray-painted graffiti.
Reproduction
Be a janitor while people are mucking up the station.
Screenshots

Additional context

This wouldn't be much of an issue if it was easier to replace floor tiles, but it's currently a tedious, time consuming task to pry them up and replace them.
The same goes for Space Cleaner, it's tedious to get, doesn't have enough reach, and only gets 10 sprays before being empty. (Along with the examine text not showing how much you even have left.) That, and actually trying to spray graffiti is a crapshoot, it feels like 50% of the time, it doesn't even hit the thing I'm spraying at.
Slightly outside the scope, I can't seem to figure out how to mop things under tables, using the mop on the tile (even if clicking somewhere other than the table) causes me to put the mop -on- the table instead.

I thought that mobs did that, by putting water on the floor with the mob and picking it back up. Maybe at some point it stopped working?

maybe cool solution is to use soap for cleaning decals, since you cant soak clothes in blood (yet) have doafter of a second or two for removing graffiti or barratrys tiles, space cleaner being a higher grade instant + aoe solution leaving soap as poor tider's tool


[Task] Let VCs and VPs throw errors during validation, include expiration functionalities.

Description
Currently Verifiable Credentials and Verifiable Presentation either return true or false during validation. It would be more clear to add why a validation failed, therefore we should throw an error (code). In addition, a credential doesn't check if it has been expired, this should be added.
Motivation
Provide user more information on what is wrong.
To-do list
Create a task-specific to-do list . Please link PRs that match the To-do list item behind the item after it has been submitted.

[ ] Check for valid expiration and issuance dates
[ ] Align on error strategy within the framework that is FFI compatible
[ ] Return error(codes)

Change checklist
Add an x to the boxes that are relevant to your changes, and delete any items that are not.

[ ] The feature or fix is implemented in Rust and across all bindings whereas possible.
[ ] The feature or fix has sufficient testing coverage
[ ] All tests and examples build and run locally as expected
[ ] Every piece of code has been document according to the documentation guidelines.
[ ] If conceptual documentation (mdbook) and examples highlighting the feature exist, they are properly updated.
[ ] If the feature is not currently documented, a documentation task Issue has been opened to address this.

For more context:
In the case of verifiable credentials this is the boolean field https://github.com/iotaledger/identity.rs/blob/dev/identity-iota/src/credential/validator.rs#L24 that is used to indicate whether the validation was successful or not.  The reason for this field to be present in the type is that there are situations where one may want to permit credentials that are technically invalid (for instance in some countries a recently expired drivers licence may still be considered as valid for identification purposes, even though it no longer permits the owner to drive). On the other hand the return type of https://github.com/iotaledger/identity.rs/blob/dev/identity-iota/src/credential/validator.rs#L78 is  Result<CredentialValidation<T>>, indicating that errors are part of the Err variant, it is indeed somewhat awkward to have a "verified" field in the CredentialValidation struct.

A provisional (currently Rust only) implementation can be found in this draft PR https://github.com/iotaledger/identity.rs/pull/564. It adds a lot more type safety and the ability to specify which deficiencies in the credential are acceptable during validation. It needs some more tests and a little more thought needs to be put into the API.

This functionality will be part of this PR: https://github.com/iotaledger/identity.rs/pull/599


注解方式怎么配置纠结说

注解方式怎么配置纠结说

Hi, could you provide some more details?

We recommend using https://github.com/dubbo/dubbo-spring-boot-project


mobile body text width shrink

some page's body text width is too small.
ps. btw. such a nice program.. thanks.

v0.3 fixes this


[:bulb: FEATURE REQUEST]: Requests with application/x-www-form-urlencoded content-type are not parsed when request method is DELETE

No duplicates 🥲.

[X] I have searched for a similar issue in our bug tracker and didn't find any solutions.

What happened?
When sending requests with application/x-www-form-urlencoded parameters with the DELETE request method, it seems that the parameters are lost somewhere inside Roadrunner, a simple way to test is to use the following (assuming Roadrunner is listening in the port 9000):
# When sending as POST, the parameters appear properly on the PHP side
$ curl http://localhost:9000 -X POST --data-urlencode 'id=123' -v -o /dev/null
# But when sending with DELETE, they appear as `{}`
$ curl http://localhost:9000 -X DELETE --data-urlencode 'id=123' -v -o /dev/null

I've attached a log showing the Request object that is received inside the PSR7Worker in both cases
Version (rr --version)
2.10.6
Relevant log output
ROOT/vendor/spiral/roadrunner-http/src/PSR7Worker.php (line 107)
########## DEBUG ##########
object(Spiral\RoadRunner\Http\Request) id:0 {
  remoteAddr => '<IP_ADDRESS>'
  protocol => 'HTTP/1.1'
  method => 'POST'
  uri => 'http://localhost:9000/'
  headers => [
    'Accept' => [
      (int) 0 => '*/*'
    ],
    'Content-Length' => [
      (int) 0 => '6'
    ],
    'Content-Type' => [
      (int) 0 => 'application/x-www-form-urlencoded'
    ],
    'User-Agent' => [
      (int) 0 => 'curl/7.80.0'
    ]
  ]
  cookies => []
  uploads => []
  attributes => []
  query => []
  body => '{"id":"123"}'
  parsed => true
}
###########################

ROOT/vendor/spiral/roadrunner-http/src/PSR7Worker.php (line 107)
########## DEBUG ##########
object(Spiral\RoadRunner\Http\Request) id:0 {
  remoteAddr => '<IP_ADDRESS>'
  protocol => 'HTTP/1.1'
  method => 'DELETE'
  uri => 'http://localhost:9000/'
  headers => [
    'Accept' => [
      (int) 0 => '*/*'
    ],
    'Content-Length' => [
      (int) 0 => '6'
    ],
    'Content-Type' => [
      (int) 0 => 'application/x-www-form-urlencoded'
    ],
    'User-Agent' => [
      (int) 0 => 'curl/7.80.0'
    ]
  ]
  cookies => []
  uploads => []
  attributes => []
  query => []
  body => '{}'
  parsed => true
}
###########################

Sure, I've updated both the server and the PHP library to the latest minor version (2.10.6), and I managed to reproduce this issue following the same steps

@ekisu According to the existing HTTP RFC-7231, the DELETE (https://httpwg.org/specs/rfc7231.html#DELETE) method has no defined behavior on parsing body (which you sent with application/x-www-form-urlencoded header).

A payload within a DELETE request message has no defined semantics; sending a payload body on a DELETE request might cause some existing implementations to reject the request.

So, technically, RR behavior is correct.
You may use either POST, PUT, or PATCH methods with the application/x-www-form-urlencoded if you want to be sure that RR will parse the body.

@ekisu It's actually not replaced, but not parsed at all 😃. Unfortunately, this is not possible to send the entire body with the application/x-www-form-urlencoded, and method which has no defined semantics in your case, according to the specs.

I've taken a look a bit deeper on what happens on PHP-FPM in this specific case, and here's what I've found:

when it receives an POST request with the application/x-www-form-urlencoded content-type, it parses the data into the $_POST superglobal
when it receives a request with the application/x-www-form-urlencoded content-type with any other request method rather than POST, it does not parse the data, sending it into the php://input stream instead

Looking at the source of the http plugin, it seems that Roadrunner always attempts to parse application/x-www-form-urlencoded request bodies if they're not HEAD or OPTIONS, replacing the original body - this means that the PHP application code has no longer any means to retrieve the original contents. This is just a guess, but I imagine that the Go ParseForm method only parses the body if it's a POST/PUT/PATCH request - and, if it's not, it just sets a default, empty value, which would explain this behavior.
Fortunately, in our usecase, we can change this request to something that works under Roadrunner, but I believe that replicating PHP-FPM's behavior would be the right way here, even if it's an implementation-specific behavior

Sure, I can't change the labels though :thinking:

You're right, but this is old behavior, and it should be updated to skip any method except PUT, PATCH, and POST.
Would it be possible to treat it as a contentStream instead? Not sure if this would abide to the standards, but it would mimic the "send it as a stream" part

Would it be possible to treat it as a contentStream instead? Not sure if this would abide to the standards, but it would mimic the "send it as a stream" part

I can send a raw body in the RR's body field (we can't stream it so it might be just a binary body). I need to sync with a PHP part of the worker. We should be careful here not to break the existing behavior.

Hey @ekisu 👋🏻
We discussed this FR with our PHP team, and as promised, I'm here with the results.
Since this is not a standard, we put this ticket in the Low priority. But, if this proposal is popular, we'll introduce a flag for the http plugin to redirect the payload to the PHP worker with minimal processing by RR.

@ekisu Hey 👋🏻
After some discussion in the nearby ticket, we decided to send the untouched post form values data to the worker even if this is the DELETE method. The feature will be in the v2.11.1. (https://github.com/roadrunner-server/roadrunner/issues/1264#issuecomment-1220644959) and must be activated by the additional http plugin option (TBD).

Whoa, this is great news! Thanks @rustatian

Remember that that is valid only for the x-www-form-urlencoded values. Not for the multipart form values.
The release is scheduled for Thursday, 25 Aug.


Add Ambrosus network (AMB)

Description

[X] Symbol: AMB
[X] ChainId: 16718
[X] Website: https://ambrosus.io/
[X]  Block-Explorer: https://explorer.ambrosus.io/
[X] slip-0044 type: None

Additional comments
First PR #177

@cseguret-ledger Can I work on this issue ?

Please follow the guidelines for this chain to be supported.


Introduce enlargedImagePosition prop

Hello @ethanselzer
I just add optional prop enlargedImagePosition to choose position of enlarged image :
beside (default for ReactImageMagnify) : enlarged image will be next to the small image
over (default for ReactImageMagnifyTouch) : enlarged image will be over the small image

Have a nice day :)

@damien916 I think this is a great feature! Thank you very much for creating it! I left a couple comments on your PR. Please let me know what you think about them. ~Ethan

@ethanselzer I just add two commits to the PR. I don't finded solution to test oneOf PropType with enzyme, so I commented them. Thank you again. Damien

@damien916 - Thanks for making the adjustments I suggested! I really appreciate it. The npm package has been updated and a new release has been created on GitHub. You are awesome! ✨💫

@ethanselzer Thank you so much 👍


Selecting features from datasource

Could we get additional documentation or a sample of how to select features from a datasource based on a click on a map or the intersection of a drawn graphic?
I have been scratching my head over how to accomplish this. The SDK provides a selectFeaturesByGraphic method in the JimuMapView class but it selects everything regardless of whether or not the layer actually has a popup enabled or not. If I would like to select from a specific list of datasources (i.e. only those that are visible and have a popup enabled). I find myself having to loop every layer in the map, executing a query, and then looping the results and using the selectRecordsByIds on the datasource, but even this doesn't always give me the proper behavior, often times features are not highlighted in the map, even though results are returned. I attached a snippet of that code below.
Therefore, can we get additional documentation on how to select features from a datasource based on a graphic or mouse click?
async function handleClick(evt: __esri.ViewClickEvent) {
   const clickedPoint = new Graphic({ geometry: evt.mapPoint });

   const queries = queriableDataSources
     .filter((ds) =>
       jimuMapView.getJimuLayerViewByDataSourceId(ds.id).isLayerVisible()
     )
     .map((ds) => {
       return ds.query({
         geometry: clickedPoint.geometry.toJSON(),
         spatialRel: "esriSpatialRelEnvelopeIntersects",
         returnGeometry: true,
         outFields: ["*"],
         distance: 0,
         units: "esriSRUnit_Meter",
       } as FeatureLayerQueryParams);
     });

   const results = (await Promise.all(queries)).filter(
     (q) => q.records.length
   );

   console.log("results", results);

   results.forEach((result) => {
     result.records[0].dataSource.selectRecordsByIds(
       result.records.map((record) => record.getId()),
       result.records
     );
   });

 }

@Party-Pelican The main reason why you can't use selectFeaturesByGraphic is it selects layers even the popup is not enabled, right?

@qlqllu yes, that is correct. Is there another method that I should be using instead? what do you recommend? I appreciate any info.

This method is the best choice for your requirements, but it seems to miss some features. If we add an option, such as a callback function, you can check whether you need to select by checking the layer property in the function. Is this a good solution for your case?

That would work, so in the callback function, would I need to clear the selection of layers that don't have the popup enabled or do the selection in the callback? I'm not sure of the specifics, but if it's possible to allow for more options in this method, that would be great!


TextEdit text is not clipped into content margin.

Godot version:
3.2.3
OS/device including version:
Windows 10 ltsc 64 bit
Issue description:
The TextEdit text is not clipped to the styles content margin on a per pixel basis.

Steps to reproduce:

create a theme
add all text edit items
set the style for normal so that it has really small content margin
apply theme to text edit
run project and see that the scrollbar is limited to it but not the text drawn.

Minimal reproduction project:
FocusBug.zip

this seems to be with dialog too
this is what it does...

what it should be...


Add ActionController::Metal as possible base class of ApplicationController

This is common when performance is deeply cared for. One use-case is
ActionController::API.without_modules(blacklist) to blacklist what's not needed.
The diff appears bigger than it is, I've just wrapped the old code in a loop.

I like it - thanks!

Thank you for open sourcing your gems, the documentation and all that! And for the fast merge.