Add secure text field

This pull request closes #48 and #37, as well as the issue #76.
The implementation uses a ternary operator to set which text field is being used, instead of the if-else blocks used in the other pull requests. The semantic difference between them was if not bool and if bool.
Both pull requests have not been touched for a long time, and need to merge in master before being ready for a pull request. So instead, there is now this.
I will merge this pull request in 48 hours if there are no concerns or observations withstanding.

https://github.com/jaredks/rumps/pull/95


a new railway system map?

Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
i just used Vue to enhanced the railway map few days ago and it works very well
so i think we can have a better railway system map
Additional Information
u can visit live demo at here

From 4.0.0, MTR is using new web railway system map https://github.com/Minecraft-Transit-Railway/Transport-Simulation-Core/tree/555558f6e005ca3c171abbdc06ca376c73dd223f/buildSrc/src/main/resources/website
It is written in Angular and MTR 3.3.0 seems no longer upgrade.

From 4.0.0, MTR is using new web railway system map https://github.com/Minecraft-Transit-Railway/Transport-Simulation-Core/tree/555558f6e005ca3c171abbdc06ca376c73dd223f/buildSrc/src/main/resources/website
It is written in Angular and MTR 3.3.0 seems no longer upgrade.

nooo i have 0 experience to write Angular

The online system map is still a work in progress. Are there any specific changes you would like to see? Otherwise, I will close this issue, thanks.


track as label git_hash instead of git-commit

git_commit is a regular CI variable and as result we track as a label sha1 of the test project code. This particular knowledge is not so popular because in test automation multi-branching is a common and if no changes in the app then no commits in the TA code.
Let's adjust extra labels registration here: https://github.com/zebrunner/carina/blob/7631305df2a891d8d439de85f734e2b2ac75db3b/carina-core/src/main/java/com/qaprosoft/carina/core/foundation/listeners/CarinaListener.java#L228

rename everywhere including documentation git_commit -> git_hash
extra sha1 label should be registered only if git_hash is not empty
remove completely "branch" label registration and GIT_BRANCH parameter

done. changes are available in 7.3.15-SNAPSHOT. no need to do extra testing


Reuse map instance. closes #12

Also fixed existing tests and added one.
closes #12

Nice :smile:


fix:use sprintf to provide proper logs w/signoff

Notes for Reviewers
This PR fixes #11035
The logging was not done properly fix it using sprintf so that the model name is displayed at the right place rather than it showing %s
Signed commits

[x] Yes, I signed my commits.

Merge conflicts.


1.1.0 beta1: Undefined index: detailed_version_url in /themes/default/Admin.template.php

While browsing the admin interface, I ran into this (nut sure when exactly, but maybe the message below helps).
PHP Notice:
Undefined index:
detailed_version_url in [redacted]/themes/default/Admin.template.php on line 657" while reading response header from upstream,
client: [redacted],
server: [redacted],
request: "GET /index.php?action=admin;area=maintain;sa=routine;activity=version HTTP/1.1",
upstream: "fastcgi://unix:[redacted].sock:",
host: "[redacted]",
referrer: "https://[redacted]/index.php?action=admin"

(Line breaks and edits are mine.)

As the request URL suggests this happens when I access the "detailed version check" within the Admin area. On this page, no version information is provided except "ElkArte Package" in the "Your version" column. All other table cells only bear "??".
Note that I have configured the following for this PHP-FPM pool (which may be related):
php_admin_value[disable_functions] = dl,exec,passthru,shell_exec,system,proc_open,popen,curl_exec,curl_multi_exec,parse_ini_file,show_source


Pass to order assignments in dataflow order

The dataflow order for a set of assignments is a topological sort of the assignments such that for all cells, writes to their ports are ordered before the reads from their ports.

Dataflow Order
A pass that takes a set of assignments with no combinational loops and sorts them in dataflow order, i.e., an ordering where combinational inputs are written to before the respective combinational outputs are read from.
Sorting Assignments using Combinational Signals
The dataflow order of a set of assignments is defined by combinational inputs and outputs. For example, when sorting the following example where add0, add1, and add2 are both std_add.
add1.left = add0.out;
add1.right = add2.out;
add0.left = 4'd2;
add2.left = add1.out;
add0.right = 4'd1;
add2.right = 4'd3;

With std_add, we know all output ports are combinationally related to the input port and therefore all inputs of an instance must be ordered before any of the outputs.
In general, we can say that an assignments a1 is less than a2 when cell_read_set(a2) overlaps with cell_write_set(a1).
No combinational loops. To ensure that there are no combinational loops, we also require that cell_write_set(a2) does not overlap with cell_read_set(a1) which would make it impossible to define an ordering over the assignments.
Sorting with Sequential Elements
Consider the following set of assignments (where add is a std_add and r is a std_reg):
add.left = r.out;
add.right = 1'd1;
r.in = add.out;
r.write_en = 1'd1;

This set of assignments does not have a well defined ordering under the criteria defined above since these two assignments violate the no combinational loop require:
add.left = r.out;
r.in = add.out;

But of course, there is no combinational loop here since a register's output port is not combinationally using its input port. We can refine our criteria above by stating that the cell_read_set and cell_write_set operators only return combinational cells which will allow us to correctly state that these two assignments can be ordered independently from each other.
Defining Combinational Paths
The last problem with our criteria is that it is too coarse-grained because sequential cells may allow for combinational paths between their ports. For example, our core memory implementation has the following signature:
primitive std_mem_d1<"static"=1>[WIDTH, SIZE, IDX_SIZE](
  addr0: IDX_SIZE,
  write_data: WIDTH,
  @go write_en: 1,
  @clk clk: 1
) -> (
  read_data: WIDTH,
  @done done: 1
);

This signature does not specify that memories perform combinational reads and sequential writes which means that addr0 needs to be ordered before read_data but write_en and write_data can be ordered independently of read_data.
Possible Solutions
We can use the @read_together specification which defines which input ports must be driven before an output port is read. The problem with this approach is that it is not correct-by-default---in case a primitive is missing such a specification and is not defined as a comb primitive, the pass will just assume all outputs can be ordered independently from inputs which would be erroneous.
We can also use the @stable annotation will usually specifies that an output port is not going to lose its value once the inputs are stopped being driven. We can also take it to mean that it cannot combinationally rely on the value of an input port. I'm not sure if this last part is actually true since you can probably write something like:
logic [0:3] r;

if (in)
  out = r;
else
  out = r.out;

Such a port will be stable because it will always have a value but not have the required property.
The final option is using a new attribute altogether that implies a stronger property than @stable and states that an output port definitely does not change combinationally.
(CC @sampsyo @EclecticGriffin if y'all have thoughts on this. Happy to discuss it retroactively if it is closed.)

After writing this down and implementing it, I realized it's better to phrase the sorting problem as a topological sort instead of a classic array sort. This requires creating dependency edges and some representation for the graph which requires a little bit more thinking.


Deprecated method: storage.create

A developer reported that storage.create is deprecated and should be changed.
https://github.com/GoogleCloudPlatform/getting-started-java/blob/master/bookshelf/3-binary-data/src/main/java/com/example/getstarted/util/CloudStorageHelper.java#L66
b/110770153

Bookshelf is being rewritten this quarter, so this will be resolved with that.


Comments in Basic programs

While REM is supported, rem is not.  Would be nice to support both.
The single quote is used as a replacement for rem in some dialects - such as GW-Basic. Would be nice to have that.

Good catch on case-sensitivity of REM!  That was not intended.  I'll get that fixed right away.
I'm going to hold off on the single quote though, at least for now.  That's not standard enough to really fit with MiniBASIC's objectives.
Thank you for the report!

Now fixed for v0.9.3.


Created Cassandra Connector Module for Play Framework

Created a Cassandra connector module and tests for it under the new Play Framework.
All tests old and new are passing.

All the tests are now passing, there was extra code added to Postgres recently that was not added to Cassandra respectively.


dropdown: add nzArrow property to show an arrow

I will work on it since I implemented this feature in the React version of antd.


PowerToys Run uses all available RAM

Microsoft PowerToys version
0.67.0
Installation method
WinGet
Running as admin
No
Area(s) with issue?
PowerToys Run
Steps to reproduce
Running on Windows 10
PowerToys log (taken during high RAM consumption)
PowerToysReport_2023-03-03-12-27-11.zip
✔ Expected Behavior
PowerToys Run not consuming all of my RAM
❌ Actual Behavior

Other Software
No response

Did this happen only once or is it happening consistently?

/needinfo

Happened a second time. This time right after I had booted up my computer and tried to use PowerToys Run, no results would show up and now my RAM is full and pagefile disk usage skyrockets.

/dup https://github.com/microsoft/PowerToys/issues/27387


[bug] search doesn't work with no default home

mv $HOME/.helm /charts
echo $HELM_HOME
/charts/.helm
helm search stable
Error: open /.helm/repository/repositories.yaml: no such file or directory
helm search stable --home /charts/.helm
Error: open /.helm/repository/repositories.yaml: no such file or directory
helm repo list
stable    	https://kubernetes-charts.storage.googleapis.com
helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈
helm version
Client: &version.Version{SemVer:"v2.5.0", GitCommit:"012cb0ac1a1b2f888144ef5a67b8dab6c2d45be6", GitTreeState:"clean"}

I was unable to reproduce the root issue in v2.6.0:
><> mv ~/.helm/ /tmp/helm
><> export HELM_HOME=/tmp/helm/
><> helm search stable
NAME                         	VERSION	DESCRIPTION
stable/acs-engine-autoscaler 	1.0.0  	Scales worker nodes within agent pools
...

However, I was able to reproduce after I ran helm repo update, because it reads $HOME.
@cridam I would suggest upgrading to v2.5.1 first and see if that fixes the majority of your issues. I'll see what I can do about helm repo update. There were a number of $HOME-related fixes in v2.5.1 that should solve your issue.

I found that my issue occurs because the cache path in $HELM_HOME/repository/repositories.yaml contains absolute paths to cache indexes, which is loaded during repo.LoadRepositoriesFile().
><> cat /tmp/helm/repository/repositories.yaml
apiVersion: v1
generated: 2017-05-12T17:12:36.856307157-07:00
repositories:
- caFile: ""
  cache: /Users/bacongobbler/.helm/repository/cache/stable-index.yaml
  certFile: ""
  keyFile: ""
  name: stable
  url: https://kubernetes-charts.storage.googleapis.com
- caFile: ""
  cache: /Users/bacongobbler/.helm/repository/cache/deis-index.yaml
  certFile: ""
  keyFile: ""
  name: deis
  url: https://charts.deis.com/workflow
- caFile: ""
  cache: /Users/bacongobbler/.helm/repository/cache/incubator-index.yaml
  certFile: ""
  keyFile: ""
  name: incubator
  url: https://kubernetes-charts-incubator.storage.googleapis.com/

This file is written out during helm init, which is why when I mv $HELM_HOME to another directory, some repo commands may fail.
Either way this is unrelated to OPs issue. @cridam I still suggest you should update to v2.5.1 and see if that fixes things.

I confirm issues are fixed using 2.6.0 version.
Thanks !

following up with my issue in #2839.


4515 - Deactivated partners should not appear in the dropdown when producing a new distribution.

Resolves #4515
Description
When creating new distributions, the "Partner" dropdown should not contain deactivated partners.
However, when editing an existing distribution, you should still see deactivated partners.
This change is to reduce the number of errors and make it easier for the banks to create distributions.
To implement this feature, I added in a conditional check on the distribution form partial. If the "source" local variable has been passed to the partial and contains the value "new", then the deactivated partners will be filtered out of the partner list.
In any other case, the form partial will just render the full partner list associated with the bank.
This allows the bank to still edit distributions for partners that may have been deactivated since the distribution was created.
Type of change
New feature (non-breaking change which adds functionality)
How Has This Been Tested?
I first tested this manually by deactivated one of the partners.
I created a new distribution and confirmed that the partner was no longer in the dropdown.
I tried to make a new distribution but intentionally added in errors and confirmed that it would still properly filter out deactivated partners on a re-render.
I tried to edit some existing distributions and confirmed that the deactivated partners still showed up on the list.
I also created unit tests that are located in spec/system/distribution_system_spec.rb
Screenshots
New distribution after error filters out Pawnee Parent Service

Editing an existing distribution still allows you to select Pawnee Parent Service

I've made those updates!

Looks good now!


python_script too restricted

Home Assistant release (hass --version): 0.48.1
Component/platform: python_script
Description of problem: The python_script execution environment is too restricted. As it is not allowed to import libraries, it can't be used for many use cases. E.g. if some calculations are needed, the "math" library needs to be imported. This isn't allowed at the moment
Expected: Whiteliste a number of libraries that can be accessed by python_script
Problem-relevant configuration.yaml entries and steps to reproduce:
python_script:

from math import log10
Traceback (if applicable):
2017-07-10 10:45:50 ERROR (Thread-9) [homeassistant.components.python_script.air_control.py] Error executing script: __import__ not found
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/dist-packages/homeassistant/components/python_script.py", line 107, in execute
    exec(compiled.code, restricted_globals, local)
  File "air_control.py", line 2, in <module>
ImportError: __import__ not found

Additional info:

Covered in the python_script feedback thread.


Add src-git MR <-> dist-git MR relation to db

This is also needed to be able to have source-git repos and dist-git repos on a different GitService, which is the case for Fedora, where the source-git repos will (initially?) be in https://gitlab.com/fedora/src while dist-git repos remain in https://src.fedoraproject.org/rpms

Currently, we have 2 handlers

DistGitMRHandler reacts to source-git MR and creates dist-git MR.
PipelineHandler (name will probably change) reacts to the created dist-git MR and updates the original source-git MR. It currently knows only id of the original source-git MR as it expects that both MRs and on the same git forge, but that will change with the source-git service for Fedora.

The task here is to:

Design how the source-git MR <-> dist-git MR relation will be modeled in the DB. The information will be later (#44 ) used in the PipelineHandler as it needs to know where is the source-git MR to update.
Ideally, the new model(s) would be added to hardly only, to not touch any models in packit-service, because they don't need this. Please discuss with our DB design guru @lachmanfrantisek
At the end of DistGitMRHandler.run() when the new dist-git MR has been created, store the info in DB

dg_mr contains newly created dist-git PullRequest
mr_url contains url of the original source-git MR as it was parsed as MergeRequestGitlabEvent in Parser.parse_mr_event()

For context, here is a spike result with the plans we have for the database.


clarify comment

What does module accomplish that
cont app = feathers();

if(process.env.NODE_ENV === 'server-production') {
  app.configure(rest());
} else {
  const socket = io();
  app.configure(socketio());
}

Doesn't already do?

@daffl, nothing, really, other than provide a clean API for doing the same thing.


[aws][cloudformation] Updates Refinery to 1.20

Short description of the changes

Picking up Refinery 1.20 and all the new config options
Updates AL2022 to AL2023
Hostmetrics 1.50 -> 1.70
Re-ordering the YAML for readability rather than idealized (but totally unnecessary & false) resource creation order

okay @tdarwin I just went through a few rounds of testing on this, and I feel good about it.   stamp pls?


Question 02-Use-prompt-flow.md

Module: 02
Lab/Demo: 00
Task: Configure
Step: 07
Hey,
first of all: thank you for creating this repo.
I'm currently going through module 2 and try to set up a prompt flow. Unfortunately though, I can't select the two Inputs in the LLM-Node after validating and parsing the input (please see screenshots below), as they don't seem to be available in it. Did I do something wrong? Any suggestion?
Thank you!
Fabian

Hey, just figured out that I don't should copy {% raw %} and {% endraw %} with it. If I remove raw and endraw it works as expected.


Add tests for current filter types and refactor filter creation

There will need to be some manual testing but I think I got all the various filters and test added before the refactor.
Need to double check filters created from controls I think that is what this code block was from
                if filter_key == "query":
                    filt_index = list(f.get(filter_key))[0]
                    filter_dict["must_not"].append({filt_index: f.get(filter_key).get(filt_index)})

when the object nested under query wasn't bool and the key wasn't provided

@natebynum20 This is ready for review and merge. It fixes three issues.

not all filter cases where being parsed correctly
if a bad filter was sent like

{
 "exits": {
   "field": "name"
 }
}

the datashader would immediately have the client try again causing valid requests to get interrupted when gunicorn shuts down the worker after x number of requests to clean up memory leaks.
3. the cleanup cache code wasn't cleaning up empty directories this would lead to a build up of directories that would eventually cause glob to take longer than the default gunicorn timeout eventually putting datashader in a state where it wouldn't start up (this would take a month or two)

Nate, Did you have a chance to double check the commits after you approval?

Just went over the commits that were submitted after my initial approval. Looks good from my stand point


School Data on Map

Used schools.geojson to get school data on the map.
Filter by school type
Basic formatting and legend

This is fantastic, huge props man! I'll get this pulled in tonight!

Thanks.
#21

I rebased this from most recent master and merged in that way. Looks great!


Library Name

Sorry for the delay in getting this put together.
This pull request incorporates two different approaches. The two different commits show each of the approaches.
The first approach is simply a string parameter passed to singleSpaAngularWebpack. To be backwards compatible, it falls back to trying to get the project name from angular.json. If that fails, it uses a default value, and prints a warning message that explains why a default value might be undesirable, and a link to information on how to fix it.
The second approach is similar, but uses a property defined in angular.json. It has equivalent fallback to the first approach. For this second approach, I've also shown an example of another property (libraryTarget) that might be helpful, especially since that was supported back pre-Angular 8 builder.
Once we finalize the approach we want to take, and get this into mergeable shape for the 4.x branch series, I'll backport it to 3.x. (See the 3.xLibraryName branch in my fork if desired).
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)

Not clear what the best way to even approach automated testing would be. Trying to parse the webpack output seems like a bad idea. I suppose technically setting something up to try to pull it in via named amd could work, but that feels obnoxious at best.
PR Type
What kind of change does this PR introduce?

[x] Feature

What is the current behavior?
Issue Number: #220
Does this PR introduce a breaking change?

[x] No

@arturovt do you have time to review this one?

Fixed several of the mentioned things.
Also switched the require(angularJsonPath) to JSON.parse(fs.readFileSync(angularJsonPath, 'utf8')) since that is more explicit about what we are doing, and avoids a lint suppression.

Any update on this? Switching to @angular/cli/utilities/find-up seems to be the last item to be addressed?

Yeah. Sorry, I've gotten a bit busy, and have not had a chance to make that
change and push it. I'll try to make time for it this evening.
On Wed, Jul 1, 2020, 12:21 Joel Denning<EMAIL_ADDRESS>wrote:

Any update on this? Switching to @angular/cli/utilities/find-up seems to
be the last item to be addressed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/single-spa/single-spa-angular/pull/229#issuecomment-652517307,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAWEZJC65CCJ2PNKM27CE3RZNO7FANCNFSM4OD7OLNA
.

I've pushed up a simplified version that uses '@angular/cli/utilities/find-up'.
The only reason I've still left this marked as a draft is that it links to a part of the documentation that does not yet exist:
https://single-spa.js.org/docs/ecosystem-angular/#use-custom-webpack
This would be a new section similar to the existing "Use Angular Builder" that documents these two options from angular.json, and explains how to make sure you are passing the options through in custom-webpack.config.js, probably by simply showing these two lines from the template:
module.exports = (config, options) => {
  const singleSpaWebpackConfig = singleSpaAngularWebpack(config, options);

Or even quoting the whole template since it is only 8 lines long.
I won't have a chance to draft up that documentation section tonight.

Hey @KevinCathcart
Can I ask you not to squash commits? It's really hard to review what has been changed since the last commit and also it doesn't bring any benefit since we squash them when merging.

@arturovt do you have any other comments on this before we merge?

Ok cool. I'd be happy to create a PR that cherry picks this into 3.x this
evening. Having already tried that, I know it is not quite a clean merge,
but there is no significant difficulty there. (Biggest issue is some of the
files moved in a way that git failed to detect. Also a a few small linting
and lack of type annotation differences.)
On Thu, Jul 2, 2020, 11:58 Joel Denning<EMAIL_ADDRESS>wrote:

@joeldenning approved this pull request.
This looks good to me. We should also try to put together a fix for the
3.x branch for Angular versions 2-8.
Also, I am okay with merging this in before the documentation is authored
and merged.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/single-spa/single-spa-angular/pull/229#pullrequestreview-441827193,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAWEZJA2D5RKORJOKRAVIDRZSVDLANCNFSM4OD7OLNA
.

I put together the documentation for this at https://github.com/single-spa/single-spa.js.org/pull/293. @KevinCathcart could you review that pull request?

👍 I'll merge and publish this tomorrow morning.

This is released in https://github.com/single-spa/single-spa-angular/releases/tag/v4.3.1
@KevinCathcart if you're up to PR'ing the 3.x branch for Angular versions 2-8, that would be greatly appreciated! Thanks again for your work on this - was a high quality PR.

Oops I just saw https://github.com/single-spa/single-spa-angular/pull/236 where you have already created the PR for the 3.x branch. Thanks!

The 3.x version is PR #236
On Sun, Jul 5, 2020, 23:46 Joel Denning<EMAIL_ADDRESS>wrote:

This is released in
https://github.com/single-spa/single-spa-angular/releases/tag/v4.3.1
@KevinCathcart https://github.com/KevinCathcart if you're up to PR'ing
the 3.x branch for Angular versions 2-8, that would be greatly
appreciated! Thanks again for your work on this - was a high quality PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/single-spa/single-spa-angular/pull/229#issuecomment-653999816,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAWEZP2JUH6TQENDFLOQ73R2FCJ3ANCNFSM4OD7OLNA
.


Validation for enabling project community could fail when an Admin Group is assigned to it

Create a non-community project group and add at least 1 member/admin to it so there are 2+ admin/members in that group
Assign the new group to a non-community project
Try to elevate project's community to the protected status

The follow error happens for /admin/projects/<project-id>/validateEnablingCommunity endpoint:
org.springframework.dao.IncorrectResultSizeDataAccessException: Query did not return a unique result: 2 results were returned
	at skills.services.admin.UserCommunityService.validateProjectForCommunity(UserCommunityService.groovy:167) ~[!/:3.2.0-SNAPSHOT]

PR: #2989

:+1:


Add Tweag open source programme

https://www.tweag.io/posts/2020-02-14-os-fellowship.html

Hello @palash25
I would like to work on this issue.


wrong run getting shown

I just started a new run. The "logs" section is are correct, showing it on first epoch, but the graphs show 500 minutes worth of data, wondering where this metrics are coming from.
There's an earlier run with same name, but I didn't think this should matter
https://app.wandb.ai/yaroslavvb/Transformer-XL source code/runs/mn6ancca?workspace=user-yaroslavvb

The graphs seems to have refreshed and are now showing correct metrics for this run

It's happening again, just launched a fresh run, and the graphs are showing 500 minutes worth of data which are definitely not generated by this run. Checked in incognito window, showing same thing.
https://app.wandb.ai/yaroslavvb/Transformer-XL source code/runs/1twzi1oq?workspace=user-yaroslavvb

The logs are correct though

Checking 10 minutes later, and the wrong metrics disappear.

Oh....it's "Time" switching from seconds to Minutes, it wasn't actually 500 minutes worth of data


python312Packages.faraday-plugins: 1.19.1 -> 1.20.0

Diff: https://github.com/infobyte/faraday_plugins/compare/refs/tags/1.19.1...1.20.0
Changelog: https://github.com/infobyte/faraday_plugins/releases/tag/1.20.0

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 358105

x86_64-linux

:white_check_mark: 8 packages built:

faraday-agent-dispatcher
faraday-agent-dispatcher.dist
faraday-cli
faraday-cli.dist
python311Packages.faraday-plugins
python311Packages.faraday-plugins.dist
python312Packages.faraday-plugins
python312Packages.faraday-plugins.dist


Introduce a new L1 test attribute 'hardware'

There should be a way to specify test's (L1) requirements for the HW, similarly to [1].
I propose test's attribute hardware with basically the same properties as described in [1].
In particular:
hardware:
    # Basic key-value format used to specify the memory size
    memory: 8 GB

    # Processor-related stuff grouped together
    cpu:
        processors: 2
        cores: 16
        model: 37

      # Disk group used to allow possible future extensions
    disk:
        space: 500 GB

    # Optional operators at the start of the value
    memory: '> 8 GB'
    memory: '>= 8 GB'
    memory: '< 8 GB'
    memory: '<= 8 GB'

    # By default exact value expected, these are equivalent:
    cpu:
        model: 37
    cpu:
        model: '= 37'

    # Enable regular expression search
    cpu:
        model_name: =~ .*AMD.*

    # Using advanced logic operators
    and:
      - cpu:
            family: 15
      - or:
          - cpu:
                model: 65
          - cpu:
                model: 67
          - cpu:
                model: 69

https://tmt.readthedocs.io/en/stable/spec/plans.html#hardware

There's also a need for HW virtualization. This could be handled by a separate platform attribute or o cpu property.
Currently I can think of two way to express this.
hardware:
    cpu:
        virtualization: true

hardware:
    capabilities:
      - virtualization

So the hardware requirements would be gathered from individual tests and then subplans created for each hardware-compatible group as proposed in #308? It would make sense to me to keep the L1 and L2 specification for hardware requirements identical. @thrix, @happz, any thoughts or recommendations about this?

Both outlined options for hardware virtualization requirement seem good to me. @sopos, which other capabilities could be possibly provided in the section in the future? Are there any tangible examples?

Both outlined options for hardware virtualization requirement seem good to me. @sopos, which other capabilities could be possibly provided in the section in the future? Are there any tangible examples?

I do not have anything else to provide as an example. It just came to my mind when I was thinking of the best place for such information. As specifically virtualization is basically a property of CPU but it may be considered as a property of a machine as well.

Actually, what about presence of a TPM chip, it may be considered as a capability as well. And we have tests which need the TPM.

+1 on making it identical, of course I believe we should first land the plan support, following with the test support later on, as that will require a lot more changes? Are this subplans already something working?

+1 for keeping L1 and L2 specifications virtually the same.
As the relationship between L1 and L2 goes, I'd expect - naively... - some sort of inheritance, e.g. when executing a plan, tmt should probably collect L1 requirements, spawning either one plan to satisfy all or several plans for each L1 set incompatible with other requirements. I would like to avoid copy-pasting L1 requirements to L2, or merging them manually. But I suppose that's out of the scope of this particular issue - L1 hardware should be a thing no matter how the actual L1/L2 workflow would look in the future.
I'd just recommend keeping the addition of the virtualization flag for a stand-alone patch. BTW what kind of virtualization is this flag for, an environment that is capable of virtualization, or an environment that is - or better is not - virtualized itself (aka "I need a bare-metal machine")?

Are this subplans already something working?

No, for now the idea is only outlined in #308. But we would like to implement soon the first step in this direction: Splitting a single plan into multiple plans each cotaining a single test, which is basically something like wow --slice 1.

I'd just recommend keeping the addition of the virtualization flag for a stand-alone patch. BTW what kind of virtualization is this flag for, an environment that is capable of virtualization, or an environment that is - or better is not - virtualized itself (aka "I need a bare-metal machine")?

Good question. I kind of hoped that I made it self-explanatory. We may need to make it better. :-)
The intention is to specify a need of the virtualization feature. E.g. I want to spin up some VMs as a part of a test.
If I request a machine with cpu: {virtualization:true} I'm basically asking for a machine where the CPU allows me to do so. With the capability: [virtualization] it may be more obvious that I need a HW capable of virtualization.
But actually, to express a need for virtualized machine one could define something like capability: [virtualized]. This could be useful mainly in kernel team where they need to run tests on bare metal as well as in virtualized env.
Finally, I may require capabilities: [virtualization, virtualized] which would basically say I want a VM with nested virtualiyation turned on.
To allow also negative requirement it might not be a list but a list of dicts:
hardware:
    capabilities:
      - virtualization: false
      - virtualized: true

Meaning give me a VM with nested virtualization turned off.

I suppose this follow-up discussion deserves its own issue, but since we already started...
Just a few thoughts while looking at Beaker as an example, the "need bare-metal" request can be specified with Beaker XML in this way:
VIRT__BAREMETAL                                 <system><hypervisor op="==" value="" /></system>
VIRT__KVM                                       <system><hypervisor op="==" value="KVM" /></system>
VIRT__XEN                                       <system><hypervisor op="==" value="Xen" /></system>
VIRT__POWERKVM                                  <system><hypervisor op="==" value="PowerKVM" /></system>
VIRT__POWERVM                                   <system><hypervisor op="==" value="PowerVM" /></system>
VIRT__HYPERV                                    <system><hypervisor op="==" value="HyperV" /></system>
VIRT__VMWARE                                    <system><hypervisor op="==" value="VMWare" /></system>

Seems like the provisioning plugins and the whole HW area should be aware of the "hypervisor" property of the environments they can provide, which makes sense, and they really should be aware of this kind of property. Supporting a yes/no "shortcut" - as a user, I really dislike "magic" values like "empty hypervisor means bare-metal, you silly sausage", therefore is-virtualized key in HW requirements is very welcome, to shield me from this kind of details.
I'd still like to be able to test the hypervisor property on its own, but to find out whether it's "none" vs. "any"? Nah, rather give me is-virtualized flag.
The "need virtualization" request is handled like this:
MACHINE_SET__VIRT_SUPPORT  <and><key_value key="HVM" op="=" value="1"/><memory op=">" value="2047"/><diskspace op=">" value="19999"/><system_type value="Machine"/></and>

Seems to contain some additional filters, but depends on one machine property known to Beaker. Maybe there are other implementations (well, I'm pretty sure there must be), so I'd stay clear from supporting {capabilities: {hvm: true}} as means of requesting virtualization support.
I like the capabilities idea, it should work well in grouping this kind of request, things that could be queried in another way, but with more work or not fully. For example, I suppose I could construct a request:
and:
  - hypervisor: "!= kvm"
  - hypervisor: "!= xen"
  # and so on...

but I find that quite repulsive, it'd hardly be complete... So, yes:
capabilities:
  is-virtualized: true|false

looks better to me. Maybe we could define the hypervisor right away when adding the virtualization part, so people could do this:
capabilities:
  is-virtualized: true
hypervisor: "!= xen"

My point is that since the provisioning should be aware of whether the environment is virtualized or not, knowing how is this achieved and what moving pieces are in play should naturally be part of that understanding.
(Disclaimer: bikeshedding...): I'm not sure which of these would be better:
arch: x86_64
capabilities:
  is-virtualized: true
  virtualization: true

# or

arch: x86_64
is-virtualized: true
virtualization: true

After all, all those flags are some sort of capabilities... One of them is real, the other is some reflection or extract of other capabilities and/or properties. I suppose we could argue in favor of both, it's very, very hard to decide, aargh! :)

After all, all those flags are some sort of capabilities... One of them is real, the other is some reflection or extract of other capabilities and/or properties. I suppose we could argue in favor of both, it's very, very hard to decide, aargh! :)

Yeah, both approaches seem to be valid and... fine. On the other hand, not completely sure that is-virtualized is actually a capability at all. Perhaps feature would be general enough to embrace all kinds of properties and capabilities and... features?
Or we can just forget about the extra level. Let's finalize the discussion about these two keys in the #895 pull request.

Is there a list of what hardware can be specified? Also is there any idea of what is going to be used for system inventory (beaker-system-scan, or something else)? I'd like to see the inventory tool do a better job of identifying systems that have an iommu/smmu.


Add tooling support for configurable

Description:
Add tooling support for the configurable feature introduced by #26826
Related Issues:
#26729

Added the Keyword suggestions and the module suggestions. Hence closing the issue


Missing Universal C runtime CRT

Hello,
I facing this error on  latest  windows 10 version
Missing Universal C runtime CRT.
Any solution?

see https://github.com/bitbeans/SimpleDnsCrypt/issues/160


Checkpoint

Thanks for make the code open. It is very helpful for me. But, I run the kemp_best checkpoint,  it doesn't work. I want to make sure that the checkpoint is really right? Because its size is only 27.2MB, so, I hope you can upload the true checkpoint.

Hi, thanks so much for your information. Now I cannot access the server of the past. I retrain a checkpoint and substitue the crashed checkpoint file in the google drive.  Hope that helps.


[Transactions] Pulsar Admin: peekMessages is returning a wrong message, dealing with non empty list of individuallyDeletedMessages

Describe the bug
I have a topic 'MY_QUEUE' with one subscription 'jms-queue' that ends up in this situation
peekMessages against 'jms-queue' is returning 74:37:-1
but the next available message should be 74:62
pulsar-admin topics stats-internal MY_QUEUE
{
  "entriesAddedCounter" : 64,
  "numberOfEntries" : 64,
  "totalSize" : 13634,
  "currentLedgerEntries" : 64,
  "currentLedgerSize" : 13634,
  "lastLedgerCreatedTimestamp" : "2021-06-21T11:14:38.402Z",
  "waitingCursorsCount" : 1,
  "pendingAddEntriesCount" : 0,
  "lastConfirmedEntry" : "74:63",
  "state" : "LedgerOpened",
  "ledgers" : [ ],
  "cursors" : {
    "jms-queue" : {
      "markDeletePosition" : "74:36",
      "readPosition" : "74:64",
      "waitingReadOp" : false,
      "pendingReadOps" : 0,
      "messagesConsumedCounter" : 58,
      "cursorLedger" : 75,
      "cursorLedgerLastEntry" : 29,
      "individuallyDeletedMessages" : "[(74:37..74:38],(74:39..74:40],(74:41..74:42],(74:43..74:44],(74:45..74:46],(74:47..74:63]]",
      "lastLedgerSwitchTimestamp" : "2021-06-21T11:14:38.498Z",
      "state" : "Open",
      "numberOfEntriesSinceFirstNotAckedMessage" : 28,
      "totalNonContiguousDeletedMessagesRange" : 6,
      "subscriptionHavePendingRead" : false,
      "subscriptionHavePendingReplayRead" : false,
      "properties" : { }
    },
    "transaction-buffer-sub" : {
      "markDeletePosition" : "74:-1",
      "readPosition" : "74:0",
      "waitingReadOp" : false,
      "pendingReadOps" : 0,
      "messagesConsumedCounter" : 0,
      "cursorLedger" : -1,
      "cursorLedgerLastEntry" : -1,
      "individuallyDeletedMessages" : "[]",
      "lastLedgerSwitchTimestamp" : "2021-06-21T11:14:40.444Z",
      "state" : "Uninitialized",
      "numberOfEntriesSinceFirstNotAckedMessage" : 1,
      "totalNonContiguousDeletedMessagesRange" : 0,
      "subscriptionHavePendingRead" : false,
      "subscriptionHavePendingReplayRead" : false,
      "properties" : { }
    }
  },
  "schemaLedgers" : [ ],
  "compactedLedger" : {
    "ledgerId" : -1,
    "entries" : -1,
    "size" : -1,
    "offloaded" : false,
    "underReplicated" : false
  }
}

After calling "peekMessages" my code creates a Reader at that position, and it writes (correctly)
INFO org.apache.pulsar.client.impl.ConsumerImpl - [persistent://public/default/MY_QUEUE][reader-f65efe6431] Successfully getLastMessageId 74:62
There must be some problem in dealing with individuallyDeletedMessages, but I see in ManagedCursorImpl that this case should be handled well.
https://github.com/apache/pulsar/blob/76d3426b72a79ee9f8812fa66e45239830ff1c80/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/ManagedCursorImpl.java#L647
To Reproduce
I do not have an easy way to reproduce this problem.
Currently it happens while running the JMS TCK against the Pulsar JMS client using Pulsar 2.8.0 server.
I have seen that the system is in this messed situation after running the part of TCK about "transactions".
But I am able to reproduce the problem consistently.
Expected behavior
peekMessages should return the next message that is to be read by the subscription.

The problem is that we have holes in the individuallyDeletedMessages.
I have to try to reproduce this problem with a simple reproducer.
It may be related to transaction rollback, because I reproduce this situation only after running some tests about transactions

I am continuing my investigation and it looks like when I send messages using a transaction the 'commit' operation uses a messageId.
So:

create transaction 1
send message using transaction 1, message id is for instance 3:0:-1
commit transaction 1
create transaction 2
send message using transaction 2, message id is for instance 3:2:-1
commit transaction 2

so message 3:1:-1 does not exist, and when a consumer tried to acknowledge the messages the subscriptions ends up in this state in which there are systematically holes and the individuallyDeletedMessages keeps growing and peekMessages is not able to report the correct value.
I am trying to create a reproducer as a test case in current Pulsar master branch

@congbobo184 Could you please help take a look at this issue? Looks like related to the transactions

now, transaction delete marker is an asynchronous operation, if new messages continue produce and ack message continue, there will not produce problem. in some race condition, ack message1 the delete marker in process and ack message2 will not in delete marker process, in this time the producer don't send new message to broker and will not process the ack operation. the sub may not delete the message1 commit marker. So we should start a timer task in broker to check the sub delete transaction marker.


Add Chinese Simplified lang

As the title suggests

I have a question, where should I add translations for other interfaces?


ACM-10985 Remove .tekton dir from main

https://issues.redhat.com/browse/ACM-10985

Clean up .tekton dir from main as it's not needed

/approve

/approve
/lgtm


Create an API for Curve limit order bot

https://github.com/VolumeFi/curve-limit-order-bot-script
We need to create a service API using this repository.
And we need to create a new Paloma account for it, set the mnemonic key, and fund the account.

Completed.


Simplify installation instructions

I order to follow my own development process & rules, I have edited the commit comment, but otherwise integrated your submission unchanged here:
commit e76a3bdb8e0a3ae662fc7a3a45d8d6de0bd5efcb
Author: Alexey Palazhchenko<EMAIL_ADDRESS>Date:   Wed Apr 20 10:15:33 2016 +0400
fixes #44 Simplify installation instructions

Thanks for your contribution!


Could not find appliance D828C99CE098 in known device list

For some reason my integration started complaining and throwing this error in the logs every now and then.
I don't know where this is coming from since my appliance ID is different. Also I can't find any entities for D828C99CE098.

2024-03-04 20:26:39.930 WARNING (MainThread) [custom_components.ge_home.update_coordinator] Could not find appliance D828C99CE098 in known device list.

I would like to get rid of this annoying error, thank you!

I get the same error for an unknown reason.

I am experiencing the same issue with my washer and dryer as well.

I see the same error message, different device ID.  I have a GE Oven.

This is normal, at some point I can change it to info level but it's not a high priority.  Feel free to submit a PR on it if you'd like.


[Event Request] Report 99003803 Copy Production Forecast - dataitem "Production Forecast Entry" trigger OnPreDataItem - OnBeforePreDataItemProductionForecastEntry

Please add the following existing Event OnBeforePreDataItemProductionForecastEntry to dataitem "Production Forecast Entry" trigger OnPreDataItem in Report 99003803 Copy Production Forecast
	trigger OnPreDataItem()
	begin
	    ToProdForecastEntry.TestField("Production Forecast Name");
	    IsHandled := FALSE;
            OnBeforePreDataItemProductionForecastEntry(IsHandled); <-- NEW EVENT
            if not IsHandled THEN <-- NEW CODE
		    if not Confirm(Text000, false) then
			    exit;

	    LockTable();

	    LastEntryNo := ProdForecastEntry2.GetLastEntryNo();
	    NextEntryNo := LastEntryNo + 1;
	end;

[IntegrationEvent(false, false)]
local procedure OnBeforePreDataItemProductionForecastEntry(VAR IsHandled : Boolean)
BEGIN
END

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 52577.


Why not use grid_sample?

I think the function in PyTorch grid_sample can get the value given the position, and that may be more convenient

Good suggestion!

I think the function in PyTorch grid_sample can get the value given the position, and that may be more convenient

Good suggestion!


Update http4s-blaze-client, http4s-circe, ... to 0.21.24

Updates

org.http4s:http4s-blaze-client
org.http4s:http4s-circe
org.http4s:http4s-client
org.http4s:http4s-dsl

from 0.21.1 to 0.21.24.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Migrations

dependency:v0_21@org.http4s:http4s-scalafix:0.21.5

Documentation:

https://github.com/http4s/http4s/releases/tag/v0.21.5

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, semver-patch, scalafix-migrations

Superseded by #202.


feat: show error when accessing variables not exposed in CJS build

Description
No error happened when accessing variables not exposed in CJS build. This PR adds an error for that, so the user can know what is needed to do.

Added that check (fbcfc1c0acac70f15cfa1a371c9c9efef26f7b85) 👍


webpage not found- Error 404

Here is the link that I think is not implemented or not routed properly  : https://keras.io/api/layers/advanced_activations

It's located at: https://keras.io/api/layers/activation_layers/
Fixing the wrong link now.


drive: add new command 'about' to get quota info from a remote

I have tried to implement a new rclone command called about that fetches quota information from a remote (it only works with Google Drive at the moment). My main motivation behind this was a colleague of mine who requested this feature; other users have expressed a similar interest in #1138 and #1564.
The command output looks like this:
$ rclone about gdrive:
Quota: 15 GiB | Used: 5.6 GiB (Trash: 0.0 GiB) | Available: 9.4 GiB | Usage: 37%
Space used in other Google services (such as Gmail): 0.05 GiB

With no previous knowledge of Go programming I relied on reading up earlier pull requests and their corresponding commits to get an idea about how such a feature could be added to rclone. As such, my attempt is probably a bit amateurish so please forgive any mistakes you may spot. Having said that, I did try to follow the 'Contributing to rclone' document and actually ran the unit tests for the remote I modified (there were a few SKIPs but the rest PASSed).
One thing that's unclear to me is whether I need to add a file under docs/content/commands for the about command. The existing files contain the line Auto generated by spf13/cobra so I guess there's a script that creates them automatically?

It looks like I can only get the Travis CI build to succeed partially (apparently, some build jobs are failing due to golint errors). Apologies for not spotting these earlier: my system's (Debian 9) Go version is too old (1.7.4), so the source quality checks were skipped when I ran make check. I'll try to install the 1.9.4 release from golang.org and try again.

One thing that's unclear to me is whether I need to add a file under docs/content/commands for the about command. The existing files contain the line Auto generated by spf13/cobra so I guess there's a script that creates them automatically?

You don't - these are automatically generated by make commanddocs and I don't generally update them  except during the release.
I've looked at the code you've done and it looks very good :-)
I have some comments I'll write here

there needs to be a pass-through implementation for crypt too.
The about interface should either take an io.Writer or return a string (see below for some other ideas)
note there is rclone cachestats which could potentially be folded into about

What do you think of taking the level of abstraction up a little?  Rather than just getting the About() methods to print things, return some more structured info.
You can be sure that the next request will be to return things in machine readable format!  I can see a --json flag request  ;-)
Looking at https://github.com/ncw/rclone/issues/1564#issuecomment-318887660 I had the idea that this should be returning a struct with a superset of all possible info.
So something like this, which returns the specific info, but also has room for extra stuff.  The about command can then print this in a sensibly formatted way (I'd suggest reasonably machine parse-able). Having an About command which returns machine readable data would mean that for instance sync could use it to check the data would fit and rclone mount could use it to return a sensible bytes free and available`.
type Usage struct {
	Total   int64                  // quota of bytes that can be used
	Used    int64                  // bytes in use
	Trashed int64                  // bytes in trash
	Other   int64                  // other usage eg gmail in drive
	Free    int64                  // bytes which can be uploaded before reaching the quota
	Text    []string               // lines of freeform text to show the user
	Values  map[string]interface{} // extra data that doesn't fit into the above
}

Note that you can print those int64 by casting them to a fs.SizeInfo and they will print neatly.
That would make the Abouter interface About() (*Usage, err)
Thoughts?

I've looked at the code you've done and it looks very good :-)

Thank you for your feedback. I was merely mimicking CleanUp() and copying/pasting code here and there ;-)

Thoughts?

I agree that About() should return some more structured info instead of just printing strings. Your idea of other parts of rclone using the data from the struct for their own purposes is also very cool -- I hadn't thought about that.
However, having battled with this on and off over the last few days I've made very little progress. For the most part I've been reading up on Go programming principles (things like the Go Bootcamp book, gobyexample.com, etc.) and also perusing the rclone source code to get an idea about how to implement a function that does what you suggested.
It looks like the next step is a bit more complicated; I'm determined to pursue this further but I think it's going to require a fair amount of hand-holding...
For example, my questions at this stage are:

What is meant by "pass-through implementation" in a Go (or even rclone) context?
I've changed the Abouter interface to About() (*Usage, err) in fs/fs.go and also added the Usage struct definition in the same file. I've also modified the About() function signatures and corresponding return statements in backend/cache/cache.go, backend/drive/drive.go and fs/operations/operations.go.
Building the project now yields the following message: # github.com/ncw/rclone/cmd/about | src/github.com/ncw/rclone/cmd/about/about.go:24:4: too many arguments to return | have (*fs.Usage, error) | want (error)
Looking at the other cmd.Run() calls in cmd/<command>/<command>.go they all have a fourth argument of func() error, so how to fix this?

It looks like the next step is a bit more complicated; I'm determined to pursue this further

Great!

What is meant by "pass-through implementation" in a Go (or even rclone) context?

The crypt and cache backends wrap other remotes.  This means you need to pass through the About call to the wrapped remote.
It would end up being quite simple probably, just something like this
// About returns info about a remote
func (f *Fs) About() (*fs.About, err) {
	return f.Fs.About()
}

Actually reading the code again, you don't need to so that.  Because the wrapped Fs is embedded in crypt.Fs its About method will be visible directly.

Building the project now yields the following message: # github.com/ncw/rclone/cmd/about | src/github.com/ncw/rclone/cmd/about/about.go:24:4: too many arguments to return | have (*fs.Usage, error) | want (error). Looking at the other cmd.Run() calls in cmd//.go they all have a fourth argument of func() error, so how to fix this?

Not sure I understand exactly what is happening without seeing the code.  Remember you now need to print what is in the *About in the cmd/about/about.go - I expect you are trying to return it...

@a-roussos I see you haven't had time to work on this recently - would you like me to finish off this pull request?
In the mean time I've rebased it and stuck it in the about branch
Here is a beta based off it
https://beta.rclone.org/v1.40-085-g76dd198d-about/ (uploaded in 15-30 mins)

I just tried Nick's beta on Ubuntu X86-64.
I have an unlimited gdrive and get some rather odd looking output so maybe a bit of sanity checking is needed.  (For all I know it's google themselves returning these numbers.)
Quota: 0 GiB | Used: 7920.3 GiB (Trash: 0.0 GiB) | Available: -7920.3 GiB | Usage: -9223372036854775808%
Space used in other Google services (such as Gmail): 0.00 GiB

This looks really really good. For reference, I came here from https://forum.rclone.org/t/feature-request-cloud-storage-quota-querying/5393.
$ ./rclone about asmqb7:
Quota: 15 GiB | Used: 6.0 GiB (Trash: 0.0 GiB) | Available: 9.0 GiB | Usage: 40%
Space used in other Google services (such as Gmail): 0.74 GiB

I can immediately file a minor bug with this command however: forgetting the colon (which I may or may not have done the first time I tried the new command) breaks in fascinating ways.
$ ./rclone about asmqb7
2018/04/16 12:06:05 ERROR : Attempt 1/3 failed with 0 errors and: Local file system at /data/rclone-v1.40-085-g76dd198d-aboutβ-linux-386/asmqb7 doesn't support about
2018/04/16 12:06:05 ERROR : Attempt 2/3 failed with 0 errors and: Local file system at /data/rclone-v1.40-085-g76dd198d-aboutβ-linux-386/asmqb7 doesn't support about
2018/04/16 12:06:05 ERROR : Attempt 3/3 failed with 0 errors and: Local file system at /data/rclone-v1.40-085-g76dd198d-aboutβ-linux-386/asmqb7 doesn't support about
2018/04/16 12:06:05 Failed to about: Local file system at /data/rclone-v1.40-085-g76dd198d-aboutβ-linux-386/asmqb7 doesn't support about

My guess is that something's trying to assume the parameter is a local path.
Notwithstanding general heuristic error handling (something for the future), I'd probably handle this by bombing out and insisting on a colon rather than accepting no colon just for this command - unless someone can think of something about could do with local directories/files? Reporting something like "this is a local sync directory, it's such-and-such in sync with this remote" comes to mind, but the amount of implicit state and duct tape I'm imagining would be needed for such a feature does scare me off a little.

I can definitely +1 the idea of JSON reporting for this command. I could easily see myself using it.

@turly: My guess is that unlimited gdrive accounts return interesting JSON (a vague scan-over of the documentation recently suggested there may be no quota field (very nice)). It would be useful to get an unambiguous example of exactly what the JSON looks like in this case, and fetching it directly is actually quite straightforward thanks to Google's API explorer:

Head over to https://developers.google.com/drive/v3/reference/about/get, and scroll down to the Try section

Drop down "Show standard parameters", and put storageQuota in fields (the UI says "no method-level parameters", I'm unsure if this is a bug since this parameter is required)

If you wish, you can drop down "Show scopes" and deselect all but https://www.googleapis.com/auth/drive, which is the only required scope for this API call

When you hit Execute you'll get an OAuth popup, which may ask you which Google account to proceed with if you have more than one
(NB. In some cases the OAuth flow doesn't provide a way to "go back" and switch accounts if you pick the wrong one. If you hit this edge case, the simplest solution (besides clearing cookies) is probably Incognito.)

Let us see the JSON that gets returned - for example, mine looks like

{
 "storageQuota": {
  "limit": "18253611008",
  "usage": "771845240",
  "usageInDrive": "238462557",
  "usageInDriveTrash": "0"
 }
}

Which, for context, corresponds to 17GB quota, 736.1MB used total, 227.4MB used by Drive (and a tidy trashcan :P).

@turly - I have a very good idea of what is happening here!  I suspect it is signed vs unsigned 64 bit integers coerced to floating point doubles.  Anyway, can you run the command with -vv --dump bodies and paste the bit of JSON that @i336 suggests above which mentions storageQuota.

Sorry, I should have thought of doing that:
77
{
 "storageQuota": {
  "usage": "8505366693932",
  "usageInDrive": "8505366693932",
  "usageInDriveTrash": "1628"
 }
}

0

Hi @ncw! Yes, if you could finish off this pull request it would be great. Thank you!

OK @a-roussos will do - thank you for starting the ball rolling :-)

I have merged this into the about branch.  I'm going to work on this there - this will produce betas with the -about tag on them.
For further updates see #1564
I'm going to close this PR - expect it to land in v1.41!

OK here is probably the final version of about before I merge it - comments appreciated!
https://beta.rclone.org/v1.40-089-gef3bcec7-about/ (uploaded in 15-30 mins)
See the docs here: https://github.com/ncw/rclone/blob/about/cmd/about/about.go#L44
This is supported for local, crypt, cache, drive, swift, hubic, onedrive, pcloud, dropbox


fix: remove unused plugins in lib/babel-hook

Current coverage is 82.30% (diff: 100%)

Merging #444 into master will not change coverage

@@             master       #444   diff @@
==========================================
  Files           166        166
  Lines          1791       1791
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1474       1474
  Misses          317        317
  Partials          0          0

Powered by Codecov. Last update e7316c0...82ada67


Calculate not adding select values in paged view

I have two groups containing select one question(likert) and widgets style is set to page in settings. There is a calculate field to add the values of select questions. The select options values are numbers, when user selects, the values are added and displayed at the end.
For the first time when I select values, the note is showing expected added calculate value. I go back to the first page and comes back to the note (last page), it's showing expected value. But if I go to second page and change question selection, the note is not showing expected value. This works fine if I am not using page view.
Enclosing form formStrHtml & modelStrXml to be plugged to app.s to reproduce scenario.
var formStrHtml = '<form autocomplete="off" novalidate="novalidate" class="or clearfix" id="tmpYo1VYj">

Household Survey
 Village|गॉव<input type="text" name="/tmpYo1VYj/village" data-type-xml="string"/>Value not allowed Family Number|परिवार संख्या<input type="text" name="/tmpYo1VYj/family_number" data-type-xml="string"/>Value not allowed

Family Members

Name|नाम<input type="text" name="/tmpYo1VYj/family_members/name" data-type-xml="string"/>Value not allowedAge|आयु( वर्ष/ माह)<input type="number" name="/tmpYo1VYj/family_members/age" data-type-xml="int"/>Value not allowed<fieldset class="question "><fieldset><legend>Gender|लिंग </legend>
<input type="radio" name="/tmpYo1VYj/family_members/gender" data-name="/tmpYo1VYj/family_members/gender" value="male" data-type-xml="select1"/>Male<input type="radio" name="/tmpYo1VYj/family_members/gender" data-name="/tmpYo1VYj/family_members/gender" value="female" data-type-xml="select1"/>Female
</fieldset>Value not allowed</fieldset>Income|आय<input type="number" name="/tmpYo1VYj/family_members/income" data-type-xml="int"/>Value not allowed

 <fieldset id="or-calculated-items" style="display:none;"><input type="hidden" name="/tmpYo1VYj/meta/instanceID" data-calculate="concat(\'uuid:\', uuid())" data-type-xml="string"/></fieldset></form>';

var modelStrXml = '<model><instance> <tmpYo1VYj id="tmpYo1VYj"> <village/> <family_number/> <family_members template=""> <name/> <age/> <gender/> <income/> </family_members> <meta> <instanceID/> </meta> <form_code>001</form_code></tmpYo1VYj> </instance></model>';

Thanks!
For easier reproduction, could you perhaps link or send either the XForm or the XLSForm?

thanks for the form https://docs.google.com/a/enketo.org/spreadsheets/d/1WM_FT5zX27rRf_gtuy2EQShSmrTn8AEnNRcV5MEvkas/edit?usp=sharing (private link).

I cannot reproduce, but I wonder if there may be a misunderstanding... :)
The calculation shows NaN if any of the 8 questions is empty. That's as expected.
Is that the behaviour you are seeing?
https://odk.enke.to/preview?form=http://<IP_ADDRESS>/xlsform/tmp/tmpsPDq9D/CommunityDevelopmentIndex.xml

I can see it working as expected.

Great. This is the commit: 5ed25511e19d5cdbfecfe4fa676ca9163b39ba4f.
I don't think this bug was present in a previous commit, but maybe.

My bad, I apologise. It's not reproducible. Possibly I misses some
inclusion or did wrong inclusion.
Thanks for taking time.
On Thu, May 28, 2015 at 8:21 PM, Martijn van de Rijdt <
<EMAIL_ADDRESS>wrote:

Great. This is the commit: 5ed2551
https://github.com/enketo/enketo-core/commit/5ed25511e19d5cdbfecfe4fa676ca9163b39ba4f.
I don't think this bug was present in a previous commit, but maybe.
—
Reply to this email directly or view it on GitHub
https://github.com/enketo/enketo-core/issues/280#issuecomment-106371759.

no worries.
P.S. Let me know when you want me to start promoting your tool.


Publish Fails after Upgrade to 1.2.0

Publish Now Fails after Upgrade.
Describe the bug
After upgrading to the new version 1.2.0 when I attempt to publish I get an error: "Expected signal to be an instanceof AbortSignal"
Version
1.2.0
Browser

[ ] Electron distribution
[ ] Chrome
[ ] Safari
[ ] Firefox
[x] Edge

OS

[ ] macOS
[x] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to 'Publish'
Click on 'Publish profile'
Publish errors out
See error

Expected behavior
As before successful publish before upgrading to v1.2.0
Screenshots

Additional context
This was working in the previous version.  Once I upgraded to v1.2.0 the publish with no changes now fails.

this has been addressed in 1.2.1


ubuntu out of memory with node

Description
Hi,
I used this plugin for long time ago, but now it's starting to give me problems.
Things that change, I only can think in the  project size that now is 200M.
I'm in Ubuntu22, but I recently change, and before I work with Ubuntu18 and 20, that has the same problem... yes, I change twice my S.O. in one year.
I started to see that when I try things like 'go to definition', it takes like a minute (when it works), and see lot of errors like 'Client n quit with exit code n and signal n' (the numbers change so I put an 'n')
And another thing I notice is that node starts to give me some problems, because ubuntu tell me to send the report.
I follow the README and install with basic configuration. Commenting code here and there I discover the line that give me problems.
I tried to look where node is launch, and without that line, node doesn't start:
lspconfig.pyright.setup {}
with the line node starts with:
CPU: 190,7
MEM: 13,8
(more or less)
The problem with node apparently is a resource problem, so maybe it's getting too much resources with the basic configuration.
Neovim version
NVIM v0.10.0-dev-698+g02d859a07
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Run "nvim -V1 -v" for more info
Nvim-lspconfig version
No response
Operating system and version
Ubuntu22
Affected language servers
python
Steps to reproduce
Install plugin with Suggested configuration
Actual behavior
It takes some minutes to 'go to definition'
node stop working
Expected behavior
No response
Minimal config
-- Setup language servers.
local lspconfig = require('lspconfig')
lspconfig.pyright.setup {}
lspconfig.tsserver.setup {}
lspconfig.rust_analyzer.setup {
  -- Server-specific settings. See `:help lspconfig-setup`
  settings = {
    ['rust-analyzer'] = {},
  },
}

-- Global mappings.
-- See `:help vim.diagnostic.*` for documentation on any of the below functions
vim.keymap.set('n', '<space>e', vim.diagnostic.open_float)
vim.keymap.set('n', '[d', vim.diagnostic.goto_prev)
vim.keymap.set('n', ']d', vim.diagnostic.goto_next)
vim.keymap.set('n', '<space>q', vim.diagnostic.setloclist)

-- Use LspAttach autocommand to only map the following keys
-- after the language server attaches to the current buffer
vim.api.nvim_create_autocmd('LspAttach', {
  group = vim.api.nvim_create_augroup('UserLspConfig', {}),
  callback = function(ev)
    -- Enable completion triggered by <c-x><c-o>
    vim.bo[ev.buf].omnifunc = 'v:lua.vim.lsp.omnifunc'

    -- Buffer local mappings.
    -- See `:help vim.lsp.*` for documentation on any of the below functions
    local opts = { buffer = ev.buf }
    vim.keymap.set('n', 'gD', vim.lsp.buf.declaration, opts)
    vim.keymap.set('n', 'gd', vim.lsp.buf.definition, opts)
    vim.keymap.set('n', 'K', vim.lsp.buf.hover, opts)
    vim.keymap.set('n', 'gi', vim.lsp.buf.implementation, opts)
    vim.keymap.set('n', '<C-k>', vim.lsp.buf.signature_help, opts)
    vim.keymap.set('n', '<space>wa', vim.lsp.buf.add_workspace_folder, opts)
    vim.keymap.set('n', '<space>wr', vim.lsp.buf.remove_workspace_folder, opts)
    vim.keymap.set('n', '<space>wl', function()
      print(vim.inspect(vim.lsp.buf.list_workspace_folders()))
    end, opts)
    vim.keymap.set('n', '<space>D', vim.lsp.buf.type_definition, opts)
    vim.keymap.set('n', '<space>rn', vim.lsp.buf.rename, opts)
    vim.keymap.set({ 'n', 'v' }, '<space>ca', vim.lsp.buf.code_action, opts)
    vim.keymap.set('n', 'gr', vim.lsp.buf.references, opts)
    vim.keymap.set('n', '<space>f', function()
      vim.lsp.buf.format { async = true }
    end, opts)
  end,
})

LSP log
[START][2023-07-26 10:00:40] LSP logging initiated [ERROR][2023-07-26 10:00:40] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"\n<--- Last few GCs --->\n\n[35793:0x6435f20]   706547 ms: Mark-sweep (reduce) 1869.1 (2046.0) -> 1869.1 (1992.8) MB, 2193.1 / 0.0 ms  (average mu = 0.386, current mu = 0.000) last resort; GC in old space requested\n[35793:0x6435f20]   708360 ms: Mark-sweep (reduce) 1869.1 (1992.8) -> 1869.1 (1979.8) MB, 1813.2 / 0.0 ms  (average mu = 0.250, current mu = 0.000) last resort; GC in old space requested\n\n\n<--- JS stacktrace --->\n\nFATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory\n" [ERROR][2023-07-26 10:00:40] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 1: 0xb83f50 node::Abort() [/usr/bin/node]\n 2: 0xa94834  [/usr/bin/node]\n 3: 0xd647c0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]\n 4: 0xd64b67 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]\n" [ERROR][2023-07-26 10:00:40] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 5: 0xf3039f v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]\n" [ERROR][2023-07-26 10:00:40] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 6: 0xf10760 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [/usr/bin/node]\n" [ERROR][2023-07-26 10:00:40] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 7: 0xf07d2c v8::internal::FactoryBasev8::internal::Factory::AllocateRawArray(int, v8::internal::AllocationType) [/usr/bin/node]\n" [ERROR][2023-07-26 10:00:40] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 8: 0xf07ea5 v8::internal::FactoryBasev8::internal::Factory::NewFixedArrayWithFiller(v8::internal::Handlev8::internal::Map, int, v8::internal::Handlev8::internal::Oddball, v8::internal::AllocationType) [/usr/bin/node]\n" [ERROR][2023-07-26 10:00:40] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 9: 0x11c2f0e v8::internal::MaybeHandlev8::internal::OrderedHashMap v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Allocatev8::internal::Isolate(v8::internal::Isolate*, int, v8::internal::AllocationType) [/usr/bin/node]\n" [ERROR][2023-07-26 10:00:40] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"10: 0x11c2fc3 v8::internal::MaybeHandlev8::internal::OrderedHashMap v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Rehashv8::internal::Isolate(v8::internal::Isolate*, v8::internal::Handlev8::internal::OrderedHashMap, int) [/usr/bin/node]\n" [ERROR][2023-07-26 10:00:40] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"11: 0x12cd30d v8::internal::Runtime_MapGrow(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node]\n" [ERROR][2023-07-26 10:00:40] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"12: 0x17035b9  [/usr/bin/node]\n" [START][2023-07-26 13:44:12] LSP logging initiated [ERROR][2023-07-26 13:44:12] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"\n<--- Last few GCs --->\n\n[87797:0x5badf20]   353038 ms: Mark-sweep (reduce) 1862.2 (2045.5) -> 1862.2 (1990.5) MB, 995.3 / 0.0 ms  (average mu = 0.438, current mu = 0.000) last resort; GC in old space requested\n[87797:0x5badf20]   354840 ms: Mark-sweep (reduce) 1862.2 (1990.5) -> 1862.2 (1974.3) MB, 1802.1 / 0.0 ms  (average mu = 0.232, current mu = 0.000) last resort; GC in old space requested\n\n\n<--- JS stacktrace --->\n\nFATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory\n" [ERROR][2023-07-26 13:44:12] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 1: 0xb83f50 node::Abort() [/usr/bin/node]\n 2: 0xa94834  [/usr/bin/node]\n 3: 0xd647c0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]\n 4: 0xd64b67 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]\n 5: 0xf3039f v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]\n" [ERROR][2023-07-26 13:44:12] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 6: 0xf10760 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [/usr/bin/node]\n" [ERROR][2023-07-26 13:44:12] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 7: 0xf07d2c v8::internal::FactoryBasev8::internal::Factory::AllocateRawArray(int, v8::internal::AllocationType) [/usr/bin/node]\n" [ERROR][2023-07-26 13:44:12] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 8: 0xf07ea5 v8::internal::FactoryBasev8::internal::Factory::NewFixedArrayWithFiller(v8::internal::Handlev8::internal::Map, int, v8::internal::Handlev8::internal::Oddball, v8::internal::AllocationType) [/usr/bin/node]\n" [ERROR][2023-07-26 13:44:12] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 9: 0x11c2f0e v8::internal::MaybeHandlev8::internal::OrderedHashMap v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Allocatev8::internal::Isolate(v8::internal::Isolate*, int, v8::internal::AllocationType) [/usr/bin/node]\n" [ERROR][2023-07-26 13:44:12] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"10: 0x11c2fc3 v8::internal::MaybeHandlev8::internal::OrderedHashMap v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Rehashv8::internal::Isolate(v8::internal::Isolate*, v8::internal::Handlev8::internal::OrderedHashMap, int) [/usr/bin/node]\n" [ERROR][2023-07-26 13:44:12] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"11: 0x12cd30d v8::internal::Runtime_MapGrow(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node]\n" [ERROR][2023-07-26 13:44:12] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"12: 0x17035b9  [/usr/bin/node]\n" [START][2023-07-26 15:26:17] LSP logging initiated [ERROR][2023-07-26 15:26:17] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"\n<--- Last few GCs --->\n\n[95110:0x6fcdf20]   570221 ms: Scavenge (reduce) 1976.9 (2080.2) -> 1976.0 (2080.2) MB, 6.9 / 0.0 ms  (average mu = 0.346, current mu = 0.462) allocation failure; \n[95110:0x6fcdf20]   570272 ms: Scavenge (reduce) 1977.0 (2080.2) -> 1976.1 (2080.2) MB, 21.4 / 0.0 ms  (average mu = 0.346, current mu = 0.462) allocation failure; \n[95110:0x6fcdf20]   570298 ms: Scavenge (reduce) 1977.0 (2080.2) -> 1976.2 (2080.5) MB, 6.1 / 0.0 ms  (average mu = 0.346, current mu = 0.462) allocation failure; \n\n\n<--- JS stacktrace --->\n\nFATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory\n 1: 0xb83f50 node::Abort() [/usr/bin/node]\n 2: 0xa94834  [/usr/bin/node]\n 3: 0xd647c0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]\n" [ERROR][2023-07-26 15:26:17] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 4: 0xd64b67 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]\n 5: 0xf42265  [/usr/bin/node]\n 6: 0xf43168 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node]\n 7: 0xf53673  [/usr/bin/node]\n" [ERROR][2023-07-26 15:26:17] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 8: 0xf544e8 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node]\n" [ERROR][2023-07-26 15:26:17] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 9: 0xf2ee4e v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]\n" [ERROR][2023-07-26 15:26:17] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"10: 0xf30217 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]\n" [ERROR][2023-07-26 15:26:17] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"11: 0xf113ea v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/usr/bin/node]\n" [ERROR][2023-07-26 15:26:17] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"12: 0x12d674f v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node]\n" [ERROR][2023-07-26 15:26:17] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"13: 0x17035b9  [/usr/bin/node]\n" [START][2023-07-26 15:36:23] LSP logging initiated [ERROR][2023-07-26 15:36:23] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"\n<--- Last few GCs --->\n\n[97111:0x6bb0f20]   532971 ms: Mark-sweep (reduce) 1863.9 (2039.3) -> 1863.9 (1987.5) MB, 2504.2 / 0.0 ms  (average mu = 0.294, current mu = 0.000) last resort; GC in old space requested\n[97111:0x6bb0f20]   536481 ms: Mark-sweep (reduce) 1863.9 (1987.5) -> 1863.9 (1983.8) MB, 3509.8 / 0.0 ms  (average mu = 0.139, current mu = 0.000) last resort; GC in old space requested\n\n\n<--- JS stacktrace --->\n\nFATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory\n 1: 0xb83f50 node::Abort() [/usr/bin/node]\n 2: 0xa94834  [/usr/bin/node]\n 3: 0xd647c0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]\n 4: 0xd64b67 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]\n 5: 0xf3039f v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]\n" [ERROR][2023-07-26 15:36:23] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 6: 0xf10760 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [/usr/bin/node]\n 7: 0xf07d2c v8::internal::FactoryBasev8::internal::Factory::AllocateRawArray(int, v8::internal::AllocationType) [/usr/bin/node]\n 8: 0xf07ea5 v8::internal::FactoryBasev8::internal::Factory::NewFixedArrayWithFiller(v8::internal::Handlev8::internal::Map, int, v8::internal::Handlev8::internal::Oddball, v8::internal::AllocationType) [/usr/bin/node]\n 9: 0x11c2f0e v8::internal::MaybeHandlev8::internal::OrderedHashMap v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Allocatev8::internal::Isolate(v8::internal::Isolate*, int, v8::internal::AllocationType) [/usr/bin/node]\n10: 0x11c2fc3 v8::internal::MaybeHandlev8::internal::OrderedHashMap v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Rehashv8::internal::Isolate(v8::internal::Isolate*, v8::internal::Handlev8::internal::OrderedHashMap, int) [/usr/bin/node]\n" [ERROR][2023-07-26 15:36:23] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"11: 0x12cd30d v8::internal::Runtime_MapGrow(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node]\n" [ERROR][2023-07-26 15:36:23] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"12: 0x17035b9  [/usr/bin/node]\n" [START][2023-07-26 16:08:31] LSP logging initiated [ERROR][2023-07-26 16:08:31] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"\n<--- Last few GCs --->\n\n[101147:0x7738f20]   363091 ms: Mark-sweep (reduce) 1862.0 (2039.0) -> 1862.0 (1986.3) MB, 1251.0 / 0.0 ms  (average mu = 0.324, current mu = 0.000) last resort; GC in old space requested\n[101147:0x7738f20]   364354 ms: Mark-sweep (reduce) 1862.0 (1986.3) -> 1862.0 (1968.8) MB, 1263.0 / 0.0 ms  (average mu = 0.199, current mu = 0.000) last resort; GC in old space requested\n\n\n<--- JS stacktrace --->\n\nFATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory\n 1: 0xb83f50 node::Abort() [/usr/bin/node]\n 2: 0xa94834  [/usr/bin/node]\n 3: 0xd647c0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]\n 4: 0xd64b67 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]\n 5: 0xf3039f v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]\n 6: 0xf10760 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [/usr/bin/node]\n 7: 0xf07d2c v8::internal::FactoryBasev8::internal::Factory::AllocateRawArray(int, v8::internal::AllocationType) [/usr/bin/node]\n 8: 0xf07ea5 v8::internal::FactoryBasev8::internal::Factory::NewFixedArrayWithFiller(v8::internal::Handlev8::internal::Map, int, v8::internal::Handlev8::internal::Oddball, v8::internal::AllocationType) [/usr/bin/node]\n 9: 0x11c2f0e v8::internal::MaybeHandlev8::internal::OrderedHashMap v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Allocatev8::internal::Isolate(v8::internal::Isolate*, int, v8::internal::AllocationType) [/usr/bin/node]\n10: 0x11c2fc3 v8::internal::MaybeHandlev8::internal::OrderedHashMap v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Rehashv8::internal::Isolate(v8::internal::Isolate*, v8::internal::Handlev8::internal::OrderedHashMap, int) [/usr/bin/node]\n11: 0x12cd30d v8::internal::Runtime_MapGrow(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node]\n" [ERROR][2023-07-26 16:08:31] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"12: 0x17035b9  [/usr/bin/node]\n" [START][2023-07-26 16:27:45] LSP logging initiated [ERROR][2023-07-26 16:27:45] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"\n<--- Last few GCs --->\n\n[103641:0x5decf20]   510891 ms: Mark-sweep (reduce) 1862.1 (2041.5) -> 1862.1 (1985.3) MB, 2700.5 / 0.0 ms  (average mu = 0.315, current mu = 0.000) last resort; GC in old space requested\n[103641:0x5decf20]   513125 ms: Mark-sweep (reduce) 1862.1 (1985.3) -> 1862.1 (1971.8) MB, 2233.0 / 0.0 ms  (average mu = 0.195, current mu = 0.000) last resort; GC in old space requested\n\n\n<--- JS stacktrace --->\n\nFATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory\n 1: 0xb83f50 node::Abort() [/usr/bin/node]\n 2: 0xa94834  [/usr/bin/node]\n 3: 0xd647c0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]\n 4: 0xd64b67 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/bin/node]\n 5: 0xf3039f v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/usr/bin/node]\n 6: 0xf10760 v8::internal::Factory::AllocateRaw(int, v8::internal::AllocationType, v8::internal::AllocationAlignment) [/usr/bin/node]\n 7: 0xf07d2c v8::internal::FactoryBasev8::internal::Factory::AllocateRawArray(int, v8::internal::AllocationType) [/usr/bin/node]\n" [ERROR][2023-07-26 16:27:45] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	" 8: 0xf07ea5 v8::internal::FactoryBasev8::internal::Factory::NewFixedArrayWithFiller(v8::internal::Handlev8::internal::Map, int, v8::internal::Handlev8::internal::Oddball, v8::internal::AllocationType) [/usr/bin/node]\n 9: 0x11c2f0e v8::internal::MaybeHandlev8::internal::OrderedHashMap v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Allocatev8::internal::Isolate(v8::internal::Isolate*, int, v8::internal::AllocationType) [/usr/bin/node]\n10: 0x11c2fc3 v8::internal::MaybeHandlev8::internal::OrderedHashMap v8::internal::OrderedHashTable<v8::internal::OrderedHashMap, 2>::Rehashv8::internal::Isolate(v8::internal::Isolate*, v8::internal::Handlev8::internal::OrderedHashMap, int) [/usr/bin/node]\n11: 0x12cd30d v8::internal::Runtime_MapGrow(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node]\n" [ERROR][2023-07-26 16:27:45] .../vim/lsp/rpc.lua:675	"rpc"	"/home/hugo/projects/ue/ue-dev/venv/bin/pyright-langserver"	"stderr"	"12: 0x17035b9  [/usr/bin/node]\n"

I used this plugin for long time ago, but now it's starting to give me problems.

"This plugin" is just a collection of configs. Problems with whatever LSP server are running have nothing to do with this plugin.

Things that change, I only can think in the project size that now is 200M.

This plugin is just a collection of configs. If pyright or whatever LSP server is having problems, you need to resolve that with pyright or whatever LSP server.


[SPARK-5957][ML] better handling of parameters

The design doc was posted on the JIRA page. Python changes will be in a follow-up PR. @jkbradley

Use codegen for shared params.
Move shared params to package ml.param.shared.
Set default values in Params instead of in Param.
Add a few methods to Params and ParamMap.
Move schema handling to SchemaUtils from Params.

[x] check visibility of the methods added

Test build #29906 has started for   PR 5431 at commit 29b004c.

Test build #29906 has finished for   PR 5431 at commit 29b004c.

This patch fails to build.
This patch does not merge cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/29906/
Test FAILed.

Test build #29909 has started for   PR 5431 at commit d63b5cc.

Test build #29910 has started for   PR 5431 at commit 55be1f3.

Test build #29910 has finished for   PR 5431 at commit 55be1f3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

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

Test build #29909 has finished for   PR 5431 at commit d63b5cc.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

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

Test build #30150 has started for   PR 5431 at commit eec2264.

Test build #30150 has finished for   PR 5431 at commit eec2264.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

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

Should this method in Params be made abstract?
def validate(paramMap: ParamMap): Unit = {}

I just realized we haven't been using it, and making it abstract would force users to think about it.

@mengxr I added minor comment but don't have major ones.  That's it for now!

Test build #30210 has started for   PR 5431 at commit 26ae2d7.

LGTM once tests pass

Test build #30212 has started for   PR 5431 at commit d19236d.

Test build #30210 has finished for   PR 5431 at commit 26ae2d7.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/30210/
Test FAILed.

Test build #30212 has finished for   PR 5431 at commit d19236d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.
This patch does not change any dependencies.

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

Merged into master.


Improving the FIT

A typical fit with SHERLOCK (via allesfitter) looks like that:

Here it can be seen that rr and rr_suma parameters are not correctly explored. This issue is coming from the injected values imported by TLS, which is using the maximum depth of the full set of transits, which is unrealistic. Hence, a better estimation for these two parameters:

Use of the mean of the trantist depths
uncertainties x 2 to provide a larger distribution to sample

The red noise can be modeled using a GP Matern 3/2, whose hyperparameter at this point are not correctly sampled and they never converge (last two rows in the image above). To solve this we may use the noise estimation via allesfitter:
import allesfitter
#MCMC - evaluation of the noise out of transit
allesfitter.estimate_noise_out_of_transit(datadir)
allesfitter.mcmc_output('allesfit')
#NS - we propagate the noise in transit
allesfitter.show_initial_guess('allesfit')
allesfitter.ns_fit('allesfit')
allesfitter.ns_output('allesfit')

Then, transits are masked (8h around each) and the perform an MCMC fitting the hyperparameters:

These values can be used now in the fitting. Since we are providing with a relatively fast and accurate fitting, we may fix these values and not fit anymore when fitting the transits.
As a final touch we may include a fitting in the LD coefficients q1 and q2, performing a sampling from 0 to 1.
This would be the most efficient fitting to trigger a ground-base follow up

Done, but the red noise previous fit won't be done.


[Bug]: Double-clicking an object in the object tree does not open details

ODC version
ODC 4.2.2
OB version
Any version of OceanBase.
What happened?
Double-clicking an object in the object tree does not open details,only expands the object tree.

What did you expect to happen?
Double-click the object name can display the object details.
How can we reproduce it (as minimally and precisely as possible)?
Double-click the object name
Anything else we need to know?
No response
Cloud
No response

Fixed In Commit ee56af18cca37643af77eea9e5369b551fe22af9
------
晓康
Tue Nov 21 16:34:31 2023 +0800


⚠ Bofrost.de has degraded performance

In 08ed40f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1419 ms

Resolved: Bofrost.de performance has improved in 860c21a.


Add rules for FR Time

Add / modif rules to support:

début|milieu|fin de matinée (early|mid|late morning)
début|milieu|fin de après-midi (early|mid|late afternoon)
début|milieu|fin de journée (early|mid|late day)
début|fin de soirée (early|late evening)
début|fin de mois (early|late month)
début|fin d'année (early|late year)
plus tard (later)
plus tard que ... (later than ...)
plus tard <time> (later than <time>)
plus tard <part-of-day> (later than <part-of-day>)

And add additional corpus' examples for FR Time

Merci @amenella!
I've reverted some of the changes around part of days delimitations to avoid breaking existing clients. The long-term solution is the ability to override assumptions (see #29).


Extract  section of index.html file

Extract <body> section to be displayed.
Gist with fully-formed index.html:
https://gist.github.com/ggirou/73239b9204eaf6c375dd

I added tests :)

:) Thanks!
lgtm


maintainers: add yuka

If this seems strange to you, or you are a maintainer of one of these
packages, please contact me on Matrix: @yuka:yuka.dev

(@yu-re-ka is a new GitHub account for an existing committer.)


Add support for MercadoPago 3.2.0

Hi!
I want to tell you that I'm working on a newer version of this library on a fork, where I try to integrate the MercadoPago SDK v3.2.0 for Android/IOS.
I have currently done with the Android setup. The newer version of this SDK provides the ability to start the checkout in two modes. One for Payment, and another one for PaymentData (Intended to be used when you work with MP Connect/MarketPlace).
The current modifications to your codebase are the following ones:

Add the ability to customize checkout appearance through DecorationPreference class
Add the ability to start the checkout in case of Payment, or PaymentData.
Some other minor modifications to the code related to the ActivityEventListener.

I have to work still on the IOS part.
Are you currently interested in the possibility of merging my changes? If so, let me know, and I will open a PR, where you can track my development progress.

@JonatanSalas thank you very much, your PR will be more than welcome.

@scarmuega Great! I will open a PR so you can keep track.

@scarmuega PR is able to merge!