RIOXX v3 OAI profile support

Description
This PR  implements a RIOXX v3 compliant OAI profile. RIOXX stands for Research Outputs Metadata Schema and the latest version of the specification is available at https://www.rioxx.net/profiles/v3-0-final/
This PR also adds support for exposing in OAI resource policies for bitstreams to address the issues / use cases described in #9075 and #9050 - see references below.
References
Add references/links to any related issues or PRs. These may include:

Fixes #9075
Fixes #9050

Instructions for Reviewers
This PR implements a new RIOXX OAI context available at /oai/rioxx.
The solution adds a method in the XOAI ItemUtils.java file, that is called when the item is processed. It adds the extra XML elements to the XOAI bitstream, that expose the defined resource policies related to access level (group Anonymous + action READ).
To test all RIOXX elements are populated (in particular those that rely on related entities), follow similar instructions to those for OpenAire 4 (https://wiki.lyrasis.org/display/DSDOC7x/OpenAIRE4+Guidelines+Compliancy):

Deploy PR
Enable entities (load both relationships.xml and rioxx3-relationships.xml)
Replace virtual-metadata.xml with contents of virtual-metadata.xml.rioxx3
Restart Tomcat container
run the OAI import from the command line with the cleaning cache parameter to reload all data to OAI

List of changes in this PR:

ItemUtils.java: expose resource policy information at the bitstream level
Addition of rioxx.xsl (metadataFormats and associated rioxx.xsl transformer)
Configuration of context in xoai.xml
Addition of filter ItemsWithBitstreamFilter to support context filtering to only include items with bitstreams associated with them
Addition of item.hasbitstream field to OAI solr schema (used in the RIOXX OAI context to determine whether an item has files in ORIGINAL Bundle)
Addition of  virtual-metadata.xml.rioxx3 and rioxx3-relationships.xml to model required relationships to expose relevant funding and project entities information

Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[X] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
[X] My PR passes Checkstyle validation based on the Code Style Guide.
[X] My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
[X] My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
[X] If my PR fixes an issue ticket, I've linked them together.

The overhead added to OAI was mentioned as a side effect of processing and including resource policies in the OAI metadata. I have run a full OAI reindex using this PR on a DSpace 7.6.1 instance for a large repository - 325,000 items:

First run allocating 4GB of mem to the process and it did not complete. It errored close to the end (at around 310,000 items) with a java heap error
Second run with 8GB mem (it probably does not need that much) and it has finished successfully in ~3 hours, which is a good time compared to previous runs in our repository

@amgciadev : I meant to add that after merging this, we'll need to create some clear documentation for Rioxx support in DSDOC8x similar to the documentation for OpenAIRE v4: https://wiki.lyrasis.org/display/DSDOC8x/OpenAIRE4+Guidelines+Compliancy
Specifically, I think we'll need to make it clear when sites should use Rioxx versus OpenAIRE v4.  It sounds like they are mostly "compatible" but you may only be able to support one or the other?  (Or maybe I'm wrong and there's a way to support both?)  In any case we need to add / enhance documentation here.

@tdonohue  thanks so much for the review and the +1. You've made very useful comments re the documentation, absolutely agree re adding the page for Rioxx similar to the one for Openaire, and I am happy to work on that one too.
You've made a really important point re compatibility of Openaire and Rioxx: they should be completely compatible and in fact it is highly important that you are able to have them both enabled at the same time. @paulo-graca hopefully can help confirming this one / adding his thought given his knowledge of the Openaire work.
I'll work on the minor comments asap. Thanks a lot!

@amgciadev : Thanks for clarifying that it should be possible to support both Rioxx v3 and OpenAIRE v4.
One challenge that I see to that in DSpace is that we appear to have 3 different virtual-metadata.xml files:

Default virtual-metadata.xml for Configurable Entities
virtual-metadata.xml.openaire4 for OpenAIRE v4 support
virtual-metadata.xml.rioxx3 for Rioxx v3 support (added by this PR)

Which file should be used if you want to support both Rioxx & OpenAIRE?  Currently, it's confusing to me how to achieve that.  But, maybe you or @paulo-graca would have suggestions on how to do this.  (Do we need a combined virtual-metadata.xml for both Rioxx and OpenAIRE?)

@tdonohue let me review virtual-metadata.xml.rioxx3 as what I tried to do with this one was to actually combine the default entities virtual-metadata file with the additions needed for rioxx re project fundind and awards (which are very close to those specified in openaire).
It may be that we don't need the added virtual-metadata.xml.rioxx3. Likewise, we don't need the separate entities/rioxx2-relationships.xml as the contents  are the same as those in openaire-relationships.xml (I only added it to add the relevant comments for the metadata fields that they are used for as those are different between the two profiles). It may likely be that we could re-use relationships and virtual metadata for openaire and what we need to do is be very clear in the docs?

@amgciadev : That all sounds reasonable. If we find that Rioxx support just requires using the OpenAIRE configs, that's fine with me. As you said, we can just be clear in the docs.  We could even say that Rioxx support depends on first enabling OpenAIRE support, if we find that is the best approach.
In any case, I'll wait to merge this until we have a final direction.  Overall though, this works great & looks good.  I can give it a final test again once it is ready.

@tdonohue  I have performed more tests and wanted to raise the following:

Removed virtual-metadata.xml.rioxx3 as the relationships to populate related entities metadata for openaire4 can be reused for Rioxx
Kept rioxx3-relationships.xml eventhough the relationships are the same as for openaire, the file has useful docs as to what rioxx fields rely on what relationships (happy to remove if you feel that documenting this in the wiki suffices)
I think I have encountered a bug in virtual-metadata.xml.openaire which was using the incorrect direction of the relationship in publicationProject_projectFunderId_related

Without the change in 3. I have confirmed that oaire:funderIdentifier and oaire.funderName metadata from related entities was not being populated. This was also affecting the equivalent rioxxterms:grant elements which also includes a reference to the funder name and funder id. I didn't think it was a bug originally, which is why I ended up having a different virtual-metadata.xml file for Rioxx but I now believe is a bug.
With my changes in this last commit I can confirm that both openaire and rioxx metadata for funder names and funder identifiers are exposed in the following scenarios

A publication is linked with a project
That project is linked with a funder (orgUnit entity)
The funder has org name and identifier metadata

@amgciadev : Thanks for clarifying that it should be possible to support both Rioxx v3 and OpenAIRE v4.
One challenge that I see to that in DSpace is that we appear to have 3 different virtual-metadata.xml files:

Default virtual-metadata.xml for Configurable Entities
virtual-metadata.xml.openaire4 for OpenAIRE v4 support
virtual-metadata.xml.rioxx3 for Rioxx v3 support (added by this PR)

Which file should be used if you want to support both Rioxx & OpenAIRE?
Currently, it's confusing to me how to achieve that. But, maybe you or @paulo-graca would have suggestions on how to do this. (Do we need a combined virtual-metadata.xml for both Rioxx and OpenAIRE?)

Sorry for my late feedback on this. I'm being swamped with local stuff.
We are currently using OpenAIRE's file configuration. To use it, we rename the existing file before the build process. However, I would prefer not to do it and instead I would prefer to rely on a configuration setting, possibly in my local.cfg, to use that speicific virtual metadata. What @amgciadev has done is the only way to have support for  different virtual metadata on DSpace. In this case, we are incorporating RIOXX schema into DSpace, which requires some addional fields that aren't present in default virtual metadata. Additionally, since every .xml file in the /spring/api folder is interpreted, a non-xml file must be present.

My comment has on hold for a while and I just saw recent commits. I'm glad that @amgciadev could use existing virtual metadata.

@paulo-graca thanks for the comments. Since you implemented the Openaire v4 integration, could you have a look at my changes in the last commit (in virtual-metadata.xml.openaire4) as per the below:

I think I have encountered a bug in virtual-metadata.xml.openaire4 which was using the incorrect direction of the relationship in publicationProject_projectFunderId_related

Without the change in 3. I have confirmed that oaire:funderIdentifier and oaire.funderName metadata from related entities was not being populated. This was also affecting the equivalent rioxxterms:grant elements which also includes a reference to the funder name and funder id. I didn't think it was a bug originally, which is why I ended up having a different virtual-metadata.xml file for Rioxx but I now believe is a bug.
With my changes in this last commit I can confirm that both openaire and rioxx metadata for funder names and funder identifiers are exposed in the following scenarios

A publication is linked with a project
That project is linked with a funder (orgUnit entity)
The funder has org name and identifier metadata

If you could confirm that this is a bug, that would be great. Thanks!

Merging as this is now at +2.  Thanks again @amgciadev !
This now needs documentation to be added to the DSpace 8 documentation space similar to the OpenAIRE v4 docs in that space: https://wiki.lyrasis.org/display/DSDOC8x/OpenAIRE4+Guidelines+Compliancy   Once those docs are added, the needs documentation label can be removed from this PR.

@tdonohue can you give me permissions to add/copy/edit pages in confluence? I tried copied the openaire page but got a permissions error while logged in.

@amgciadev : I've just updated your wiki permissions to have full permissions to the DSpace documentation spaces.  You should now be able to edit/add pages.

Thanks @amgciadev ! Docs look good to me.  I'll take off the "needs documentation" label.


Ability to select what inline styles to retain/strip in paste

Right now, you can choose whether your editor accepts rich text or not in paste using stripPastedStyles. It's not always all-or-nothing, though: in case your editor only supports a subset of the supported styles, pasting can insert things the user can't remove anymore. For example, the Facebook Notes editor doesn't support underline or strikethrough, and yet you can paste underlined/striked text, and you can't get rid of that style anymore without deleting the entire piece of text.
It would be handy to have a prop on the editor component to specify which inline styles should be retained on paste. (opt-in)

You're right, we could handle this better. One idea would be to replace stripPastedStyles with a configuration object, and pass that through to the paste processor:
// Flow type
type DraftPasteSupport = {
  inlineStyles: List<string>,
  blockTypes: List<string>,
  links: boolean,
};

// in DraftEditorProps
pasteSupport: DraftPasteSupport,

// defaultProps
pasteSupport: {
  inlineStyles: List('BOLD', 'ITALIC', 'UNDERLINE', ...),
  blockTypes: List('header-one', ...),
  links: true,
}

Then the equivalent of stripPastedStyles={true} would be:
const PLAINTEXT_PASTE = {
  inlineStyles: List(),
  blockTypes: List(),
  links: false,
};

What do you think?
cc @CLowbrow

Sounds great to me! 👌🏻
I'm assuming this will play nice with custom blocks pasting, if it should ever be implemented #125?

Yeah, internal pastes should never be a problem here, since we just use the extracted fragment and this will contain any copied custom styles.

I like this. Would it make sense to pass blocks an inlines as a map of tag -> Draft editor style?
If we are making this customizable we might as well go all the way.

Interesting, instead of doing the mapping ourselves within the paste processor?
That could work for blocks, but for inlines, what happens to these: https://github.com/facebook/draft-js/blob/master/src/model/paste/DraftPasteProcessor.js#L148?

That's a good point. Those styles are more baked in to the editor and aren't generated based on tag name. Would probably still be a list.

For pasting, I myself am happy with the configuration object mentioned above.
However, per the change in #174 : I'm interested in having the ability to customize what happens when the html2block convertor encounters tags it doesn't know (img, figure); I was thinking of the ability to provide a function that takes an HTMLElement and returns a block (with a block entity). As I said, I don't really need this for paste, I wanted this more in a use case to one-off populate the editor from another (HTML-based) format, but I guess such a function would be useful for customizing paste support as well (e.g. to support image paste). This would only be block-level though, so maybe this is orthogonal to the original request.

That makes sense, but we are going to hit some weird edge cases.
Paste handler takes a tree structure and reduces it to a flat array of blocks, so we throw away nested block elements (a list inside a blockquote will get ignored as we don't have a way of storing that). The simplest thing to do would be to only call that function on block elements we care about that aren't inside other block elements we care about. I'm worried that will be confusing and not useful enough.
My other concern is that we convert to blocks at the very end of going through the DOM tree. Until we are done walking the tree, the document state is just a long string with some associated arrays for block types/entities.
I think I'm going to work on making the list of tags we care about customizable first, and will save passing in custom handlers later.

@CLowbrow @hellendag Has there been any progress on this? I just now ran into a similar issue where it is desirable for internal text to just be copy/pasted as is, but to prevent certain or all styles from external pastes.

Would love to see this implemented. It has a lot of potential use cases.

I have implemented @hellendag's suggestion in #1057. Review is welcomed

Great to see this is being worked on.
Just to check would you envisage this functionality eventually allowing:

Calling back interested observers when styles are stripped. A single call back post-paste might be ideal, allowing us to let the user know what has been stripped.
Clients overriding the stripping behavior for each type of element, for example in some cases you might want to replace an image with custom text where as in others you'd want to completely remove it.

Is it planned to release this feature?

same concern. The idea with
// in DraftEditorProps
pasteSupport: DraftPasteSupport,

is very valuable. Is it already done?

Here is stand-alone version of mine:

const removeInlineStyles = (
    editorState: EditorState,
    retainInlineStyles: string[] = []
) => {
    let blocks = editorState
        .getCurrentContent()
        .getBlocksAsArray()
        .map(singleBlock => {
            return singleBlock.set(
                "characterList",
                singleBlock
                    .getCharacterList()
                    .map(charMetaData => {
                        if (charMetaData) {
                            let entity = charMetaData.getEntity();
                            let style = charMetaData.getStyle();
                            return CharacterMetadata.create({
                                entity: entity,
                                style: style.intersect(retainInlineStyles)
                            });
                        }
                        return charMetaData;
                    })
                    .filter(x => !!x)
            );
        }) as ContentBlock[];
    return EditorState.createWithContent(
        ContentState.createFromBlockArray(blocks)
    );
};

// Usage on the editor onChange, e.g. retain only bold styling:
    onChange = (editorState: EditorState) => {
        if (editorState.getLastChangeType() == "insert-fragment") {
            editorState = removeInlineStyles(editorState, ["BOLD"]); // This retains only BOLD styling
        }
        this.setState({
            editorState
        });
    };


Video Flickering issue with usb 3.0 video capture card

I am having video flickering issue in new device(usb 2.0 video capture card) which is connected alternative for frame grabber(epiphan av.io.4k frame grabber). Also, we observed that the issue appears in linux(for virtual display) and with windows(streaming with webcam application) working fine.
Also we are using opencv2/opencv.hpp and cpp-mjpeg-streamer in linux for streaming.

Hi, sorry for the late reply.
I don't really understand the streaming system that you have. Maybe you can explain a bit more about your streaming system so that I can understand what parts of this library that contributed to your problem.
Also, this library only responsible to stream image via HTTP and didn't include frame retrieval from device or other source.
Thank you


KAFKA-9663: Doc some null returns in KafkaStreams

Documents the possibility of null return value in KafkaStreams.getMetadataForKey(), and KafkaStreams.queryMetadataForKey().
This fixes KAFKA-9663.

@guozhangwang, @mjsax please could you review?

Closed in error. Now fixed @mjsax.

Thanks for the PR @tombentley! Merged to trunk.


T001: Pandas deprecation warnings

Talktorial 1 uses the pandas applymap-function which has been deprecated in pandas version 2.1. We either need to fix pandas to <2.1 in devtools/test_env.yml or update the code accordingly.
The deprecation warning causes a test failure.

This issue has disappeared more recently. See here.


[Feature Request] UI enhancement for airgap function

For v0.6.0, the airgap package management from UI don't have the download progress or logs. Following features might need to be considered:

[x] Add Downloading state for package
~Add progress bar when package is in Downloading state~
[x] Shows where the airgap package is downloaded(aliyunoss or github)
[x] Maybe show download progress logs when package is in Downloading state

Use download logs to show the progress instead of progress bar. More friendly and easy to implement.

For Shows where the airgap package is downloaded(aliyunoss or github)
Add a new dropdown button next to view install script, displaying <source> Source Text.

And select AliyunOSS or Github from dropdown.
Please use role-secondary class for the button.

Display <source> Source Text.

If the airgap package is downloading too slowly or the package download failed with the specified source(e.g. using github source in a bad network environment). Is it better to add a retry button on the UI page to retry download after switching Source?

If the airgap package is downloading too slowly or the package download failed with the specified source(e.g. using github source in a bad network environment). Is it better to add a retry button on the UI page to retry download after switching Source?

If so, I think both Cancel and Retry are also needed. For now, It will retry and re-download it after editing the package without any changes.

Sure. It also makes sense. I think it's better to add information about this to the doc for users who want to retry and re-download the package after switching the source or some other case.

@ly5156 The #589 requires UI enhancement.

Add actions(Cancel and Download) for airgap package.
Popup logs when the package is created and changed to Downloading state

[ ] The package will re-download after Edit package. UI need to show download logs also after edit package.
[ ] UI needs to Disconnect the download log when user canceled the downloading process.

Edit the package with Active status, and save without modification. The package changed to OutOfSync status, UI shows popup logs, and the log shows the package xxxxx is ready, skip downloading resources. The log API won't Disconnect and the package won't change to Active status.


Modified Hbase version to 1.0.3 to fix docker:build error.

There  is no Hbase 1.0.2 from apache.mirrors.pair.com/hbase.

ping @koo-taejin


[Microsoft Edge] Support for Edge Canary

Extension
https://www.raycast.com/KartikKumarSahoo/microsoft-edge
Description
Currently the extension only seems to support the Microsoft Edge Stable and Dev builds. It would be nice if it also supported Microsoft Edge Canary.
Who will benefit from this feature?
Myself and any others who use the Canary build.
Anything else?
No response

Support added in this PR https://github.com/raycast/extensions/pull/7526


Composing enums with @inaccessible tag in two subgraphs fail with wrong @repeatable check

Component(s)
composition
Component version
0.22
wgc version
NA
controlplane version
NA
router version
NA
What happened?
Description
Composing two subgraphs with enums with inaccessible tag failed with wrong @repeatble check error
Steps to Reproduce
Adding these two subgraphs to inaccessible.test.ts, it should succeed, however it failed

test('that there should be no error composing two enum fields with @inaccessible across subgraphs', () => {
  const { errors } = federateSubgraphs([subgraphEnum1, subgraphEnum2]);
  // console.log(errors)
  expect(errors).toBeUndefined();
});

const subgraphEnum1: Subgraph = {
name: 'subgraph-enum1',
url: '',
definitions: parse(`
  type Query {
    entity: String
  }

  enum TestEnum {
    A
    B @inaccessible
  }
`),
};

const subgraphEnum2: Subgraph = {
name: 'subgraph-enum2',
url: '',
definitions: parse(`
enum TestEnum {
  A
  B @inaccessible
}
`),

Expected Result
Composition success
Actual Result
Error, the repeatable should not check across subgraphs?
[
  Error: The definition for the directive "inaccessible" does not define it as repeatable, but the directive has been declared on more than one instance of the type "B".
      at Module.invalidRepeatedFederatedDirectiveErrorMessage (/Users/jiajun.zhao/cosmo/composition/src/errors/errors.ts:269:10)
      at getValidFlattenedPersistedDirectiveNodeArray (/Users/jiajun.zhao/cosmo/composition/src/schema-building/utils.ts:1902:19)
      at getPersistedDirectiveNodes (/Users/jiajun.zhao/cosmo/composition/src/schema-building/utils.ts:1920:8)
      at Module.getNodeWithPersistedDirectivesByData (/Users/jiajun.zhao/cosmo/composition/src/schema-building/utils.ts:1937:26)
      at FederationFactory.federate (/Users/jiajun.zhao/cosmo/composition/src/federation/federation-factory.ts:949:35)
      at Module.federateSubgraphs (/Users/jiajun.zhao/cosmo/composition/src/federation/federation-factory.ts:1382:5)
      at /Users/jiajun.zhao/cosmo/composition/tests/inaccessible.test.ts:161:24
      at file:///Users/jiajun.zhao/cosmo/composition/node_modules/@vitest/runner/dist/index.js:135:14
      at file:///Users/jiajun.zhao/cosmo/composition/node_modules/@vitest/runner/dist/index.js:60:26
      at runTest (file:///Users/jiajun.zhao/cosmo/composition/node_modules/@vitest/runner/dist/index.js:771:17)
]

Environment information
NA
Router configuration
No response
Router execution config
No response
Log output
No response
Additional context
Seems the repeatable check is wrongly applied across subgraphs. We observe this issue after this pr https://github.com/wundergraph/cosmo/pull/595

Hi @jiajun-brex,
This is fixed with the following minimums:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Thanks for the report!


Change exception text to be more readable

Describe the feature
After reading this article - https://docs.aws.amazon.com/appstream2/latest/developerguide/access-api-cli-through-interface-vpc-endpoint.html
They have the following example:
appstream2client = boto3.client('appstream',region_name='<aws-region>',endpoint_url='<vpc-endpoint-id>.api.appstream.<aws-region>.vpce.amazonaws.com'
If endpoint url is given for the boto3 appstream client without a schema (HTTPS/HTTP) the following exception is raised (ValueError)  -https://github.com/boto/botocore/blob/a3c3628cbc7f222a94fbbbf3c478a80198876531/botocore/endpoint.py#L402
which doesn't help the developer understand what should he fix
Use Case
I'm trying to use appstream API via boto3 from Lambda
Proposed Solution
I would suggest adding schema to the error message so it would be clear what is the desired fix -
e.g -  raise ValueError("Invalid endpoint: HTTPS/HTTP://%s" % endpoint_url) or something like that
Other Information
No response
Acknowledgements

[X] I may be able to implement this feature request
[X] This feature might incur a breaking change

SDK version used
1.29.152
Environment details (OS name and version, etc.)
Windows/Linux

Hi @shayfisher thanks for the feature request. Here is the is_valid_endpoint_url function code for reference, and here is where is_valid_ipv6_endpoint_url is defined.
Because there are several conditions that could result in the Invalid endpoint... message, there are some nuances to consider for what the error message should say. I think more discussion is needed to determine what improvements there could be to the error message depending on each condition.
Also in the meantime you could also consider get more detailed logs when debugging by adding boto3.set_stream_logger('') to your script.


Feature Idea: Summary/Short view

I know this isn't directly in the scope of a ls replacement, but I recently wanted to do something like this so I thought I'd ask.
Basically I don't want lsd to blow up my terminal scrollback buffer when I accidentally invoke it in a directory with thousands of files. Piping it to head -10 works, but the performance feels worse than it could be, because it still outputs the whole directory to stdout, we just throw 99.9% of it away. Also this doesnt print multiple entries per line so we're not making efficient use of the screen space
I think what would be useful is a set of flags with something like the following effects:

Only print the first N lines of output
Enable Multiple entries per line even when piped to another program (like--color always --icon always)
Print a summary of the files

This could be applied to the remaining files from the previous option
Number of files, perhaps grouped by filetype, last modified etc

We could probably add something for second point. Something that forces grid display even if the output is being piped through an external program. This combined with head should give you something better.
About the third point, we could probably add another flag --summary but we'll probably have to explore a bit more on what should be display in that.

Builtin head functionality would be nice.  I automatically list the directory whenever I cd and its only a matter of time before I list a directory with thousands of items.  To do the automatic listing I am using the common snippet of bash code as a redefinition of cd:
cd() {
	builtin cd "$@" && ls
}

As pointed out by OP, piping into head is not the most desirable solution.  It changes formatting and if the directory is galactic you will have wait while most of the output is thrown into the void.

lsd will probably never implement a way to limit the number of items that gets printed. We could however enable an option to force grid mode even if the output gets piped to another process. With this, along with forcing colors you can make use of head to trim out just the necessary content.

That solution makes sense to me too

Add a flag which will allow users to force grid view even when the content gets piped through another process. Something like --grid.


⚠ ClamAV has degraded performance

In 12b1a2c, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 102 ms

Resolved: ClamAV performance has improved in 09f2855.


Unexpected insertion when using unordered_map and capacity equals to 4

Describe the bug
The insertion of unordered_map does not work correctly under capacity=4.
Steps to reproduce
Change the n from 100 to 4 in examples/cuda/unordered_map.cu, compile and run this example code.
Expected behavior
the terminal should be:
The duplicate-free map of numbers contains 5 elements (5 expected) and the computed sums are (2, 4) ((10, 30) expected)
Actual behavior
the terminal actually shows:
The duplicate-free map of numbers contains 2 elements (5 expected) and the computed sums are (2, 4) ((10, 30) expected)
System (please complete the following information):

OS: Ubuntu 20.04
Compiler: GCC
Backend: CUDA
Library version: master

@stotko Can you take a look? thanks!

Thanks for the report! This is indeed an issue for very low capacity sizes as the internal excess list is too small in this case. #414 fixes this issue.


Fix bug where peeking to determine whether a field is an SQ would be …

…skipped if the vrCallback returned undefined, meaning it could not determine the VR.

Coverage increased (+0.1%) to 52.027% when pulling 629a825f0786b63090dcb945918079b7a37cafd2 on yagni:vr-callback-undefined-fix into 00071e123d860ceacb7b5f82e4d84ff65b7dda6d on cornerstonejs:master.


bump NCS to v2.1.0

NRF_SECURITY module in NCS is enabled by default and we probably want to
keep it enabled, so that existing NCS users are not restricted by Golioth
SDK (e.g. by forcing NRF_SECURITY to be disabled). This module seems to
dropped old/legacy SPM module and now uses something new, which pulls in
NCS fork of mbedTLS as a dependency. This is expressed by 'select
DISABLE_MBEDTLS_BUILTIN if MBEDTLS' in both NRF_SECURITY and
NRF_SECURITY_BACKEND Kconfig options.
Using NCS fork of mbedTLS means selecting
CONFIG_MBEDTLS_TLS_LIBRARY (CONFIG_MBEDTLS_TLS_LIBRARY is NCS fork,
CONFIG_MBEDTLS_BUILTIN is Zephyr fork of mbedTLS).
NCS fork (as compared to Zephyr fork) of mbedTLS has set of Kconfig options
that are named differently (like CONFIG_MBEDTLS_SSL_PROTO_DTLS in NCS vs
CONFIG_MBEDTLS_DTLS in Zephyr), while other options are named the same. As
a result we are selecting CONFIG_MBEDTLS_SSL_PROTO_DTLS and
CONFIG_MBEDTLS_GCM_C to match what net/golioth/Kconfig file is selecting
automatically for the user.
Disable unused CONFIG_MBEDTLS_KEY_EXCHANGE_DHE_PSK_ENABLED and
CONFIG_MBEDTLS_KEY_EXCHANGE_DHE_RSA_ENABLED. Those are enabled by default
in NCS, by questionable 'default y if !NET_L2_OPENTHREAD'. Leaving them in
default state (y) breaks the build because of unmet dependencies (other
mbedTLS configuration options).
Increase mbedTLS heap size from 10kB (in prj.conf) to 48kB in order to make
it run. 32kB was still not enough in case of samples/hello/, so 48kB was
chosen to give enough room for future.
Tested with lightdb, lightdb_stream, logging and dfu samples.

10kB (in prj.conf) to 48kB

That's a big jump, but I suppose there's not much we can do it about it right now.

Not even able to easily measure peak consumption, as mbedtls shell command that I developed (and upstreamed to Zephyr) for that purpose works only with MBEDTLS_BUILTIN (Zephyr fork). Hence I only tried 32 (with failure) and then 48 (with success). So here it is. At least there is stil plenty of RAM (total of 200kB) to be utilized, so we are still far from the limit.


add: Rishitha Nandanapu

Description
Added My Profile
Related Issues

Changes Proposed

Checklist

[x] I have read and followed the Contribution Guidelines.
[x] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

Hi @n14rishitha , thanks for your interest in contributing to DevDisplay!
We noticed you adding your profile on #DevDisplay but forgot to star the repo. It's like making an amazing sandwich and forgetting to take a bite! -- I think our repo's feeling a little lonely without your 🤗 So, be sure to star the DevDisplay GitHub Repository. 🌟
💌 This is a mandatory step for all contributors. & It's is the first priority of contribution in DevDisplay 💌
Thanks 👍🏻


Update chatbot_model.py

User description
未命中场景时 不用大模型作通用回答，直接回复“未命中场景”

PR Type
Bug fix

Description

Removed the fallback to the large model for unmatched scenarios in process_multi_question.
Directly respond with "未命中场景" when no scenario is matched.

Changes walkthrough 📝
Relevant filesBug fix

chatbot_model.pyModify unmatched scenario response handling

models/chatbot_model.py
Removed fallback to large model for unmatched scenarios.  Directly respond with "未命中场景" when no scenario is matched.

+0/-2

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

Preparing PR description...

PR Description updated to latest commit (https://github.com/yanyg123/llm_intend/commit/7a2db214f1a7afe101ce13c71886bab3d3a3ab21)

Preparing PR description...

Preparing PR description...

Preparing PR description...

PR Description updated to latest commit (https://github.com/yanyg123/llm_intend/commit/7a2db214f1a7afe101ce13c71886bab3d3a3ab21)

Preparing PR description...

PR Description updated to latest commit (https://github.com/yanyg123/llm_intend/commit/7a2db214f1a7afe101ce13c71886bab3d3a3ab21)

Preparing PR description...

PR Description updated to latest commit (https://github.com/yanyg123/llm_intend/commit/7a2db214f1a7afe101ce13c71886bab3d3a3ab21)

Preparing PR description...

PR Description updated to latest commit (https://github.com/yanyg123/llm_intend/commit/7a2db214f1a7afe101ce13c71886bab3d3a3ab21)

Preparing PR description...

PR Description updated to latest commit (https://github.com/yanyg123/llm_intend/commit/7a2db214f1a7afe101ce13c71886bab3d3a3ab21)

Preparing PR description...

Preparing PR description...

Preparing PR description...

Preparing PR description...

PR Description updated to latest commit (https://github.com/yanyg123/llm_intend/commit/7a2db214f1a7afe101ce13c71886bab3d3a3ab21)

Preparing review...

PR Review 🔍

 ⏱ Estimated effort to review [1-5]
1, because the PR involves a simple change in the logic by removing a couple of lines and altering the response message. The change is straightforward and limited to a single file with a clear description.

 🧪 Relevant tests
No

 ⚡ Possible issues
Possible Bug: The commented line # return '未命中场景' might be intended to replace the removed lines. If it's supposed to be active code, it should be uncommented.

 🔒 Security concerns
No

 Code feedback:
relevant filemodels/chatbot_model.py
suggestion

It seems like the line # return '未命中场景' is intended to be the new response when no scenario is matched. If that's the case, this line should be uncommented to activate it. [important]

relevant line# return '未命中场景'

Generating PR code suggestions
Work in progress ...

Preparing answer...

Ask❓
What is the purpose of this PR?
Answer:
The purpose of this PR is to modify the behavior of the process_multi_question function in the chatbot_model.py file. Specifically, it aims to address a bug by removing the fallback mechanism that previously routed unmatched scenarios to a large model for a generic response. Instead, the function will now directly respond with "未命中场景" (which translates to "Scenario not matched") when no scenario is matched.

Preparing PR description...

PR Description updated to latest commit (https://github.com/yanyg123/llm_intend/commit/7a2db214f1a7afe101ce13c71886bab3d3a3ab21)

/review

/test

/analyze

/test chatbot_model.py

/test  process_multi_question


fix: Add long dependency

Fixes #998

the ci/cd is a nightmare

Has anyone managed to resolve this problem?


Do you have a concrete plan to release YOLOX-P6?

Yes, but with a very low priority, which is the same for 365object pretrain. Currently, our computing resources have more interesting tasks to do. For larger models on COCO, I suggest you consider Swin-Transformer or Scale-yolov4 at this time.

What's your current interesting tasts?


Plans to create new commands (open and close)?

Does anyone have plans to extend this to have commands to open and close pull requests? If not, I'll send a PR.
To create a pull from the current branch:
git pull open -t <title> -d <description>
Would need to determine the target repo and branch name somehow.
Straight forward close:
git pull close <id>

What about making git request-pull a 1st-class citizen on GitHub? http://git-scm.com/docs/git-request-pull

It doesn't create pull requests. GitHub has its own Pull Request mechanism that we’ll go over in GitHub. git request-pull command generates an output you can email to the project maintainer manually. That's all.
Since last time, a lot happened regarding octokit. I'll try to go with Octokit/Client/PullRequests#create_pull_request and Octokit/Client/PullRequests#update_pull_request.

For anyone not wanting to wait another 3 years, you can use
hub pull-request

http://github.com/github/hub

No need to be condescendant. For those who don't want to wait, they can contribute and even take over the project. That's what I did (mainly as a maintainer). You just need to ask.
Still, hub is a perfect alternative.

@AdrienGiboire a comment on why you are closing this without fixing would be appropriate

As you rightly mentioned, this is going nowhere. The OP does not seem to be about to make the PR and I don't have time to duplicate behaviours implemented by hub.

So you close all issues that dont have a PR? Why have issues at all?

Because this is a request for a feature, pending for a long time now. I don't handle bug issues the same way.


Add unsortedsegment(prod/min/max/sqrt_n/mean).

This pull request

adds CPU/GPU implementations of

tf.unsorted_segment_min,
tf.unsorted_segment_prod and a
GPU implementation for tf.unsorted_segment_max.

adds python implementations of:

tf.unsorted_segment_mean
tf.unsorted_segment_sqrt_n

fixes the gradient calculation for unsorted_segment_sum/max.
#13055 introduced silent dropping of negative values on the cpu.
However, the gradient of e.g. unsorted_segment_sum used tf.gather
and therefore failed for negative indices on cpu.

I tried to simplify the code and to remove code duplication,
addressing this todo.
(Also I once filed an  issue  to add these ops but only now had time to finish it ;).)
Some notes on this pull request:

tf.gather returns zero on GPU for negative indices and raises an exception on
CPU. To overcome this, the current implementation masks negative indices and
sets them to zero later. This is of course not as efficient as the original gather.
Would it make sense to use something like if "gpu" in op.device.lower(): to run
different functions, depending on the device?

Instead of having a native op for mean/sqrt_n I added them in python.
Making them native would require two additional template arguments
(a functor to process the counter), resulting in more complicated code with
probably only minor performance improvement, if at all. In my quick
benchmarks, the python ops are nearly as fast as unsorted_segment_sum. However,
they use more memory than a native op would, due to creating a tensor of ones.
(bincount doesn't work here as it doesn't support negative indices)

I simply copy-pasted some atomicOp code in cuda_kernel_helper.h instead of
writing this more nicely as for a short period there was a completely different
version of this file online and I wanted to check back with you before
doing something more sophisticated. What's the status of this?
Additionally, I guess the function AccumulateInto in segment_reduction_ops_gpu.cu.cc
could be removed? CudaAtomicAdd has specializations for complex types in
cuda_kernel_helper.h

Cheers,
Phil

Thanks for the comments!
I tried to enable bfloat16, but I struggle to do so for unsorted_segment_{mean,sqrt_n}. I enabled bfloat16 for cwise_max and fixed double registration in the reshape op but I don't know enough about the inner workings of tf to quickly implement the real_div op for bfloat16. So for now I disabled the test cases for mean/sqrtn + bfloat16.
In theory, these ops should work with bfloat16 once real_div is implemented. Would you be fine with enabling the test cases as soon as someone implemented div?

@PhilJd Thanks a lot for adding partial support for additional types! We can certainly leave complete support for bfloat16 for a future change.

I'll look into the test failures tomorrow morning!

The GPU CC build should be fixed, the failure of the Android Demo App seems unrelated (tar exited with 1). I'm not sure why Ubuntu Python3 PIP failed,  I can't reproduce it locally...

@PhilJd Thanks again for a great contribution!


Update Importing 3D scenes links to match splitting PR

See https://github.com/godotengine/godot-docs/pull/7830

Is it ok if we merge this first or will the urls be in consistent?

Didn't see it was based on a yet unmerged docs PR, so of course this should wait for the godot-docs one to be merged.


feat: added prop to call http request with more parameters

This this contribution work for call intelligense Search request with more parameters beyond the default?
Loom

UP @wellingtonjr3873

Closed by inactivity.


fix(build): revert inadvertently-committed directories

This PR contains the following changes:

it reverts a recent commit that inadvertently committed the coverage, dist, and node_modules directories
temporarily removes the generation and publishing of jsdocs until we can figure out the correct course of action
bumps the version of normalize-url package to avoid a high-severity vulnerability

PS: Wow, my PR is removing 3.3M lines :)

:tada: This PR is included in version 2.11.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Refactor sychronization in client factories

Implementation for #269
Refactored NFHttpClientFactory  and ClientFactory to synchronize on the name of the client being registered instead of the entire class instance.

NetflixOSS » ribbon » ribbon-pull-requests #66 SUCCESS
This pull request looks good


Publicly export MapFieldNames

Describe your question
arrow::array::MapBuilder is public (https://github.com/apache/arrow-rs/pull/1355), but MapFieldNames is not, making it impossible to call new() and with_capacity() with a proper value.
https://github.com/apache/arrow-rs/blob/3096591520d303eb34a432c82733e86f34999232/arrow/src/array/builder/map_builder.rs#L61-L68
I guess MapFieldNames should be exported too, should it?

This was an accidental bug introduced by #1879

@tustvold  is this a regression in 19.0.0 (aka should I cut a new release candidate)?

I think it was a regression that landed in 17.0.0 and was only just noticed...


Updating Scalar List Values  of a Node does not trigger a change of the updatedAt value of a Node

Changing a scalar list value of a node should change the updatetAt value of that node.

The Mongo connector already behaves like expected and will change the updatetAt value when changing a list value.


Seeking Resource Manager for ClassLink

I am searching for someone to manage study material for the ClassLink App, assuring relevant and up-to-date information. Contributions will have a significant influence. Interested? Please leave a comment!

Hey I am interested in managing the resources.


Enable reading secrets from files

This only addresses the prometheus/prometheus portion of this issue.
Similar issues exist in other repositories under the prometheus
organization.
Closes: #8551
Signed-off-by: Marcelo E. Magallon<EMAIL_ADDRESS>

This depends on an open review in promethes/common (https://github.com/prometheus/common/pull/320)
This part of the code doesn't seem to have many tests, I wasn't sure whether they should be added
Which documentation should be updated? I suppose it's only docs/configuration/configuration.md?

@mem @roidelapluie we have run into this during our bug scrub. It would still be nice to get this unstuck. @mem at first glance, @roidelapluie 's comment about sigv4 getting fixed upstream in prometheus/common is not addressed yet. Would you be willing to still work on this?
Maybe other comments still need to be addressed?

Hello again from the bug scrub. We still think this is valuable, but there was no response to the last nag almost half a year ago. We are closing this now, but whoever wants to pick up the work, please re-open or create a new PR.


Optionally override one-span-per-rpc

Add option to override default one-span-per-rpc behaviour. This is
useful to visualize RPC calls as nested spans.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

Coverage increased (+0.3%) to 94.296% when pulling 39c88a46a27fecb9c3848a39677edf1b7a7f5b44 on philipgian:one-span-per-rpc into 626ee224d3b46ddaa600f2e8e23c7c63c6055ac1 on uber:master.

Please merge or rebase from master to fix the build (cf. #33).
Also, you will need to sign a contributor agreement (once).

Coverage increased (+0.3%) to 94.296% when pulling e53086ab71f7f4f8888f5825a0bd1cfa6dbf5391 on philipgian:one-span-per-rpc into 312a9d08febf95427568a4ab03a642a74b33088a on uber:master.

I've signed the CLA, but the relevant check is not updated. Does it require manual approval or is something wrong ?

It's possible the check only runs on push. Can you add a line to the CHANGELOG file, e.g. "Allow overriding one-span-per-rpc behavior" and push again?

Coverage increased (+0.3%) to 94.296% when pulling a4eb99f4ea811fb508a40ab9bfba4c5c7c29473f on philipgian:one-span-per-rpc into 312a9d08febf95427568a4ab03a642a74b33088a on uber:master.


Create version for Intellij IDEA

That would be great.

Hey @rofrol, thanks for the interest in the project! Due to how long ago this issue was opened, I'm going to close it. You are more than welcome to fork this repo and create a version for Intellij!


Added Announcement bars & Footer

Handle multiple announcements
Added color picker field on WP
Added html parser to render the wysiwyg field

Updated Footer with components created

Wired wp menu to gatsby header
Doc on wp menu


Update service-bus-powershell-how-to-provision.md

Change Write-Output to Write-Host.

Hi @alexandair, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

@sethmanheim Hi Seth. Please review this proposed content. Thanks.

@alexandair Many thanks for catching that (and good to meet you)! OK to merge.  #sign-off


Is the microsoft/power-platform provider available in the OpenTofu registry?

Thank you for reporting an issue.
Hello OpenTofu team,
I am currently migrating my Terraform setup to OpenTofu and have encountered an issue while trying to use the microsoft/power-platform provider. It seems that the provider is not available in the OpenTofu registry, as I receive the following error during initialization:
Error: Failed to query available provider packages

Could not retrieve the list of available versions for provider
microsoft/power-platform: provider registry registry.opentofu.org does not
have a provider named registry.opentofu.org/microsoft/power-platform

I would like to confirm whether the microsoft/power-platform provider is currently supported in the OpenTofu registry, or if there are plans to add it in the future.
Additionally, if it is not available, are there any alternative providers that can be used for managing Power Platform resources in Azure?
Thank you for your help, and I look forward to any guidance you can provide.
Best regards,
OpenTofu Version
$ tofu version
OpenTofu v1.6.1
on linux_amd64

OpenTofu Configuration Files
$ cat providers.tf
provider "powerplatform" {
use_cli = true
}

It is not currently in the registry, I can submit it now.  In the future, you can try to submit a provider via https://github.com/opentofu/registry/issues/new/choose, which will auto-close the issue if the provider already exists.

https://github.com/opentofu/registry/issues/1092

@jmservier Provider entry added, should deploy within the next 15-20 minutes.

For reference, we scraped GitHub looking for providers 10 months ago.  Any providers created since then need to be manually registered with OpenTofu like I have done here.  I'll bring up automating that process with the team next week.

Thanks that is perfect


Multiple events are triggered when hold gesture is not precise

Describe the bug
I was trying to play with Oculus Quest and MRTK. I setup MRTK in a blank unity project and loaded the hand interaction scene.
As i was starting to interact with the scene, i noticed there's some heavy flickering of the hand ray when the ray falls on certain items. Later i released that it occurred when the ray was pointed to certain areas. Areas which will register click or move events.
I've attached a YouTube video and a GIF below. The YouTube video includes the sounds that these events fire. You can judge by the sounds that these events are being fired in a loop like succession.
To reproduce
Steps to reproduce the behavior:

Setup MRTK v2.6.0 on Unity v2020.3.4f1
Load and Run Hand Interaction Example scene on Quest.
Use Hand gestures to interact with the objects in the scene.

Expected behavior
The hand ray shouldn't stutter and multiple events should not be fired when the pinch gesture in in incomplete state.
Youtube Video

Your setup (please complete the following information)

Unity Version [e.g. 2018.3.11f1]
MRTK Version [e.g. v2.6.0]
i.e
Mixed Reality Toolkit Examples v2.6.0
Mixed Reality Toolkit Extensions v2.6.0
Mixed Reality Toolkit Foundation v2.6.0
Mixed Reality Toolkit Standard Assets v2.6.0
Oculus XR Plugin 1.9.0
XR Plugin Management 4.0.1
Oculus Integration 27.0

Target platform
Oculus Quest

This sounds like the bug that should be fixed by https://github.com/microsoft/MixedRealityToolkit-Unity/pull/9576. FYI @RogPodge
Looks like it should have shipped in our 2.7.0-preview.3 package, if you want to take a look!

This sounds like the bug that should be fixed by #9576. FYI @RogPodge
Looks like it should have shipped in our 2.7.0-preview.3 package, if you want to take a look!

With these changes, it seems to have gotten rid of the flicker . Another issue with this fix is that the gesture still emits the event even if there sizable gab between the index finger and the thumb. Although that's not much of a problem as the flickering was.

yeah currently the minimum pinch distance to determine whether an event ought to be raised isn't configurable outside of the code.
If it's alright, can you raise an issue for us to track to make the pinch sensitivity configurable, and we can try to get it in a future release! We could then also close this issue at the same time @kaushikwavhal

We appreciate your feedback and thank you for reporting this issue.
Microsoft Mixed Reality Toolkit version 2 (MRTK2) is currently in limited support. This means that Microsoft is only fixing high priority issues. Unfortunately, this issue does not meet the necessary priority and will be closed. If you strongly feel that this issue deserves more attention, please open a new issue and explain why it is important.
Microsoft recommends that all new HoloLens 2 Unity applications use MRTK3 instead of MRTK2.
Please note that MRTK3 was released in August 2023. It features an all-new architecture for developing rich mixed reality experiences and has a minimum requirement of Unity 2021.3 LTS. For more information about MRTK3, please visit https://www.mixedrealitytoolkit.org.
Thank you for your continued support of the Mixed Reality Toolkit!


#1046: add all necessary dependencies for CVs

Well that was easy. Definitely had some dependencies bugs that this uncovered.

Looks good!


error: unpack requires a buffer of 4 bytes

I get the following error when I try to read one of my .xdf files:
~/lib/python3.7/site-packages/pyxdf/pyxdf.py in load_xdf(filename, select_streams, on_chunk, synchronize_clocks, handle_clock_resets, dejitter_timestamps, jitter_break_threshold_seconds, jitter_break_threshold_samples, clock_reset_threshold_seconds, clock_reset_threshold_stds, clock_reset_threshold_offset_seconds, clock_reset_threshold_offset_stds, winsor_threshold, verbose)
    258             log_str = ' Read tag: {} at {} bytes, length={}'.format(tag, f.tell(), chunklen)
    259             if tag in [2, 3, 4, 6]:
--> 260                 StreamId = struct.unpack('<I', f.read(4))[0]
    261                 log_str += ', StreamId={}'.format(StreamId)
    262             else:

error: unpack requires a buffer of 4 bytes

Although, I can easily read the same file using EEGLab in Matlab. Do you have any recommendations on how I can solve this?
Thanks.

That suggests that you've reached the end of the file buffer, but if True then it should have followed a different code path to break out of the loop.
What logs are printed before this point?
Can you share the datafile?

@cboulay , Thank you for the quick answer. There are no other lines prior to this error.
Here's a link to the file.

I just checked it again with MATLAB and it raises this warning:
Warning: Specified key type does not match the type expected for this container.
> In load_xdf (line 332)
  In eeg_load_xdf (line 35)
  In pop_loadxdf (line 112)

But it still outputs the data inside the file without any errors. It would be nice if we could get rid of this error in pyxdf.
Note: Matlab uses eegplugin_xdfimport to import xdf.

Do you know if your eegplugin_xdfimport is the latest version? Could you try comparing it to https://github.com/xdf-modules/xdf-EEGLAB? (Note that uses xdf-Matlab as a submodule)
I'm not about to install and try to remember how to use EEGLAB, but if your EEGLAB importer is using the same version as general xdf-Matlab then I can test the file on my local Matlab install.

@cboulay I checked it and it is the latest version. It is using exactly the same code as in https://github.com/xdf-modules/xdf-EEGLAB

According to XDFBrowser, there is a stream packet after the footer. Weirdly, enough, for a different stream which apparently does not have a Stream Header. This would explain why i can load successfully.

@FarnoodF How did you record this datafile? Did you use LabRecorder?
Can you think of anything that was different about this file that might lead to a ghost stream?
While we COULD modify pyxdf to not fail when it encounters a 0-byte stream with no header, really the better solution is to figure out how this happened in the first place and prevent it from happening again.

So there is only one valid stream inside, to be more specific, EEG with 18 channels, and 500 Hz sampling rate. Is this as expected, or did you also plan to record more than this stream?

Thank you guys for your time.
I recorded this using a cEEGrid and SMARTING. I just intended to record an 18-channel stream at 500Hz, that's all.
I have recorded over 1000 .xdf files and I have 5 files with the same problem. To my best of knowledge, there was no change in the way I did those experiments.
If the data is present in one of the streams, It would be more convenient to get a warning, instead of an error.

I understand that you recorded the stream with SMARTING streamer, and not with LabRecorder? If that's the case, you might want to inform their developers about the issue.


Added option cachedTransportsCount to shard JDBC connections

Codecov Report
Attention: Patch coverage is 88.23529% with 2 lines in your changes missing coverage. Please review.

Project coverage is 79.71%. Comparing base (577e6c5) to head (5a77a64).

Files with missing lines
Patch %
Lines

...rc/main/java/tech/ydb/jdbc/settings/YdbConfig.java
75.00%
0 Missing and 2 partials :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #86      +/-   ##
============================================
+ Coverage     79.65%   79.71%   +0.05%
- Complexity     2073     2075       +2
============================================
  Files            61       61
  Lines          5638     5639       +1
  Branches        664      666       +2
============================================
+ Hits           4491     4495       +4
+ Misses          847      843       -4
- Partials        300      301       +1

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


CredentialUnavailable [Error]: ManagedIdentityCredential authentication failed. Message AbortController is not defined at ManagedIdentityCredential.

@azure/identity:
2.1.0:
Windows 10:
[x] nodejs

14.21.3:

[x] Chrome

name/version:

[ ] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
When calling the getToken function on a recently created instance of a ManagedIdentityCredential this error occurs:

CredentialUnavailable [Error]: ManagedIdentityCredential authentication failed. Message AbortController is not defined at ManagedIdentityCredential. (/home/site/wwwroot/node_modules/@azure/identity/dist/index.js:1397:27) at Generator.throw () at rejected (/home/site/wwwroot/node_modules/tslib/tslib.js:167:69) at processTicksAndRejections (internal/process/task_queues.js:97:5)
Error

To Reproduce
Steps to reproduce the behavior:
const ManagedIdentityCredential = require("@azure/identity");

const credential = new ManagedIdentityCredential();
try {
  const serviceToken = await credential.getToken("https://graph.microsoft.com/.default");
} catch (e) {
  context.log.error(e) // prints out error seen above in description
}

Expected behavior
Proper service token is generated by the getToken function.
Screenshots

Additional context
Please let me know if more information is necessary.

It looks like the underlying bug might be in @azure/abort-controller 2.0.0. It looks like some code was accidentally removed or commented out in that release of @azure/abort-controller.
The following program fails to run (or typecheck with tsc) because 'AbortController' is no longer exported by @azure/abort-controller.
import { AbortController } from "@azure/abort-controller";

if I look at<EMAIL_ADDRESS>AbortError is the only thing exported. However, the README for @azure/abort-controller 2.0.0 contains several pieces of example code that have exactly the above import statement in them.

@richardbarrell-calvium yes, we remove our implementation of AbortController in @azure/abort-controller v2 because our current supported platforms all have AbortController built in.
However, if I remember correctly we haven't published any packages that depend on @azure/abort-controller v2 yet.  Published version of @azure/identity still depends on @azure/abort-controller ^1.0.0 https://www.npmjs.com/package/@azure/identity/v/4.0.1?activeTab=code

For full reference of the versioning of packages in our project:
package.json
"dependencies": {
    "@azure/identity": "^1.2.3",
    ...
}

However to check what version is actually installed I'll run npm list on the packages:
npm list @azure/identity

+--<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>  `--<EMAIL_ADDRESS>
So initially v1.5.2 is installed but it looks like tedious is pulling in v2.1.0
npm list @azure/abort-controller

+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| | +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>| |   `--<EMAIL_ADDRESS>deduped
| +--<EMAIL_ADDRESS>| | `--<EMAIL_ADDRESS>deduped
| `--<EMAIL_ADDRESS>|   `--<EMAIL_ADDRESS>deduped
`--<EMAIL_ADDRESS>  +--<EMAIL_ADDRESS>  | `--<EMAIL_ADDRESS>deduped
  `--<EMAIL_ADDRESS>    +--<EMAIL_ADDRESS>deduped
    +--<EMAIL_ADDRESS>    | `--<EMAIL_ADDRESS>deduped
    `--<EMAIL_ADDRESS>      `--<EMAIL_ADDRESS>deduped

Looks like @azure/abort-controller is consistently being pulled in at v1.1.0
Is<EMAIL_ADDRESS>incompatible with<EMAIL_ADDRESS>Is there an ideal versioning setup I should lock them to?
ex<EMAIL_ADDRESS>+<EMAIL_ADDRESS>

I would be surprised if there was an incompatibility between those versions, at least in a way that would cause AbortController to not be defined. The abort-controller package has been stable for a long time and 2.1.0 was released in June 2022.
I will say though that Node 14 is not a supported runtime (our current minimum is 18) and we strongly recommend updating as older Nodes do not receive security updates and have known vulnerabilities. Likewise, using the latest stable of @azure/identity (4.0.1) is highly recommended.

The Fix: So it seems our deployed environments were actually installing different versions of the packages. As soon as I made explicit version definitions in the package.json and deployed it, the issue resolved. The specific  working versions for anyone curious:
...
"dependencies": {
    "@azure/identity": "1.2.3",
    "@azure/abort-controller": "1.1.0"
}
...

Thank you all for the assistance!

@richardbarrell-calvium yes, we remove our implementation of AbortController in @azure/abort-controller v2 because our current supported platforms all have AbortController built in.
However, if I remember correctly we haven't published any packages that depend on @azure/abort-controller v2 yet. Published version of @azure/identity still depends on @azure/abort-controller ^1.0.0 https://www.npmjs.com/package/@azure/identity/v/4.0.1?activeTab=code

Thank you for the clarification.


316514 - [Newsroom][Content Migration] Missing Hero Text Display

Description: Missing Hero Text Display
Steps to Reproduce:
Open Migrated Newsroom page https://tempnewsroom.accenture.com/news/2002/accenture-campaign-breaks-new-ground-for-professional-services-firms-brcenteri-am-your-idea-use-me-center
Legacy Page: https://newsroom.accenture.com/news/accenture-campaign-breaks-new-ground-for-professional-services-firms-brcenteri-am-your-idea--use-me-center.htm
Check the hero of the page
Expected:

Actual:

Azdo Link: https://dev.azure.com/accenturecio26/WebContentDigAssetMgmt_PR1093/_workitems/edit/316514
cc: @ravkiran @amol-anand @raymond-h-dev

We have only one style of Hero for all the pages. These articles are older articles that will now follow the new style of hero which is there for all newer articles.


Sidemenu starter: Unexpected animation when using split-pane in other component than app component

Bug Report
Ionic version:
[x] 4.x
Current behavior:
I used the sidemenu starter and moved the split-pane from the AppComponent to a separate component so I can have a login page at root level and make all the stuff with the side menu available to authenticated users only. This seems to work so far, but there is a page transition animation only in the first click on any side menu link. It does not matter which link I click first. See this video.
The browser (tested with Firefox and Chrome) as well as the platform (iOS or MD) does not matter, the issue stays the same.
Expected behavior:
I would expect this animation not to happen.
Steps to reproduce:
See related code.
Related code:
I published the code from the demo app shown in the video here: https://github.com/mahnuh/ionic4-sidemenu-issue-demo
Ionic info:
Ionic:

   ionic (Ionic CLI)             : 4.9.0 (/Users/manuel/.nvm/versions/node/v10.15.0/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 4.0.0
   @angular-devkit/build-angular : 0.12.4
   @angular-devkit/schematics    : 7.2.4
   @angular/cli                  : 7.2.4
   @ionic/angular-toolkit        : 1.3.0

System:

   NodeJS : v10.15.0 (/Users/manuel/.nvm/versions/node/v10.15.0/bin/node)
   npm    : 6.4.1
   OS     : macOS Mojave

Implement your side menu like the sidemenu starter project. Implement your login as a guard and show a component as a modal in your canActivate() method, using modalController.create().

@redwolf2 Thanks for your input, but I do not think that is an ideal solution. I'm not even sure a modal would work without the AppComponent as the main component being loaded.
In the AppComponent there would be lots of stuff that should not be executed for unauthorised users (hello 401), so using a modal to just "hide" all that stuff does not work either.

It's not in the app component. Default route redirects to home. Home has a guard applied.
See: https://medium.com/@ryanchenkie_40935/angular-authentication-using-route-guards-bf7a4ca13ae3

Sure, but when redirected to home, AppComponent will be loaded as the main router outlet is in AppComponent. The menu is in AppComponent as well including the stuff only authenticated users should see or are allowed to execute. Thats why the menu and other stuff needs to be in a separate component only accessible for authenticated users (with the help of guards).

I understand, I only figured it would be easier for you to have a landing page and then use the guard from there.
In your app.component.html you have:
<ion-router-outlet main></ion-router-outlet>
and inside side-menu.page.html
 <ion-router-outlet main id="foo"></ion-router-outlet>
Try to remove the attribute main from app.component.html, because that might be what freaks out the ion-split-pane.

Thanks for the issue! I do not use the main anymore. This is my code:
<ion-split-pane when="lg" contentId="abc-sidebar">
  <ion-menu #leftSidebar contentId="abc-sidebar" menuId="left" type="reveal" side="start">
    <app-sidebar-menu></app-sidebar-menu>
  </ion-menu>

  <ion-router-outlet id="abc-sidebar"></ion-router-outlet>

</ion-split-pane>

Inside app.component.html I only have <ion-app><ion-router-outlet></ion-router-outlet></ion-app> and this is working without problems


Setting up a Node development environment - Using NPM section

Request type

[] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[ x] Correction or update

Details
I may be missing something - I'm very new.  In step 5 of the section Using NPM on the "Setting Up a Node development environment" page, it mentions adding a require statement to "your index.js file."  However, if you follow the steps from the beginning, an index.js file is never generated.

Oh, I see.  The direction to create the file is below the instruction to add the require to the file.  Pretty confusing!

I can see how this could trip people up. I've changed the order around so that it tells you to create the index.js file above the code block instead. Is this better now?


Pixel distortion / shifting when using setDepth()

Version

Phaser Version: 3.70.0

Operating system: Windows 11

Browser: Observed in both Chrome 121.0.6167.8 and Firefox 120.0.1

Description

Game objects appear to visually shift slightly when interacted with, which appears to be based on setDepth(). Although, this may not actually be the culprit. Here's an example:

Which you can interact with here: https://jsitor.com/3vkO_hzB0S
I had made a forum post about this: https://phaser.discourse.group/t/pixel-distortion-shifting-issue/13774 so the full context is available there, but after commenting out setDepth(), which is being used to bring the object to the front so that it can be dragged over other game objects, the problem goes away.
On the forum post, there was a solution posted to specifically set roundPixels to false on the camera, which does solve this problem. However, this seems like a bug? Why would setting a game object's depth cause this visual issue? Also, this problem does not happen in 3.60.0.
Thanks.
Example Test Code

https://jsitor.com/3vkO_hzB0S
Additional Information

Looks like it's only a issue with the WEBGL renderer, can't get it to reproduce in canvas.

seems to only be an issue in WEBGL and not CANVAS, also seems to be an issue with having multiple scenes render, I consolidated your example test code into a single scene (with some minor adjustments) https://jsitor.com/z3lB4A5yWE and can't get it to reproduce afterwards. I'm not versed enough in the webgl renderer to dive much further but hopefully this helps Richard or someone else track this down.

Thanks for taking a look. My original example was born from the project I'm working on that uses two scenes - one for the game world and one for drawing UI objects and handling UI interactions (e.g. dragging game items to your inventory). Although the issue presented itself while using setDepth() and there's at least a temporary fix by setting the UI scene's camera roundPixels property to false, maybe the root issue is more in line with what you've discovered - using webGL and multiple scenes.

https://phaser.io/sandbox/q89fEzzs

Thanks for that example @samme - this was a roundPixels issue and is fixed in v3.85 - you can confirm this in the sandbox by changing the version to 'dev'.


increase benchmark rounds to 10

We need to increase the benchmark rounds to 10 to get realistic benchmarks. After 4 rounds it optimizes for maximum speed.
uzlopak@uzlopak-Lenovo-Legion-5-17ARH05H:~/Workspace/fastify/busboy$ npm run bench:dicer

><EMAIL_ADDRESS>bench:dicer
> node deps/dicer/bench/dicer-bench-multipart-parser.js

1515.15 mb/sec
1351.35 mb/sec
1333.33 mb/sec
2127.66 mb/sec
2127.66 mb/sec
2127.66 mb/sec
2127.66 mb/sec
2127.66 mb/sec
2173.91 mb/sec
2127.66 mb/sec

Checklist

[x] run npm run test and npm run benchmark
[x] tests and/or benchmarks are included
[x] documentation is changed or added
[x] commit message and code follows the Developer's Certification of Origin
and the Code of conduct

Would be nice to move the whole benchmark thing over to some proper benchmarking engine, but this is a welcome improvement until that happens :)

linting is failing

I wonder if benchmark needs to be expanded to be run on less static data, otherwise its results are actually going to be less accurate due to optimizer tightly optimizing specifically for the one hardcoded path in the benchmark, e. g. completely disregarding potential megamorphism that would be present in real-world scenarios.


fix(secret)!: change from 'password' to 'passphrase' for secrets

This differentiates between "Passwords", used to authenticate access to the app,
and "Passphrases", which are used to encrypt/decrypt secrets.
The API parameters also change from 'password' to 'passphrase' for secret generation/decryption.
FIXES: #6

Nice! I'll check it out and review tomorrow morning

This does quite a bit more than change password -> passphrase. Can you update the commit message to better reflect that? i.e. "fix terminology, typos, and optimize javascript"?

Instead of augmenting the commit message, I decided to break some of the changes into separate commits and PRs.  This one is as minimal as I can make it.
Side note:  I've started to use https://www.conventionalcommits.org/en/v1.0.0/ for things.   If we/you wanted to, follwoign that allows you to auto generate the CHANGELOG and other stuff that is useful.  YMMV.


🚀 2021.4.0 Beta - the one with TypeScript

<EMAIL_ADDRESS>Note: all packages received a pre-minor bump (instead of pre-patch) for the beta and upcoming stable
See comments below, fixes INS-706

It appears CI is failing on smoke tests because it cannot install insomnia-importers because<EMAIL_ADDRESS>is bugged.

In order to fix this we need to fix importers and release a beta.1, then re-build the release.
I will do so now in the following commits, otherwise merging this to develop will break all CI.

This is why smoke tests keep failing after publishing packages

@develohpanda I don't think we can pack insomnia-plugin-kong-bundle since we need to be able to read the package.json of it, currently getting the following error when launching the app:

Interesting 🤔 okay, what I'll do for the time being is disable smoke tests and remove it from packed deps to make sure everything is green; we know smoke tests run and the few cases in there we can check manually


Running as a service under linux and windows

Linux : set up Tabula to run as a Docker service : https://github.com/newsdev/tabula/blob/master/Dockerfile
NOTE : idea by  jeremybmerrill
Windows : set up Tabula to run as a Windows service using NSSM : http://nssm.cc/
NOTE : it doesn't require a "Windows server" flavour, I am running it under a virtualized Win XP.
Open issues:

at startup, disable the automatic launch of a browser ( issue 534 );
disable the document history ( My files ) : it is common to all users and in this usage it is useless and unwanted ( privacy first ).

Please add you comments and suggestions.
Best regards, Sala

Issue 534 solved.
Runnning tabula as a windows service, at every service start it spawns a istance of IEXPLORE.EXE.
Adding this to the java options, stop launching the system browser
-Djava.awt.headless=true

Reading the source code, I understand it isn't possible to disable "My files", is it right ?
So, a simple idea : not using a common workspace, but one different for every user.
To keep it simple,  as a quick test, my idea is not creating user's sessions, but just use clients' IP address to create different workspaces.
In these JRuby files
tabula_web.rb
generate_document_data.rb
how is it possible to use

worspace-<client_IP>.json

I don't know Ruby, I found the property request.ip but I don' know how to update the code.
Last step : make the javascript make a request not for a static file

/pdfs/workspace.json

but for a dynamic workspace.json file.
The back-end, receving this HTTP GET, reply with a redirect to the correct

worspace-<client_IP>.json

If the developers help me to make these changes, I can test it and report to you.
best regards, Massimo

@massimosala The way you describe would work fine, I think, and it could probably be done without affecting the primary single-user use case. However, I don't think it is a high priority for the Tabula developers right now.
This would be a good enhancement to be submitted as a pull request by someone looking to contribute to the Tabula project.


Fix safesnap excecutor to owner rename

But existing spaces may fail

closing for https://github.com/snapshot-labs/snapshot.js/pull/372


Some tests are currently disabled

Tests that did not run on the ROS2 CI (mostly rendering related) are currently commented out in the code.
The reason is supposedly the missing display on the Jenkins slave.
Ideally the ROS2 Jenkins setup should be able to run the tests.
Our local Jenkins currently executes the tests using the Jenkins Xvfb plugin.
@wjwwood: Is it possible to update the ci.ros2.org setup to run these tests?

Yeah, sorry this was going to be mentioned in my debrief issue about that release, but I haven't gotten around to make that issue yet.

@wjwwood: Is it possible to update the ci.ros2.org setup to run these tests?

No idea 😄.  Might be hard since they are running in docker and the linux host for docker is also headless. Maybe @j-rivero or @scpeters or @sloretz have some ideas about this given their experience testing gazebo.

We run GUI and GPU tests with nvidia-docker on some machines on build.osrfoundation.org. It's not too hard to get it configured, but it does require an nvidia GPU. I have tried with little success to get intel GPU's working with CI, but their power-save features are too strong; I can't get the GPU to work without a monitor physically plugged in.
I've had much fewer issues with the lack of an external display when running GUI and GPU tests on our mac machines, though I do have to make sure the XQuartz app is running for the current user (each user has a distinct X server). I made the XQuartz app one of the startup items for our jenkins user, but I always make sure to manually log in to that user whenever I reboot the machine after software updates.

Is this related to needing an X server to get a render context for opengl? Running gazeob in docker with rendering requires an X server running on the host, with a socket to it mounted as a volume and some related environment variables (see this script for an example).
I haven't investigated, but supposedly EGL solves the problem.
https://devblogs.nvidia.com/parallelforall/egl-eye-opengl-visualization-without-x-server/
https://www.khronos.org/egl

In my experience rviz doesn't need X11 to work on macOS. Though that might be our newer version of ogre (1.10.10 + some commits, i.e. we're using some commit from master until 1.10.11 is released).

do you have a formula for ogre 1.10? I was testing one but it had some runtime problems with gazebo that I haven't resolved

Nope, we build it as one of our packages right now:
https://github.com/ros2/rviz/tree/ros2/rviz_ogre_vendor
This is because we need it on Windows too, and until we can use a released version without patches, it's easier to iterate on it as one of our packages we build.

In my experience rviz doesn't need X11 to work on macOS
It does not specifically require X11, but some kind of display server is necessary to get an OpenGL context.
A virtual framebuffer (e.g. xvfb) should be enough on a Linux slave, but I don't know if something similar exists in the macOS ecosystem.
On Windows a physical display seems to be required.

I'm going to add some information I found when investigating some issues on Windows:

Here is a question listing prerequisites to running display tests on Windows https://stackoverflow.com/questions/19441324/how-to-run-gui-tests-on-a-jenkins-windows-slave-without-remote-desktop-connectio
This implies that running as System user only will probably not be enough. There needs to be some kind of "User" to have a GUI
For us, we also had problems running Jenkins via a Windows system service, we succeeded by using a .bat file and autostart it. This might also be a problem.


[FLOC-2143] Remove host attribute from /state/containers

Probably not strictly necessary, but I feel like it'll encourage people to interact badly with the API.

Thanks.  Is good (except, you know, all the standard red).  Merging.


Review/willem

input events could be combined back together ( my bad :) )
updateInputError returns errors

Should validateInput, clearInputError  still be exported in this case?

Ah you're right. I forgot about the keyup scenario when user fills in fields for the first time.
Never mind!


specify the output path by -o doesn't work

Always output to pdf-vitepress/vitepress-exmaple.pdf
➜  AllAboutIdentity git:(main) ✗ npm run export-pdf

> export-pdf
> press-export-pdf export docs -o docs/public/identity.pdf

  ➜  Local:   http://localhost:16762/

  ◆ Generating  ██████████████████████████████ 1/1 || Idea | 数字身份认证技术与实践

Exported to pdf-vitepress/vitepress-example.pdf

https://github.com/Jeff-Tian/AllAboutIdentity/blob/main/docs/.vitepress/vitepress-pdf.config.ts#L16-L17
Config file first

> export-pdf
> press-export-pdf export docs -o docs/public/identity.pdf

  ➜  Local:   http://localhost:16762/

  ■ Generating  ██████████████████████████████ 71/71 || 数字身份认证技术与实践 | 数字身份
Loading micropip, packaging
Loaded packaging, micropip

Exported to vitepress-20230714-101220.pdf

I removed the configs, and tried again; it output to the current folder with the name vitepress-20230714-101220.pdf, still did not work as expected.
Are any other steps needed?

"docs:outFile": "press-export-pdf export docs --outFile docs.pdf",
"docs:outDir": "press-export-pdf export docs --outDir /tmp/outDir",

parameter without abbreviation


Thoth.Json.Net depends on Fable.Core

Thoth.Json.Net (3.5.1)
  Fable.Core (>= 3.0 < 4.0) - restriction: && (< net46) (>= netstandard2.0)
  FSharp.Core (>= 4.6.2) - restriction: || (>= net46) (>= netstandard2.0)
  Newtonsoft.Json (>= 11.0.2) - restriction: || (>= net46) (>= netstandard2.0)

I think this dependency on Fable.Core should be removed.

This is normal, we need it to support StringEnums
See https://github.com/MangelMaxime/Thoth/issues/148
We include Fable.Core only, for frameworks version supporting it.

if I use netcoreapp3.0 then it shouldn't be there, right?

I don't know, are netstandard2.0 libraries supported by netcoreapp3.0?
For example, if I remember correctly netstandard1.6 was usable from `and co apps.


Update create-compute.yml

@amardeep-jaiman-bh You will need to accept the CLA before we can do the merge. Can you please make sure to agree to the terms?


error: LNK2019

i build my your program QT_GUI on 64x compiler 14 and opencv 3.3.0 and qt creator 4.3.1 64bit and your new update source (bgslibrary-bgslib_py27_ocv3_win64), but i have error below
mainwindow.obj:-1: error: LNK2019: unresolved external symbol "public: __cdecl bgslibrary::algorithms::CodeBook::CodeBook(void)" (??0CodeBook@algorithms@bgslibrary@@QEAA@XZ) referenced in function "class bgslibrary::algorithms::IBGS * __cdecl bgslibrary::createInstance<class bgslibrary::algorithms::CodeBook>(void)" (??$createInstance@VCodeBook@algorithms@bgslibrary@@@bgslibrary@@YAPEAVIBGS@algorithms@0@XZ)
debug\bgslibrary_gui.exe:-1: error: LNK1120: 1 unresolved externals

Had the same error. Change the following to fix it:
diff --git a/gui_qt/bgslibrary_gui.pro b/gui_qt/bgslibrary_gui.pro
index feedbf6..66a6d28 100644
--- a/gui_qt/bgslibrary_gui.pro
+++ b/gui_qt/bgslibrary_gui.pro
@@ -124,7 +124,8 @@ SOURCES += bgslibrary_gui.cpp\
     ../package_bgs/VuMeter.cpp \
     ../package_bgs/WeightedMovingMean.cpp \
     ../package_bgs/WeightedMovingVariance.cpp \
-    ../package_bgs/_template_/amber/amber.c
+    ../package_bgs/_template_/amber/amber.c \
+    ../package_bgs/CodeBook.cpp

 HEADERS  += mainwindow.h \
     qt_utils.h \
@@ -236,7 +237,8 @@ HEADERS  += mainwindow.h \
     ../package_bgs/ViBe.h \
     ../package_bgs/VuMeter.h \
     ../package_bgs/WeightedMovingMean.h \
-    ../package_bgs/WeightedMovingVariance.h
+    ../package_bgs/WeightedMovingVariance.h \
+    ../package_bgs/CodeBook.h \

 FORMS    += mainwindow.ui

Add the ./bgslibrary-master/package_bgs/CodeBook.cpp to the project source files, the file called CodeBook.cpp was ignored.


⚠ ClamAV has degraded performance

In c421c1d, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 61 ms

Resolved: ClamAV performance has improved in b6d9338.


update project to use Swift5

This is basically #698 but without the SPM support since I think that could be a separate PR.
Since the a.m. PR seems to be stale or the branch was not existing anymore I wanted to add this here.

Does the Xcode version also need to be bumped up?


Allow overwriting CompletionFinder debug_stream

We use argcomplete for virt-install (part of virt-manager) and it works great for us!
virt-install command line syntax is quite large and we have
many argument substrings, so we implement custom completer
functions. Naturally we want to test this as well, so we have
some unittest infrastructure for hitting this code. We capture
output by overriding the CompletionFinder output_stream=
argument.
I'm working on moving virt-manager to use pytest as our test
runner, but our completion tests were triggering weird pytest
behavior. After the first completer test was run the pytest
debug logs would show lots of 'Bad file descriptor' errors
and no more test results would be reported.
This seems to have something to do with CompletionFinder
debug_stream behavior, which will unconditionally attempt to
interact with fd=8 if it is available. For the shell case
this is desired behavior but maybe not for the unittest case.
This small series adds a debug_stream option similar to
output_stream, to allow API users to override the debug_stream
default behavior. I verified this can be used to avoid the
issues I'm seeing with pytest.
Patch #1 renames the global debug_stream, so we can use that
variable name for the call signature.
Patch #2+#3 fix some doc issues in this area.
Patch #4 adds debug_stream argument and test coverage

FWIW the travis failure seems unrelated to this PR.

Thanks for your contribution. I'm afraid this level of configurability is outside the scope of argcomplete's commitment to its users and we will not be able to take on this feature and its associated future maintenance overhead.
If you need something like this for testing, I recommend looking into subclassing, mocking, or monkey-patching to inject this behavior in your test suite.

Thanks for your contribution. I'm afraid this level of configurability is outside the scope of argcomplete's commitment to its users and we will not be able to take on this feature and its associated future maintenance overhead.
If you need something like this for testing, I recommend looking into subclassing, mocking, or monkey-patching to inject this behavior in your test suite.


[Improvement] Enderwire peripheral connector for turtles and pocket computers

Describe your idea
Basically, there is should be a way to connect pocket computer and turtles to enderwire networks. I guess, only interdimensional once, to avoid problem with range invalidation
Additional context
No response
Linked Issues
No response

After discussion with SquidDev, I figure out, that I can try to implement modem interface and not using modem itself: https://github.com/SquidDev-CC/CC-Tweaked/blob/mc-1.16.x/src/main/resources/data/computercraft/lua/rom/apis/peripheral.lua#L37.


Issue with source map in v0.2.37 when running with Vite

When running the project with Vite, it's throwing this error:
(It doesn't prevent Vite from running, it's just annoying)
  VITE v5.2.11  ready in 257 ms

  ➜  Local:   http://localhost:7860/
  ➜  Network: http://<IP_ADDRESS>:7860/
✘ [ERROR] Expected "," in source map but found "MLC_DUMMY_REQUIRE_VAR"

    node_modules/@mlc-ai/web-llm/lib/index.js.map:1:212952:
      1 │ ...st performanceNode = "MLC_DUMMY_REQUIRE_VAR";\r\n            ret...
        │                          ~~~~~~~~~~~~~~~~~~~~~
        ╵                          ,

  The source map<EMAIL_ADDRESS>was referenced by the file<EMAIL_ADDRESS>here:

    node_modules/@mlc-ai/web-llm/lib/index.js:8190:21:
      8190 │ //# sourceMappingURL=index.js.map
           ╵                      ~~~~~~~~~~~~

Temporary solution: remove the //# sourceMappingURL=index.js.map line from @mlc-ai/web-llm/lib/index.js before compiling and Vite won't throw any errors.

Extra info: The v0.2.35 didn't have this problem.

Thanks for reporting the error, will send a fix soon

Could you try 0.2.38? Should be fixed via https://github.com/mlc-ai/web-llm/pull/415. Apologies for the inconvenience

Thanks for the quick response, @CharlieFRuan!
I've installed v0.2.38 and noticed a difference already, but now the error is in another place of index.js.map:

Which seems to be fixable with the same solution used in #415.

Sorry, @CharlieFRuan and @tqchen,
It seems the fix on https://github.com/mlc-ai/web-llm/pull/420 didn't solve the problem with "MLC_DUMMY_PATH".
I just confirmed that this issue is present on v0.2.39:

I also double-checked it on https://www.npmjs.com/package/@mlc-ai/web-llm?activeTab=code and we can see the issue is there on v0.2.39 release:

Can we re-open this issue, and could you confirm why the change on #420 didn't fix it?

Ahh thanks for the catch; this should be due to the other dummy string we set. Will send a patch now and fix in 0.2.30

Could you try 0.2.40 which includes https://github.com/mlc-ai/web-llm/pull/440?

Thank you! Now it's fixed! 🎉
Confirmed here:

And also by removing the workaround I had for the issue.


chore: release 1.2.96

:robot: I have created a release *beep* *boop*
1.2.96 (2022-05-05)
Features

update helm v3.8.1 to v3.8.2 (7f4e6b7)

Bug Fixes

helm: solved broken 3 way merge case when pre-upgrade hook fails (a4610e3)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/werf/werf/releases/tag/v1.2.96 :sunflower:


No auto-import on Mac VSCode

In our team (all Mac) we can't seem to get auto-import in Vue files working.
If we type const foo = computed and hit tab, it won't import computed from vue, but will instead auto-complete to getComputedStyle. None of vue's methods get imported and we have to do that manually.
It looks like auto-complete does work for people on Windows (I can't test that myself).
Maybe we're missing a setting or something, but this is the default install for Volar and our tsconfig has the proper node resolution and strict mode.

I can't reproduce the problem, can you try:

Can working on *.ts files?
Can working on a new project? (Try https://github.com/johnsoncodehk/volar-starter)
Can working with Vetur?

These are my results (I will also dig deeper in the mean time):
Using .ts files (my Vite project, not working):

New project (cloned from your repo, working):

Vetur (my Vite project, not working):

So far it looks like it may be something related to the configs?

So far it looks like it may be something related to the configs?

Yes I think so, can you share a small reproduce to me for check?

If I copy over the vite config and tsconfig it still doesn't work.
I'm at a complete loss...

I think it might be related to path finding of node_modules, share full project (no need *.ts and *.vue) to me will be better.

I can't unfortunately, it's a huge, private repo.
I'll try to figure this out myself then :/

Oh man I found it!
This particular instance is a vue component library and it doesn't have vue as a dependency as it gets removed from the library anyway. If I make it a dep it works.

@TheDutchCoder I am facing the same problem as you. Please let me know the specific cause and how to fix it!

my *.ts is no problem , but in my *.vue file  auto import not working .what happend? (vetur plugins is working, volar not working)

Please provide a repro case, otherwise I can't survey at all.

@ami7ava thanks. [TS Error] Error: Debug Failure. False expression is upstream TS bug, you can try to use lower TS version from workspace to avoid for now.

Same problem. Use https://github.com/johnsoncodehk/volar-starter as project, in vscode plugin vetur is ok, but volar is not. In *.ts or *.vue file, volar can only auto import defineComponent from '@vue/runtime-core', other like ref, reactive will not work.

I also have this problem again. If memory serves me well, I reported the issue and it was closed due to it being a TS problem.
I just don't understand how this keeps changing with TS versions.

It seems like using Take Over mode, and switching TypeScript version from VS Code version (4.4.3) to workspace version (4.5.2) at the Command Palette worked for me. Not sure if this solution may help.

It seems like using Take Over mode, and switching TypeScript version from VS Code version (4.4.3) to workspace version (4.5.2) at the Command Palette worked for me. Not sure if this solution may help.

It worked! Thank you so much.

I just don't understand how this keeps changing with TS versions.

We are downstream so we can't avoid it. :S We can just try to adapt it as fast when it introduces breaking changes.
You can follow @hakula139's suggestion to config fixed TS version in workspace, so VSCode version updating will not change your TS behavior in IDE.

@johnsoncodehk I understand, thanks, I will try @hakula139's suggestion!

@TheDutchCoder I think it just because volar extension have not active yet, you need to open any *.vue script to trigger volar active.


Disable stacktrace checking for TestVerificationFailureHandlingIntegr…

…ationTest
Otherwise it's flaky because of the IOException stacktrace. e.g: https://ge.gradle.org/s/axa4pkgduy3nc/tests/:testing-jvm:noDaemonIntegTest/org.gradle.testing.TestVerificationFailureHandlingIntegrationTest/task does not execute when it has a test task output dependency and VM exits unexpectedly?top-execution=1

@bot-gradle test rfr

OK, I've already triggered ReadyForRelease build for you.

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test and merge

OK, I've already triggered a build for you.


ValueError: Cannot create a tensor proto whose content is larger than 2GB.

Hello,
I am hitting tensorflow limits when feeding a larger dataset to the model.
my model looks like:
@pm.model
def model(X, clicks, conversions):

    b_0 = yield pm.Normal(loc=0., scale=10, name='b_0')
    betas = yield pm.Normal(loc=0., scale=10, name='betas', batch_stack=X.shape[1])

    # Expected value
    p = tf.math.sigmoid( b_0 + tf.tensordot(betas, tf.cast(X.T, tf.float32), axes=1) )

    # Data likelihood
    obs = yield pm.Binomial('obs', clicks, p, observed=conversions)

In this way I believe tensorflow is including the whole dataset into the graph. Is that the correct way of doing linear regression? How can I avoid hitting such limit? Other examples are doing smth similar, e.g.:
https://github.com/pymc-devs/pymc4/blob/master/notebooks/radon_hierarchical.ipynb
Thanks in advance
C

There exist a protobuf limit reported here


Looking for ideas for decreasing the webpack bundle Size

When you run npm run build you can see the bundle size is ~1.5mb parsed and ~480kb gzipped. I am curious if there are any experts on webpack that help with solutions for decreasing the bundle size.

I don't believe it would be realistic to do so, but I did experiment with Preact and saw a significant decrease in size. I did not explore this fully, but wanted to field this issue to see if anyone has some quick wins.
with preact 👇🏾

480kb is not that bad..

Yes preact is great stuff!
Idea 1: update to webpack 2 and use tree shaking..  it really works.. https://webpack.js.org/guides/tree-shaking/
Idea 2: optimize lodash loading via a webpack plugin and save some kb-s. https://github.com/lodash/lodash-webpack-plugin

Good pointers @peet86  - if you're up for giving either of those a shot it'd be a welcome improvement :)

Slightly beside the point here, but wouldn't it be better, if you guys are hosting it on HTTP/2, to bundle the netlify-cms code separately from all its dependencies for caching purposes?