[changelog] Indentation is not preserved for GitHub releases on Linux

I'm using a fixed changelog message template when releasing and announcing to GitHub and Discord.
It looks for example like this:
🚀 {{projectName}} {{projectVersion}} has been released

If you have already installed {{projectName}} and have updates enabled,
this update will eventually be automatically installed when launching it the next time.

You can get the standalone version here: {{releaseNotesUrl}}

{{#rawChangelog}}
Changes in {{version}}
{{{rawChangelog}}}
{{/rawChangelog}}

where the raw changelog is supplied via the jreleaser environment, and it works fine.
However, I noticed that when the raw changelog contains indents, e.g.
- Hello
  - World

the GitHub release body drops the indents, resulting in
- Hello
- World

This happens only when the tasks are run on Linux. When releasing on a Windows machine, the indents are preserved.
I also tried to normalize the line endings to \n, but that doesn't help.

If understood correctly the value of rawChangelog is set as an environment variable by you? Does the raw changelog also contain special characters such as quotes?

I set it like this (note my attempt to normalize the line endings):
environment {
    properties.put('rawChangelog', file("changelogs/${canonicalVersion}.md").exists() ?
            file("changelogs/${canonicalVersion}.md").text.replace('\r\n', '\n') : "")
}

In my test case the content was literally just
- Hello
  - World

Thanks. I've had a quick look and environment properties are added to the template context "as is" -> https://github.com/jreleaser/jreleaser/blob/1d3f651392e60c22e29f85a5f580e8db61ef9745/core/jreleaser-model-impl/src/main/java/org/jreleaser/model/internal/JReleaserModel.java#L467
Could you do me a favor and wrap the content of the whole raw changelog with double exclamation at both ends? that is "!!" + rawchangelogText + "!!".

I think I didn't highlight it enough in the initial message, but the problem only exists for GitHub Releases changelogs. Everything works fine on discord, even though the content of the changelog and template is identical.

Furthermore, this issue only occurred when I switched my GitHub actions runners from Windows to Linux.

I see. What configuration do you have in place for the changelog in the release?

This is the relevant release configuration:
release {
    github {
        repoOwner = 'xpipe-io'
        name = 'xpipe-app'
        overwrite = true
        tagName = '{{projectVersion}}'
        releaseName = '{{tagName}}'
        token = proj.hasProperty("XPIPE_GITHUB_TOKEN") ? proj.property("XPIPE_GITHUB_TOKEN") : System.getenv("XPIPE_GITHUB_TOKEN")

        files = true
        artifacts = true
        checksums = true
        signatures = false

        prerelease {
            enabled = isPreRelease
            pattern = '.*-pre'
        }

        changelog {
            enabled = true
            formatted = 'ALWAYS'
            contentTemplate = file('misc/github.tpl')
        }
    }
}

github.tpl:
{{#rawChangelog}}
## Changes in {{version}}
{{{rawChangelog}}}
{{/rawChangelog}}

## Downloads

If you have already installed X-Pipe, this update will eventually be installed automatically.
In any other case you can download it from here:

### Installers

Installers are the easiest way to get started. They come with the automatic updater feature. The following installers are available:

- [Windows Installer](https://github.com/xpipe-io/xpipe-app/releases/download/{{version}}/xpipe-installer-windows-{{version}}.msi)
- [Linux .deb Installer](https://github.com/xpipe-io/xpipe-app/releases/download/{{version}}/xpipe-installer-linux-{{version}}.deb)
- [Linux .rpm Installer](https://github.com/xpipe-io/xpipe-app/releases/download/{{version}}/xpipe-installer-linux-{{version}}.rpm)
- [MacOS .pkg Installer](https://github.com/xpipe-io/xpipe-app/releases/download/{{version}}/xpipe-installer-mac-{{version}}.pkg)

### Standalone

If you don't like installers, you can also use a portable version, which is packaged as an archive:

- [Windows Portable](https://github.com/xpipe-io/xpipe-app/releases/download/{{version}}/xpipe-portable-windows-{{version}}.zip)
- [Linux Portable](https://github.com/xpipe-io/xpipe-app/releases/download/{{version}}/xpipe-portable-linux-{{version}}.tar.gz)
- [MacOS Portable](https://github.com/xpipe-io/xpipe-app/releases/download/{{version}}/xpipe-portable-mac-{{version}}.dmg)

I created this configuration a while ago and wanted to look up what the formatted = 'ALWAYS' setting does, but the documentation is very vague about it.

Your recommendation of wrapping the content with !! actually fixed the problem, at least the indentation is right. Now if I could remove the !! from the output, that would be nice.

What is the course of action here? Is this behavior intended? If so, is there any way to remove the !!, as the result currently looks as follows: https://github.com/xpipe-io/xpipe-app/releases/tag/<IP_ADDRESS>

Nevermind, it seems like it didn't change the formatting at all. Only the way GitHub displays lists made it seem like there was an indentation. But the raw result for the GitHub release looks as follows:
## Changes in <IP_ADDRESS>
!!- Hello
- World!!

## Downloads

If you have already installed X-Pipe, this update will eventually be installed automatically.
In any other case you can download it from here:

### Installers

Installers are the easiest way to get started. They come with the automatic updater feature. The following installers are available:

- [Windows Installer](https://github.com/xpipe-io/xpipe-app/releases/download/<IP_ADDRESS>/xpipe-installer-windows-<IP_ADDRESS>.msi)
- [Linux .deb Installer](https://github.com/xpipe-io/xpipe-app/releases/download/<IP_ADDRESS>/xpipe-installer-linux-<IP_ADDRESS>.deb)
- [Linux .rpm Installer](https://github.com/xpipe-io/xpipe-app/releases/download/<IP_ADDRESS>/xpipe-installer-linux-<IP_ADDRESS>.rpm)
- [MacOS .pkg Installer](https://github.com/xpipe-io/xpipe-app/releases/download/<IP_ADDRESS>/xpipe-installer-mac-<IP_ADDRESS>.pkg)

### Standalone

If you don't like installers, you can also use a portable version, which is packaged as an archive:

- [Windows Portable](https://github.com/xpipe-io/xpipe-app/releases/download/<IP_ADDRESS>/xpipe-portable-windows-<IP_ADDRESS>.zip)
- [Linux Portable](https://github.com/xpipe-io/xpipe-app/releases/download/<IP_ADDRESS>/xpipe-portable-linux-<IP_ADDRESS>.tar.gz)
- [MacOS Portable](https://github.com/xpipe-io/xpipe-app/releases/download/<IP_ADDRESS>/xpipe-portable-mac-<IP_ADDRESS>.dmg)


Fix bug where foo = False did not trigger Y015

cc. @sobolevn
Came up in https://github.com/python/typeshed/pull/7058

Typeshed PR here: https://github.com/python/typeshed/pull/7060


python311Packages.python-roborock: 0.30.2 -> 0.30.3

Diff: https://github.com/humbertogontijo/python-roborock/compare/refs/tags/v0.30.2...v0.30.3
Changelog: https://github.com/humbertogontijo/python-roborock/blob/v0.30.3/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

5 packages built:

home-assistant-component-tests.roborock
python310Packages.python-roborock
python310Packages.python-roborock.dist
python311Packages.python-roborock
python311Packages.python-roborock.dist


⚠ Bofrost.lu has degraded performance

In 7ea8f38, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1007 ms

Resolved: Bofrost.lu performance has improved in afd5496 after 38 minutes.


Login failed for user '' - connection lost after a period of time

Issue Type: Bug

Connect to database hosted on Azure SQL Database using Azure Active Directory - Universal with MFA Support. This works successfully - I'm able to query the database as expected. (Making this a different issue to https://github.com/microsoft/azuredatastudio/issues/10298, I think.)
Leave the Azure Data Studio tab for a certain amount of time (I'd struggle to say how long - at most ~an hour rather than days), then try running a query.
Query fails with the following message:

Msg 18456, Level 14, State 233, Line 1
Login failed for user '<token-identified principal>'. Token is expired.

I have to reconnect in order to run the query.
What I would have expected to happen: Azure Data Studio refreshes tokens when they expire, saving me from erroring and having to reconnect
Azure Data Studio version: azuredatastudio 1.32.0 (4a45ba7cf20dd4129f1a08e5e776dfb33e3d1d1e, 2021-08-16T18:08:28.086Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz (8 x 1896)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.82GB (1.40GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

import
Mic
1.3.1

azdata-sanddance
msr
3.3.0

vscode-todo-highlight
way
1.0.4

Closing as a duplicate of #10352 - there's an open PR right now to fix this issue for query editors : #16936


Add an utility: in-place string replacement

This utility is necessary for #274

-1

+1. Just one small nit.

LGTM

Squashed and merged in ac46512b05cc859b87634c8413e785fefd181263


ORGANISM tag in GBK input & conda

Hi @cbertell @bkm - thanks for developing this tool - it seems great! I'm giving it a try on some of my MAGs and was confronted with the fact that my prodigal-generated GBK files were apparently incomplete. After correcting this using pyrodigal, I was then confronted with the lack of an ORGANISM field, which isn't relevant in my case. I wrote a python script to quickly go around this, but then was left wondering if it wouldn't be possible to remove this requirement and accept 'incomplete' prodigal-generated GBK input? I think this is a golden-standard tool used by a significant fraction of the metagenomics community for example, which will benefit from this tool.
Additionally, I noticed zDB uses conda to generate its environments during the NextFlow run - maybe using mamba could improve the run time of the tool?
Hope this is relevant & helps you! Thanks in advance!

Quick follow-up on this as it's conda-related - I can't run the webapp command as it can't create the conda environment. Could you look into this as well please?
$ zdb webapp --conda --name=MG1_zdb_270923
Building conda environment...
Failed to build conda environment, you can check conda_log for details

Just taking time to try out a couple different things - all works for me if I change conda to mamba in [this line](https://github.com/metagenlab/zDB/blob/d9069abbc92e60236a5fbe645ed1030ca6eaab2c/bin/zdb#L354) (having already installed mamba in the zdb environment...

Hi @GeoMicroSoares
The gbk field ORGANISM is not required if you add a column name in the sample file to label your input files.
Prodigal gbk outputs do not contain any sequences, which is the main reason why we cannot use them as input for zDB. It would probably be possible to take the original fasta file + the prodigal gbk file as input. We could also provide a script to generate complete gbk records from incomplete prodigal outputs.
We are aware of the fact that some environments are difficult to install with conda, this is one of the the reasons why we recommend using docker or singularity. Switching to mamba is probably a good idea.
Thank you for your feedback!

I'm closing this issue as it is really old and you seemed OK with the answer given.


[ACM] Create a kustomize function to remove namespace from cluster scoped CRs

As described in kubernetes-sigs/kustomize#2498 a problem right now is that kustomize will apply the namespace transform to cluster scoped custom resources. As a result we end up setting namespace on certain cluster scoped resources. ACM doesn't allow this.
Related to kubernetes-sigs/kustomize#2498
Related to #4  Deploy with ACM

Prototype in kubeflow/kfctl#335

Following: https://googlecontainertools.github.io/kpt/reference/fn/run/#declaratively-run-one-or-more-functions
The next steps are to make this configurable using a "client side" CRD resource. This way we can just list whatever resources we need to strip the namespace from.

I'm getting the error:
caip-fl-bp   KNV9999: metadata.annotations must be a map

When trying to apply the latest manifests for Kubeflow using ACM.


Bring back ViewComponentTagHelpers for new Razor

We removed this for the initial OOB VSIX release because we didn't have code gen that supported it. Now that we do, we need to re-add the logic.

385e2523a9242313e3ab26843d2b39350a495c67


Configuration to run in a docker container

This adds a Dockerfile to build the application and install ffmpeg so it can be run in a container. I have also updated the readme and added an example configuration for docker compose.
Inside the container the application is run as a non-priviledged user, so I have added some cli arguments to make it possible to work around any permission problems that may arise due to that:
--file-permissions (or -fp) and --directory-permissions (or -dp) to specify which mode is used to create files and directories.
In addition I also added another option --temp-directory (or -td) to specify a directory for temporary files which solves #175 for me.
Disclaimer: This is the first time I did anything with go, so please excuse if I made any obvious mistakes in the code. It compiles and runs fine though, so hopefully everything should be ok.

I'm not accepting commits to add Docker support directly into this repo. See https://github.com/Kethsar/ytarchive/pull/100#issuecomment-1200085624
If you make it so only changes regarding the new options are added, I'll be willing merge after testing it if it works.

Fair enough. I've created a new pull request for them. See #179 .

You could still add a short note to the readme regarding your stance though. I did look through the issues, but missed the pull request since github didn't include them in the search and I didn't actually expect there to be one.


Lando.Lando version 3.10.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.4 schema?

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

Microsoft Reviewers: Open in CodeFlow

@microsoft-github-policy-service agree

/azp run

Validation is failing with an installer error:

2023-01-25 20:34:52.720 Message box (OK):
Access violation at address 76B8FC8E in module 'ucrtbase.dll'. Read of address 03199FCC.

Close with reason: Stale pull request;


Ale on vim 7 fails silently

On Vim 7.4, Ale does not work but neither does it produce any error messages, causing the unfortunate user to spend hours trying to investigate why it is loading but not working at all.
The situation is not helped by the installation instructions having a "Installation on Vim 8" section (3.i) followed by what appears to be "Installation on previous versions of Vim" sections (3.ii, 3.iii).
I have now, much later, discovered that there is such a thing as Vim 8, and that Ale apparently requires it.

https://github.com/w0rp/ale/blob/daecbad543c68de1c0a2d8c368e4edde2f90461e/plugin/ale.vim#L27 ALE tells you to upgrade your editor if you run the script and don't have the required features.

The README says the same.

The whole point of my issue report is that it does not tell you to upgrade your editor. You might have code to that effect, but if so, it does not work.

Okay then. If anyone has any suggestions, feel free to create a pull request.

Thanks @jribbens for reporting this. I too spent an hour understanding why ALE didn't appear on my vim command line. Finally realized from the help docs that it required vim>8.0 (but failed silently - no warning when installed using pathogen). @w0rp perhaps it's worth putting out an error for older vim versions?
For others facing this, just upgrade to vim>8.0 using these simple steps.


setNetwork function similar to connect

We have our own custom wallet connector modal using the adapter.  We have an issue on our public testnet where when a user has their wallet set to mainnet, we have no way of helping them switch their wallet to testnet.  The user must manually set their wallet to testnet, then try to connect to our dapp again.
It would be great if we could show users a prompt with a button to swap networks.  This would also be useful for projects to do the opposite (ie a wallet is set to testnet but the user is trying to access the mainnet page).
There is a helper network() that shows the network.  I think it would be helpful if there was a function like setNetwork(chainId || NetworkName).

Agreed! Take a look at the new wallet standard we are about to follow from now on, especially the  aptos:changeNetwork feature

That looks like the perfect fit, thanks for the response.  Looking forward to this standard.  Happy to help work on the Aptos Wallet Adapter when the AIP is finalized!


HDR mezzanine

There is an interest in creating test content for static and dynamic HDR. That in turn needs mezzanine content that is in HDR.
@haudiobe provided the following links on possible content.
In 3GPP, we collected a database of content including HDR and SDR.
Details on the sequences can be found in TR 26.955 here: https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3741
The sequences can be accessed here: https://dash-large-files.akamaized.net/WAVE/3GPP/5GVideo/ReferenceSequences/. All sequences include copyright statements and metadata.
An overview of the sequences are provided here: https://dash-large-files.akamaized.net/WAVE/3GPP/5GVideo/ReferenceSequences/sequences.csv
@rbouqueau mentioned the following;
The HDR sequences from Netflix I talked about:
https://opencontent.netflix.com/
It was also mentioned that Ateme and Harmonic may be able to generate (dynamic) HDR from SDR.

Initial HDR10 mezzanine streams have been generated and can be found here:
https://dash-large-files.akamaized.net/WAVE/Mezzanine/development/2024-01-02/
Files (each with corresponding JSON):
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Based on updated HEVC test vector sparse matrix here (now including cud1, clg1, chd1 in addition to chh1):
https://docs.google.com/spreadsheets/d/1Bmgv6-cfbWfgwn7l-z0McUUI1rMjaWEwrN_Q30jaWk4/edit?usp=sharing
They are based on the Netflix Sol Levante asset found here (CC BY 4.0) - thanks to Romain for mentioning them:
http://download.opencontent.netflix.com.s3.amazonaws.com/SolLevante/hdr10/SolLevante_HDR10_r2020_ST2084_UHD_24fps_1000nit.mov
http://download.opencontent.netflix.com.s3.amazonaws.com/SolLevante/imf/SolLevante_IMF_DolbyVision_PQP3D65_UHD_24fps/CPL_0a207596-a0f5-458a-811e-a97a4286d00c.xml
Next steps:

Create HLG10 mezzanine streams using HLG source of EBU Croatia sequence.
Resolve issues found with HDR10 streams if any.
Create remaining missing HDR10 streams (including those for splicing tests: A1 / AD-A1 labelled streams).
Update mezzanine scripts for HDR metadata handling (ST2086, MaxFALL, MaxCLL) - initial streams have been generated using some hardcoded values.
Add dynamic metadata to HDR10 mezzanine streams (e.g. ST2094-10, ST2094-40).


useTreeData update method causing infinite loop

🐛 Bug Report
The tree.update method from useTreeData hook is causing some kind of infinite loop.
Context
I was trying to build a tree component using the useTreeData hook from @react-stately/data package, where you can expand and collapse sections with children. I was using an expanded property on an item to track the state.
🤔 Expected Behavior
Expected the expand / collapse to work by updating the expand property on the value of an item in the tree using tree.update method provided.
😯 Current Behavior
When using tree.update to toggle the expanded state of a node. It works as expected for the first time but after that if you try to expand or collapse any node it goes into some kind of infinite loop (the UI freezes and crashes).
💻 Code Sample
Codesandbox that reproduces the bug - https://codesandbox.io/s/react-stately-usetreedata-fws7j
How to reproduce?
Click on any of the folder icon in the tree to expand / collapse a composite node, the first action will behave as expected. Then, try to expand / collapse any of the node again and the UI will freeze.

Software
Version(s)

@react-stately/data
3.1.0

Browser
Chrome Version 85.0.4183.121 (Official Build) (64-bit)

Operating System
macOS Catalina

I was able to reproduce this in the useTreeData test, need to dig into what is happening.

I believe it is because of this line<EMAIL_ADDRESS>Should be parentKey: oldNode.parentKey, infinite loop was happening because of the self referential parentKey causing updateTree to keep looping over the same node
Gonna double check locally.

Hey @LFDanLu, I can give it a try. I was anyway planning to monkey-patch over the weekend for my sideproject.
Will be willing to make a PR if it's still unassigned.

Hey @drenther did you still want to give this a try? It has not been picked up yet.

@LFDanLu i can confirm parentKey: oldNode.parentKey is the fix locally.
I can pick this up add some tests and do a PR if that is oki.

@LFDanLu i can confirm parentKey: oldNode.parentKey is the fix locally.
I can pick this up add some tests and do a PR if that is oki.

@razvanip Absolutely, that would be great!

@razvanip Absolutely, that would be great!


Added FixedSizeList wrappers

Requires corresponding changes to the spec pythonizer.

Should we go with Arrray? (It's what Golang uses. Also see this comment.)

Should we go with Arrray? (It's what Golang uses. Also see this comment.)

I disagree with this notation. Many, if not the majority of, languages seem to deem Array to be dynamically sized. [Source]

That table is pretty cool. It looks like it's roughly 50/50 (what they call "init" and "heap" is a special case of fixed sized).

Agreed. My point is more that the terminology may be ambiguous to users of certain languages. (A quick poll of the 3 CS majors in the room with me had them all declaring it to be dynamic. (I am aware this is not a strong argument))

If we want clarity, the name needs to evoke the property that actually make static and dynamic sized lists different. List vs tuple, array vs slice, list vs array all fail to do that.
I'll keep thinking for better alternatives...

Ideas: Mutable List vs Immutable list. Or appendable list vs fixed list. Or list vs vector.
Honestly I think it's better to keep it simple and be clear in the definition of the type itself.
Slice vs Array is clear enough for me, and so is List vs Tuple.

If one-word-ness is a desideratum then list vs vector is definitely the least bad of what I've seen so far.

+1 for list vs vector. Happy to rename "tuple" to "vector" in the SSZ spec.


Use SVG lines in panel to better match map trail paths

@shua123 Thoughts? I replaced the css borders we were using in the panel to better match look of the trail paths on the map. They are now all SVG. I positioned them so dotted/dashed lines were optimized for the desktop panel width (on mobile the varied width means they may stop short or get cut off on the right side).
desktop:

mobile:

trailhead.js:
https://github.com/smartchicago/trailsy/blob/gh-pages/js/trailhead.js#L2683
CSS:
https://github.com/smartchicago/trailsy/blob/gh-pages/styles/css/newguts.css#L186

Looks good


Diversity Support

🏻 U+1F3FB
🏼 U+1F3FC
🏽 U+1F3FD
🏾 U+1F3FE
🏿 U+1F3FF
http://unicode.org/reports/tr51/#Diversity

done in #22.


hlo.md.txt

Your pull request seems good, but must be checked by a human maintainer for the following reason(s):

Your file is not in a project folder ("Friends", "Games"). This may be intentional, but most likely not.

Please be patient until a maintainer has time to look over your contribution.
This is an automated response, beep boop.
if you think there is a mistake, contact a maintainer

511c6226fc133393152e44911e30bf4994005cc7

This follows none of the week1 rules but is clearly a submission for week1, try again.


Unhandled Rejection (TypeError): Cannot read property 'json' of undefined

I can access the home page fine, and then when I click "go to annotator," the page loads for about 1 second before displaying this error:
  551 | var result = this.getImageToAnnotate(this.props.annotation_table).then(imageToAnnotate => {
  552 |   this.setNewImageState(imageToAnnotate);
  553 | }).catch(error => {
> 554 |   error.response.json().then(reason => {
      | ^  555 |     log("Setting blank image state")
  556 |     this.setBlankImageState()
  557 |     this.setState({ 'errorCause': reason["detail"] })

Download the React DevTools for a better development experience: https://fb.me/react-devtools
Consts.js:5 SERVER_HOST: localhost
Consts.js:6 APP_HOST: localhost
index.js:1452 Warning: The tag <h> is unrecognized in this browser. If you meant to render a React component, start its name with an uppercase letter.
    in h (at Annotator.js:94)
    in header (at Annotator.js:93)
    in div (at Annotator.js:92)
    in Annotator (created by RouterContext)
    in div (at App.js:6)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router (at src/index.js:14)
console.<computed> @ index.js:1452
index.js:1452 Warning: Invalid DOM property `class`. Did you mean `className`?
    in button (at Annotator.js:102)
    in div (at Annotator.js:98)
    in div (at Annotator.js:92)
    in Annotator (created by RouterContext)
    in div (at App.js:6)
    in App (created by RouterContext)
    in RouterContext (created by Router)
    in Router (at src/index.js:14)
console.<computed> @ index.js:1452
ImgBlock.js:22 eventListeners added
2:5678/api/get_image_to_annotate?annotation_table=player_bbox:1 Failed to load resource: the server responded with a status of 500 (Internal Server Error)
annotator:1 Access to fetch at 'http://localhost:5678/api/get_image_to_annotate?annotation_table=player_bbox' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
ImgBlock.js:554 Uncaught (in promise) TypeError: Cannot read property 'json' of undefined
    at ImgBlock.js:554
webpackHotDevClient.js:120 ./src/components/annotator/FieldLinesImgBlock.js
  Line 1:     'React' is defined but never used                   no-unused-vars
  Line 1:    'Component' is defined but never used               no-unused-vars
  Line 2:    'vizserverURI' is defined but never used            no-unused-vars
  Line 5:     'eps' is assigned a value but never used            no-unused-vars
  Line 95:   'segmentIndex' is already defined                   no-redeclare
  Line 96:   Expected '!==' and instead saw '!='                 eqeqeq
  Line 150:  Expected '===' and instead saw '=='                 eqeqeq
  Line 164:   'activeSegment' is assigned a value but never used  no-unused-vars
  Line 203:  Expected '===' and instead saw '=='                 eqeqeq
  Line 213:  'doLog' is assigned to itself                       no-self-assign
  Line 234:  Expected '!==' and instead saw '!='                 eqeqeq
  Line 262:  'isPoint1' is assigned a value but never used       no-unused-vars
  Line 454:  'i' is already defined                              no-redeclare
  Line 477:  Expected '===' and instead saw '=='                 eqeqeq
  Line 489:  'lseg' is already defined                           no-redeclare
printWarnings @ webpackHotDevClient.js:120
webpackHotDevClient.js:120 ./src/components/annotator/PlayerBboxImgBlock.js
  Line 1:     'React' is defined but never used          no-unused-vars
  Line 1:    'Component' is defined but never used      no-unused-vars
  Line 2:    'imgRootPath' is defined but never used    no-unused-vars
  Line 2:    'vizserverURI' is defined but never used   no-unused-vars
  Line 5:     'eps' is assigned a value but never used   no-unused-vars
  Line 7:    'log' is defined but never used            no-unused-vars
  Line 218:  'doLog' is assigned to itself              no-self-assign
  Line 254:  'isTl' is assigned a value but never used  no-unused-vars
  Line 365:  Expected '===' and instead saw '=='        eqeqeq
  Line 377:  'rect' is already defined                  no-redeclare
printWarnings @ webpackHotDevClient.js:120
webpackHotDevClient.js:120 ./src/components/annotator/GameplayStateImgBlock.js
  Line 1:    'React' is defined but never used                   no-unused-vars
  Line 1:   'Component' is defined but never used               no-unused-vars
  Line 2:   'fieldLinesNames' is defined but never used         no-unused-vars
  Line 2:   'vizserverURI' is defined but never used            no-unused-vars
  Line 5:    'eps' is assigned a value but never used            no-unused-vars
  Line 7:   'log' is defined but never used                     no-unused-vars
  Line 36:   'toChangeState' is assigned a value but never used  no-unused-vars
  Line 84:  'i' is already defined                              no-redeclare
printWarnings @ webpackHotDevClient.js:120
webpackHotDevClient.js:120 ./src/components/annotator/ImgBlock.js
  Line 203:   'rect' is assigned a value but never used                                                                  no-unused-vars
  Line 205:   'img' is assigned a value but never used                                                                   no-unused-vars
  Line 229:   'rect' is assigned a value but never used                                                                  no-unused-vars
  Line 230:   'img' is assigned a value but never used                                                                   no-unused-vars
  Line 344:   'context' is assigned a value but never used                                                               no-unused-vars
  Line 464:  Expected '===' and instead saw '=='                                                                        eqeqeq
  Line 474:  Expected '===' and instead saw '=='                                                                        eqeqeq
  Line 491:  Expected '===' and instead saw '=='                                                                        eqeqeq
  Line 510:  Expected '===' and instead saw '=='                                                                        eqeqeq
  Line 551:   'result' is assigned a value but never used                                                                no-unused-vars
  Line 570:  Expected '===' and instead saw '=='                                                                        eqeqeq
  Line 596:   'result' is assigned a value but never used                                                                no-unused-vars
  Line 599:  Expected '===' and instead saw '=='                                                                        eqeqeq
  Line 631:  Expected '!==' and instead saw '!='                                                                        eqeqeq
  Line 635:  'result' is assigned a value but never used                                                                no-unused-vars
  Line 684:  img elements must have an alt prop, either with meaningful text, or an empty string for decorative images  jsx-a11y/alt-text
printWarnings @ webpackHotDevClient.js:120
webpackHotDevClient.js:120 ./src/index.js
  Line 3:  'Route' is defined but never used       no-unused-vars
  Line 3:  'Link' is defined but never used        no-unused-vars
  Line 3:  'IndexRoute' is defined but never used  no-unused-vars
printWarnings @ webpackHotDevClient.js:120
webpackHotDevClient.js:116 There were more warnings in other files.
You can find a complete log in the terminal.
printWarnings @ webpackHotDevClient.js:116


[BUG] Make the tests run successfully on my local machine

I used to be able to run cargo test and have everything succeed on my local machine. I can't seem to do that anymore when on the main branch. So I will be doing a git bisect to figure out what changed to make this happen and fix that change.

Okay I finally figured it out. Having an old or wrong version of the default executor causes very non obvious failures. That was the issue.


Deleting a project/feedsource/feedversion should also delete respective namespaces in SQL database

 Issue by evansiroky
Monday Oct 29, 2018 at 23:27 GMT
Originally opened as https://github.com/catalogueglobal/datatools-server/issues/120

Currently, they do not delete the namespaces in the SQL database which results in unnecessary storage space being consumed.

See https://github.com/conveyal/gtfs-lib/issues/78


Update jackson-dataformat-yaml to 2.18.0

About this PR
📦 Updates com.fasterxml.jackson.dataformat:jackson-dataformat-yaml from 2.16.2 to 2.18.0
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.fasterxml.jackson.dataformat", artifactId = "jackson-dataformat-yaml" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.fasterxml.jackson.dataformat", artifactId = "jackson-dataformat-yaml" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #190.


Duplicate deletion

Because of network slow. delete context.messageQueue;  invoke twice 。
https://github.com/binance-exchange/node-binance-api/blob/2caa181daec8b7f01d3ac315edf9940fd98ca618/node-binance-api.js#L1673
https://github.com/binance-exchange/node-binance-api/blob/2caa181daec8b7f01d3ac315edf9940fd98ca618/node-binance-api.js#L1683

Thank you. This has been merged. Great work!!

Available in v0.7.2


feat: built-in library

Closes partially #433
Summary of Changes

Add the built-in library from the old Xtext version
Load in into the VS Code workspace

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

Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


Filesystem header not very portable

The recent commit bc5b562 and the ones before introduced functions from the header filesystem and filesystem namespace.
Unfortunately, filesystem header and namespace are not compatible with gcc 8 on windows (and that's what I am using). I tested the program while temporarily removing all the filesystem lines and it worked fine. I added them back for now in the include-pdb-input branch I was working on.
I will have to see if I can move to gcc 9 which seems to support filesystem on windows. Otherwise, we might have a problem with portability of the program.
It's already the second OS compatibility problem we have (see issue #27 ).
We should probably see how to limit such problems in the future as it causes unnecessary loss of time to find workarounds (which could end up being to revert back to previous compatible code). So before introducing new headers, library dependencies, etc, I would suggest to check whether they are fully compatible with Windows 10 (+7 ideally), Linux and macOSX.

I agree. I did actually check whether filesystem was compatible and I found conflicting information. [Articles like this(https://www.codingame.com/playgrounds/5659/c17-filesystem) say:

With C++17 there’s a nice improvement: for example, we now have the standard filesystem!

So I just decided to try it, I figured you'd tell me if it didn't work. In regards to this issue the fix is pretty simple. It's possible to sacrifice some security by simply using std::strings for the path comparison, and leaving out the check for changed files. In that case, there would be an issue if the user decided to change the file and start the calculations without reimporting the files manually. That's a pretty minor issue though.
The website I linked writes:

Depending on the version of your compiler you might need to use std::experimental::filesystem namespace.

GCC: You have to specify -lstdc++fs when you want filesystem. Implemented in <experimental/filesystem>.

Do you want to try that?

It's already the second OS compatibility problem we have

I would exchange the "already" with "only". Honestly, designing a program that works cross-platform is no easy task and we likely will have to handle some work arounds unless we want to severely limit the features.

So I just decided to try it, I figured you'd tell me if it didn't work. In regards to this issue the fix is pretty simple. It's possible to sacrifice some security by simply using std::strings for the path comparison, and leaving out the check for changed files. In that case, there would be an issue if the user decided to change the file and start the calculations without reimporting the files manually. That's a pretty minor issue though.

I would go for that solution. The file change while running the program and not reimporting is just an extreme case scenario involving very bad computer practice.

The website I linked writes:

Depending on the version of your compiler you might need to use std::experimental::filesystem namespace.

GCC: You have to specify -lstdc++fs when you want filesystem. Implemented in <experimental/filesystem>.

Do you want to try that?

I tried briefly, didn't work. My compiler (gcc 8 on windows 10) didn't even find experimental/filesystem header.

It's already the second OS compatibility problem we have

I would exchange the "already" with "only". Honestly, designing a program that works cross-platform is no easy task and we likely will have to handle some work arounds unless we want to severely limit the features.

I agree that two is not many but it would be better if we can limit future incompatibilities as much as possible in "working" builds. (since I found these incompatibilities in the master branch while previous versions were fully compatible)

Apparently C++20 will include a portable filesystem. Maybe this solve this issue?

So I just decided to try it, I figured you'd tell me if it didn't work. In regards to this issue the fix is pretty simple. It's possible to sacrifice some security by simply using std::strings for the path comparison, and leaving out the check for changed files. In that case, there would be an issue if the user decided to change the file and start the calculations without reimporting the files manually. That's a pretty minor issue though.

I would go for that solution. The file change while running the program and not reimporting is just an extreme case scenario involving very bad computer practice.

Alright, I'll change it then.

So, I tested with the newer version of gcc 9.2 which supports filesystem on windows.
While filesystem functionalities were recognized and didn't cause any error when compiling with the flag -std=c++17 (required for filesystem header in gcc 9.2), new compilation errors arose.
It seems that wxWidgets 3.0.5 that we are using has compatibility issues when using the flag -std=c++17.
Thus, we would need to either
(i) tweak wxWidgets 3.0.5,
(ii) move to a newer version of wxWidgets if one version fixes this issue (didn't check), or
(iii) simply forget about filesystem functionalities and remove the flag -std=c++17 for compilation.
I vote for solution 3 which will make everything simpler and more portable.

Why do you need to compile wxWidgets with the -std=C++17 flag? Have you tried compiling it with the -std=C++11 flag, but then compiling our software with the -std=C++17 flag?

PS: I haven't tested solution (ii):

(ii) move to a newer version of wxWidgets if one version fixes this issue (didn't check)

It might be simple to try if there is no compatibility issue with the wxWidgets features we already implemented in our program.
Since we only used very simple features, I suppose we could move to a newer version.

I have now tested the newest version of wxWidgets: https://www.wxwidgets.org/news/2020/07/wxwidgets-3.1.4-released/
Our code is almost compatible with wxWidgets 3.1.4 (only had few errors easily fixed, see detail below). Some new dependencies require to link more libs.
The errors mainly concern

the function SetCellValue which went from SetCellValue(value, row, column) to SetCellValue(row, column, value)
adding sizers to wxBoxSizer(wxHORIZONTAL). The wxALIGN_RIGHT flag becomes unnecessary because the last sizer will be on the right anyway so there is an error during run time. (we only had three such occurrences in our code, so easily fixed)

And most importantly, the flag -std=c++17 works on windows 10. I could build wxWidgets libraries with this flag and then compile our program code with it. The header <filesystem> is also compatible.
Now, the obvious solution would be to move to wxWidgets 3.1.4 but before doing so, we need to consider few points:

wxWidgets 3.1.x is not yet the official latest stable version. It is still officially version 3.0.x
I checked everything on windows 10 but we need to make sure that everything runs smoothly on macOSX and linux.

So @jmaglic and @BSVogler , I'll make a branch for my stable code running with wxWidgets 3.1.4, before going any further for anything else, could you try to build wxWidgets 3.1.4 on your side and compile the code from this branch, please?

Can we not just rely on the wxwidget binaries? I did not compile wxwidgets myself and only installed the binaries via brew. The binaries are provided on the download section.

Can we not just rely on the wxwidget binaries? I did not compile wxwidgets myself and only installed the binaries via brew. The binaries are provided on the download section.

I didn't try myself but from what I read, it was always recommended to build wxWidgets on your system to make sure that everything would work properly. Another issue with pre-build binaries is that your program will need them and won't run if you don't have them on the system (such as a random user):

Please note that during run-time the executables will require wxWidgets DLLs in addition to MSVC run-time DLLs, so you should consider adding the directory containing these DLLs to your PATH and either distributing them with your application or instructing your users to download them.

I built them as static (SHARED=0 flag when building wxWidgets) so the executable will be completely independent.

This works for me on Mac. Can we merge and revert the previous merge to include the filesystem header?

This works for me on Mac. Can we merge and revert the previous merge to include the filesystem header?

You mean the filesystem header only or all functions related to filesystem?
In the later case, I would first like to have your opinion on the "compartmentalized file loading and calculation" branch that deal with all potential issues without having to rely on filesystem.

To conclude: the use of the filesystem library is not necessary right now, but may be used in future since it poses no compilation issue. We use the C++17 standard and WxWidgets 3.1.


Added Sleep as Android icon (closes #24)

@patrykmichalik Done.

Thanks for contributing, @hardeik!


Replaced question.md issue-template with contact_links to StackOverflow

Also disables use of blank-issue-template:

Thanks!

Seems I config.yaml should be renamed to config.yml #4920

Not sure if its now working?

@snakefoot maybe we should also update the support link on nlog-project.org? (Or perhaps split it)


21Vianet?

What is up with the reference to 21Vianet on this page in the menu?

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

ID: 1feb89e6-c5e0-693e-425e-8fd8b0198001
Version Independent ID: 7b683879-67a9-299a-73e9-6e3654846fdf
Content: Set up file storage and sharing - Microsoft 365 admin
Content Source: microsoft-365/admin/setup/set-up-file-storage-and-sharing.md
Service: o365-administration
GitHub Login: @SKjerland
Microsoft Alias: sharik

@cwidhelm Thank you for your feedback. We are working with the author to find out and fix the Menu.
Thanks
Sri

@msbema I believe @cwidhelm is asking why "Office 365 operated by 21Vianet is showing up in the left nav (TOC). This issue isn't specific to this article, as that navigation is displayed for every article on the site. It should only display when "Office 365 operated by 21Vianet (China)" is selected in the Version drop-down list. I will investigate this and try to resolve it. However, this more a nuisance than a content issue, so I'm closing this.
@cwidhelm  Thank you for bringing this to our attention.


Add option to override 'Host' header

This is useful when querying IPs directly, especially in load-balancer or testing scenarios.

hi @nh2
Looks good to me,
can you update the readme with the new flag as well? or even describe the use case and usage.

@Lusitaniae ah sorry, I had missed the first message. Thanks for documenting it in bb0dfc1973bb5c62beb9cb7327c052357fea7d14 !


net: if: net_if_set_link_addr: Mention lifetime for address buffer

This function just stores the buffer pointer passed, so explicitly
mention that the buffer must remain valid while netif itself is
valid. For example, it can't be stored stored on stack.
Signed-off-by: Paul Sokolovsky<EMAIL_ADDRESS>

in your commit message: stored is written 2 times.

Fixed, thanks.


Accordion / Nav Element - highlight currently selected menu item

I'm using a combination of Accordion and Nav, like in the Spectre.css docs.
What would be the best way to highlight the currently selected menu item in an accordion menu? I found this example with a combination of :focus and tabindex, but wasn't sure how to implement it in spectre css:
https://stackoverflow.com/questions/17479912/how-to-change-link-color-when-clicked

You could add an active class on user click and style the <li>, or whichever html tag you use inside the accordion, in your css as a highlight

Thanks a lot candacej97. Understood! I'll give it a try with my complicated navigation.

Still struggling with this. It would be great if there was a solution that would dynamically add the class "active" to the currently active menu item / anchor, also when scrolling the page.

Dynamic solutions would involve Javascript.
For the click event, you could use
function onLinkClick(e) {
  e.target.classList.append('active');
}

and add the function name to an event listener on the anchor from the menu item
and for the scroll event (code from https://www.w3schools.com/jsref/event_onscroll.asp)
function addActiveClass() {
    if (document.body.scrollTop > 50 || document.documentElement.scrollTop > 50) {
        document.getElementById("myP").className = "test";
    } else {
        document.getElementById("myP").className = "";
    }
}
window.addEventListener("scroll", addActiveClass);

if you have a jsfiddle you can put your code on there to show what exactly you currently have

Thanks so much, Candace. I will check this as soon as i find the time to work on this again.


Uppercase first character

@ldhnam From pull request #47, title format change to "Vi du ...". So first character of title should be lowercase like "Ví dụ ứng dụng thời gian thực với deepstreamHub".
In my opinion, we should close this pull request.


Add IBC representation of the NEOK token

Follow up of this PR https://github.com/cosmostation/chainlist/pull/538.

@stamper-dev sorry for sounding pushy, is there anything you need from us to merge the PR? 🙇

Dear @vrde
For double check your PR
is your request asset CW20?
If that please PR this file
instead of this

For double check your PR is your request asset CW20?

Our token is both an ERC20 and an IBC coin. We made a proposal to the EVMOS chain for that, see https://app.evmos.org/governance?id=144

If that please PR this file instead of this

In did that, see https://github.com/cosmostation/chainlist/pull/538, it's referenced in the description of this PR.
Our token is both an ERC20 and an IBC coin.

@stamper-dev :partying_face: :confetti_ball:


Bipartite graphs on Networkit

I am working with a huge bipartite graph, and the calculation of the projections is computationally very demanding. On the cluster I usually use Networkit, which of course is much more efficient than anything else when you have a lot of cores at your disposal, but I couldn't find any algorithm or function related to bipartite graphs. So I had to stick to the networkx.algorithms.bipartite module, but if I specify even a simple function for the calculation of the weights to be used in the projections with the bipartite.generic_weighted_projected_graph() function, the (quite powerful) cluster I am using simply won't make it.
Are you planning on extending Networkit to bipartite graphs? Is there any function or algorithm that already exists that maybe I missed?

There are no special arrangements so far for handling bipartite graphs more efficiently than ordinary graphs.
Two questions would clarify your request for me: What do you want to compute exactly? Why can't it be done with what is already there?

I'm closing this as no further info about the issue was provided. Please comment if you want it reopened.


feat: remove using namespace std in header files.

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

晚点有空的时候我检查并合并下


migrated to Helm 3

Signed-off-by: Sebastien Dionne<EMAIL_ADDRESS>Migration to Helm 3 format

Moved dependancies into Chart.yaml
bump apiVersion to v2

It looks like @survivant hasn't signed our Contributor License Agreement, yet.

The purpose of a CLA is to ensure that the guardian of a project's outputs has the necessary ownership or grants of rights over all contributions to allow them to distribute under the chosen licence.
Wikipedia

You can read and sign our full Contributor License Agreement here.
Once you've signed reply with [clabot:check] to prove it.
Appreciation of efforts,
clabot

[clabot:check]

@confluentinc It looks like @survivant just signed our Contributor License Agreement. :+1:
Always at your service,
clabot

no troubleI forgot that one
I'll do that.

@gAmUssA I updated the readme to reflect changes to Helm 3 and I updated Prometheus and Grafana link (stable/xx) repos are deprecated.

@survivant could you rebase changes from master?
also, I tested it locally on gcp and everything seems to work.

still waiting to be merge

@gAmUssA Can you please merge this?


ping output search is wrong on ping.py 50th line re.search('(\d+) packets transmitted, (\d+) packets received', line)

Fixed via pull request https://github.com/CiscoZeus/don/pull/21


Remove version: ChilliBits.Spice version 0.12.1

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/spicelang/spice/releases/download/0.12.1/spice_x64_setup.msi
Status Code: 200
(Automated message - build 857)


Don't copy extension assets to project root

When you render to quarto-preprint, the .svg files get copied to the project root.

Hi @mvuorre what you think about directly defining svg in the  template files? Laprepint is defining orcid in a file https://github.com/LaPreprint/typst/blob/c908cd05da8e13eb8add652a613d00add73d1f58/lapreprint.typ#L50

I think it would be sweet. I did not do this for two reasons:

Unsure if it works in .docx (that doesn't really matter tho)
Not sure if/how to implement the psyarxiv et cetera logos. Might just deprecate those in favor of simplifying this...

If someone is using project yml someone can delete those files as postprocessing, it will not work for files not included to the project
project:
  title: "Quarto preprint"
  render:
    - index.qmd
  output-dir: docs
  post-render: rm  orcid.svg psyarxiv.svg

execute:
  cache: true
 ```


Add About / Credit Page

Should have an about page containing your info, github project, and credit to libraries and Todoist API

As a curious user, I want an about/credits page so that I can see who made this project, learn how to contribute/view the code, and see the credits.


#2 - Fix new message shows every time add new message

Details

This is the 2nd attempt of https://github.com/Expensify/App/pull/44724.
Fixed Issues

$ https://github.com/Expensify/App/issues/43486
PROPOSAL: https://github.com/Expensify/App/issues/43486#issuecomment-2162491991
Tests

Same as QA Steps

[x] Verify that no errors appear in the JS console

Offline tests

Same as QA Steps
QA Steps

A.

Open a chat with long message history
Send a chat
Verify there are no "New messages" banner shows

B.

[User A] Invite User B to a workspace
[User B] Open workspace switcher
[User B] Click on the invited workspace. (This will open the workspace chat for the first time)
[User B] Verify the chat doesn't auto-scroll to top
[User B] Verify the skeleton loader disappears once chat is loaded

C. (web/desktop only)

Sign out
Log in
Verify a report is shown after the app loading is completed

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/50919443/723909fc-d75d-43b9-ab92-6cd5780cce67

Android: mWeb Chrome

https://github.com/Expensify/App/assets/50919443/e11bf1fe-fc49-4d92-aa04-1c6ae6e3ce86

iOS: Native

https://github.com/Expensify/App/assets/50919443/bf59b678-6206-45f2-bc19-6eeef4e29bb0

iOS: mWeb Safari

https://github.com/Expensify/App/assets/50919443/12a4fb21-600f-428c-93cb-7da133ae827e

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/50919443/be3b4680-cd82-46b5-bdf9-e3692e2ae5f2
https://github.com/user-attachments/assets/2427a5d3-c86a-4f46-bd76-afe6adecf4e6
https://github.com/user-attachments/assets/a8fa44c4-db78-4441-b885-1cc9f81a62fc

MacOS: Desktop

https://github.com/Expensify/App/assets/50919443/e094ffc9-267b-4ade-ab01-6e7dfe449b16

Holding on https://github.com/Expensify/App/pull/45494

@rayane-djouah thanks!
@shubham1206agra ready for review

Done

Hm I can't reproduce the original issue anymore, was this fixed somewhere else somehow?

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by https://github.com/Beamanator in version: 9.0.15-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by https://github.com/roryabraham in version: 9.0.15-9 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


unable to download the Myo-SDK

The link on github as well as the link on https://myo-python.readthedocs.io/en/latest/index.html this page for downloading the SDK don't exist any more. Could somebody release the SDK again?

Hi @monicaYang , you can download the SDK from the GitHub releases page: https://github.com/NiklasRosenstein/myo-python/releases/tag/v1.0.4


sht_get_configured_sht_address definition missing for Linux userspace driver

Hi, I'm trying to compile the driver for the Linux User Space.
However, I've ran into an issue about the sht_get_configured_sht_address() function in the hw i2c implementation.
It's not defined in any place. What should I do? Hard-code the device address (for instance, for the SGP30 should be 0x58 right?)? Or I'm missing something?

Hi @cocus, thanks for reporting. The Linux Sample implementation is based on the generic SHT driver, we'll need to fix this. To get you up and running without having to wait for us you can however apply the following quickfix:
diff --git a/hw_i2c/sample-implementations/linux_user_space/sensirion_hw_i2c_implementation.c b/hw_i2c/sample-implementations/linux_user_space/sensirion_hw_i2c_implementation.c
index 68eccb4..af6ea48 100644
--- a/hw_i2c/sample-implementations/linux_user_space/sensirion_hw_i2c_implementation.c
+++ b/hw_i2c/sample-implementations/linux_user_space/sensirion_hw_i2c_implementation.c
@@ -52,7 +52,7 @@
 #define I2C_READ_FAILED -1

 static int i2c_device = 0;
-static u8 sht_address = 0;
+static u8 sgp_address = 0;

 /**
  * Initialize all hard- and software components that are needed for the I2C
@@ -66,11 +66,11 @@ void sensirion_i2c_init()
         return;
     }

-    /* get sht address of used sensor */
-    sht_address = sht_get_configured_sht_address();
+    /* get sgp address of used sensor */
+    sgp_address = sgp_get_configured_address();

     /* open specific device */
-    ioctl(i2c_device, I2C_SLAVE, sht_address);
+    ioctl(i2c_device, I2C_SLAVE, sgp_address);
 }

 /**
@@ -85,7 +85,7 @@ void sensirion_i2c_init()
  */
 s8 sensirion_i2c_read(u8 address, u8* data, u16 count)
 {
-    if (sht_address != address) {
+    if (sgp_address != address) {
         return I2C_READ_FAILED;
     }

@@ -108,7 +108,7 @@ s8 sensirion_i2c_read(u8 address, u8* data, u16 count)
  */
 s8 sensirion_i2c_write(u8 address, const u8* data, u16 count)
 {
-    if (sht_address != address) {
+    if (sgp_address != address) {
         return I2C_WRITE_FAILED;
     }

Thanks!
By the way, what do you think about doing the ioctl() call that sets the I2C Slave address in the read and write methods?
Because you already have the address of the device as an argument. By doing this, you won't need to specify the sensor address in a "hardcoded" way (using sht_get_configured_sht_address()), and allows you to use 2 of the same kind sensors (in two addresses on the same bus, on the same app).

Thanks for the suggestion, that sounds like what we need. I'll look into it. It'll probably still be at least a week though.. I'll keep the issue open until it's fixed.
Cheers

Pending review and merge, you're welcome to try out this commit:
https://github.com/Sensirion/embedded-common/pull/5/commits/49e7d0e18561c105aa77816b37abbfb0ff27966d

Thanks, it works perfectly! So I'm closing this ticket.


Implement get_default_database (Fix #198)

Add a simple implementation of MongoClient.get_default_database. It always returns the same database __DEFAULT__ specified by the class field MongoClient.DEFAULT_DB.
This would be more accurately implemented by using pymongo.uri_parser.parse_uri (docs) to parse the default database from the URI if the MongoClient was created with a URI and otherwise throw an error if not.
I did not use this approach because I wanted to get some feedback on the best approach for how to do that since I'm guessing we do not want to add pymongo as a dependency.
From pymongo:
def get_default_database(self):
    if self.__default_database_name is None:
        raise ConfigurationError('No default database defined')

    return self[self.__default_database_name]

I would actually prefer if the implementation would behave as much as possible as the pymongo code itself. That means that it should raise a ConfiguartionError in the way you described it above (if the MongoClient has not been initialised with a proper URL). I'm aware that that would imply the necessity to implement at least a simple URI parser (but maybe the urllib2.urlparse.urlparse already does most of the job).

@mdomke agreed. I went back through and re-implemented it. However instead of using urllib2.urlparse.urlparse I tried to replicated the pymongo code as much as possible without bringing over any unnecessary complexities (so all the parsing and testing only focuses on the database, the only component of the URI which is currently used).
For the uri_spec testing I wanted to directly copy the pymongo spec tests to ensure a full spec testing (to ensure any valid URI is parsed valid) and allow easy expansion of tests in the future. Much of the test specification is unused however since only the database is parsed out.
I hope this is more appropriate. I would be happy to make any changes or additions that you see fit.

@sm11963 thank you very much for your effort!


Improve the links of previous team section

Looks bad right now

claim

closed https://github.com/abhishekshree/spo-website/commit/c8110f145a379b8ebb09d64bea7bc6d2c3cf4632


[WIP] add api to extend root partition of  volume

we cann't rely on cloud-init to extend root partition when the partition is on a multipath disk. So add a new API in this PR to do the extention of guest root volume, by punching a script to the target guest.

The script has been tested on RHEL7 and RHEL8. But This API is not ready yet.
Commiting first to get review comments.
@bjhuangr @jichenjc pls provide some comments on whether you think this API is acceptable. Thanks.

Two overall comments:
* If we plan to provide the API to extend the partition, why not resize files system in the same API?

Don't want to introduce too many regression issue. For ECKD/FBA they are done in unpackdiskimage, too much effort for me to contain this change at this period.

* suggest to generate the gpartvol.sh script in zvmsdk/dist.py , to make it easier support other linux distro

OK. I will make change. Current script is compatible for RHEL7 & 8.

Two overall comments:
* If we plan to provide the API to extend the partition, why not resize files system in the same API?

Don't want to introduce too many regression issue. For ECKD/FBA they are done in unpackdiskimage, too much effort for me to contain this change at this period.

I'm fine that just extend partition in this PR, add resize file system in future changes. For long term, it's better to get rid of cloud-init dependency.

what's the position and future of cloud-init and those scripts ?
I mean do we want to remove cloud-init totally (for disk part)? or just want to add this as add on for cloud-init feature that didn't cover?
and this API will only be called when VM startup (run once and only once) , correct?

what's the position and future of cloud-init and those scripts ?
I mean do we want to remove cloud-init totally (for disk part)? or just want to add this as add on for cloud-init feature that didn't cover?
and this API will only be called when VM startup (run once and only once) , correct?

In my opinion, it looks strange that expend partition in zvmguestconfigure, while resize file system in cloud init. We had this discussion before, that have agreement that zcc support bu not rely on cloud init, which means zcc's main activate engine is zvmguestconfigure, but also support consumers like openstack to utilize cloud init to do further configurations.

ok, works for me

Two overall comments:
* If we plan to provide the API to extend the partition, why not resize files system in the same API?

Don't want to introduce too many regression issue. For ECKD/FBA they are done in unpackdiskimage, too much effort for me to contain this change at this period.

I'm fine that just extend partition in this PR, add resize file system in future changes. For long term, it's better to get rid of cloud-init dependency.

Sorry that I misunderstood your comments, now the resize2fs is also added in the script.

Function tested with driver changes, for both RHEL7.8 and RHLE8.1


Add a 'mbed compile --debug' command

It's hard to figure out how to do a debug build using mbed CLI, instructions differ between mbed OS 2.0, 5.0/5.1, 5.2+... mbed CLI should have a command to make such a build.
FYI, here are the instructions:

If using mbed 2.0, include -o debug-info in your workspace_tools/build.py and workspace_tools/make.py commands to build with debug symbols.
If using mbed 5.1, add -o debug-info to your mbed compile command.
If using mbed 5.2+, add --profile mbed-os/tools/profiles/debug.json to your mbed compile command.

I think as of 5.3, we simplified it a bit so you can just do --profile debug. Do you think this is enough?

@bridadan But that only works for 5.3... We should have a standard way of doing this across all versions of mbed OS.

@bridadan But that only works for 5.3... We should have a standard way of doing this across all versions of mbed OS.

What do you suggest? The way to go are profiles. This was a breaking change, and a replacement for old -o options that were not much clear what they do.

@0xc0170 Sure, but I think making debug builds is such a common action that we should add it to mbed CLI. Suggestion:
mbed build --debug

Which magically sets some stuff in mbed 2, builds with the right -o in mbed OS 5.2 and lower, and with the debug profile in mbed OS 5.3.

I see what you're saying @janjongboom, though there's a part of me that doesn't want to treat debug as "special" even though it is such a common operation.
@screamerbg do you have any thoughts on this?

I'll second @bridadan. @janjongboom I'll close the issue as there wasn't any activity for some time, but please reopen or create new with proposal how this could work as a workflow.
@BlackstoneEngineering


Control Center can't get fingerprint from Subutai Console

Control Center can't get fingerprint from Subutai Console, which cause Peer state not ready, however it's working and you even register it to the Bazaar
logs from CC

[16:10:37] [../hub/src/RestWorker.cpp(296)] Info: "Getting finger from 9999" (in function bool CRestWorker::peer_finger(const QString&, QString&))
[16:10:37] [../hub/src/RestWorker.cpp(869)] Critical: Send request network error : Connection refused (in function QByteArray CRestWorker::send_request(QNetworkAccessManager*, QNetworkRequest&, int, int&, int&, int&, QByteArray, bool))
[16:10:37] [../hub/src/RestWorker.cpp(311)] Debug: Http code  0 Error code  6 Network Error  1 (in function bool CRestWorker::peer_finger(const QString&, QString&))

Environment:

Distributor ID:	Debian
Description:	Debian GNU/Linux 9.4 (stretch)
Release:	9.4
Codename:	stretch

Bridged Interface for the Peer:

enp3s0

Where this bug came from: Peer doesn't become ready for a long time, so when I registered peer from localhost, there second peer appeared in "My peers" list and it shows this peer is not on my machine. But first peer still is not ready.

/etc/hosts file was corrupted, fixing it solve the problem.

fixed on prod.


Training on new class/dataset

Hello, thank you for releasing this package. The work is very interesting.
I want to train the network for shape completion on my own data. I have partial and full point-clouds for a large number of samples, but don't understand how the currently supported formats are generated. For example, CRN seems to come as .h5 files.
What is the best way to go from partial and full point clouds (.ply or .obj or other) to the proper input format? After that point I'd presumably run the trainer and point it to my new class choice and dataset location.

I am able to create h5 files now, but it seems like the code makes the assumption that all point clouds are 2048 points in size. Is this true? Is there a way to have variable sizes for each sample? And have different sizes for ground truth and measured?

Hi, thanks for your interest in our work!
You can adapt from data.ply_dataset. PlyDataset. Depends on your canonical frame, you may not need to conduct swap_axis.  You can also write your own dataset as long as you make sure __getitem__ return a tuple of (partial, gt, idx).
You may want to start from pretraining the tree-GAN using your own data (train split), by calling pretrain_treegan.py, where you only need the gt point clouds. Then, you can use your pretrained model to do shape completion on the test split, by calling trainer.py, where you only need the partial point clouds for training, and the gt point clouds are for evaluation and visualization only.
Let me know if you need more help.
Best,
Junzhe

Due to the architecture of  tree-GAN, the generated complete shape is of 2048 points. However, the input partial shape can be of any resolution. You can verify the robustness of k-mask with different resolution of partial shapes, either by modifying the input directly, or specify 'target_downsample_method' in the arguments.

Thank you, I was able to write my own dataset following ply.
Regarding canonical orientation; all I have to do is ensure that the gt and input meshes are oriented in the same way when I generate them and I won't have to reorient when I load the dataset using your package, correct?

@marcusabate yes you are write. If your canonical frame is different from CRN, then you would need to pretrain the tree-GAN on your own.

Hi @junzhezhang, I wanted to pretrain the tree-GAN on the well known ScanNet dataset. Can I directly use the ply_dataset.py file for it, with the dataset_path being the path to the originally downloaded ScanNet dataset form their website?


bug: Tailwind LSP plugin (plugins/extras/lang) ignores provided/custom 'filetypes'

Did you check docs and existing issues?

[X] I have read all the LazyVim docs
[X] I have searched the existing issues of LazyVim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.9.2
Operating system/version
ArchLinux
Describe the bug
If a custom 'filetypes' table is provided for tailwind: e.g.
  {
    "neovim/nvim-lspconfig",
    ---@class PluginLspOpts
    opts = {
      ---@type lspconfig.options
      servers = {
        tailwindcss = {
          filetypes = { "templ" },
        },
      },
    },
  },

then the 'filetypes' is ignored. It appears to be because the included setup function ...
     setup = {
        tailwindcss = function(_, opts)
          local tw = require("lspconfig.server_configurations.tailwindcss")
          --- @param ft string
          opts.filetypes = vim.tbl_filter(function(ft)
            return not vim.tbl_contains(opts.filetypes_exclude or {}, ft)
          end, tw.default_config.filetypes)
        end,
      },

... overwrites the 'filetypes' table with a filtered version of the default filetypes from the lspconfig - in order to filter out 'filetypes_exclude'
Perhaps a setup function along these lines would be a solution:
      setup = {
        tailwindcss = function(_, opts)
          local tw = require("lspconfig.server_configurations.tailwindcss")
          opts.filetypes = vim.list_extend(opts.filetypes or {}, tw.default_config.filetypes)
          --- @param ft string
          opts.filetypes = vim.tbl_filter(function(ft)
            return not vim.tbl_contains(opts.filetypes_exclude or {}, ft)
          end, opts.filetypes)
        end,
      },

Steps To Reproduce
Add the builtin tailwind lsp config and then extend it to have custom 'filetype' table. Notice that this never makes its way through to the LSP config
Expected Behavior
Any added 'filetypes' are appended or prepended to the default list
Repro
No response

I just fixed this and added a filetypes_include option to achieve what you want. Check the diff for more info

Yep, that appears to do the trick - thanks!


interest in arm64 (armv8, aarch64, 64-bit arm) support

Feature request
I'm interested in arm64 support for numba. Before diving in to look at code,
I looked at the issues repository, and found some items related to the Tegra TX2 (e.g. #2849 ) which suggested that the "build from source" option could be useful.

ah, I notice hidden documentation at https://github.com/numba/numba/commit/e1335a44971ae1fbd99ef7d02e2b6ed3dc0bd7ac#diff-918372d20763a54fb1530f1e41e96f4b pending news from @seibert - I'll be patient to see how the referenced dependencies shake out.

Yeah, we've tested Numba on the Jetson TX2 board running Ubuntu 16.04 and confirmed both the CPU and CUDA backends work.  The main obstacle to wider use is a good way to distribute binary packages, since building LLVM from scratch is a pain.  Berryconda is a great conda-based distribution for the Raspberry Pi.  I have a fork of it called Jetconda that we've used to build a very skeleton environment for Numba testing on the TX2 (though I expect the packages to work on any Ubuntu-based ARMv8 board).  It needs more packages, however, and I haven't had time to expand it yet.

There's a few 0.40.0dev0 builds for aarch64 on the Numba channel.
$ CONDA_SUBDIR=linux-aarch64 conda search -c numba numba
Loading channels: done
# Name                  Version           Build  Channel
numba                0.40.0dev0   np111py36_316  numba
numba                0.40.0dev0   np111py36_328  numba
numba                0.40.0dev0   np111py36_331  numba
numba                0.40.0dev0   np111py36_356  numba

these were built against Jetconda on a TX2. They are hugely experimental!

@seibert said

The main obstacle to wider use is a good way to distribute binary packages, since building LLVM from scratch is a pain.

It looks to me like the numba/llvmlite developers do this for x86 and other platforms using automated build scripts and posting the binary wheels to pypi.  But I have found that arm64 build servers are a bit hard to find.  Maybe the system/cloud you use to run the automated builds has no arm64 servers.
Instructions for running this build manually are here but how are the builds run automatically?  I see yaml files that describe how to apply the patches but I'm not sure what uses them.

We use conda-build, which takes the YAML recipe files you see and produces binary conda packages.  We built a very limited fork of the Berryconda for ARMv8 that we're calling Jetconda (because it is built and tested on the Jetson TX2).  Jetconda is not kept very up to date, since we don't currently have the resources to do that, but it does let us confirm that Numba/llvmlite/LLVM work properly on ARMv8.
Due to various limitations of public CI systems (no GPUs, no PPC, no ARM, generally slow hardware), the Numba developers maintain a private build farm at Anaconda that contains one of every supported platform (ARMv7 is handled by a Raspberry Pi 3B+, and ARMv8 is built and tested on the Jetson TX2) and does the final build and test of packages.  We currently use buildbot to launch conda-build when commits are made to the master branch, but in the past we have also used Jenkins for this.  Either way, conda-build is doing all the heavy lifting, regardless of what job scheduler we use.

I made that wheel: llvmlite-0.23.0-cp27-cp27mu-linux_aarch64.whl.  What about posting it?
FWIW, the manual build instructions at https://llvmlite.readthedocs.io/en/v0.23.0/admin-guide/install.html do not include patching instructions and the patches don't work out of the box so it involved some manual cleanup.  If I knew how conda-build applied patches it might have been easier.  And building that llvm monster on a TX2 takes more than an hour.  I applied these patches:
llvm-lto-static.patch
twine_cfg_undefined_behavior.patch
intel-svml.patch
0001-Transforms-Add-missing-header-for-InstructionCombini.patch

@seibert - @nmgeek - If it would help the jetconda effort to have data center grade arm64 servers to run on, please contact me - I run the @worksonarm program at Packet and we have resources specifically to provide CI/CD infrastructure to open source projects for that platform. Specifically we have access to 64-bit Arm machines with 32 or more cores that greatly speed up build cycles for any builds that are even the least bit parallel.

Hi,
Can we compile or use your binary in the NanoPc T4 which is Rockchip 3399 [http://wiki.friendlyarm.com/wiki/index.php/NanoPC-T4]
(http://wiki.friendlyarm.com/wiki/index.php/NanoPC-T4)
what is your suggestion. I have plenty time today and try to compile..
is berryconda can work ?

@MyraBaba Given the cost of trying is quite low, perhaps try with berryconda first (but be aware that it's all 32 bit, so you may need a 32 bit OS or the 32 bit runtime libraries), and if that doesn't work try jetconda. If neither work, it'd be interesting to know what happens and what's on your system!
If you want to build from source, then llvmlite needs building first, this requires a specific build of LLVM, instructions are here: http://llvmlite.pydata.org/en/latest/admin-guide/install.html#building-manually

Starting to compile llvmlite now.. Let you know the situation
Best

On 6 Feb 2019, at 13:46, stuartarchibald<EMAIL_ADDRESS>wrote:
@MyraBaba https://github.com/MyraBaba Given the cost of trying is quite low, perhaps try with berryconda first (but be aware that it's all 32 bit, so you may need a 32 bit OS or the 32 bit runtime libraries), and if that doesn't work try jetconda. If neither work, it'd be interesting to know what happens and what's on your system!
If you want to build from source, then llvmlite needs building first, this requires a specific build of LLVM, instructions are here: http://llvmlite.pydata.org/en/latest/admin-guide/install.html#building-manually http://llvmlite.pydata.org/en/latest/admin-guide/install.html#building-manually
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/numba/numba/issues/3308#issuecomment-460978793, or mute the thread https://github.com/notifications/unsubscribe-auth/AQscn9y-u-elM-7bpXnzvOgrAQLZ9v45ks5vKrJqgaJpZM4WoO6Q.

Update...
I successfully compiled numba . as everybody said yes there is a pain in the ....:)
`>>> import numba

numba.version
'0.43.0dev0+271.g865b87a97'`

now compiling mxnet..

Hi @MyraBaba - is there an update on your progress?

Just tried Ubuntu 20.04 (64bit) on a Raspberry4.
Numba 0.48 is in the 20.04 repository and works like a charm.

Closing the issue as the original issue appears to be resolved, and no further updates have been provided in quite some time.


ci: Test in --release mode and simplify workflow.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
7743

Relevant Lines:
8388

💛  - Coveralls


[WFCORE-6417] Upgrade Jandex to 3.1.2

https://issues.redhat.com/browse/WFCORE-6417

Thanks @bstansberry


[BUG] RuntimeError: Failed to init API, possibly an invalid tessdata path

Traceback (most recent call last):
File "C:\Users\tuna7\AppData\Local\Programs\Python\Python311\Lib\threading.py", line 1038, in _bootstrap_inner
self.run()
File "C:\Users\tuna7\AppData\Local\Programs\Python\Python311\Lib\threading.py", line 975, in run
self._target(*self._args, **self._kwargs)
File "C:\Users\tuna7\Desktop\RokTracker-3.0.0\rok_scanner.py", line 1183, in start_from_gui
scan(
File "C:\Users\tuna7\Desktop\RokTracker-3.0.0\rok_scanner.py", line 883, in scan
governor = governor_scan(
^^^^^^^^^^^^^^
File "C:\Users\tuna7\Desktop\RokTracker-3.0.0\rok_scanner.py", line 452, in governor_scan
with PyTessBaseAPI(path=str(tesseract_path)) as api:
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "tesserocr.pyx", line 1219, in tesserocr._tesserocr.PyTessBaseAPI.cinit
File "tesserocr.pyx", line 1233, in tesserocr._tesserocr.PyTessBaseAPI._init_api
RuntimeError: Failed to init API, possibly an invalid tessdata path: C:\Users\tuna7\Desktop\RokTracker-3.0.0\deps\tessdata

I found a similiar issue posted on the site, but as recommended there tessdata is in deps folder and also the most recent "tessdata-main" folder is with traineddata folders from this link; https://github.com/tesseract-ocr/tessdata

Sorry for the late reply. With version 3 you need a tessdata folder in deps and not tessdata-main (it's also shown in the readme).


Wait-RSJob doesn't sleep

Do you want to request a feature or report a bug?
Both.
What is the current behavior?
Wait-RSJob doesn't sleep between completed job checks in its Do/While loop. So it's probably consuming a lot of CPU needlessly.
What is the expected behavior?
It should probably sleep but I'm not sure for how long. 0.5 - 1s would be fine. Anything is better than what it does now.
Which versions of Powershell and which OS are affected by this issue? Did this work in previous versions of our scripts?
Current but it goes back a while.

I added to Wait-RSJob line 192.
if($WaitJobs){
    Start-Sleep -Milliseconds 500
}

I tested:
Import-Module PoshRSJob -Force; Measure-Command { 1..8 | Start-RSJob { Start-Sleep -Seconds 4 } -Throttle 4 | Wait-RSJob }

Prior to the change CPU on one core jumps to 100%. After the change it idles at 10%. Completion times for the query before and after are the same.
So before any

After a close look at Wait-RSJob I dont like it at all :)
I dont like the -match used in $FilterScript and $FilterScript itself
# Preparation:
$all = 1..100000 | %{  [PSCustomObject]@{ID=$_; Name="Name$_"; Guid=[Guid]::NewGuid().ToString()} }
$wn = 1..50 | %{ Get-Random -Minimum 1 -Maximum 99999 }
$wn = $all[$wn]
$m = '^' + ($wn.Name -join '$|^') + '$'
$wn_name = $wn.Name
$hash = @{}; $wn.Name | %{ $hash[$_] = 1 }
# Measurements:
 C:\> measure-command { $all | ?{ $_.Name -match $m} }
Seconds           : 3
Milliseconds      : 50
C:\> measure-command { $all | ?{ $wn_name -contains $_.Name } }
Seconds           : 3
Milliseconds      : 682
C:\> measure-command { $all | ?{ $hash.ContainsKey($_.Name) } }
Seconds           : 2
Milliseconds      : 675
# !!!!
 C:\> measure-command { $all.where( { $hash.ContainsKey($_.Name) } ) }
Seconds           : 0
Milliseconds      : 870
C:\> measure-command { foreach ($a in $all) { if ( $a.Name -match $m ) { $a } } }
Seconds           : 0
Milliseconds      : 648
 C:\> measure-command { foreach ($a in $all) { if ( $wn_name -contains $a.Name ) { $a } } }
Seconds           : 1
Milliseconds      : 245
C:\> measure-command { foreach ($a in $all) { if ( $hash.ContainsKey($a.Name) ) { $a } } }
Seconds           : 0
Milliseconds      : 293

Last is the absolute winner!
so code should looks like
$hash = @{}
# collect $hash like collect $list now, set $property
# [...]
# and filter like
$jobs = foreach ($job in $PoshRS_jobs) {
   if ($Hash.ContainsKey($job.$property)) {
     $job
   }
}

If i have a time today I write it :)

Wait-RSJob still needs a sleep.

Leave a comment


fix(generate): parse input_tokens from api

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.001%) to 97.114%

Totals

Change from base Build<PHONE_NUMBER>:
0.001%

Covered Lines:
2591

Relevant Lines:
2668

💛  - Coveralls


The payment amount should be adjusted in the test mode only for the bank card payment option (both 3D Secured and not 3D Secured), and should not be adjusted for other payment options (PayPal, POLi Payments, etc.)

#17 (The last 3 digits of every payment amount should be «000» in the test mode for Westpac)

It need to be clarified: [AlphaCommerceHub] Should a payment amount be adjusted in the test mode for some other payment options besides bank cards (both 3D Secured and not)?

The question is answered, so I am starting to implement this task.

Implemented in 0.7.0.


Chrisda to Master

Docs Build status updates of commit f0403d8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-HostedOutboundSpamFilterPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/New-LabelPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-HostedOutboundSpamFilterPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-LabelPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

sharepoint/sharepoint-ps/sharepoint-online/Set-SPOTenantSyncClientRestriction.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[Mbed] Update Mbed platform implementation

Problem
Update the Mbed platform port to be compatible with the new version of the CHIP stack implementation
Change overview

Fix Mbed examples debugging issue

Add user access to openocd in VSCode Docker file
Update the arm toolchain path in launch.json
Update path to server setting name and set the correct value
for cortex-debug extension in launch.json

Autonomous connection status for network commissioning

Add NetworkStatusChangeCallback service in the network
commissioning driver
Add last disconnect reason with getter and setter
Implement OnNetworkStatusChange function

Fix key-value builder issue

Key value must not include some specific characters in Mbed
They will be replaced by '-' sign

Update configuration manager implementation

Add reboot count, uptime, and total operational hours keys
Implement get/set reboot count functions
Implement get/set reboot total operational hours
Improve init function - add generic class initalization
Testing
Build and run mbed examples

 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.Artur Tynecki seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Set up one-click image

Closes #38.

Similarly to https://github.com/hpi-swa-lab/SqueakByExample-english/pull/104#issuecomment-827118574. I have cleaned up all  noisy releases that were created for debugging purposes with the help of the following snippet:
client := WebClient new
	token: githubOauthToken;
	yourself.

releases := Json readFrom: (client httpGet: 'https://api.github.com/repos/hpi-swa-lab/squeak-inbox-talk/releases') content readStream.

releases do: [:release | self assert: (client httpDelete: 'https://api.github.com/repos/hpi-swa-lab/squeak-inbox-talk/releases/' , release id do: [:req | req headerAt: 'Authorization' put: 'token ', client token]) isSuccess]


Add assertArrayCountEqual, which checks if two containers have the same elements

Unlike assertCountEqual, the two contaners can include numpy arrays. This is useful for integration and end-to-end tests where you want to pass through PCollections with different element types, including numpy arrays.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---

---
---

Java

Python

---

---
---

Pre-Commit Tests Status (on master branch)

---
Java
Python
Go
Website

Non-portable

Portable
---

---
---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

retest this please

R: @udim

Now that the assertArrayCountEqual method is much shorter, do you think it still makes sense to have it in an external file, or should I just copy-paste it into the two places where I use it?

@udim Now that the assertArrayCountEqual method is much shorter, do you think it still makes sense to have it in an external file, or should I just copy-paste it into the two places where I use it?

I believe it still makes sense to have a reusable module.


Improve zookeeper

Support for zookeeper with prometheus monitoring
Support zookeeper backup and restore

resolve https://github.com/apecloud/kubeblocks/issues/5649

@wangyelei

It seems that the monitor is also not working.


MeasurementService should provide more guidance about moving version number to the .serviceconfig file

Bug Report
If the service specifies the version number in code but not in the serviceconfig file, the discovery service assumes that the service is unversioned and assigns it a default version number. If this doesn't match, calling the measurement service from TestStand will fail.
From @nick-beer

Yeah - in fact, passing the a version to the constructor is problematic if it is not also found in the .serviceconfig file.  We should probably update the service.py code to enforce this.  The problem is as follows:

You specify a version in your constructor, but not in your .serviceconfig file.
When the service is published to plugin library or statically installed, the DiscoveryService thinks the service is unversioned - because there's no version in the .serviceconfig file.
As a result, it registers it internally with a default version (used to be 1.0.0, but as of last night, it's now 0.0.1)
However, when the service starts itself and registers itself with discovery service, it uses this version that's passed in the constructor, and those versions don't match.  This means DiscoveryService fails to see this as a valid registration/resolution, and the client is left hanging, waiting for that valid registration.

...
I think an appropriate fix is to allow the following and raise an error for anything else:

No version specified in either the constructor or serviceconfig.  This will just get the default version
No version specified in the constructor, but a version specified in the serviceconfig.
A version specified in the constructor, and that same version is specified in the serviceconfig

If someone has an existing service with a version in the constructor (effectively all services), they'll be required to make some kind of change when updating SDK versions.  This is unfortunate, but because DiscoveryService reads the .serviceconfig file to get version information, I'm not sure how else to get around it.

See this PR discussion for more details:
https://github.com/ni/measurement-plugin-python/pull/907#discussion_r1769231913
AB#2863530

In addition to @nick-beer's suggestions, I think it would be reasonable to emit a DeprecationWarning:
if version:
    warnings.warn("The 'version' parameter is deprecated. Specify the version in the .serviceconfig file instead.", DeprecationWarning)

The test failure looks like flakiness in one of the new client cancellation tests:
================================== FAILURES ===================================
____ test___streaming_measurement_execution___cancel___cancels_measurement ____

measurement_plugin_client_module = <module 'test_measurement_client.py' from 'C:\\Users\\ec2-user\\AppData\\Local\\Temp\\pytest-of-unknown\\pytest-5\\measurement_plugin_client_files7\\test_measurement_client.py'>

    def test___streaming_measurement_execution___cancel___cancels_measurement(
        measurement_plugin_client_module: ModuleType,
    ) -> None:
        test_measurement_client_type = getattr(measurement_plugin_client_module, "TestMeasurement")
        measurement_plugin_client = test_measurement_client_type()

        with pytest.raises(grpc.RpcError) as exc_info:
            with concurrent.futures.ThreadPoolExecutor() as executor:
                measure = executor.submit(lambda: list(measurement_plugin_client.stream_measure()))
                measurement_plugin_client.cancel()
>               measure.result()
E               Failed: DID NOT RAISE <class 'grpc.RpcError'>

C:\actions-runner\1\_work\measurement-plugin-python\measurement-plugin-python\packages\generator\tests\acceptance\test_streaming_measurement_client.py:96: Failed

I filed #910