An important reminder to people who might plan potential attacks against the Piston project as a joke

Lately, the Piston project has experienced several potential security threats due to suspicious activity. It is suspected that some of these incidents are politically motivated.
Due to the risk of attracting more attackers, perhaps of desire to achieve status (perhaps as a "black hat") or because of a belief that "people on their side" (political motivation) see the Piston project as a target, I (@bvssvni, leader of the Piston project) have to remind potential attackers of the following:

Criminal acts against people or property do not fall under the policies of the Piston project, but under the jurisdiction of legal authorities for that respective country which the person/people involved reside.
There is nothing the Piston project can do to prevent or stop non-proportional retaliation from legal authorities. None. People working under the Piston project might report incidents to legal authorities if they feel threatened or violated, e.g. by attacks intended to intimidate or destroy property. If the attack is reported to legal authorities and the identity of the attacker is revealed, the attacker must be prepared to face legal consequences. In particular, politically motivated attackers have high risk of making irrational judgements about the expected consequences of their actions. For example by cognitive bias that "people think like me so I'm safe" or that they only expect that their target will be the one to expect potential retaliation from.
Since the Piston project hosts development of some widely used libraries, any attack might be seen as a potential threat to the security infrastructure of outside actors. This includes potentially large and powerful institutions like governments in various countries, military forces or intelligence agencies. For example, the attacker might make a judgement about the security analysis of the Piston project, but forget that outside actors run their own analysis where any attack might be considered coming from a military enemy. This means that the identity of the attacker might have higher chance of getting revealed than for usual targets, leading to higher risk of legal consequences for the attacker and more severe consequences if there is suspected evidence of aiming at such institutions.
Therefore, it is strongly recommended, to remind, in particular for people with a history of mental illness or otherwise might have chronic or episodic impaired cognitive function: Do not attack the security structure of the Piston project for any reason. For example, a person might view the act of attacking the Piston project as a harmless joke, but even if some people working here might find it amusing, it is not certain that everybody will find it funny. In particular, if the attacker commits a criminal act or create suspicious activity that might be viewed as a security threat to powerful institutions like governments in various countries.

Per security analysis of today, any attack will very likely have none or little consequence to the Piston project, except time delay. Therefore, it is expected that most attacks will be irrationally motivated in case they seek to harm this project. The most expected category of attackers are people who are mentally ill, politically motivated, or both, in which mental state there is a higher risk of making irrational choices.
It is very unlikely that large institutions or organizations will view the Piston project as a threat, but e.g. viruses and malware in widespread targets or aiming for such organizations might accidentally also be targeting property of people working under the Piston project. For this reason, security agencies might be monitoring public logs and reports to detect potential threats to their own infrastructure.
The attacker might face non-proportional consequences that they did not consider when planning the attack. This depends on whether criminal acts are made against individuals, or outside actors that consider an attack as something to investigate for security reasons.

Closing since there are no signs of this kind attack. Apparently it's just bots.

You may want to reconsider posting things like this without doing prior research: you're going to scare off a LOT of developers.


[demo] fix bug in incomming predict

The config for this demo is inconsistent. The used model is additive_model_with_dynamic_buckets which specify the output to ${additive_model_name}. However, eval_testing and eval_training read model from ${spline_model_name}. This PR fix this bug so that they are consistent.
The model_output entry in train_model is not used at all, so it's removed.

LGTM

👍


docs: Add alt text to images

Add alt text to images in docs roughly stating the contents of the
image.

Part of #15948
Testing Plan:
GIFs or Screenshots:

Merged, thanks @gr455!  A useful follow-up might be to rename a lot of those 002.png files in the integration docs to names like 002-plugin-configuration.png for better readability.
@punchagan FYI as we might want to also modify our tooling for generating screenshots to use a cleaner naming scheme while we're thinking about this.


Feature/non linear spine items

introduces navigation history (breadcrumb) too, as the "return to primary reading flow from ancillary document" feature is built upon the same mechanism.
Fixes:
https://github.com/readium/readium-shared-js/issues/149
https://github.com/readium/readium-shared-js/issues/26
See:
https://docs.google.com/document/d/1XY4SL0hwcr4b6XvCw8yf9tKQMnDXDnjKs_MDEzPKTHc

ACTION:  Under active development Daniel owns this.


fix: IDs XML target URL

This is an hotfix for #378 , as I understood this issue is blocking from releasing a new draft
The issue behind having the malformed URL for some IDs is still under investigation.

The draft in question was unblocked by another workaround, so I don't think an error-masking hotfix is the right approach.
I'm curious - why is this line the way it is, and is this the source of the errant value?
https://github.com/ietf-tools/bibxml-service/blob/31dc5f297ad8be097e6f861fc248c386b74cd914/datatracker/internet_drafts.py#L175


QML2_IMPORT_PATH is not set by package qtquickcontrols2

Issue description
The package qtquickcontrols2 does not set QML2_IMPORT_PATH, so the qml files cannot be found.
workaround
export  QML2_IMPORT_PATH=$QML2_IMPORT_PATH:$(nix-env --query --no-name --out-path  qtquickcontrols2)/lib/qt-5.9/qml

Steps to reproduce

install qtquickcontrols2

Write this to test.qml
import QtQuick.Controls 2.2

Page {
    id: page
    hoverEnabled: true
    Label {
        text: "Hello QtQuick.Controls 2"
        font.pixelSize: 100
        font.italic: page.hovered
    }
}

open qmlscene test.qml

Technical details

System: (NixOS: 17.03.1623.138313fe01 (Gorilla)
Nix version: nix-env (Nix) 1.11.13
Nixpkgs version: nix-env (Nix) 1.11.13 and 17.09pre-git
Sandboxing enabled: build-use-sandbox = true

I've written a better script for setting QML2_IMPORT_PATH. In nix-shell, the environment variable CMAKE_PREFIX_PATH can serve as input.
#!/usr/bin/env bash

# Source this file to set QML2_IMPORT_PATH
# We use information from CMAKE_PREFIX_PATH

# read the setting for nullglob ('on' or 'off')
nullglob=$(shopt nullglob | cut -f 2)
# turn on nullglob
if [ $nullglob = "off" ]; then
    shopt -s nullglob
fi

QML2_IMPORT_PATH=
for v in $(echo "$CMAKE_PREFIX_PATH" | tr : '\n' | sort | uniq); do
    list=($v/lib/*/qml)
    for f in "${list[@]}"; do
        if [ -z "$QML2_IMPORT_PATH" ]; then
            QML2_IMPORT_PATH=$f
        else
            QML2_IMPORT_PATH=$QML2_IMPORT_PATH:$f
        fi
    done
done
export QML2_IMPORT_PATH

# turn nullglob back to the initial value
if [ $nullglob = "off" ]; then
    shopt -u nullglob
fi

[ $nullglob = "off" ] is exactly backwards. off can't possibly need to be quoted -- it's a constant. "$nullglob" should be quoted so it's correctly parsed as exactly one word, even if it somehow doesn't include one of the expected single-word values.

It seems that this issue still exists.


Refactor: Node connection statuses as constants

Also your refactoring is completely changing the design of networks page, where the goal was to show the connection status right underneath the network name.

The popup doesn't have connection status and both buttons deny accept are missaligned.


[SPARK-47305][SQL][TESTS][FOLLOWUP][3.4] Fix the compilation error related to PropagateEmptyRelationSuite

What changes were proposed in this pull request?
https://github.com/apache/spark/pull/45406 has been backported to branch-3.4, where the newly added test case in PropagateEmptyRelationSuite uses DataTypeUtils, but DataTypeUtils is a utility class added in Apache Spark 3.5(SPARK-44475), so this triggered a compilation failure in branch-3.4:

https://github.com/apache/spark/actions/runs/8183755511/job/22377119069

[error] /home/runner/work/spark/spark/sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/PropagateEmptyRelationSuite.scala:229:27: not found: value DataTypeUtils
[error]     val schemaForStream = DataTypeUtils.fromAttributes(outputForStream)
[error]                           ^
[error] /home/runner/work/spark/spark/sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/optimizer/PropagateEmptyRelationSuite.scala:233:26: not found: value DataTypeUtils
[error]     val schemaForBatch = DataTypeUtils.fromAttributes(outputForBatch)
[error]                          ^
[info] done compiling
[info] compiling 1 Scala source to /home/runner/work/spark/spark/connector/connect/common/target/scala-2.12/test-classes ...
[info] compiling 25 Scala sources and 1 Java source to /home/runner/work/spark/spark/connector/connect/client/jvm/target/scala-2.12/classes ...
[info] done compiling
[error] two errors found

Therefore, this PR changes to use the StructType.fromAttributes function to fix the compilation failure."
Why are the changes needed?
Fix the compilation failure in branch-3.4
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass Github Actions
Was this patch authored or co-authored using generative AI tooling?
No

This is my first time handling such a situation, is it better to create a new Jira or is it better as a FOLLOWUP of SPARK-47305?
cc @HyukjinKwon @HeartSaVioR @zhengruifeng

also cc @dongjoon-hyun

Thanks @HyukjinKwon

FOLLOWUP tag should be OK. Thanks for handling this.

Merged into branch-3.4 for fix compilation failure. Thanks @HyukjinKwon @yaooqinn @HeartSaVioR @zhengruifeng


[BEAM-7331]Create PAssert util function for late panes.

Create PAssert util function for late panes (in addition to other panes that are already available).

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

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

Please add a JIRA related to this.
It might be worthwhile to add a TestStream test that exercises inLatePane

R: @lukecwik
updated with new unit test case(s) in PaneExtractorTest.


tests: skip integration tests (primarily API tests) if not running on Github

This allows local development without setting up full set of API keys.

Could we make it possible to toggle this via flags/settings? For some aspects doing API calls for some might be nice (e.g. for the "magi" logic) - we eventually, we might want to mock our way around it though :))

Totally! We can disable tests based on what's in the env variables, and then re-activate if the variable is set: https://stackoverflow.com/questions/66970626/pytest-skip-test-condition-depending-on-environment


wayland-logout: init at 1.4

Description of changes
A simple package that logs you out of any Wayland compositor.

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

as far as i see, this is the first pr using the new pkgs/by-name structure introduced in #237439 :tada:

@wegank why  homepage -> website? Website is not a documented meta attribute.
Also, wouldn't it be easier to just wait until RFC 101 gets merged, and the whole codebase gets autoformatted before we try to enforce rules like spaces in lists.

@wegank why homepage -> website? Website is not a documented meta attribute.

What I've done is website -> homepage. The PR also had meta.licenses, which is not a valid attribute.

Also, wouldn't it be easier to just wait until RFC 101 gets merged, and the whole codebase gets autoformatted before we try to enforce rules like spaces in lists.

This is what a formatter expects to produce, but the change is indeed not necessary here.

oh bruh sorry im dumb
i'm going to have to be more careful for these attributes

another thing: why remove the trailing comma for ninja?
now ninja always has to be the last argument, because any argument added after ninja would need to change 2 lines
- ninja
+ ninja,
+ anotherdependency

as far as i know, nix has no problem with trailing commas in function arguments,
so even if you remove the ..., the trailing comma could've stayed


Same model for Squidb and Parceler

Does it work? Not working for me.
Please suggest.
Thanks,
Raj

Are you referring to models implementing Parcelable? This simple unit test works for me:
public void testModelParcelable() {
    TestModel model = new TestModel()
            .setFirstName("Fname")
            .setLastName("Lname")
            .setLuckyNumber(2)
            .setBirthday(System.currentTimeMillis())
            .setIsHappy(true);

    Bundle bundle = new Bundle();
    bundle.putParcelable("model", model);
    TestModel parceledModel = bundle.getParcelable("model");
    assertEquals(model, parceledModel);
}

Can you post a code snippet of what's not working for you?

Sorry, just realized my unit test is flawed. This updated one still works though:
public void testModelParcelable() {
    TestModel model = new TestModel()
            .setFirstName("Fname")
            .setLastName("Lname")
            .setLuckyNumber(2)
            .setBirthday(System.currentTimeMillis())
            .setIsHappy(true);

    // Obtain a Parcel object and write the parcelable object to it:
    Parcel parcel = Parcel.obtain();
    model.writeToParcel(parcel, 0);

    // After you're done with writing, you need to reset the parcel for reading:
    parcel.setDataPosition(0);

    // Reconstruct object from parcel and asserts:
    TestModel createdFromParcel = TestModel.CREATOR.createFromParcel(parcel);
    assertFalse(model == createdFromParcel);
    assertEquals(model, createdFromParcel);
}

I think @inawlaljar is referring to this library: https://github.com/johncarl81/parceler
You shouldn't need to use Parceler on your @ModelSpec classes. In fact, you shouldn't have to refer to your @ModelSpec classes at all, only your actual model classes that are generated by SquiDB. Those generated models are already Parcelable and have the necessary boilerplate to support that.

Since there's been no activity, hopefully that means your issue is resolved. If not, please let us know.


Does this app allow you to use this ADB shell on your phone without a computer

How do I get this to work on my phone without having to have a computer I just want to uninstall Facebook it's a pre-installed app and I would like to uninstall it but I can't seem to figure out how to get this to work I've tried to default IP address and Port 5555 and I'm thinking that's if it's on a Wi-Fi network and I do the wireless pairing I can get it to work if I do that but I don't know what the pairing code is but then again I'm not on a Wi-Fi network I don't have a router at all I'm just using my mobile data also looked under about phone and got my IP address and tried that in Port 555 and Port 5037 didn't work either please help thank you

Please refer to https://github.com/jarhot1992/Remote-ADB/blob/main/md/tutorials.md#i-dont-have-a-pc-how-can-i-use-this-application-locally


Automatically edit Istio Operator config

We currently require the user to insert some custom prometheus config to their Operator config (in README.md).
We should take care of this automatically in the setup command, and let the user specify which Istio Operator they want to edit with two flags: --operatorName & --operatorNamespace.

closed by #21


itest: extend multi-input PSBT spend test to include partial value spend

This commit extends the existing multi-input PSBT spend test to also include a partial value spend.

@jharveyb: review reminder

@jharveyb: review reminder
@georgetsagk: review reminder


First pass at publishing existing PXL scripts

Will add more documentation, linting and CI in coming PRs.

 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.


Can't build on macOS

⟩ ./waf build
Waf: Entering directory `/Users/ruihpacheco/Desktop/cquery/build'
CLANG_INCLUDE_DIR: /Users/ruihpacheco/Desktop/cquery/build/clang+llvm-4.0.0-x86_64-apple-darwin/include
CLANG_LIB_DIR:     /Users/ruihpacheco/Desktop/cquery/build/clang+llvm-4.0.0-x86_64-apple-darwin/lib
[ 1/33] Compiling src/cache.cc
[ 2/33] Compiling src/clang_complete.cc
[ 3/33] Compiling src/clang_cursor.cc
[ 4/33] Compiling src/clang_index.cc
[ 5/33] Compiling src/clang_translation_unit.cc
[ 6/33] Compiling src/clang_utils.cc
[ 7/33] Compiling src/command_line.cc
In file included from ../src/clang_index.cc:1:
../src/clang_index.h:3:10: fatal error: 'clang-c/Index.h' file not found
#include <clang-c/Index.h>
         ^~~~~~~~~~~~~~~~~
1 error generated.

In file included from ../src/clang_translation_unit.cc:1:
In file included from ../src/clang_translation_unit.h:3:
../src/clang_cursor.h:3:10: fatal error: 'clang-c/Index.h' file not found
#include <clang-c/Index.h>
         ^~~~~~~~~~~~~~~~~
1 error generated.

In file included from ../src/clang_cursor.cc:1:
../src/clang_cursor.h:3:10: fatal error: 'clang-c/Index.h' file not found
#include <clang-c/Index.h>
         ^~~~~~~~~~~~~~~~~
1 error generated.

In file included from ../src/cache.cc:3:
In file included from ../src/indexer.h:3:
../src/clang_index.h:3:10: fatal error: 'clang-c/Index.h' file not found
#include <clang-c/Index.h>
         ^~~~~~~~~~~~~~~~~
1 error generated.

In file included from ../src/clang_complete.cc:1:
In file included from ../src/clang_complete.h:2:
../src/clang_index.h:3:10: fatal error: 'clang-c/Index.h' file not found
#include <clang-c/Index.h>
         ^~~~~~~~~~~~~~~~~
1 error generated.

In file included from ../src/clang_utils.cc:1:
../src/clang_utils.h:5:10: fatal error: 'clang-c/Index.h' file not found
#include <clang-c/Index.h>
         ^~~~~~~~~~~~~~~~~
1 error generated.

In file included from ../src/command_line.cc:3:
In file included from ../src/clang_complete.h:2:
../src/clang_index.h:3:10: fatal error: 'clang-c/Index.h' file not found
#include <clang-c/Index.h>
         ^~~~~~~~~~~~~~~~~
1 error generated.

Waf: Leaving directory `/Users/ruihpacheco/Desktop/cquery/build'
Build failed
 -> task in 'app' failed with exit status 1 (run with -v to display more information)
 -> task in 'app' failed with exit status 1 (run with -v to display more information)
 -> task in 'app' failed with exit status 1 (run with -v to display more information)
 -> task in 'app' failed with exit status 1 (run with -v to display more information)
 -> task in 'app' failed with exit status 1 (run with -v to display more information)
 -> task in 'app' failed with exit status 1 (run with -v to display more information)
 -> task in 'app' failed with exit status 1 (run with -v to display more information)

~/Desktop/cquery · (master)
⟩

Can you rerun ./waf configure?

I've done so countless times.

@ruipacheco try nuking build/ and .waf* from the repo checkout, too. I've had issues in the past where a half-downloaded clang tarball caused issues.

Worked for me.

On 23 Nov 2017, at 17:42, Josh Elsasser<EMAIL_ADDRESS>wrote:
@ruipacheco https://github.com/ruipacheco try nuking build/ and .waf* from the repo checkout, too. I've had issues in the past where a half-downloaded clang tarball caused issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/jacobdufault/cquery/issues/79#issuecomment-346663000, or mute the thread https://github.com/notifications/unsubscribe-auth/AAfK7_yVcwivAtKQeitFTwNfEnVVvpfWks5s5aCKgaJpZM4QoGdS.


[WIP]Add accessibility dump

Why
https://github.com/takahirom/roborazzi/issues/46
How
val explanation: ((RoboComponent) -> String)

    onView(ViewMatchers.isRoot())
      .captureRoboImage(
        filePath = "$DEFAULT_ROBORAZZI_OUTPUT_DIR_PATH/manual_view_first_screen_with_query_compose_custom.png",
        roborazziOptions = RoborazziOptions(
          captureType = RoborazziOptions.CaptureType.Dump(
            explanation = RoborazziOptions.CaptureType.Dump.AccessibilityExplanation, // ←
          )
        )
      )

👀
https://github.com/google/talkback/blob/master/utils/src/main/java/com/google/android/accessibility/utils/TreeDebug.java

It seems that AccessibilityNodeInfoCompat.obtain(view) doesn't work well. 👀
If I use nodeDebugDescription from TreeDebug.java, it will be like this:

However, I believe it is better to have some implementation, even if it is not perfect.

This looks great. Building the accessibility description in makes sense.  The labels with lines look great.
I'd love to be able to provide a different implementation, not using the exploded view, but just showing a flat image with highlighted rectangles.  Is that possible to make overridable?
Maybe it's just changing the elevation (to zero), and the layer transparency (to fully)?

What's with the "-1??" text in the second image?

There is a depthSlideSize property that allows you to change the slide size. As for layer transparency, we don't currently have that option. However, I believe we can add it.
https://github.com/takahirom/roborazzi/blob/main/roborazzi/src/main/java/com/github/takahirom/roborazzi/capture.kt#L210C11-L210C25
It might be the window ID. I agree that it's not very readable. Regardless, I'm not going to use the TalkBack implementation in this PR.
https://github.com/takahirom/roborazzi/commit/4301660a4bc5836e9665e98db4c5e05a406e5e42#diff-b5721281cee7bf3e6758c3f8943ed7bed6de8caa71dfc072a2d22752c3549126R63

Add some properties


Cannot resolve type: "MCL_BLS12_381.fp"

Describe the bug
When using code from this repo https://github.com/genievot/zk-ae-private-transactions/ and do aeproject test.
To Reproduce
Steps to reproduce the behavior:

Please clone the main branch from this repo https://github.com/genievot/zk-ae-private-transactions/
Install Dependencies
Run aeprject nodes
Then run aeproject test
The error I got:

TypeResolveError: Cannot resolve type: "MCL_BLS12_381.fp"
      at TypeResolver.resolveType (node_modules/@aeternity/aepp-calldata/src/TypeResolver.js:231:15)
      at TypeResolver.resolveType (node_modules/@aeternity/aepp-calldata/src/TypeResolver.js:126:25)
      at /home/ubuntu/aeternity-projects/bounty/zkp-aes/node_modules/@aeternity/aepp-calldata/src/TypeResolver.js:251:56
      at Array.map (<anonymous>)
      at TypeResolver.resolveRecord (node_modules/@aeternity/aepp-calldata/src/TypeResolver.js:251:42)
      at TypeResolver.resolveType (node_modules/@aeternity/aepp-calldata/src/TypeResolver.js:212:25)
      at TypeResolver.resolveType (node_modules/@aeternity/aepp-calldata/src/TypeResolver.js:126:25)
      at TypeResolver.resolveType (node_modules/@aeternity/aepp-calldata/src/TypeResolver.js:126:25)
      at /home/ubuntu/aeternity-projects/bounty/zkp-aes/node_modules/@aeternity/aepp-calldata/src/TypeResolver.js:251:56
      at Array.map (<anonymous>)
      at TypeResolver.resolveRecord (node_modules/@aeternity/aepp-calldata/src/TypeResolver.js:251:42)
      at TypeResolver.resolveType (node_modules/@aeternity/aepp-calldata/src/TypeResolver.js:212:25)
      at TypeResolver.resolveType (node_modules/@aeternity/aepp-calldata/src/TypeResolver.js:126:25)
      at TypeResolver.getReturnType (node_modules/@aeternity/aepp-calldata/src/TypeResolver.js:79:21)
      at Encoder.decode (node_modules/@aeternity/aepp-calldata/src/Encoder.js:99:41)
      at Object.c.call (node_modules/@aeternity/aepp-sdk/dist/aepp-sdk.js:1:97822)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)
      at async Context.<anonymous> (test/zkp_verify_test.js:34:17)

Expected behavior
I expected to not have predefined data type errors.
Screenshots

Please tell us about your environment:

Node Version: v14.18.3
Protocol Version: Latest
Aeproject:  v4.0.0-beta.6
Compiler version: Docker node from latest beta
VM Version: fate | fate2
SDK Version: From aeproject beta
Python version: v3.7.5

this only seems to be an  issue with https://github.com/aeternity/aepp-calldata-js can you open a full issue there?

yes, we already have the issue there:

https://github.com/aeternity/aepp-calldata-js/issues/126


Error executing lua callback: Vim:E315: ml_get: invalid lnum: 1

For some reason I have this error when I tray to delete buffer. Not sure if this related to the telescope. Any idea? Thanks in advance
Error executing lua callback: Vim:E315: ml_get: invalid lnum: 1
stack traceback:
        [C]: in function 'bufload'
        vim/_editor.lua: in function 'region'
        ...ls/neovim/0.9.1/share/nvim/runtime/lua/vim/highlight.lua:35: in function 'range'
        /Users/vucinjo/.local/share/nvim/lazy/markid/lua/markid.lua:87: in function 'highlight_tree'
        /Users/vucinjo/.local/share/nvim/lazy/markid/lua/markid.lua:103: in function 'cb'
        ...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:736: in function '_do_callback'
        ...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:176: in function 'invalidate'
        ...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:877: in function '_on_detach'
        ...s/neovim/0.9.1/share/nvim/runtime/lua/vim/treesitter.lua:73: in function <...s/neovim/0.9.1/share/nvim/runtime/lua/vim/treesitter.lua:69>
        [C]: at 0x010f000a80
        [C]: in function 'pcall'
        .../nvim/lazy/telescope.nvim/lua/telescope/actions/init.lua:1040: in function 'delete_cb'
        ...share/nvim/lazy/telescope.nvim/lua/telescope/pickers.lua:720: in function 'delete_selection'
        .../nvim/lazy/telescope.nvim/lua/telescope/actions/init.lua:1038: in function 'run_replace_or_original'
        ...re/nvim/lazy/telescope.nvim/lua/telescope/actions/mt.lua:65: in function 'key_func'
        ...hare/nvim/lazy/telescope.nvim/lua/telescope/mappings.lua:253: in function <...hare/nvim/lazy/telescope.nvim/lua/telescope/mappings.lua:252>

MacOS
NVIM v0.9.1
Build type: Release
LuaJIT 2.1.0-beta3

Hi @avucic ,
Thanks for reporting! Can you include the steps to reproduce this problem? When I delete a buffer, everything works as expected.
Thank you and best regards,
David

Hi @David-Kunz thanks for helping me.
Not sure but I think this is related to the https://github.com/neovim/neovim/issues/21416 and this plugin has the same issue
https://github.com/HiPhish/nvim-ts-rainbow2/issues/40
When I open multiple files and I try to delete one I'm getting similar error like one mentioned in nvim-ts-rainbow2
E5108: Error executing lua ...al/share/nvim/lazy/bufdelete.nvim/lua/bufdelete/init.lua:134: Vim:Error executing lua callback: ....1/share/nvim/runtime/lua/vim/treesitter/highlighter.lua:148: Vim:Error executing lua callback: Vim:E315: ml_get: invalid lnum: 1
stack traceback:
        [C]: in function 'bufload'
        vim/_editor.lua: in function 'region'
        ...ls/neovim/0.9.1/share/nvim/runtime/lua/vim/highlight.lua:35: in function 'range'
        /Users/vucinjo/.local/share/nvim/lazy/markid/lua/markid.lua:87: in function 'highlight_tree'
        /Users/vucinjo/.local/share/nvim/lazy/markid/lua/markid.lua:103: in function 'cb'
        ...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:736: in function '_do_callback'
        ...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:176: in function 'invalidate'
        ...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:877: in function '_on_detach'
        ...s/neovim/0.9.1/share/nvim/runtime/lua/vim/treesitter.lua:73: in function <...s/neovim/0.9.1/share/nvim/runtime/lua/vim/treesitter.lua:69>
        [C]: in function 'bdelete'
        ...al/share/nvim/lazy/bufdelete.nvim/lua/bufdelete/init.lua:134: in function 'buf_kill'
        ...al/share/nvim/lazy/bufdelete.nvim/lua/bufdelete/init.lua:213: in function 'bufdelete'
        /Users/vucinjo/.config/nvim/lua/astronvim/utils/buffer.lua:138: in function 'close'
        [string ":lua"]:1: in main chunk

Similar issue was mentioned on bufdelete
It looks like some issue with callback mentioned in https://github.com/HiPhish/nvim-ts-rainbow2/issues/40 but I'm not sure. When I disable markid I have no issue.
Let me know if this is not related to the markid or if I can help you more.
Regards

Hi @avucic,
Thank you so much for this detailed analysis, greatly appreciated!
I still cannot reproduce the problem but I implemented a similar fix as in this PR.
Would you mind trying it out?
Thank you again and best regards,
David

I'm not familiar with nvim / lua so I'm not sure how to try it. What I did is following:
-- inisde lsp on_attach function
return function(client, bufnr)
  vim.api.nvim_buf_attach(bufnr, false, {
    on_detach = function()
      local ns = vim.api.nvim_get_namespaces()["markid"]
      vim.api.nvim_buf_clear_namespace(bufnr, ns, 0, -1)
    end,
  })
end

No luck. Can you give me a hint hot to try?

@avucic , sorry I should've been more precise: The fix is already in the main branch, so you just need to update the plugin.

A ha...I did that but unfortunately same thing
E5108: Error executing lua ...al/share/nvim/lazy/bufdelete.nvim/lua/bufdelete/init.lua:134: Vim:Error executing lua callback: ....1/share/nvim/runtime/lua/vim/treesitter/highlighter.lua:148: Vim:Error executing lua callback: Vim:E315: ml_get: invalid lnum: 1
stack traceback:
        [C]: in function 'bufload'
        vim/_editor.lua: in function 'region'
        ...ls/neovim/0.9.1/share/nvim/runtime/lua/vim/highlight.lua:35: in function 'range'
        /Users/vucinjo/.local/share/nvim/lazy/markid/lua/markid.lua:90: in function 'highlight_tree'
        /Users/vucinjo/.local/share/nvim/lazy/markid/lua/markid.lua:106: in function 'cb'
        ...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:736: in function '_do_callback'
        ...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:176: in function 'invalidate'
        ...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:877: in function '_on_detach'
        ...s/neovim/0.9.1/share/nvim/runtime/lua/vim/treesitter.lua:73: in function <...s/neovim/0.9.1/share/nvim/runtime/lua/vim/treesitter.lua:69>
        [C]: in function 'bdelete'
        ...al/share/nvim/lazy/bufdelete.nvim/lua/bufdelete/init.lua:134: in function 'buf_kill'
        ...al/share/nvim/lazy/bufdelete.nvim/lua/bufdelete/init.lua:213: in function 'bufdelete'
        /Users/vucinjo/.config/nvim/lua/astronvim/utils/buffer.lua:138: in function 'close'
        [string ":lua"]:1: in main chunk
stack traceback:
        [C]: in function '__newindex'
        ....1/share/nvim/runtime/lua/vim/treesitter/highlighter.lua:148: in function 'destroy'
        ....1/share/nvim/runtime/lua/vim/treesitter/highlighter.lua:184: in function 'on_detach'
        ....1/share/nvim/runtime/lua/vim/treesitter/highlighter.lua:83: in function 'cb'
        ...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:736: in function '_do_callback'
        ...1/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:878: in function '_on_detach'
        ...s/neovim/0.9.1/share/nvim/runtime/lua/vim/treesitter.lua:73: in function <...s/neovim/0.9.1/share/nvim/runtime/lua/vim/treesitter.lua:69>
        [C]: in function 'bdelete'
        ...al/share/nvim/lazy/bufdelete.nvim/lua/bufdelete/init.lua:134: in function 'buf_kill'
        ...al/share/nvim/lazy/bufdelete.nvim/lua/bufdelete/init.lua:213: in function 'bufdelete'
        /Users/vucinjo/.config/nvim/lua/astronvim/utils/buffer.lua:138: in function 'close'
        [string ":lua"]:1: in main chunk
stack traceback:
        [C]: in function 'bdelete'
        ...al/share/nvim/lazy/bufdelete.nvim/lua/bufdelete/init.lua:134: in function 'buf_kill'
        ...al/share/nvim/lazy/bufdelete.nvim/lua/bufdelete/init.lua:213: in function 'bufdelete'
        /Users/vucinjo/.config/nvim/lua/astronvim/utils/buffer.lua:138: in function 'close'
        [string ":lua"]:1: in main chunk

That's unfortunate. Let's wait for the response of your comment.

@David-Kunz After I install everything from scratch the issue disappear. Not sure what was the problem. Maybe it was related to the Astrovim update. Anyhow feel free to close this issue for and thanks for the help. Regards

That's great news, thanks for the info @avucic  👍

@norpie-dev Thank you. That seems to be the fix. I thought a clean install was the solution, but it's not...soon the problem appeared again.


connectChat reveals your IP Adress if you set a proxy for the bot!

First shot for a Solution:
in the function there are two parts who reveals the IP
http.NewRequest and websocket.Dial
proxyUrl, err := url.Parse("http://proxyIp:proxyPort")
myClient := &http.Client{Transport: &http.Transport{Proxy: http.ProxyURL(proxyUrl)}}

/*
You could also modify the default transport used by the "net/http" package. This would affect your entire program (including the default HTTP client).
*/

proxyUrl, err := url.Parse("http://proxyIp:proxyPort")
http.DefaultTransport = &http.Transport{Proxy: http.ProxyURL(proxyUrl)}

 var d = websocket.Dialer{
     Proxy: http.ProxyURL(&url.URL{
          Scheme: "http", // or "https" depending on your proxy
          Host: "ipaddress:port" ,
          Path: "/",
    }
 }

https://github.com/alaingilbert/ogame/blob/master/ogame.go#L620
That is the only call that needs to be proxied.
It's the only http call that they monitor in their admin tools.

Okay @TuxLinus I would like to say that the http has already set an Transport Proxy in the api ogame.go any further requests are using the Proxy Server!
about the Websocket.Dialer yes it seems that it uses Direct Connection and dont uses the http Proxy.


Wildcard support?

Are wildcard SSL certs supported in v<IP_ADDRESS>?
If not when will this be supported?

Still getting a "wildcard certificates are not supported" message. Has this not been implemented yet?

I've locked the conversation. See #464


AccessViolationException at SetTo() method with a mask.

Hi,
I tried to use SetTo() with a mask, but it throw an AccessViolationException.
My code snippet is below:
	using (Mat graySrc = Cv2.ImRead("C:/test.jpg", ImreadModes.GrayScale))
	using (Mat resultImage = graySrc.Clone())
	using (Mat mask = graySrc.InRange(100, 200))
	{
		resultImage.SetTo(0, mask); // System.AccessViolationException
	}

SetTo() without mask(mask==null) has no problem.
If you know what the problem is, please reply me to fix it up.
Thank you :)

thanks! this is fixed in https://github.com/shimat/opencvsharp/commit/0b59d0fbf7f6fbea039b7525a69450fa75e45b98

Do you have any idea when the next release to nuget will be and if this fix will be included in the release?
Also I think the if (mask == null) should be reversed since if the mask is not null you're not using it.


Added placeholder docs for SPO Version 16.0.19724.12000

SPO Management PowerShell Version 16.0.19724.12000 has 6 new cmdLets.
Related to #4930

Docs Build status updates of commit db16128:
:clock10: Full build: the average full build time is 12 min(s) 12 sec(s), this is based on the last 1000 build(s) for this repository.

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

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelationByPartner.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelationByScenario.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/New-SPOTenantOrgRelation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTenantOrgRelation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Verify-SPOTenantOrgRelation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Thanks for the contribution @andikrueger 🥇
We should get input from @trent-green as, once these articles go online, as they are not fully complete, users will start creating issues on them...

Docs Build status updates of commit 90925c0:
:clock10: Full build: the average full build time is 12 min(s) 12 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 90925c0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelationByPartner.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Get-SPOTenantOrgRelationByScenario.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/New-SPOTenantOrgRelation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Remove-SPOTenantOrgRelation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

sharepoint/sharepoint-ps/sharepoint-online/Verify-SPOTenantOrgRelation.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


<EMAIL_ADDRESS>Corrected hash value in accordance with original repo

Updated the hash value to match the correct one based on the information from the original repository at https://gitlab.com/bztsrc/usbimager/-/blob/binaries/sha256checksums.txt. The corrected hash is now "7C57380C050F186E420AA60A15A0F16B047539160D98BC2B7CAE97882FF992CA"

[x] I have read the Contributing Guide.

/verify


Links to cli-reference are broken on core-concepts page (website)

Hi all
Seems like links pointing to commands like ks generate, ks apply, ks param etc. are broken on this page https://ksonnet.io/docs/concepts
links are pointing to https://docs/cli-reference#ks-prototype
instead of https://ksonnet.io/docs/cli-reference#ks-prototype
Also link to Manifest anchor is broken
In Application paragraph it points to https://ksonnet.io/#manifests , while it should point to https://ksonnet.io/docs/concepts#manifest

We are reviewing / fixing issues with the site links. An update will be issued soon.

Fixes are committed; pending deploy of new site.


[Site] Clean demos & packages pages

Raaaah... now i have the Sitemap / Robots in here 🤦

Thanks Simon.


fix: get not availiable param changes from db to validate old dag blocks

prnet cleaned-up successfully


I NEED HELP

i am new in these, and i need to know how i connect the ds 2431 to my arduino, because i dont have any idea of it. if you know please tell me

Please make a research before asking on the Internet like this...
Here are some resources to get you started :
DS2431 datasheet to get the pinout (which pin on the DS2431 corresponds to which function)
1-Wire devices tutorial for Arduino Please note that in the library examples I used Arduino pin 9 for the data communication, while they use pin 3 in this tutorial.


questions re. RESTART options in GEOSldas

@smahanam
I have a couple of questions re. the RESTART options in GEOSldas.

Re. option 1, it looks like the help text in the "exe inp" file is not complete.  Specifically, in lines ~1500 of "ldas_setup" (branch WJ_ldassa_regrid):
print '# RESTART: 1                                               #'
print '#   YES, have restart file(s) from GEOSldas or LDASsa    #'
print '#        on the SAME grid                                  #'
print '#   Must specify RESTART_ID, RESTART_PATH, RESTART_DOMAIN, #'
print '#     with restarts stored as follows:                     #'
print '#     RESTART_PATH/RESTART_ID/output/RESTART_DOMAIN/rs/    #'
print '#   GEOSldas-produced restarts must be on the same         #'
print '#     GRID and for the same or a larger domain.            #'
print '#   LDASsa-produced restarts must be on the same           #'
print '#     GRID and for the GLOBAL domain (only!).              #'

From looking at the code, I understand that the source and target restart also MUST have the same bcs and the same WEMIN values.  But this is not clear from the help message and should probably added to the help message.

Re. option 2:
print '# RESTART: 2                                               #'
print '#   YES, have restart file(s) from GEOSldas or LDASsa    #'
print '#        on a DIFFERENT grid                               #'
print '#   Must specify RESTART_ID, RESTART_PATH, RESTART_DOMAIN, #'
print '#     with restarts stored as follows:                     #'
print '#     RESTART_PATH/RESTART_ID/output/RESTART_DOMAIN/rs/    #'
print '#   RESTART_DOMAIN must be GLOBAL.                         #'

From looking at the code, I understand that switching bcs does NOT work correctly for LDASsa restarts because the script does not know or find the source bcs.  That is, if the LDASsa restart was based on bcs that are different from the target bcs, then the restart variables will not be scaled properly.
Perhaps the easiest solution would be to restrict option 2 to only GEOSldas restarts, where we don't need to know the source bcs.  (I assume that the numbers needed for scaling the restart variables are all contained in "catch_internal_rst" restarts.)
Please advise, Rolf

PS: Here is another question:  It looks like mk_LDASsaRestarts does not necessarily involve (old) LDASsa restarts.  There seem to be use cases where only GEOSldas "catch_internal_rst" files are involved.  Can we rename the script accordingly to avoid mistakes?  Perhaps: "mk_LDASRestarts"?

@smahanam
I have a couple of questions re. the RESTART options in GEOSldas.

Re. option 1, it looks like the help text in the "exe inp" file is not complete.  Specifically, in lines ~1500 of "ldas_setup" (branch WJ_ldassa_regrid):
print '# RESTART: 1                                               #'
print '#   YES, have restart file(s) from GEOSldas or LDASsa    #'
print '#        on the SAME grid                                  #'
print '#   Must specify RESTART_ID, RESTART_PATH, RESTART_DOMAIN, #'
print '#     with restarts stored as follows:                     #'
print '#     RESTART_PATH/RESTART_ID/output/RESTART_DOMAIN/rs/    #'
print '#   GEOSldas-produced restarts must be on the same         #'
print '#     GRID and for the same or a larger domain.            #'
print '#   LDASsa-produced restarts must be on the same           #'
print '#     GRID and for the GLOBAL domain (only!).              #'

From looking at the code, I understand that the source and target restart also MUST have the same bcs and the same WEMIN values. But this is not clear from the help message and should probably added to the help message.

Re. option 2:
print '# RESTART: 2                                               #'
print '#   YES, have restart file(s) from GEOSldas or LDASsa    #'
print '#        on a DIFFERENT grid                               #'
print '#   Must specify RESTART_ID, RESTART_PATH, RESTART_DOMAIN, #'
print '#     with restarts stored as follows:                     #'
print '#     RESTART_PATH/RESTART_ID/output/RESTART_DOMAIN/rs/    #'
print '#   RESTART_DOMAIN must be GLOBAL.                         #'

From looking at the code, I understand that switching bcs does NOT work correctly for LDASsa restarts because the script does not know or find the source bcs. That is, if the LDASsa restart was based on bcs that are different from the target bcs, then the restart variables will not be scaled properly.
Perhaps the easiest solution would be to restrict option 2 to only GEOSldas restarts, where we don't need to know the source bcs. (I assume that the numbers needed for scaling the restart variables are all contained in "catch_internal_rst" restarts.)
Please advise, Rolf

@smahanam , did you intend to just close this issue?
Re. my 2nd question about option 2, we do need to also think about how we can deal with the WEMIN in/out values.   If someone is using a source restart from MERRA-2, the WEMIN_in value should be 26.

Re. option 1, it looks like the help text in the "exe inp" file is not complete.  Specifically, in lines ~1500 of "ldas_setup" (branch WJ_ldassa_regrid):
From looking at the code, I understand that the source and target restart also MUST have the same bcs and the same WEMIN values. But this is not clear from the help message and should probably added to the help message.

Since Option 1 does not scale restarts, unless we go further step and make changes to scale if WEMIN from old restarts and new experiment are inconsistent, we don't need to worry about the help message for RESTART: 1.

Re. option 2:
print '# RESTART: 2                                               #'
From looking at the code, I understand that switching bcs does NOT work correctly for LDASsa restarts because the script does not know or find the source bcs. That is, if the LDASsa restart was based on bcs that are different from the target bcs, then the restart variables will not be scaled properly.

mk_LDASsaRestarts reads input land parameters from rc_out///catparam in RESTART directory, and that are used to scale soil moisture and GHTCNT.
As you know, WEM change is associated with the source code tag, not the BCs used.
We used the BCS-based approach to select WEMs in regrid.pl for the AGCM since there is no other way to determine it easily for regrid.pl. As for ldas_setup, help message can use reichle-LDASsa_m3 or GEOSldas-m4 tag names to recommend suitable WEMs

Perhaps the easiest solution would be to restrict option 2 to only GEOSldas restarts, where we don't need to know the source bcs. (I assume that the numbers needed for scaling the restart variables are all contained in "catch_internal_rst" restarts.)

Restarts files that people have at the moment are from LDASsa. So during this LDASsa-to GEOSldas transition period, ability regrid LDASsa restarts is very important and useful.
If you look carefully, ldas_setup actually does not allow people to communicate the choice of WEMs to ldas_setup. People use sample script to make changes to options, but the current sample does not show WEMIN/WEMOUT - it is intentionally hidden (a decision you, JP and WJ made a while back).
I think offline driver has moved away from 26 long enough not to worry about it.

PS: @smahanam Here is another question: It looks like mk_LDASsaRestarts does not necessarily involve (old) LDASsa restarts. There seem to be use cases where only GEOSldas "catch_internal_rst" files are involved. Can we rename the script accordingly to avoid mistakes? Perhaps: "mk_LDASRestarts"?

I'll do it now

PS: @smahanam Here is another question: It looks like mk_LDASsaRestarts does not necessarily involve (old) LDASsa restarts. There seem to be use cases where only GEOSldas "catch_internal_rst" files are involved. Can we rename the script accordingly to avoid mistakes? Perhaps: "mk_LDASRestarts"?

I'll do it now

How about mk_GEOSldasRestarts.F90? Since the purpose of the program is to create catch[cn]_internal_rst for GEOSldas.
It is always good to create CATCHCN restarts for LDASsa too - but in this context, the code is serving GEOSldas

@smahanam

Since Option 1 does not scale restarts, unless we go further step and make changes to scale if
WEMIN from old restarts and new experiment are inconsistent, we don't need to worry about the
help message for RESTART: 1.

Note that I did not say we should worry about scaling for WEMIN.  I want to change the comments provided with the RESTARTS=1 option to make it explicitly clear that this option is not appropriate if bcs or WEMIN are different between the source and target restarts.  Once you have a pull request, I'll edit the text.
Re. RESTART=2

mk_LDASsaRestarts reads input land parameters from rc_out///catparam in RESTART directory, > and that are used to scale soil moisture and GHTCNT.

Thanks, this is good to know!  And it explains the mysterious "pfile" variable in mk_LDASsaRestarts...  A comment or two in the program would have been helpful.

Restarts files that people have at the moment are from LDASsa. So during this LDASsa-to GEOSldas > transition period, ability to regrid LDASsa restarts is very important and useful.

I agree, and now that I understand that bcs are handled correctly, it is best to keep the LDASsa-to-GEOSldas option when switching bcs.

If you look carefully, ldas_setup actually does not allow people to communicate the choice of
WEMs to ldas_setup. People use sample script to make changes to options, but the current sample > does not show WEMIN/WEMOUT - it is intentionally hidden (a decision you, JP and WJ made a
while back).
I think offline driver has moved away from 26 long enough not to worry about it.

This decision was made before we introduced RESTART=2.  At that time, GEOSldas did not offer a way to change bcs when putting together the catch restart.  Now that we have this functionality with RESTART=2, we do need to make a smart guess for the WEMIN in/out values.  The problem with the off-line system is that, unlike the ADAS, we do not query for source bcs, so it's not clear whether the input WEMIN should be 13 or 26.
I strongly disagree with the final sentence about the offline driver having moved away from 26 long enough.  Users will likely regrid MERRA-2 restarts for several more years because there will not be a new 30+year reanalysis for several more years.
I think we now have two options:
a) Make the script smart enough to detect WEMIN_in=26 if the restart is from MERRA-2 or FP up to 5.22.  Otherwise, assume (with some optimism) that WEMIN_in=13.  Ask the user to confirm this educated guess (perhaps as part of confirming all ldas_setup inputs, that is, don't introduce the WEMIN in/out query as a separate question).
b) As part of RESTART=2, strongly recommend that spin-up is going to be needed after regridding whenever the bcs or WEMIN have changed.
On second thought, we probably should recommend spin-up (option 2) in any case...

How about mk_GEOSldasRestarts.F90? Since the purpose of the program is to create
catch[cn]_internal_rst for GEOSldas.
It is also good to create CATCHCN restarts for LDASsa too - but in this context, the code is serving > GEOSldas

Good suggestion.  When you rename the file, make sure to use the git rename functionality (i.e., "git mv ...").

I think we now have two options:
a) Make the script smart enough to detect WEMIN_in=26 if the restart is from MERRA-2 or FP up to 5.22. Otherwise, assume (with some optimism) that WEMIN_in=13. Ask the user to confirm this educated guess (perhaps as part of confirming all ldas_setup inputs, that is, don't introduce the WEMIN in/out query as a separate question).

ldas_setup > mk_LDASsaRestarts.F90 : still can not regrid MERRA-2 or FP restarts.
If we think this going to be very useful, first we need to add that capability to ldas_setup.

Sarith,
Since you are going to change mk_LDASsaRestars.F90, would you please also change the subroutine read_bcs_data() so that it doesn’t not read catchCN if we only need catch? It is way too slow to read catchCN when running ldas_setup.
Thanks
Weiyuan
From: Sarith Mahanama<EMAIL_ADDRESS>Reply-To: GEOS-ESM/GEOSldas<EMAIL_ADDRESS>Date: Wednesday, February 12, 2020 at 12:44 PM
To: GEOS-ESM/GEOSldas<EMAIL_ADDRESS>Cc: "Jiang, Weiyuan (GSFC-61A.0)[SCIENCE SYSTEMS AND APPLICATIONS INC]"<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: [EXTERNAL] Re: [GEOS-ESM/GEOSldas] questions re. RESTART options in GEOSldas (#108)
PS: @smahanamhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_smahanam&d=DwMCaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=SZHGQvwk5qYXensoM4g4Fr_aEfq5rxS_qQY1paompMc&m=q7j6MkWtFkDijmrTioOZ4OTf8o9JMnF6D4Oj6kNnzQk&s=1hpu7hB53AX_UvfA_yJneHEWJ1IogBqWFjbpOK-E-y0&e= Here is another question: It looks like mk_LDASsaRestarts does not necessarily involve (old) LDASsa restarts. There seem to be use cases where only GEOSldas "catch_internal_rst" files are involved. Can we rename the script accordingly to avoid mistakes? Perhaps: "mk_LDASRestarts"?
I'll do it now
How about mk_GEOSldasRestarts.F90? Since the purpose of the program is to create catch[cn]_internal_rst for GEOSldas.
It is always good to create CATCHCN restarts for LDASsa too - but in this context, the code is serving GEOSldas
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_GEOS-2DESM_GEOSldas_issues_108-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAMQTYOOSEVUVO4Z47WAROITRCQYMDA5CNFSM4KT5GPS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELRWRKI-23issuecomment-2D585328809&d=DwMCaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=SZHGQvwk5qYXensoM4g4Fr_aEfq5rxS_qQY1paompMc&m=q7j6MkWtFkDijmrTioOZ4OTf8o9JMnF6D4Oj6kNnzQk&s=zaWD4NTde9SrIiG9nPmb0FNYzd1keFfe3_KZpml6Gj8&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMQTYOOANA3MPD7UTPI6UUTRCQYMDANCNFSM4KT5GPSQ&d=DwMCaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=SZHGQvwk5qYXensoM4g4Fr_aEfq5rxS_qQY1paompMc&m=q7j6MkWtFkDijmrTioOZ4OTf8o9JMnF6D4Oj6kNnzQk&s=IYv8vZsd_PCnNmR8FdIcyXUDqGeCLiNzjTCyHE8qvMw&e=.

Addressed with pull request #149


Invest / withdraw modal consistency

title alignment (left vs center)
token row styling (and for withdraw total/price impact row styling)
"you've successfully..." -> separate or part of transaction details?
order of transaction details & "return to pool" button

@1saf I believe you mentioned something about these modals?


ecl_16_1_2: Adopt upstream error handling patch

Motivation for this change
Adopt an upstream fix for a infinite loop bug. This also disables threadSupport by default, since the package is only used by maxima-ecl anyways and that seems to work better (or at least the only package that depends on that, sage) without threading.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

This only overrides threadSupport for the ecl version that is pinned at 16_1_2, specially for maxima-ecl.

Point taken.

(I slightly regret not being optimistic enough to believe that «asking ofborg if sage still builds» makes sense)

What do you mean?

Well, it could be useful to know if it still builds, but I know that it is a guaranteed timeout.

Ah right. Well the current sage doesn't depend on this and the new version might build within the timeslot. Its tests will probably time out though, but not by a lot (its split in sagelib and sage, where sage just glues everything together and runs the testsuite).

Off topic: Github suddenly seems to flip a coin to decide wether or not to notify me about things. I didn't get a notify for your reply for example. Is that only me?

Did you have the page open? It might JS-push the comment and decide there is no need to further notify you.

I don't think so, but maybe. It happens all the time today. Hopefully not github getting too clever.


[GHSA-rp65-9cf3-cjxr] Inefficient Regular Expression Complexity in nth-check

Updates

Affected products
Description

Comments
https://github.com/facebook/create-react-app/issues/11647
https://github.com/facebook/create-react-app/issues/11647

Hi @NManning_Perkins, thank you for your suggestions. Unfortunately, the changes you proposed are out of scope for this advisory.

👋 This pull request has been marked as stale because it has been open with no activity.  If you do nothing this pull request will be closed eventually by the stale bot. Please see CONTRIBUTING.md for more policy details.


Radio button issue on ios 9

On ios 9 app the radio button isnt reacting to touch. I have two radio groups and it only changes once both have been touched. However it won't update after the buttons have been picked.
Found this on the ionic blog.
http://blog.ionic.io/preparing-for-ios-9/

iOS 9 has issue with css ~ sibling selector. Can be replaced with the + selector

What is the + selector?

Do you have a fix for this ? I forked and applied the patch (https://github.com/driftyco/ionic/commit/11232d4) but the radios are not working still.
Before I had incoherent behavior like in this issue: https://github.com/driftyco/ionic/issues/4347
The fix corrects the behavior but now, my radio buttons are not working. I can select an option in a group, but modifications are not reflected.
Do you still experience the problem ? If not, how did you fix this issue ?


Failing The Build Scalafmt

Have an independent macro that users set up in addition to their scalafmt_scala_library targets which looks something like:

def scala_fmt_test(name,target):
    native.sh_test(
        name = name + "_scala_fmt_test",
        srcs = [target + ".format-test"],
    )

Have scalafmt_scala_library actually be a macro that delegates to _scalafmt_scala_library_rule and scala_fmt_test.
If you want this to be toggled via a toolchain then you can do something like 2 but instead of using a regular sh_test you can write one of your own that will depend on the toolchain.

Reference from https://github.com/bazelbuild/rules_scala/pull/912#issuecomment-578927303

Thanks!
Can you elaborate on 3? The rule will use the toolchain to decide it to run the action or not?

This would be very useful. In fact rules_scala implementation from higherkindness provides a similar feature: https://github.com/higherkindness/rules_scala/blob/master/docs/scalafmt.md#scalafmt.

I don't suppose anyone has made this work?  I also went down the "create a wrapping sh_test that invokes the foo.format-test path, and ran into the same issue of missing manifest file (and, presumably, the formatted output files)


Extension mostly non-functional within a VSCode-Remote workspace

In a local window, this extension seems to basically be working as expected. I can load pages, close, re-open, bookmark, etc.
However, when I attempt to use this extension in a Remote session, it behaves really strangely: I can open a page immeaditely after opening the workspace; but if I close that page, I cannot then re-open it — clicking on the bookmark has no effect, no new VScode panes open or anything.
Similarly, although I can open pages on the Remote (once each) by clicking them in bookmarks, the vscode-notion.openPage command has … no effect. The 'input URL' window refuses to appear on the remote workspace, period.

Er, woah, I also get this — although it's possibly unrelated, it doesn't happen immediately after attempting to issue the vscode-notion.openPage command …


Update gettingstarted.md

Proposed changes
suggest to remove ADD . /code after adding the volume as it becomes irrelevant.

Deploy preview for docsdocker ready!
Built with commit 1cc74223ae5e6758c8fe0c725533d98e7c98ded7
https://deploy-preview-8177--docsdocker.netlify.com

@thaJeztah PTAL, thanks!

Closing the PR based on the comment above. We can look into improving the Compose getting started as a new work item.


Offer second chance to request permission from organization.

It would be nice to be able to retroactively request access to an organization. Currently I can only find this functionality on the main start page.

Hello @Vince-Smith, I think you can see pending requests on Github. If you go to this page https://github.com/settings/applications and click on Gitify, at the bottom of the page it says Organization access and it lists approved & pending requests.
Ps. Not sure if GitHub allows to resend a request.

Closing due to inactivity.


Score Bar fix + toggleable health on Score Bar

(Adds) Fixes #674
Fixes #841

I absolutely despise health percentage. good pr, but I hate the feature.

KadeDev moment

KadeDev moment


Implementation of flow control APIs for python UDF

Currently the flow control APIs to get credit information is not implemented for python UDF.

Three steps:

enable Python credit passing on ack #1748;
enable backpressure on Python side #2195;
report the credit to the upstream operator by using Python queue size + Proxy queue size (TODO).


TypeError: Cannot read property 'syncScrollArea' of undefined

Run insiders on macOS and see in the console:
TypeError: Cannot read property 'syncScrollArea' of undefined
    at InputHandler.setMode (InputHandler.ts:1339)
    at InputHandler.ts:179
    at EscapeSequenceParser.parse (EscapeSequenceParser.ts:464)
    at InputHandler.parse (InputHandler.ts:319)
    at Terminal._innerWrite (Terminal.ts:1357)
    at Terminal.ts:1326

Maybe related to the new startup task that runs when opening the VSCode workspace from @alexr00 ?

This'll be fixed when vscode-xterm gets updated.


Getting error while running inference code

Hi, getting the below error while running inference code
python -m scripts.run_distillation
--in_dir ./examples/lock
--out_dir /path/to/output_dir
--weights_dir /path/to/weights
--name lock
Traceback (most recent call last):
  File "/home/mit/anaconda3/envs/upfusion/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/home/mit/anaconda3/envs/upfusion/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/mnt/d/Git/upfusion/scripts/run_distillation.py", line 17, in <module>
    from pytorch3d.renderer import PerspectiveCameras
  File "/home/mit/anaconda3/envs/upfusion/lib/python3.10/site-packages/pytorch3d/renderer/__init__.py", line 7, in <module>
    from .blending import (
  File "/home/mit/anaconda3/envs/upfusion/lib/python3.10/site-packages/pytorch3d/renderer/blending.py", line 10, in <module>
    from pytorch3d import _C
ImportError: /home/mit/anaconda3/envs/upfusion/lib/python3.10/site-packages/pytorch3d/_C.cpython-310-x86_64-linux-gnu.so: undefined symbol: _ZN3c106SymInt19promote_to_negativeEv

on wsl ubuntu, rtx 4090 with cuda 11.7

It should most likely be an issue with installing pytorch3d. I personally did not face this issue with the current installation script.
Could you try uninstalling and reinstalling pytorch3d? Do let me know if the issue still persists, thanks!

It worked. Uninstalled cuda and pytorch3d and reinstalled it.


Issue when upgrading to stack heroku-18

I just run into an issue after deploying the exact same project (same npm dependencies and puppeteer) in the new heroku stack heroku-18
/app/node_modules/puppeteer/.local-chromium/linux-579032/chrome-linux/chrome: error while loading shared libraries: libxcb-shm.so.0: cannot open shared object file: No such file or directory

Nothing else has changed, so I believe must be due to the new image upgrade?
I'm using 1.7 version of pupeteer

Hey @diervo thanks a lot for letting me know.
Can you please try resetting your build cache? The instructions for that are here: https://help.heroku.com/18PI5RSY/how-do-i-clear-the-build-cache
Then just make another commit to your project and push it to heroku which will cause heroku to run the build step again (just restarting dynos won't do this).
If that doesn't resolve it please let me know and we will figure it out!

@jontewks Thanks for the quick response.
I did two things removed the cache and used the buildpacks:
heroku/nodejs
https://buildpack-registry.s3.amazonaws.com/buildpacks/jontewks/puppeteer.tgz
I got a similar error:
/app/node_modules/puppeteer/.local-chromium/linux-579032/chrome-linux/chrome: error while loading shared libraries: libpangoft2-1.0.so.0: cannot open shared object file: No such file or directory

And also I started brand new app (private spaces)
with the master webpack: (https://github.com/jontewks/puppeteer-heroku-buildpack)
And with that I got the issue I stated previously.

@diervo thats odd since that library is listed in the buildpack.
Ok a few more things to try, can you try swapping the order of the buildpacks on heroku? This has seemed to help people in the past.
Can you also post your package.json just so we can peek at the version requirement for puppeteer?
Also would you mind posting how you are calling puppeteer in your code? Specifically where you call puppeteer.launch?

@jontewks Very odd, I just install it again from scratch, and ever time I get a different runtime missing dependency:
Error: Failed to launch chrome!
/app/node_modules/puppeteer/.local-chromium/linux-579032/chrome-linux/chrome: error while loading shared libraries: libpangoft2-1.0.so.0: cannot open shared object file: No such file or directory

Here is the full logs and the way I use puppeteer:
https://gist.github.com/diervo/921f04eef06c824bb9c43578e6c88729
For the record I have like 10 other instances up and running, it just started failing now...

Isn't: libxcb-shm missing?

Might be worth trying the forced garbage collection part of this as well?  http://engineering.generalassemb.ly/post/143896522629/the-heroku-build-cache-and-exceeding-compiled-slug

@jontewks I send you a PR request. A library was missing.

Yes but my concern is that heroku lists that package as available on heroku-18 all the time, and that I am not running into that issue myself with the test app. It would be pretty concerning to need to install dependencies even when heroku says they are available to your applications. Hoping to get to the bottom of the issue you are running into rather than patching it

@diervo I see you have your buildpack up so at least you aren't stuck, my concern is that once it showed one lib missing that should have been there, and another time it showed a lib missing that was specifically installed by this buildpack, so it really seems like there is something else going on that I'm not aware of since adding the dependency to the buildpack list didn't fix the issue in one of those cases.
If your code is public someplace I'd love to try to deploy it to an app as well and see what happens. Did you try different orders of buildpacks? Can you post a screenshot of your current setup? Also could you confirm the puppeteer version from your package.json?

@jontewks the other library was because I was using your old buildpack. You haven't upgraded heroku buildpacks:set jontewks/puppeteer I think.

Sorry the code is not yet public. If you are willing to sign a Salesforce NDA I can give you access :)

@jontewks the other library was because I was using your old buildpack. You haven't upgraded heroku buildpacks:set jontewks/puppeteer I think.

Thanks, I didn't realize I had to update heroku buildpacks manually, so that should be resolved.
A few last ditch effort things to try since its pretty strange that the issue only seems to be affecting you:

Can you try updating puppeteer to the latest version (1.8.0)? Its a different version of chromium, so its worth a shot
Can you run the following command and let me know the output: heroku apps:info -a APP_NAME
Can you run the following commands to open a bash shell on your app and manually inspect whether or not the library in question is available to you:

heroku run bash -a APP_NAME
Once shell is up and running, dpkg -s libxcb-shm0, and paste that output as well?

Connecting to my test app and doing the above I'm getting
~ $ dpkg -s libxcb-shm0
Package: libxcb-shm0
Status: install ok installed

Haven't heard back in a week, hopefully the issue is resolved for you somehow. I couldn't replicate this on my test apps or my company's production apps. Feel free to open the issue back up if its still happening.


Deprecated configurations around SPI_CS_GPIO

I was rebasing my Zephyr application on v1.13 RC1 when I noticed warning: SPI_CS_GPIO defined without a type.
Searching into Zephyr code base for the new feature that has been used to replace this configuration shows me there are few platforms (arch/x86/soc/intel_quark, boards/arc/arduino_101_sss, boards/x86/arduino_101) and SPI options (SPI_n_CS_GPIO_PORT  and SPI_n_CS_GPIO_PIN) depending on this non-existing KConfig option.
I guess it should be fixed/cleaned for v1.13.
I am not sure if SPI_CS_GPIO, SPI_n_CS_GPIO_PORT  and SPI_n_CS_GPIO_PIN can be simply removed.

Looks like we've removed these so closing this issue.  Please re-open if I missed something.


Cannot bootstrap FreeBSD (bash is not installed)

I am trying to bootstrap a FreeBSD droplet on DigitalOcean. I can get the Ubuntu one working, but the FreeBSD one fails with
RuntimeError
------------
Error: command 'bash -c ' bash /tmp/chef-install.sh'' exited with code 1.

At first I thought it was not running this with sudo, but then I logged in manually to run the command and remembered bash is not installed on the FreeBSD image! bash: Command not found.
I can't see any obvious way to tell this to use tcsh instead: https://github.com/chef/chef-provisioning/blob/4638bdf99e048452b5b80e06c118ba2a0a0132a3/lib/chef/provisioning/convergence_strategy/install_sh.rb#L36
Just some more context:
with_driver 'fog:DigitalOcean'
fog_key_pair 'my_key'

with_machine_options(
  bootstrap_options: {
    image_distribution: 'FreeBSD',
    image_name: '10.1',
    flavor_name: '512MB',
    region_name: 'San Francisco 1',
    key_name: 'my_key' # side note, this seems to do nothing and always uses chef_default
  },
  sudo: true, # tried with and without this
  ssh_username: 'freebsd')

Hopefully it is also prefixing everything with sudo correctly (I think it must as I have set ssh_user: 'freebsd' and before this command tries to run I do see, e.g.,
- write file /tmp/chef-install.sh on test.example.com

Confirmed the issue is that FreeBSD is missing bash: after manually running sudo pkg install bash I can converge the host.

Here is a workaround for now:
machine 'example.com' do
  action :ready
end

machine_execute 'pkg install -y bash' do
  machine 'example.com'
end

machine 'example.com' do
...
end

I'm spiking a solution to this currently


Added a tool

Password generator using python

Hey can you Pls add the label hacktober fest for the PR?

Hey, can you pls add hacktoberfest label to the PR?


[secure] Replace secure/time with common/time-service

Add "blocking" support for common/time-service. Users writing non-async code can call time_service.sleep_blocking(wait), which will block the current thread until wait duration has elapsed. In the real time service, this just does a std::thread::sleep.

Add MockTimeService auto advance feature. MockTimeService now has the option to auto advance time when new Sleeps are created. When we're auto advancing, new Sleeps are immediately resolved and the simulation time is advanced to the wait deadline. New Sleeps whose deadlines are after the auto advance deadline will be pending and must be manually woken by the MockTimeService::advance_{..} methods. A version of auto advance is already used by the consensus time service and is necessary to support blocking clients.

Replace secure/time with common/time-service. Some visible benefits include: (1) removes the T: TimeService trait that otherwise infected most of the types in secure/storage and (2) can now use the same time service across modules, including async modules like consensus and network.

Add async feature gating tokio in MockTimeService to prevent tokio from infecting the TCB.

 The time service crate was probably the hardest to upgrade due to the tokio Sleep type no longer being Unpin

Hopefully I don't hate life too much if this gets merged in before the tokio upgrade. The time service crate was probably the hardest to upgrade due to the tokio Sleep type no longer being Unpin

Hopefully I don't hate life too much if this gets merged in before the tokio upgrade. The time service crate was probably the hardest to upgrade due to the tokio Sleep type no longer being Unpin

Yeah I noticed that haha. I'm fine landing this after the tokio upgrade goes through : )

Hopefully I don't hate life too much if this gets merged in before the tokio upgrade. The time service crate was probably the hardest to upgrade due to the tokio Sleep type no longer being Unpin

Yeah I noticed that haha. I'm fine landing this after the tokio upgrade goes through : )

rebased
/land

rebased
/land

LSR dependency change summary:
target packages:
  A diem-time-service 0.1.0 (workspace, path 'common/time-service')
    * features: default
  R diem-secure-time 0.1.0 (workspace, path 'secure/time')
    * (old features: [none])

LSR dependency change summary:
target packages:
  A diem-time-service 0.1.0 (workspace, path 'common/time-service')
    * features: default
  R diem-secure-time 0.1.0 (workspace, path 'secure/time')
    * (old features: [none])

LEC dependency change summary:
target packages:
  A diem-time-service 0.1.0 (workspace, path 'common/time-service')
    * features: default
  R diem-secure-time 0.1.0 (workspace, path 'secure/time')
    * (old features: [none])

LEC dependency change summary:
target packages:
  A diem-time-service 0.1.0 (workspace, path 'common/time-service')
    * features: default
  R diem-secure-time 0.1.0 (workspace, path 'secure/time')
    * (old features: [none])

release binaries dependency change summary:
target packages:
  A diem-time-service 0.1.0 (workspace, path 'common/time-service')
    * features: default
  R diem-secure-time 0.1.0 (workspace, path 'secure/time')
    * (old features: [none])

release binaries dependency change summary:
target packages:
  A diem-time-service 0.1.0 (workspace, path 'common/time-service')
    * features: default
  R diem-secure-time 0.1.0 (workspace, path 'secure/time')
    * (old features: [none])


How do we know the size of the graph in memory after we call LoadIndex?

Hi searchivarius@,
Is there a way to know the memory consumption of the graph once loaded onto memory?
Usecase:-
I am trying to keep graphs which of certain size in memory and delete the smaller graphs right  away after usage

Hi @vamshin there's no direct API call for this. It's not difficult to implement the one that would estimate the size. However, it is difficult to know for sure due to all the fragmentation issues. That said on many OS you can surely estimate the amount of memory used by the program. So, you can estimate the footprint, load the graph, estimate the footprint and compute the difference.


WinRT class throws InvalidCastException on Desktop

In porting a library to WinUI3, a class started throwing an InvalidCastException.
It appears to fail trying to QI the class to an IDependencyObject.
This QI succeeds when done from a UAP but fails in a Desktop packaged app.
Version Info
CsWinRT 1.1.4
.NET SDK 10.0.19041.15
ProjectReunion.0.5.0-prerelease

@getrou - Are you authoring a C#/WinRT component? I assume you are creating a C#/.NET5 class library, and consuming it in a C# desktop packaged app (Project Reunion)?
Would you be able to provide a repro?

I too am encountering invalid cast exception when porting to WinUI3 for a desktop application.
The following line causes the exception to be thrown:
var bitmap = new CanvasRenderTarget(canvasdevice, 16, 16, 96);
Stack trace:
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHR(Int32 errorCode)
at WinRT.IObjectReference.As[T](Guid iid)
at WinRT.IObjectReference.As(Guid iid)
at Microsoft.UI.Xaml.DependencyObject..ctor(IObjectReference objRef)
at Microsoft.Graphics.Canvas.CanvasBitmap..ctor(IObjectReference objRef)
at Microsoft.Graphics.Canvas.CanvasRenderTarget..ctor(IObjectReference objRef)
at Microsoft.Graphics.Canvas.CanvasRenderTarget..ctor(ICanvasResourceCreator resourceCreator, Single width, Single height, Single dpi)
Microsoft.Graphics.Win2D  v<IP_ADDRESS>
Microsoft. ProjectReunion  v0.5.5
Microsoft.Windows.csWinRT v1.2.5


Update falco_rules.yaml

Signed-off-by: 0xsh4dy<EMAIL_ADDRESS>(clouddefense.ai)
What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area rules
What this PR does / why we need it:
Incorporated 21 new rules to detect a range of events, and for each rule, comments have been added that provide a comprehensive description of its function.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: 0xSh4dy
Once this PR has been reviewed and has the lgtm label, please assign andreagit97 for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @0xSh4dy! It looks like this is your first PR to falcosecurity/rules 🎉

@0xSh4dy thank you ❤ could we split this into 21 PRs and go one by one? Also I see it is mixed with formatting fixes. We could convert this PR into formatting adjustments and then open the first PR for the first new rule?

Thank you for these big contributions! I agree with @incertum, to let the review process be smoother, we better split this PR in many, and keep the formatting as a last step. If you have rules related together, feel free to deal with them in a single PR, but not more than 2/3 per PRs. Thanks a lot really appreciated!! 🚀

Thanks for the comments. We will raise separate PRs shortly. One of my teammate is going to raise a new PR. I'm closing this PR for now.


Update dependencies to fix vulnerabilities

This PR fixes vulnerabilities in ssri library. The problem is that we are not using it directly and in order to update ssri to the non-vulnerable version I had to update some of the other dependencies. But after the update tests seem to work, so we should be good.

Ping @amir-hadzic

Looks good I'll merge and deploy.

Awesome, thanks!


When to release the code ?

It is best if you could provide runable code other than pseudo code to eliminate vagueness, which would facilitate other researchers on your theoretic results also.

We sincerely apologize for the late reply. We would like to note that Algorithms 1 & 2 only serve as part of the proofs and should not be regarded as empirical approaches -- our work aims to build a principled framework to understand MAE rather than empirical approaches. Some analysis codes and checkpoints will be released ASAP, but not for Algorithms 1 & 2.

Same question.

Same question, still waiting...


Apostrophes/single quotes not handled

https://github.com/gtalarico/airtable-python-wrapper/blob/484f42edcabc0808880bd67b55cd1804161f0cfe/airtable/airtable.py#L581
This is an issue when for example searching for a name like "O'Brien".  The apostrophe in the name "closes" the apostrophe in the query and airtable throws an error.  In my local copy I just if'd my way around the problem, but it smells like there should be a more elegant way to handle this.

Interesting. Thanks for the suggestion.
Per the airtable documentation, I think single and double quotes need to be escaped with a backslash.
Maybe we can add a simple regex replacement that replaces unescaped quotes with /' and /"

It's easy enough to escape the input field value before it is passed into the function.
val_escaped = val.replace("'", r"\'")

I think #120 fixes this - feel free to reopen otherwise


Excel buffer functions

Is this the right place to request additional features for extending Excel Buffer / Excel integration (OnPrem)?
We used to have an OfficeHelper add-in to manipulate Excel files (client-side) by protecting a range, password protecting the Workbook and adding custom properties to the Excel file.  What would be the alternatives for the modern client to manipulate the generated Excels?
OfficeHelper.ProtectRange(XlApp, ProtectedColumns.xlColID + '1', ProtectedColumns.xlColID + Format(MaxRowNo));
OfficeHelper.SetPasswordOnWorkSheet(XlApp, ProtectionPassword);
OfficeHelper.AddCustomPropertyToActiveWorksheet(XlApp, WorksheetProperties.Code1, WorksheetProperties.Text1);

@JesperSchulz

Unsure if we can provide a solution. @AndreiPanko, what is your take on this?

I'm afraid I don't have an answer for you here on the spot. We realize that certain capabilities went away with the retirement of the windows client - such as running client side add-ins. So far, we've mostly been able though to develop server side equivalents, which also in this case seems viable! We also know, that our Office integration story is due for a little refresh after the move to the new client - work we do have in our backlog, but which I don't know when we'll get to!
Unfortunately I don't know enough about the functionality you need to advise you, if this indeed would work server side. Maybe the community can help you (e.g. mibuso forum?).
If you would like Microsoft to take a stab at this, I would advice you to create an idea on aka.ms/bcideas to get this routed to a team, which may have the capacity to execute on it. I'm afraid the workload is higher than what we can deal with through an issue in this repo. Sorry that I cannot be of more help on this issue right now.


Created Recursion Example Using C++

R-Recursion is already present here
please delete fork and commit your changes in right file path
Thanks Happy Coding !!


Add extra step to editing WSL terminal

Let's add another step to tell the user to reopen WSL after making changes to profile and and also add slight typo fixes

Awesome thank you for this! Everything looks good!


this.pin === undefined

If I'm not mistaken, this.pin is undefined here.

Doh, yes. Originally each peripheral had a single instance, looks like I forgot to refactor that method. This is why I initially wanted to do unit tests before I2C :).
I think it should be something like:
for(var i = 0; i < this[pins].length; i++) {
  delete this[pins][i];
}

Unfortunately I'm about to leave to go out of town, so I don't have time to implement, test, publish, etc until Monday, but I'll make sure to get right on it then.

I didn't get around to submitting a PR for this at the weekend. It's not a blocker for the I2C code.

No worries, I'll try and get to it tomorrow

Fixed with v1.1.1 of raspi-peripheral


Preocts 20220715

Codecov Report

Merging #5 (26477f1) into main (9db48bd) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main        #5   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           11        11
  Lines          238       268   +30
  Branches        18        19    +1
=========================================
+ Hits           238       268   +30

Flag
Coverage Δ

unittests
100.00% <100.00%> (ø)

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

Impacted Files
Coverage Δ

src/runtime_yolk/config_loader.py
100.00% <ø> (ø)

src/runtime_yolk/yolk.py
100.00% <100.00%> (ø)

tests/yolk_test.py
100.00% <100.00%> (ø)

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 9db48bd...26477f1. Read the comment docs.


FR: Make SpeechRecognition etc. large AI libs just "extra" dependencies.

SpeechRecognition  is a massive dependency, like pocketsphinx. And possibly others too. Making those dependencies "extra" would remove a lot distribution load, burden and install errors.
Anyway one wouldn't expect a tool "textract"  to run complex AI recognition tools just so light-mindedly - which are instable and non-deterministic. One wouldn't use those in serious projects. Usually such file types need to be filtered before letting textract try.
So these massiv AI libraries should better all become "extra" dependencies at least.

I came here to suggest the same thing: It would be great if textract was more lightweight by default. I only need something to extract text from common document formats such as .pdf, .rtf, .docx. The dependency on SpeechRecognition is problematic because its massive size greatly slows down build time of our project and increases the size of the resulting Docker image substantially.
As @kxrob suggested, the dependency could be moved to "extra" and the tool could provide clear instructions when the package is unavailable when trying to extract text from an audio file, e.g. "Extracting text from audio files is an optional feature. Please run pip install SpeechRecognition~=3.8.1".


Arduino GIGA R1 Support

Would it be possible to use this library with giga r1? Thank you!

no. that board uses a stm32-derivate


MAINT: Improve changelog documentation process

To aid in releases and PRs, it would be nice not to have to do so much changelog management. In particular, it would be great if:

We didn't have to tell people to add anything to doc/changes/latest.inc
A changelog could be (at least nearly) automatically generated

Ideas:

In sphinx-gallery we use github-changelog-generator in between releases. You label PRs (before or after merge!) to get them correctly categorized as enhancement/bug. I think you can even change the PR title after the merge to then have that text used in the changelog entry.

Clearly this list is incomplete :) @drammock or others feel free to add other ideas up here after commenting about them below

... and as part of this, we should abandon any further updates to names.inc. We can keep it for posterity / our old logs, but for the future we should use some automated tool to get the change -> GH user link, which then gets us their name (contributors should keep their GH profile up to date, if they don't, then they just get their handle as their name, which I think is okay) and we just link to their GH profile -- where they can keep and update their own URLs.

can we first experiment with this on a smaller repo like mne-bids ?

Message ID: @.***>

At least github-changelog-generator we've already used in SG for years now. But yes if we want to try something else then we could experiment elsewhere in principle.
But in practice I think you try the tool and see if it produces some usable RST or not, so it would be easy to evaluate in a PR I think....

ok you know better. Let's try !

Message ID: @.***>

I think you can even change the PR title after the merge to then have that text used in the changelog entry.

yes, and you can also define a certain GitHub label to explicitly exclude a PR / issue from the changelog, see e.g.:
https://github.com/bids-standard/bids-specification/blob/5d749397c50d33a498c629c279171667f439fae7/.circleci/config.yml#L123

FWIW I just went through the process with sphinx-gallery and this is the result:
https://sphinx-gallery.github.io/stable/changes.html#v0-12-0
label->section mapping is configurable. It still involves a few steps but in general it's faster and I think I'd prefer it to what we have now.
Ahead of our next release I could try running it on our repo for 1.4 and we could see the result. I don't think it would take too much time for me to mock it up at least.

Tentative plan from discussion with @agramfort and @drammock :

Continue using devel.rst for 1.6 release (i.e., ~1 month)
Use github_changelog_generator for the 1.7 release, meaning we no longer change devel.rst with every change

In the next month, I can try github_changelog_generator to see what it would have produced for 1.6 so we can iterate on that process ahead of time to make sure it's tractable.

@drammock thinking about this again, I'm starting to think towncrier might make sense:

Used by astropy etc. so we're not alone or blazing a new trail
There is an action to make sure there is a fragment which will help maintenance
Customizable sections will allow us to easily address #12233


[Proposal] Allow simple negation of validation rules with ! prefix

I needed a validation rules to check for the absence of a field on a table and thought negation would be useful in general, i.e:
!exists:user,id
I implemented it as follows: https://github.com/sooqini/framework/commit/fa50a03ae23b572c9cc2020d3cc9420a48141494

url validation doesn't have a negation. It would be interesting to have a validation rule to validate that the input provided WAS NOT an URL.
**Use case: **

input field to insert a YouTube Video ID
user is compelled to insert a video url, e.g. https://www.youtube.com/watch?v=vqqS8lYYSdk

@borys-p could you share your validator?

@isometriq sorry, can't find it now.
But you can write a custom Form Request class and use the (undocumented) method validator() to put your extra logic in. Then you have access to all request fields and can check if something is present, but it shouldn't be.

Yes i use that and sometimes validator::after()

Same here, would love to see this implemented!

I have use URL negation. '!url' would be real handy! :)


Add xproto module

I have reviewed all variables to have the type expected by the C Api functions, and works with my own project (github.com/rustmore/rumenu).

This PR duplicates some of the constants that are already defined in the 'xlib' module but doesn't include the structs from Xproto.h - that might make it difficult for other people using this package to know where to find constants and functions when looking at the Rust documentation or translating existing C code snippets (from blogs, StackOverflow, existing GitHub projects etc.) using X11 headers to Rust code using x11-rs.
My suggestion would be to have one Rust module per 'public' X11 header (eg. Xproto.h -> xproto, Xlib.h -> xlib, X.h -> x) with the same structs, functions and constants. These could be auto-generated in many cases. Thoughts @Daggerbot ?

I'm agree, I have to rewrite it to split the xproto, I think this must be xproto::xproto, xproto::x, xproto::xatom... etcetera.
Anyway there are some duplication between xproto and xlib because are independent packages, and X.h from xproto package have constants from the Xlib package, this means that for coherence, this must be duplicated, ins't it?

I'm agree, I have to rewrite it to split the xproto, I think this must be
xproto::xproto, xproto::x, xproto::xatom... etcetera.

By 'package' do you mean Debian/Ubuntu/Red Hat packages? On my system there is just one X.h file, perhaps I misunderstand?
I was thinking more along the lines of /usr/include/X11/<foo>.h => <foo> (so just 'x11::x' rather than 'x11::xproto::x'). The idea being that a code snippet beginning with:
#include <X11/X.h>
#include <X11/Xproto.h>
...

Could be easily translated into Rust as:
use x11::x;
use x11::xproto;

I'm using the http://cgit.freedesktop.org/xorg/proto/xproto/ repository as base for the xproto, then I'm think in this like an indpendent package (I don't have a good knowledge about X11 C library, I'm learning it while I create my project, and when I needed extra constants I tried to find the better way to include it :disappointed: )
Anyway, knowing that the base of the code used must be my system /usr/include/X11, I think I can retry it.
Thanks for your patient and the info :)

Then, I'm thinking that some variables from xlib.rs must moved to x.rs, ins't it? mainly all the X.h constants. It's correct?

I'm going to close this PR and open probably other 2. One for include in the xlib.rs all the X.h constants, and one with the Xproto.h structures and constants.
Thanks for your help @robertknight


docs: fix some formatting issues

While reviewing Rasmus' PR I spotted a few other formatting issues. Mainly malformed pull-quotes and nested inline markup issues.

Good spot. 😄


Fix mixin annotation processor issues

I noticed you asked for help with these issues in the mixin channel of the SpongePowered discord server and I decided to take a look. These issues were caused by CompilationConfig.configureCompilation() overwriting JavaCompile's options.compilerArgs list which removed any previously added arguments, including those added by fabric-loom and mixingradle. I decided to make this as a pull request so that people in the future may find this/can be linked to this for a explanation and solution to this issue.

Ah, that was my mistake. I forgot to contact the lists rather than overwrite them

Thanks! I've been trying to figure out what was going on for months, lol


Handling infinite redirection loop

Fixes infinite redirections to the same url. This could happen when we get a 302 HTTP code by response and the referrer never changes.
Typhoeus seems to have its own infinite loop redirection control but also seems to not be working at the moment: https://github.com/typhoeus/typhoeus/blob/181834e2483d392d0f7ab0cd17f544cd252c7b2f/lib/typhoeus/request.rb#L217

Closing, not compatible with latest changes


test(createRenderer): add tests for element rendering

@yyx990803 your request was completed

You need test updated props in https://github.com/vuejs/vue-next/pull/382#discussion_r339302486

Sorry, merged #699 before coming back to this one. Still, thanks for the PR!


Should we require all scopes to be used?

A transaction specifies the scopes that it must access, these scopes in turn impact when it can be scheduled. If a transaction specifies a scope that is not used then it represents unnecessary locking.
On the other hand, it may not be possible to know if a scope will be accessed at the time the transaction is generated.
When it comes to billing a contract we should count CPU time as execution time * scopes.size()^2

This would help.  I have this hack in place now, I'm not sure if it will work..
For example:
struct transfer
   from      AccountName  # may not be the message.sender if message.sender has delegated authority by from
   to        AccountName
   amount UInt64

transfer inita initb 1 yields scope: ['inita', 'initb'], authorization: ['inita', ...]
given the following hack:
    {// FIXME Hack, until an API call is available
      const fields = Object.keys(definition.fields)

      const f1 = fields[0]
      if(definition.fields[f1] === 'AccountName') {
        tx.scope.push(params[f1])
        tx.messages[0].authorization.push({
          account: params[f1],
          permission: 'active'
        })
      }

      if(fields.length > 1) {
        const f2 = fields[1]
        if(definition.fields[f2] === 'AccountName') {
          tx.scope.push(params[f2])
        }
      }
}

Does not work with new account.. newacct probably should not be in the scope because it does not exist in the block that the newacct will execute in.
struct newaccount
   creator   AccountName
   name      AccountName
   owner     Authority
   active    Authority
   recovery  Authority
   deposit Asset

yields scope: ['creator', 'newacct'], authorization: ['creator', ...]
So, I need the scope to be automated or done in an API call or I'll start adding these case by case to eosjs.  Also, notice the authorizations is something we need too.

OBE


Test against PHP 7.1

Coverage remained the same at 100.0% when pulling 31aa7c7364da6e4680e7de82f8d08cceab9dc125 on php71 into 64737947ac65adfdae376ca10ffb2bc8d9bd7e9e on master.


remember why we're using 'script' to launch pytest

Add a comment in case we forget why script was needed here.

Thanks


Do not crash Executor when send_response fails due to client failure

https://github.com/ros2/rclcpp/pull/2276/ got merged

We should cherry-pick the original commit rather than copying it

Created https://github.com/irobot-ros/rclcpp/pull/119 for galactic.
https://github.com/irobot-ros/rclcpp/pull/120 for Iron