2.8.0: what is this number?

updated add-on and now i have this number.
I don't understand what it refers to.
My "Icon badge" setting is disabled.

It shows number of detected feeds on active website, I'll be looking for alternative methods of announcing them, sorry for the confusion
You can now easily subscribe to found feeds using toolbar item context menu instead of messy PageAction and I'll be adding extended detection for pages that don't announce feed existence

yes, ok I understand.
but could we have an option to not show that number? 😊

sure, now I'm exploring other options to indicate that there is something interesting to do on that website


Incorrect Launch template ID refered when Launch template name is changed

Description
I am trying to use this module to create an ASG using an already existing launch template. As part of my requirement I want to be able to change the instance template of the ASG. I attempted it it using the below paramters.
  create_launch_template   = false
  launch_template          = "my-template-first"

Then, I changed the value of launch_template to a different launch template. Terraform fails complaining that it can't find the template ID.
Versions

Terraform: 1.1.5

Provider(s): 4.2.0

Module: 5.1.1

Reproduction

Steps to reproduce the behavior:

Code Snippet to Reproduce
I used the official example with the following as the module code...
module "asg_sg" {
  source  = "terraform-aws-modules/security-group/aws"
  version = "~> 5.1.1"

  name        = "myasg"
  description = "A security group"
  vpc_id      = "sg-xxxxxx"

  create_launch_template   = false
  launch_template          = "my-template-first"

  tags = local.tags
}

Expected behavior

Actual behavior

Generates the following error.
module.asg_sg.aws_autoscaling_group.this[0]: Modifying... [id=myasg]
╷
│ Error: Error updating Auto Scaling Group: ValidationError: Could not find the specified version 10 for the launch template with ID lt-0b8bd84c8f06fa112.
│       status code: 400, request id: 15593a61-1469-47a0-8778-ca01f5702b8c
│
│   with module.asg_sg.aws_autoscaling_group.this[0],
│   on .terraform/modules/asg_sg/main.tf line 226, in resource "aws_autoscaling_group" "this":
│  226: resource "aws_autoscaling_group" "this" {
│

Terminal Output Screenshot(s)

Additional context

Here is my observation...... When I change the value of the launch_template in the module, Terraform doesn't automatically go an fetch the template ID of new template and use that along with the launch_template name. Instead it uses the old template ID with the new launch_template name. If it is possible to add support to specify the launch template ID and/or launch_template name, then this would be fixed.

you'll need to add the variable launch_template_version since the template is managed externally from the module
Ref: https://github.com/terraform-aws-modules/terraform-aws-autoscaling/blob/master/main.tf#L235-L239

I added used launch_template and launch_template_version both. Still it gives e the same errors. It keeps looking for previous instance template ID.


[WIP] Skeleton of SD example with QNN EP

Describe your changes

Skeleton of SD example with QNN EP

Checklist before requesting a review

[ ] Add unit tests for this change.
[ ] Make sure all tests can pass.
[ ] Update documents if necessary.
[ ] Lint and apply fixes to your code by running lintrunner -a
[ ] Is this a user-facing change? If yes, give a description of this change to be included in the release notes.
[ ] Is this PR including examples changes? If yes, please remember to update example documentation in a follow-up PR.

(Optional) Issue link

more description to explain the background would be helpful.

This PR does not aim to be merged. Just a demo fro qnn team. Already shared with them, will close it.


[Bug]: LlamaIndex taking too long i.e like about 20-30 minutes to bring back a response.

Bug Description
My RAG implementation takes about 20-30 minutes before bringing a response. Whenever I use a pdf containing 190 pages or even when I use a pdf containing 5 pages, it still takes a really long time to generate a response. I am not sure whether it is a bug or simply my laptop lacking the required requirements. When I started using LlamaCPP or Llama Index, my_query.query() function would take only like 2-5 minutes to run. However it's like with each run thereafter, it only took longer.
My laptop is a Dell Inspiron 3521 with an 8gb RAM, no dedicated GPU,an Intel 3rd Gen Core processor, core i3 with 4cores with processing power of 1.9GHz.
I would really appreciate it if someone could tell me what is wrong.
Version
llama-index v0.10.5
Steps to Reproduce
Running query_parser.query(question) function.
Relevant Logs/Tracbacks
No response

llama.cpp in general is very slow. Especially without leveraging a GPU (I'm not sure if llama.cpp works on intel CPUs?)
I recommend using ollama for a more optimized time (or as optimized as it can be on your machine)

@abhim1509 do you have any tutorials for each point you mentioned, please?


Generated Thrift client

This PR is the start of an auto-generated Framed Thrift Binary Protocol
client.
Some work was needed in order to make the client work. This included
modifying the existing generators to:

Properly handle void return types
Create exceptions using defexception rather than defstruct.

I also modified the thrift test case so it was able to pass context from
setup functions. This is necessary because testing is accomplished by
creating an erlang server off of a test client and running actual thrift
calls against it. I've validated a number of different scenarios, and
all appear to work

@fishcakez, I pretty much stole most of the client from your connection example. I'd appreciate any comments about that.

Coverage increased (+0.6%) to 91.576% when pulling c0be0ab496246c394025cc5199c8e0cc4988bc7e on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage increased (+0.6%) to 91.576% when pulling 6d0ca32e6e6a373f1857be0db523c73f2c49cbe6 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage increased (+0.6%) to 91.576% when pulling d2106dbce245eced9b9e1bcb1e1921abf3199772 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage increased (+0.6%) to 91.576% when pulling 01829e75ab4a9759cead3bd1611ffa9fe51f53d9 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage increased (+0.6%) to 91.576% when pulling e20f8c94e91112210ccd426d492c4d72a7780564 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage increased (+0.6%) to 91.576% when pulling 115f6b49db504981769a35303b8e04d204829298 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage increased (+0.6%) to 91.576% when pulling 115f6b49db504981769a35303b8e04d204829298 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage increased (+0.6%) to 91.553% when pulling 86237bd8f558f2c7b84e9f427cbe2ea4217eebe6 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage decreased (-4.3%) to 86.683% when pulling a75aa6a3e2a746be290068114b2c03ff3d2dd535 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage decreased (-4.4%) to 86.525% when pulling bbd1ccdb612e8bb8eb42f5b64a55522f3d452bd8 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage decreased (-4.4%) to 86.525% when pulling bbd1ccdb612e8bb8eb42f5b64a55522f3d452bd8 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage decreased (-4.4%) to 86.525% when pulling bbd1ccdb612e8bb8eb42f5b64a55522f3d452bd8 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage decreased (-4.4%) to 86.525% when pulling bbd1ccdb612e8bb8eb42f5b64a55522f3d452bd8 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage decreased (-4.4%) to 86.525% when pulling bbd1ccdb612e8bb8eb42f5b64a55522f3d452bd8 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage decreased (-5.02%) to 85.915% when pulling 1e7c1d5eadf5e1640f3116b701aa5d22351efd6b on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage decreased (-1.5%) to 89.412% when pulling a322fd5c54bd539dafce583478aa06ef93b74373 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage decreased (-1.6%) to 89.327% when pulling 283932a15975ba44ee5dec2d1af6b508b6660599 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage decreased (-1.6%) to 89.327% when pulling 283932a15975ba44ee5dec2d1af6b508b6660599 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage decreased (-1.6%) to 89.327% when pulling 283932a15975ba44ee5dec2d1af6b508b6660599 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage decreased (-1.6%) to 89.327% when pulling 283932a15975ba44ee5dec2d1af6b508b6660599 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Coverage increased (+1.2%) to 92.111% when pulling 066f6a0987b40f7f0f8d420aec22f58d6dbe3e94 on scohen:thrift_client into ce6e90efee9ca72b98a523891acfac1802c488b0 on pinterest:thrift_tng.

Hello, @scohen! This is your first Pull Request that will be reviewed by Ebert, an automatic Code Review service. It will leave comments on this diff with potential issues and style violations found in the code as you push new commits. You can also see all the issues found on this Pull Request on its review page. Please check our documentation for more information.

Ebert has finished reviewing this Pull Request and has found:

20 possible new issues (including those that may have been commented here).
1 fixed issue! 🎉

But beware that this branch is 10 commits behind the pinterest:thrift_tng branch, and a review of an up to date branch would produce more accurate results.
You can see more details about this review at https://ebertapp.io/github/pinterest/elixir-thrift/pulls/72.

Ebert has finished reviewing this Pull Request and has found:

1 fixed issue! 🎉

But beware that this branch is 10 commits behind the pinterest:thrift_tng branch, and a review of an up to date branch would produce more accurate results.
You can see more details about this review at https://ebertapp.io/github/pinterest/elixir-thrift/pulls/72.

Ebert has finished reviewing this Pull Request and has found:

3 possible new issues (including those that may have been commented here).
1 fixed issue! 🎉

You can see more details about this review at https://ebertapp.io/github/pinterest/elixir-thrift/pulls/72.


bump minor version

Codecov Report

Merging #60 (dde2531) into main (49c5b3e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #60   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           10        10
  Lines          316       316
  Branches        40        40
=========================================
  Hits           316       316

Continue to review full report at Codecov.

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


Configure all of the awaits in the simulator

We don't need to synchronize the context in the simulator. Let's add .ConfigureAwait(false) to all of the async calls. See 1f888d4bb8994122a20f0ebfbf0d4f30fa41375d for an example.

this is a duplicate of #171


Upgraded to Angular 13

No longer relevant after Dependabot upgrades

Fix was based on:
https://github.com/angular/angular/issues/44026#issuecomment-958385983
https://github.com/angular/angular/blob/master/integration/platform-server/base-config.mjs#L3

FYI
Here are the reasons for module changes from cjs to mjs:
webpack.common.js imports now a mjs: '@angular/compiler-cli/linker/babel', therefore it is now a mjs, and would be good that all files that depends on  webpack.common.js  also changes to mjs, they are:
webpack.aot.js
webpack.dev.js
webpack.prod.js
First one is already converted since it is the one executed by the gradle build.
If this is accepted as the correct solution to the problem, then it will be also necessary to update webpack.dev.js and webpack.prod.js to mjs.

@reisfmb Seems like a fine solution, please fix other files. Also note conflicts in this PR that should also be solved.


Build system rewrite

Build system rewrite
If anyone has any other ideas of things to add to the new build system (even stuff that was there before and I missed it), please leave a comment in this PR and I will add it to the list.
Tasks to complete

[x] Initial version of the build system done.
[x] Better way for targets to select a cpu/arch
[x] Patch elf
[x] Build formats
[x] Better ux for port writing
[ ] Change all ports to work with the new build system (wip)

[ ] rp2xxx: find a way to build bootrom and also expose it so as to allow user targets to reference it
[x] lpc
[x] stm32
[x] nrf5x
[x] gd32
[x] atsam
[x] avr
[ ] esp

[ ] Change all examples to work with the new build system

[x] rp2xxx
[x] lpc
[x] stm32
[x] nrf5x
[x] gd32
[x] atsam
[x] avr
[ ] esp

[x] Final touches

[x] Add the remaining options from the previous build system
[x] Add the package command back to the root build.zig

If each port is now a type, is it possible to add out of source ports? If we can't is this a direction we want to take the project?

Sure. This is how it would look if you followed the same design as the ports in the repo (though this is not required).
pub fn build(b: *std.Build) void {
    const optimize = b.standardOptimizeOption(.{});

    const mz_dep = b.dependency("microzig", .{});
    const mz = MicroZig.init(b, mz_dep);

    const port_dep = b.dependency("port", .{});
    const port = @import("port").init(port_dep);

    const fw = mz.add_firmware(.{
        .name = "test",
        .root_source_file = b.path("src/main.zig"),
        .target = port.whatever,
        .optimize = optimize,
    });
    mz.install_firmware(fw, .{});
}

I don't understand why altering the structure of the core package is useful to this task.

I did this because since the root build.zig contains the build system, it seemed logical to make core/microzig.zig a part of this package (since it is the one that merges all the moving parts we have to add all the necessary imports, which can be done even if the module belongs to a different package, but it makes sense that the package that creates the module also adds all the imports). The same goes for core/start.zig or any other modules (chip, hal, board). They are constructed by the build system.
Another reason is that core can't be used on it's own (at least in it's current form), it would only ever be used by the microzig build system. There are some definitions that I think can be placed in another package (core) that contains Mmio, etc. This would allow other packages to access those definitions.
I apologize for the excessive amount of changes and for making you navigate the long long diff :). I guess my lack of experience with open source really shows here. I went through several iterations of the code (without starting fresh) and I changed a lot of things I didn't write in the process. If there are two many changes, I can make a cleaner pr.

I agree that this is not a pr, but more of a playground of ideas and it contains stuff not necessarily related to the purpose of the original pr. If it's ok with you, I'll make a new pr with only the only changes being to the build system or force push in this one. There is also a bug in the stm32 chip generation (fixed here) for which I'll make a different pr.

@tact1m4n3 Thank you for the example, I really like how this is turning out. No worries on being new to open source, you've done some great work here and I'm happy to help get this into the main branch. As a bit of extra information, we do squash commits here, so in the final history every PR will result in a single commit. This makes it so that one feature, bug fix, etc is reflected by every commit, so when you look at a patch, it's a meaningful addition to the codebase.
You're making some big changes to the build system so it makes sense that it'll touch a lot of files, but if you can please make those other, PRs that you mentioned!

Just fixed the build error and merged the branch with upstream/main.

if you can please make those other, PRs that you mentioned!

Can you clarify please to what PRs are you referring to?

There is also a bug in the stm32 chip generation (fixed here) for which I'll make a different pr.

I've already submitted this one. #282

I've already submitted this one. #282

I removed the changes addressed by #282 from this PR. I think it would be better to merge this one first (there are conflicts between them) because then it would be clearer what PR patched what.


Simple README.md typo

I think under the styled components section you meant to say  To see the **styled components** approach in this demo, start the app with yarn develop, then navigate to http://localhost:8000.
Both the styled components and the CSS components say To see the CSS approach...
BTW: Thanks for this repository!

Thanks @typerory! If you wanted to make the corrections in a PR, I'd be happy to merge it!


Unable to run

Hi, I'm trying to build the project and am using the general build routine for Grafana custom datasources/plugins:

yarn install
yarn dev

The yarn install works normally, but I run into this error when running yarn dev
$ yarn dev
yarn run v1.22.5
error Command "dev" not found.

I would appreciate it if someone could share some instruction on the proper way to run the project after cloning. Was unable to find this documentation in the README.md

Hello @colramos-amd,
Grafana 7+ changed a lot of the way plugins are built, my repo still uses https://grafana.com/docs/grafana/v6.0/plugins/developing/development/ as base for plugin development.
I'll try to update the README to be more helpful, but the steps are:

Run the server with npm run server or node server/mongo-proxy.js, its defaults to port 3333.
Clone the project in /usr/local/var/lib/grafana/plugins folder
Build the plugin front end with npm run build or npx gulp
Make sure the dist folder was created
Restart the Grafana server. If installed via Homebrew, this can be done with brew services restart grafana

You should now see the "Mongo to Grafana" plugin in your grafana plugins page

Thanks for sharing @portothree. Was also able to find these instructions here if anyone is curious.
Issue resolved.

@portothree I'm running this on v8.1.5, works fine

@portothree I'm running this on v8.1.5, works fine

Good to know! I have some 7+ instances as well. I guess they just changed the way to develop plugins, but kept the compatibility

@portothree I'm a bit lost how to get this to run.
What I've done:

Created a Dockerfile with contents:

FROM node:lts-alpine
ADD . /opt/app
WORKDIR /opt/app
RUN yarn install && npm run build
CMD [ "npm", "run", "server" ]

Copied the folder /opt/app/dist out into /var/lib/grafana/plugins/grafana-datasource-mongodb/dist
Restarted Grafana's container (grafana-oss:latest) & verified that /var/lib/grafana/plugins/grafana-datasource-mongodb/dist exists and contains files.
Browsed to Settings -> Plugins
???
Cant find your plugin...

Seems like I'm missing a step somewhere, any idea?


Unable to be used in server

The symbol used causes me to get kicked from the server, if it is possible could you provide a way to change it, or show us how to change it our selves , ive tried changing it in the code and "trying" to compile it but im not as programmer good as id like

I'm not sure what you're trying to do. Do you have the mod installed on the client? Why do you need to change the symbol?

Kicking the player when they try to use the formatting symbol is the default vanilla behavior and this cannot be changed clientside. it will work only if the mod is installed serverside.

The & symbol works for chat formatting on servers. If there was an option to replace § with & it could make it work on any server.

@Ari-RERA-43 you can use %% instead of &

Then there should be an option to use that


Removing all currency from DB

I've recently purged all waifus from the DB with sqlite.
Now i would like to reset everyone's currency (flowers) to zero.
Is it safe to do
DELETE FROM Currency;
for that to work ?
Would i also have to do the same for CurrencyTransactions?

I suggest you do it from currencytransactions too yeah. But you don't have to.


the vault title appears on the right

but when quick explorer 0.1.35 is activated, the vault title appears on the right
Obsidian 0.15.9

The vault title is on the right in the screenshot you posted.  This looks exactly like what it's supposed to look like with the new Obsidian, because Obsidian 0.15 normally adds the note name to the title and puts it in the center, where it would collide with Quick Explorer, making it impractical to use with smaller windows and screens.
Is there something different you wanted it to do?

indeed, on the right :P
If this was the case with 0.15 I noticed this just now (I was using Insider whole time), and I have problem with Minimal, by  default the vault title is hidden, but after the latest quick explore update the vault name is visible again, I wasn't sure if I should address it here or as an issue for Minimal
Feel free to close this issue if this is intended behaviour

I added a CSS workaround; some changes I made to make it work properly with a different theme caused it to reappear when using Minimal.  0.1.36 should fix the issue.


ld: library not found for -lWeChatSDK

ld: library not found for -lWeChatSDK
clang: error: linker command failed with exit code 1 (use -v to see invocation)

-_-


🐛 Bug ➾ Contextual help can only be obtained by making an erroneous request, e.g., missing a parameter

🚥 Status (Internal Taqueria Team Use Only)

[x] 🔬 Investigated and Verified
[ ] ⚗ Solution Identified and Designed
[ ] 🧫 Dev Implementation of Fix
[ ] 🧪 Fix Tested and Validated
[ ] 🏆 PR Merged

🆘 What happened?
The existing E2E tests were managing to invoke contextual help while my simplified rewrite was not succeeding. It turns out that the contextual help only comes in stderr and won't appear if you use the --help flag with or without the --projectDir param. If I set the test to call 'taq originate', provoking an error by missing the parameter, I get contextual help.
🆘 Steps to Reproduce?

taq init test-project
cd test-project
taq install @taqueria/taqueria-plugin-ligo@next
taq compile --help
gets contextual help!
taq compile --help --p test-project
Does not show contextual help

🪵 Relevant log output
❯ taq compile --help -p test1
taq [command]

Commands:
  taq init [projectDir]                     Initialize a new project
  taq scaffold [scaffoldUrl] [scaffoldProj  Generate a new project using pre-mad
  ectDir]                                   e scaffold
  taq opt-in                                Opt-in to sharing anonymous usage an
                                            alytics
  taq opt-out                               Opt-out of sharing anonymous usage a
                                            nalytics

Options:
  -p, --projectDir  Path to your project directory               [default: "./"]
  -e, --env         Specify an environment configuration
      --version     Show version number                                [boolean]
      --build       Display build information about the current version[boolean]

Taqueria is currently in BETA. You've been warned. :)

🐘 How impactful is this bug?
🤯 Major disruption
⏱ Prevalance
anyone looking for contextual help
💻 Operating System
Windows -> Linux VM
🕸 System Architecture
x64
🌮 Taqueria Version
dev-main
🌿 Node.js Version
v17.9.0
☎ Contact Details
<EMAIL_ADDRESS>Code of Conduct

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

This is a roadblock to a large class of tests.

seems to be a timing error in the tets.
The call for contextual help is made before the plugin loading is fully completed.
will redo tests to repair this.

@michaelkernaghan and I hopped on a call and found that this was related to two things in the tests:

The --projectDir flag needed to be removed, as the test was already executing within the test-project as its working directory
We found that some time needs to elapse between a) installing a plugin, and b) executing a task provided by that plugin


User documentation

It would be good to migrate and update user documentation from https://github.com/avogadro/manual and https://avogadro.cc:

[ ] Getting started
[ ] Tools
[ ] Menus
[ ] Rendering / Display options
[ ] Building molecules
[ ] Building materials
[ ] Optimizing geometry
[ ] Tutorials / Walkthrough

Hello! Can I work on this issue?

Sorry for the late reply - I didn't see this notification. I'd love to have help on this.
Some of the work is simply to migrate previous docs in manual and add updated screenshots.
(see https://github.com/avogadro/manual/tree/rev-2.0)


Custom aggregations on GroupBy dataframes

Hello,
I just started using your package and I find it really great!
However I cannot find a direct way of computing a custom aggregation on a GroupBy dataframe, something like:
sdf.groupby('name').aggregate(Mean())

in the spirit of https://streamz.readthedocs.io/en/latest/dataframes.html#dataframe-aggregations
Am I missing something?
Of course I can do the groupby operation inside the aggregation and keep all the keys inside the state but it would be very convenient if the framework could handle this for me
Thanks

If you look at GroupbyMean, you will see that the aggregation instance really does keep all the known keys in its internal state, but this state is small. It is accessed via GroupBy.mean (i.e., using GroupBy._accumulate). You could follow the same pattern for whatever aggregation you wished to do.

Thanks for the quick reply. I will check this out!

Thanks a lot for the quick reply!
Could you give me some direction on how to implement groupby followed by a window for dataframes as well?
Something like:
sdf.groupby('name').window(n=2).aggregate(Mean())

(I don't know if I should open a different issue though)

I have rarely seen windowing happening immediately after a groupby in streaming where state is being maintained. That's why I guess streaming systems like Spark Streaming and Flink (and streamz ofc) don't support windowing-after-groupby.
We use pipelines like the one below in production and they've worked reliably so far. I would also recommend having a map function do some groupby before passing dataframes into/creating an SDF, I've seen that help a lot of use cases as well, as it ensures that the SDF (and the state maintained) is light-weight, and only relevant columns are stored in the SDF.
def func(window_df):
    aggs = window_df.groupby(["Key"]).agg({"Col1":"min", "Col2": "mean"})
    aggs = aggs.reset_index()
    return aggs

downstream = sdf.window("8h").apply(func).stream

downstream.map(some_func).sink()

Hope this helps!


How to pad mini-batches in a training loop?

First of all, thanks for this wonderful library!
I have been reading through the tests and examples but I'm struggling to figure out one basic use case, so I hope you don't mind me asking here. What is the idiomatic way to iterate through a labeled dataset and pad the mini-batches before each step? I understand tch::data::Iter2 provides something akin to pytorch data loaders but the Iter2 constructor requires me to input the data as tensors, which means padding all data samples to the maximum length. As I'm working with language data this is not feasible in my case.
I looked at the translation example but it doesn't seem to use batching. Is my best option to implement something like tch::data::TextData{Iter} for labeled data myself, or have I missed some essential piece of the API somewhere?
Thanks a lot.

Hey, I don't think there is anything like this baked in tch for now. Might be good to look at rust-bert if you haven't done so already as it's likely to have more specialized NLP code.

Thanks, I had a look at rust-bert but unless I am mistaken it doesn't seem to support model training, only running inference on pretrained huggingface models.
I may have a go at implementing it myself based on the tch::data::TextData code.
Cheers!


tealdeer: 1.0.0 -> 1.1.0

bump tealdeer version to 1.1.0 and adapt meta.description to changed upstream README.
Motivation for this change
Things done

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

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

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

@GrahamcOfBorg build tealdeer

Success on aarch64-linux (full log)
Attempted: tealdeer
Partial log (click to expand)
    Finished release [optimized] target(s) in 2m 09s
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/jahcdilfnkrxyjyxiwjachm5bgmrr9yw-tealdeer-1.1.0
shrinking /nix/store/jahcdilfnkrxyjyxiwjachm5bgmrr9yw-tealdeer-1.1.0/bin/tldr
strip is /nix/store/p9akxn2sfy4wkhqdqa3li97pc6jaz3r1-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/jahcdilfnkrxyjyxiwjachm5bgmrr9yw-tealdeer-1.1.0/bin
patching script interpreter paths in /nix/store/jahcdilfnkrxyjyxiwjachm5bgmrr9yw-tealdeer-1.1.0
checking for references to /build in /nix/store/jahcdilfnkrxyjyxiwjachm5bgmrr9yw-tealdeer-1.1.0...
/nix/store/jahcdilfnkrxyjyxiwjachm5bgmrr9yw-tealdeer-1.1.0

Success on x86_64-linux (full log)
Attempted: tealdeer
Partial log (click to expand)
    Finished release [optimized] target(s) in 5m 46s
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/wvi7y6nbjlgf6ih1xdkzk4b7srp2ws86-tealdeer-1.1.0
shrinking /nix/store/wvi7y6nbjlgf6ih1xdkzk4b7srp2ws86-tealdeer-1.1.0/bin/tldr
strip is /nix/store/vcc4svb8gy29g4pam2zja6llkbcwsyiq-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/wvi7y6nbjlgf6ih1xdkzk4b7srp2ws86-tealdeer-1.1.0/bin
patching script interpreter paths in /nix/store/wvi7y6nbjlgf6ih1xdkzk4b7srp2ws86-tealdeer-1.1.0
checking for references to /build in /nix/store/wvi7y6nbjlgf6ih1xdkzk4b7srp2ws86-tealdeer-1.1.0...
/nix/store/wvi7y6nbjlgf6ih1xdkzk4b7srp2ws86-tealdeer-1.1.0

Timed out, unknown build status on x86_64-darwin (full log)
Attempted: tealdeer
Partial log (click to expand)
cannot build derivation '/nix/store/kpjx1rkz98x4cj163rr5kgwszh3afgyg-rust_serde_derive-1.0.18.drv': 6 dependencies couldn't be built
cannot build derivation '/nix/store/rjx3a0q6wg19y9b6id7sqy0jp2nrxkx5-rust_crates-io-0.11.0.drv': 27 dependencies couldn't be built
cannot build derivation '/nix/store/8aggs5cv8ifg0l6b15bbf9p07la74jzp-rust_docopt-0.8.1.drv': 19 dependencies couldn't be built
cannot build derivation '/nix/store/bn3l5khz2a646c1dmpjk3k39hyjfqysq-rust_git2-curl-0.7.0.drv': 19 dependencies couldn't be built
cannot build derivation '/nix/store/qb9hmvy8mjpiakgiim6hbrhbnj0k2y4q-rust_ignore-0.2.2.drv': 18 dependencies couldn't be built
cannot build derivation '/nix/store/qjzkag4bh1gipi327ih2h27c2g23ifhq-rust_cargo-0.22.0.drv': 78 dependencies couldn't be built
cannot build derivation '/nix/store/1wmw79b95m418fa4799sclb6pl9mhakr-rust_cargo-vendor-0.1.13.drv': 79 dependencies couldn't be built
cannot build derivation '/nix/store/isykh8ax2xk080yc0icmhvgg4da81zfg-tealdeer-1.1.0-vendor.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/g3iq8qvppm06jl15kiyh5w4zmda00smb-tealdeer-1.1.0.drv': 3 dependencies couldn't be built
error: build of '/nix/store/g3iq8qvppm06jl15kiyh5w4zmda00smb-tealdeer-1.1.0.drv' failed

cc @davidak


Running cactus-example-discounted-asset-trade is causing errors

Describe the bug
I plan to develop a bridge using Hyperledger Cactus between Ethereum and Hyperledger Fabric. While reviewing the examples, I found the cactus-example-discounted-asset-trade example, which seems like a great starting point.
There are two issues:

The script-start-ledgers.sh script doesn't work because the application uses V2_5, while the peer/orderer images use 2.4. I resolved this by updating the versions as follows, these version were obtained from the bashing inside the docker image:export CACTUS_FABRIC_ALL_IN_ONE_VERSION="2.5.6"
export CACTUS_FABRIC_ALL_IN_ONE_NODEENV_VERSION="2.5.4"

The yarn setup-credentials command still fails with the error described below.

To Reproduce

Cleaned up everything by running sudo ./script-cleanup.sh and ./script-cleanup.sh in cactus-example-discounted-asset-trade.
Made the following changes in script-start-ledgers:export CACTUS_FABRIC_ALL_IN_ONE_VERSION="2.5.6"
export CACTUS_FABRIC_ALL_IN_ONE_NODEENV_VERSION="2.5.4"

Ran the ledger using the following script: ./script-start-ledgers.sh &> out.txt
Following the commands mentioned in README ran the following command, in a separate shellcd ./examples/cactus-example-discounted-asset-trade-client
LOG_LEVEL=debug yarn setup-credentials &> out.txt
popd

Expected behavior
The commands should run and all the credentials should be generated.
Logs/Stack traces
Log for the command, ./script-start-ledgers.sh: https://hastebin.skyra.pw/foqotikeju.shell
Log for the command, yarn setup-credentials:  https://hastebin.skyra.pw/upanuvagej.swift
Logs of asset_trade_indy_all_in_one container:  https://hastebin.skyra.pw/rivevayora.pgsql
Screenshots
Added comprehensive logs along with this.
Cloud provider or hardware configuration:
Running this on a dev machine.
Operating system name, version, build:
Darwin 22.6.0 x86_64
node v20.11.1 (npm v10.2.4)
**Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
fa6cb101e
Hyperledger Cactus Plugins/Connectors Used

Nothing apart from the ones used in the example.

Additional context
Once the problem occurs, the following error is observed on subsequent attempts: https://hastebin.skyra.pw/uporepidar.swift.
It seems like the error is in:
  await agent.dids.import({
    did,
  });

but I haven't been able to pinpoint exactly what's missing.

cc:  @izuru0 @outSH @takeutak

I continued working on this issue and tried resolving it by updating the following code in the agent-setup.ts file:
- await agent.dids.import({
+ await agent.dids.create({

This allowed the process to proceed a bit further, but it is still not fully resolved. Here are the logs after the update: Logs.
Could you please help me resolve this?

The example seems to be working fine on linux environment, after merging the PRS.
We can close this now.

@rajat-dlt Nice, thank you very much for confirming and sorry for the slow responses!


SEAB-5808: Upgrade sonarscanner version

Description
This PR upgrades sonarscanner to version <IP_ADDRESS>06 to remove the warning related to the Java version. Previously we were using 4.7.0 with an embedded Java 11 which is being deprecated, and it seems sonarscanner is requiring Java 17 after version 5.0 (see https://docs.sonarsource.com/sonarqube/latest/analyzing-source-code/scanners/sonarscanner/ and https://community.sonarsource.com/t/why-does-sonar-scanner-force-the-usage-of-the-embedded-jre/4307).
Review Instructions
Check that sonarcloud doesn't warn about Java in pull requests (see below compared to this PR).
Issue
SEAB-5808
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!

[ ] Check that your code compiles by running npm run build
[ ] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[ ] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[ ] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[ ] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[ ] Do not use cookies, although this may change in the future
[ ] Run npm audit and ensure you are not introducing new vulnerabilities
[ ] Do due diligence on new 3rd party libraries, checking for CVEs
[ ] Don't allow user-uploaded images to be served from the Dockstore domain
[ ] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.
[ ] Check whether this PR disables tests. If it legitimately needs to disable a test, create a new ticket to re-enable it in a specific milestone.

Closing this PR because it's targeting the wrong branch. Here's the correct one: https://github.com/dockstore/dockstore-ui2/pull/1835


Warning: Tag: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.

Closing this as its fixed now


Windows Test Failure: unit._local_credentials_test.LocalCredentialsTest

Python unit test for local credential is failing on Windows. The observed behavior is hanging until timed out. It requires much more digging into Windows.
https://fusion.corp.google.com/runanalysis/info/prod:grpc%2Fcore%2Fmaster%2Fwindows%2Fgrpc_basictests_python/prod:grpc%2Fcore%2Fmaster%2Fwindows%2Fgrpc_basictests_python/KOKORO/f41c15a8-189d-4c8c-a17c-20dc203bc4d4/1566580323353/build %231772/Targets?e=-TargetLevelInsightsEnabled&jsmode=du

Haven't seen this issue in a long time, closing.


Ordering results on multiple properties

The Sorting section of realm-swift documentation states:
"Results allows you to specify a sort criteria and order based on a single or multiple properties."
The example only shows sorting on a single property. I need to order results on multiple properties, to produce the same result as the plain old SQL:  "select * from some_table order by foo, bar". Is this possible with Realm and if so what is the syntax? I've tried chaining sorted() properties to no avail.
It would be a really good idea to add an example to the documentation. Thank you!

The section of the documentation that you mention contains links to the API documentation for Results.sorted(_:ascending:) and Results.sorted(_:). The latter takes a sequence of SortDescriptors, representing the properties to sort by. Using that could look something like:
// Sort tan dogs with names starting with "B" from oldest to youngest, then by name
let dogs = realm.objects(Dog).filter("color = 'tan' AND name BEGINSWITH 'B'")
let sortedDogs = dogs.sorted([SortDescriptor(property: "age", ascending: false), "name"])

Thank you @bdash that works. It wasn't clear to me when looking at the API doc. One good example does a lot to clear things up.

I agree @Alamoz that is the only useful example that I've found... 👍

+1

@thonydam FYI this is currently supported


User/alexlam/37319832 main 220617

Enabled PreFast scanning to run on this repo. This is done by invoking the BinaryAnalysis template exposed by Packaged ES. Aside from PreFast, this template can also run BinSkim, Anitmalware, etc. scans.
Notes:

Currently PreFast is hitting a few errors, therefore, "break the build on error" mode is currently disabled. We should consider enabling that mode once the PreFast errors are resolved. Most other scans already default to the "break the build on error" mode.
Two switches are exposed to pipeline users in the form of parameters: 1) setting runSDLBinaryAnalysis to false will skip calling the BinaryAnalysis template altogether, including PreFast, this mode is useful for getting the fastest and cleanest pipeline run, 2) setting runSDLBinaryAnalysis to true but setting enablePREFast to false will still call the BinaryAnalysis template but skip only PreFast. This mode is useful for running BinSkim etc. scans but prevents the build tasks to report warnings due to PreFast issue.
Other than PreFast, PoliCheck and BinSkim are also reporting issues, but none of them look severe enough to break the build.
Also started calling the SourceAnalysis template from Packaged ES to do PoliCheck, CredScan, etc. scans, replacing the existing explicit call to the CredScan and BinSkim tasks. SourceAnalysis currently runs for in each pipeline run because they are relatively fast, and they currently don't produce much noise.
I don't see BimSkim results in older pipeline runs, but we get BinSkim results with this PR.
With the calling of both of the SourceAnalysis and BinaryAnalysis templates, we satisfy the Executive Order (EO) requirement.
The "auto file bugs" capability is not yet enabled, we should consider enabling it when the scan results are mostly clean and we are ready to track new scan errors by auto-filed bugs.

The PreFast issues can be found in this sample run:
https://microsoft.visualstudio.com/ProjectReunion/_build/results?buildId=51306833&view=results
Here's where to find the PreFast issues from the build results page:
•	Summary->Job->Build Release_x86->Guardian: PreFast -    0 Warning(s)    1 Error(s)
•	Summary->Job->Build Release_x86->Guardian: PreFast -       0 Warning(s)    1 Error(s)
•	Summary->Job->Build Release_Arm64->Guardian: PreFast -       0 Warning(s)    1 Error(s)
•	Summary->Job->BuildMRT Release_x86->Guardian: PreFast -    2271 Warning(s)    3 Error(s)
•	Summary->Job->BuildMRT Release_x64->Guardian: PreFast -    2273 Warning(s)    3 Error(s)
•	Summary->Job->BuildMRT Release_Arm64->Guardian: PreFast -  2276 Warning(s)    0 Error(s)
By default, PreFast is skipped in pipeline runs, like below, to avoid getting warnings for the build tasks:
https://microsoft.visualstudio.com/ProjectReunion/_build/results?buildId=51307855&view=results

/azp run

/azp run


Pop up an error after expanding Blob Containers for the second attached storage account

Repro Steps:

Right click one storage account and select 'Copy Connection String'.
Attach the storage account using the copied Connection String in Storage Explorer.
Attach the same account again using the copied Connection String.
Expand the Blob Containers node for the second attached storage account.

Expect:
There is no error dialog.
Actual:
Pop up an error dialog.

More Info:

This issue reproduces on Mac/Windows.
This issue also reproduces for File Shares, Queues and Tables.

Moved to Storage Explorer bugs.


Add be-RSE to the list of national RSE chapters

This PR adds be-RSE to the list of national RSE chapters and associates Johan Philips with it.
https://140-267395254-gh.circle-artifacts.com/0/SORSE20/contact/chapters/index.html
https://140-267395254-gh.circle-artifacts.com/0/SORSE20/contact/chapters/index.html#beRSE

👍 two remarks:

would it be possible to also add https://gitter.im/be-rse/ in the list of contact details?
I am currently still listed at UK RSE as well. But I could send a different PR to update my details, if you'd like. Also I am part of the program and organising committee :-)

sure, no problem. I'll fix both points when I am back on my laptop this evening. thanks @johanphilips!

alright @johanphilips, I updated your teams with 007fe8949681635e70c37eb0699dc659922e1e6e and I added gitter with d9ceadffff76fd4bf0f51874603f2fec3695f58a

can this then be merged?

You know, if you flipped the p (or speaking bubble in the graphic) on it's head, you'd have a "b" for Belgium!

Or you mirror the "d" in the de-RSE logo and you have a be-RSE logo :wink:

:exploding_head: !!!

So if I rip off both logos, we get something 'original' X-D
@Philipp, yes you can merge!
On Thu, Jun 18, 2020 at 9:17 PM Vanessasaurus<EMAIL_ADDRESS>wrote:

🤯 !!!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RSE-leaders/SORSE20/pull/84#issuecomment-646256781,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQABIOUQ5PMTGD62WIO7YFLRXJR4DANCNFSM4OBWBNKQ
.

Thanks, regarding the logo, we could use the avatar from Gitter:
https://avatars-01.gitter.im/group/iv/1/5eea1690d73408ce4fe727d8?s=144
On Thu, Jun 18, 2020 at 10:13 PM Philipp S. Sommer<EMAIL_ADDRESS>wrote:

Merged #84 https://github.com/RSE-leaders/SORSE20/pull/84 into master.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RSE-leaders/SORSE20/pull/84#event-3459885269, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AQABIOU7YSPHEQQUWL6H52LRXJYM7ANCNFSM4OBWBNKQ
.

@johanphilips that's beautiful!


Is there example of pog.json?

Hi there, would like to experiment a bit with your nice project, but after installing and running I just see a button to import pog.json file, and I'm not sure what is it and where to add dummy one to play with app. Is there one for tests?
P.S. I understand its very early project, just wanted to play with it a bit)

Ouch, sorry, misunderstood, it asks just to select directory)


[HOLD for payment 2024-12-25] [$250] Billable-Billable and "members must categorize all expense" on toggle off text color behavior

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: V9. 0.70-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Issue reported by: Applause Internal Team
Action Performed:

Launch app
Open a workspace chat with billable option enabled
Try to create a expense
Note in confirmation page, all option displayed in different color and billable option in different color
Toggle off billable option
Note now it matches with other option colors
Navigate to workspace settings - category- setti gs
Note the "members must categorize all expense" And below category heading text color is different
Toggle on/off "members must categorize all expense"
Note text color doesn't changes

Expected Result:
Billable and "members must categorize all expense" on toggle off text color behavior must be consistent.
Actual Result:
Billable and "members must categorize all expense" on toggle off text color behavior is inconsistent.
Workaround:
Unknown
Platforms:

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

Screenshots/Videos
https://github.com/user-attachments/assets/54d5d2f2-5241-45f9-8eb2-d26456f9484f

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021865173764798215374
Upwork Job ID:<PHONE_NUMBER>798215374
Last Price Increase: 2024-12-06
Automatic offers:

ikevin127 | Reviewer | 105276675
FitseTLT | Contributor | 105276677

Issue OwnerCurrent Issue Owner: @johncschuster

Proposal
Please re-state the problem that we are trying to solve in this issue.
Billable-Billable and "members must categorize all expense" on toggle off text color behavior
What is the root cause of that problem?
We are only applying the textSupporting color style when the iouBillable is false
https://github.com/Expensify/App/blob/64829131fe962681626b4b016140521d05f7fe52/src/components/MoneyRequestConfirmationListFooter.tsx#L532
What changes do you think we should make in order to solve the problem?

We should always apply the text supporting style unconditionally
                        titleStyle={{color: theme.textSupporting}}

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
What alternative solutions did you explore? (Optional)

Proposal
Please re-state the problem that we are trying to solve in this issue.
When the "Billable" toggle is turned off, the text color changes to match other options.
However, when toggling the "members must categorize all expenses" setting, the text color doesn't change consistently.
What is the root cause of that problem?

Consistent State Handling: Ensure that the toggle states for both "Billable" and "members must categorize all expenses"

Styles Consistency:

For the ToggleSettingOptionRow used in both "Billable" and "members must categorize all expenses," ensure that a consistent style is applied based on whether the toggle is on or off.

Use the same conditional logic for text color change as applied in the "Billable" toggle for the "members must categorize all expenses" toggle.

The existing logic applies a style change when iouIsBillable is false. You can apply similar logic to the "members must categorize all expenses" toggle.
src/components/MoneyRequestConfirmationListFooter.tsx
const membersCategorizeStyle = {
    color: isMembersCategorizeActive ? theme.textPrimary : theme.textSupporting,
};

// Apply this style in the "members must categorize all expenses" section.
<MenuItemWithTopDescription
    key={translate('common.membersMustCategorize')}
    title={translate('common.membersMustCategorize')}
    description={translate('common.membersMustCategorizeDescription')}
    style={[styles.moneyRequestMenuItem, membersCategorizeStyle]} // Apply the consistent style
/>

When the "Billable" toggle is switched off, you already apply titleStyle={!iouIsBillable && {color: theme.textSupporting}}. Ensure that the style for "members must categorize all expenses" is handled similarly in the style prop based on the toggle state

From my understanding of the issue here is that while the switch inputs are toggled OFF the Billable label should be the same as the Members must categorize all expenses label, since toggled ON are the same currently.

Billable and "members must categorize all expense" on toggle off text color behavior must be consistent.

Since the Expected result is a bit vague, I'd want to ask @Expensify/design's take on what consistent should mean in this issues case for both Billable and Members must categorize all expenses before making a decision on the proposals:

Billable OFF
Members OFF

Billable ON
Members OFF

Billable w/ Context
Members w/ Context

The reason why I want design's take on this is because if we look at the w/ Context images we can notice that in both cases the input labels are grey and the values are black but in the Billable case the label is grey when OFF and black when ON, while in the Members case the switch label is always black even though in both cases  input labels are grey and the values are black.

From my understanding of the issue here is that while the switch inputs are toggled OFF the Billable label should be the same as the Members must categorize all expenses label (meaning black), since toggled ON are the same currently.

Yeah, we don't fade out the text when the toggle is on, so it should remain black at all times. Nothing changes here from how we do it in the rest of the app 👍
On the Category Settings, I noticed that part of the top screen stays fixed when you scroll which shouldn't be the case:

Keen to hear what rest of  @Expensify/design thinks about this too

Updated according to the above feedback

Nothing changes here from how we do it in the rest of the app 👍

Agree with Jon—the label for the toggle row should be the same color regardless of on/off state. Here's an example from Preferences:

Yup, agree with all of those comments.

Clarifying timeline of events

first proposal came in, incomplete as it was not addressing the fix in MoneyRequestView component

second proposal came in, pretty much a copy of the first proposal (not adding anything new)

third proposal came in, a complete proposal in the sense that it was addressing the MoneyRequestView component as well, but the issue was that it suggested keeping theme.textSupporting and removing the condition instead:

To achieve this, we can remove the condition from both places and always apply the theme.textSupporting color.

I came in as a reviewer and requested design team's input in #53460 (comment)

design team clarified the expectations, confirming that we don't want the theme.textSupporting (grey / faded) but instead the switch labels should be black (on light theme) and white (on dark theme):

don't fade out the text when the toggle is on, so it should remain black at all times

additionally the design team requested a change regarding the top part of the WorkspaceCategoriesSettingsPage which should move with the scroll instead of being fixed (see details in #53460 (comment))

third proposal was updated, the only change being the additional change requested by the design team related to the top part of the WorkspaceCategoriesSettingsPage moving with the scroll instead of being fixed

first proposal was updated, adding the missing part related to MoneyRequestView label color:

we should not fade out on toggle off so we can remove textSupporting styles

and added a solution for the additional change requested by the design team related to the top part of the WorkspaceCategoriesSettingsPage moving with the scroll instead of being fixed

[!important]
The distinction between the first and third proposal is that the first one mentions that we should remove the theme.textSupporting styling completely, while the third proposal mentions removing the condition which would keep the theme.textSupporting styling (grey) which is not what we want according to the design team's feedback.

Given the timeline of events detailed in https://github.com/Expensify/App/issues/53460#issuecomment-2530101884, let's go with @FitseTLT's proposal as the root cause of our issue was identified correctly and the solution works as expected given all the requirements, including the additional scrolling requirement requested by design team.
🎀👀🎀 C+ reviewed

@ikevin127 and @FitseTLT, I will be OOO starting December 23 and will be returning January 6th. A handful of folks on the BZ team will be online for a few days in between the 25th and the 1st, but we'll be operating with a skeleton crew. I will be issuing my payments when I return on January 6th. If you would like the payment issued sooner, please post this issue in #expensify-open-source and someone on the team will jump in.
Thank you!

Regression test proposed, payments complete.


Hindi does not display correctly

Hello!
Hindi does not display correctly. The PDF Viewer gives extra spaces for the hindi joining characters, and does not combine with the letters.
On iOS are multiple emojis/emoticons appearing. This is only occurring on iOS devices. It appears to be that certain diacritics are being rendered as the emojis instead of diacritics.
See example.
http://www.pdf-archive.com/2015/01/28/hindisssues/hindisssues.pdf
It is rendered normally in other PDF readers, including Adobe Reader.
Best regards.
Qutbiddin.

Closing as duplicate of issue #5677.


Need negative semantics for K

Currently many definitions that are correct work correctly. The number of incorrect definitions that report a good error message is much lower. We need to come up with an integration test to test a number of the more common error messages in K to ensure that they are caught and given good error messages no matter what.

Why was this removed from the milesttone? I get that it's not part of the tutorial itself, but it's still vitally needed before we can release K 4.0 and get rid of the old pipeline?
Also, one error in particular I want to make sure we catch is that we need to have a good error message if the user accidentally makes a typo and includes a klabel in their definition that is never declared in a production.


Shader compile error running android godot editor on chromebooks

Tested versions

Reproducible in 4.3 from Google Play Store
Not Reproducible in 3.6 from Google Play Store

System information
Reproduces on our 2 chromebooks:
ChromeOS 103.0.5060.53 - Godot v4.3.stable - compatibility renderer - Acer Chromebook R11 (CB5-132T, C738T) - Celeron N3160
ChromeOS 126.0.6478.222 - Godot v4.3.stable - compatibility renderer - Dell Chromebook 5190 - Celeron N3350
Issue description
Running godot editor there is no 3d rendered, for example no grid lines or meshes drawn in new 3d scene. 2d is fine.

There are shader compile errors shown in adb logcat:
Creating new Godot fragment instance.

OnCreate: GodotFragment{75026bc} (035fb026-ec39-4ab5-8c63-f137278a4bb2 id=0x7f0800a1)
Initializing Godot plugin registry
OnInitNativeLayer: GodotFragment{75026bc} (035fb026-ec39-4ab5-8c63-f137278a4bb2 id=0x7f0800a1)
Godot native layer initialization completed: true
USER ERROR: Couldn't load file '/project.binary', error code 12.
   at: _load_settings_text_or_binary (core/config/project_settings.cpp:803)
Godot native layer setup completed
OnInitRenderView: GodotFragment{75026bc} (035fb026-ec39-4ab5-8c63-f137278a4bb2 id=0x7f0800a1)
OnStart: GodotFragment{75026bc} (035fb026-ec39-4ab5-8c63-f137278a4bb2 id=0x7f0800a1)
OnResume: GodotFragment{75026bc} (035fb026-ec39-4ab5-8c63-f137278a4bb2 id=0x7f0800a1)
Skipped 47 frames!  The application may be doing too much work on its main thread.
Loading /vendor/lib/hw/gralloc.cros.so from current namespace instead of sphal namespace.
android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasWideColorDisplay retrieved: 0
android::hardware::configstore::V1_0::ISurfaceFlingerConfigs::hasHDRDisplay retrieved: 0
Initialized EGL, version 1.4
Swap behavior 2
Device claims wide gamut support, cannot find matching config, error = EGL_SUCCESS
creating OpenGL ES 3.0 context :
Loading<EMAIL_ADDRESS>from current namespace instead of sphal namespace.
Loading /vendor/lib/hw/gralloc.cros.so from current namespace instead of sphal namespace.
Godot Engine v4.3.stable.official.77dcf97d8 - https://godotengine.org
1:
USER ERROR: SceneShaderGLES3: Program linking failed:
error: declarations for uniform `world_transform' have mismatching invariant qualifiers
   at: _display_error_with_code (drivers/gles3/shader_gles3.cpp:254)
USER ERROR: Method/function failed.
   at: _compile_specialization (drivers/gles3/shader_gles3.cpp:456)
USER WARNING: shader failed to compile, unable to bind shader.
   at: _version_bind_shader (./drivers/gles3/shader_gles3.h:222)
OpenGL API OpenGL ES 3.1 Mesa 19.0.0-rc5 (git-2e7833ad91) - Compatibility - Using Device: Intel Open Source Technology Center - Mesa DRI Intel(R) HD Graphics 400 (Braswell)
PlayerBase::PlayerBase()
TrackPlayerBase::TrackPlayerBase()
Emulating old channel mask behavior (ignoring positional mask 0x3, using default mask 0x3 based on channel count of 2)
AUDIO_OUTPUT_FLAG_FAST denied by server; frameCount 0 -> 1418

Displayed org.godotengine.editor.v4/org.godotengine.editor.GodotEditor: +2s522ms
Selected screen scale:  1
Selected screen scale:  1
Attempting to set client state on removed layer: Splash Screen org.godotengine.editor.v4#0
Attempting to destroy on removed layer: Splash Screen org.godotengine.editor.v4#0
OnGodotSetupCompleted
Skipping profile installation for org.godotengine.editor.v4
OnGodotMainLoopStarted

Steps to reproduce

install Godot 4 from google play store on chromebook
Run and create new project in compatibility mode
There are no 3d grid lines drawn in 3d scene editor, meshes added to scene do not draw

Minimal reproduction project (MRP)
Just create a new project

Commenting out line 323 in godot/drivers/gles3/shaders/scene.glsl   Fixes the error on both our chromebooks:
//invariant gl_Position;
I don't know much about shaders, so I don't know what other problems this change could cause. Our games look fine now though


Flag allowing a Winrm4jTool to use unique context

Fixes https://github.com/cloudsoft/winrm4j/issues/63
To test add in location configuration:
brooklyn.winrm.config.use.unique.context: true

LGTM (though I'v just read the code rather than testing it).
Note that in SshMachineLocation, it caches the sessions and reuses them only if a given set of config keys are identical (e.g. usename, password, etc).
I'm not suggesting you change this code to do that, but it's something worth bearing in mind.
@neykov any more comments/concerns before we merge this?

Thank you @neykov. I changed PR as you suggested.

Thanks @bostko, merging.


Unreliable energy extract and convergence check in script/vasp/general/check_vasp_status.py

Unreliable energy extract and convergence check in script/vasp/general/check_vasp_status.py, especially for un-converged jobs or SCF calculations.

Switched to ASE VASP calculator for convergence check from 4aaade570056afb3a6a855de1edcf40fbd475c9d. But need testing for various job type (optimization, SCF and more).

creating a new script under branch "vasp", under scripts.vasp.general.check_job_status_and_energy

Switched to Pymatgen for convergence check in 4d1c12aa50d9c97e5ba07553a6b0207757b2cbfe. Tests are yet to be performed.


Fixed auto focusing (bug #120)

Coverage remained the same at 86.657% when pulling 6baecc7349a858c77d5f0beb3f7da24e18866c13 on Valentin1918:fix-refocusing into 32bb58dc1b372379b8561b95fe934af9dd230439 on airbnb:master.

How does this fox a bug? Can you add a test that covers the bug? Also, please don't just comment out code - if it's commented out it should be deleted.

If src/component/DateInput.jsx inside an input (line 120) was passed onFocus={onFocus} , so logically it was made knowingly, based on some reasons. That's why I decided not to delete it but comment. My particular case was exactly the same as discussed in bug #120. And this little change, fixed issue for me. It seems should be some additional parameter to pass in component, which will manage passing or not onFocus method in Input tag.

Coverage remained the same at 86.657% when pulling 136cd95236db513e3fe72b7e6d5a18e83d393e0c on Valentin1918:fix-refocusing into 32bb58dc1b372379b8561b95fe934af9dd230439 on airbnb:master.

Coverage remained the same at 86.657% when pulling 46a9886775a9f2c62589a407f8e8b05af9f2df20 on Valentin1918:fix-refocusing into 32bb58dc1b372379b8561b95fe934af9dd230439 on airbnb:master.

This should be fixed by https://github.com/airbnb/react-dates/pull/212 in v4.1.1


localStorage not defined in server side

when doing SSR,  it shows error:
error while server-rendering' 'ReferenceError: localStorage is not defined\n    at LoginForm.getDefaultFieldValues (packages/std:accounts-ui/imports/ui/components/LoginForm.jsx:443:9)
may be add more check in LoginForm
typeof localStorage === 'undefined'

Ah, yeah, I haven't done a lot to make this work great in SSR. Would you mind creating a PR that checks this?

Great work @comus, this is now in the released version 1.2.15.


[HOPPER]feat(flash_attention_v2): enable backward tma feature[draft]

please create these PRs as draft directly instead of adding the [DRAFT] tag

must test in these environment variables: ENABLE_TMA=0, ENABLE_MMA_V3=1

seems like this PR also makes bwd pass faster. Can you update the ref numbers?


Climate Temperature control increaments

Current Behavior
Currently When changing the temperature up or down it goes in 0.5 increments.
Expected Behavior
I would like to be able to set the increment amount my AC only does whole amounts.
Steps To Reproduce
If you go down 26  it goes to 25.5 or if you go up  it goes 26 to 26.5.
Environment
- OS: Home Assistant 2022.7.7
- Node:  Supervisor 2022.07.0
- Version: Operating System 8.4
- Hassio: Frontend 20220707.1 - latest

I just installed mushrooms today.

Anything else?
No response

Hi 🙂 Each climate entity expose target_temp_step (and the default is 0.5 in Home Assisant).
You can customize this in your configuration.yaml if you want :
https://www.home-assistant.io/docs/configuration/customizing-devices/#manual-customization
homeassistant:
  customize:
    thermostat.family_room:
      target_temp_step: 1

Hi 🙂 Each climate entity expose target_temp_step (and the default is 0.5 in Home Assisant). You can customize this in your configuration.yaml if you want :
https://www.home-assistant.io/docs/configuration/customizing-devices/#manual-customization
homeassistant:
  customize:
    thermostat.family_room:
      target_temp_step: 1

I've been researching this for weeks. Multiple people asking the same. Nobody had an answer.
I came to request it for the Mushroom card, searched beforehand and there you are, solving the question at a system level. You're the man! Thank you 🙏

It's always better to fix the thing at the system level instead of providing an option because it will be fixed in every card 👍


harbor_project not detecting changes to some deployment security settings

Describe the bug
I have a Harbor project which is created via terraform:
resource "harbor_project" "main" {
  name                   = "xxx"
  public                 = false
  vulnerability_scanning = true
  enable_content_trust   = false
  deployment_security    = "high"
  storage_quota          = 20
  force_destroy          = true
}

When the checkbox Prevent vulnerable images from running or the corresponding severity drop-down is changed via UI, the provider does not notice the changes when doing a terraform plan.
To Reproduce

Create a project (see above)
In the Harbor UI go to project configuration. Under "Deployment security" section: Change the severity to Medium, uncheck Prevent vulnerable images from running and the save
Do a terraform plan => Terraform reports no changes detected

Expected behavior
In step 3 from above: Terraform reports changes for the two attributes
Additional context
If you now go on and also change another property (for example uncheck Automatically scan images on push) and again do a terraform plan, only this change will be detected:
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place
Terraform will perform the following actions:
  # module.XXXXX_harbor_project.harbor_project.main will be updated in-place
  ~ resource "harbor_project" "main" {
        id                          = "/projects/XXX"
        name                        = "XXXXX"
      ~ vulnerability_scanning      = false -> true
        # (9 unchanged attributes hidden)
    }
Plan: 0 to add, 1 to change, 0 to destroy.

But if you do now a terraform apply, all three properties will be restored.

Provider Version 3.10.12
Terraform Version 1.5.7
Harbor Version 2.11.0

I did some digging through the code.
It seems the two attributes are not propagated, when the project is read: https://github.com/goharbor/terraform-provider-harbor/blob/v3.10.12/provider/resource_project.go#L106-L158

hi @BlueIce ,
Thank you for the bug report
This will be fixed in the next version

Thanks for looking into this so fast. :smiley:


Add more color choices for login screen

I use different colors to distinguish visually between firewalls I manage. I wanted some more variation.
I checked that chosen colors have a high contrast to the white that is used for the text-entry, so that the text is clearly visible.

[?] Redmine Issue: https://redmine.pfsense.org/issues/NNNN
I read https://docs.netgate.com/pfsense/en/latest/development/submitting-a-pull-request-via-github.html, and I would consider this to be a "very minor typo/wording fixes" so I have not created an issue.
[x] Ready for review

Referes to https://redmine.pfsense.org/issues/9706


updated Consul version to 1.8 and removed sentence SMI adapter for ku…

Signed-off-by: user<EMAIL_ADDRESS>Description
Update Consul Version to 1.8
This PR fixes #1526

Updated Consul version from 1.5 to 1.8

Removed "The SMI adapter for Kuma can also be installed using Meshery" sentence from https://meshery.layer5.io/docs/service-meshes/adapters/consul

Notes for Reviewers
This is my very first open source contribution. its a start of a new dawn.
i'll get use to the process soon enough.
Signed commits

[x] Yes, I signed my commits.

Ka-pow! 💥 Thank you, @Rex739.

This PR fixes #1504


Update installing-the-github-copilot-extension-in-your-environment.md

Why:

If someone was installing copilot on Neovim, they would reasonably come across the vim section, follow the instructions and then realise, as they scroll down, they did it incorrectly,
On the other hand, if someone was installing it on vim, they would be much less likely to read the Neovim part and believe it was for them.

Also, the two sections are very difficult to tell apart when you first come across them, due to the differences in them being minor.
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):
Switched the Neovim and Vim install instructions around.
To further emphasise the difference between the sections, I put vim and neovim in italics in the subheadings.

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@sammyhori Thanks so much for opening a PR! I'll get this triaged for review ✨


Create a github action that uses fuel.nix to install forc

This would give us an idea of whether fuel.nix could be a viable replacement for fuelup in CI, in terms of latency to install forc.

Just for reference, today downstream users should already be able to use tools from fuel.nix in CI actions with something like this:
jobs:
  my-build-job:
    runs-on: ubuntu-latest
    steps:
      - uses<EMAIL_ADDRESS>      - uses: cachix/install-nix-action@v20
        with:
          nix_path: nixpkgs=channel:nixos-unstable
          extra_nix_config: |
            extra-substituters = https://fuellabs.cachix.org
            extra-trusted-public-keys = fuellabs.cachix.org-1:3gOmll82VDbT7EggylzOVJ6dr0jgPVU/KMN6+Kf8qx8=
      - run: nix shell github:fuellabs/fuel.nix#forc-0-39-0
      # Following steps now have `forc` version `0.39.0` available.
      - run: forc build

But yes, it would be great to test latency, and perhaps provide some wrapper action that takes care of the cachix installation with the necessary binary cache etc.

Another thought w.r.t. latency:
If it turns out that relying directly on the fuellabs cache does take too long, I'd imagine there's some way to provide a docker image that provides forc pre-fetched? I don't have enough docker experience to be sure :sweat_smile:


Raycast returns always null on first frame [AMMO]

Reproduced
var Main = pc.createScript('main');

// initialize code called once per entity
Main.prototype.initialize = function() {
    this._box = this.app.assets.find("Box", "template").resource.instantiate();
};

Main.prototype.postInitialize = function(){

    this.box1 = this._box.clone();
    this.app.root.addChild(this.box1);
    this.box1.setPosition(0, 0.5, 0);

    this.box2 = this._box.clone();
    this.app.root.addChild(this.box2);
    this.box2.setPosition(3, 0.5, 0);

    const from = this.box1.getPosition();
    const to = this.box2.getPosition();
    console.log(this.app.systems.rigidbody.raycastFirst(from, to));
};

Thinking about this, should we run/initialize the physics world before the very first script update with a dt of 0?

But often you set up positions and create physics elements in the first update.

Hmm, the positions and physics elements are set on body initialization, which often takes place on script initialization. I don't think creating a physics body in update method is a common practice. I think you need to step the world at least once, after adding a body to it in order to be able to query it, e.g. hit it with a raycast.
I did encounter issues caused by dt being zero a couple of times. It is not obvious, but debugging shows it immediately and it is easy to avoid. Being aware of the first frame delta time being zero, I simply ignore the update frame if dt === 0 when my update method depends on dt or I need a query. You can still interact with bodies normally on the first frame, like applying forces and such, even with dt being zero. This is mostly happening on some test scenes, where I do a raycast immediately for some feature test. In real apps, the physics interaction usually happens way later into the app lifecycle.
We can probably just document that caveat.


"NotFound: No such file or directory" on Deno Deploy

Hi, I've tried to deploy the minimal blog example to Deno Deploy, but encountered this issue:

I'm pretty new to Deno ecosystem and I'm not sure how I can debug it, especially I cannot reproduce it on my machine. Locally (deno task dev) works just fine - no issues.

Well, fortunately it didn't took long to find out what happened - I deployed the blog with en empty posts directory and no .md file whatsoever, what caused the above issue to occur.
Maybe it would be a nice idea to improve handling of this error, especially if it's not present when in dev mode.
When run locally without --dev flag and with empty posts dir, I only saw the following error: No such file or directory (os error 2), stat '/Users/michalweglarz/Code/deno-blog/hmr.js', but it didn't help me that much.

I think you have to deploy your where you compile it because it searches for posts directory in the place where compiling happens!


Standup Sandbox Environment for Pen Testing

We need to stand up a sandbox environment for pen testing.  This also fits in with the dev team's desire to be able to create a performance test environment on demand.
AC:

[ ] Sandbox environment running
[ ] Discovery UI is reachable on public DNS
[ ] Users are able to login to see private datasets
[ ] At least 1 public and 1 private dataset in system
[ ] Tearing Down removes all resources.

If anything learned from this card helps with common #432 or common #433 - please update those cards to capture it.  Thanks


Log Level Detection and Insights: Broken elements table

Describe the bug:
In the Log Level and Detection page, the table under the image with A, B, C, D, E, F elements is broken. The A and B rows of the table are formatted correctly, but the others - C through F - are not treated as a table anymore.

Desktop/Tablet/Smartphone (please complete the following information):

OS: MacOS 14.2
Browsers checked: Firefox, Chrome

@astencel-sumo, thank you for reporting the issue. The table is fixed now. It evidently got corrected by doc PR #3482.

@astencel-sumo, I spoke too soon. Once we merged doc PR #3486, the problem cropped up again. I'll get it fixed today.


PartTips resets transform Position/Rotation/Scale changed with B9PS when open

Basically I have a B9PS that alternates between how many engines the part supports and another to add or remove the engine shielding. but to properly pick the correct meshes without one module interfering with the other, I change the location and the scale of the mesh to hide it inside the part.
I also have another B9PS to change the position and rotation of a transform that allows different ways to dock.
When I open the Part Tips menu, those values are reset to default, as you can see in the videos (I apologize for the quality, had to compress a bit to upload to git) and are only corrected when updated again by B9PS.
https://github.com/user-attachments/assets/8322e97d-cf56-4bd1-9db4-f1a862a2431f
https://github.com/user-attachments/assets/6ab3ba37-5809-4af5-a0d0-6a2452a00b26
This appears to only happen when using positionOffset rotationOffset scaleOffset on a Transform node inside a B9PS subtype. I have not tested if this affects stock ModulePartVariants (which I believe offers a similar function, however I can't see the guide I always used because the forums are down)
For your own convenience, I've made a MM patch to add a B9PS module on the MK3 Shuttle Cockpit that allows you to test it.
@PART[mk3Cockpit_Shuttle]
{
    MODULE
	{
		name = ModuleB9PartSwitch
		moduleID = test1
		switcherDescription = test
		affectDragCubes = false

		SUBTYPE
		{
			name = y
			title = Default
			descriptionSummary = default position
			primaryColor = #FFFFFF
			secondaryColor = #808080

		}

		SUBTYPE
		{
			name = n
			title = Moved
			descriptionSummary = First Introduced on Ship 26
			primaryColor = #808080
			secondaryColor = #FFFFFF

		    TRANSFORM
            {
                name = cockpit
                positionOffset = 5.0, 0.0, 7.0
                rotationOffset = 180.0, 90.0, 0
                scaleOffset  = 1.5
            }
		}
	}
}

Thanks for such a detailed report and a config to test with. I'll get back to you once I've done some testing.

What's happening is that when Part Tips asks the game to compile a fresh set of part info for that particular instance of the part, the game asks each module on the part for the text you see here using GetInfo:

And B9PartSwitch is using GetInfo to do some initialisation of the different types probably with the expectation that GetInfo will only ever be called by the game at a certain time.
The call to InitializeSubtypes() seems to make the switcher reset.
public override string GetInfo()
{
    InitializeSubtypes();
    string outStr = $"<color=#7fdfffff>{SubtypesCount} {switcherDescriptionPlural}</color>";
    foreach (var subtype in subtypes)
    {
        outStr += $"\n- {subtype.title}";
        foreach (var resource in subtype.tankType)
            outStr += $"\n  <color=#99ff00ff>- {resource.resourceDefinition.displayName}</color>: {resource.unitsPerVolume * GetTotalVolume(subtype) :0.#}";
    }
    return outStr;
}

This is the full call stack from the button press in Part Tips to the
> Void B9PartSwitch.PartSwitch.PartModifiers.TransformMover:Deactivate ()+0x1 at B9PartSwitch\B9PartSwitch\PartSwitch\PartModifiers\TransformMover.cs:[45:13-45:27]
Void B9PartSwitch.PartSwitch.PartModifiers.TransformMover:OnBeforeReinitializeActiveSubtype ()+0x1 at B9PartSwitch\B9PartSwitch\PartSwitch\PartModifiers\TransformMover.cs:[32:69-32:81]
Void B9PartSwitch.PartSubtype:OnBeforeReinitializeActiveSubtype ()+0x1a at B9PartSwitch\B9PartSwitch\PartSwitch\PartSubtype.cs:[241:17-241:62]
Void B9PartSwitch.ModuleB9PartSwitch:InitializeSubtypes (Boolean)+0x52 at B9PartSwitch\B9PartSwitch\PartSwitch\ModuleB9PartSwitch.cs:[424:13-424:64]
String B9PartSwitch.ModuleB9PartSwitch:GetInfo ()+0x3 at B9PartSwitch\B9PartSwitch\PartSwitch\ModuleB9PartSwitch.cs:[232:13-232:34]
Void PartLoader:CompilePartInfo (AvailablePart, Part)+0x148 at KSP-Decompiled\Assembly-CSharp\PartLoader.cs:[1205:5-1205:53]
Void PartTips.PartTips:Open (Part)+0xb1 at PartTips\Solution\PartTips\PartTips.cs:[171:13-171:70]
Void PartTips.PartTips:CheckInput ()+0x1ab at PartTips\Solution\PartTips\PartTips.cs:[137:17-137:41]
Void PartTips.PartTips:Update ()+0x2 at PartTips\Solution\PartTips\PartTips.cs:[71:13-71:26]

It doesn't look like B9PartSwitch has been updated in a long time and I'd doubt they'd update for a minor compatibility problem with a small mod so I will have to think about what to do.

Here's a version of the PartTips.dll with a crude fix. Let me know if it works with your test case.
PartTips.zip

@Kari1407 I’m going to assume that this solves your case and close the issue. Let me know if it’s otherwise.

oh yeah, sorry, got a bit busy with work these past few weeks, but yeah it's good


Encapsulation of modules such as embedding,rerank, and ocr is too serious

Is there an existing issue for the same feature request?

[X] I have checked the existing issues.

Is your feature request related to a problem?
These modules are expected to be in OpenAI-formatted api configuration, pluggable form

Describe the feature you'd like
These modules are expected to be in OpenAI-formatted api configuration, pluggable form
Describe implementation you've considered
No response
Documentation, adoption, use case
No response
Additional information
No response

Coud you make an example of the scenario of usage.

The company has its own embedding, rerank, OCR, and VLM models, which are provided as APIs for external use. The company hopes that these atomic capabilities can be quickly integrated into projects, but it seems to be lacking related pluggable configurations. Thank you.


Letters with accents written twice

monaco-editor version: 0.13.0
Browser: Firefox
OS: Ubuntu
When you write a letter with an accent (such as á) it is written twice on Firefox under Ubuntu.
I've made tests and it happens with the last few Firefox 64-bit versions up to the newest (60.0) under Ubuntu 16.04 xenial x86-64. Also tested on an Ubuntu 16.04 live usb that includes firefox 64-bit version 51.0.1 to discard a particular problem with the first firefox.
Also checked with chromium in this ubuntu version and firefox in windows and works fine.
I've performed the tests here: https://microsoft.github.io/monaco-editor/index.html so it is not a problem with my implementation of monaco

Hi,Have you solved this problem? Or do you have any good ideas to deal with this problem?
Thank you

monaco-editor version: 0.16.2
Browser: Firefox v66.0.3
OS: Mac Mojave v10.14.3
Found out it also happens in firefox with mac

I could no longer reproduce on the latest at https://vscode-web-test-playground.azurewebsites.net/ so I believe this was resolved with https://github.com/microsoft/vscode/pull/106873


fix(exclude): support negative exclude matching child of excluded parent

I've fixed the filtering of files and directories with exclude patterns. Before, a negative exclude pattern was ignored when some parent path matched the exclude patterns. The reason lies in the custom top-down filesystem walk implemented in Worker._render_folder() which didn't traverse the contents of a directory if the exclude patterns matched, even when a negative exclude pattern matched a child of an excluded directory.
The solution is based on a different approach to walking the filesystem and excluding paths. Now, an iterator of all paths (files and directories) in the tree rooted at the template's copy root is produced via a recursive extension of os.scandir() and then filtered with the exclude patterns, so a subtree isn't pruned during the top-down tree walk. Instead, every path in the tree is considered and filtered individually based on the exclude patterns. Thus, Worker._render_folder() no longer implements a tree walk but simply creates a directory at the specified path. Also, Worker._render_{folder,symlink,file}() no longer render path templates, as paths need to be rendered prior to filtering with exclude patterns.
I decided to use os.scandir() over os.walk() or Path.glob("**/*") for better performance. It's also worth noting that the new implementation will walk subtrees of, e.g., .git/, even when they are excluded by the (default) exclude patterns. When using the subdirectory setting, the subtree of .git/ is ignored though because the root of the tree walk is the configured template subdirectory.
Fixes #1794.

Tests for Python 3.8 are failing because Path.readlink() was added in Python 3.9: https://docs.python.org/3/library/pathlib.html#pathlib.Path.readlink I'll fix this later.

Done. I think this PR is ready for review now.


viya4-orders-cli 1.6.0 has wrong version info

If I download the 1.6.0 release and execute:
./viya4-orders-cli_linux_amd64 --version

I get the following output:
viya4-orders-cli version 1.5.0

Thanks so much @tonineri! I fixed it.


UI does not appear to show git URL for book

Possibly user error but I searched for half an hour to find the git URL for a new book and could not find it, including anywhere in the book settings. Finally it is explained in the manual.

It is explained here: #189. It will be redesigned to make it easier to find.

Ok, that is far too important to hide behind a dropdown. Thanks for
listening.
On 1 Oct 2016 7:04 am, "nagim"<EMAIL_ADDRESS>wrote:

It is explained here: #189
https://github.com/GitbookIO/feedback/issues/189. It will be redesigned
to make it easier to find.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GitbookIO/feedback/issues/194#issuecomment-250892875,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AASzCGZlWTwfJ8Cguw3TfeQVLTBGxnGVks5qvenBgaJpZM4KLlth
.


[FLOC-1186] New docker-py

https://clusterhq.atlassian.net/browse/FLOC-1186
Skipped design review phase since there's nothing else left to do.

Thanks @itamarst
Some of the tests are failing which use the docker-py Client directly. Client seems to be using the 1.16 API version by default now so we need to force the older API version in those tests. I might quickly fix that and push so that we can see if there are any other build failures.
Not sure if we're still maintaining the python-flocker.spec file? If yes, update that too and ask @tomprince to package the new docker-py.
Otherwise this looks fine. Fix those tests and then merge.


Is there an example for going from JSON (not schema) to Java class using the Java API?

I'd like to have the same functionality the website has of converting a JSON (not schema) into a POJO but it seems like the documentation only has an example for converting a JSON schema. Any help would be appreciated!

`import java.io.File;
import java.io.IOException;
import java.net.URL;
import org.jsonschema2pojo.SchemaGenerator;
import org.jsonschema2pojo.SchemaMapper;
import com.fasterxml.jackson.databind.node.ObjectNode;
import com.sun.codemodel.JCodeModel;
public class JsonToJava {
public static void main(String[] args) throws IOException {
	JCodeModel codeModel = new JCodeModel();

	URL source = new URL("file:///C:/file.json");

	SchemaGenerator sg = new SchemaGenerator();

	ObjectNode jsonschema = sg.schemaFromExample(source);
	SchemaMapper mapper = new SchemaMapper();

	mapper.generate(codeModel, "ClassName", "com.package", jsonschema.toString());

	codeModel.build(new File("outputDir"));
}

}
`

Thanks @afxgroup. @allisonking I hope this helps.


Bug in http://getbootstrap.com/docs/4.1/examples/carousel/ on iPhone

Cursor is moving outside search text field when focused. Tested on Safari and Chrome on IOS 11.0.3. Problem occur when phone is vertical and horizontal. Makes it difficult to press submit-button since iPhone think you are inside the text field and start asking questions like "look up", "copy all".

Confirmed ok on iOS 12.0.1.


Update performance test script for SUSE

Coverage remained the same at 73.272% when pulling f7ff2825fe90d8fd8ff02c1f55f291d305ebcc68 on david-puglielli:perf-script-suse-update into 554ae999be5174cc830e859f7c49b766b418b96a on Microsoft:dev.


Will Frameit support RTL languages?

Any plans for frameit to support RTL languages? based on the search, it was not mentioned since #14941, #7522, and #8131.

We would be very happy to review and accept a Pull Request if someone submits one.

Sadly #8131 appears to have fixed the issue but it was not merged.

I've written a simple script for titles with RTL languages until Frameit gets builtin support.
I maintain a title.strings.before files that contains the original titles, and run this tool before running Frameit:
$ python3 reverse_titles.py

The script is here:
https://gist.github.com/amitkot/367f95ac1cb3ea73e20f80131e20c8e9


Update Readme to inform users they can use their Emma Credentials

Users can utilize their Emma credentials instead of the private/public
key to access the API if the keys are unavailable

Hey @sastrakhan
Thanks for the PR. Where did you find this information? I'm not seeing that ability in the documentation: http://api.myemma.com/


Remove redundant system tx check

This system tx check happens in verify_user_input()

@mystenmark there is one other place that we could remove a redundant check and its in ValidatorService::handle_certificate_v2. We would still need the following check or else getting the digest for the error span could panic when getting the inner tx data. If you think it is worth adding a another method that just does this check in SenderSignedData so we dont have to do all the checks here and then immediately again in handle_certificate
fp_ensure!(
            self.0.len() == 1,
            SuiError::UserInputError {
                error: UserInputError::Unsupported(
                    "SenderSignedData must contain exactly one transaction".to_string()
                )
            }
        );


Use .update_attribute over .save! for User login

For the two columns in question:

Updating :failed_login_attempts
Updating :lastlogin

Doing a full set of user validations is unnecessary, and ends up triggering some extra quries thanks to the UniqueWithinRegionValidator:
https://github.com/ManageIQ/manageiq/blob/cadc08a7/lib/unique_within_region_validator.rb
Since neither of these column updates have any relevance to that uniqueness check, there is no need to validate, and in turn, make extra queries as part of every API request each login request.
Similar fixes in the future will be addressing User authentication in the API further, but this is a simple and succinct set of changes to start that effort.
Benchmarks
tl; dr:  There is ~17% reduction in queries (26 -> 20) with this change, but that isn't reflected in ms in my environment due to nearly zero latency between app and DB.
This has been tested to reduce queries when using based token auth in the API. I was mistaken with this statement... and these particular fixes only affects /api/auth routes.
Both the Before and After benchmarks were taken with two runs of the same command from manageiq-performance:
$ bundle exec miqperf benchmark -ac 5 "/api/users"
D, [2020-08-21T11:38:21.658079 #79425] DEBUG -- : --> logging in...
D, [2020-08-21T11:38:22.012845 #79425] DEBUG -- : --> making GET request: /api/users
D, [2020-08-21T11:38:22.107294 #79425] DEBUG -- : --> making GET request: /api/users
D, [2020-08-21T11:38:22.198779 #79425] DEBUG -- : --> making GET request: /api/users
D, [2020-08-21T11:38:22.291756 #79425] DEBUG -- : --> making GET request: /api/users
D, [2020-08-21T11:38:22.383895 #79425] DEBUG -- : --> making GET request: /api/users

The reporting for manageiq-performance splits out the requests based URL, so the first /api/auth command is then associated with first 5 /api/users calls, and the second /api/auth is with the last 5 /api/users calls.
Note:  the savings is only in the number of queries for /api/auth, and not for any of the /api/users calls (though some separate fixes to address that will be added in the future), and the first request of the Before and After are slow because the server process just booted (so autoloading).
Before
/api/auth
|   ms | queries | query (ms) | rows |
| ---: |    ---: |       ---: | ---: |
| 5115 |      26 |        187 |   10 |
|  261 |      26 |        9.6 |   10 |
/api/users
|   ms | queries | query (ms) | rows |
| ---: |    ---: |       ---: | ---: |
|  140 |      12 |         12 | 1494 |
|   53 |      10 |        3.8 |   12 |
|   17 |      10 |        3.6 |   12 |
|   15 |      10 |        3.1 |   12 |
|   16 |      10 |        3.3 |   12 |
|   16 |      10 |        3.3 |   12 |
|   16 |      10 |        3.3 |   12 |
|   16 |      10 |        3.5 |   12 |
|   16 |      10 |        3.1 |   12 |
|   15 |      10 |        3.3 |   12 |

After
/api/auth
|   ms | queries | query (ms) | rows |
| ---: |    ---: |       ---: | ---: |
| 5148 |      20 |        185 |    8 |
|  256 |      20 |        7.4 |    8 |
/api/users
|   ms | queries | query (ms) | rows |
| ---: |    ---: |       ---: | ---: |
|  140 |      12 |         12 | 1494 |
|   18 |      10 |        3.9 |   12 |
|   17 |      10 |        4.2 |   12 |
|   15 |      10 |        3.3 |   12 |
|   14 |      10 |        3.2 |   12 |
|   16 |      10 |        3.4 |   12 |
|   16 |      10 |        3.1 |   12 |
|   16 |      10 |        3.1 |   12 |
|   16 |      10 |        3.3 |   12 |
|   16 |      10 |        3.0 |   12 |

Links

Helping speed up the API:  https://github.com/ManageIQ/manageiq-api/issues/880
The extra .update! calls were introduced in https://github.com/ManageIQ/manageiq/pull/20087

Yeah, so this is about reducing queries, where in a situation where there is actually database latency (in other words: not my laptop where these benchmarks were taken), this could have some improvements.

Sure wish we didn't have to give this disclaimer so often.
It is tricky for people to see numbers and then try and guess what the numbers would be if something like network latency were applied.

It's funny but I am frequently the one giving that disclaimer, too...from the review end though, I usually read the statistics given to me, and don't extrapolate for some reason 😄
For testing latency (or perhaps to enhance your number when queries are involved), it might be worth it to check out the tc tool, which allows you to introduce latency on your network connection.

For a while I was running the postgres daemon in a container (the database was still on my main machine)
But just the transfer over the virtual network really showed the difference this latency can make.
Of course it got corrupted and was enough of a pain to get back up and running that I ended back in bare metal land

Don't know why this popped in my head at 12:45 am, but it is what it is 😆

I saw this come in on Friday, and was thinking it was a little weird myself 😄
Anyway, I like the idea, so I will more this [WIP] and test it out at some point and confirm the same number of queries with that change.

Early tests still show 24 queries being executed on the /api/auth route... and this was what I tried to change:
diff --git a/lib/unique_within_region_validator.rb b/lib/unique_within_region_validator.rb
index ee90e944f5..4bae38c61b 100644
--- a/lib/unique_within_region_validator.rb
+++ b/lib/unique_within_region_validator.rb
@@ -14,6 +14,8 @@
 class UniqueWithinRegionValidator < ActiveModel::EachValidator
   def validate_each(record, attribute, value)
     return if value.nil?
+    return unless record.changed.include?(attribute)
+
     match_case = options.key?(:match_case) ? options[:match_case] : true
     record_base_class = record.class.base_class
     matches =

(did also "revert" the .update_attribute calls as well)
Still haven't figured out what are causing the extra calls yet.

Okay, so I found our culprit:
https://github.com/ManageIQ/manageiq/blob/f0b6fa0a07484d80748f9c47df059596502b7bd3/app/models/user.rb#L47
This validator causes the following two queries after each save:
SELECT  "miq_groups".* FROM "miq_groups" WHERE "miq_groups"."id" = $1 LIMIT $2

SELECT  1 AS one
FROM "miq_groups"
INNER JOIN "miq_groups_users" ON "miq_groups"."id" = "miq_groups_users"."miq_group_id"
WHERE "miq_groups_users"."user_id" = $1
  AND "miq_groups"."id" = $2
LIMIT $3

So making the above change to our custom validator removes two out of the extra 6 queries, but doesn't do the ones from this built in validator.

Wonder if there's a way to make that validates_inclusion_of  :current_group nicer (perhaps also similarly for changes to current_group)

Wonder if there's a way to make that validates_inclusion_of :current_group nicer (perhaps also similarly by checking there are changes to current_group)

@Fryguy Is this something that we want to try for now and in lieu of these changes, or is this just a thought for the future?  If it is the latter, then I am going to remove the [WIP] from this PR then.

-    return unless record.changed.include?(attribute)
+    return unless record.changed.include?(attribute.to_s)

@Fryguy Is this something that we want to try for now and in lieu of these changes, or is this just a thought for the future? If it is the latter, then I am going to remove the [WIP] from this PR then.

I'm thinking now.  It seems to make sense, as checking changed would help validations across the board, and my hunch is that if we get rid of the validations, then the update_attribute change would no longer be necessary.

Cool.  Going to leave this open as until that effort is complete as a reminder (mostly to myself) to check once those changes are merge that the new validator had the same effect.

Hope these will reduce the number of validations run:

https://github.com/ManageIQ/manageiq/pull/20520 (followup: https://github.com/ManageIQ/manageiq/pull/20539)
https://github.com/ManageIQ/manageiq/pull/20526

Closing in favor of https://github.com/ManageIQ/manageiq/pull/20590


Space cash stack sprite doesnt work

Description

Reproduction

spawn 1 cash in stack, have 1 sprite (green)
spawn 10 cash, have the same sprite
spawn 100, same sprite
Screenshots

Additional context

if you read the yml its not currently possible with the way stacking works and is a todo


Refactor set response object

closes https://github.com/SpoonX/aurelia-authentication/issues/120

This is a breaking change for me I think. I can make the change no problem but just to let you know

@AdamWillden what's the breaking part

It is strictly because I needed this feature before it was officially
implemented therefore I was reaching through with
authService.authorisation.reaponseObject = newResponse or whatever it
is. Because the method wasn't part of the officialy supported API it's not
really breaking I guess
On 28 May 2016 13:28, "doktordirk"<EMAIL_ADDRESS>wrote:

@AdamWillden https://github.com/AdamWillden what's the breaking part
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SpoonX/aurelia-authentication/pull/149#issuecomment-222306085,
or mute the thread
https://github.com/notifications/unsubscribe/AEaimDzwFXnyOz4uCsNB71iBQDeSewhqks5qGDUBgaJpZM4IpCZp
.

@AdamWillden i re-added the getter/setter. any chance you +1 me on this ;) i know i should go back and forth so ofter, but the get/set was stupid in the first place (i think i needed it in some step, but didn't consider to replace them then). anyways, this way it's better for a bc setTimeout approach (next PR)

I'll +1 anything :-p Are you saying I won't need to change anything now then? I don't mind if it's better either way

you woudn't need to change anything. just if the timeout PR gets in 3.1, i'd recommend using authService.setResponseObject(response) to use the non dirty checked authService.authenticated

I'm curious as to the purpose of this.

you mean the whole thing? for one get/set was stupid of me. secondly, makes the timeout thing possible

👍


Emma development

Thus far the main things I have done are add a navigation bar, add headers for different topics I want to talk about and added information about where I have lived.

Can you undo that merge, submit the original pull request, and the merge back and create another pr?
We gave approvals for the code until our review. So any new code you want to merge should be in a different pr.