SubfloatFlow causes incorrect decompilation with large constants

Describe the bug
The SubfloatFlow rule traverses the operation tree of float2float PcodeOps backwards and converts floating-point constants to the same precision as the float2float output, if I understood correctly. This can cause issues when, for instance, two large floating point numbers are subtracted from each other, resulting in a (relatively) small floating point number which may get rounded down to 0 if the two large numbers are rounded to a smaller floating-point precision format.
Note that I am not asking for this simplification rule to be entirely removed, as it does a good job at keeping the output clean while only slightly reducing the accuracy of the output. But it would be better if this rule were not applied to operations which have only constants as input (since those will be eventually simplified by RuleCollapseConstants, and accuracy can be vital there to having the correct result, see demonstration program)
This issue was first noticed in an instance where the PowerPC int-to-float conversion sequence (https://www.warthman.com/images/IBM_PPC_Compiler_Writer's_Guide-cwg.pdf#G9.303610) was used on a constant value. A simpler example to demonstrate the problem is provided below in the "Additional context" section.
To Reproduce
Steps to reproduce the behavior:

Assemble the provided demonstration program.
Import it into Ghidra and analyse with default settings.
Observe that the decompiler outputs the following:

void demo_float2float_propagate(float *param_1)

{
  *param_1 = 0.0;
  return;
}

Expected behavior
The expected output of the decompiler is:
void demo_float2float_propagate(float *param_1)

{
  *param_1 = 16962.0;
  return;
}

Environment (please complete the following information):

OS: Windows 11
Java Version: 17.0
Ghidra Version: 10.2-DEV
Ghidra Origin: locally built from master

Additional context
_Z26demo_float2float_propagatePf:
    lis r4, fconst1@h
    ori r4, r4, fconst1@l
    lis r5, fconst2@h
    ori r5, r5, fconst2@l

    # load the two large constants and subtract them
    lfd f1, 0(r4)
    lfd f2, 0(r5)
    fsub f1, f1, f2

    # convert result to 32-bit floating point and store into 0(r3)
    stfs f1, 0(r3)
    blr

fconst1:
#<PHONE_NUMBER>871106.0
.long 0x43300000, 0x80004242
fconst2:
#<PHONE_NUMBER>854144.0
.long 0x43300000, 0x80000000

demo_compiled.zip
Edit: In order to conform with the floating point conventions of the PowerPC architecture, there should actually be an frsp f1, f1 before the stfs instruction, but since the decompiler output is the same with and without that line, this is irrelevant for this issue.

@caheckman This ticket has been on "Internal" status for over a year now - has there been any progress towards a fix for this? Would be greatly appreciated, this bug keeps coming up occasionally "in the wild", messing up the decompiler output.

Nice!! 🤯


API wrapper for plugin

Instead of providing raw plugin access, we want to wrap the plugin in a nice facade supporting local TS objects like Date and Enum

closed in #9


libqpdf/Pl_SHA2.cc calls functions that aren't defined in libqpdf/sha2big.c if SPH_64 isn't set to 1

In qpdf 6.0.0,  libqpdf/sha2big.c has several functions that are only defined if SPH_64 is set to 1 (via libqpdf/sph/sph_types.h). However, some of those functions are called from libqpdf/Pl_SHA2.cc with no check for SPH_64's value - examples are:
sph_sha384_init()
sph_sha512_init()
sph_sha384()
sph_sha512()
sph_sha384_close()
sph_sha512_close()
This causes compilation failures when SPH_64 isn't set to 1.
Note that this also impacts libtests/qtest/sha2.test, which fails with undefined function errors when SPH_64 isn't set to 1.

Sorry for the long delay on responding to this. I'm not going to fix this. However, I may implement #218, which would make this irrelevant. There are other parts of qpdf that won't work without a 64-bit type, so I don't think this is worth fixing.


Xcode 10 GM Uncategorized error during build

Hi,
We've got a Swift compiler errors "Command CompileSwift failed with a nonzero exit code" while compiling in Xcode 10 GM .
Xcode 10 GM (Version 10.0 (10A254a))
PromiseKit v6.2.8 with cocoapods. (same with v6.4.0)
Thanks

We've been building against Xcode 10 for over 2 months, and have the travis successes on CI to prove it.
Maybe you can provide some more information, like the build log.


Soon Git, soon I know how to do this alright...

Background

Changes

Documentation

Test Plan

PR Quality Checklist

[ ] My pull request is atomic and focuses on a single change.
[ ] I have thoroughly tested my changes with multiple different prompts.
[x] I have considered potential risks and mitigations for my changes.
[ ] I have documented my changes clearly and comprehensively.
[ ] I have not snuck in any "extra" small tweaks changes.
[x] I have run black . and isort . against my code to ensure it passes our linter.

This is the way.

This is the way.


Fix off-by-one error in reading TileDB File arrays.

Also updates test to verify fix.

Tested with rest server and works


fix: unhandled promise error when response has invalid json format

What kind of change does this PR introduce?
on handleError method, we call error.json() without a catch block. It can end up with an unhandled promise error. This kind of error can kill a Nodejs application
What is the new behavior?
add catch block and reject with a StorageUnknownError

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


File Uploader

In gitlab by @CalumTowers on Nov 26, 2016, 22:18
Create a page for Ops to access where they can upload sector files to the correct directory.
Relevant security should be put in place to check the file type etc.

In gitlab by @CalumTowers on Nov 27, 2016, 14:13
@A-Lawrence Can I get your opinion on this please before we look at putting it up for grabs?

In gitlab by @CalumTowers on Nov 27, 2016, 14:13
Made the issue confidential


Implement exports in Kh2SystemEditor

I have only KH2 Japanese and KH2FM, thus I cannot verify whether text output is good or not. Please someone test it.

I guessed that UCM (universal character modifier) discussed at discord may be associated with Id of item table. Thus exporting item list should help knowing about ARD file structure. Just I guessed.

Copy encoding idea from Place Editor:

Export seems to be ok too:

Thanks for reviewing! I'll check it

OK this will be better...

I did not know you had to duplicate the entire class to allow to export them as any format. I am sure that later on a common solution will be found and we can refactor it. For now, I will be happy to merge the changes!


An error that occurs when setting hyperparameters "'x' must be numeric."

Let me ask you about an error that occurs when setting hyperparameters in Robyn, "'x' must be numeric.".
(I reinstalled Robyn today, so I think the version is 3.10.4.
This is an error that did not occur when I used version 3.7.1.)
After entering the hyperparameters as below,
////////
hyperparameters <- list(
media_A = c(0.5, 1),
media_A = c(0.3, 1),
media_A = c(0, 0.05),
media_B = c(0.5, 1),
media_B = c(0.3, 1),
media_B = c(0, 0.2),
train_size = c(0.5, 0.8)
)
////////
run "InputCollect <- robyn_inputs(InputCollect = InputCollect, hyperparameters = hyperparameters)".
Then the following error occurs.
////////
Error in mutate():
ℹ In argument: ds = cut(.data$ds, intervalType).
Caused by error in cut.default():
!  'x' must be numeric.
Backtrace:
▆

├─Robyn::robyn_inputs(InputCollect = InputCollect, hyperparameters = hyperparameters)
│ └─Robyn:::robyn_engineering(InputCollect, ...)
│   └─Robyn:::prophet_decomp(...)
│     └─Robyn:::set_holidays(dt_transform, dt_holidays, intervalType)
│       └─... %>% ...
├─dplyr::summarise(...)
├─dplyr::group_by(., .data$ds, .data$country, .data$year)
├─dplyr::select(., .data$ds, .data$holiday, .data$country, .data$year)
├─dplyr::mutate(., ds = cut(.data$ds, intervalType))
├─dplyr:::mutate.data.frame(., ds = cut(.data$ds, intervalType))
│ └─dplyr:::mutate_cols(.data, dplyr_quosures(...), by)
│   ├─base::withCallingHandlers(...)
│   └─dplyr:::mutate_col(dots[[i]], data, mask, new_columns)
│     └─mask$eval_all_mutate(quo)
│       └─dplyr (local) eval()
├─base::cut(.data$ds, intervalType)
├─base::cut.default(.data$ds, intervalType)
│ └─base::stop("'x' must be numeric")
└─base::.handleSimpleError(...)
└─dplyr (local) h(simpleError(msg, call))

└─rlang::abort(message, class = error_class, parent = parent, call = error_call)

////////
And run "print(InputCollect)", Robyn says"Hyper-parameters: Not set yet".
All data is either integer or numeric.
And I am converting a date column to date data as below.
////////
data$DATE <- as.IDate(data$DATE)
////////
What is the problem with this error and how can I resolve it?

Your hyperparameter names don't look right. They should be media_A_alpha, _gamma, _theta etc. please read the demo.R guides

We've actually deprecated data.table from Robyn completely. You're installing from CRAN right? You should get rid of this problem if you install from GitHub.

I strongly recommend to use the latest version for future modelling. Backwards compatibility is not always guaranteed.

Please reopen if necessary.


Approvals are not excluded from task timeout

At the moment there is a task timeout for all tasks, including approvals.
Approvals require manual interaction and therefore we don't need a timeout here.

The implementation of the issue: https://github.com/keptn/keptn/issues/3778 (ShipyardController: Termination of orphaned tasks) terminates a sequence when a task is .triggered that does not receive a .started event.
To address the above-mentioned bug, the approval service has to send out an approval.started event when reacting on an approval.triggered event.

If the approval is set to automatic then the approval-service will take care of sending the approval.finished
If the approval is set to manual  then the finished event will be received when, e.g., the user presses a button in the Bridge.

By sending the approval.started immediately, the timeout (TASK_STARTED_WAIT_DURATION) of the shipyard controller gets ignored and the task can stay open as long as needed.
To be discussed: If this is implemented, the Bridge does not need to send the approval.started event anymore.


@motorcycle/dom fails to bundle

It works if I try to browserify the module by itself on my pc (I'm using npm3). Here's the output:
https://wzrd.in/debug-bundle/@motorcycle%2Fdom
---FLAGRANT SYSTEM ERROR---

(logs uuid: 0a022f30-f404-11e5-a27b-c9bb8d56db80 )

Error: "browserify exited with code 1"

code: 1
stderr: Error: Cannot find module 'most/lib/source/MulticastSource' from '/tmp/@motorcycle%2Fdom116227-23032-9i8wnx/node_modules/@motorcycle%2Fdom/node_modules/@most/hold/dist'
    at /usr/lib/node_modules/browserify/node_modules/resolve/lib/async.js:50:17
    at process (/usr/lib/node_modules/browserify/node_modules/resolve/lib/async.js:119:43)
    at /usr/lib/node_modules/browserify/node_modules/resolve/lib/async.js:128:21
    at load (/usr/lib/node_modules/browserify/node_modules/resolve/lib/async.js:60:43)
    at /usr/lib/node_modules/browserify/node_modules/resolve/lib/async.js:66:22
    at /usr/lib/node_modules/browserify/node_modules/resolve/lib/async.js:21:47
    at Object.oncomplete (fs.js:107:15)

dirPath: /tmp/@motorcycle%2Fdom116227-23032-9i8wnx

This is probably an issue with the package, and not browserify-cdn itself.
If you feel differently, feel free to file a bug report at:

    https://github.com/jfhbrook/browserify-cdn/issues

Include the ENTIRETY of the contents of this message, and the maintainer(s)
can try to help you out.

Have a nice day!

Nvm, sorry. This is an issue with the @motorcycle/dom package itself because most is a peerDependency rather than a dependency, and I accidently had most installed:
[user@arch motorcyclejs-seed]$ browserify -r @motorcycle/dom  -s dom -o dom.js
Error: Cannot find module 'most' from '/home/user/git/javascript/motorcyclejs-seed/node_modules/@motorcycle/dom/lib'
    at /usr/lib/node_modules/browserify/node_modules/resolve/lib/async.js:46:17
    at process (/usr/lib/node_modules/browserify/node_modules/resolve/lib/async.js:173:43)
    at ondir (/usr/lib/node_modules/browserify/node_modules/resolve/lib/async.js:188:17)
    at load (/usr/lib/node_modules/browserify/node_modules/resolve/lib/async.js:69:43)
    at onex (/usr/lib/node_modules/browserify/node_modules/resolve/lib/async.js:92:31)
    at /usr/lib/node_modules/browserify/node_modules/resolve/lib/async.js:22:47
    at FSReqWrap.oncomplete (fs.js:82:15)


Server Crash when player near area

Issue description:
When a specific player's base is loaded on the StoneBlock modpack the player is kicked and the server assumes a crash and shuts down.
What happens:
same as above
What you expected to happen:
no crash
Steps to reproduce:
Unknown. It would appear to be a corrupt autocrafting function but the players couldn't remember anything and the the locations of said issue were not in the crash logs.
Version (make sure you are on the latest version before reporting):

Minecraft: 1.12.2
Forge: forge-1.12.2-<IP_ADDRESS>68-universal.jar
Refined Storage: 1.6.8 (& addons 0.4.2)
StoneBlock modpack version: 1.0.25

Does this issue occur on a server?
Yes
If a (crash)log is relevant for this issue, link it here:
https://pastebin.com/bBZZmcg7

This is a watchdog crash, which may or may not be an RS problem. Can you reproduce this without RS?

Okay, then I'll have to close this since there's not anything more I can do.

@raoulvdberge This has happened again on another pack (World of Dragons) not long after the creation of a max size auto crafting setup that was chunk loaded. I can provide crash logs for that too if it'll help.


Entities - Match design

What has changed and why?
Changing the page to match design
Wasn't sure what to do with the badges though, any suggestions welcome.

How to test this change

[ ] test in multiple browsers
[ ] test in mobile view
[ ] at least one a reviewer ran the code

Gorgeous.


Behaviour of sqleet library if call to entropy function fails

In the implementation of the functions entropy and read_urandom you chose to call system function abort in case of failure to provide random data.
I don't know under which exact conditions a failure might happen. However, for a library I find it inappropriate to abort the process/application. The application should at least get a chance to handle this situation and to gracefully shut down the application. Yes, it is possible to implement a signal handler, but the library behaviour should be at least documented, so that a developer is aware of this.
Personally, I would prefer a solution where some sort of fallback function would be called in case the system function fails. For example, one could provide an own PRNG - yes, maybe slightly less secure, but certainly better than aborting the process. In addition, a warning message could be written to the log.

I agree that the current behavior is non-ideal. A better approach is to return an error and prevent accessing encrypted databases if entropy generation fails. Maybe also spam error messages to stderr given the critical security implications of the failure. In practice, entropy generation should never be broken except maybe on emulators or early in the boot of embedded systems.
In my opinion, the best solution would be to avoid pseudorandom number generation altogether by switching to deterministic nonces based on counters or hashes. However, maintaining persistent counter(s) in a simple and efficient way is an unsolved problem in the context of SQLite3 encryption extensions. Hashing the plaintext contents of a database page incurs a small performance hit but would be easy to implement. Replacing the hash algorithm with keyed BLAKE2 (or other HMAC) would be nice as the result could serve as a MAC and nonce for ChaCha20 at the same time (allowing removal of Poly1305, but that would break compatibility).
Anyway, I will modify the code to return errors on failing entropy generation. And maybe consider the fancy HMAC nonces for the next major version of sqleet (if there ever will be one).


Rule checks are applied to logsource configs/mappings

Seems hard to fix. I could add a check, so that files that are withing the config directory would not get set as Sigma.
Seems a bit like a hack but that's the best way i can think of right now


Latest fxcop fixes

Let's see if GlobalSuppressions.cs is still necessary.

@joelverhagen updates since our discussion:

NoWarn didn't work for CA3103 for some reason, so I left GlobalSuppressions.cs with module-level suppressions (generated by FxCop.exe) that actually worked. Changed to UTF-8 encoding, since GitHub thinks this file is binary.
Didn't need all the csproj changes I had, so reverted
Removed a lot of the old inline suppressions and CodeAnalysis references in csproj, which don't seem to be relevant anymore
This PR fixes errors, but we have lots of TSA issues for warnings to fix (~700 across all repos)

/cc @agr @scottbommarito Checking in, to finish off this task... but feel free to 'r' me with feedback for changes since you approved.


Consider "inlining" oneof messages

In addition to #41, I was wondering if inlining message fields into oneof generated enums might be something you'd consider.
message Foo {
    oneof foo_type {
        Bar bar = 1;
        Baz baz = 2;
        float y = 3;
    }
}

Bar {
    required string a = 1;
}

Baz {
    oneof baz_type {
        int32 id = 1;
        float number = 2;
    }
}

Can be interpreted as
// Omitting probably necessary module scoping

enum BazType {
    Id(int),
    Number(float),
}

enum FooType {
    Bar { a: String },
    Baz { baz_type: Option<BazType> },
    Y(f32),
}

struct Foo {
    foo_type: Option<FooType>
}

Which also reduces stutter a lot. This would allow the code I mentioned in my reply to #41 to be (in addition to the switching to Unknown fields)
match self.specific_msg {
    SpecificMsg::Config {
        which_module: WhichModule::CoreCfg {
            plugin_type: plugin_type,
        }
    } =>{ /* do things */ },
     SpecificMsg::Config {
       which_module: WhichModule::CoreCfg {
            plugin_type:  OneOfEnum::Unknown,
        }
    } => panic!("Invalid plugin_type"),
    SpecificMsg::Config {
        which_module: WhichModule::Unknown
     } => panic!("This module doesn't handle this type of config"),
    SpecificMsg::Unknown => panic!("Invalid variant denoting the specific message type"),
}

It's not quite as notable with this example, but it reduces the fact that all oneof fields have to be double nested which causes a lot of extra levels. It also looks a lot more like the Rust code I'd write to describe these types. Personally, I'd prefer having both an inline enum and a struct I can convert to (if the message occurs outside this context) that always having to use a struct. Because I have a lot of oneofs with marker messages like
message Foo {
    oneof type {
        A a = 1;
        B b = 2;
        C c = 3;
        D d = 4;
    }
}

message A {}
message B {}
message C {}
message D { required string name = 1; }

Because marker messages reduce error handing from the other way of doing this (enums with accompanying optional fields) as well as improving future extensibility.
To me this is basically the exact same thing as writing
enum Foo {
    A,
    B,
    C,
    D { name: String },
}

(Albeit prost would probably generate a struct with one field for Foo which is fine, I don't expect too complex of auto-sugaring).
This is neglecting the Option/Unknown variant of course, but if #41 is not adopted in favor of Unknown variants, there's no harm in just generating struct Foo { type: Option<foo::Type> } and if it is it's just an extra variant.
I'll admit there are some questions about the semantics here with regards to if you can/should do this if a message is used both as a field and in a oneof, but personally I'd prefer having both a standalone and an inlined variant available to having to use the struct because I tend to use deeply-nested messages. At the very least, I think this should be done if it appears a message is only used as a oneof variant.

I've been thinking about this.  Unfortunately it would be very hard to support two different representations of oneofs, and it would add a lot of testing surface area.  I'm inclined to stick with wrapping oneofs in an Option for one important reason: once the Option part of the field has been peeled away, the inner oneof type can be operated on without worrying about non-existence, including passing it to another method.
Unfortunately there is an impedance mismatch between Protobufs and Rust.  The over-abundance of Optional fields is also an issue when working with proto2, which I do a lot.  I've found defining a helper trait like the following in the end-user project to be really helpful for dealing with protobuf-optional fields which are in reality required in order to make sense of a message:
pub trait ExpectField {
    type Value;
    fn expect_field(self, message: &'static str, field: &'static str) -> Result<Self::Value, Error>;
}

impl <T> ExpectField for Option<T> {
    type Value = T;
    fn expect_field(self, message: &'static str, field: &'static str) -> Result<T, Error> {
        match self {
            Some(value) => Ok(value),
            None => Err(Error::Serialization(format!("required field absent: {}::{}",
                                                     message, field))),
        }
    }
}

(obviously this will need to be adapted to whatever error type you are using in your application).
The idea is that when you are unpacking the message with optional fields, you can call expect_field("MessageName", "field_name")?, which is a pretty light-weight way to handle the non-existence.  If you are OK panicking, expect_field could return T instead of a result.


[BM-663] Changed onboarding feature text and resized the text area.

Task

JIRA

          1 Message

:book:
:link: BM-663

JaCoCO Code Coverage 18.72% :white_check_mark:

Class
Covered
Meta
Status

APK file size

size

30.4MB

Number of method references

Dex file
count

classes.dex
46966

  Generated by :no_entry_sign: Danger


Refactor reflection parts

Removed the need for recreating reflection properties and methods in the get*WithAttributes methods and improved the logic of some parts to be more crisp.

Also added a reflection instance cache as all we now need is one ReflectionClass instance


Request to customize the markdown link format of the file

This plugin is very useful for me, thanks to the author! I have a new requirement, I wonder if it can be realized?
When wikilink is disabled in obsidian, paste an image into a markdown file whose file name contains whitespace, and the generated link will be like this:
![](assets/my%20file/file-202409.png)
I hope to add a configuration to generate a link format like this:
![](<assets/my file/file-202409.png>)
If the path name or file name contains spaces, use the (<link>) format link.

This can be done via https://github.com/mnaoumov/obsidian-better-markdown-links

@mnaoumov
Thanks for your reply, this plugin has the function I want, thank you!


Add world pose, remove dep on scipy Rotation

Also removed a scipy dist for numpy linalg.norm
TODO: some euler<->quat functions still used in arb

Removed scipy from ARB. ARB needs repair, but for this pull: LGTM!


Resize image does nothing...

Microsoft PowerToys version
Release v0.77.0
Installation method
Microsoft Store
Running as admin
Yes
Area(s) with issue?
Image Resizer
Steps to reproduce
Install the app and try to use it as intended.
✔ Expected Behavior
Open a File Explorer window
Choose 1 or more images
Select Image Resize from pull down
Images are sized and refreshed
❌ Actual Behavior
Open a File Explorer window
Choose 1 or more images
Select Image Resize from pull down
Nothing happens.
Menu goes away and images have not been touched.
PowerToysReport_2024-01-09-11-19-53.zip
Other Software
No response

Seems like ImageResizer isn't even opening. I've got no logs from what I can see.
Are these images in any special Path, like a path that represents image in a cloud account? Where are the images located?
If you try to run "PowerToys.ImageResizer.exe" directly from "C:\Program Files\PowerToys", a file picker should appear to let you select the images. Are you able to do it this way?
/needinfo

Hi @eAddict , this means it is not working when trying to use the context menu entry, right? Do you get any error in the Windows "Event Viewer" when you try to use Image Resizer through the context menu? /needinfo

No errors now.  And it seems since that it worked once directly it now works through the File Context Menu.
-Vince
On Wednesday, January 10, 2024 at 09:18:19 AM MST, Jaime Bernardo @.***> wrote:
Hi @eAddict , this means it is not working when trying to use the context menu entry, right? Do you get any error in the Windows "Event Viewer" when you try to use Image Resizer through the context menu? /needinfo
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Thanks for the feedback @eAddict


No documentation for those defined functions

clangd version: 10.0.0 (https://github.com/llvm/llvm-project.git f01b9aa89e8cd5d3cca0e13835302f69c1f879d2)
OS: win10

foo.cpp

#include "foo.h"

void foo() {}

foo.h

#ifndef FOO_H
#define FOO_H

// foo is defined
void foo();

// bar only have declaration
void bar();

#endif

main.cpp

#include "foo.h"

int main() {
    foo();
    bar();
}

compile_commands.json

[
    {
        "directory": "F:/VSCode/tt",
        "command": "g++ -Wall -o F:/VSCode/tt/main.cpp.obj F:/VSCode/tt/main.cpp",
        "file": "F:/VSCode/tt/main.cpp"
    },
    {
        "directory": "F:/VSCode/tt",
        "command": "g++ -Wall -o F:/VSCode/tt/foo.cpp.obj F:/VSCode/tt/foo.cpp",
        "file": "F:/VSCode/tt/foo.cpp"
    }
]

Open main.cpp after opening foo.cpp

the older version clangd version 10.0.0 (https://github.com/llvm/llvm-project.git 8d6a863b02f199960590973f06b4c4dd29df578f) works fine.

https://reviews.llvm.org/D68467

I believe this is a regression, we should still show documentations for these functions, fixed in https://github.com/llvm/llvm-project/commit/41104a9406dd284d984f7bee30c7756fcfe2b59e.


Release appconfiguration armappconfiguration v0.1.0

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] MIT license headers are included in each file.

/azp run prepare-pipelines

/azp run go - armappconfiguration - ci

/check-enforcer override


add repost and comment function

This P.R.
Import repost and comment function.
Limit the displays in profile.php?u=antriez are all posted by antriez.
Can check his/her followers and following.

:+1:  +1


Cannot create host port binds on 443

I'm running a cluster generated with kube spray on Ubuntu 1604 bare metal with calico networking. I need to expose 443 for ssl on web apps, but when trying to add it to all my hosts I get an issue with pods not being able to access the internal Api through <IP_ADDRESS>:443. Note, my masters have scheduling enabled but this happens even if I cordon off masters.
Expected Behavior
When creating a host port on 443 I assume I can route to the proper pod and still have my pods be able to connect to the internal Api endpoint.
Current Behavior
All internal Api calls in pods get connection refused errors and port mapping doesn't work for the external access
Possible Solution
Steps to Reproduce (for bugs)

Create a daemon set that exposes on the host port 443

Context
I'm trying to port an older coreos cluster to a new k8s install and they used virtual ips and keepalived to have psuedo load balancing in the cluster. Currently I just want to get their systems running on the new cluster because the old one is degrading. The keepalived in k8s should theoretically still work fine but I'm running into issues.
Your Environment

kubespray default configuration on Ubuntu 1604

@fasaxc Yea that is the case. I ended up moving towards metallb instead since it accomplishes exactly what I want it to do and there aren't port conflicts. This is a non-issue and not really related to calico.


Fix a bug

A bug exists where becoming more emo causes the "I'm becoming well-adjusted" message. This SHOULD fix that.

Thanks!

Also please note that I've now rebased master with the gh-pages content, and deleted gh-pages. So your changes are now applied to master.


Removing prefix on default language ?

Hello there , I am pretty new at laravel , and I've started my first project with translations. I can't figure out if it is possible to remove the prefix for the default language .  For example if the site def language is English the url should be example.com and if it is French example.com/fr ?

I don't think this package handles any URL logic, you have to work that out yourself. Like in the tutorial in the readme.
You could do something like adding the locale (prefix) as an optional route parameter, and set your app's locale to the default locale if no the parameter was not found in the route.


Add all the things to publish to PyPi

Before merging, make sure to set up trusted publishing with PyPi. From there, it should automatically push a new version every time you commit to main
https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/#configuring-trusted-publishing

┌──(kali㉿kali)-[~/git/ntlm_relay_gat]
└─$ pipx list
venvs are in /home/kali/.local/pipx/venvs
apps are exposed on your $PATH at /home/kali/.local/bin
manual pages are exposed at /home/kali/.local/share/man
   package ntlm-relay-gat 0.1.dev15, installed using Python 3.11.7
    - ntlm-relay-gat


Suggestion: Toggle Off change cells on hover

Find myself changing numbers in the cells by mistakenly hovering over them with mouse.... Batch set to 50 all a sudden! Be great to toggle this feature off once locked in.

Sorry but i can't do it because it's a native component of comfyui and i don't have any control on it :(


[question] - is sql filter enable by default ?

check here :https://github.com/apache/rocketmq/blob/aaa92a2e53d773c7f1d9e9f25e41709f6948fa83/common/src/main/java/org/apache/rocketmq/common/BrokerConfig.java#L149


ACUS: Better explain the new auth system and needing to create a userid

Three people so far keep trying to reset their old userid ...

We had the same problem with acnw. It's hard to make people read, too little and they ignore it, too much and they ignore it.
Btw there is a faq entry on auth issues, maybe we link to it by the login button.
https://www.ambercon.com/faq

Yeah. Added some bold text to summarize, a link to the FAQ, and a step-by-step on what to do.


Award badges from person-edit view

This is a little bit alternative to #110, and somewhat more limited in options, as it only allows us to add one badge per request from the person-edit view.
However, in here we use two crispy forms that integrate easily and visually appeal, + we have tests in place.

This may require a little rebase if we merge #336 first.

Rebased.
@gvwilson are you happy with this PR as a solution to #37 °1?

I'll test it tonight - about to head out for a bit.

Since we can now set superuser in the "edit person" view, we should show superuser status on the "person details" page.
When I clicked "Change password" for a person who didn't already have a password, the "New Password" field was auto-filled with one of my browser's saved passwords.
Badge award works!

So I'm :+1: to merge as-is, and file separate issues for 1 and 2 above.

Thanks!!!


[FEATURE] Convert all issue templates to issue forms

Proposal
We should use the newly provided GitHub issue forms. These can prevent blank issues or issues without enough information.
We can mark fields as optional or required, making things much more efficient, IMO.
Check the official GitHub blog about this: https://github.blog/changelog/2021-06-23-issues-forms-beta-for-public-repositories/
Additional
I want to work on this. 🙂

Hi,
Thanks for your proposal, looks good.
It will be merged when you make your changes in your fork and open the PR.
Please add refer this issue to your PR.

Thanks. I'll be working on this PR soon.


Try to fix issue where columns duplicate

This will fix the issue where we sometimes get both defined and generated columns.
Fixes issue where:
Steps:

open demo app
go to columns demo
open more rows

Expected outcome:
Should not have generated and defined columns (this fix will make it behave that way)
Actual outcome (before this fix):
Both generated and defined columns shown

I moved some functionality to own method, to help with debugging. Hopefully this is ok.


Navbar: break at correct viewport width and give option to be collapsed at no or all breakpoints

Fixes #21691, fixes #21706
Currently the navbar-toggleable-* breaks at viewport size of the next breakpoints (i.e navbar-toggleable-md breaks at 992px instead of 768px).
This PR fix the navbar-toggleable-* generation to break at the corresponding breakpoint.
In addition, it generate navbar-toggleable that would prevent the navbar to collapse at all viewport size and mention it in the docs.
Finally it mentions in the docs that a navbar without navbar-toggleable-* will make it always collapsed.
It might be useful in order to created always/never collapsed navbar (as requested in #21706)

This doesn't make any sense to me. If this PR makes the toggleable classes collapse at the specified breakpoint, navbar-toggleable-xs should always collapse- which is also the default if no class is set? And why should a navbar-toggleable class make it never toggleable?

The naming of "toggleable" might be a bit confusing.
It has to be understood this way:

The navbar is by default toggled (which mean collapsed and visible only by opening the menu)
The classes navbar-toggleable-* determine at which breakpoint the navbar becomes expanded (which means toggle button invisible and nav-item visible)
The navbar becomes expanded when the viewport expand to a with superior to the breakpoint defined by the class ( navbar-toggleable-md means collapsed below "md" and expanded above)

The "toggleable" in navbar-toggleable-md means as "stop appearing toggleable above breakpoint md".
Therefore navbar-toggleable means "do not appear toggleable ever".
And no navbar-toggleable-* means "always appear toggleable".
It's counter intuitive because everything responsive class in Bootstrap usually means "Do what the class says above the breakpoint" and in the case of the navbar it means "Stop doing what the class says above the breakpoint".
I think it would be a lot clearer if these classes were renamed navbar-expand-* instead. Or navbar-visible-* maybe? Or even navbar-untoggleable-*...?
@mdo any thoughts on this ?

I agree that navbar-expand-* would be a better naming convention, but I also think the logic should be reversed (unless I'm misunderstanding how it now works). No class means it's always collapsed (how it currently is), and navbar-expand-xs would make it always expanded/uncollapsed/not toggleable, navbar-expand-sm would be collapsed on xs, but expanded on sm and up, and so on. This would keep it cognitively harmonized with the grid classes, where col-md-6 makes the element 50% width on medium screens and higher.

The fact that the navbar is by default collapsed (i.e no navbar-toggleable-* class means always collapsed) is by design. If I remember well it was the opposite on Bootstrap v3.
I'm pretty sure I read in a PR or comment the reason of this choice but I couldn't remember. Maybe @mdo can shed some light on this.

Phew, working through all these navbar issues. I think i'm onto something. Using this PR as a base, I've tweaked how the toggler works, improved the container behavior, etc. How do the navbars in this JS Bin behave? https://jsbin.com/zixoxah/edit?output

The problem solved by this PR is also solved in the JSBin. Everything looks good to me !
One remark though, that is out of the scope of this PR (and maybe out of the scope of the component): The first navbar wraps weirdly on viewport smaller than 700px.
The search button wraps under the search input while it might be more logical to keep them next to each other. Also the carret of the dropdown wraps under it.

Maybe navbar-collapse should be flex-wrap: wrap and navbar-nav and form-inline should be flex-wrap: nowrap. Or at least use the flex-wrap utility in a doc sample.

Oh yeah, that's just to demo the different navbar sizes—sm, md, and lg respectively for those first three. The broken display is definitely intentional.

Ok, so works great then !
What's your though on the naming convention ? see comment
I also have similar questioning in #21720.

Working on that shortly. Consolidating all these PRs into one and trying to include as many relevant changes from folks as I can to keep the attribution. It's been a lot to track. 😅

Working on that shortly. Consolidating all these PRs into one and trying to include as many relevant changes from folks as I can to keep the attribution. It's been a lot to track. 😅

As far as I'm concern the attribution doesn't matter much to me, if that can make your life easier in the merge/consolidation process.

Boom, peep #22230.

I tried the JSBin and there doesn't seem to be an option to never collapse. I tried navbar-toggleable-xs and it acts the same as navbar-toggleable-sm.

@spongessuck I've updated the example to include a never collapse option: https://jsbin.com/zixoxah/edit?html,output. It requires .navbar-toggleable. This is supported and documented in the changes from #22230.

I argued that requiring a class called navbar-toggleable to make it never toggleable makes no semantic sense and I still feel that way.

But thanks for the clarification.

@spongessuck Ah, yeah, that's given the class name itself though, right? Not the specific need for a class that says "behave this way"?

Yes, exactly.
navbar-toggleable, to me, says 'somehow, some way, it's toggleable' when in reality, it behaves exactly opposite to that.
Even navbar-toggleable-xs, if you follow the convention of the others, would mean 'the navbar expands at the xs breakpoint,' meaning it never collapses. It's still weird, but the suffix gives an important clue as to what the class does.


bug fix test case failed with fuzzy fold constatnt to false

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Updated install.sh

Install Script update
This PR updates the tools/install.sh script to include the latest version of Ubuntu 17.04. This will correct issue #206
Testing

[ ] sudo tool/install.sh successfully installs King Phisher on Ubuntu 17.04

@wolfthefallen closing this out since it's a one line change and should actually be targeting the master branch due to being a bug. Additionally, master should be bumped to 1.7.2-beta which I'll take care of at the same time then cherrypick this bug fix back into dev.


nostr One tap zap via Phoenix Wallet

user story
As a Phoenix Wallet user who uses nostr apps, I would like to be able to set up my Phoenix Wallet with my nostr app(s), so that I can one tap zap others.
acceptance criteria

There is a method to set up one tap zaps using Phoenix Wallet

implementation details
https://github.com/nostr-protocol/nips/pull/224
nwc.dev
https://docs.nwc.dev/
https://docs.nwc.dev/bitcoin-lightning-wallets/getting-started
https://discord.nwc.dev/
benefits to Phoenix Wallet user
No need to leave nostr app to use phoenix wallet.
benefits to Phoenix

Increase Phoenix Wallet usage; increase Phoenix Wallet revenue
Stress test increase of smaller, frequent payments of Phoenix LN channel management

Amethyst, Damus, Nostrudel, Primal, Snort, and dozens others.

I'd love to zap with my Phoenix wallet in my favourite Nostr clients.

It's not only for one-tap-zapping, but many apps have started implementing NWC. I'd like to use them with my Phoenix, +1

Thanks for the links to the doc, it's very helpful. Seamless integration with nostr looks good but it is not on top of our priority list for now. We'll try to find time to work on that after bolt12 integration (so maybe around June or July if things go well).


update pics in create-deployment

fixed #2978, except for the description of secret

See preview: https://deploy-preview-4576--daocloud-docs.netlify.app/kpanda/user-guide/workloads/create-deployment#_4


code

I admire your work in this paper, and I was wondering if you could provide me with your code. Thanks

Thank you for your appreciation of my work on this paper.  I am unable to provide code though due to proprietary limitations.


chore(norelease): add terraform validate action

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


Move "global" tests from ./tests to the correct crates

There are a few tests in the root directory ./tests dir. These should be moved to the correct crate found in ./crates.

Hello! I'm new to all of this and looking for a contribution I may be able to make to this project, for an assignment in my class I'm taking on FOSS. I was interested in taking this on, but I am a bit unclear on it. I am unsure specifically which files need to get moved out of the tests folder, and where they should be put in the crates folder. I've also put this message on the Zulip.

Completed in #457


Ptarafdar branch

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] New algorithm
[ ] Optimization in previous algorithms
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Other, please describe:

Briefly describe the changes in this PR

Other information:

Hi @ptarafdar001,
You have to make commit on the branch of pull request #404, so this pull request will be closed.


Access burger menu context from ember route?

I have a use case where I want to conditionally trigger opening and closing the menu during route transitions.  Additionally, it would be nice to be able to send actions from components in nested routes up to the application to trigger opening and closing the burger menu.
From what I can tell, this seems like it is out of the scope of this add-on.  Is this a correct assumption?

@dbollinger I would create a burger-menu service that has an open property. Once created, you can pass it to the component like so {{burger-menu open=burgerMenuService.open}}.
Now you can inject your service anywhere in your app and toggle the open state of the menu.

That makes perfect sense.  Thank you!
Did not think to pass the property into the component like that.

No problem at all 😄


Color Map for Depth-Anything V2

The color map used in Depth-Anything v2 is significantly different from the one in v1 (COLORMAP_INFERNO). In my opinion, the v2 color map appears more vivid and colorful, providing better contrast. Could you specify which color map you have used for v2?

I found the code from here
cmap = matplotlib.colormaps.get_cmap('Spectral_r')


Files imported as custom resource types are not considered as resources

First of all sorry if this issue title is unclear. I can't find a better way to describe this in a quick way.
Godot version: 832e2bf
OS/device including version: Win10 x64
Issue description:
Here are possibly related issues I've found: #17395, #6763, #6067
I have this pretty simple plug-in defining a custom resource type and a resource importer.
tool
extends EditorPlugin

var import_plugin

func _enter_tree():
	add_custom_type("InkStory", "Resource", preload("ink_story.gd"), preload("icon.png"))
	import_plugin = preload("import_plugin.gd").new()
	add_import_plugin(import_plugin)

func _exit_tree():
	remove_import_plugin(import_plugin)
	import_plugin = null
	remove_custom_type("InkResource")

The import plugin is setting the resource_type like so.
tool
extends EditorImportPlugin

[...]

func get_resource_type():
	return "InkStory"

[...]

So far, everything's fine.
The import plug-in works like a charm:

And the custom resource type is shown in the list of exported properties (I used export (Resource) var Story):

However, even once imported, the icon aside the file here does not update (it's updating if the resource_type in the import plug-in is set to a built-in one):

More importantly, it's impossible to set this file/resource to the previously mentioned exported property (whether it is by drag'n'dropping it or using the Load button).

Bests ❤

Hello from the future! Dunno if you're past this, but I'm running into something similar now. If you change the type returned from the EditorImportPlugin to "Resource", it lets you use either Load or drag'n'drop to associate a file to a resource slot, as you'd expect. I'm not sure what functionality you might lose by doing that, but at least so far it doesn't seem to hurt anything.
That might be all it takes, though I hit another snag after getting past that - the ResourceSaver doesn't seem to be serializing my resource correctly. I'm using C#, and it's possible it's a C#-specific issue and may not affect you. If it does, you can work around it by skipping the ResourceSaver and directly writing the tres file with the information you need to the file system (I used the inspector to generate one and then used it as a template.) I opened a separate ticket about that issue here: https://github.com/godotengine/godot/issues/38191

The first arguments passed on add_custom_type and remove_custom_type are pretty different ("InkStory" & "InkResource"), is that a typo?

is that a typo?

Yes, it is.

However, even once imported, the icon aside the file here does not update (it's updating if the resource_type in the import plug-in is set to a built-in one)

I think that's https://github.com/godotengine/godot/issues/32706
Is this stills relevant @paulloz  ? I can use imported files as resources in exported resource variables

@AnidemDex Will check as soon as I can.

@paulloz this is the reproduction project https://github.com/AnidemDex/Godot-CustomResource

So @AnidemDex, nothing changed AFAIK. Your example works because you are importing things as a Resource, not as an actual custom type. As soon as you'll change the return of get_resource_type from Resource to your custom type extending Resource you'll see the same behaviour as described in the original post.

Maybe is related to this? https://github.com/godotengine/godot-proposals/issues/18#issuecomment-988053877
ClassDB can't found that type in native classes, so is not recognized as resource or that specific resource type

Duplicate of https://github.com/godotengine/godot/issues/32706.


Warning: "nodeModulesDir": true deprecated in Deno 2.0 - Fresh project initialization

When initializing a new Fresh project using deno run -A -r https://fresh.deno.dev myapp --force --tailwind --vscode --docker with Deno 2.0.1, the following warning appears twice:
Warning "nodeModulesDir": true is deprecated in Deno 2.0. Use "nodeModulesDir": "auto" instead
    at file:///myapp/deno.json

This warning occurs once immediately after project initialization and a second time when starting the development server with deno task start.
Steps to reproduce

Create a new Fresh project using the following command (within a Docker container using denoland/deno:2.0.1):

deno run -A -r https://fresh.deno.dev myapp --force --tailwind --vscode --docker

Observe the warning.

Navigate to the project directory: cd myapp

Start the development server: deno task start

Observe the warning again.

Expected behavior
The Fresh project initialization should either:

Automatically set "nodeModulesDir": "auto" in the generated deno.json file, preventing the warning.

https://github.com/denoland/fresh/blob/d9764e20055c2a972074c86907d8cc674b27dabc/init.ts#L635-L642
Environment

Deno version: 2.0.1
Fresh version: 1.7.3 (as indicated by the downloaded dependencies)
OS: Linux (inside Docker container denoland/deno:2.0.1)

Additional context
The test.sh script used to reproduce the issue is attached below:
#!/bin/bash
docker run --rm -i denoland/deno:2.0.1 sh <<EOF
date
env
deno run -A -r https://fresh.deno.dev myapp --force --tailwind --vscode --docker
cd myapp
deno task start
EOF

The full output of the script showing the warnings.
Fri Oct 18 00:46:39 UTC 2024
HOSTNAME=1aad4b2db1c5
HOME=/root
DENO_INSTALL_ROOT=/usr/local
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
DENO_DIR=/deno-dir/
PWD=/
DENO_VERSION=2.0.1
Download https://fresh.deno.dev/
Download<EMAIL_ADDRESS>Download<EMAIL_ADDRESS>Download<EMAIL_ADDRESS>Download<EMAIL_ADDRESS>Download<EMAIL_ADDRESS>Download<EMAIL_ADDRESS>
  ...

Download<EMAIL_ADDRESS>Download<EMAIL_ADDRESS>
 🍋 Fresh: The next-gen web framework.

Let's set up your new Fresh project.

The manifest has been generated for 5 routes and 1 islands.

Project initialized!

Enter your project directory using cd myapp.
Run deno task start to start the project. CTRL-C to stop.

Stuck? Join our Discord https://discord.gg/deno

Happy hacking! 🦕
Warning `"nodeModulesDir": true` is deprecated in Deno 2.0. Use `"nodeModulesDir": "auto"` instead
    at file:///myapp/deno.json
Task start deno run -A --watch=static/,routes/ dev.ts
Watcher Process started.
Warning `"nodeModulesDir": true` is deprecated in Deno 2.0. Use `"nodeModulesDir": "auto"` instead
    at file:///myapp/deno.json
Download https://registry.npmjs.org/tailwindcss
Download https://registry.npmjs.org/@alloc/quick-lru

  ...

Download https://esm.sh/v135/<EMAIL_ADDRESS>
 🍋 Fresh ready
    Local: http://localhost:8000/

This issue highlights a minor inconsistency between the generated deno.json and Deno's current recommendations.  Addressing this will improve the user experience by removing unnecessary warnings and ensuring generated projects are up-to-date with best practices.

No such warning in deno 2.0.2, but I got an error on Deno  Deploy :"nodeModulesDir should be a boolean"


Update instructor-led-training-teams-landing-page.yml

Learn Build status updates of commit 58e9ab1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Teams/instructor-led-training-teams-landing-page.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Overlapping funcs in 4.0.1 don't work

"@XeroOl my code errors any time there are overlapping func easing calls, where before it would just disregard the first ease and start doing the next one"

This was a mistake I made in the code refactor. I've fixed it for 4.0.2 now


bug: collectives not showing in supercollective

Reads 4 collectives, only shows 2: opencollective.com/europe

Collective opencollective.com/kea is hosted by it, tagged but it's not showing up

added a parent collectiveID it increased the amount to 5 but still not showing up

also see: opencollective.com/uk

Might be related to this, when user created a new collective with the link opencollective.com/gorge-genie/apply the collective was created with no tiers and it had no host.

That's because since we order them by balance, we only show the ones that have at least one transaction. We should fix that but at least now you know why it happens.


Chain Canonicity functionality does not respect canonical_threshold CLI Argument

when running the mina-indexer, one can pass in a flag canonical_threshold that should determine how many blocks after (confirmations) from the current Best Tip to consider as a Canonical block. Currently, the indexer does not respect this flag, and simply uses a constant CANONICAL_UPDATE_THRESHOLD defined in src/lib.rs. Fix will include removing this constant from all code excepting as a default in the clap command line parser.

Asana Tasks Referenced

https://app.asana.com/0/1203669416123378/1205188242779822/f

This isn't a bug. The canonical_update_threshold pertains to how often the canonical_tip is updated in the witness tree, not how many confirmations determine a block's canonicity. A cli arg could also be added for this, but canonical_update_threshold is not it.

I see, you're asking for another cli arg. On it!

Requires tests that pass in CI to show completion. Re-opening.


Fix for the c15 ascend exploit

Ascending in c15 could let a player play the challenge with less than the specified corruption if corruption/completes were high enough to avoid dumping them out of the challenge, for a highly inflated expo. This change ensures the c15 all-11 corruption array is kept intact. As a side effect it seems to even prevent the player from accidentally completing c15 with an ascend.

Not reviewed yet? In that case I might as well add a fix for the "go into debt" Abyssals in Platonic upgrades. Begone!

Conflicts with new Plat upgrade cost (which fixed that issue anywa), so nuking this PR, will submit a new one for the c15 fix


MAHOUT-1737: implement AewUnaryFunc on H2O

This closes apache/mahout#142
Signed-off-by: Anand Avati<EMAIL_ADDRESS>

looks good to me.


poor performance of sorting by Highest Severity column in HTML report

Describe the bug
My HTML report is 35,619,264 bytes in size. I can click on Dependency column and it sorts nearly imediately. But when I click the Highest Severity the page stops responding.
Version of dependency-check used
The problem occurs using version 6.2.2 of the Maven plugin HTML report.
Log file
Scan Information (show less):

    dependency-check version: 6.2.2
    Report Generated On: Wed, 16 Jun 2021 15:20:19 +0200
    Dependencies Scanned: 6802 (6468 unique)
    Vulnerable Dependencies: 185
    Vulnerabilities Found: 841
    Vulnerabilities Suppressed: 43
    NVD CVE Checked: 2021-06-16T15:17:13
    NVD CVE Modified: 2021-06-16T14:00:53
    VersionCheckOn: 2021-06-16T15:17:13

To Reproduce
Steps to reproduce the behavior:

Open sufficiently large generated HTML report.
Click on Highest Severity column
...
See browser pop up

Expected behavior
Sorting by any column should be (nearly) instantaneous.

sorting is done using the "jQuery Stupid Table Plugin by Joseph McCullough" see: https://github.com/jeremylong/DependencyCheck/blob/3e352c4fbf7aa5c2ffd9fda43f7461a1188732cd/core/src/main/resources/templates/htmlReport.vsl#L35
you are welcome to propose a better alternative

Well, it is capable of sorting by the Dependency column fast but not by the Highest Severity. I am suggesting there is maybe something on our part that is wrong with how we provide the sortable data set to it?

I see one potential issue. The template declares the Highest Severity field as sorted by int value: Highest Severity
But the rendered report contains floating point in the attribute value: CRITICAL
But the Stupid-Table-Plugin does support float.

thanks for the analysis and PR!


0.99.2 not tagged as latest docker image

Home Assistant release with the issue:

Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Component/platform:

Description of problem:
0.99.1 is still tagged as "latest", "stable", "rc" and "beta" on docker hub even thou 0.99.2 is released. See https://hub.docker.com/r/homeassistant/home-assistant/tags
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

Is this not an automated process?

I don't know, but if it is there's a bug in it. If it's manual it's just missed for this release.

I don't know, but if it is there's a bug in it. If it's manual it's just missed for this release.

I should have said: "should this not be an automated process". It's not the first time this happend :)

It is automated now, however, 99.1 was tagged without the frontend fixes, so 99.2 was released immediately after it. The build for 99.2 was finished quicker (for some reason) hence 99.1 became the latest.
This is a bit of an edge case, unfortunately

Fixed with the release of 99.3.


GroupMe messages out of order

For whatever reason GroupMe puts CalmanBot's response after the requesting message sometimes. I'm guessing it's a timing issue. Add a ~500ms sleep before posting and it should fix it.

Fixed in v1.2.4


Make kubeconfig_server_address configurable

Closes #1390

@kranich Thanks for this, appreciate it! Did you test it and can confirm that it works properly?

Yes, I have tested it successfully.


Fixed #33733 -- Used functools.wraps to fix inspect.signature output.

@felixxm After digging through wraps internals I found that we just need the below change to fix the signature issue:
manager_method.__name__ = method.__name__  # existing
manager_method.__doc__ = method.__doc__  # existing
manager_method.__wrapped__ = method  # addition

wraps assigns some of the original func's attributes to the decorated one, __name__ and __doc__ being two of those.
It also assigns the original function to the wrapped function's __wrapped__ attribute.
inspect.signature checks for __wrapped__ attribute in a function, and if present uses that to determine the signature instead of the function passed to inspect.signature.
wraps does lot more things than we need for fixing the signature issue. Doing the minimal change of setting __wrapped__ attribute is a better option.
If we go this route, I will add a test case that ensures docstring and signatures are matching. I will skip checking for names since that's handled implicitly in the existing test case: https://github.com/django/django/blob/90aabd730a2a434c227faf8a927b0e2ccd67e291/tests/basic/tests.py#L725
Let me know your thoughts. If you agree, I will amend my commit.

inspect.signature checks for __wrapped__ attribute in a function, and if present uses that to determine the signature instead of the function passed to inspect.signature.
wraps does lot more things than we need for fixing the signature issue. Doing the minimal change of setting __wrapped__ attribute is a better option.

I've not checked any of this, but hypothetically how do type annotations play with inspect.signature with & without using wraps? Does avoiding using wraps leave us open to creeping of more __x__ additions to cover additional use-cases that wraps would handle for us?
(And if we did still choose to introduce wraps here, we ought to make sure that we're in-line with the recently merged #15723 if we're not already (mentioning only because that was very recent))

Since other attributes are not checked, I was concerned about any unexpected effects of adding __module__, __qualname__ and __dict__ attributes. I wanted to take the least risky route of just adding __wrapped__ that would fix the issue.

@wraps was created exactly for our use case, I would not hesitate to use it.

@kshivakumar Thanks :+1: Welcome aboard :boat:


Altair documentation

I am wondering if there is documentation of all of the features of Altair.  I am looking specifically now for the options that exist for the "mark_<  >" method of the Chart object.  The Aggregate Operations have a listing (I am assuming it is a complete listing) of all the choices.  I don't see that for the mark_ method.  Since this is a statistical visualization API, I am wondering about boxplots, since these are sometimes useful during exploratory data analysis.
Thank you.

OK, I answered part of the question myself, I found the mark methods farther down the Introduction notebook.

Hi @ERDataDoc – The best way to find the options available to the function is to use the documentation string.  For example, in IPython/Jupyter Notebook you can type
Chart.mark_<TAB>

to see all the available mark methods, and e.g.
Chart.mark_point?

to see the documentation for the method, which includes a description of all the available options.
Additionally, since Altair is built around Vega-Lite, the Vega-Lite documentation will be helpful in answering questions about various available properties. Here's the Vega-Lite mark configuration docs. Scroll down to "Mark Configuration" there.
Regarding Box Plots, we don't have an easy way to make those – yet. But the Vega-Lite project is actively discussing this, and as these kinds of features are added to it we will make them accessible from Altair as well.

Thank you for that update.  I went back and was successful at using the tab completion and help functions.  Thanks for your help.  Looking forward to getting to know Altair better.


Versioning - version injection enhancement

From a Twitter request from @GordonBeeming

It would be cool for Manifest Versioning Build Tasks in the @VSTS marketplace to be able to take in a variable and just set that. I have some of my own logic that does to get version numbers and those extensions are awesome

@Gordon-Beeming it took a while but the feature has just been published in 2.3.x


Every request errors after some time

Hi,
a continuous running application with some requests per second becomes unavailable after a few days of running without any problems.
Every request to every path fails because of an internal error, maybe related to some deque from metrics.
The following stacktrace ist inverted by journalctl and some long lines are cut. But I guess for a first view it should be enough.
I will test the application with disabled metrics.
Thanks for this great package!

Jun 06 09:32:59  julia[3904]: │    Stacktrace:
Jun 06 09:32:59  julia[3904]: │    BoundsError
Jun 06 09:32:59  julia[3904]: │   exception =

Hi @kawild,
Thanks for the logs, I'm sorry you're running into this issue with metrics. You're right on the money, this issue appears to be coming from the metrics collection middleware function.
I will admit this is super weird, I chose a CircularDeque data structure specifically to avoid using too much memory and avoid index out of bounds issues. Is there any more information? You cut off the logs right at the exception which will have the info I need to debug this better. Depending on that log output, we may have to raise this issue with the DataStrutures.jl package if it's something I can't fix within Oxygen.

Thanks for your response, but I´m sorry, it seems I don´t have the complete logs anymore.
Also this error is hard to reproduce, because it occured after nearly 2 weeks of runtime and only within an productive environment.
Please let me know, If I can help any further!

No worries, do you have a rough number of requests that were sent? Are the request bodies large? I can setup a server and mock a bunch of requests to see how well it holds up under high load.
If you're not sure how much load your app is getting, I'll try to mock a couple million requests to see how the server holds up over time with metrics enabled.

The app has a request rate of about 10/sec.
The request bodies are empty, because it is also called from Grafana, and there I can not interpolate something into the body, so everything is handled via request parameters.
So the url can be quite long - about 2000 signs and even longer.

I'm going to close this issue for now, feel free to reopen this issue if you run into it again.

Apologies for commenting on a closed issue, but I've ran into this problem as well. I'm running Oxygen v1.5.15 on a webserver with an average request rate of 20/s.  As a quick band-aide patch, I'd recommend turning off server metrics off to bypass this part of the code for your application. set metrics=false as part of your serve() or serveparallel() call
I'll need to release a patch to handle cases where this can fail and also raise an issue with the datastructures package.


Make Group Add and Remove Commands

[x]  Add group add and group remove commands

This will be helpful to resolve the modern-unix installation group:

https://github.com/candrewlee14/webman-pkgs/issues/1
https://github.com/ibraheemdev/modern-unix/issues/99
https://github.com/ibraheemdev/modern-unix/issues/5
https://github.com/ibraheemdev/modern-unix/issues/85

Got it implemented!
webman group add modern-unix and webman group remove modern-unix are working!
I just need to add the necessary packages.


Heirline crashes when there isn't enough horizontal space for the bar

Overview
Hi there! Love Heirline–it's probably the best Nvim statusline I've used.
I'm having an odd error that's causing some problems in my normal workflow. I use AstroNvim which, as of the 2.0 release, comes with Heirline preinstalled and preconfigured (configuration below). Recently, I started getting seemingly random crashes and stack overflows (screenshot also below) from Heirline, and when I dug into it today, I realized that Heirline only encounters the error when there is not enough horizontal space to fit all of the statusline information.
I went through the stack trace and realized that the error originates from the expand_or_contract_flexible_components function in the `utils.lua file, which seems to be in line with my observations about window width. From there, though, I'm not well-versed enough in Lua to really have much more of an insight into what could be happening.
Hopefully, this can point someone in the right direction to opening a PR fix! I'm happy to help however I can, so don't hold back with questions or other things to try!
Steps to Reproduce

Expand terminal emulator to the full width of screen (obviously, results here will vary based on screen size and resolution)
Open a file in Nvim and see the statusbar work
Shrink terminal emulator window to the point where parts of the statusbar have collapsed
Perform an action like creating a new split to the right (multiple actions can do this, but this is the simplest for example's sake)
See the error appear
Heirline is replaced with the default Nvim statusline

Details
Neovim Version: 0.8 - Release
Last Updated:

AstroNvim - today (10/21/22)
Heirline - today (10/21/22)

Heirline Configuration

heirline = function(config)
      -- statusline
      config[1] = {
        hl = { fg = "fg", bg = "bg" },
        astronvim.status.component.mode(),
        astronvim.status.component.git_branch(),
        astronvim.status.component.file_info(
          astronvim.is_available "bufferline.nvim" and { filetype = {}, filename = false, file_modified = false } or nil
        ),
        astronvim.status.component.git_diff(),
        astronvim.status.component.diagnostics(),
        astronvim.status.component.fill(),
        astronvim.status.component.macro_recording(),
        astronvim.status.component.fill(),
        astronvim.status.component.lsp(),
        astronvim.status.component.treesitter(),
        astronvim.status.component.nav(),
        astronvim.status.component.mode { surround = { separator = "right" } },
      }

      -- winbar
      config[2] = {
        fallthrough = false,
        -- if the current buffer matches the following buftype or filetype, disable the winbar
        {
          condition = function()
            return astronvim.status.condition.buffer_matches {
              buftype = { "terminal", "prompt", "nofile", "help", "quickfix" },
              filetype = { "NvimTree", "neo-tree", "dashboard", "Outline", "aerial" },
            }
          end,
          init = function() vim.opt_local.winbar = nil end,
        },
        -- if the window is currently active, show the breadcrumbs
        {
          condition = astronvim.status.condition.is_active,
          astronvim.status.component.breadcrumbs { hl = { fg = "winbar_fg", bg = "winbar_bg" } },
        },
        -- if the window is not currently active, show the file information
        {
          astronvim.status.component.file_info {
            file_icon = { highlight = false },
            hl = { fg = "winbarnc_fg", bg = "winbarnc_bg" },
            surround = false,
          },
        },
      }

      -- return the final configuration table
      return config
    end,

Screenshots:

Heirline (for reference)

Stack Overflow Error

Dear @alexandersix, thanks for your efforts!
Unfortunately I am unable to reproduce the issue with my and other testing configurations.
This is likely fault of one flexible component, and possibly one that generates children each time it is evaluated (possibly a navigation component), which then creates an infinite call stack every time it's evaluated to check its lenght.
I think you should verify that this is the case, then I'll  have a look at AstroNvim implementation of components

Hey @rebelot, thanks for taking a look! Sorry that you weren't able to reproduce–definitely sounds like an issue with a specific AstroNvim flexible component.
I'll take a look and figure out which component specifically is causing the issue. Thanks for the insight about a potential issue being a component that generates children on each evaluation; I'll start my search there!
I'll report back when I have more information. It's it's an AstroNvim-specific component, I'll open an issue on that repository as well.

Hi,
I also ran it this problem with Astrovim. For my situation, it was much easier to reproduce than @alexandersix 's . I just had to spin up more than 7-8 vsplits, and heirline will crash.
I disabled and tested the each AstroVim component, and found the astronvim.status.component.lsp() to be the culprit. When it is the only enabled, creating a lot of vsplit will cause that heirline to crash.

@rebelot Just a heads up, the component that was originally reported is just using vim.fn.fnamemodify(vim.api.nvim_bug_get_name(0), "%p") as the function provider. This component doesn't use the flexible component stuff at all directly so I'm confused why Heirline's utils are jumping in here. Our (AstroNvim's) status API doesn't actually use heirline.utils at all so I figured it would separate us from that code. It seems to pop up when the full path gets very very long and we aren't trimming it down. This might be what's causing the stack overflow? Could you shine some insight why the expand_or_contract_flexible_component stuff is kicking in when we aren't using it.

@mehalter
Because of this in the main eval function:
https://github.com/rebelot/heirline.nvim/blob/d72ec3d3ca8406dffd7da72ae6d355e94d8c59fe/lua/heirline/init.lua#L75
the utility is always called, but should return immediately if there's no flexible components:
https://github.com/rebelot/heirline.nvim/blob/d72ec3d3ca8406dffd7da72ae6d355e94d8c59fe/lua/heirline/utils.lua#L208-L210
But from the stack trace, it seems there are indeed flexible components to evaluate (eval is being called from there, this is needed to check the length of the component)

I really wouldn't know how to reproduce this and I have a pretty complex config..

could you please try b6044c8d650904f205999e6eea0dae81b38b713f? I still can't really figure out why that's happening but following the stack trace that's where __index gets called seemingly endlessly.

@alexandersix @Uduchi2nd could you guys also test this latest commit and see if it resolves your stack overflows? :)

@mehalter I'll give it a go as soon as possible and report back.
Thank you and @rebelot for being so quick about working on this. Massive props to the both of you 🙌🏻

I'm encountering the same issue. In my setup, it happens on a smaller monitor with a lower resolution (1366 x 7689. Then I have a v-split. Save the session, quit then re-open the session.
Note that the error won't show the first time you do a v-split. It errors out when it starts to load on a vsplit with minimal on low resolution screen.

I still have this same issue when opening even a single vertical split on my 14" laptop. I am on AstroNvim too.

Can you please retry with latest commit?
I am very sorry but being unable to reproduce the issues I am going a little bit blind here. I would be super helpful if some of you could pinpoint the component that's causing the error so I can take a look at the implementation.
@mehalter does AstroNvim make use of flexible components anywhere? I am very surprised to see the error spawns from a function that should run to that point only if flexible components are present
could some of you try this command and report the output?
:lua for _, c in ipairs(require'heirline'.statusline._flexible_components) do vim.pretty_print(c.id) end

Retry w/ Latest Commit
Hey @rebelot, just tried with your latest commit (9b814e6) and I'm still getting the same error.
Pinpointing the Erroring Component
Also, I'm so sorry, I misread an earlier comment and thought we had narrowed down which component was causing the issues!
I took some time this morning to play around with the default Heirline config in AstroNvim by adding the snippet found  here (second image in this section) to my user configuration file. Turns out, at least from what I can tell, the lsp() component is causing the issue, but only when it is paired with another component on the bar.
So, for example, with a configuration that looks like this:
["heirline"] = function(config)
    config[1] = {
        hl = { fg = "fg", bg = "bg" },
        astronvim.status.component.lsp(),
    }
end

Heirline works no matter the size of the window.
However, with a configuration that looks like this:
["heirline"] = function(config)
    config[1] = {
        hl = { fg = "fg", bg = "bg" },
        astronvim.status.component.lsp(),
        astronvim.status.component.treesitter(),
    }
end

Heirline will throw that error when the screen is too narrow to fit both components.
To reiterate, this issue with the lsp() component occurs with any of the other components, not just treesitter(), provided you can get the nvim window narrow enough.
Command Output
Also, I tried the command you put in your last comment and this was the result:
{ 1, 2, 1, 1, 1 }

could some of you try this command and report the output?

{ 6, 1, 1, 1, 1 }
{ 9, 2, 1, 1, 1 }

Also, things are breaking even with a single window (i.e. a single buffer/split).
E5108: Error executing lua ...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:369: stack overflow
stack traceback:
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:368: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:372: in function 'traverse'
	...k/packer/start/heirline.nvim/lua/heirline/statusline.lua:382: in function 'eval'
	...e/pack/packer/start/heirline.nvim/lua/heirline/utils.lua:229: in function 'expand_or_contract_flexible_components'
	...te/pack/packer/start/heirline.nvim/lua/heirline/init.lua:75: in function <...te/pack/packer/start/heirline.nvim/lua/heirline/init.lua:66>

I also get a (different?) error when, after opening an empty buffer, I open a lua file:  E5108: Error executing lua error in error handling

I also get a (different?) error when, after opening an empty buffer, I open a lua file: E5108: Error executing lua error in error handling and then the status line disappears.

@krishnakumarg1984 I've been noticing that I get this error when I open a window too quickly after launching Nvim. Possibly related, but I'd imagine that something involving the error handling hasn't loaded so instead of showing the full stack trace, this little error is shown. I don't have the Lua chops to prove that, but that's what I'd assume.

@rebelot we do make use of the flexibile components in the lsp component where we display the LSP client names and if it gets too long then it will shorten them.

@alexandersix Thank you again for your clarifications. I was confused by a comment stating the pinpointed component was different from what you originally reported.
I am looking at the layers cast by AstroNvim over heirline. I might just end up installing it to help with debugging. I am going to ask you one last curtesy, could you please use this config
["heirline"] = function(config)
    config[1] = {
        hl = { fg = "fg", bg = "bg" },
        astronvim.status.component.lsp(),
        astronvim.status.component.treesitter(),
    }
end

and report the output of the command
:lua =require'heirline'.statusline

I could finally find a way to reproduce. The bug is due to setting the update field directly to a flexible component. I still need to grasp why.
local crash = u.make_flexible_component(1, { provider = "craaaaaaaaaaaaaaaaaaash" }, { provider = "or not" })
crash.update = { "User", pattern = "DoCrash" }

require("heirline").setup(crash)
vim.cmd("wincmd 300v | doau User DoCrash")

This won't crash
local dontcrash = {
    update = { "User", pattern = "DoCrash" },
    u.make_flexible_component(1, { provider = "craaaaaaaaaaaaaaaaaaash" }, { provider = "or not" })
}
require("heirline").setup(crash)
vim.cmd("wincmd 300v | doau User DoCrash")

Once I understand why this is happening we'll be able to fix this

That's fantastic @rebelot! Glad we could finally reproduce it–makes me feel a little less crazy.
In case you still need it, here's the output from =require'heirline'.statusline. If there's any other way I can help, let me know!

Command Output

<1>{ <2>{ {
      _tree = <3>{ "%#Stl2c323c_2c323c__#  %*" },
      fallthrough = true,
      hl = <function 1>,
      id = { 1, 1 },
      merged_hl = {
        bg = "bg",
        fg = "lsp_bg"
      },
      provider = "  ",
      <metatable> = <table 2>
    }, <4>{ <5>{ <6>{ <7>{ {
              _tree = <8>{ "%#Stlcdd6f4_2c323c__#%*" },
              fallthrough = true,
              id = { 1, 2, 1, 1, 1, 1 },
              merged_hl = {
                bg = "lsp_bg",
                fg = "lsp_fg"
              },
              provider = <function 2>,
              <metatable> = <table 7>
            }, {
              fallthrough = true,
              id = { 1, 2, 1, 1, 1, 2 },
              provider = "",
              <metatable> = <table 7>
            },
            __index = <function 3>,
            _priority = 1,
            _tree = <9>{ <table 8> },
            _win_child_index = { 1 },
            fallthrough = true,
            id = { 1, 2, 1, 1, 1 },
            init = <function 4>,
            merged_hl = {
              bg = "lsp_bg",
              fg = "lsp_fg"
            },
            pick_child = { 1 },
            restrict = {
              _win_child_index = true
            },
            <metatable> = <table 6>
         }, <10>{ {
              _tree = { "%#Stlcdd6f4_2c323c__#  sumneko_lua, misspell, stylua, luacheck%*" },
              fallthrough = true,
              id = { 1, 2, 1, 1, 2, 1 },
              merged_hl = {
                bg = "lsp_bg",
                fg = "lsp_fg"
              },
              provider = <function 5>,
              <metatable> = <table 10>
            }, {
              fallthrough = true,
              id = { 1, 2, 1, 1, 2, 2 },
              provider = "  LSP",
              <metatable> = <table 10>
            },
            __index = <function 6>,
            _au_id = 97,
            _priority = 2,
            _tree = <11>{ "%#Stlcdd6f4_2c323c__#  sumneko_lua, misspell, stylua, luacheck%*" },
            _win_cache = { "%#Stlcdd6f4_2c323c__#  sumneko_lua, misspell, stylua, luacheck%*" },
            _win_child_index = { 1 },
            fallthrough = true,
            id = { 1, 2, 1, 1, 2 },
            init = <function 7>,
            merged_hl = {
              bg = "lsp_bg",
              fg = "lsp_fg"
            },
            pick_child = { 1 },
            restrict = {
              _win_child_index = true
            },
            update = { "LspAttach", "LspDetach", "BufEnter" },
            <metatable> = <table 6>
          },
          __index = <function 8>,
          _tree = <12>{ <table 9>, <table 11> },
          fallthrough = true,
          id = { 1, 2, 1, 1 },
          merged_hl = {
            bg = "lsp_bg",
            fg = "lsp_fg"
          },
        <metatable> = <table 5>
        },
        __index = <function 9>,
        _tree = <13>{ "%@v:lua.heirline_lsp@", <table 12>, "%X" },
        fallthrough = true,
        hl = {
          fg = "lsp_fg"
        },
        id = { 1, 2, 1 },
        merged_hl = {
          bg = "lsp_bg",
          fg = "lsp_fg"
        },
        on_click = {
          callback = <function 10>,
          name = "heirline_lsp"
        },
        <metatable> = <table 4>
      },
      __index = <function 11>,
      _tree = <14>{ <table 13> },
      fallthrough = true,
      hl = <function 12>,
      id = { 1, 2 },
      merged_hl = {
        bg = "lsp_bg",
        fg = "fg"
      },
      <metatable> = <table 2>
    },
    __index = <function 13>,
    _tree = <15>{ <table 3>, <table 14> },
    condition = <function 14>,
    fallthrough = true,
    id = { 1 },
    merged_hl = {
      bg = "bg",
      fg = "fg"
    },
    <metatable> = <table 1>
  }, <16>{ {
      _tree = <17>{ "%#Stl2c323c_2c323c__#  %*" },
      fallthrough = true,
      hl = <function 15>,
     id = { 2, 1 },
      merged_hl = {
        bg = "bg",
        fg = "treesitter_bg"
      },
      provider = "  ",
      <metatable> = <table 16>
    }, <18>{ <19>{ {
          _tree = { "%#Stla6e3a1_2c323c__#綠TS%*" },
          fallthrough = true,
          id = { 2, 2, 1, 1 },
          merged_hl = {
            bg = "treesitter_bg",
            fg = "treesitter_fg"
          },
          provider = "綠TS",
          <metatable> = <table 19>
        },
        __index = <function 16>,
        _au_id = 87,
        _tree = <20>{ "%#Stla6e3a1_2c323c__#綠TS%*" },
        _win_cache = { "%#Stla6e3a1_2c323c__#綠TS%*" },
        fallthrough = true,
        hl = {
          fg = "treesitter_fg"
        },
        id = { 2, 2, 1 },
        init = <function 17>,
        merged_hl = {
          bg = "treesitter_bg",
          fg = "treesitter_fg"
        },
        once = true,
        update = { "OptionSet",
          pattern = "syntax"
        },
        <metatable> = <table 18>
      },
      __index = <function 18>,
      _tree = <21>{ <table 20> },
      fallthrough = true,
      hl = <function 19>,
      id = { 2, 2 },
      merged_hl = {
       bg = "treesitter_bg",
        fg = "fg"
      },
      <metatable> = <table 16>
    },
    __index = <function 20>,
    _tree = <22>{ <table 17>, <table 21> },
    condition = <function 21>,
    fallthrough = true,
    id = { 2 },
    merged_hl = {
      bg = "bg",
      fg = "fg"
    },
    <metatable> = <table 1>
  },
  __index = <function 22>,
  _buflist = {},
  _flexible_components = { <table 7> },
  _tree = { <table 15>, <table 22> },
  _updatable_components = {},
  fallthrough = true,
  hl = <23>{
    bg = "bg",
    fg = "fg"
  },
  id = {},
  merged_hl = <table 23>,
  winnr = 1,
  <metatable> = {
    __index = <function 23>,
    _eval = <function 24>,
    _freeze_cache = <function 25>,
    broadcast = <function 26>,
    clear_tree = <function 27>,
    eval = <function 28>,
    find = <function 29>,
    get = <function 30>,
    get_win_attr = <function 31>,
    is_empty = <function 32>,
    local_ = <function 33>,
    new = <function 34>,
    nonlocal = <function 35>,
    set_win_attr = <function 36>,
   traverse = <function 37>
  }
}

Wow thank you so so much for your help @rebelot !!! Let me know if there is anything you would like me to do to help with the investigation!

It should be fixed now.
@mehalter on a side note, consider the difference here
-- 1
local updatable_flex = utils.make_flexible_component(1, { ... }, { ... })
updatable_flex.update = { ... }

-- 2
local flex_updatable = utils.make_flexible_component(1, { ..., update = {...}}, { ..., update = {...}})

in the first case, the flexible component won't shrink nor expand until the update event is fired, and this is intended behaviour, in the second case, the flexible component will shrink or expand, but the displayed child will just use the cached value. I If I read correctly, you're implementing a version of the first approach, but I think the second approach is what you actually want with the LSP component.

@rebelot That seems to have done the trick! Thanks so much for doing all the hard work–I very much appreciate it! 🎉


feat: add possibility to refresh items manually

Pull Request Test Coverage Report for Build 834542654

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 93.705%

Totals

Change from base Build 816584020:
-0.05%

Covered Lines:
918

Relevant Lines:
958

💛  - Coveralls


Question: Can DataFusion handle larger than RAM datasets?

I browsed the readme and slides but failed to grok - can DataFusion handle larger than RAM datasets? In other words, if I register multiple parquet files, which size exceeds RAM, will they get all loaded into memory or will DataFusion carefully manage memory buffers to avoid out of memory exception?
As an extension of this question, I'd like to ask for pointers on how can one tune DataFusion resource usage if necessary ?

@voltcode  -- DataFusion is at its core an in memory processing system.
That being said, depending on what the plan is doing, simply reading from a large number of parquet files does not necessarily mean they will be decompressed all at once into memory.
DataFusion has several features that keep the memory usage down:

It will only read columns required for the query "projection pushdown"
It will attempt to prune row groups  (based on metadata) and skip them entirely if possible
It has a "streaming" model of computation and so will read the parquet files into memory in small batches.

Certain operations in DataFusion are likely to consume large amounts of memory, notable "Sort" and "Join" (as well as grouping where there are large numbers of distinct groups)

I am not sure there is any documentation written about tuning resource usage of DataFusion -- perhaps @andygrove would know if such documentation existed

Possibly related: https://github.com/apache/arrow-datafusion/issues/587https://github.com/apache/arrow-datafusion/issues/587

I think this question is answered so closing this ticket


Number of output channels is not the same with input

Thank you for your code. My input is [1,3,16,112,112] (C3D video action detection network), and the each video is [16,112,112]. But my output is [7,112,112]. I am not able to have attention map for each frame of video. Any idea where is my mistake?

I would start from feeding every 112x112 frame seperately into the network, and making sure the CAM makes sense.


VSCode bug: "window.titleBarStyle": "custom" cause sftp stop working.

With new VS feature "window.titleBarStyle": "custom" don't work Upload File function!
Error log:
[error] TypeError: Cannot read property 'substr' of undefined     at normalizeTriePath (C:\Users\CHROM\.vscode\extensions\liximomo.sftp-1.2.3\out\src\modules\config.js:99:32)
OS: Windows

Can you provide the full log with sftp.printDebugLog setting to true ?

@liximomo its too in Output: sftp ? If so then here:
[info] config at c:\Web\domains\sportbets {"protocol":"ftp","host":"185.***.***.**","port":21,"username":"******","password":"******","connectTimeout":10000,"agent":null,"privateKeyPath":null,"passphrase":null,"interactiveAuth":false,"sshConfigPath":"~/.ssh/config","secure":false,"passive":false,"remotePath":"/var/www/sport","uploadOnSave":false,"downloadOnOpen":false,"syncMode":"update","ignore":["**/.vscode/**","**/.git/**","**/.DS_Store",".vscode",".sass-cache","config.rb","*.sql",".git",".git*","/node_modules/","/node_modules","/node_modules/","*/node_modules/","*/node_modules"],"watcher":{"files":false,"autoUpload":false,"autoDelete":false},"concurrency":4,"context":"c:\\Web\\domains\\sport"}
[error] TypeError: Cannot read property 'toString' of undefined
    at args.map.arg (C:\Users\CHROM\.vscode\extensions\liximomo.sftp-1.2.3\out\src\ui\output.js:32:22)
    at Array.map (native)
    at Object.print (C:\Users\CHROM\.vscode\extensions\liximomo.sftp-1.2.3\out\src\ui\output.js:28:10)
    at VSCodeLogger.trace (C:\Users\CHROM\.vscode\extensions\liximomo.sftp-1.2.3\out\src\logger.js:10:20)
    at FileCommand.<anonymous> (C:\Users\CHROM\.vscode\extensions\liximomo.sftp-1.2.3\out\src\commands\FileCommand.js:35:30)
    at Generator.next (<anonymous>)
    at C:\Users\CHROM\.vscode\extensions\liximomo.sftp-1.2.3\out\src\commands\FileCommand.js:7:71
    at Promise (<anonymous>)
    at __awaiter (C:\Users\CHROM\.vscode\extensions\liximomo.sftp-1.2.3\out\src\commands\FileCommand.js:3:12)
    at FileCommand.handleFile (C:\Users\CHROM\.vscode\extensions\liximomo.sftp-1.2.3\out\src\commands\FileCommand.js:33:16)
    at pendingTasks.concat.map.target (C:\Users\CHROM\.vscode\extensions\liximomo.sftp-1.2.3\out\src\commands\FileCommand.js:54:72)
    at Array.map (native)
    at FileCommand.<anonymous> (C:\Users\CHROM\.vscode\extensions\liximomo.sftp-1.2.3\out\src\commands\FileCommand.js:54:53)
    at Generator.next (<anonymous>)
    at fulfilled (C:\Users\CHROM\.vscode\extensions\liximomo.sftp-1.2.3\out\src\commands\FileCommand.js:4:58)
    at <anonymous>

And this is end 🔚

What did you do?

@liximomo i update VS to 1.25, and enable new feature in settings: "window.titleBarStyle": "custom", after this open my project and wanted to upload file to FTP server...
This feature changes the top bar to non-standard, and with it all drop-down lists. I think it's because of non-standard lists 😡

So can you confirm that it can work without "window.titleBarStyle": "custom".

@liximomo yes, of course! It's just because of this

Unfortunately,  it's fine on my MacBook Pro.  I think it's more likely a bug of vscode. I will find the answer. Give me some time.

Okay, thanks. I think its Windows only problem...
If you have the opportunity, test it on Windows 💻

This bug is resolved in the latest version of vscode (1.26.0)

I can close it now.

I had the same problem and have solve it by writing the password in config file.


Multiple fixes for newer vim and trivy executables.

 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.

@bhundven - I can't approve this but hopefully @simar7 can

Any update on merging this? I just started using the plugin and these additions would be appreciated.


font-awesome-rails and jquery-awesome-cursor

This is a cross-project issue, so not sure it is the perfect place for this ticket, but I guess it's at least 50% ok... :)
I am trying to use jquery-awesome-cursor which, as the name suggests, provides a way to use Font Awesome as a cursor.
With font-awesome-rails, the icons are not loading. I have opened a detailed ticket over there, but the owner does not use rails, so can't help figuring out the problem.

Closing this out. Browsers can load fonts after DOMContentLoaded potentially causing a race condition with jquery-awesome-cursor. Either jquery-awesome-cursor should take this into consideration internally, or they should update their docs to only load the plugin after fonts are finished loading.


Completion of html tags

When the HTML tags is incomplete,  Mail and Calendar App cannot render the mail content.

@Ansen thanks for making this change. Can you please check?