Switch to using broccoli-persistent-filter

See #92
This updates broccoli-asset-rev to use broccoli-persistent-filter. Although the APIs are similar, it was not possible to do a simple swap-out replacement. In particular, the previous implementation relied on getDestFilePath() not being called for certain relativePaths for which it is now being called. While this could have been worked around, we opted to refactor a bit and use more of broccoli-persistent-filter's public API. The hashing is now done within processString() which is passed in each file's contents so we now avoid an extra readFileSync for every file.
I should explain all of the text fixture renames: hashing the contents parameter of processString() results in different digests for the binary files in the test fixture directories (previously we were hashing a Buffer and now a string).

Current coverage is 93.37%

Merging #93 into master will decrease coverage by -2.02% as of e2e0700

@@            master     #93   diff @@
======================================
  Files            3       3
  Stmts          152     151     -1
  Branches        36      38     +2
  Methods          0       0
======================================
- Hit            145     141     -4
  Partial          2       2
- Missed           5       8     +3

Review entire Coverage Diff as of e2e0700

Powered by Codecov. Updated on successful CI builds.

@stefanpenner Would you mind reviewing and signing off?

Will do

Just tried this and the new broccoli-asset-rewrite PR, unfortunately they don't appear to work correctly.
When used together, it appears broccoli-asset-rewrite seems to prevent assets on disk from getting the correct fingerprinted name, removing it and all appears well.
The issue might be in the other project, but requires a deeper look.

Is this PR dead?
I want to add pluggable getDestFilePath but it would obviously clash with the change to processString(), so I'd like to know if this is happening.

@stefanpenner @elucid @rickharrison I too wonder about the status of this PR/repository. This particular PR is 14 months old now. How's the support?


pip version mismatch in packs virtual environment

ISSUE TYPE

Other

STACKSTORM VERSION
2.7.2
OS / ENVIRONMENT / INSTALL METHOD
ubuntu
SUMMARY
We have upgraded stacktstorm to 2.7.2, we are able to see different versions of pip in the virtual env of packs.
Examples

in pack test1 pip version is pip 9.0.1
requirements.txt for test1 pack contains following
azure-graphrbac==0.40.0

in pack test2 pip version is pip 10.0.1
requirements.txt for test2 pack contains following
requests==2.18.4
reportlab==3.4.0
urllib3==1.22

Please clarify this.
Is the version of pip within virtual environment dependent on the python modules mentioned in requirements.txt of pack ?

@guptasakshi01 Please confirm that the above^ works for you.

@Kami
I have deleted the virtual env for pack test2 and registered again, but still i am getting pip version as 10.0.1

@guptasakshi01 what were the exact commands that you ran?

After Removing test2 pack and installing it again i am getting error:-
+--------------------------+---------------------+---------------+----------------+-------------------------------+
| id                       | status              | task          | action         | start_timestamp               |
+--------------------------+---------------------+---------------+----------------+-------------------------------+
| 5b0bb63c7052cf05b2ca4166 | failed (1s elapsed) | download pack | packs.download | Mon, 28 May 2018 07:56:44 UTC |
+--------------------------+---------------------+---------------+----------------+-------------------------------+

Is there anything useful in the logs? For example, the st2api.log, or the st2actionrunner logs?
What if you look at the full output for that execution above - what does it tell you?

What does st2 execution get 5b0bb63c7052cf05b2ca4166 tell you? There should have been some more output when you ran the command. If it failed at the download step, it could be something else going on - e.g. your proxy setup, GitHub outage, etc. Look at the details and logs and it should tell you.

@LindsayHill  Result of st2 execution get 5b0bb63c7052cf05b2ca4166
id: 5b0bb63c7052cf05b2ca4166
status: failed (1s elapsed)
parameters:
force: false
packs:

test2
result:
exit_code: 1
result: None
stderr: "Traceback (most recent call last):
File "/opt/stackstorm/runners/python_runner/python_runner/python_action_wrapper.py", line 320, in
obj.run()
File "/opt/stackstorm/runners/python_runner/python_runner/python_action_wrapper.py", line 179, in run
output = action.run(**self._parameters)
File "/opt/stackstorm/packs/packs/actions/pack_mgmt/download.py", line 88, in run
pack_url, pack_version = self._get_repo_url(pack, proxy_config=self.proxy_config)
File "/opt/stackstorm/packs/packs/actions/pack_mgmt/download.py", line 312, in _get_repo_url
raise Exception('No record of the "%s" pack in the index.' % name_or_url)
Exception: No record of the "test2" pack in the index.
"
stdout: ''

test2 is not a valid pack on exchange.stackstorm.org. If your pack is hosted on an internal index, you should check that.
If your pack is not listed on exchange.stackstorm.org or your internal index, you need to install it by giving a path to the git repo, eg st2 pack install https://my.gitlab/org/test2
Where is the pack test2 located?

Closing due to no response


support for offscreen canvas

truly want the support for offscreen canvas

Oh, did you mean OffscreenCanvas? Proton can easily extend your own Custom renderer, I think it should not be complicated

@drawcall  yes, I create a custom class Image in the WebWorker which results in an ImageBitMap for "ctx.drawImage". and it works;


[Improvement] in GravitinoMetaLake.java subclass has equals method but parent does not

What would you like to be improved?
Class should have an equals method.
How should we improve?
Add equals method.

I am happy to try this! I have not worked on an Open Source project before but I think I understand everything I need to do.

Just to make sure I understand, do I add the equals method from MetalakeDTO to GravitinoMetaLake?

Hi @justinmclean ,
This issue seems to be inactive in past 4 months.
Can this be assigned to me?
Best Regards,
Edward

Sure, you might want to read the comments in https://github.com/apache/gravitino/pull/4448


Update PayoutRoutes.swift

Make public methods

@Maxim-Inv any reason why the status checks don’t run? Maybe try re opening a PR.

Idk. Should I close this PR and create a new one?

Yea I’d probably do that to see if it corrects itself.

Also make sure you have the latest master pulled in (which I think you do anyway)

Yes, I have the latest


Try out  Literate.jl workflow for jupyter notebooks and document it

The https://github.com/fredrikekre/Literate.jl is supposed to allow generation of jupyter notebooks.  It would be great if we could write all of our Jupyter tests/tutorials with this.
Documents should go in the tutorials repository.

Lower priority, but worth playing with. Feel free to use this repository as a scratch pad

@jlperla I gave this a shot. It's really neat. This is how you call the code. Workflow doesn't require much except a generate_docs file, that has some code like the following. Plotting on Jupyter notebooks works flawlessly.
using Literate

import Plots

function update_date(content)
    content = replace(content, "DATETIME" => Date(now()))
    return content
end

Literate.markdown(pwd() * "\\julia_sandbox\\literate_test.jl", pwd() * "\\julia_sandbox\\"; preprocess = update_date)
Literate.notebook(pwd() * "\\julia_sandbox\\literate_test.jl", pwd() * "\\julia_sandbox\\"; preprocess = update_date)
Literate.notebook(pwd() * "\\julia_sandbox\\literate_test_2.jl", pwd() * "\\julia_sandbox\\"; preprocess = update_date)

Let me know if you'd like me to write a tutorial on this or something.

Results are in 0451b5f.


Remove Announcement Banner

What is the purpose of the change
To remove the announcement (yellow) banner. Currently about LVN and milkTIA.

Brief Changelog

Removes toggle from feature-flag.ts
Removes text from all 12 localization files.

Testing and Verifying
This change has been tested locally by rebuilding the website and verified content and links are expected

fyi @MaxMillington


Add serving support for MarkedSource and deprecate Formats. [phab:D1183]

Created by zarko at 2016-12-14 22:00:39:
This diff also refactors xrefs_test so that the code
for setting up a mock service is only written once.

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
Did you mean to include a synopsis of the contents of the MarkedSource in this case?

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
You could also make this
err = proto.Unmarshal(value, rsig)
return rsig, err

The general assumption when err != nil is that the other values are garbage. It's up to you, though.
Even return rsig, proto.Unmarshal(value, rsig) would be OK, though that's a little more subtle on the reader.

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
Rather than a negative value, you could use presence in the map for this.
dp, ok := deets.defaultParams[ticket]
if ok {
   useDefault(dp)
} else {
   noDefault()
}

Not that -1 is bad, but it's a little peculiar.

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
return nil, fmt.Errorf("invalid default parameter %q: %v", d, err)

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
Suggestion:
if d := string(node.Facts[facts.ParamDefault]); d != "" {…

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
if sersig := node.Facts[facts.Code]; len(sersig) != 0 {…

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
func slowSignatureTraverseLevel(ctx context.Context, service Service, ticket, kind string, sig *xpb.MarkedSource, defaultParam, depth int, details *SignatureDetails) (*xpb.MarkedSource, error) {…

With this many parameters it feels like it would be really easy to twiddle values. It's unexported, so I'm not too worried, but one thing you might consider is using a parameter type:
type slowSigSettings struct {
	service      Service
	ticket       string
	kind         string
	marked       *xpb.MarkedSource
	defaultParam int
	details      *SignatureDetails
}

This would let you use named initializers at the call site, e.g.
func slowSignatureTraverseLevel(ctx context.Context, depth int, settings slowSigSettings) (*xpb.MarkedSource, error) {

slowSignatureTraverseLevel(ctx, 0, slowSigSettings{
	service:      s,
	ticket:       myNode.Ticket,
	kind:         nodes.Anchor,
	marked:       new(xpb.MarkedSource),
	defaultParam: 25,
})

Mileage may vary.

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
Could also be, maybe:
for _, param := range details.params[int(sig.LookupIndex):] {

as long as you know the lookup index is in bounds, and if you can live without the parameter index.

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
count -= int(sig.LookupIndex) - defaultParam

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
This is doing enough work that it deserves an explanatory comment.

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
Please comment.

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
ticket, kind string
defaultParam, depth int
(possibly another candidate for parameter struct, but again up to you)

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
Please document, particularly the accumulator behaviour.

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
signatureLinkTickets (s/get//)

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
Please mention what service this implements.

fromberger commented inline (context lost during migration) at 2016-12-15 03:15:13:
You probably want t.Errorf + continue here, so subsequent tests can get logged.
Below also.

zarko wrote at 2016-12-15 22:07:04:

Address comments.

zarko commented inline (context lost during migration) at 2016-12-15 22:07:33:
Yes--I'm writing a little library for that in a separate diff.

fromberger commented inline (context lost during migration) at 2016-12-15 22:17:30:
Although it's more lines, it's easier to read with breaks:
	outc, err := slowSignatureLevel(slowSignatureState{
		ctx:          s.ctx,
		service:      s.service,
		ticket:       param,
		kind:         s.details.kinds[param],
		marked:       s.details.signatures[param],
		defaultParam: s.details.defaultParam(param),
		depth:        s.depth + 1,
	})

fromberger wrote at 2016-12-15 22:17:30:
Just another small thing; feel free to land this without another round unless you want more comments.

fromberger accepted this revision at 2016-12-15 22:17:30

zarko wrote at 2016-12-15 22:33:30:

Address comments.


Explicit naming of subcommands

This PR allows subcommands to have a different name than their file name via an optional attribute name
Usage:
# commands/mycommand.py
class MyCommand(Command):
   name = "fancy-name"

Will then become anemoi-package fancy-name instead of anemoi-package mycommand
If the name attribute is not present in the class, the filename is used. I suggest we use that as the default, and only add a name if an explicit rename is required.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 89.40%. Comparing base (90b82bc) to head (0ffca1b).
Report is 1 commits behind head on develop.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop      #34   +/-   ##
========================================
  Coverage    89.40%   89.40%
========================================
  Files            5        5
  Lines          151      151
========================================
  Hits           135      135
  Misses          16       16

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

Following internal feedback, name was renamed to command.


Support like $regex

Hello,
I see $lt, $in and etc mongodb operators, how to find by { $regex: /name/i } and etc?

duplcate https://github.com/nodkz/graphql-compose/issues/3


Polymorphic elements in logical model

How to convey "data type A or data type B" in a logical model?
It looks particularly ugly when using a mixture of FHIR and self-defined data types:

Options:

We use polymorphic data types even when it's ugly
We always write out all options with the class allowing only one subelement to be present at the time.

Discussed in 13.09 meeting.
Using FHIR data types and logical models the [x] approach looks prettier and could be used. We will try it. We have, for now, moved away from self-declared data types, but the issue should be revisited if we decide to use our own data types.

Might be a good idea to capture this decision in the authoring conventions

22.10.2024 decision
We leave it as it is for now ([x] approach with models as data types). Hopefully we will find a solution for display. References used only when you can be absolutely sure that this is only a reference (which we might never be able to).

@costateixeira
Reading this thread, I am not sure if "type = EHDSModelName" should be in all the models or not? I'm eager to fix, but not sure I understand which way.

No, the type should not be added. This will be addressed in the tooling and when done we can rever the changes I did.

https://github.com/HL7/fhir-ig-publisher/issues/978

I removed the type when I was cleaning up the qa. I was afraid I was overly eager to do something that had a negative impact instead. Please give us a ping when you notice the update in the Publisher.


Implement Feature: Drag and Drop

I am pleased to submit this pull request addressing Feature Request #182

As per the feature request. I have successfully implemented "drag and drop file" method in the notes upload section. Along with this i have also updated the layout of the upload notes "form" for better user interface. All the screen shots have been attached.

Resolves: [182]
Checklist

[yes ] Have you adhered to the repository's defined coding convention rules?

Screenshots

Functioning of drag and drop file

Updated layout of form for large screens

Layout for small and medium screens

I certify that I have carried out the relevant checks and provided the requisite screenshot for validation by submitting this pull request.

@hereisSwapnil can you verify my code and merge this as early as possible? Also please let me know if there are any changes to be made. It's been two weeks since I opened this pull request, could you please speed up the process of merging this pull request?

hello sir @hereisSwapnil it's been a month since I opened this pull request, please review this and merge at your earliest

Hello @hereisSwapnil is this pull request still active, it's more than  a month since i opened this request, i didn't receive any updates regarding merging of this PR. Please convey your views on this Pull request.


google.golang.org/api-v0.128.0: 1 vulnerabilities (highest severity is: 7.5) - autoclosed

 Vulnerable Library - google.golang.org/api-v0.128.0

Found in HEAD commit: b5979f96d710d352081a6d0f533e43130dbdbc15
Vulnerabilities

CVE
Severity
 CVSS
Dependency
Type
Fixed in (google.golang.org/api-v0.128.0 version)
Remediation Possible**

CVE-2023-39325
 High
7.5
golang.org/x/net-v0.15.0
Transitive
N/A*
❌

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details

 CVE-2023-39325
Vulnerable Library - golang.org/x/net-v0.15.0

Library home page<EMAIL_ADDRESS>
Dependency Hierarchy:

google.golang.org/api-v0.128.0 (Root Library)

:x: golang.org/x/net-v0.15.0 (Vulnerable Library)

Found in HEAD commit: b5979f96d710d352081a6d0f533e43130dbdbc15
Found in base branch: main

Vulnerability Details

A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection. This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2. The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.
Publish Date: 2023-10-11
URL: CVE-2023-39325

CVSS 3 Score Details (7.5)

Base Score Metrics:

Exploitability Metrics:

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged

Impact Metrics:

Confidentiality Impact: None
Integrity Impact: None
Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version
Origin: https://pkg.go.dev/vuln/GO-2023-2102
Release Date: 2023-10-11
Fix Resolution: go1.20.10, go1.21.3, golang.org/x/net - v0.17.0

Thank you for reporting the vulnerability.  The google.golang.org/api-v0.128.0 library depends on golang.org/x/net-v0.15.0, which is vulnerable to CVE-2023-39325. Unfortunately, there is no version of google.golang.org/api that fixes this vulnerability.
You can consider upgrading golang.org/x/net to a version that includes the fix. The fix is available in versions go1.20.10, go1.21.3, and golang.org/x/net - v0.17.0.
Please let us know if you have any further questions.


GUI actions are not reproduced by recorded Python script

Describe the bug
I'm trying to generate a script to convert some files from the Tecplot format to a more compressed Silo format. I recorded the procedure in the GUI, but got different results when executing the recorded Python script.
As a temporary workaround, what output format  is highly compressed, documented and well supported by visit?
Helpful additional information

[ ] Did VisIt crash?
[x] Did you get wrong results?

Impact

[ ] High - User productivity significantly degraded
[x] Medium - User productivity partially degraded
[ ] Low - User productivity trivially degraded

Likelihood

[x] High - occurrence is not specific to platform, data, config, a combination of operators, queries, etc.
[ ] Medium - neither low nor high likelihood
[ ] Low - occurrence is specific to combination of multiple factors such as configuration, data, platform, etc.

To Reproduce
I activated the GUI's record function:

GUI's menu -> Controls -> Commands -> Record

Afterwards,I used the GUI interface to generate a compressed SILO file by the following procedure:

GUI's menu -> Export database:

Export to -> Silo
Added the following to the text box:
-> Export ->

Driver ->HDF5
Checksums -> checked
DBSetCompression()'s textbox was filled with the following string:  ERRMODE=FAIL MINRATIO=2.5 METHOD=SZIP LEVEL=9
-> Ok

As a result, a 1.6MB file is generated.
After stopping the record function, the output did not include the string used for DBSetCompression(). The output of the record function is:
ExportDBAtts = ExportDBAttributes()
ExportDBAtts.allTimes = 0
ExportDBAtts.dirname = "."
ExportDBAtts.filename = "ERRMODE=FAIL MINRATIO=2.5 METHOD=GZIP LEVEL=9"
ExportDBAtts.timeStateFormat = "_%04d"
ExportDBAtts.db_type = "Silo"
ExportDBAtts.db_type_fullname = "Silo_1.0"
ExportDBAtts.variables = ("head")
ExportDBAtts.writeUsingGroups = 0
ExportDBAtts.groupSize = 48
ExportDBAtts.opts.types = (5, 0, 4)
ExportDBAtts.opts.help = ""
ExportDatabase(ExportDBAtts)
This script generates a 17.1 MB file. Please, notice that DBSetCompression() and HDF5 options are not set by the Python script.
I tried to use the python command to generate such options "ExportDBAtts.SetOpts('test')", and got the error message:

ExportDBAtts.SetOpts('test')
The opts field can only be set with DBOptionsAttributes objects.

After executing dir(DBOptionsAttributes), no library is found to create the DBOptionsAttributes object. This occurs in spite there is a DBOptionsAttributes file in the Python source code.
Additionally, please attach a (zipped) sessionfile to this ticket to easily reproduce (In the viewer, use File->Save Session).
File attached is  visitSession.zip
visitSession.zip
Expected behaviour
It is expected that the exact same files are generated by the GUI and the script.
Attachments

Can you reproduce the bug on our test data?.
Yes

If so, which file?
CThead_mid.silo

Please attach a (zipped) sessionfile to easily reproduce (In the viewer, use File->Save Session).
File attached is  visitSession.zip
visitSession.zip

Please attach any screenshots relevant to understanding the issue.

The file GUI-Procedure.png has the steps in the GUI

The file pythonCapture.png has the captured script.

Desktop

OS and version: Ubuntu 16.04
VisIt Version: 2.13.2

Additional context
Add any other context about the problem here. Attach any (zipped) relevant files, such as data, configurations, sessionfiles, etc.
Files:

compressionScript.py : Executes the captured python commands and generates the bigger file

GUI-output.zip : Contains the GUI output

python-output.zip : Contains the python script output

@cfforiguar sorry this is so confusing. The database options uses a different way to encode and pass around options and that path is not wired up to the python recoding.
Complicating things, the way to pass the options also a special case. You call ExportDatabase using two arguments, the first is the attributes object, and the second is the options.
Here is basic example that you can pull from that shows how to export with options:
OpenDatabase("rect2d.silo")
AddPlot("Pseudocolor","d")
DrawPlots()

export_atts = ExportDBAttributes()
export_atts.filename = "myexport"
export_atts.timeStateFormat = "_%04d"
export_atts.db_type = "Silo"
export_atts.db_type_fullname = "Silo_1.0"
export_atts.variables = ("d")

export_opts = GetExportOptions("Silo")
print(export_atts)
{'Checksums': 0, 'Driver': 'PDB # Options are: PDB, HDF5', 'DBSetCompression()': ''}
export_opts["DBSetCompression()"] = "ERRMODE=FAIL MINRATIO=2.5 METHOD=GZIP LEVEL=9"
export_opts["Driver"] = "HDF5"

ExportDatabase(export_atts,export_opts)

Note for how to fix in the future:
We should change the error message for:
ExportDBAtts.SetOpts('test')
The opts field can only be set with DBOptionsAttributes objects.

To mention using ExportDatabase with two args

I can confirm that this solves my problem. Shall I close the issue?. (Sorry, I'm a newbie)
Thank you very much.

@cfforiguar good to hear! And thanks for letting us know this helped.
I think we cant still keep this open -- we do want to address the issue to get proper GUI recording, so we will keep it in our queue.

This came up again as an SRE inquiry

Related to #1054 and seems to duplicate #2804

Another issue: recoding includes the opts help, which is html and may break python string containment:
ExportDBAtts.opts.help = "
Driver:

PDB: Silo library will create a PDB file.

HDF5: Silo library will create an HDF5 file.

Checksums:

Valid only for HDF5 files.

Enables HDF5's Fletcher32 checksum filter.

DBSetCompression():Enter any compression string that would be valid to pass to Silo'sDBSetCompression() method."

Update: I have path forward + solution on this for the 3.1.2 release. Needs some cleanup --
I expect to get to it this weekend or Monday.

New Examples:
w/o opts:
ExportDBAtts = ExportDBAttributes()
ExportDBAtts.allTimes = 0
ExportDBAtts.dirname = "."
ExportDBAtts.filename = "visit_ex_db"
ExportDBAtts.timeStateFormat = "_%04d"
ExportDBAtts.db_type = "Blueprint"
ExportDBAtts.db_type_fullname = "Blueprint_1.0"
ExportDBAtts.variables = ()
ExportDBAtts.writeUsingGroups = 0
ExportDBAtts.groupSize = 48
ExportDatabase(ExportDBAtts)

with opts:
ExportDBAtts = ExportDBAttributes()
ExportDBAtts.allTimes = 0
ExportDBAtts.dirname = "."
ExportDBAtts.filename = "visit_ex_db"
ExportDBAtts.timeStateFormat = "_%04d"
ExportDBAtts.db_type = "Silo"
ExportDBAtts.db_type_fullname = "Silo_1.0"
ExportDBAtts.variables = ()
ExportDBAtts.writeUsingGroups = 0
ExportDBAtts.groupSize = 48
DBExportOpts = {'Checksums': 1, 'Driver': 'HDF5', 'DBSetCompression()': ''}
ExportDatabase(ExportDBAtts, DBExportOpts)

Closing, I merged a fix for 3.1RC in #4725 , PR in progress for develop.


python3Packages.beancount-black: init at 0.1.11

Description of changes
An opinionated beancount formatter.
https://github.com/LaunchPlatform/beancount-black/
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

I have tested the resulting executable on a simple test file taken from the repository.
I wasn't sure whether the addition of beancount-black to top-level/all-packages.nix should be in its own commit or not. I merged it with the addition to python-packages.nix.

Could you fix the conflicts @ambroisie ?

@RaitoBezarius done.

Result of nixpkgs-review pr 169195 run on x86_64-linux 1

5 packages built:

beancount-black (python310Packages.beancount-black)
darwin.builder
python310Packages.beancount-parser
python39Packages.beancount-black
python39Packages.beancount-parser


Segfault while printing warning

invalid format string is being passed for warning in case connection is refused
 perf_log_warning("Error: cannot use connection %i, fd %: %s",
                                       *socknum, tinfo->socks[*socknum], strerror(error));

which causes a segfault as:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff32fc700 (LWP 6612)]
0x00007ffff4f32af7 in _IO_vfprintf_internal (s=<optimized out>, format=<optimized out>, ap=<optimized out>)
    at vfprintf.c:2013
2013                process_string_arg ((&specs[nspecs_done]));

Merged


VOC data set evaluation index

How to calculate the precision index when using VOC data set for training? At present, only these GTS | dets | recall | AP are given

AP is average precision. Does your precision mean that?

No, it's TP / (TP + FP)

https://github.com/open-mmlab/mmdetection/blob/5c7c74d77dfba3663431fe00b6872dfff8bcce1d/mmdet/core/evaluation/mean_ap.py#L364


PSReadline crashes on startup running from the new Win32 SSH server

Exception:
System.IO.IOException: The handle is invalid.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.Console.GetBufferInfo(Boolean throwOnNoConsole, Boolean& succeeded)
   at Microsoft.PowerShell.PSConsoleReadLine.Initialize(Runspace runspace, EngineIntrinsics engineIntrinsics)
   at Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics)
-----------------------------------------------------------------------

Oops, something went wrong.  Please report this bug with the details below.
Report on GitHub: https://github.com/lzybkr/PSReadLine/issues/new
-----------------------------------------------------------------------
Last 0 Keys:

Steps to reproduce:

Install OpenSSH from https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH

Connect to your windows box from somewhere else / localhost via SSH

Run Powershell (with a profile that loads PSReadLine)

This is a duplicate of #158.


Release 1.15

@pvictorlv What do we need for a new release?

I think that's ready to go, for future versions we should work on some tests and some compatibility support for sqlserver and sqlite.

@pvictorlv May you prepare release notes?


[SPARK-35530][ML][TESTS] Fix rounding error in DifferentiableLossAggregatorSuite with Java 11

What changes were proposed in this pull request?

This PR fixes an test failure of DifferentiableLossAggregatorSuite with Java 11.
Why are the changes needed?

I'm personally checking whether all the tests pass with Java 11 for the current master and I found DifferentiableLossAggregatorSuite fails.
https://github.com/sarutak/spark/runs/2661859541?check_suite_focus=true#step:9:13895
The reason seems that the implementation of Blas.daxpy is different between for Java 8 and Java 11. For Java 11, Math.fma is used.
https://github.com/luhenry/netlib/blob/v2.2.0/blas/src/main/java/dev/ludovic/netlib/blas/Java8BLAS.java#L92
https://github.com/luhenry/netlib/blob/0053ea30b11686336cbdb8c7fceb41d59d268fa2/blas/src/main/java/dev/ludovic/netlib/blas/Java11BLAS.java#L40
To remove the rounding error, this PR changes TestAggregator.add with fma.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

I confirmed DifferentiableLossAggregatorSuite passes with both Java 8 and Java 11.

Test build #138970 has started for PR 32673 at commit 89cd2b9.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43490/

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

Test build #139017 has started for PR 32673 at commit 26d9cc8.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43534/

Test build #139017 has finished for PR 32673 at commit 26d9cc8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43534/

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

Merged to master.


Fixed the version release bug.

Please answer these questions before submitting pull request

Why submit this pull request?
[X] Bug fix
_

Bug fix

Bug description.
Version change failure when release version.

How to fix?
Add oracle and resin SDK plugin module into parent maven pom.

Coverage increased (+0.08%) to 23.443% when pulling 12ae3a70ce034b2abcad024e7e0da8923bceb502 on release/5.0.0-beta into 4e047353f9afbb6cf27c73b0ad3dd0b5f6e29170 on master.

We can't add these modules in. Fail in RAT check.


HLS Initial segment number

When restarting it would be good to be able to specify the start number for the segment, so instead of going back to 0 we could restart from an arbitary point
--start-segment-number X

Hi @joolzg, The option --start-segment has been added in version 3.17 as a response to request #197 from ... @joolzg 😉

This is for HLS output, sorry

What do you mean by start segment number in an output playlist?
Is it the value of #EXT-X-MEDIA-SEQUENCE ?

Yes, as if a stream stops and restarts it would be nice to carry on with the sequence instead of starting at 0

Option --start-media-sequence has been added.

Thanks again


New version: CologneCodeCompany.XYplorer version 26.20.0200

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Abandoning this in favor of re-creating a new one with the correct version number.


feat: Beeing able to enable autostart

Allows to enable autostart. May need testing, as it's my first attempt to work on a Terraform module.

👍  LGTM, nice addition


Migration scripts for older versions contain incompatible syntax for H2 2.1.210

Describe the issue:
Migration scripts for older versions contain incompatible syntax for H2 2.1.210. For example, this contains MODIFY syntax which is not officially supported by H2 in default mode (https://github.com/h2database/h2database/issues/2404#issuecomment-575680811).

How to reproduce:
Run a migration from IS 5.3.0 to 6.0.0 with embedded H2 configured as the primary userstore
Possible workaround
Running H2 in Oracle or MySQL compatibility mode might be a possible workaround

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


Added rspec test for connect/bound

Based on contributing-patch.asciidoc
Fixes: #9
If this pull request gets merged, https://github.com/elastic/logstash/blame/master/docs/static/contributing-patch.asciidoc#L224 should be updated to reference a commit-hash prior to this bugfix.

Jenkins standing by to test this. If you aren't a maintainer, you can ignore this comment. Someone with commit access, please review this and clear it for Jenkins to run; then  say 'jenkins, test it'.

Not relevant anymore - logstash-mixin-zeromq

@avishai-ish-shalom The code in logstash-mixin-zeromq is still wrong and does not include the additional tests. I suggest to keep this one open, util logstash-mixin-zeromq is correctly updated.

yeh, did that :)


Xsv Distinct, LdfTabularReader CR fixes

Xsv: Add Distinct mode.
LdfTabularReader CR fixes from Sophie review (not previously submitted).

SBeland reviewed in person.


fix: replace tbl_flatten to flatten():totable()

This also fixes #408

Thanks for the PR!

This introduced a regression for me,
neotest-kotest: ...local/share/nvim/lazy/neotest/lua/neotest/utils/init.lua:4: E5560: vimL function must not be called in a lua loop callback
stack traceback:
	...ocal/share/nvim/lazy/neotest/lua/neotest/client/init.lua:89: in function <...ocal/share/nvim/lazy/neotest/lua/neotest/client/init.lua:88>
	[C]: in function 'has'
	...local/share/nvim/lazy/neotest/lua/neotest/utils/init.lua:4: in function 'tbl_flatten'
	...al/share/nvim/lazy/neotest/lua/neotest/lib/file/init.lua:358: in function 'match_root_pattern'
	/home/cody/dev/src/neotest-kotest/lua/neotest-kotest.lua:13: in function 'root'
	/home/cody/dev/src/neotest-kotest/lua/neotest-kotest.lua:115: in function 'build_spec'
	...al/share/nvim/lazy/neotest/lua/neotest/client/runner.lua:76: in function '_run_tree'
	...al/share/nvim/lazy/neotest/lua/neotest/client/runner.lua:65: in function <...al/share/nvim/lazy/neotest/lua/neotest/client/runner.lua:22>
	[C]: in function 'xpcall'

I'll try and do some more digging

Should be fixed in latest commit :smile:

thanks!


Hide columns in data entry app

This pull request fulfills #352. It adds a feature that hides a column and its input controls if the column has either a tag:misd.isi.edu,2015:hidden or tag:isrd.isi.edu,2016:ignore annotation. If a column has the 2016:ignore annotation and the annotation is an empty array, null, or has the entry context, then the column is hidden.
Columns that are hidden/ignored are also added to the defaults parameter when submitting form data so that the sever will fill in those columns for us.
To Test:
This feature is live on synapse-dev. The Zebrafish:Subject table has both tag:misd.isi.edu,2015:hidden and tag:isrd.isi.edu,2016:ignore annotations on the ID and Sub-sequence columns. The code can be pulled from de-hide-columns#352.

I can confirm that this works the way I expect on my use case. Should assign within UI team to review code and merge though...

Okay I'm assigning to @robes for code review.


doc: add usage section

Add some additional info as requested in https://github.com/dapr/docs/issues/3828

@lburgazzoli did you wanted to add more here? Or should I merge now?

@lburgazzoli did you wanted to add more here? Or should I merge now?

merge it


Pass extra arguments to prisma db seed to the seed command

Problem
I can't pass extra arguments to the command defined in prisma.seed in the package.json to the seed command.
Suggested solution
prisma db seed -- --extra-args=extra-values
Alternatives
Env vars work as well but are not as nice.
Additional context

+1 to this issue.
Usage: for the development environment, we would want args passed to allow for development data to be seeded. For production, we may want some basic production metadata. For now, we will also use an environment variable.


Different resolutions cause options menu to misalign

Offset values to correct menu sliding are hardcoded because I didn't realize the values would change at different resolutions, need to make them calculations instead

Fixed with latest update


how to deal with so serious memory leaks?

see my attachment
memory_leaks.zip

These memory leaks are mostly coming from what looks like CString, which suggests to me that the code that uses pugixml & CString isn't doing something correctly. If you share code used to load the document and extract data from it I might be able to spot the issue.

hi,
i have checkd the leak, when i remove all pugixml codes,as well as lib, the leak still exists, so i think it's not pugixml who lead to this leak happen.
but, i want to show an another error:
when i remove all children of an node, i find nodes haven't been removed when i call saveFile interface after of this, codes show below:
xml_object_range<xml_node_iterator>* pRange = &node->children();
auto iter = pRange->begin();
for (; iter != pRange->end(); iter++) {
node->remove_child(*iter);
}

I'm not sure how this even compiles. You should not be taking a pointer here, use this instead:
xml_object_range<xml_node_iterator> pRange = node->children();
auto iter = pRange.begin();
for (; iter != pRange.end(); iter++) {
node->remove_child(*iter);
}


Add Lambda support

What problem are you facing?
Would like add a AWS Lambda support.
How could Crossplane help solve your problem?
Add Lambda as a managed resource.  It is unclear how this would be supported within Crossplane without design input.
References

This was fixed by #559