Add ListBlock comparison class to avoid rendering to HTML

Final implementation of #9623.

Please check the following:

[ ] Do the tests still pass?[^1]
[ ] Does the code comply with the style guide?

[ ] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Would you be able to take a look at this @gasman? Unfortunately I did too much of it to be able to review the work myself

Merged in 28a78a6e52f79d4375ba8035813118a92727b031


Generic support has trouble with arrays

Given the following example:
<?php declare(strict_types=1);

/** @template Magic */
class Foo {

	/** @var Magic */
	protected $magic;

	/** @param Magic $magic */
	function __construct( $magic ) {
		$this->magic = $magic;
	}

	/** @param Magic[] $in
	  * @return Magic */
	function unbox( $in ) {
		return reset( $in );
	}

	/** @return Magic */
	function magic() {
		return $this->magic;
	}

	/** @return Magic[] */
	function magicRay() : array {
		return [ $this->magic ];
	}

}

class Bar {

	function baz() {
		echo "baz\n";
	}

}

$foo = new Foo( new Bar );
$foo->magic()->baz();
$foo->unbox( [ new Bar ] )->baz();
foreach ( $foo->magicRay() as $bar )
	$bar->baz();

Phan reports:
$ phan generic3.php
generic3.php:42 PhanTypeMismatchArgument Argument 1 (in) is \Bar[] but \Foo::unbox() takes \Magic[] defined at generic3.php:16
generic3.php:44 PhanUndeclaredClassMethod Call to method baz from undeclared class \Magic

It seems like the support for generics is not yet able to detect when a template type name is being used as an array, whether for a parameter or return value, and it treats the name as referring to an undeclared class instead.
Is this something it would be possible to add?  If so, how would one go about it?
Thanks!

This is probably possible to add - see src/Phan/Language/Type.php , src/Phan/Language/Type/GenericArrayType.php , and src/Phan/Language/Type/TemplateType.php
I'm not sure how complicated it is to implement, I don't use this feature as much as other maintainers. It may end up being simple.
If it's complicated, this is related to https://github.com/etsy/phan/issues/522
I also thought about something somewhat related for static methods, in https://github.com/TysonAndre/phan/issues/10 (Didn't work on implementing it)

This is somewhat gauche, but I've added templated array support in my own static analysis tool.
The only thing that doesn't work is the /** @return Magic[] */, which needs to be rewritten as /** @return array<Magic> */ to work.

Other things to note:
After this issue was filed, ArrayShapeType was added to Phan's type system (e.g. array{fieldName:T} where T is a template)


Own "arguments" and "caller" properties of non-strict functions don't observe the invariability of nonconfigurable, nonwritable properties

Only tested in a stable Edge release. Please confirm.
According to ES6 <IP_ADDRESS> Invariants of the Essential Internal Methods:

     If a property P is described as a data property with Desc.[[Value]] equal to v and Desc.[[Writable]] and Desc.[[Configurable]] are both false, then the SameValue must be returned for the Desc.[[Value]] attribute of the property on all future calls to [[GetOwnProperty]] ( P ).

Testcase against Function#arguments
function f() { return Object.getOwnPropertyDescriptor(f, 'arguments'); }
Object.getOwnPropertyDescriptor(f, 'arguments');
// value: null, writable: false, configurable: false
f();
// value: Arguments[], writable: false, configurable: false

Testcase against Function#caller
function g() { return Object.getOwnPropertyDescriptor(g, 'caller'); }
function h() { return g(); }
Object.getOwnPropertyDescriptor(g, 'caller');
// value: null, writable: false, configurable: false
h();
// value: function h(), writable: false, configurable: false

Suggested fix: Use getters.

@claudepache is this pending spec change?

@claudepache @bterlson Since many implementations differ here, and there's the ongoing discussion linked above, it's not clear what the desired/spec'd behavior should be exactly.

Since it wasn't clear and I just skimmed that whole issue looking for some kind of resolution, the only relevant point is here:
https://github.com/tc39/ecma262/issues/562#issuecomment-221396833
The current implementation violates the current spec.

Not something that is worth picking up in 1.4.1

Some work has been done in the area of caller/arguments that may have partially or completely resolved this issue. Please verify there is still an issue.


ErrorException: "Creating default object from empty value" in config

Go to "more" in the settings page and click "Save my modifications, I accept the Risk!"  No property for dropboxKey.

    System Information
    ------------------
    Lychee Version:  3.2.13
    DB Version:      040000
    System:          Linux
    PHP Version:     7.2
    MySQL Version:   5.7.25-0ubuntu<IP_ADDRESS>
    Imagick:         1
    Imagick Active:  1
    Imagick Version: 1687
    GD Version:      2.2.5

    Config Information
    ------------------
    version:                 040000
    checkForUpdates:         1
    sortingPhotos_col:       takestamp
    sortingPhotos_order:     ASC
    sortingAlbums_col:       description
    sortingAlbums_order:     DESC
    imagick:                 1
    skipDuplicates:          1
    small_max_width:         0
    small_max_height:        360
    medium_max_width:        1920
    medium_max_height:       1080
    lang:                    en
    layout:                  0
    image_overlay:           1
    image_overlay_type:      exif
    default_license:         none
    compression_quality:     90
    full_photo:              1
    deleteImported:          1
    Mod_Frame:               0
    Mod_Frame_refresh:       30000
    landing_page_enable:     0
    landing_owner:
    landing_title:
    landing_subtitle:
    landing_facebook:
    landing_flickr:
    landing_twitter:
    landing_instagram:
    landing_youtube:
    landing_background:
    thumb_2x:                1
    small_2x:                0
    medium_2x:               0
    site_title:              Lychee v4
    site_copyright_enable:   1
    site_copyright_begin:    2019
    site_copyright_end:      2019

@ildyria  I've made a monky patch to the backend API.
https://github.com/LycheeOrg/Lychee-Laravel/pull/181

yup saw it. Thanks. :)


doc: update README.md to notice the user about RisingWave's usage of Scarf

A few examples of other open source projects using similar communication:

https://github.com/apache/superset/wiki/Superset-Third‐Party-Dependencies
https://github.com/ngx-lottie/ngx-lottie
https://github.com/apache/sedona/blob/c878485ef7f5941baa2871d6f0cc03b782e41a5c/docs/asf/telemetry.md?plain=1
https://github.com/search?q="https%3A%2F%2Fscarf.sh%2F"+language%3AMarkdown&type=code&l=Markdown

Our telemetry communication:
https://docs.risingwave.com/docs/current/telemetry/#how-to-opt-out

There is a Notes on telemetry section below already.

There is a Notes on telemetry section below already.

RisingWave collects anonymous usage statistics to better understand how the community is using RisingWave. The sole intention of this exercise is to help improve the product. Users may opt out easily at any time. Please refer to the user documentation for more details.

Telemetry is not our only usage of Scarf. We also track user IP from docker download link (pending CNAME change from our network infra provider) as well as various website pages visits. For this reason I think it may be more appropriate to put the notice at a higher level location.


V0.2 vm scheduling decision event

Description

Fix the data preparation bug.
Add frame index into decision event (payload).

Linked issue(s)/Pull request(s)

issue_number

Type of Change

[ ] Non-breaking bug fix
[x] Breaking bug fix
[x] New feature
[ ] Test
[ ] Doc update
[ ] Docker update

Related Component

[ ] Simulation toolkit
[ ] RL toolkit
[ ] Distributed toolkit

Has Been Tested

OS:

[ ] Windows
[ ] Mac OS
[ ] Linux

Python version:

[ ] 3.6
[ ] 3.7

Key information snapshot(s):

Needs Follow Up Actions

[ ] New release package
[ ] New docker image

Checklist

[ ] Add/update the related comments
[ ] Add/update the related tests
[ ] Add/update the related documentations
[ ] Update the dependent downstream modules usage

Codecov Report

Merging #257 (0a43b20) into v0.2 (d51b192) will decrease coverage by 0.07%.
The diff coverage is 8.33%.

@@            Coverage Diff             @@
##             v0.2     #257      +/-   ##
==========================================
- Coverage   64.31%   64.24%   -0.08%
==========================================
  Files         111      111
  Lines        5411     5417       +6
==========================================
  Hits         3480     3480
- Misses       1931     1937       +6

Flag
Coverage Δ

unittests
64.24% <8.33%> (-0.08%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...mulator/scenarios/vm_scheduling/business_engine.py
17.94% <0.00%> (-0.30%)
:arrow_down:

maro/simulator/scenarios/vm_scheduling/common.py
51.42% <50.00%> (-1.52%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d51b192...0a43b20. Read the comment docs.

Codecov Report

Merging #257 (0a43b20) into v0.2 (d51b192) will decrease coverage by 0.07%.
The diff coverage is 8.33%.

@@            Coverage Diff             @@
##             v0.2     #257      +/-   ##
==========================================
- Coverage   64.31%   64.24%   -0.08%
==========================================
  Files         111      111
  Lines        5411     5417       +6
==========================================
  Hits         3480     3480
- Misses       1931     1937       +6

Flag
Coverage Δ

unittests
64.24% <8.33%> (-0.08%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...mulator/scenarios/vm_scheduling/business_engine.py
17.94% <0.00%> (-0.30%)
:arrow_down:

maro/simulator/scenarios/vm_scheduling/common.py
51.42% <50.00%> (-1.52%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d51b192...0a43b20. Read the comment docs.


Enable debug logging of signature verification

This is a request from @pmeulen so that debugging is easier when Response signature verfication fails.

[ ] Inject the logger rather than pass in method call.

poke @rjkip

Added log message, anything else?

To me it's weird that a signature verification, if successful, ends with the message 'attempting to use each for verification', instead of 'yay it workstest'

See this line for the statement about attempting verification of the signature with key X, and this line that notifies that the signature was verified (3 lines lower it logs when it could not verify). So you get:

log about extracting keys
log how many keys found, filtering X509
log how many X509 keys found, attempting to verify
for each key:

log attempting to verify with key X, detailing key contents
if success: log Signature Verified => exit with return true
if fail: log signature not verified

endforeach: log signature could not be verified with any of the keys => exit with return false

Duplicating that the signature was verified right after the message that the signature was verified which is right after the message detailing the key with contents is redundant imho.

As an aside: the requester was already very happy with what was logged :wink:

I have yet to wake up properly. I agree with you. :+1: Ship it.


Application has a custom icon

Create and add an icon to use for the application.

added in https://github.com/eklynx/SimForeflightLink/pull/10


Can i consult this artical to config helm to work over https

Formerly i used linkerd and ingress to config https for a web application . Now i tried to deploy this web application by helm. But can i consult this article to config with helm to work over https.

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

ID: ada58160-dc50-b977-d3bc-65f92406e16d
Version Independent ID: 5c596e04-fddb-effe-3b72-575f4df42d4e
Content: Create an HTTPS ingress with Azure Kubernetes Service (AKS) cluster
Content Source: articles/aks/ingress-tls.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@cuongdnv
Thanks for your feedback! We will investigate and update as appropriate.

@cuongdnv I don't see why this would't work. Are you doing any tests and having issues?

No , i want to use this article to config with helm to work over https

Got it. I am not sure if this is possible.
@iainfoulds @seanmck can either of you comment further?

This isn't specific to this doc or using AKS, but yes, you can configure Helm to use TLS - https://helm.sh/docs/using_helm/#enabling-tls
The Helm docs (https://helm.sh/docs/) and GitHub repo (https://github.com/helm/helm/issues) are great resources if you have follow-up needs or questions in using Helm or Helm charts.

Thanks @iainfoulds that makes sense
@cuongdnv check the above links provided by Iain and let us know if you have questions.


[BUG] build templates/worker-rust err

Is there an existing issue for this?

[X] I have searched the existing issues

What version of workers-rs are you using?
0.0.9
Describe the bug
Build err
openssl-sys v<IP_ADDRESS> build err
Log:
Compiling termios v0.3.3
Compiling quote v1.0.18
error: failed to run custom build command for openssl-sys v0.9.74
Caused by:
process didn't exit successfully: /tmp/cargo-installXQR0K8/release/build/openssl-sys-588c1e901cec6614/build-script-main (exit status: 101)
--- stdout
cargo:rustc-cfg=const_fn
cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_GNU_OPENSSL_NO_VENDOR
X86_64_UNKNOWN_LINUX_GNU_OPENSSL_NO_VENDOR unset
cargo:rerun-if-env-changed=OPENSSL_NO_VENDOR
OPENSSL_NO_VENDOR unset
CC_x86_64-unknown-linux-gnu = None
CC_x86_64_unknown_linux_gnu = None
HOST_CC = None
CC = None
CFLAGS_x86_64-unknown-linux-gnu = None
CFLAGS_x86_64_unknown_linux_gnu = None
HOST_CFLAGS = None
CFLAGS = None
CRATE_CC_NO_DEFAULTS = None
DEBUG = Some("false")
CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
running "perl" "./Configure" "--prefix=/tmp/cargo-installXQR0K8/release/build/openssl-sys-4848a54ac28472a7/out/openssl-build/install" "--openssldir=/usr/local/ssl" "no-dso" "no-shared" "no-ssl3" "no-unit-test" "no-comp" "no-zlib" "no-zlib-dynamic" "no-md2" "no-rc5" "no-weak-ssl-ciphers" "no-camellia" "no-idea" "no-seed" "linux-x86_64" "-O2" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64"
Configuring OpenSSL version 1.1.1o (0x101010ffL) for linux-x86_64
Using os-specific seed configuration
Creating configdata.pm
Creating Makefile

***   OpenSSL has been successfully configured                     ***

***   If you encounter a problem while building, please open an    ***
***   issue on GitHub https://github.com/openssl/openssl/issues  ***
***   and include the output from the following command:           ***

***       perl configdata.pm --dump                                ***

***   (If you are new to OpenSSL, you might want to consult the    ***
***   'Troubleshooting' section in the INSTALL file first)         ***

running "make" "depend"
--- stderr
thread 'main' panicked at 'called Result::unwrap() on an Err value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', /home/muyu/.cargo/registry/src/github.com-1ecc6299db9ec823/openssl-src-111.20.0+1.1.1o/src/lib.rs:488:39
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
error: failed to compile wasm-pack v0.10.2, intermediate artifacts can be found at /tmp/cargo-installXQR0K8
Error: installation of wasm-pack exited with status exit status: 101
✘ [ERROR] Command failed with exit code 1: cargo install -q worker-build && ~/.cargo/bin/worker-build --release
If you think this is a bug then please create an issue at https://github.com/cloudflare/wrangler2/issues/new/choose
Steps To Reproduce
rustc --version = rustc 1.61.0 (Arch Linux rust 1:1.61.0-1)
cargo --version = cargo 1.61.0
wrangler --version = 2.0.8
git clone templates/woker-rust
cd worker-rust
wrangler dev
buidl err

archlinux vps 1vCpu 2GMem  50Gsda 10G/tmp dir


changes

so many changes
so much improvement

I seriously need some changes. Or else.

Happy now?


HindiWordNet Scraping

In reference to Issue Discovering Datasets
Scraping data off the Hindi WordNet.
Tasks include:

[ ] Understanding How the WordNet works.

[ ] Scraping data in a manner that can be used  by the lemmatizer.

[ ] Pushing the files to the repository.

@mayankk98 has been temporarily unassigned this issue.
He has a latent dependency on @MansiBreja and @AnkitaMohanty scraping work.
He will resume working on this once that is done.


chore: add CODEOWNERS file

Signed-off-by: Jennifer Power<EMAIL_ADDRESS>

Blocked by https://github.com/emporous/.github/pull/28


Project idea: guide for maintainers on handling incidents

As per https://github.com/ossf/SIRT/pull/5#issuecomment-1256341717
The SIRT's goals are indeed to help with incidents and vulnerability coordinations, but the documentation and training of it should not be handled by the SIRT itself. It was suggested to have the Vuln Discslosure WG look at taking this effort instead.

It was discussed in the WG today that we may wish to search to see if any existing art or docs exist on this to kickstart our efforts.  The team generally thought pursuing this has merit.

We may Check Red Hat's Open Source Incident Response Plan
Red Hat Incident Response Plan - Red Hat Incident Response Plan

We have this previous issue we may want to merge here https://github.com/ossf/wg-vulnerability-disclosures/issues/100

I'm in favor of this as the next project for the working group before #115 and #116, but think all 3 are great ideas.

Agree with @taladrane. I'm also in favor of this project being the next in line. All of the projects sound interesting!

I am interested to be a part of the sub-working group or SIG for this project


remove the "thank you" message on install

It is getting time to remove the thank you message that pops up when a person first downloads the client.  I think it might be better instead if we made an introduction video to NCC and then put that in a link for people to watch if they want, or just delete it altogether.

i totally agree.
we could also directly embed the video. only problem: china blocks youtube...


🎮 Game Request
Mahjong game offers players the classic experience of matching identical pairs of tiles on a board. The starting page presents the shape of the board, and players can choose the difficulty level before beginning the game. Once the board is selected, the objective is to make matches by selecting two tiles at a time. Each time a pair of identical tiles is matched, the player's score increases by 2 points.
Game Logic:
1.Set up the board:
Create a grid or layout for the Mahjong board.
Populate the board with Mahjong tiles. Each tile should have a unique identifier and an associated image or symbol.
Randomly distribute the tiles across the board, ensuring that each tile is hidden from view initially.

Player interaction:

Allow the player to select two tiles at a time. When a tile is selected, it should become visible to the player.
If the two selected tiles match, remove them from the board. If they don't match, hide them again.
Keep track of the player's score, initially set to 0.

Matching logic:

Determine the matching criteria for tiles. Typically, Mahjong tiles can match if they have the same symbol or number.
Implement logic to check if the two selected tiles match according to the matching criteria.
If the tiles match, remove them from the board and increase the player's score by 2 points.
If the tiles don't match, hide them again, and the player's score remains unchanged.

Win condition:

Continuously check if all the tiles have been removed from the board.
If all the tiles are removed, the player has won the game. Display a victory message and the final score.
Point down the features

Matched Pair: When the player successfully matches a pair of identical tiles, their score increases by 2 points. This encourages the player to make accurate and efficient matches.

Incorrect Match: If the player selects two tiles that don't match, their score remains unchanged. This emphasizes the importance of memory and concentration in the game.

Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

/assign


meson/setup-hook.sh: make build directory configurable

Description of changes
closes https://github.com/NixOS/nixpkgs/issues/335818 @Ericson2314

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

https://github.com/NixOS/nixpkgs/blob/master/doc/hooks/cmake.section.md Boo the CMake equivalent doesn't document this either, so we can't just cut and paste.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/2024-09-18-nix-team-meeting-minutes-179/52361/1

I tested this with
diff --git a/pkgs/development/libraries/frozen/default.nix b/pkgs/development/libraries/frozen/default.nix
index 26c47617c1f6..2681c377977b 100644
--- a/pkgs/development/libraries/frozen/default.nix
+++ b/pkgs/development/libraries/frozen/default.nix
@@ -19,6 +19,10 @@ stdenv.mkDerivation rec {

   nativeBuildInputs = [ meson ninja ];

+  preHook = "set -x";
+
+  mesonBuildDir = "asdf";
+
   # frozen has a simple Makefile and a GN BUILD file as building scripts.
   # Since it has only two source files, the best course of action to support
   # cross compilation is to create a small meson.build file.


SectionHeader is blank for ListView only for android

  **Issues that do not describe a bug or do not fill out the template below will be closed**
We use GitHub Issues exclusively for tracking bugs in React Native.

If you're looking for help with your code, consider asking on Stack Overflow instead: http://stackoverflow.com/questions/tagged/react-native
Want to know more about future plans? Check out the roadmap: https://github.com/facebook/react-native/wiki/Roadmap
Have a feature request that is not covered in the roadmap? Submit it here: https://react-native.canny.io/feature-requests

Reporting bugs
Want to report a bug? Please read the bug reporting guidelines: https://github.com/facebook/react-native/blob/master/CONTRIBUTING.md#bugs

Description
Use ListView, and stickySectionHeadersEnabled is true, the data is dynamic，if the new data is part of section part 0, the SectionHeader will be shown blank, and data is wrong.
Reproduction Steps
Run the  example codes， scroll the view of list to up, when request the data is more, the issue will happening.
This issue only for android to happening.
Sample Code
'use strict';
import React, { Component, PureComponent } from 'react';
import {
Platform,
Image,
LayoutAnimation,
ListView,
StyleSheet,
Text,
TouchableOpacity,
View,
} from 'react-native';
class StudySectionHeaderList extends Component {
constructor(props) {
    super(props);

    this.startIndex = 0;
    this.moreData = true;
    this.dataBlob = {};
    this.sectionIDs = [];
    this.rowIDs = [];

    this.dataSource = new ListView.DataSource({
        getRowData: this.getRowData,
        getSectionHeaderData: this.getSectionData,
        rowHasChanged: (row1, row2) => row1 !== row2,
        sectionHeaderHasChanged: (s1, s2) => s1 !== s2,
        // rowHasChanged: (row1, row2) => true,
        // sectionHeaderHasChanged: (s1, s2) => true,
    });

    this.loadData();
}

renderRow(rowData, sectionID, rowID){
    return <Text>{rowData.path}-----{rowData.name}</Text>
}

renderSectionHeader(sectionData, sectionID){
    return (
        <View style={styles.section}>
            <Text style={styles.text}>
                {sectionData}
            </Text>
        </View>
    );
}

loadData(){
    if(!this.moreData){
        return;
    }
    console.log('---------loadDate');

    let reqeustSize = 50

    for (let ii = this.startIndex; ii < this.startIndex + 1; ii++) {
        let sectionName = 'Section ' + ii;
        console.log('---------loadDate---sectionName=' + sectionName);
        this.sectionIDs.push(sectionName);
        this.dataBlob[sectionName] = sectionName;
        this.rowIDs[ii] = [];

        for (let jj = 0; jj < reqeustSize; jj++) {
        // for (var jj = 0; jj < Ma／th.floor(Math.random() * 20)+1; jj++) {
            let key = 'S' + ii + ', R' + jj;
            let path = 'path' + jj;
            let name = 'name' + jj;
            let rowData = {path:path, name:name};
            this.rowIDs[ii].push(key);
            this.dataBlob[key] = rowData;
        }
    }

    this.startIndex = this.startIndex + 1;

    if(this.startIndex === 3){
        for(let kk = 100; kk < 120; kk++){
            let key = 'S1' + ', R' + kk;
            let path = 'path' + kk;
            let name = 'name' + kk;
            this.rowIDs[0].push(key);
            let rowData = {path:path, name:name};
            this.dataBlob[key] = rowData;
        }
    }

    if(this.startIndex === 10){
        this.moreData = false;
    }

    // this.state = {
    //     dataSource: this.dataSource.cloneWithRowsAndSections(this.dataBlob, this.sectionIDs, this.rowIDs),
    // };
    this.setState({});
}

getSectionData(dataBlob, sectionID){
    return dataBlob[sectionID];
}

getRowData(dataBlob, sectionID, rowID){
    return dataBlob[rowID];
}

render() {
    let allData = this.dataSource.cloneWithRowsAndSections(this.dataBlob, this.sectionIDs, this.rowIDs);

    return (
        <View style={{flex: 1, flexDirection: 'column'}}>
            <View style={{height: (Platform.OS == 'ios') ? 20 : 0}} />
            <ListView
                style={styles.listview}
                dataSource={allData}
                renderSectionHeader={this.renderSectionHeader}
                renderRow={this.renderRow}
                onEndReached={this.loadData.bind(this)}
                onEndReachedThreshold={10}
                initialListSize={10}
                pageSize={4}
                // rowHasChanged={(r1, r2) => {
                //     // FIXME: only to refresh the changed rows
                //     return true;
                // }}
                // scrollRenderAheadDistance={500}
                stickySectionHeadersEnabled={true}//
            />
        </View>
    );
}

}
var styles = StyleSheet.create({
listview: {
backgroundColor: '#B0C4DE',
},
header: {
height: 40,
justifyContent: 'center',
alignItems: 'center',
backgroundColor: '#3B5998',
flexDirection: 'row',
},
text: {
color: 'white',
paddingHorizontal: 8,
},
rowText: {
color: '#888888',
},
thumbText: {
fontSize: 20,
color: '#888888',
},
buttonContents: {
flexDirection: 'row',
justifyContent: 'center',
alignItems: 'center',
marginHorizontal: 5,
marginVertical: 3,
padding: 5,
backgroundColor: '#EAEAEA',
borderRadius: 3,
paddingVertical: 10,
},
img: {
width: 64,
height: 64,
marginHorizontal: 10,
backgroundColor: 'transparent',
},
section: {
flexDirection: 'column',
justifyContent: 'center',
alignItems: 'flex-start',
padding: 6,
backgroundColor: '#5890ff',
},
});
module.exports = StudySectionHeaderList;
Solution
What needs to be done to address this issue? Ideally, provide a pull request with a fix.
Additional Information

React Native version: react native 0.44.0，
Platform: this issue is happening only for android

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.


Fix missing issuer in QR URI causing duplicate tokens

Hello,
Resolves: #379
Issue analysis:
Assuming the issuer is missing in the URI. The issuer prompt view will be pushed into the secne. And when the user clicks next The below code will warn the user and process the form.

Here, we can see if the user clicks "use empty issuer" the app will process the form.

The form is processed twice (Could be more if the user clicks cancel and repeat) according to the logic above.
The fix is simple:
Now submitForm is called only in two cases. One if the issuer is entered or if the user use empty issuer where submitForm is called inside the function.

Thank you @falghamdi125 for the PR and the explanation. One minor request, can you add the text Resolves: https://github.com/freeotp/freeotp-ios/issues/379 into the commit message, such as in https://github.com/freeotp/freeotp-ios/pull/352/commits/37845bd2ba602592d5b71699c524e42c94687e9c

You're welcome! Suggested text has been added into the commit message.


Parsing of generated SPARQL via langchain rdflib always gives "pyparsing.exceptions.ParseException"

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
the following code:
metaqa_path = pathlib.Path(__file__).parent.absolute() / 'mydata' / 'metaQA'
metaqa_rdf = metaqa_path / 'knowledge_graph.rdf'
metaqa_ttl = metaqa_path / 'kb_wo_parse.ttl'

graph = RdfGraph(
    source_file=str(metaqa_ttl),
    standard="rdf",
)

chain = GraphSparqlQAChain.from_llm(
    ChatOpenAI(temperature=0), graph=graph, verbose=True
)

print(chain.run(r'which movies starred the actor Gert Fröbe'))

Error Message and Stack Trace (if applicable)
line 1200, in parse_string
raise exc.with_traceback(None)
pyparsing.exceptions.ParseException: Expected {SelectQuery | ConstructQuery | DescribeQuery | AskQuery}, found '`'  (at char 0), (line:1, col:1)
Description

It should be eliminitaing the ``` (triple quotes) generated by the LLM, that cannot be parsed by RDFLIB.
Should generate

PREFIX metaQAKB: <http://metaQAKB.org/>
SELECT ?movie
WHERE {
    ?movie metaQAKB:starred_actors "Gert Fröbe" .
}

Instead of

PREFIX metaQAKB: http://metaQAKB.org/
SELECT ?movie
WHERE {
?movie metaQAKB:starred_actors "Gert Fröbe" .
}

System Info
langchain-0.1.14
rdflib-7.0.0
langchain-openai-0.1.1

Adding this in the langchain sourcecode
\venv\Lib\site-packages\langchain\chains\graph_qa\sparql.py
generated_sparql = generated_sparql.strip()[3:-3] -> eliminates the first and last set of the triple quotes and makes SPARQL parsable

Will this bug be merged into master branch anytime soon?


make tf_upgrade.py more useful

When we upgrade tf code to version 1.0.0 in a directory tree, some times we also want to copy all the other files from --intree to the --outtree，this makes it easier to upgrade an entire project.
So I add an option named --copyotherfiles in tf_upgrade.py. Hopefully useful!
# just upgrade the .py files
tf_upgrade.py --intree coolcode --outtree coolcode-upgraded
# after upgrade the .py files, then copy all the other files to the outtree
tf_upgrade.py --intree coolcode --outtree coolcode-upgraded --copyotherfiles True

Can one of the admins verify this patch?

gentle ping @aselle

Thanks for the patch @primetang, LGTM

@tensorflow-jenkins Test this please.

Jenkins, test this please

Jenkins, test this please


Quasilyte/type guard v1

Does trigger for cases from testdata/type-guard.
Does not handle nested type switches if containing type switch already triggered warning.
Will fix that later (todo is on it's place).

At least we saw that CI still works. ;)

Refs https://github.com/PieselBois/kfulint/issues/10.

@fexolm, I think AST filters and combinators are a way to go, far better than hardcoded walkFuncDeclBodies things.
Also re-implemented find function in terms of astutil.Apply. Requires no panic now.

@Quasilyte maybe we should merge that pr at last? It becomes large.

@fexolm, here goes.


Enhance duration UX by accepting formatted strings

zipkin-web accepts raw microseconds in the search form for minimum duration. Eventhough the HTTP api should accept this (as there's no standard URI encoding of duration, especially microseconds), we should make the user experience better.
#863 was raised against this, but approached this by changing the query api to parse scala types. A better solution would be to address this in javascript, similarly to how we address endTs
Ex. the hidden endTs parameter is assembled by a flightjs component named timeStamp, using momentjs.  Since momentjs supports duration strings, we should be able to use this as well. By using momentjs, we can allow validation and coersion to happen in the browser, where other similar aspects are addressed.
As a first step, we can create a text component which attempts to use momentjs if the contents are non-numeric. Ex. if the contents are purely numeric, we could assume it is microseconds, a granularity very untypical in javascript. Ex. 2 hours would use momentjs, whereas 140 is missing a unit and be passed raw as microseconds. Alternatively, we could special case some unit for micros and default purely numeric strings to millis.
The normal flow in flight seems to be to define an inputfield, hidden outputfield, and a javascript component to plumb them together.

@danchia @yurishkuro @eirslett @nikhil2406 @gneokleo @synk Fishing for those who've touched flight components before :) Do any of you have some cycles to try this?

@jcarres-mdsol I suspect your answer is "scala...", but just in case you can help :P

@dev-priya really really really fishing :) I remember you saved me back in the day on twitter UI stuff.. if this looks like something you could help with, you'd win the adoration of millions (of lines of code?! :))

@adriancole let me give this a stab.

So I took a quick stab at this, and it turns out it's not that easy.
momentjs supports ASP style durations (H:m:s), but not human readable ones like "1 second".
Even worse is that their human readable forms of durations, e.g. moment.duration("0:00::00:1").humanize() gives you a few seconds which is not parsable back into a duration.
Any ideas?

might not work, but I was thinking the 2 arg methods, which look like they
accept a number and a unit? (ex  'm' or 'minutes')
http://momentjs.com/docs/#/manipulating/add/
http://momentjs.com/docs/#/utilities/

Hm.. interesting. Still have to solve the bijection problem, but I have an idea..

@danchia I hope this task didn't scare you from zipkin forever :P

Nah, really busy at work :(
Zipkin is definitely one of my favorite projects to watch :)

This issue refers to zipkin-classic which is no longer maintained and replaced by Lens. If the duration search component is not satisfactory there please open a new issue.


Release candidate 0.1rc1

Merge changes from main into the release branch, and update the version to 0.1rc1.

Documentation style action is failing due to a bug in the action itself; this runs fine on main. Reported as https://github.com/ansys/actions/issues/655


Convert time extension not working for non-smithy crates

DateTimeExt works for aws_smithy_types but not for other crates like EC2.
use aws_smithy_types_convert::date_time::DateTimeExt;
use chrono::Utc;
use std::{convert::TryFrom, time::SystemTime};

fn main() {
    aws_smithy_types::date_time::DateTime::from_secs(5).to_chrono_utc(); // works

    let ec2_time = aws_sdk_ec2::types::DateTime::from_secs(5);
    ec2_time.to_chrono_utc(); // doesn't work;no method found

    // works
    let sys_time = SystemTime::try_from(ec2_time).unwrap();
    let chrono_time = chrono::DateTime::<Utc>::from(sys_time);
}

Minimum working example repo here --> https://github.com/allan2/aws-convert-time

I think this should work for you if you change the 0.48 versions to 0.47 to be consistent with what the EC2 crate is depending on:
aws-smithy-types-convert = { version = "0.47", features = ["convert-chrono"] }
aws-smithy-types = "0.47"
aws-sdk-ec2 = "0.17"

Thanks John. That works.
Is there any way to show a warning when versions are mismatched?

Is there any way to show a warning when versions are mismatched?

Not an easy way that I'm aware of, unfortunately. You can setup cargo-deny to disallow or warn on duplicate dependencies, but it will likely complain about many other transitive dependencies as well.
I think this is a problem that will go away once we reach 1.0 since we'll have stability guarantees among all these crates. Until then, the versions.toml file in aws-sdk-rust tracks which versions pair together for any given release (for a specific release, look at that file at the release tag).


fix: the dependency error of node.js in mix.deps in example_project

Hi @Valian , The document  specifies elixir-nodejs for SSR, but the actual dependency is Valian/elixir-nodejs in example_project. mix deps.get will fail.

Yes, thanks you. when update it to  {:nodejs, "~> 3.1"}, it works fine.


Cannot open JSONB view

Overview of the issue
I have very simple diagram with just single table. After playing with different settings I'm not longer able to access JSONB view.
Expected Outcome
I expect to see the tab with JSONB view when pressing Ctrl+B or selecting the "JSONB View" option from context menu.
Current Outcome
I get error message with following description:
java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
Steps to Reproduce(Only for bug reports)
Try to open JSONB View on following diagram:
diagram.zip
Jeddict Version(s)
4.9

Thanks @biobob for reporting the issue.


Async property can’t have a setter

async_property version: 0.2.2
Python version: 3.11.9
Operating System: Windows 11

Description
I created an async property. It needed a setter, so I made a synchronous setter for it. It raised an error saying async_property has no attribute 'setter'.
I am aware of the other async setter issue. It was, however, closed with the explanation that setters can’t be asynchronous. That is not my issue, I want a synchronous setter for an async property.
What I Did
The code
    @async_property
    async def channel(self) -> hikari.GuildChannel:
        """La steltabula kanalo"""
        if not self.__channel:
            self.__channel = await plugin.app.rest.fetch_channel(self.__channel_id)
        return self.__channel

    @channel.setter
    def channel(self, new_value: hikari.GuildChannel | int):
        if isinstance(new_value, hikari.GuildChannel):
            self.__channel = new_value
            self.__channel_id = new_value.id
        else:
            self.__channel_id = new_value
            self.__channel = None
        self.__update_in_database("steltabula-kanalo", self.__channel_id)

The traceback
  File "c:\Esperanto\Espiralo\steltabulo.py", line 76, in StarboardSettings
    @channel.setter
     ^^^^^^^^^^^^^^
AttributeError: 'AsyncPropertyDescriptor' object has no attribute 'setter'

You should be using the async_cached_property instead

Using async_cached_property kinda works, but now I have another issue
from async_property import async_cached_property
import asyncio

class TestClass:
    def __init__(self, value):
        self.__value = value.upper()

    @async_cached_property
    async def value(self):
        return self.__value

    @value.setter
    def value(self, new_value: str):
        self.__value = new_value.upper()

    def set_value(self, new_value: str):
        self.__value = new_value.upper()

async def main():
    test_obj = TestClass("first value")
    print(await test_obj.value)
    test_obj.value = "second value"
    print(await test_obj.value)
    test_obj.set_value("third value")
    print(await test_obj.value)

asyncio.run(main())

Editing a cached property is a hassle: I can’t modify the value in the setter, since it assumes I want to return the value I set it to, and a separate set method doesn’t affect the returned value at all. Is there a way to make sure each call of the setter clears the cache for that value?


React 16.6.0 and new context API "static contextType"

While playing with this new feature just released: https://reactjs.org/docs/context.html#classcontexttype
I got the following:
Uncaught Error: [undefined] Please use ThemeProvider to be able to use WithTheme
    at Object.initial (create-theme-listener.js?6a8e:13)
    at new Jss (createHoc.js?ffe6:144)
    at constructClassInstance (react-dom.development.js?61bb:11864)
    at updateClassComponent (react-dom.development.js?61bb:13681)
    at beginWork (react-dom.development.js?61bb:14489)
    at performUnitOfWork (react-dom.development.js?61bb:17014)
    at workLoop (react-dom.development.js?61bb:17054)
    at HTMLUnknownElement.callCallback (react-dom.development.js?61bb:149)
    at Object.invokeGuardedCallbackDev (react-dom.development.js?61bb:199)
    at invokeGuardedCallback

The above error occurred in the <Jss(Text)> component:
    in Jss(Text) (created by Auth)
    in form (created by Form)
    in Form (created by Auth)
    in main (created by Auth)
    in Auth (created by Jss(Auth))
    in Jss(Auth) (created by Route)
    in Route (created by withRouter(Jss(Auth)))
    in withRouter(Jss(Auth)) (created by Route)
    in Route (created by Router)
    in Switch (created by Router)
    in Layout (created by Jss(Layout))
    in Jss(Layout) (created by Route)
    in Route (created by withRouter(Jss(Layout)))
    in withRouter(Jss(Layout)) (created by Router)
    in Router (created by BrowserRouter)
    in BrowserRouter (created by Router)
    in Router
    in ThemeProvider

Snippet of not working component:
import React from 'react';
import PropTypes from 'prop-types';
import cx from 'classnames';
import injectSheet from 'react-jss';
import ClearIcon from 'muicons/dist/CloseCircle.js';

import { context } from './Form.js';

@injectSheet(theme => ({
}))
export default class Text extends React.PureComponent {
    static contextType = context;

    static propTypes = {
        classes: PropTypes.object.isRequired,
        name: PropTypes.string.isRequired,
    };

    render = () => {
        // destructuring defaultValue to not have it in otherProps
        const { classes, name, value, defaultValue, ...otherProps } = this.props; //eslint-disable-line
        const { values, onChange, onClear } = this.context

        return (

                <input id={name} name={name} value={values[name] || ''} onChange={onChange(name)} type={'text'} {...otherProps} />
                { !!onClear && !!value && <ClearIcon onClick={onClear(name)} />}

        );
    };
}

Snippet of working component (without using the new API):
import React from 'react';
import PropTypes from 'prop-types';
import cx from 'classnames';
import injectSheet from 'react-jss';

import { context } from './Form.js';

import ClearIcon from 'muicons/dist/CloseCircle.js';

@injectSheet(theme => ({
}))
export default class Text extends React.PureComponent {
    static propTypes = {
        classes: PropTypes.object.isRequired,
        name: PropTypes.string.isRequired,
    };

    render = () => {
        // destructuring defaultValue to not have it in otherProps
        const { classes, name, value, defaultValue, ...otherProps } = this.props; //eslint-disable-line

        return (
            <context.Consumer>
                { contextValue => {
                    const { values, onChange, onClear } = contextValue;

                    return (

                            <input id={name} name={name} value={values[name] || ''} onChange={onChange(name)} type={'text'} {...otherProps} />
                            { !!onClear && !!value && <ClearIcon onClick={onClear(name)} />}

                    );
                } }
            </context.Consumer>
        );
    };
}

Hey @kof, yes: I'm using the new React context API, and the ThemeProvider as well.
import React from 'react';
import ReactDOM from 'react-dom';

import { jss, ThemeProvider } from 'react-jss';
import theme from './theme';

import Router from './Router';

jss.createStyleSheet(theme.globals).attach();

ReactDOM.render(
    <ThemeProvider theme={theme}>
        <Router />
    </ThemeProvider>
, document.getElementById('app'));

Feel free to close the issue, I'll be reopening it once I manage to create a codesandbox reproducing the error.
I just wanted to report this issue as soon as possible so if anyone was already working on new context API integration then he'd be aware of this behaviour as well.

We will move away from the old context API soon.
As this repo is about to be archived, please create a new issue in the jss repo with a codesandbox link as soon as you are able to reproduce the error.


关于I2VGen-XL模型的问题

General Question
Before asking a question, make sure you have:

Searched the tutorial on modelscope  doc-site
Googled your question.
Searched related issues but cannot get the expected help.
The bug has not been fixed in the latest version.

Please @ corresponding people according to your problem:
Model related: @wenmengzhou @tastelikefeet
Model hub related: @liuyhwangyh
Dataset releated: @wangxingjun778
Finetune related: @tastelikefeet  @Jintao-Huang
Pipeline related: @Firmament-cyou @wenmengzhou
Contribute your model: @zzclynn
按照modelscope提供的demo:
from modelscope.pipelines import pipeline
from modelscope.outputs import OutputKeys
pipe = pipeline(task="image-to-video", model='damo/Image-to-Video', model_revision='v1.1.0', device='cuda:0')
IMG_PATH: your image path (url or local file)
output_video_path = pipe(IMG_PATH, output_video='./output.mp4')[OutputKeys.OUTPUT_VIDEO]
print(output_video_path)
执行后报错信息如下
WARNING - No preprocessor key ('image-to-video-model', 'image-to-video') found in PREPROCESSOR_MAP, skip building preprocessor.
2023-12-06 18:54:38,779 - modelscope - WARNING - task image-to-video input definition is missing
2023-12-06 18:55:32,676 - modelscope - ERROR - Save Video Error with
2023-12-06 18:55:32,678 - modelscope - WARNING - task image-to-video output keys are missing
没有结果生成，请问怎么解决？

The reason is that the video generation process is fixed to use ffmpeg and no results will be generated if your ffmpeg does not support x264 codec. You can change the video generation command to other commands such as imageio.

ok , thank you .By the way, there is also a problem, that is, if there is someone in the input picture, the face will be distorted and changed in the output video.


Bug: Running the tests does not work on Mac OS out of the box

Expected behavior
Following the steps in Src/Newtonsoft.Json-for-Unity.Tests/ as-is successfully guides the user to run the tests on all platforms.
(I am assuming that Mac OS is a supported platform since it is required to build iOS.)
Actual behavior
ci/local_build_into_package.ps1 works, but running the tests does not. I tried all three methods.
Running via command line
See output_unity_runtests.txt for the full output. Relevant error sections here:
Assets/Newtonsoft.Json.Tests.Aot/EnsureTypes.cs(4,23): error CS0234: The type or namespace name 'Utilities' does not exist in the namespace 'Newtonsoft.Json' (are you missing an assembly reference?)
Assets/UnityTests/HttpUtilityTests.cs(12,21): error CS0103: The name 'HttpUtility' does not exist in the current context
Assets/UnityTests/HttpUtilityTests.cs(19,21): error CS0103: The name 'HttpUtility' does not exist in the current context

Running via Unity Editor
Same errors as running via command line, but in the editor console.
Running via Docker
(This is not my main issue, as I'd like to be able to run the tests without Docker, but noting here for completeness.)
➜  Newtonsoft.Json-for-Unity git:(master) $ ci/local_test_in_unity_container.ps1 -VolumeSource $(pwd)
Resolve-Path: /Users/lincolnbergeson/Workspace/Newtonsoft.Json-for-Unity/ci/local_test_in_unity_container.ps1:49
Line |
  49 |      Resolve-Path (Join-Path "$PSScriptRoot" "Unity_v$UnityVersion.ulf …
     |      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Cannot find path '/Users/lincolnbergeson/Workspace/Newtonsoft.Json-for-Unity/ci/Unity_v2019.2.11f1.ulf' because it does not
     | exist.

ls ci shows no .ulf files in that directory:
docker_build_images.ps1           local_build_into_test_project.ps1 package-builder.Dockerfile        package-unity-tester.Dockerfile
docker_publish_images.ps1         local_docker_run.ps1              package-deploy-github.Dockerfile  scripts
local_build_into_package.ps1      local_test_in_unity_container.ps1 package-deploy-npm.Dockerfile     version.json

Steps to reproduce
Full repro in a fork at https://github.com/lwb4/Newtonsoft.Json-for-Unity
First I installed the dependencies:

Install Powershell via Homebrew
Install Docker Desktop via their website
Install Unity version 2019.2.11f1 via Unity Hub

Then, to repro the bug:

Clone this repo
mkdir Src/Newtonsoft.Json-for-Unity.Tests/Assets/Newtonsoft.Json.Tests
cp -R Src/Newtonsoft.Json.Tests/* Src/Newtonsoft.Json-for-Unity.Tests/Assets/Newtonsoft.Json.Tests/ (No need to remove bin or obj folders, since none were found)
ci/local_build_into_package.ps1 (output attached in output_local_build_into_package_ps1.txt)
/Applications/Unity/Hub/Editor/2019.2.11f1/Unity.app/Contents/MacOS/Unity -runTests -batchmode -projectPath Src/Newtonsoft.Json-for-Unity.Tests -testResults results.xml -testPlatform iOS -logFile output_unity_runtests.txt

output_ci_local_build_into_package_ps1.txt
output_unity_runtests.txt
Details
Host machine OS running Unity Editor: Macbook Pro 2019 running Mac OS Big Sur Version 11.2.3
Unity build target: iOS targeted above, but the default testPlatform parameter (editmode) doesn't work either.
Newtonsoft.Json-for-Unity package version: Latest master from this repo
I was using Unity version 2019.2.11f1
Checklist

[x] Shutdown Unity, deleted the /Library folder, opened project again in Unity, and problem still remains.
[x] Checked to be using latest version of the package.

Hi! Thanks for reporting this! Didn't know anyone even inspected those scripts. No doubt that you're having issues with these scripts; they are not well maintained (by me).
I'm really sorry about the lack of documentation and outdated scripts here. I've let those scripts rot because I'm more or less only testing via CircleCI atm.
The ULF file that it needs is intentionally omitted from the repo as it contains personal authentication tokens for Unity.
I did writeup some kind of guide a long time ago here: https://github.com/jilleJr/Newtonsoft.Json-for-Unity.Converters/blob/master/Build/CIRCLECI_SETUP.md#obtain-unity-license-ulf-files No clue how relevant it is anymore. Don't even know why I have that added to my converters repo but not this one.
I will look into this and start cleaning up the scripts and such. I want to be able to run the tests in the editor locally as well, and I remember that I got it working before at some point. It was the only way I could get it to run tests with IL2CPP.
But! I cannot promise a timeframe here. Everytime I touch this project I seem to do a little bit of work and then kind of get burned out by it.

Thanks for the quick response! (I'm working with @lwb4) We were trying to troubleshoot other issues, were digging in and this seemed like it might be related, but then we were able to fix our issues (for now) by following the directions in the wiki for using AotHelper. So ... cool if this gets fixed eventually, but I don't think we're going to be worrying about this much more at the time being.

Good to know! Glad that you got it resolved :)
I'll want to keep this issue open so I don't forget about it.

Yeah, I found this issue while trying to get a repro for the other issue, so no big deal.
That said, a simple message at the top of that README saying "these scripts are out of date and don't work" would have saved me a lot of time! Just a suggestion. :)

@lwb4 That's a great note. I can really understand your frustration here, even though you're not saying it, as I've been there myself sometimes. :) Will add that note


cli: Restore _suppress_exceptions

Also update the self-transpile tests to reflect
that cpp, julia and nim no longer have exceptions
occur due to recent bug fixes.
Only go still has exceptions during self-transpilation.

@adsharma, ping, this is the last regression that I believe is blocking https://github.com/adsharma/py2many/issues/356

ping @adsharma

It's used only for dependency management in toposort_modules.py, so both
variants work.
But it's possible that we start using module_for_path() for other stuff in
which case this becomes significant.
On Tue, Jul 13, 2021 at 5:47 PM John Vandenberg @.***>
wrote:

@.**** commented on this pull request.
In py2many/toposort_modules.py
https://github.com/adsharma/py2many/pull/421#discussion_r669201791:

@@ -7,7 +7,7 @@

def module_for_path(path: Path) -> str:
# strip out .py at the end

return ".".join(path.parts)[:-3]

curious that there were no tests failing.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/adsharma/py2many/pull/421#discussion_r669201791, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFA2A5UV7MXZTN7BL3GYWTTXTNBFANCNFSM5AH5FV2Q
.


UnCheckedColor parameter (from v6) not getting picked up as a warning by the v7 analyzer

Things to check

[X] I have searched the existing issues for this bug
[X] To rule out a caching problem I made sure the bug also happens in an incognito tab

Bug type
Component, Analyzer
Component name
MudRadio
What happened?
Followed the migration guide from v6 to v7, fixed pretty much all the errors that showed, including the warnings. Ran tests, some failed for obscure reasons, so I tried testing manually those cases, and realized that the parameter UnCheckedColor of the MudRadio (renamed in v7 to UncheckedColor) was misspelled. I searched in the warnings in case I missed it there, and no warnings from the new MudBlazor analyzer picked up this issue, which end up causing a runtime crash.
Expected behavior
The new analyzer should've flagged UnCheckedColor as illegal like other misspelled parameters to prevent runtime crashes or unexpected behaviors, because of the said misspelled parameter.
Reproduction link
https://try.mudblazor.com/snippet/mOGyOsvXKbSKwStb
Reproduction steps

Add a MudRadio
Set the parameter UnCheckedColor to any valid value
Compile
No warning occurs
Open the app in the browser
Crash

Relevant log output
No response
Version (bug)
7.6.0
Version (working)
No response
What browsers are you seeing the problem on?
Firefox, Chrome, Edge, Other
On which operating systems are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@peterthorpe81

I will take a look. I dont think it's checking case past the first character for the html attribute Vs blazor parameter.
I'm not 100% why it would error rather than just not set the parameter though.

ping


Support Relation With LateralView

What changes were proposed in this pull request?

Users can more convenient to use LATERAL VIEW with relation instead of creating a subqury
Why are the changes needed?

Before this change:
SELECT *
FROM ( SELECT CC1.C_AGE1 FROM PERSON1 AS P1
LATERAL VIEW EXPLODE(ARRAY(30, 60)) CC1 AS C_AGE1 ) AS P1
LEFT JOIN PERSON2 P2 ON P1.ID = P2.ID  AND P1.C_AGE1=P2.AGE;

After:
SELECT *
FROM PERSON1 AS P1
LATERAL VIEW EXPLODE(ARRAY(30, 60)) CC1 AS C_AGE1
LEFT JOIN PERSON2 P2 ON P1.ID = P2.ID  AND CC1.C_AGE1=P2.AGE;

Does this PR introduce any user-facing change?

How was this patch tested?

Add unit tests

Can one of the admins verify this patch?


SoftDelete trait throws PHP error with PHP7.2

Laravel Version: 5.1.46
PHP Version: 7.2.0RC6
Database Driver & Version: pgsql

Description:
Using the SoftDelete trait on a model when using PHP 7.2 throws an internal error because of the usage of count in the SoftDeletingScope on line 75. The property joins isn't always an array and results in a call of count(null).
Updating line 92 of Illuminate/Database/Query/Builder.php to
    /**
     * The table joins for the query.
     *
     * @var array
     */
    public $joins = [];

is enough to stop the error from happening, although it looks like there are multiple other properties in the class that should be updated in a similar way to prevent this error from happening elsewhere.
Steps To Reproduce:

Install a version of PHP 7.2
Create a model that implements SoftDeletes
Attempt to delete an instance of the model
Notice the error count(): Parameter must be an array or an object that implements Countable

Hey
5.1 is no longer supported. I submitted a PR fixing this for 5.6

I thought 5.1 had support for another year still (because of the LTS). 5.5 should also be updated too I think, again, because it's an LTS release.

Yeah but it can be considered a breaking change for 5.5

I don't see how it'd be a breaking change. All of the doc blocks there hint it as an array, it's just not been initialised correctly. If it is a breaking change then the call to count can be changed to do a check for null first (and revert the change initialising the array)

This shouldn't be affecting 5.5 for what I've tested. We have tests for soft deleting feature (e.g. https://github.com/laravel/framework/blob/5.5/tests/Database/DatabaseSoftDeletingTraitTest.php) and the Continuous Integration builds for PHP 7.2 aren't failing: https://travis-ci.org/laravel/framework/builds
This indeed affects Laravel 5.1, but the support for bug fixes have been ended - just security fixes are being accepted. 👍

Thanks everyone.

If 5.1.x is LTS and doesn't support 7.2 then the documentation should reflect this page only says PHP >= 5.5.9 (and not PHP >= 5.5.9 < 7.2.0) which means it is promising something that is not being delivered...

Yes it does because when 5.1 was created PHP 7.2 wasn't even though about :stuck_out_tongue:

I understand that. I'm not suggesting it should support 7.2. Just that releases still being supported should at least tell users which versions of PHP aren't supported. That's not unreasonable.

I solved by changing "$originalWhereCount = count($query->wheres);" for "$originalWhereCount = is_null($query->wheres)
                     ? 0 : count($query->wheres);" in the function "callScope(callable $scope, $parameters = [])" in the file "/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php"

we are using Laravel 5.1.46 (LTS), PHP 7.2.4  (project is too large to upgrade)
any solution without changing core file/s ?

Thanks!!!


[R] error in file io

> mat = mx.nd.array(1:20)
> mx.nd.save(mat, 'temp.mat')
Error: could not convert using R function : as.list

@terrytangyuan You should fail the unit test in R. Let me fix this first.

@thirdwing Let us only support saving list of ndarray for now, and report error for single ndarray. As discussed with @hetong007

You can just wrap the single one in a list: https://github.com/thirdwing/mxnet/blob/master/R-package/R/ndarray.R#L36

Users might be confused if they saved an ndarray but got a list after loaded back.

As user will get confused by getting a list after loading back, so we can disable it for now.
Special treatment might could be done to encode a special list, say the first element is a 1x1 ndarray with key="ndarray_workspace", then the behavior indicates load ndarray back


when creating a snaphsot, restore and delete icons of other snapthots are not disabled

similar to #808
when a snapshot is being created, only that snapshot has delete and restore buttons disabled, others don't.

Duplicate of https://github.com/oVirt/ovirt-web-ui/pull/798 and fixed in https://github.com/oVirt/ovirt-web-ui/pull/798


Add more programs from COP 3514 Lectures

Need more programs from the Week 6 videos.   If you have any to add, please submit a pull request.

Week 6 is done!


Revert "Use css to center quick input (#163878)"

This reverts commit 40e7185033da52a465918bef7f7ac3bf43ae024e, which broke the monaco editor.
FYI @mjbvz
Before:

After:

Deprecated by https://github.com/microsoft/vscode/pull/173709


bug: Firestore emulation doesn't work with hot reloading

Describe the Bug
I think this may be an issue with sveltekit but since this repository represents the blend of sveltekit and firebase it seemed like an appropriate place to document the problem
I have a firebase.ts file configures a connection to firebase.  It connects to the emulator if it detects a development environment.  This works fine, but if the firebase module is edited while running in development mode / with hot module replacement it results in an error:
Firestore has already been started and its settings can no longer be changed. You can only modify settings before calling any other methods on a Firestore object.

Here is the code just for the record:
const firebaseConfig = {...};

// Initialize Firebase
const app = initializeApp(firebaseConfig);
const db = getFirestore(app);
if (env.NODE_ENV !== 'production') {
	console.log(env);
	console.log('Using Firestore Emulator');
	connectFirestoreEmulator(
		db,
		'localhost',
		8080,
	);
}

Steps to Reproduce

Create a sveltekit project using firebase + an emulator
Run npm run dev
Edit the module that sets up firebase file
Attempt to invoke a firestore transaction
See the error

Expected Behaviour
I would expect the firestore emulation configuration to continue to work.
svelte-adapter-firebase version
0.14.4
sveltejs/kit version
1.0.0-next.488

Understood if this ends up being considered irrelevant to this repository, but I thought creating the issue might help others.  At this point the only solution I could find is to manually restart npm run dev instead of relying on hot module reloading.


Please include our school Otto Hahn Gymnasium to your school license program

https://ohg-bensberg.de/
https://ohg-bensberg.de/index.php/unterricht/faecher/naturwissenschaften/informatik

@R00tBosbach I am sorry for a delay with processing your request.
Pull request merged. Thank you!


Add support for Jekyll 4.0

This is not a bug-report

Background
Jekyll 4.0 is planning to improve build times by caching parsed Liquid Templates.
Proposed Ideas: jekyll/jekyll#7136 (considerably stable) and jekyll/jekyll#7169 (WIP)
While the fundamental result of both PRs are more or less the same for Jekyll Assets, this ticket is just about jekyll/jekyll#7136.

Details
A known side-effect of jekyll/jekyll#7136 is that since a Liquid tag is initialized just once per given markup token, (i.e. {% asset foo.js %} in a template is going to create just a single instance of Jekyll::Assets::Tag irrespective of how many times the template is used.), the tag is going to render the same output if the data hash provided to it is cached as well.
Reference: https://github.com/aarongustafson/jekyll-webmention_io/issues/81#issuecomment-411419794
A similar observation was seen with {% seo %} where every generated page had the same metadata. The "issue" there could however be resolved with a simple diff:
def drop
- @drop ||= Jekyll::SeoTag::Drop.new(@text, @context)
+ Jekyll::SeoTag::Drop.new(@text, @context)
end

But, I was unable to pinpoint where the data hash or drop passed to the "asset tag" is cached and would like your assistance with it.

⚠ It's still  too early to ask plugin authors to test caching, when the new cache API is not well definded, let's hold on until a proper RC version is released. ⌛

Like I mentioned in the ticket body, this is not about the WIP Cache API but strictly in context of my PR jekyll/jekyll#7136 ..

Same rule applies, wait for a beta or RC release before contact plugins authors about possible changes.

I'm confused as to what's going on, and since I can't ask for clarification on Jekyll, you'll have to clarify here.  We provide our caching, and have no plans to rely on Jekyll for caching (in that we won't ever rely on Jekyll for caching,) if this is about tag caching you'll need to elaborate a bit more.
As for why our drops, and tags, and filters are confusing, it's because they're all the same thing to Jekyll-Assets, we take KISS, and shared code to the max around here, if you can show me an RC once it's available, I'll happily see about working with Jekyll Tag caching (though that wont help us much since we already optimize around that internally.)

@envygeeks Thank you for responding to this ticket. I'll get back to you once Jekyll ships a v4.0.0.rc

I know this is not a priority right now, but I just want to inform you that this currently breaks Jekyll master branch.

@nhoizey Since Frank and I have already asked Jordon to wait till Jekyll ships a beta or rc, Can we move this discussion to your blog's repository..?
Thanks.

@ashmaroli Keeping me in the dark, and then expecting me to rush changes is not going to work out that well. I'm a single developer, to your team, so if you have information it's best to share it early, instead of expecting rushable changes that only push the blame onto me.
@nhoizey do you have any errors you can supply? Or debug logs.

@envygeeks does previous comments and https://github.com/ashmaroli/jekyll/blob/master/docs/_docs/upgrading/3-to-4.md#template-rendering help?

@envygeeks I don't have any error during build, I have an issue with the result of the build.
Like before in https://github.com/aarongustafson/jekyll-webmention_io/issues/81#issuecomment-411419794 I get the same content in the resulting HTML for all assets.
I don't know how @ashmaroli then fixed this issue for the jekyll-webmention_io plugin.
I can give you any log you want, if it helps.

It's fixed.

@nhoizey To clarify, I did not fix a similar issue in jekyll-webmention_io.. You have misunderstood..
@envygeeks I did not intend to keep you in the dark. That's why this ticket was still open. I was just respecting Frank's request to wait till Jekyll ships a 4.0.0.pre..

The changes have been picked into 3.0-current, and released as v3.0.12.  Good luck.

Thanks for the quick response, Jordon :smiley:

Thanks a lot Jordon, I'll try a build ASAP!

I confirm that this works perfectly with both Jekyll 3.8.5 and master branch, thanks again @envygeeks !


Cant install

Version 1.4.0
Tell us which versions you are using:
react-google-charts ?.?.?
react v0.?.?
Expected behaviour : try to install npm i -s<EMAIL_ADDRESS>Actual behaviour
+-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| --<EMAIL_ADDRESS>-- UNMET PEER DEPENDENCY<EMAIL_ADDRESS>Steps to reproduce

npm i -s<EMAIL_ADDRESS>
Link to a git repo that reproduces bug :

Please try : npm i -s<EMAIL_ADDRESS>

I got the same error

Got the same error today, since I was using node v6.7.0 nvm I ran
nvm install node --reinstall-packages-from=node
That bumped me up to v7.7.2 which made npm i -s<EMAIL_ADDRESS>work.
Hope it helps


macOS: Only use the LLVM-bundled clang for code generation

This fix is included in #1017/#1026 but the scope continues to grow and I'd like this simple fix in. This resolves the error seen on latest AppleClang:
Reading input 'bytecode_handlers_ir.bc' ...
Parsing into LLVM Module ...
Error parsing bytecode handler bitcode file: Unknown attribute kind (60) (Producer: 'APPLE_1_1<IP_ADDRESS>_0' Reader: 'LLVM 8.0.1')

We only want to use the LLVM-bundled clang for code generation.

Seems to be an issue with compiled mode now. Not sure where to start on debugging that.

Release mode on macOS passed, but debug mode seems to get duplicate output from check-tpl:
http://jenkins.db.cs.cmu.edu:8080/blue/organizations/jenkins/terrier/detail/PR-1029/1/pipeline
@lmwnshn @tanujnay112 @amlatyrngom @pmenon Any guesses where to start debugging this?

It's failing in JIT mode for 'Assertion failed: ((symbol.getAddress().get() != 0) && ("Resolved symbol has no address!")), function findSymbol, file /Users/matt/git/terrier/src/execution/vm/llvm_engine.cpp, line 78.\n'

Putting this here as I try to pull myself back out of rabbit holes:
https://github.com/google/sanitizers/issues/1086
Will revisit this later.

Redundant.


Implement trait_newly_sealed new lint

Should contribute to  #870 by adding trait becoming newly sealed lint. Welcome any feedback as I am by no means a rust expert and first time contributor here.
Edit: Not sure if there is a standard for the reference_link, as sealed traits didnt have a specific section. Also not sure if i am missing any cursed sealed impls, but welcome any newer ones that should be added.
Thanks!

Also not sure if i am missing any cursed sealed impls, but welcome any newer ones that should be added.

The current test cases are great. We really want to catch cases where the query in the lint might have a typo or a bug. If the engine running the query has misclassified a trait as sealed when it isn't (or vice versa), that's an upstream bug not a bug in the lint itself. We already have a large test suite of cursed sealed and "can't believe it's not sealed" trait patterns specifically to ensure our analysis of whether a trait is sealed remains accurate.
This is one of the advantages of using Trustfall for a linter: you don't have to be an expert in "what are all the ways to seal a trait" in order to lint for sealed traits! We've already plugged in that knowledge into the query graph, and now it's accessible at the low low cost of writing a query 😁

Excellent work — merging right away 🚀
Thank you for contributing 🙌

Thanks so much for the encouragement on 'X', and the awesome code. Hope I can contribute further either here or TrustFall if there are issues which are not at "expert" levels. :D Looking foward !


Remove Reactor (Mono) and use CompletableFuture

Describe the proposal
Before Project Reactor, I used CompletableFuture for async programming in Java. When writing the first complete version for this SDK, Project Reactor was the recommended async programming model - it was (probably still is) used by the Azure's Java SDK.
Based on my experience in the last few years and a few in person conversations about Project Reactor, I would like to propose this SDK to move into using CompletableFuture. For me, my biggest problem with Project Reactor is how it completely changes the programming model for Java, having a sub-syntax of its own, while also forcing apps that don't want to use Project Reactor to have this dependency forced on them if they want to use Dapr with Java. It means a new interface, not depending on Project Reactor at all, keeping the existing implementation for 2 releases (deprecation path for the Dapr Project).
For projects that depend on the current interface and don't want to change any code (like wrapping CompletableFuture into a Mono object), we can still offer the existing interface via a new artifact (dapr-sdk-reactor, or some similar name).
In summary, these are the benefits for this change (in order of importance):

Apps that don't want to use Project Reactor, will not be forced to use it or even have it as a dependency.
Apps that want to operate as-is, will still have a path forward, requiring just to add a new dependency to their pom.xml file and all the CompletableFuture interfaces will be available as wrapped inside a Mono.
Lower barrier of entry to contribute, since people that are not familiar with Reactor can contribute without having to re-learn a new "language".
Simplify the SDK's code readability and debugging.

What does the community think about this change? Please, react (pun not intended) to vote:
👍 We need this ASAP.
👎 Let's keep it as-is today.
😕 Need more time to think.
PS: I know this can be a controversial proposal as I have heard passionate opinions both ways on this matter.

One thing that I would like to mention, is compatibility with Spring Boot 3.x.. whatever we do, we should try to follow their lead to make sure that we don't go to a place where Spring Boot users find issues because we choose to use something that will not work with that stack.

@artursouza I really like idea. One thing I would like to mention is that we should probably use CompletionStage instead of CompletableFuture. Depending on an interface is always easier to test and we could potentially have our own optimized CompletionStage implementation if required, for whatever reason.


New version: Harmonoid.Harmonoid version <IP_ADDRESS>

Result: Installation Successful

Manifest
Add/Remove Programs

Name
Harmonoid
Harmonoid version <IP_ADDRESS>

Version
<IP_ADDRESS>
<IP_ADDRESS>

Publisher
Hitesh Kumar Saini
Hitesh Kumar Saini

ProductCode

{C2D0837C-0DBE-432B-865E-53C092A56DFB}_is1

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 1490
Microsoft Reviewers: Open in CodeFlow

Sorry for the problem. 🙏🙏🙏
Fixing in a while.


Migrate Twitter to X | optimize icons

Changes

Migrate Twitter to X
Optimize icons with ImageOptim (saves 11KB!)

Testing

Check iconography page in PR preview for X icon.


Polyline.remove() dos not work

When I add a line to the map and then delete it (as indicated in documentation) the line remains on the map.
ArrayList<LatLng> firstRoute = google_roads.get(0);

PolylineOptions routeOptions = new PolylineOptions();

for (int i = 0; i < firstRoute.size(); i++) {
    routeOptions.add(firstRoute.get(i));
}

// Get back the mutable Polyline
mRoadPolyline = mGoogleMap.addPolyline(routeOptions);

....

// try to remove line - line still on the map
if (mRoadPolyline != null) {
            mRoadPolyline.remove();
            //mRoadPolyline = null;
            //mRoadPolylineOptions = null;
            Log.d(TAG, "clearRouteForGoogleMaps() -> remove()");
}

Android info:
compileSdkVersion 26
buildToolsVersion '26.0.2'
minSdkVersion 16
targetSdkVersion 26 (run on Android 4.4.2)
Package info:
com.google.android.gms:play-services-maps:11.0.2

If I clear the whole map,
mGoogleMap.clear();
the line disappears, and, respectively, the markers. I really do not want to use crutches in the application (clear the entire map -> re-draw markers)

This would be a bug with the SDK rather than this util lib. Please open a bug in the issue tracker:
https://issuetracker.google.com/savedsearches/5446940


Add user-specified memory management to all "context" data

Resolves #61.

Heads up @paulyoung and @kastiglione that this will be a breaking change for bindings—but one that will probably make them easier to implement!


New version: Box.Box version 2.41.226

Created by 🥟 Dumplings in workflow run #9143.

Log
Updated: 2.40.333 → 2.41.226
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

@wingetbot run


HTTP response headers don't seem to be getting captured

We definitely capture request headers in request.headers.txt but don't seem to capture the response headers.

Accidental dupe due to my impatience.


functional: call systemctl is-enabled instead of list-unit-files

TestSingleNodeConnectivityLoss has been so far retrieving is-enabled status by calling "systemctl list-unit-files UNITS". It was expected to get "enabled" for each unit. This has worked until systemd v227. However, that's not the case any more since systemd v228, precisely since https://github.com/systemd/systemd/commit/0ec0deaa30d0e68430f03fa6f32affa576481d18 ("install: follow unit file symlinks in /usr, but not /etc when looking for [Install] data"). Since then, systemctl list-unit-files returns "linked-runtime" status for each fleet unit, which is actually reasonable behavior for units that are not installed persistently under /etc/systemd.
With systemd v228 or newer, however, TestSingleNodeConnectivityLoss in fleet functional tests cannot make use of "systemctl list-unit-files" any more. And it would not be optimal to simply change "enabled" to "linked-runtime", because then the test couldn't work with systemd < v228.
So let's work around it, by calling "systemctl is-enabled UNIT" instead. That command has returned correct status "linked-runtime", no matter whether systemd >= 228 or not.
Fixes: https://github.com/coreos/fleet/issues/1588

I just updated minor things: s/break/continue, and fixing a comment.

If no one objects, I'd like to merge it tomorrow. Actually this is a critical one, as systemd v228 has been already around since many months.

Merged. Thanks.


String parsing crash with manual generator flutter_i18n/flutter_l10n/

Hello,
I add flutter_l10n to my pubspec.yaml to allow my team with others IDE as AndroidStudio or Intelij to generate translation.
So I add this :
 l10n_generator:
    git:
      url: https://github.com/long1eu/flutter_i18n
      path: flutter_l10n/

My team can run the package with the following commande :
flutter packages pub run l10n_generator:main -o lib/generated

But their is a problem which wasn't present when we use flutter_i18n plugin directly on the IDE :
In my arb file I have string like :
"appMessage": "The message... Blabla ...\n Blabla.",
When using generator manually, string parsing fail on the \n  and I got this following string on generated/i18n.dart :
String get appMessage => "The message... Blabla...

To continue benefiting from a fully functional App";

As you can see, the \n was interpreted and broke all the processus...
Can you fix it please :) ?
@noordawod

I have the same,
I'm using Android Studio 3.5.3 on Windows and i18n.dart doesn't generate automatically (while my mac is OK). I've run AS by addministration privillage but have problem.
And finally use manual generator and face the issue @EArminjon had mentioned.


Prevent XSS attack in azure function app c#

Hi Team,
How to prevent xss attack in azure function app with c# while accessing swagger endpoint.
Currently I am using

Hello @raiajithkumarr ... This isn't the best spot to ask general questions. This is a working repo for documentation issues. Your best bet is to ask on a public support forum. We recommend ...

Stack Overflow
ASP.NET Core Slack
ASP.NET Gitter


Uglify throws an error when using '`'

Hello!
I use ` (replaced with ? in error log {Github doesn't like it either!}) for multi-line text in JS, but gulp-uglify doesn't seem to like it :(
Error: /-----min.js: Unexpected character '?']   message: '/-----min.js: Unexpected character \'?\'',   fileName: '/-----min.js',   lineNumber: 16802,   stack: 'Error\n    at new JS_Parse_Error (...)
Here's a code example that seems to cause this issue:

var text = `<div onclick="runMe('V1'); return false;"...`;

Thanks for your help :)

Thanks for using gulp-uglify 💖 !
The currently releases version of UglifyJS doesn't support any ES6 or later language features. The UglifyJS project is working hard on adding them.
You can still use template strings, you just must first convert them to ES5 code, such as by using Babel.
Hopefully this helps, if not fill free to leave a comment.

Hello :)
Which Babel Preset should I use?
Thank you!
-Looking forward to es6 in UglifyJS :)

Found it: es2015
Thanks and keep up your work :)


security: fix CVE-2023-45288

This is a PRIVATE issue for CVE-2023-45288, tracked in http://b/319262343 and fixed by http://tg/2130527.
/cc @golang/security and @golang/release

@gopherbot please open backport issues for this security fix.

Duplicate of #66297

We accidentally opened a duplicate issue for this: #66297. Closed that one in favor of keeping the original issue.
Current status: This is the main issue for CVE-2023-45288.
#65387 is the 1.21 backport
#66298 is the 1.22 backport
#65386 was the 1.20 backport, obsolete because we missed the 1.20 window.

@neild @dmitshur Will there be an updated tag released for golang.org/x/net as well?

@geofffranks There will be a new golang.org/x/net tag with the fix in CL 576155 included, soon.

Is this an http2 vulnerability, or is HTTP also vulnerable?

Is this an http2 vulnerability, or is HTTP also vulnerable?

HTTP/2 only.

Can someone please clarify something for me? I have a Golang project that relies on net/http and has golang.org/x/net in its go.mod file.
Is it the case that moving my project to Go v1.21.9 is sufficient to address this issue? Or do I ALSO need to run go get -u<EMAIL_ADDRESS>

It is sufficient, unless you are directly importing the x/net/http2 package and using it to initialize HTTP2 servers.


Confusing pinning error exposing CFG internals

Input
→ View on sorbet.run
def bar
  "bar"
end

class A
  extend T::Sig

  sig {params(x: Integer).returns(String)}
  def foo(x)
    if x == 0
      T.let(bar, String)
    else
      "a"
    end
  end
end

Observed output
editor.rb:13: Incompatible assignment to variable declared via `let`: String("a") is not a subtype of NilClass https://sorbet.org/docs/error-reference#7001
    13 |      "a"
              ^^^

editor.rb:9: Returning value that does not conform to method result type https://sorbet.org/docs/error-reference#7005
     9 |  def foo(x)
    10 |    if x == 0
    11 |      T.let(bar, String)
    12 |    else
    13 |      "a"
    14 |    end
    15 |  end
  Expected String
    editor.rb:9: Method foo has return type String
     9 |  def foo(x)
          ^^^^^^^^^^
  Got T.nilable(String) originating from:
    editor.rb:9:
     9 |  def foo(x)
          ^^^^^^^^^^
    editor.rb:11:
    11 |      T.let(bar, String)
              ^^^^^^^^^^^^^^^^^^
Errors: 2

Expected behavior
Ideally this is not an error, or there is a better error message.

The "variable declared via T.let in the message is misleading; it's referring to a CFG temp variable that we synthesize to hold the return value. It just happens that in one of the assignments (there are multiple because there's a branch) into this temp we "pin" it accidentally because there's a T.let in that branch.
Originally reported by @danj-stripe

Simpler test
https://sorbet.run/#%23 typed%3A strict

a %3D []
a %3D T.let(['a']%2C T%3A%3AArray[String])


Limit fanouts to the number of active peers, Credit: Equilibrium

Motivation

Zebra fans out getaddr, getdata, and mempool messages to 3 peers. But this is useless when we only have 1-3 ready peers. This mainly happens on testnet, but it can also happen on busy mainnet nodes.

When Zebra sends a request, it stops the peer connection being used for other things, until a response or request timeout. This can really slow down the node, because those connections can't be used for syncing. We can observe these timeouts using waiting for the peer service to become ready logs.

Scheduling
We should try to fix the underlying PeerSet bugs first, and then see if Zebra still has hangs.
This is a complex refactor, so we should avoid doing it unless we are sure it is needed. Instead, we should try to find easier fixes for the underlying PeerSet issues.
We should re-evaluate the risk as part of the lightwalletd work.
Solution
Refactoring
This depends on the refactoring done as part of #3230.

[ ] Add a PeerSet::route_fanout method, that routes a request to multiple peers. The fanout number should be limited to the number of ready peer services (should it be ready and unready peer services?)
[ ] Refactor existing fanouts in different places to not perform a manual fanout, and make the PeerSet decide which requests to fanout

Existing fanouts

[ ] GetAddr fanout in the candidate set

[ ]  Restore this fanout to 3 as part of this change

[ ] GetData fanouts in the syncer

[ ] obtain tips
[ ] extend tips

[ ] MempoolTransactionIds fanout in the mempool crawler

Tests

[ ] proptest to see if fanouts go to the correct number of peers
[ ] proptest to see if the PeerService recovers from a fanned out request (i.e., the peers handling the fanned out requests become ready again. We might need to fanout multiple times until we know we have sent at least one request to each peer, and then check if the PeerSet becomes ready after a while)
[ ] proptests to see if the PeerService handles errors during fanout requests

[ ] returns an error if all responses to fanned out request are errors
[ ] returns at least one response if at least one fanned out request succeeds

Alternatives
The foundation could run some Zebra or zcashd nodes on testnet, to increase the number of available testnet peers.
Put a watch channel in the peer set that is updated with the total number of connected peers (ready and unready), pass that channel to the crawler and syncer, and use it to limit their fanouts.

Before starting this ticket, we need to decide on the best design for this ticket, because the suggested design is a lot of work.

Zebra has a large number of peers connected on mainnet, so it is unlikely we will send any of the 3 fanout requests to the same peer. We also made changes that make sure a broadcast only goes to half the peers, which means there are always peers available.
(This issue really only happens on testnet.)


Create a minimist wrapper that validates a schema

It'd, upon a false by default throwOnUnexpectedFlag, throw if you define {boolean: ['version']} and the program is called with --testing

This issue was moved to zeit/now-cli#770


Improve Auto-Arrange function of pipeline canvas

Is your feature request related to a problem? Please describe.
Larger pipelines get overwhelmingly confusing. The auto-format feature then is not handy anymore as it arranges all nodes horizontally or vertically.
Describe the solution you'd like
Introduce a "line break" where nodes get arranged horizontally until a certain (configurable) with is reached, then it automatically starts in the next row and so on
Describe alternatives you've considered
Automatic horizontal arrangement of all elements, then move blocks around...
Additional context

@ptitzler mni tnx!

@lresende
Elyra canvas provides a basic horizontal (and a vertical) auto-arrange algorithm but more application specific auto-arrangements don't necessarily have to be implemented inside Elyra canvas.  The host application, in this case Elyra, can calculate whatever x and y co-ordinates it wants for the nodes, based on its own layout algorithm, and then feed them to Elyra canvas either in the pipeline flow document or by calling the CanvasController API to set node positions individually.
The general guidance for adding function in to Elyra Canvas should be we add things:

when a feature is required by more than one host app team
when a feature cannot be implemented by a host app developer. e.g. direct manipulation gestures

So in this case, unless other teams want the exact same type of auto-arrange I think it should be implemented outside of Elyra Canvas.

I opened this issue for this: https://github.ibm.com/NGP-TWC/wdp-abstract-canvas/issues/3104


Support PagedList

Do you plan to support PagedList?
Or sth similar which allows to load Data from the Database (in my case with Room) step by step.
Android Paging Library Overview

+1 here, support for PagedList along with leaving beta stage for the LiveData extension lib would be awesome


Is this repo still maintained?

The last commit date is 28 Mar 2014. And 13 pull requests  stayed lonely for long long time.

It is maintained but for bugfixes only.


Check for material when getting the node_tree

Fixes #1846
This PR adds a check to make sure the material slot is not empty when checking for its node_tree.

 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.


Trailing 0s are lost when typecasting is done to float

Go Version: go version go1.14.2 darwin/amd64
Does this issue reproduce with the latest release? Yes
For float64 values like 0.0 or 1.0 etc. values loose trailing 0s when declared as interface and typecasting is done.
Eg.
var x interface{}
x = 1.00
fmt.Println(float64(x.(float64)))
Expected output here is 1.00 however, output is 1. Missing trailing 0s for such numbers.
When such data is Json marshalled same thing happens. When this marshalled data is consumed, unmarshalled and loaded in Parquet which is a schema on write format there is an inconsistency because of this issue.
Expectation is when float64 typecasting / json marshalling is done it should return  float value without stripping decimal precision even if it's 0.

Languages like python do maintain such precision even though there are 0s after decimal.

This is how floating point values are converted to text by default - it is unrelated to interfaces.
Please check https://pkg.go.dev/fmt for details on formating floating point values.
You can try this example to experiment with formating: https://play.golang.org/p/q0aWVhkWtlb
f := 1.0                // float64
fmt.Println(f)          // 1
fmt.Printf("%v\n", f)   // 1
fmt.Printf("%f\n", f)   // 1.000000
fmt.Printf("%.2f\n", f) // 1.00

This is not a bug with Go. If you have any questions, please follow up on the golang-nuts mailing list.

Primary issue is when json marshalling is done. This loses the precision and when unmarshalling is done there is no way to determine if such value is int or float.

In json, all numbers are floating point

Agreed on json part. However, why can't this maintain 1.0 in json.Marshal?
This is the case in Python. As mentioned this kind of stuff creates issue in Parquet which is a schema on write format. It can not differentiate between floats and ints. If value is maintained as 1.0 Parquet can determine it's a float value.

However, why can't this maintain 1.0 in json.Marshal?

can you write a program that demonstrates the problem?

why can't this maintain 1.0

Floating point 1, 1.0, and 1.00 are all identical. The number of decimal digits provided is not stored in floating point - there is nothing to maintain.
As pointed out above, all JSON numbers are floating point, 1 and 1.0 must be parsed into the same floating point value. Relying on anything else is not compatible with JSON.
I'd recommend asking about the underlying problem you are trying to solve on a more appropriate forum. Please see https://github.com/golang/go/wiki/Questions

Golang
package main

import (
	"encoding/json"
	"fmt"
)

type employee struct {
	Name string
	Stocks float64
}

func main() {

	e := employee{"name1", 30.0}

	fmt.Printf("%+v\n", e)
	data, _ := json.Marshal(e)
	fmt.Println(string(data))
}

Output
{Name:name1 Stocks:30}
{"Name":"name1","Stocks":30}

Python
import json

dict = {
    "Name": "name1",
    "Stocks": 30.0
}

print(dict)

d = json.dumps(dict).encode('utf-8')
dec = json.loads(d.decode('utf-8'))
print(dec)

Output
{'Stocks': 30.0, 'Name': 'name1'}
{u'Stocks': 30.0, u'Name': u'name1'}

Sample program to illustrate this. Json marshal of float value is not printing the decimal value if it is whole number like show in python and that's the case in most of the languages.
Because of this up stream big data system like in case of parquet which are deriving the schema from Json will look at the first value and will start thinking it as int rather than float. When it receives the subsequent Json with float values like 30.001, then it will convert that as float; which creates inconsistency in the schema.

I'm not sure "most languages" keep trailing period for floating point numbers which represent integers. Javascript is a notable exception..
> console.log(1.0)
1

Go JSON marshalling has previously been changed to encode floating point numbers similar to Javascript (#6384, #14135).
Interpreting JSON numbers as different types depending on formatting is fundamentally fragile (or really, anything other an a float64). JSON is a limited serialisation format - it does not offer an "integer" type. I would recommend more robust solutions:

Using a more expressive serialisation format (eg, Protobuf)
Using a fixed JSON schema (eg, field F should always decode as float64 - no auto-detection), or
Encoding the type separately in JSON. Eg: {"my_field": 1, "my_field_type": "float"}. json.Number can also be useful to represent numbers as a string. This way a field can represent the full range of float64/int64 values (or larger).

However, you can override Go formatting with a custom type if you need to interact with an (arguably buggy) JSON consumer that guesses the type based on formatting:
type foo struct {
    Num  floatFrac
}

type floatFrac float64

func (f floatFrac) MarshalJSON() ([]byte, error) {
    n := float64(f)
    if math.IsInf(n, 0) || math.IsNaN(n) {
        return nil, errors.New("unsupported number")
    }
    prec := -1
    if math.Trunc(n) == n {
        prec = 1 // Force ".0" for integers.
    }
    return strconv.AppendFloat(nil, n, 'f', prec, 64), nil
}

func main() {
    buf, _ := json.Marshal(&foo{Num: 1})
    fmt.Printf("%s\n", buf)
    // Output: {"Num":1.0}
}

Closing old issues that still have the WaitingForInfo label where enough details to investigate weren't provided. Feel free to leave a comment with more details and we can reopen.
Also, see https://golang.org/wiki/Questions.


Output nan in the table when fitting fails

This comes after #18
The ValueError that is raised by the Simplex minimizer in problem WISH17701 panel 103 tube 3 calibration, peak 9 1 is now caught and a nan value is outputted in the table.
To test:

In example_runScript.py make sure

minimizers contains 'Simplex'
run_data = 'neutron'

Run example_runScript.py in the mantidpython terminal
Check the table comparison_weighted_v3.8_acc_nist_lower.html under column Simplex, last row, should display nan

Notes:

The table name is wrong, this is a known issue, changing it to neutron causes a crash #22 .
This only catches RuntimeErrors and ValueErrors, if the fit algorithm returns any other kind of error, the problem is still there. Doing an except that catches everything is generally bad practice so I refrained from doing so here. In this case, other kind of error should be added as they are discovered.

@Anders-Markvardsen  and @bb511 I just ran this and found that the comparison_weighted_v3.8_acc_summary.html (and the runtime summary) did not work. Do we have an issue for this?

Just checked, don't think we do. I will create one today.

@bb511 is this the bit of code you commented?
Other than that just move the function and I am happy with it

Yes, that would be the bit I commented.


Cache values used for jump instructions

TITLE
Description
Description of the pull request changes and motivation.
Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.
[ ] CHANGELOG has been updated.

Didn't work. Doesn't really speed up calculations unless using a Vec, and adding it would only hurt performance on bigger programs.


set n0 step count after building transformer

Why?

Why?

because the code currently sets steps to 0 in the event of -n not being set  or <= 0
and
fprintf(stderr, "  -n     number of steps to run for, default 256. 0 = max_seq_len\n");
says we should do otherwise.  which is more reasonable.

I proposed the same in PR#327. @karpathy merged it but decided not to keep -n 0 as a request to have the max seq length. (at the moment is my last message on the Discord channel) :)

okay. Then here is another simple chance for him to decide that which he would prefer.
A reasonable person might expect to not have to know how many steps to allow. :)

Yep, sorry I didn't read your first comment in full and did not get it .
If you have a look at my PR, I proposed these check to be closer to the loop that generates the text so to be ready for the "chat mode".  I guess will come to something similar in due time.

pushed fix, closing.


Initial xDS Translator Design and Implementation

https://github.com/envoyproxy/gateway/pull/16 specifies the need for an xDS Translator (XT) to translate IR resources to an xDS config. The XT details should be captured in this issue or a linked doc.

@skriss I assigned this issue to you based on the 5/24/22 community meeting notes. Please unassign yourself if that's not the case.

@skriss I assigned this issue to you based on the 5/24/22 community meeting notes. Please unassign yourself if that's not the case.

Removed my assignment, I'm going to focus on #32 and #38 to start. Happy to circle back to this later though if nobody has picked it up.

Fixed by https://github.com/envoyproxy/gateway/pull/123


Removed <> from ElementsShouldBeAtLeast and ConditionAndGroupGenericParameterTypeShouldBeTheSame

Check List:

Fixes: Removed <> from ElementsShouldBeAtLeast, ConditionAndGroupGenericParameterTypeShouldBeTheSame,
ElementsShouldBeAtLeast, ElementsShouldBeAtMost, ElementsShouldBeExactly  (see #2091)
Unit tests : YES
Javadoc with a code example (on API only) : NA

Integrated thanks @himadri-mandal!
I have added ElementsShouldHave, used two spaces for indentation but you get all the credit :wink: .
One thing, it's better for us if you rebase your PR on main instead of merging main so that the history does not show branches but simple commits

Integrated thanks @himadri-mandal!
I have added ElementsShouldHave, used two spaces for indentation but you get all the credit :wink: .
One thing, it's better for us if you rebase your PR on main instead of merging main so that the history does not show branches but simple commits