add method to export small data set as numpy array, astropy table and/or panda dataFrame

There are method to export to hdf5 or fits file but no method to export directly a selection (small enough) to a classical array or table format such as numpy array, astropy table and/or panda dataFrame.
ds.evaluate() might be part of the solution but it does not accept selection option.

@quiquinSP:
What I had in mind, are a few methods in the Dataset class like

as_dataframe (for pandas)
as_astropy_table
as_numpy (a dict with numpy arrays)

It makes sense for them to take a 'selection' argument, see for instance Dataset.scatter, and the arguments column_names and virtual like export_hdf5, possibly a strings argument like Dataset.get_column_names(..). It may be convenient to give the as_numpy method an extra with_units=False argument to put in the units (see http://docs.astropy.org/en/stable/units/ ). Astropy tables can also take units, for pandas dataframe I am not sure.
You might want to check out in Dataset.scatter how I protect against converting too much data, or see https://github.com/maartenbreddels/vaex/blob/2754156da08fd4fad2555fdf0d85373ebae10a35/vaex/export.py#L291 how I protect against using too much memory, and similary in the gui https://github.com/maartenbreddels/vaex/blob/master/vaex/ui/main.py#L1070 (Just noticed that the gui code should be refactored to use the vaex.utils)
Please also include unittests, looking forward to see you PR!

Implemented in 7ca315b3d8e0ade52d0d8294cc660adafa218a89, with a short description here:
http://vaex.astro.rug.nl/latest/getting_data_in_vaex.html#getting-your-data-out
should be available in the next release


Type casting fix

If we want to utilizate  uint64 type of intersection variable. We should convert 1 to 64 bit value.
Otherwise, if value of i exceeds 32 we can get an unobvious value.

Could you do it (uint64_t) 1 instead, to be size explicit

Done


Add @people completion

https://github.com/suggestions/issue/710584628?repository=telescope.nvim&user_id=nvim-lua&mention_suggester=1
- repository contributors
- issue author
- comment authors
- users already mentioned in comments or description

No description provided.

fixed in #56 by grabbing issue participants from graphql api

fixed in #56 by grabbing issue participants from graphql api

This is a test using Octo.nvim lol


Qh sils permalink

This is the skeleton of  #30.

@sbagg, this is the skeleton of the permalink setup.  I've added what I think is the best first pass at a structure, but right now it's not actaullyty getting any data.

This is the updated theme page with sils-permalink added to it.

@sbagg I see a two issues.  first,  not sure what the os package is you installed in the app, nor do I see where you use it.  Additionally, you added the request package, which I don't see you use.  If you need a HTTP request library that works on both client and server, use node-fetch, if you are just on the client, use the browser native fetch

I realized neither of those libraries are used.  I deleted them and pushed it back up.


pip install django-pg-partitioning, error on windows 10

python verison: 3.7
pip version: 19.0.3
(venv) C:\django projets\api>pip install django-pg-partitioning
Collecting django-pg-partitioning
Using cached https://files.pythonhosted.org/packages/dd/51/1030fbdd6bc64fab059b88a59eeddba4038619c6b978c5bf02b4925e8128/django-pg-partitioning-0.11.zip
Complete output from command python setup.py egg_info:
Traceback (most recent call last):
File "", line 1, in
File "C:\...\pip-install-yoqshn80\django-pg-partitioning\setup.py", line 11, in
long_description = f.read()
File "C:\....\PythonSoftwareFoundation.Python.3.7_3.7.2032.0_x64__qbz5n2kfra8p0\lib\encodings\cp1254.py", line 23, in decode
return codecs.charmap_decode(input,self.errors,decoding_table)[0]
UnicodeDecodeError: 'charmap' codec can't decode byte 0x81 in position 1411: character maps to
Command "python setup.py egg_info" failed with error code 1 in C:\....\pip-install-yoqshn80\django-pg-partitioning\

it's ok when i tried to install on my Python env, maybe the file is broken, try again with another network.


[BuildSystem] Teach swiftc command about -whole-module-optimization. …

…When enabled swift compiler produces one object file and dependency file for the entire module instead of for each of the sources

We should also have a test case for this.
You can teach the "fake" swiftc how to validate these options a tad. That doesn't test against the real thing, but it does protect against modifications to the code having unintended consequences.

ah cool

Added test for both WMO and WMO parallel

@swift-ci please test

@swift-ci please test

@swift-ci please test and merge

@swift-ci please test and merge

@swift-ci please test

I think it's not worth investing in this; -whole-module-optimization plus the -num-threads option goes back to producing several .o files. cc @eeckstein

@ddunbar CI passed but @jrose-apple says it's not worth doing?

I think @jrose-apple was just referring to WMO with !num-threads, as it is "deprecated". I still think we should make it behave correctly as long as the compiler supports it.


feat: add support for query_plans_per_minute

This adds support for configuring the Query Insights sampling rate via the query_plans_per-minute setting.
Closes: #482

What do we need to merge such feature?

/gcbrun

/gcbrun


Warning when using customized cellRenderer

Getting this warning when using cellRenderer.
Warning: Received `false` for a non-boolean attribute `editing`.

If you want to write it to the DOM, pass a string instead: editing="false" or editing={value.toString()}.

If you used to conditionally omit it with editing={condition && value}, pass editing={condition ? value : undefined} instead.
    in td (created by cellRenderer)
    in cellRenderer (created by DataCell)
    in DataCell (created by DataSheet)
    in tr (created by Row)
    in Row (created by DataSheet)
    in tbody (created by Sheet)
    in table (created by Sheet)
    in Sheet (created by DataSheet)
    in span (created by DataSheet)
    in DataSheet (created by DataTable)
    in DataTable (created by Connect(DataTable))
    in Connect(DataTable) (created by App)
    in div (created by App)
    in div (created by App)
    in App
    in div
    in Provider

My renderer looks like this:
const cellRenderer = (props) => {
  const {
    row,
    col,
    cell,
    children,
    ...rest
  } = props;
  let style;
  if (row === 0) {
    style = {
      padding: '3px',
      fontSize: '20px',
      width: '60px',
    };
  }
  // if (col === 0) {
  //   attributes.title = cell.label
  // }
  return (
    <td {...rest} style={style}>
      {props.children}
    </td>
  );
};

hey @teedoo did you figure this out?
I wanted to ask you if you could make a fiddle reproducing it ?

@nadbm thanks for getting back to me. I'm circling back to this issue and I'm still trying to figure it out. But the component below should give you the warning I see. Let me know if you cannot reproduce it.
import React from 'react';
import Datasheet from 'react-datasheet';

export default class TestTable extends React.Component {
  constructor(props) {
    super(props);
    this.state = {
      grid: [
        [
          {readOnly: true, value: ''},
          {value: 'A', readOnly: true},
          {value: 'B', readOnly: true},
          {value: 'C', readOnly: true},
          {value: 'D', readOnly: true}
        ],
        [{readOnly: true, value: 1}, {value: 1}, {value: 3}, {value: 3}, {value: 3}],
        [{readOnly: true, value: 2}, {value: 2}, {value: 4}, {value: 4}, {value: 4}],
        [{readOnly: true, value: 3}, {value: 1}, {value: 3}, {value: 3}, {value: 3}],
        [{readOnly: true, value: 4}, {value: 2}, {value: 4}, {value: 4}, {value: 4}]
      ],
    };
  }

  render() {
    const cellRenderer = (props) => {
      const {
        row,
        col,
        cell,
        children,
        ...rest
      } = props;
      let style;
      if (row === 0) {
        style = {
          padding: '3px',
          fontSize: '20px',
          width: '60px',
        };
      }
      // if (col === 0) {
      //   attributes.title = cell.label
      // }
      return (
        <td {...rest} style={style}>
          {props.children}
        </td>
      );
    };

    return (<Datasheet
      data={this.state.grid}
      valueRenderer={(cell) => cell.value}
      cellRenderer={cellRenderer}
    />);
  }
}

The problem is this:
<td {...rest} style={style}>
rest includes a boolean property called editing, which is not a valid attribute for an HTML td tag.  You need to eat the editing property when you destructure props so that you aren't passing it on to the td:
const {
        row,
        col,
        cell,
        children,
        editing,
        ...rest
      } = props;


add distributed tracing

Pull Request Description
adds distributed tracing repo.
Important to run both 5.0 and 5.2 since the project has a bunch of features only available on 5.2
Acceptance Criteria
To be accepted into the Swift source compatibility test suite, a project must:

[x] be an Xcode or swift package manager project
[x] support building on either Linux or macOS
[x] target Linux, macOS, or iOS/tvOS/watchOS device
[x] be contained in a publicly accessible git repository
[x] maintain a project branch that builds against Swift 4.0 and passes any unit tests

5.0+

[x] have maintainers who will commit to resolve issues in a timely manner
[x] be compatible with the latest GM/Beta versions of Xcode and swiftpm
[x] add value not already included in the suite
[x] be licensed with one of the following permissive licenses:

Apache License, version 2.0

[x] pass ./project_precommit_check script run

PASS: swift-distributed-tracing, 5.2, 73f2b5, Swift Package
========================================
Action Summary:
     Passed: 1
     Failed: 0
    XFailed: 0
    UPassed: 0
      Total: 1
========================================
Repository Summary:
      Total: 1
========================================
Result: PASS
========================================
--- swift-distributed-tracing checked successfully against Swift 5.2 ---

Can you also add tag "tags": "swiftpm"? example: https://github.com/apple/swift-source-compat-suite/blob/main/projects.json#L201

Can you also add tag "tags": "swiftpm"? example: https://github.com/apple/swift-source-compat-suite/blob/main/projects.json#L201

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test

@ktoso looks like it conflicts now, could you resolve so this can be merged

@ktoso looks like it conflicts now, could you resolve so this can be merged

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test and merge

@swift-ci test and merge

@swift-ci test

@swift-ci test


Drill picking does not work

@bagnell can you look at this before the 1.23 release on Friday?
Select Drill-Down Picking in the Picking Sandcastle example and mouse over the polygons.  They do not highlight in 1.23.
Compare
1.22.1: http://cesiumjs.org/releases/1.22.1/Apps/Sandcastle/index.html?src=Picking.html&label=Showcases
to
master: http://localhost:8080/Apps/Sandcastle/index.html?src=Picking.html&label=All

Just a reminder that this is needed for the release tomorrow.

Fixed in #4072.


app.asar larger after updating electron-vue (node_modules related)

Now, this isn't an extremely serious issue, but after updating my project to the most recent electron-vue template (including webpack 2) and using electron-packager (as I've always done), I've noticed that resources/app.asar is 30mb larger than it used to be, which is making my final zipped size 65mb instead of 50mb.
I extracted app.asar to have a look, and it has a node_modules folder which is full of packages. I checked my older builds and saw that the node_modules folder inside app.asar was empty. If I am understanding this correctly, the previous build was bundling modules into build.js. Is there a way to achieve the previous behaviour?
I've modified a few things in the configs, but don't think they were relevant to this. I can provide more info if necessary.

@zxc23
Yes, you would be correct. The newer electron-vue treats all packages as webpack externals and no longer bundles everything into one build.js file. The main reasoning for this was to support the main process and eliminate issues related to native node modules. All that to say, node_modules is now included within production builds.
Now there a few things you can try to minimize any extra overhead in file size.
Option 1
Use yarn clean within the app directory. This will go through all node_modules and remove extraneous files to limit overall package size (More Info). That why markdown files, test files, etc. will be removed before packaging.
Option 2
Configure webpack to no longer treat dependencies as externals by removing webpack.renderer.config.js@L18 and re-adding node_modules to the build setting's ignore option at config.js@L30 (Line numbers vary). This will set things back to bundling all assets into one file.

Thanks for the response.  I already had the externals line (almost) cleared, but the ignore option I had not updated. I ended up breaking things and then fixing everything... pretty sure it's all OK now. Easy to break things I have to say! But I've learnt a lot about electron, vue, and webpack from electron-vue, so I must give my thanks! 👍

No problem. And for anybody else that reads this later, feel free to comment any further questions. I'll be detailing some of this info in the documentation.

hi @SimulatedGREG
indeed it would be nice to mention how to use yarn clean in the docs, as the docs mention it but does not explain how to use it. I found this issue by looking for explanations.
Best,
Emmanuel

@emmanuelgeoffray
Just as posted above, the yarn documentation does a fairly good job at describing what yarn clean accomplishes. When using the current version of electron-vue, after installing dependecies with yarn, you can follow that with yarn clean.
Just as noted in the yarn documentation, this feature is typically meant for more advanced users, and there probably isn't a guarantee that your application dependencies will fully function afterwords (but I'm sure yarn knows what to do for the most part). In the end, this may not make too much of a significant difference to build size.

Thanks @SimulatedGREG for the clarification!


Conflictvisualizer Map Page Integration

PR Details
This PR integrates the jpo-conflictvisualizer map page into the cvmanager. This change allows intersection data, collected with the conflictmonitor, to be visualized in the intersection map page of the cvmanager. This is the first step in integrating the functionality of the cvmanager and conflictvisualizer tools together!
Description
This change adds a new intersection map page, which combines the Conflictvisualizer map page with the existing RsuMap intersection view. This also includes
How Has This Been Tested?
These changes have been tested by visualizing MAP/SPAT/BSM data on the map, and comparing the displays with the original jpo-conflictvisualizer.
These changes were tested running locally in docker. These changes require a jpo-Tconflictvisualizer api to be running, and to be connected to the cvmanager keycloak server (and cvmanager keycloak realm). This API also requires the jpo-conflictmonitor and jpo-geojsonconverter to be running, so that there is data available.
These changes do not affect the API or the Keycloak server.
Types of changes

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

Checklist:

[x] My changes require new environment variables:

[ ] I have updated the docker-compose, K8s YAML, and all dependent deployment configuration files.

[x] My changes require updates to the documentation:

[ ] I have updated the documentation accordingly.

[x] My changes require updates and/or additions to the unit tests:

[ ] I have modified/added tests to cover my changes.

[ ] All existing tests pass.

I created this PR as a draft, because I still have to complete a few tasks: Adding unit tests for the jpo-conflictvisualizer map page, and fixing merge conflicts

We should definitely add the required services to a docker-compose and provide information/links to deploying this so this can be easily replicated. I want to test this but I want to make sure I am doing this correctly since I have never run the conflict visualizer locally before. New users of the cv-manager will be even more clueless.

The python unit tests pass for me, but I am running into test failures with the webapp tests:

I am seeing the following error predominantly:

TypeError: Color is not a function

Using npm version 10.7.0

Just pushed a commit to resolve this issue!


Groovy-based SimpleTemplateScript1 parser for job yaml file complains about characters in commented-out lines

If you have a job spec file that contains something like:
# excludeFileNamePattern: exclude file name pattern, supported glob pattern.
# Sample usage:
#   'glob:*.avro' will exclude all avro files just under the inputDirURI, not sub directories;
#   'glob:**\/*.avro' will exclude all the avro files under inputDirURI recursively.
# _excludeFileNamePattern: ''

Then the parsing of this file will fail with:
SimpleTemplateScript1.groovy: 37: unexpected char: '\' @ line 37, column 13.

Where line 37 is #   'glob:**\/*.avro' will exclude all the avro files under inputDirURI recursively.. The problem is the \ character, which should be getting ignored since the line is commented out.

The Groovy Template Engine documentation warns about backslashes in text:

If you happen to be embedding your template directly in your script (as we did above) you have to be careful about backslash escaping. Because the template string itself will be parsed by Groovy before it is passed to the templating framework, you have to escape any backslashes inside GString expressions or scriptlet 'code' that are entered as part of a Groovy program

I think an appropriate solution would be to modify GroovyTemplateUtils.renderTemplate() to first strip out comment lines (maybe with a boolean parameter to control?) before passing text to the GROOVY_TEMPLATE_ENGINE. Or we could try to automatically escape backslashes, but I'd be in favor of removing comments.

The Groovy Template Engine documentation warns about backslashes in text:

If you happen to be embedding your template directly in your script (as we did above) you have to be careful about backslash escaping. Because the template string itself will be parsed by Groovy before it is passed to the templating framework, you have to escape any backslashes inside GString expressions or scriptlet 'code' that are entered as part of a Groovy program

I think an appropriate solution would be to modify GroovyTemplateUtils.renderTemplate() to first strip out comment lines (maybe with a boolean parameter to control?) before passing text to the GROOVY_TEMPLATE_ENGINE. Or we could try to automatically escape backslashes, but I'd be in favor of removing comments.

Agreed. Will make the change.

Agreed. Will make the change.

I just noticed some yaml files have a comment at the end of a line, so the stripping should be from # to end of line, not complete lines.

I just noticed some yaml files have a comment at the end of a line, so the stripping should be from # to end of line, not complete lines.

Hi @fx19880617 - thanks for fixing so quickly!
I am curious, though - since the template engine is inspecting text (even comments), could a poorly-formed substitution pattern in a comment also trigger an issue?

Hi @fx19880617 - thanks for fixing so quickly!
I am curious, though - since the template engine is inspecting text (even comments), could a poorly-formed substitution pattern in a comment also trigger an issue?


bug: RangeError: Invalid count value

Node.js version
19
NPM version
9
@checkly/cli version
4.03
Steps to reproduce
Trigger checks using --trigger while passing some --tags. It does not fail on every run. It's not clear what happens inside the CLI causing this.
The output on CI is
RangeError: Invalid count value: -4
    at String.repeat (<anonymous>)
    at formatSectionTitle (/home/circleci/.npm/_npx/a66ee913fe899ce0/node_modules/checkly/src/reporters/util.ts:234:39)
    at formatCheckResult (/home/circleci/.npm/_npx/a66ee913fe899ce0/node_modules/checkly/src/reporters/util.ts:98:7)
    at CiReporter.onCheckEnd (/home/circleci/.npm/_npx/a66ee913fe899ce0/node_modules/checkly/src/reporters/ci.ts:29:45)
    at /home/circleci/.npm/_npx/a66ee913fe899ce0/node_modules/checkly/src/commands/trigger.ts:130:32
    at Array.forEach (<anonymous>)
    at TriggerRunner.<anonymous> (/home/circleci/.npm/_npx/a66ee913fe899ce0/node_modules/checkly/src/commands/trigger.ts:130:17)
    at TriggerRunner.emit (node:events:512:28)
    at TriggerRunner.emit (node:domain:489:12)
    at TriggerRunner.processMessage (/home/circleci/.npm/_npx/a66ee913fe899ce0/node_modules/checkly/src/services/abstract-check-runner.ts:154:12)

What is expected?
The checks to fail or succeed without running into an RangeError.
What is actually happening?
Checks run into a RangeError.
Any additional comments?
No response

@clample could you take a look at this one when you have the availability? It is a weird error

@tdeekens thank you for reporting this issue. This should fixed in version 4.0.6 of the CLI.
Some CI environments set a terminal width of 0. The CLI wasn't handling this correctly, and I believe that was causing this RangeError when the CLI formatted output for the terminal. There should be better handling for this case now.


how to use the webapp

In your introduction you said it can be used via a webapp, so how do i use it?
thank you for your great work

Sorry,i'm busy these days.
But You said this function would like to be realized later


Show a demo url

Show a demo url

Can you explain better? Thanks

Show a website url

Well, in the next update I will add usage examples in the README.
A demo URL which could be used could be:
https://youtu.be/dQw4w9WgXcQ


Aggregate and simplify rules

Currently, jscs has 49 rules (not counting non-esprima options) and will have more i suspect, much more, most of these rules are pretty simple and can take only one or two possible values like true/false, some rules are complete opposite of each other, for example requireSpaceAfterKeywords, disallowSpaceAfterKeywords, some does not have their significant other, like disallowSpacesInsideParentheses doesn't have requireSpacesInsideParentheses some complement each other, eg disallowSpacesInsideArrayBrackets, disallowSpacesInsideParentheses, and so forth...
This amount of rules, their incompleteness could be overwhelming to set up, change and support.
At the beginning, when amount of rules was low, it was simpler and faster to add more features then try to unify them, i think now or in the near future it would makes sense to give them more structure.
This –
"requireSpaceAfterKeywords": ["if"],
"disallowSpaceAfterKeywords": ["else"],
"requireSpacesInFunctionExpression": { "beforeOpeningRoundBrace": true, "beforeOpeningCurlyBrace": false },
"disallowMultipleVarDecl": true,

could become
"space after keywords": {
	"require": ["if"],
	"disallow": ["else"]
},
"spaces in function expression": {
	"require": "before opening brace",
	"disallow": "before opening curly brace"
},
"multiple var decl": false

or
"require": {
	"space after keywords": ["if"],
	"spaces in function expression": "before opening brace"
}
"disallow": {
	"space after keywords": ["else"],
	"spaces in function expression": "before opening curly brace",
	"multiple var decl": true,
}

or
"require": [
	{ "space after keywords": ["if"] },
	{ "spaces in function expression": "before opening brace" }
],
"disallow": [
	{ "space after keywords": ["else"] },
	{ "spaces in function expression": "before opening curly brace" },
	"multiple var decl"
]

Or other formats could be adopted, goal is to make rules consistent with each other, if something is allowing something, something could declare the opposite.
If this idea is acceptable, i propose to figure out the new format and what rules are missing.
Although this is pretty big change, but of course, current format should be supported too.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/3406394-aggregate-and-simplify-rules?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F281640&utm_medium=issues&utm_source=github).

Yeah I'm forgetting to update all the function rules - there's (require|disallow)spacesIn functionExpression, anonymousFunctionExpression, namedFunctionExpression, functionDeclaration, function
functionExpression, anonymousFunctionExpression, namedFunctionExpression are basically the same code except for the node.id check

We can close this or #698 right?

Just closing this in favor of #698 for less duplication.


export internal subscriptions of feedback and status

For internal review.
Signed-off-by: Chen Lihui<EMAIL_ADDRESS>

@fujitatomoya @Barry-Xu-2018
Could you help me review this?

LGTM

Close it. (already pushed into official PR)


Removing Toolbar div completely

Hi All,
for a very Special case (only displaying Action Buttons within a Serenity grid) I want to completely remove the Toolbar div so that there is no large gap between the title and the actual grid.
I know that I can remove the toolbar Buttons and the search field but that leaves still the same vertical gap between title and the grid.
Is there some easy overriding of a method (like removing the search field by overriding createQuickSearchInput)?
I did a search in the classes:

Serenity.EntityGrid
Serenity.DataGrid

but didn't find anything useful.
Thanks for any input and
with Kind regards,
John

in .less
.s-MyModule-xyzDialog  s-Toolbar{
display:none;
}

https://github.com/volkanceylan/Serenity/issues/2086

You can completely hide div with $('.s-DialogToolbar').hide();

Hi @Zahar661 ,
thanks - the solution in #2086 given by Estrusco is exactly what I wanted :-)
Thanks @Estrusco , I played around with this but found your solution in #2086 the perfect hit :-)
protected createToolbar(): void {
}

Thanks for all your help and with Kind regards,
John


NIFI-12192 Add Codecov Reporting with JaCoCo

Summary
NIFI-12192 Adds code coverage for unit tests using the JaCoCo Maven Plugin reporting to Codecov.
Codecov provides free reporting capabilities for open source projects and enables integration with GitHub workflows using the Codecov Action.
The implementation of code coverage reporting updates the GitHub ci-workflow to run the Ubuntu Linux Java 21 job with JaCoCo coverage enabled. The JaCoCo plugin writes an aggregated report in XML, using the nifi-code-coverage module to aggregate coverage information based on an enumeration of dependencies. The Maven module is necessary for selecting and aggregating coverage reporting information. The Codecov Action reads the JaCoCo XML and sends it to Codecov for processing.
The JaCoCo prepare-agent goal updates the argLine property, which required removing custom locale information from the Ubuntu Linux job, instead relying on the default settings of the GitHub runner.
Updates include adding a Codecov badge to the README for displaying coverage on the main branch.
Current code coverage information is available in Codecov for this feature branch.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 21

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[ ] Documentation formatting appears as expected in rendered files

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

@exceptionfactory thanks for the update, the code coverage will help improve confidence in the code base going forward.
I've suggeted a couple of options to think about for improving the use of JaCoCo - more for consideration than blockers to merging this PR.
As discussed elsewhere, would it be sensible to update the integration-tests-ci profile to skip all ITRedisDistributedMapCacheClientService ITs as part of this PR - more of them failed the first time in the PR checks, but then succeeded on the retry?


Speed up transformation using Caching

(See https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows for documentation)
Currently, most of the time is spent fetching, cloning and pushing the two repositories, with a usually very short actual transformation in between
If we cache the repos, and only pull to get the current state, without needing to clone every time a single file changed, we could probably speed the transformations up by 5 to 10 minutes I think.
However, a repository may only have up to 10 GB cached data at a time. I'm not entirely sure if this disallows caching the repos — how big are they?
If size is a constraint, it might be sensible to cache only one of them (still a speed-up) or, if the issue is the git history, ensuring to remove the history (locally) after pulling or something before updating the cache
If all else fails, at the very least maybe cache the dependencies (apt packages and deno)?
@retog opinions?

Local cloning & du -sh tells me that (treatments-xml) is 16G when shallow-cloned (--depth=2) and ~19G with full history.
That rules out caching the repos


Clarify documentation for std_dev()

I'm a BA student who's learning Python for the first time. I was looking at your function to calculate the standard deviation in models.py and got very confused! What does all the commented code mean? Does it do the same as np.std() in the same function? It would be very helpful for my homework if you could clarify why the commented code is there.

The commented code needed to be deleted. Solved in b6995dbccc7f875f9e6a5122c2e305c6fceff4fc.


[SPARK-23908][SQL][FOLLOW-UP] Rename inputs to arguments, and add argument type check.

What changes were proposed in this pull request?
This is a follow-up pr of #21954 to address comments.

Rename ambiguous name inputs to arguments.
Add argument type check and remove hacky workaround.
Address other small comments.

How was this patch tested?
Existing tests and some additional tests.

cc @cloud-fan @hvanhovell

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2069/
Test PASSed.

Test build #94599 has started for PR 22075 at commit 3ccd995.

Test build #94599 has finished for PR 22075 at commit 3ccd995.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Jenkins, retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2073/
Test PASSed.

Test build #94604 has started for PR 22075 at commit 3ccd995.

Test build #94604 has finished for PR 22075 at commit 3ccd995.

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

Merged build finished. Test PASSed.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2105/
Test PASSed.

Test build #94651 has finished for PR 22075 at commit 388c2d3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
trait HigherOrderFunction extends Expression with ExpectsInputTypes
trait SimpleHigherOrderFunction extends HigherOrderFunction

Merged build finished. Test FAILed.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2111/
Test PASSed.

Test build #94663 has started for PR 22075 at commit 4b48a39.

LGTM

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2113/
Test PASSed.

Test build #94668 has started for PR 22075 at commit deee1dc.

Test build #94663 has finished for PR 22075 at commit 4b48a39.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

Test build #94668 has finished for PR 22075 at commit deee1dc.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2119/
Test PASSed.

Test build #94674 has started for PR 22075 at commit deee1dc.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2121/
Test PASSed.

Test build #94674 has finished for PR 22075 at commit deee1dc.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test FAILed.

Jenkins, retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2125/
Test PASSed.

Test build #94679 has started for PR 22075 at commit deee1dc.

Test build #94679 has finished for PR 22075 at commit deee1dc.

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

Merged build finished. Test PASSed.

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

thanks, merging to master!


Fix/multiple improvements and fixes

Allocation

Added ability to specify the maximum space in GB using --size_in_gb.
Removed --threshold parameter.
Changed the default number of --workers to adapt to the number of CPU threads.
Now, disk space is distributed equally among validators.
Added --disable_verify param to disable data allocation verification.
Optimized the --restart parameter, which greatly slowed down the regeneration of the databases.
Allowed to reduce the allocated size without having to rebuild the databases from scratch.
Optimized Rust code for faster data generation.
Reworked allocation code to improve performance.
Added auto-update.

Validator

Removed miner_min_chunks and miner_max_chunks.
Changed validation increment rate from 1.1 (10%) to fixed 10GB. It was producing validator freezes.
Now, DB size increases dynamically, not at start.
Optimized all the code.

Miner

Added ability to specify the maximum space in GB. --size_in_gb
Removed --threshold parameter.
Optimized all the code.
Added auto-update.
If a new hotkey is registered, the previous hotkey database is disconnected and deleted.


debian 7 support broken

Affected Puppet, Ruby, OS and module versions/distributions
operating system debian 7
How to reproduce (e.g Puppet code you use)
      openvpn::server { 'test_openvpn_server':
        country      => 'FR',
        province     => 'Occitanie',
        city         => 'France',
        organization => 'FOO',
        email        =><EMAIL_ADDRESS>        server       => '<IP_ADDRESS> <IP_ADDRESS>',
        local        => '',
      }

What are you seeing
When this module is used on debian 7, the current settings about cipher with a so old operating system, does not work. The service openvpn does not start
What behaviour did you expect instead
process openvpn started.
Output log
The start of openvpn server log the following :
Problem with cipher list: TLS-DHE-RSA-WITH-AES-256-GCM-SHA384:TLS-DHE-RSA-WITH-AES-256-CBC-SHA256:TLS-DHE-RSA-WITH-AES-128-GCM-SHA256:TLS-DHE-RSA-WITH-AES-128-CBC-SHA256: error:1410D0B9:SSL routines:SSL_CTX_set_cipher_list:no cipher match
If removing debian 7 support is considered as possible option,  i can provide a PR.

debian 7 is removed from metadata.json, but code is yet present in module.

Hi @Dan33l. Debian 7 isn't supported anymore. Can you please provide a PR to remove the related code?

Yes. Before, i wanted to work about EasyRSA PR #292 .


Feature Request: Add the ability to specify a virtual network

Hello, I think it would be good to add an option to start-all.sh that enables the user to specify a Docker virtual network for the Prometheus and Grafana containers. This would greatly help the Mutant Monitoring Blog Series that uses a virtual network for the Scylla containers.

The docker command is like this for a container:
docker run -d  --net=mms_web --name container-name container

I think start-all.sh can have a -n or --network option

That will not work because we are running 3 Scylla nodes. --net=host would put all the Scylla nodes on the host interface with the same IP.

@amnonh can you help? the best will be to find a way to propagate any list of parameters to each of the 3 docker run command

@amnonh ping

Just sent a pull request for a general capability to add container
parameter option
On Tue, Apr 17, 2018 at 8:38 AM, Tzach Livyatan<EMAIL_ADDRESS>wrote:

@amnonh https://github.com/amnonh ping
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/scylladb/scylla-grafana-monitoring/issues/312#issuecomment-381850126,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACBRv_2-j8U4kIsK59Iceb9p6uG5WCQcks5tpX_QgaJpZM4TOn5r
.

fixed by #314


POST /model doesn't work

Rasa version: image: rasa/rasa_core:latest (from docker-compose)
Issue: When trying to push a model to POST /model endpoint, I get a 500 Internal Server Error. I use Content-Type: multipart/form-data as header and an attribute "model" which is a trained model as ZIP (with command python -m rasa train core [...]).
Content of configuration file (config.yml):
language: en
pipeline: supervised_embeddings
policies:
  - name: KerasPolicy
    epochs: 100
    max_history: 5
  - name: FallbackPolicy
    fallback_action_name: 'action_default_fallback'
  - name: MemoizationPolicy
    max_history: 5
  - name: FormPolicy
  - name: MappingPolicy

rasa_core_1 server logs:
rasa_core_1      | 2019-04-25 14:09:08 INFO     rasa.core.server  - Received new model through REST interface.
rasa_core_1      | [2019-04-25 14:09:08 +0000] [1] [ERROR] Exception occurred while handling uri: 'http://localhost:5005/model'
rasa_core_1      | Traceback (most recent call last):
rasa_core_1      |   File "/usr/local/lib/python3.6/site-packages/sanic/app.py", line 750, in handle_request
rasa_core_1      |     response = await response
rasa_core_1      |   File "/app/rasa/core/server.py", line 148, in decorated
rasa_core_1      |     result = await result
rasa_core_1      |   File "/app/rasa/core/server.py", line 543, in load_model
rasa_core_1      |     model_file.save(zipped_path.name)
rasa_core_1      | AttributeError: 'list' object has no attribute 'save'
rasa_core_1      | 2019-04-25 14:09:08 ERROR    sanic.root  - Exception occurred while handling uri: 'http://localhost:5005/model'
rasa_core_1      | Traceback (most recent call last):
rasa_core_1      |   File "/usr/local/lib/python3.6/site-packages/sanic/app.py", line 750, in handle_request
rasa_core_1      |     response = await response
rasa_core_1      |   File "/app/rasa/core/server.py", line 148, in decorated
rasa_core_1      |     result = await result
rasa_core_1      |   File "/app/rasa/core/server.py", line 543, in load_model
rasa_core_1      |     model_file.save(zipped_path.name)
rasa_core_1      | AttributeError: 'list' object has no attribute 'save'

Thanks for raising this issue, @tabergma  will get back to you about it soon.

@Djiwaye I didn't had time to look into the issue yet. Will have a look hopefully this week.

@Djiwaye Found the issue. request.files['model'] returns a list instead of a dict. Should be request.files.get('model') instead (see https://github.com/RasaHQ/rasa_core/blob/master/rasa/core/server.py#L536).
However, on master the issue is already fixed, thus no changes needed. We recently merged the Core and NLU server into one server. The model endpoint still exists, but instead of providing binary data you just provide the path to the model (see https://github.com/RasaHQ/rasa/blob/master/docs/_static/spec/server.yaml#L636).

Hello @tabergma
Thanks for you help. I'll use the latest stable version until next master stable release.


added logging properties to all workflows

Related to this ticket: https://issues.redhat.com/browse/FLPATH-1659

@ElaiShalevRH as part of this story, pls add also the missing property to
https://github.com/parodos-dev/workflow-software-templates/blob/main/scaffolder-templates/basic-workflow/skeleton/src/main/resources/application.properties#L2
and
https://github.com/parodos-dev/workflow-software-templates/blob/main/scaffolder-templates/complex-assessment-workflow/skeleton/src/main/resources/application.properties

@masayag Maybe we should create a subfolder 'workflows' and put all workflows in it so we don't get lost with all non-related folder that come in between the workflows folders when listed in alphabetical order

@gabriel-farache that's a good idea. this entitle a jira issue on its own, since it isn't only moving the folders, but also adapting all of the scripts and github actions.


Initial File List feature does not support delete function

I would like to know, if Initial File List supports delete feature? Currently, I can see only Cancel button when the FineUploader renders with previously uploaded files.
From my understanding, Cancel just removes a file from the list (including the DOM element); but it does not remove it from the file server.
Having delete function for the initial file list would help to keep the front end list of files in sync with the actual files in the file server.

looks like this is covered by #134 / #128

Having the same problem here. The delete button is showed for the Initial File List. However, clicking it does not fire any http requests. Just remove the item from the DOM. Will investigate it further and get back to you.

From what I could gather so far, Delete Button for server loaded files does not match the this.props.id with the ID received from the Status Change event raised by the uploader.  Bypassing this check, I could delete the file.
line 27 on delete-button.jsx
if (id === _this.props.id && !_this._unmounted) {
  ...
}

Will continue to investigate why the ID prop does not match.

I fixed it calling _onStatusChange() when the DeleteButton component is mounted (rendered into the view). The problem is that the button's deletable state isn't recalculated when the files are pulled from the sessiom endpoint.
My problem was with Vue version of FineUploader but I pressume it's the same with the React one:
DeleteButon.vue
mounted () {       // Force a status change to recalculate deletable state       this.uploader.methods.getUploads().map(item =>         this._onStatusChange(           item.id,           item.status,           item.status         )       )       this.uploader.on('statusChange', this._onStatusChange)     },
I hope it help!


How to show different custom keyboard by sending different commands?

I used this, but it is not working:
    elif command == '6':        keyboard = ReplyKeyboardMarkup(keyboard=[['Add', 'List'], ['Settings', 'Web']])

Here is an example you can try and apply the method to your code
if command ==1:       keys=[]       keys.append([InlineKeyboardButton(text='Next', callback_data='next1')])       tags = InlineKeyboardMarkup(inline_keyboard=keys)

@codingsett I'm getting this error File "mybot.py", line 49     keys=[] keys.append([InlineKeyboardButton(text='Next', callback_data='next1')]) tags = InlineKeyboardMarkup(inline_keyboard=keys)


Suggestion: cost

Add a configurable item cost to redeem a player head (e.g. 3 bones)

Implemented in 1.1.0


⚠ AsianCinema has degraded performance

In a698237, AsianCinema ($ACM) experienced degraded performance:

HTTP code: 200
Response time: 2664 ms

Resolved: AsianCinema performance has improved in 776be60 after 8 minutes.


Simplify auto configurations

drop regexes identical to or compatible with the default regex,
drop template expressions identical to or compatible with the default template expression,
simplify 0|[1-9]\d* to \d+ in regexes.

Ran https://github.com/endoflife-date/release-data/blob/main/update.rb against the modified version, no diff observed.


Support for list variable as argument to Functions.type

I am trying to generate this piece of cypher where p is a path in match statement like MATCH p = (s)-[r*1...10]->(t)
[x in relationships(p)| type(x)]

Here is what I am trying using the cypher-dsl library
     ...
        // Trying to build [x in relationships(p)| type(x)]
        var x = Cypher.name("x");
        var relationTypeCast = Cypher.listWith(x)
                .in(Functions.relationships(p))
                .returning(Functions.type(x)); // <===== Error here: Cannot cast Symbolic name to RelationShip
       ...

I cannot compile the code because the variable x is of type SymbolicName where as Functions.type expects a RelationShip as argument.
I have worked around my problem by rewriting the cypher without this piece of query, but I am curious to know how to write this in cypher-dsl.
PS: I am trying to find all paths between two nodes where the path contains a list of relations anywhere within the path. There are many ways to write such a cypher query and just the first one I thought of and tested on Neo4j Browser had this piece of query but I couldn't translate it to cypher-dsl because of this issue.

Thanks for using Cypher-DSL and raising this issue, @sathishkumar294 This will be added in 2023.2.0. Until then, here's also one workaround:
@Test // GH-630
void typesOfShouldWork() {

    var p = Cypher.path("p").definedBy(Cypher.node("Movie").relationshipFrom(Cypher.anyNode()).named("r"));
    var x = Cypher.name("x");
    var relationTypeCast = Cypher.listWith(x)
        .in(Functions.relationships(p))
        .returning(Functions.type(x));

    assertThat(Cypher.match(p).returning(relationTypeCast).build().getCypher())
        .isEqualTo("MATCH p = (:`Movie`)<-[r]-() RETURN [x IN relationships(p) | type(x)]");

    // Current workaround
    var relationTypeCast2 = Cypher.listWith(x)
        .in(Functions.relationships(p))
        .returning(Cypher.call("type").withArgs(x).asFunction());
    assertThat(Cypher.match(p).returning(relationTypeCast2).build().getCypher())
        .isEqualTo("MATCH p = (:`Movie`)<-[r]-() RETURN [x IN relationships(p) | type(x)]");
}

2023.2.0 is drop-in compatible with all 2023.0.0 versions for all normal use cases.
Would that be enough for your or do you need it in a 2022.9 release, too?

Hi, thanks for the reply. We think alike, my workaround is exactly the same as yours 😀
I can wait till the release of 2023.2.0.
Thanks 👍🏽


Syntax error

Right, i have had issues with this help site before and i do not appreciate the daily struggle that i have to go through just to use your programmes. i am coming to the end of my tether, Janice. i am going to assume that is the name of the imbussile that reads these comments as previous statements that i have made have been blatently ignored. answer my comments or i'll cry (huawwwwwwww).

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

ID: d7c27586-2635-6fb1-8578-521435f95cbe
Version Independent ID: c2096aed-82c6-e9c9-c01f-d51d8acbf18e
Content: Syntax error
Content Source: Language/Reference/User-Interface-Help/syntax-error.md
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

Perhaps if instead of name-calling and complaining you actually described what the problem is, people would be more inclined to fix whatever issue it is that you might have found?
Glad you don't actually submit PRs and fix them yourself though, seeing how you write.

an imbecile that reads every comment made in this repository

@uyyrilth
Thanks for your feedback. We use Github Issues for documentation bugs, not for developer support. Please try the VBA developer community on Stack Overflow (https://stackoverflow.com/questions/tagged/vba) where you can get help from actual developers. If you find a bug in our documentation, please give us specific information as to what's wrong and how you recommend fixing it. Thank you.
@retailcoder Thank you for your input. It was spot on...


[Bug] On Relationship Field, the attribute 'attribute' doesn't work in Show View

This is a regression between a previous version of Backpack and version 5.2.1
With an identical configuration, the relationship type field has a different behavior between the ListView and the ShowView
In the ListView, the attribute works and displays my user's 'name'
In the ShowView, the attribute does not work and displays the identifier and/or the JSON object of my user

Hello @MDW-Chris thanks for the report.
List and Show uses Columns, not Fields, it might be a typo no worries.
Can you provide me more detailed information ? Your column definition, your relation definition ?
Cheers

Hello, that's right, it's Columns
class Project extends Model
{
   public function lead_user()
   {
      return $this->belongsTo(User::class);
   }
}

class ProjectCrudController extends CrudController
{
   protected function setupListOperation()
   {
      /* 'lead_user_id' display now the ID -- 'lead_user' display the JSON object of the relation */
      CRUD::addColumn([
         'name'      => 'lead_user_id',
         'type'      => 'relationship',
         'label'     => 'Leader',
         'attribute' => 'name',
      ]);
   }
}

In the ListView, the attribute works and displays my user's 'name'
In the ShowView, the attribute does not work and displays the identifier and/or the JSON object of my user

Thanks for clarification 🙏
I will make my tests and come back to you with my findings.
Cheers

Hello @MDW-Chris
I am sorry, but still unable to reproduce your issue:
my column:
[
    'name'      => 'category_select2',
    'type'      => 'relationship',
    'label'     => 'My test column',
    'attribute' => 'name',

],

my relation:
public function category_select2()
{
    return $this->belongsTo(\Backpack\NewsCRUD\app\Models\Category::class, 'select2');
}
```php

The results in List:
![image](https://user-images.githubusercontent.com/7188159/180981483-6e28e12c-cc69-4fd8-95c2-cd741c5f76b4.png)
The results in Show:
![image](https://user-images.githubusercontent.com/7188159/180981605-4b379566-13af-4829-8c9b-381330ba3350.png)

What am I doing different than you ?

Sorry I was not able to reproduce it yet :| we will get there eventually.

Cheers

Hey @MDW-Chris nice catch! 👍 Glad you figured it out.
Please be advised that it will change again in future as per this PR: https://github.com/Laravel-Backpack/CRUD/pull/4542
Maybe subscribe to it so you get notified when it gets merged 👍
Going to close this, cheers.


Question about AbstractClusterInvoker.doSelect method

Why canot select the last invoker  of invokers.
Environment

Dubbo version: 2.7.3
Operating System version:
Java version: 1.8

Steps to reproduce this issue

AbstractClusterInvoker.doSelect

first look at the location of the first selection, if not the last, select the index+1 position, in order to avoid collision

Thanks, the invoker and rInvoker is not the same object.


use fbjni as gradle dependency to solve flipper issue for android

See https://github.com/facebook/flipper/issues/707#issuecomment-573025000.
I want to know is there some hack or pitfalls in current repo.
I see fbjni already as an indendenct repo https://github.com/facebookincubator/fbjni.
cc @passy @swolchok

I believe this is the strategy in https://github.com/facebook/react-native/pull/27729

I believe this is the strategy in #27729

yeap.


nanopolish: src/alignment/nanopolish_anchor.cpp:141: HMMRealignmentInput build_input_for_region(const string&, const string&, const Fast5Map&, const string&, int, int, int, const string&): Assertion `template_idx != -1 && (!sr.has_events_for_strand(C_IDX) || complement_idx != -1)' failed.

Hi,
We recently MinION sequenced a plasmid, which was massive overkill, but fun.
I assembled it in Canu and want a better consensus. It is 7.2 kb.
I did this:
nanopolish extract --type 2d pass/ > pass.nanopolish.fa
G=../plasmid-highcov.contigs.fasta
bwa index $G
I=$G
R=pass.nanopolish.fa
bwa mem -M -x ont2d $I $R -t 8 | samtools sort | samtools view -F 4 -q 60 -bSh - > pass.nanopolish.bam
samtools index pass.nanopolish.bam
nanopolish consensus -r pass.nanopolish.fa -b pass.nanopolish.bam -g $G -o plasmid.asm.nanopolish.fasta --models-fofn nanopolish_models.fofn -w tig00000000:0:7120 -t $T

I got this:
nanopolish: src/alignment/nanopolish_anchor.cpp:141: HMMRealignmentInput build_input_for_region(const string&, const string&, const Fast5Map&, const string&, int, int, int, const string&): Assertion `template_idx != -1 && (!sr.has_events_for_strand(C_IDX) || complement_idx != -1)' failed.

Do you have any insight into what I can do to get past this error?
Many thanks,
John

p.s. I am using the latest code on github -- just cloned and installed today.

Hi John,
nanopolish consensus has been rewritten in the nanopolish variants module. Could you run the new version using the instructions here:
https://github.com/jts/nanopolish#computing-a-new-consensus-sequence-for-a-draft-assembly
Let me know how it goes.
Jared

Thanks Jared.
It has been running for ~1 hour, so I am guessing it is doing its thing.
It is a 7.2 kb sequence with 4000x coverage (I know - total overkill).
Any ideas on how long it might run for?

It finished in 4-5 hours. Thanks for the putting me in the right direction.

Thanks for the update. The long runtime is (partially) caused by the excessive depth. I'm not sure if having 4000x will effect accuracy but I suggest you have a careful look at the results.

If I have a chance I will look into the effects of using lower coverage. For now it did improve the consensus and we are reasonably comfortable with it. The experimental homopolymer fix helped a bit too.
Below are BLAST alignments so the identities are the local pct id.
BLAST of various assemblies
Canu output: Identities = 7078/7189 (98.5%), Gaps = 107/7189 (1.5%)
Nanopolished asm:
Identities = 7143/7199 (99.2%), Gaps = 48/7199 (0.7%)
Nanopolished asm – fixed homopolymers:
Identities = 7150/7199 (99.3%), Gaps = 40/7199 (0.6%)

99.3% is a bit disappointing, is this R9 data?

It is R9 yeah. I could share it with you if you'd like, along with the expected plasmid sequence (from Sanger sequencing once upon a time). We just threw it on a flow cell with other stuff to see if the sequence is still the same as was on record. I have separated out the fast5s that seem to be from the plasmid by taking those that had BLAST alignments to the plasmid sequence. Perhaps it could be filtered a little better (e.g. requiring long blast alignments) before trying to assemble and polish. I'd experiment a little more myself, but I was doing this for a friend in the lab who seems to be satisfied with the answer and need to get back to thesis writing. You're welcome to explore it more if you want, though I am sure you have much of your own data for that.

Sure, having the data would be helpful. No rush though because I'm pretty busy these days so might not get to it for awhile. In the meantime, could you paste a screenshot of the blast alignment so I can see where the errors are?

It is long enough where I'd have to take a few screen shots. I tried attaching the txt file instead. Let me know the best way to share the data.
pFRTmyc6xERE-nanopolish-fix.blast.txt


Not producing block because it isn't my turn, its eosio

please help:
167844ms thread-0   producer_plugin.cpp:167       plugin_startup       ] producer plugin:  plugin_startup() end
167844ms thread-0   http_plugin.cpp:156           plugin_startup       ] start processing http thread
167844ms thread-0   http_plugin.cpp:213           plugin_startup       ] start listening for http requests
167844ms thread-0   http_plugin.cpp:218           plugin_startup       ] http io service exit
167844ms thread-0   wallet_api_plugin.cpp:70      plugin_startup       ] starting wallet_api_plugin
167844ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/wallet/create
167844ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/wallet/get_public_keys
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/wallet/import_key
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/wallet/list_keys
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/wallet/list_wallets
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/wallet/lock
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/wallet/lock_all
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/wallet/open
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/wallet/set_timeout
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/wallet/sign_transaction
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/wallet/unlock
167845ms thread-0   chain_api_plugin.cpp:62       plugin_startup       ] starting chain_api_plugin
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/chain/abi_bin_to_json
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/chain/abi_json_to_bin
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/chain/get_account
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/chain/get_block
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/chain/get_code
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/chain/get_currency_balance
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/chain/get_currency_stats
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/chain/get_info
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/chain/get_required_keys
167845ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/chain/get_table_rows
167846ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/chain/push_block
167846ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/chain/push_transaction
167846ms thread-0   http_plugin.cpp:242           add_handler          ] add api url: /v1/chain/push_transactions
167846ms thread-0   net_plugin.cpp:2681           plugin_startup       ] starting listener, max clients is 25
168000ms thread-0   producer_plugin.cpp:227       block_production_loo ] Not producing block because it isn't my turn, its eosio
168500ms thread-0   producer_plugin.cpp:227       block_production_loo ] Not producing block because it isn't my turn, its eosio
169001ms thread-0   producer_plugin.cpp:227       block_production_loo ] Not producing block because it isn't my turn, its eosio
169500ms thread-0   producer_plugin.cpp:227       block_production_loo ] Not producing block because it isn't my turn, its eosio
170000ms thread-0   producer_plugin.cpp:227       block_production_loo ] Not producing block because it isn't my turn, its eosio
170500ms thread-0   producer_plugin.cpp:227       block_production_loo ] Not producing block because it isn't my turn, its eosio
171000ms thread-0   producer_plugin.cpp:227       block_production_loo ] Not producing block because it isn't my turn, its eosio
171500ms thread-0   producer_plugin.cpp:227       block_production_loo ] Not producing block because it isn't my turn, its eosio
172000ms thread-0   producer_plugin.cpp:227       block_production_loo ] Not producing block because it isn't my turn, its eosio
172500ms thread-0   producer_plugin.cpp:227       block_production_loo ] Not producing block because it isn't my turn, its eosio
173000ms thread-0   producer_plugin.cpp:227       block_production_loo ] Not producing block because it isn't my turn, its eosio

master is not in a state at the moment to run a private testnet. Please see the README.md

just add eosio as producer on config.ini

producer-name = eosio


update from upstream

chore(deps): update github/codeql-action action to v3.23.1
chore(deps): update actions/cache action to v4

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


Update loading screen to show all services status.

Need to update initial load screen to show list of services and their status.

I like the purple thing, but we should add::

a list of all the services being loaded
a progress bar for each service, and status colours
an idea of how long each service would take
potentially a write to disk benchmark the we run at the beginning that will scale the time for us
a series of tabs that provide documentation

this is done.


Is parse server multi threaded ? Does calling the cloud code still open a new thread?

Is parse server multi threaded ? How about when you call a cloud function?  If not , is it wise to using node cluster for aws instance ?

parse-server don't leverage multiple cores, nor comes with cluster. You should be able to run it without any problems. If you encounter issues please report your findings.


Fix Light/Dark theme switch

Clicking the Light/Dark theme button in the menu was failing with:
panicked at 'already borrowed: BorrowMutError', yewprint-doc/src/app.rs:58:33
RefCell::replace uses borrow_mut internally to replace the value which results in double borrowing attempt in this case.
Using RefCell::replace_with fixes the issue

Oops I totally overlooked this somehow.
Thanks for the fix!

So weird :thinking: ... I thought the arguments would be evaluated first. So this part should be evaluated first: !*x.borrow() then directly followed by x.replace(...). I'm not sure I understand why/how this is not the case somehow. It's not like x.replace() could "begin" to fire up and then only the argument be evaluated (that's impossible).
Since it's the mutable borrow that is failing I assume that the immutable borrow comes first but is not released before the mutable borrow occurs. It's surprising especially because I'm dereferincing the value explicitly with * so I thought at that point the immutable borrow would be released.
huh it works if I use an intermediary variable https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=05b63d886439a94b3e477b39e83460f4
Do you have an idea of what is going wrong?

I asked on Mastodon and Corax said this:

The call to borrow returns a temporary, and the RefCell regards itself as mutably borrowed until that temporary is dropped. And apparently Rust does not drop the temporary until the enveloping expression is fully evaluated.
There's probably a complicated reason for why temporary subexpressions aren't dropped as early as possible, but it escapes me too.

https://mastodon.social/@Corax42/109821809675264304

Yeah I don't really have a better explanation than what Corax provided.
Thanks for posting it here 👍

Someone told me I should use Cell instead of RefCell since it's just a bool... :woman_facepalming: Since Cell has no concept of borrowing it can't fail like that. The only requirement is that the type is either Copy or Default. It's much simpler in this case


Splitting up parser from runtime from web-preview

Thanks heaps for this library - it's been really useful in the tool we're working on (Jacquard - a yarn editor/debugger with (eventually) git integration to enable easier multi-writer collaboration on projects)
There's a few bugs with the parser in Bondage, plus @desplesda, @mcjones me and some others have  been thinking about how the yarn syntax should work in various cases (these discussions have been on the yarnspinner channel in the Narrative Game Dev slack). The other thing that @mcjones and @desplesda have done in the main Yarnspinner branch is they are in the process of changing over to an ANTLR-based parsing solution, and the Secret Lab peeps have said that's how they think yarn should be parsed in the future.
The other thing is that Yarnspinner is converting to a different internal format (a bytecode representation) - but they're doing this at runtime. I floated the idea in the slack and @desplesda agreed that ultimatley the run-times would use a bytecode format, rather than the yarn text - which should make for simpler run-times.
Our tool is being primarily written in javascript (as an electron app is an easy way to get cross-platform support happening, plus we can re-use a lot of it if we do a web version) so i've been writing a bytecode output format there, and I've been using your parser and lexer as the basis for that.
I've reached the point where I'd like to make a few changes and I'm wondering if it wouldn't be better to split some of this stuff into seperate projects:
a) something that parses .yarn.txt and .yarn.json files into a defined represenatation and provides debugging information for both parser failure and the later stages (Bondage.js currently does most of this for JS, but will need some updates)
b) something that translates representation above into the runtime bytecode format (i've realised that this format can also easily represent twine/twee syntax as well)
c) something that runs the bytecode in a web-browser and can also provide a debugger (this is a super-useful tool for writers because they don't need to fire up unity or whatever to debug their yarn logic)
We're also trying to build a consensus / get feedback on how the yarn syntax itself should evolve and we'd love your input if you have any time. Again thanks for writing this - it has been super useful!

Hello! This sounds awesome, glad this project is being of some use!
I'd actually been thinking a while ago about doing a splitup of the project that is similar to what you described there, which I was putting off until there was a usecase for it and here we are!
It's 6:30 in the morning and I'm about to catch a plane to gdc, so I won't be able to put any more thought into this until next week unfortunately. if you're going maybe we could talk there? if not ill get back to you more specifically afterwards

I'm not, but @desplesda and Robert Yang both are and were thinking of having a mini meetup - do you have a way of contacting them? (I've sent an invite to the narrative games slack, but they are both on the twitters as well)


Visual Code Freezes always now since last update

VSCode Version: 1.5.1
OS Version:  Microsoft Windows 10 Enterprise (10.0.14393)

Steps to Reproduce:

Open VSCode from a folder with my README.md files
Open an .md file
Open .md Preview
Start typing text
App freezes

I am having the same issue.
OS:
Major  Minor  Build  Revision
-----  -----  -----  --------
10     0      10586  0

Visual Studio Code Version - 1.5.2.
I've removed all extensions and reinstall VSCode.

Assuming this is related to markdown and webviews assigning to @jrieken and @kieferrm.

Can you guys check which process is running high? Please check top/htop/process_explorer and include the full command line string that was used the launch the bad processes. Thanks

I'm having the same issue under Windows 7 64 bit with v1.5.2 and previously with v1.3.1. Same process to replicate as everyone else. I had Windows Task Manager generate a process dump, but it's 350 MB so not so easy to share. Let me know if there's a better way to get information on this. When looking at the processes tab in Task Manager, one of the Code.exe *32 processes was using 250 MB of memory. I didn't see a way to get more detailed information on that specific Code.exe process.

I encountered the same problem with 1.5.2 on Win7 x64, none of the processes consume CPU, I got it to unfreeze reproducable when killing the eslint process (the last one in the screenshot).
The ESLint Plugin has Version 1.0.6

@prusello you can use the process explorer from here https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx. Select the process with the high CPU / memory consumption and run Properties from the context menu. This should give you access to the full command line used to start the process. Please provide the command line here.
Regarding eslint: I can think of no why how the eslint process spawned from the extension host could freeze the renderer without any CPU load.

I've been trying to get VSCode to freeze this morning, but no such luck. I've been typing for at least a half hour, one minor slow up but VSCode recovered in a few seconds.
In between my original post and this one, I did update the donjayamanne.python-0.3.24 extension and ms-vscode.cpptools-0.9.1 extension. I don't know why either of those would affect Markdown, but that's the only change to VSCode. A bunch of system updates happened yesterday (this is a work computer, so I don't have a list of them) as well, but I'm using the zipped VSCode install so I can update without admin rights so I'm not sure how those would affect VSCode.
If I do encounter a freeze, I'll post the Process Explorer command line here. Thanks for the help and I guess it's good I can't reproduce the freeze now, even though I'm not sure what fixed it...

@prusello good to heat thatr the freeze went away. I will keep the issue open for now in case you see it again.

I have VS Code 1.5.3 and editing markdown hangs routinely. Is there a dump file I can share?

@kieferrm any hint how to track this down. The original reports and @NearlyUnique complain about markdown.

I can use ProcDump to generate a dump file but not sure if that'll help. There is also 7 Code.exe processes and 1 CodeHelper.exe processor, I'm not sure which part hung. There is also a cmd.exe, which I assume is the terminal window.
Process Explorer says the main thread that is still running has a start address of code.exe!?setID@Transliterator@icu_54@@IAEXABVUnicodeString@2@7@@Z+0x2c9de
ProDump - https://technet.microsoft.com/en-gb/sysinternals/dd996900.aspx

This has not happened for some time now, though I cannot determine what caused it to stop.
I am now upgraded to1.6.1. I'll report it if it happens again

@bpasero also 1.5.1 could this be caused by the pipe problem as well ?
@NearlyUnique is the md file you open large ?

@dbaeumer yes quite possible. as far as I know the freeze is there since node.js 4.x

@dbaeumer The files are not large and since my last post I have been editing markdown and go with no ill effects. If it happens again I will look at trying to setup the vscode development/debug environment so I can supply more info.

The information in this issue is about pretty old versions. We haven't seen similar issues for a while. I'll close the issue. Please file a new issue when you see issues in the most recent version of VS Code.
Thanks!


Build instructions?

I'd like to use this but I'm entirely unfamiliar with building .NET code. I've tried loading it up in Visual Studio with the .net core 2.2 runtime installed and it builds/publishes dll files, but never a .exe.
I've tried building the .sln file and each individual project within and just can't figure out how to get an .exe out of this code.
I've also tried dotnet build and dotnet publish in the repo root and in each project and get the same results (only dlls, no executable)
Thank you!

I definitely plan to write build instructions when I have some free time.
I have not yet configured a self-contained exe profile so you have 2 options if you want to run this application:

execute dotnet run command in PatreonDownloader.App folder
execute dotnet build command in PatreonDownloader.App and then go to PatreonDownloader.App\bin\Debug\netcoreapp2.2 and execute dotnet PatreonDownloader.App.dll command

That works great, thanks so much! Fantastic work on this

Thanks! Glad you find it useful. I'll leave this issue open until I make a proper wiki page with build instructions.

Added build instructions wiki page as well as publishing profiles used to build self-contained executables.


Failure to reach AWS address crashes application

Using VRCFT Version <IP_ADDRESS> on Windows 10, if this address

rjlk4u22t36tvqz3bvbkwv675a0wbous.lambda-url.us-east-1.on.aws:443

resolves to "::" or otherwise fails to resolve, the application crashes, this happens on a fresh install with no modules, etc.
The 'latest.log' shows the following output:

[VRCFaceTracking.Services.ActivationService] Information: VRCFT Version <IP_ADDRESS> initializing...
[VRCFaceTracking.Services.ActivationService] Information: Initializing OSC...
[VRCFaceTracking.Core.OSC.OscQueryService] Debug: OSC Service Initializing
[VRCFaceTracking.Core.OSC.OscQueryService] Debug: OSC Service Initialized with result (False, False)
[VRCFaceTracking.Services.ActivationService] Information: Initializing main service...
[VRCFaceTracking.Core.Params.Data.UnifiedTrackingMutator] Debug: Reading configuration...
[VRCFaceTracking.Core.MainStandalone] Debug: Starting OSC update loop...
[VRCFaceTracking.Core.Params.Data.UnifiedTrackingMutator] Debug: Configuration loaded.
[VRCFaceTracking.Services.ActivationService] Debug: Checking for deletion requests for installed modules...
[VRCFaceTracking.Services.ActivationService] Information: Checking for updates for installed modules...
[App] Error: Unhandled exception
[App] Critical: Stacktrace:    at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(QueueItem queueItem)
at System.Threading.Tasks.TaskCompletionSourceWithCancellation1.WaitWithCancellationAsync(CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.HttpConnectionWaiter1.WaitForConnectionAsync(Boolean async, CancellationToken requestCancellationToken)
at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)
at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
at System.Net.Http.HttpClient.g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)
at VRCFaceTracking.Core.Services.ModuleDataService.AllModules()
at VRCFaceTracking.Core.Services.ModuleDataService.GetRemoteModules()
at VRCFaceTracking.Services.ActivationService.StartupAsync()
at VRCFaceTracking.Services.ActivationService.ActivateAsync(Object activationArgs)
at VRCFaceTracking.App.OnLaunched(LaunchActivatedEventArgs args)
at System.Threading.Tasks.Task.<>c.b__128_0(Object state)
at Microsoft.UI.Dispatching.DispatcherQueueSynchronizationContext.<>c__DisplayClass2_0.b__0()
[App] Critical: Inner exception: System.Net.Sockets.SocketException (11004): The requested name is valid, but no data of the requested type was found.
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Sockets.Socket.g__WaitForConnectWithCancellation|281_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
[App] Critical: Message: The requested name is valid, but no data of the requested type was found. (rjlk4u22t36tvqz3bvbkwv675a0wbous.lambda-url.us-east-1.on.aws:443)

Obviously if the application cannot reach what looks like an auto-update endpoint, it shouldn't completely crash, this seems to be undesirable and unintended behavior.
I found this due to the address matching a filter in the AdGuard DNS and EasyPrivacy DNS lists.

I've also encountered this issue when using AdGuard DNS and the EasyPrivacy DNS List. In my case the traffic was rewritten to localhost by AdGuard.
[App] Error: Unhandled exception [App] Critical: Stacktrace:    at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.ConnectAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.CreateHttp11ConnectionAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.AddHttp11ConnectionAsync(QueueItem queueItem)    at System.Threading.Tasks.TaskCompletionSourceWithCancellation1.WaitWithCancellationAsync(CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.HttpConnectionWaiter1.WaitForConnectionAsync(Boolean async, CancellationToken requestCancellationToken)    at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage request, Boolean async, Boolean doRequestAuth, CancellationToken cancellationToken)    at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)    at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationTokenSource cts, Boolean disposeCts, CancellationTokenSource pendingRequestsCts, CancellationToken originalCancellationToken)    at VRCFaceTracking.Core.Services.ModuleDataService.AllModules()    at VRCFaceTracking.Core.Services.ModuleDataService.GetRemoteModules()    at VRCFaceTracking.Services.ActivationService.StartupAsync()    at VRCFaceTracking.Services.ActivationService.ActivateAsync(Object activationArgs)    at VRCFaceTracking.App.OnLaunched(LaunchActivatedEventArgs args)    at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_0(Object state)    at Microsoft.UI.Dispatching.DispatcherQueueSynchronizationContext.<>c__DisplayClass2_0.<Post>b__0() [App] Critical: Inner exception: System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it.    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)    at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)    at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|281_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)    at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken) [App] Critical: Message: No connection could be made because the target machine actively refused it. (rjlk4u22t36tvqz3bvbkwv675a0wbous.lambda-url.us-east-1.on.aws:443)


Store CYOA choice in localstorage

replaces https://github.com/galaxyproject/training-material/pull/3435
This should survive reloads, as it uses the same mechanism as themes (which do).

@lldelisle we can put it in the left menu, but I cannot seem to prevent it from scrolling, due to how the CSS is done, so unfortunately I cannot address this issue currently.

@lldelisle we can put it in the left menu, but I cannot seem to prevent it from scrolling, due to how the CSS is done, so unfortunately I cannot address this issue currently.

Thanks for trying.


#1789 - Dependency settings not passed to webserver

Checklist

[x] manage.py test passes
[x] tests are included

Affected app(s)

scheduler

Description of change
Fix for status bugs in webserver.

need to finish testing these changes in dev

Docs updated; issue created 👍


Merge Entities form - location

At the moment the Merge Entities form in the Edit Entity page appears below the relations table.
Could we have the Merge form along with the entity details on the left panel on the edit view - considering that a successful merge will update the entity fields rather than create relations?
Merge is currently a link in the Actions menu but broken in release 28. Instead of fixing #1278 we could remove the link from this menu and leave the Merge field in a more prominent position.

considering that a successful merge will update the entity fields rather than create relations?

It should do both (and did for the old relations). But this has to be implemented, see  #1251

following https://github.com/acdh-oeaw/apis-core-rdf/pull/1283
we remove the not needed merge with form from the entities edit view


Sun Layout

Feature Description
After ordering genes based on genetic coordinate, layout genes that occur at the same locus outwards, sort of looking like the ray from the sun. This will add an additional dimension that we can distinguish genes on.

Tasks

[x] Position genes outwards on a ray from the center of the circle
[x] Order genes so that highest degree nodes are near the center

Notes
Is it possible to play around with labels of both genes and chromosomes so that they are visible? Maybe so that they are positioned near the center of the circle?

Done in the most recent commit, looks better, but still needs other features for this to be especially useful.


Kinetic Laws

Moreover, it should parse for lower and upper bounds to support legacy models (even though it is deprecated).

Implemented in 37eba8f.


docs: How to list datasets in a workspace

Description
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Closes #3403
Type of change
(Remember to title the PR according to the type of change)

[ ] Documentation update

How Has This Been Tested
(Please describe the tests that you ran to verify your changes.)

[x] sphinx-autobuild (read Developer Documentation for more details)

Checklist

[x] I added relevant documentation
[ ] I followed the style guidelines of this project
[ ] I did a self-review of my code
[ ] I made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I filled out the contributor form (see text above)
[ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

Hi, perhaps we would be better of with a separate database_management page? what do you think @nataliaElv

Or at least rename the section to workspace and dataset management or something?

Hi, perhaps we would be better of with a separate database_management page? what do you think @nataliaElv

You mean a datasets management page? Yes, it would give this content more visibility, but I guess that page could have a bit more content than this. We need to be careful about how that could impact other content around managing datasets already in the docs, like creating a dataset.


[Logo grid]: @sm should be two columns for logos

Engineering info:

Innovation Team engineer:
Innovation Team JIRA Ticket: https://jsw.ibm.com/browse/HC-2505
DPO consulting engineer: N/A

Description
Discovered in #8973.
The Web Components version of Logo grid is currently displaying a single column of logos and should be updated to match the newly created React wrapper version. At the @sm breakpoint, the logos should be in two columns to match the spec:
Current WC version

Specs

Component(s) impacted
Logo grid
Browser
Chrome
Carbon for IBM.com version
v1.19.0
Severity
Severity 3 = The problem is visible or noticeable to users but does not impede the usability or functionality. Affects minor functionality, has a workaround.
Application/website
C4IBM.com
Package
@carbon/ibmdotcom-web-components
CodeSandbox example
https://codesandbox.io/s/github/carbon-design-system/carbon-for-ibm-dotcom/tree/main/packages/web-components/examples/codesandbox/components/logo-grid
Steps to reproduce the issue (if applicable)
No response
Release date (if applicable)
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate issues

@emyarod FYI, this issue is assigned to our Innovation team group. I'm going to leave you as a consultant for this issue. Let me know if you have any questions.


Improve the inference of the header name when using function as value

Coverage remained the same at 100.0% when pulling 51dfae9dae0ba9dfa8e465afe61925cb796c39eb on juanjoDiaz:improve_default_header_for_getter into ffda9afe5761697bb9cebe596624ed88f00c0b31 on zemirco:master.

Coverage remained the same at 100.0% when pulling 51dfae9dae0ba9dfa8e465afe61925cb796c39eb on juanjoDiaz:improve_default_header_for_getter into ffda9afe5761697bb9cebe596624ed88f00c0b31 on zemirco:master.

Coverage remained the same at 100.0% when pulling 51dfae9dae0ba9dfa8e465afe61925cb796c39eb on juanjoDiaz:improve_default_header_for_getter into ffda9afe5761697bb9cebe596624ed88f00c0b31 on zemirco:master.


Line dash property also affects following SVG image

Description
The following code behaves different than expected
#box(
    height: 20pt,
    image("calendar.svg")
)

#line(length: 100%, stroke: (paint:rgb("#cbd5e1"), dash: "dashed"))

#box(
    height: 20pt,
    image("calendar.svg")
)

I would expect the SVG to be rendered the same twice, but that is not the case

Reproduction URL
https://github.com/Hofer-Julian/typst_reproducer
Operating system
Linux
Typst version

[X] I am using the latest version of Typst

that's interesting. i will take a look

I just comfirmed this only happens in pdf export. SVG and PNG export are OK. @LaurenzV can you take a look when you have time?

I'll try, but might be a while until I get to it. But I'm 90% sure that the problem is that Typst sets the line stroke as "dashed" in the PDF stream and it's not resetted in svg2pdf (since by default it assumes that the line stroke is solid), so that's probably why this is happening. But I'll have a look once I find the time.

Okay it was just a one-line fix. Will mark this issue resolved once it's been upstreamed.

@LaurenzV can this be closed?

Yup, just double checked!


relative argument for place function

Description
It would accept a selector (such as page) and the content argument would be placed relative to the closest parent matching that selector.
For example, place(end, relative: page)[Note: this is a note] will place a note at the end of the page on the same height as the content before and after the place call
Use Case
E.g. margin notes in equations etc., generally more flexible absolute placement
Also see: https://github.com/typst/typst/issues/2544#issuecomment-1862499002

I think it might be more reasonable to use the same system as gradients where it can be relative to the container or the parent container, but any higher gets really complicated with the current system. Especially arbitrary selectors imo

Possibly closed by #5017, but still arbitrary selectors or at least absolute (page-relative) placements (and correspondingly gradients) feel like they are missing


Create common_prefix.java

Write a function to find the longest common prefix string amongst an array of strings.If there is no common prefix, return an empty string "".

@Dinki-Yaduwanshi kindly create an issue for the same and get it assigned then use the pr template provided in readme.md

Okay, I have created the issue as you told me and will resubmit the PR in the correct format. Thank you!

use proper pr template given in readme file this

updates ? @Dinki-Yaduwanshi


Refactor apis in MapValue to BMap

Description:
Following apis are in MapValue which is actually internal class.

long getDefaultableIntValue(BString key);
Object merge(MapValue v2, boolean checkMergeability);
TypedescValue getTypedesc();
void populateInitialValue(K key, V value);

These are used by stdlibs. We need to move these to BMap which is the public api interface. Then need to implement for the table as well.

Releated PR to http module https://github.com/ballerina-platform/module-ballerina-http/pull/38


Material labels do not show an asterisk when required as the bootstrap elements do

I'm submitting a ...  (check one with "x")
[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request

Current behavior
When using the material design, form elements that are required do not have an asterisk.
Expected behavior
Elements that are required should show an asterisk as they do with the bootstrap module.
Minimal reproduction of the problem with instructions
https://angular-dece1p.stackblitz.io
What is the motivation / use case for changing the behavior?
Fixing
Please tell us about your environment:
Windows 10
WLS Ubuntu
Visual Studio Code

Angular version: 5.0.0

Ngx-formly version: 2.0.0-rc.3

Browser:
All

Language:
All

let me know if you want to work on this,  change should be made at: form-field
similar to bootstrap label

I've already fixed it and I want to put a PR up for it, but I'm running into an issue trying to test formly as I work on it with material.
First off, I can't npm link the library to an angular project to test it as I work.
Second, I wanted to update the documentation (examples) to add material ui examples. If you take any of the examples, and swap out the bootstrap module for the material one, you get an error:
'mat-label' is not a known element:
I've tried including the material modules that are required in the example's module file, but nothing seems to work. I'm still not 100% up to speed with Angular's new module system so maybe you could shed some light on this.
Once I can figure that these out, I can help add material examples to the documentation and it would make working on any features in regards to material easier.

First off, I can't npm link the library to an angular project to test it as I work.

you should go into dist folder and link the package you wish to include.

Second, I wanted to update the documentation (examples) to add material ui examples. If you take any of the examples, and swap out the bootstrap module for the material one, you get an error: 'mat-label' is not a known element:

yep it's a known issue, that's why I didn't include it in doc example, material require angular 5.0, if you want to check it just update all @angular package into v5 and it should work!


Classes for protein/transcript variant effects

changed mutate to use transcript_effects objects instead of single ProteinMutation object

Merging after a code walkthrough with @ihodes and @tavinathanson.


Was removeLuaScript removed in 0.7.1h?

What is your question?
When I tried to use removeLuaScript, the game would just crash. It works on 0.6.3, but hot here...

i just used it too and the game crashes