Update ja.json, Update README_JA.md

Thanks for your contribution! ^^
Quick note: The files in the docs/readmes/generated folder should generally not be touched directly, as they are generated from the files in the docs/readmes/src folder. I've quickly fixed this! :)


Font is gray instead of black in drop downs

Describe the bug
The font colour for the text in the drop down menus on the analyst side (and possibly on the applicant side) are in gray instead of black before a value is selected in the drop downs.  This is an issue on PC when using Chrome or Edge.  They remain black on Mac.
To Reproduce
Steps to reproduce the behavior:

Open an assessment or conditional approval and where no previous value was selected
Use the drop down on the form
Font colour will show as gray instead of black

Expected behaviour
Font colour should be black
Screenshots
If applicable, add screenshots to help explain your problem.
Logs/tracebacks
Additional context
Add any other context about the problem here.

I'm not sure if it's a local issue for my browser but I am still seeing gray font in the drop downs.  PC with Chrome

PC with Edge


Add query functionality on the Interpolation

Added the query Functionality
Written the Test For the new functionality
Updated the TS function interface
Updated the README Docs with new functionality changes

Full functionality and changes can be viewed at:
https://github.com/bhattaraib58/pinterpolate/tree/add-query-functionality

@pratishshr dai, please review this PR and let me know if there are any changes needed.


android: fix onload not called

Its does not work yet! Please APPLY this commit!!!

Any plans for merging this PR?

Still not working

Beware that this line makes android crash when huge images are being loaded as no compression will take place
.override(Target.SIZE_ORIGINAL)


Sanitizing user input a little bit.

When entering coordinates on my phone I have to switch input modes between letters and numbers and colons. Removing the need to enter the colons will simplify things a little bit.
It seems my IDE has decided to remove all the unnecessary whitespace. I can create another commit to add it back if the diff size is a problem.
The logic requires that a colon should be entered after every four characters. This matches what I've seen in-game, but if there are other requirements then this will not give the expected result. A user can just enter colons themselves to avoid any sanitizing.

Do you mean in general map coordinate input or coordinate-to-glyphs input?
In first case you can just input spaces instead colons, since version 0.5 or so.
Doesnt have to be a 4character pack (even if it's leftpadded with 0s ingame) . you can write "i want to go to 469 81 d6d" in the coordinate field and it will work. The space feature was noticed on reddit thread, not on the website UI though.
In any case, i have a rework of the parsing points, done on closed tests in desktop languages, so colons wont be required (although parseable).

I mean the string that looks like "INQO:07F7:0077:07F7:0001" but now I've found coordinates that begin with 5 letters, so this PR isn't capable of handling that.


Use smarter type detection for AssignableTypes

Hi there,
This PR stems from an issue I've asked about in Gitter but didn't end up with a response, so I figured I'd submit the fix myself.
When developing agents locally and importing them via the ADDITIONAL_GEMS=some_agent(path:../some_agent) pathway, I noticed that any agents within the gems wouldn't end up in the agents list of the agent creation page. Doing some digging, I found that the reason was that the dropdown was being populated, via various layers of the stack, by this line in assignable_types.rb:
const_set(:TYPES, Dir[Rails.root.join("app", "models", module_name.underscore, "*.rb")].map { |path| module_name + "::" + File.basename(path, ".rb").camelize })

Searching through the app/models/agents directory naturally omits agents provided by gems, as they're stored not only outside of that directory, but even outside of the Huginn project root. This PR fixes this by populating the TYPES constant with the actual list of constants contained by the namespace at runtime.
The one thing I'm a little stumped on is how this list ends up getting populated properly (ie including agens in gems) when in production, as this is an issue I've only been able to replicate on my development instance. Perhaps there's something I'm missing here, but otherwise this seems like a pretty straightforward fix.

@gooroodev please take a look

Thanks, @admsev! Let's do this!
1. Summary of Changes
The pull request updates the method load_types_in within the AssignableTypes concern. The original implementation used file path detection to determine the types. This has been replaced with a more intelligent method that uses module constants to detect types. Specifically:

The old method collected types by reading file names from a directory.
The new method collects types by inspecting the constants within the specified module and filtering them based on the module's singular name.

2. Issues, Bugs, or Typos
Issue 1: Potential Inaccuracy in Type Detection
The new type detection method filters constants based on whether their names include the singular name of the module. This could potentially miss some valid types or include irrelevant ones if the naming convention is not strictly followed.
Improvement Proposal:
Instead of using include?, consider using a more precise matching strategy, such as checking if the constant's name starts with or ends with the singular name.
types = module_name.constantize.constants
  .select { |t| t.to_s.start_with?(my_name) || t.to_s.end_with?(my_name) }
  .map { |t| "#{module_name}::#{t}" }

Issue 2: Missing Newline at End of File
The file is missing a newline at the end, which is a common convention in many coding standards.
Improvement Proposal:
Add a newline at the end of the file to adhere to coding standards.
3. General Review of Code Quality and Style
Code Quality

The new method for type detection is more dynamic and reduces dependency on file paths, which is a positive change.
The code is more maintainable as it relies on the module's constants rather than the file system structure.

Code Style

The use of select and map is appropriate and follows Ruby conventions.
Indentation and spacing are consistent and readable.

Potential Improvements

Documentation: Adding comments to explain the logic behind type detection would improve code readability and maintainability.
Error Handling: Consider adding error handling to manage cases where module_name.constantize might fail or return unexpected results.

Conclusion
The pull request introduces a more dynamic approach to type detection, which is a positive change. Addressing the potential inaccuracy in detection and adding a newline at the end of the file will further improve the quality of the code.
Yours, Gooroo.dev. Got thoughts? Don't hesitate to reply or add a reaction.


Software closed after completion of piped screener

After completing the piped screener, pressing enter closes the entire screen. Could you please add an option to return to the main menu instead?
Because of this need to start software everytime,which is time consuming.
Thanks

Fixed in aefa9e63bd8e148d0ff5443f18509fa36dfd7d88

Fixed in the latest release: build number 532 and above.


oh-my-zsh error source:118 no such file or directory

I have installed oh-my-zsh along with spaceship theme in the past but recently I change the username folder in mac users which affected the theme.
When I open iterm, the theme is not there and I get this error:
/Users/someuser/.oh-my-zsh/oh-my-zsh.sh:source:118: no such file or directory: /Users/someuser/.oh-my-zsh/themes/spaceship.zsh-theme
I went into .zshrc, to change the the export ZSH=.., but it's still not fixing the problem.
It's complaining it can find the spaceship theme but it looks like theme is in another folder, /Users/someuser/.oh-my-zsh/custom/theme.
Not sure, how to let oh-my-zsh know to look in the custom folder. Has anyone encountered this issue? your help will be appreciated

You should put the them in $ZSH_CUSTOM/themes, note the extra s at the end of the directory.


Argument forwarding doesn't work with spaces in strings

Related to https://github.com/casey/just/issues/631
w +args="":
    cargo watch -x "r {{args}}"

> just w -- -a "D:\foo bar baz.mp3"
cargo watch -x "r -- -a D:\foo bar baz.mp3"
[Running 'cargo r -- -a D:\foo bar baz.mp3']
    Finished dev [optimized + debuginfo] target(s) in 0.65s
     Running `D:\projects\myproject.exe -a 'D:\foo' bar 'baz.mp3'`
Unrecognized argument: bar

error: process didn't exit successfully: `D:\projects\myproject.exe -a 'D:\foo' bar 'baz.mp3'` (exit code: 1)
[Finished running. Exit status: 0]

As a workaround escape the double quotes with \ when you run Just:
> just w -- -a \"D:\foo bar baz.mp3\"

Unfortunately this is an issue that I don't have a good solution for.
Each recipe line is passed to the shell as a single string, and just has no knowledge of the shell's splitting and quoting rules.
It might be possible to add logic to quote argument values when interpolating, but this would probably be flakey and not always do what you wanted.
One possibility would be to allow arguments to be exported as environment variables, since I believe that most shells ignore spaces when interpolating into strings:
# tell just that `args` should be exported as an environment variable
w $+args="":
    cargo watch -x "r $args"

This is definitely ugly and weird though.

Actually, I don't think exporting the argument as an environment variable does what you would want, so scratch that.

I think this could be resolved by single quoting the values in the argument interpolation.
For the Just invoc just foo "bar baz" qux, clap will parse ARGUMENTS as:
MatchedArg { occurs: 2, indices: [3, 4], vals: ["bar baz", "qux"] }

Say our justfile is:
foo +args:
  ls {{args}}

We'd get the desired behaviour by interpolating args as 'bar baz' 'qux', as parsed by clap.

There are a couple issue that I can think of with automatically adding quotes, one is that it might not always be desired. For example:
foo file +flags:
  cc {{file}} {{flags}}

If the flags arg is intended to hold multiple compiler flags, surrounding them with single quotes will cause them to be passed to cc as a single argument.
Another is that it's shell specific. Just supports both switching the shell with the shell setting, and shebang recipes that use #!... directives to use an arbitrary interpreter. Shells and interpreters might have different quoting rules, so single quotes might not be desired in all cases.

Just to clarify I meant quoting each arg as parsed by the shell rather than the entire expansion.

foo file +flags:
  cc {{file}} {{flags}}

Using this justfile we'd get:

foo foo.c -o foo.o: cc 'foo.c' '-o' 'foo.o'
foo foo.c -o "foo bar.o": cc 'foo.c' '-o' 'foo bar.o'

Shells and interpreters might have different quoting rules, so single quotes might not be desired in all cases.

Hmm yeah, this one is tricky.
Intuitively it feels like Just should respect the argument quoting. Without applying some sort of quoting to the argument expansion I'm not sure how else this could be achieved (without introducing weird new syntax for expansion behaviours). Perhaps with #604 there could be an attribute to opt-out of quoting on expansion of variadic arguments? This would mean that expansion would "just work" by default, but the quoting could still be disabled to satisfy cases where it's not desired.

This would have to be applied as the last step in interpolation. For example:
foo a b:
  echo {{a + b}}

If you do just foo x y you probably want echo xy or echo 'xy' and not echo 'x''y'.
Concatenating a variadic and non variadic argument is also tricky:
bar a +b:
  echo {{a + b}}

What should just bar a b c print? It isn't clear to me that there are any quoting rules that would make sense.
Also, if anything is inserted into a string literal, and not passed to the shell, then quoting would be undesirable:
checkpoint message:
  git commit -am "checkpoint: {{message}}"

Escaping \ the spaces of a string would have the desired effect without introducing over specific quotes which may break the string in question which may potentially contain both single and double quotes. I believe this works on Windows CMD and PowerShell as well using ^

@runeimp You mean that just could insert the backslashes? Or that it can't, and that the only way to make this work is to manually insert the backslashes in the args passed to just?

@Boscop Yes, just could look at an argument, determine it has spaces, then present that argument with spaces escaped when expanded. 🙂

There could be a function to shell escape its argument.

I added a quote function in #1022, which should work to quote strings for most shells.
However, having to call the quote function all the time would be tedious.
This would have some downsides:

All arguments would be quoted, even arguments that don't need to be. This might make output more verbose.
If you want not to quote arguments, for example, if you're passing multiple flags to a program, or you want the user to be able to pass globs, you would have no way to turn off quoting for a particular value.

I'm not sure such a setting would be worth it, and it might be better addressed in other ways.

@casey The quote function does not work for this use case. +args can contain multiple arguments, but {{quote(args)}} merges them into one.
For example, with this justfile:
run *args:
    cargo run -- {{quote(args)}}

When you type just run foo "bar baz", it will be expanded to cargo run -- 'foo bar baz', but it should be cargo run -- 'foo' 'bar baz'.
I agree with @runeimp that escaping spaces would be a solution: cargo run -- foo bar\ baz works in sh, bash, fish and zsh. It doesn't work in Powershell or cmd, however.

@casey The quote function does not work for this use case. +args can contain multiple arguments, but {{quote(args)}} merges them into one.

This is a limitation of how variadic arguments work. Just merges them into one space-separated string before they get to the quote function.
The best way to solve this is probably to pass arguments positionally:
use positional-arguments

run +args:
    cargo run -- "$@"

@casey Thanks, this worked!
One nit: s/use positional-arguments/set positional-arguments/

Does this work?
set positional-arguments

w +args="":
    #!/usr/bin/env zsh
    cargo watch -x "r ${(q-)@}"

I think the recommended way to avoid splitting is to use set positional-arguments, so this can be closed. It's annoying that there isn't a better option without positional arguments, but I think that's just a limitation of how just variables work. (E.g. they use string interpolation and don't know anything about the shell.)

@casey would you accept this contribution?
w *VARGS:
  egcmd {{quote_each(VARGS)}}

to quote each variadic arg like this: egcmd {{quote(VARGS[0])}} {{quote(VARGS[1])}}...

@MayCXC That would not work the way you think.
In just, everything is a string. The VARGS parameter is never a list. If you run just w 'foo bar' baz, the VARGS parameter will be set to foo bar baz, and a quote_each function would have no way to know not to return 'foo' 'bar' 'baz'.
Although, maybe that could be helped with a just setting to separate variadic parameters' arguments by an unlikely character (e.g. NULL character \x00) instead of space? (Or maybe the setting could even allow specifying a custom character/string? But that would be more useful if just strings allowed more escape sequences.)

maybe we can just add another parameter named like egcmd {{@VARGS}} for variadic arguments? the "actual" args come in unconcatenated here: https://github.com/casey/just/blob/d3bbde0c6049eb124d56fac396b670397e2c3977/src/main.rs#L2 and set positional-args` does stuff with them here https://github.com/casey/just/blob/d3bbde0c6049eb124d56fac396b670397e2c3977/src/justfile.rs#L335C18-L335C37 , so i think just already has everything it needs to do this, except a syntax.

other syntaces could be {{quote_each(VARGS[])}} or {{quote_each([VARGS])}}

after another minute of deliberation I'd like to propose {{quote_each(*VARGS)}}

how about with Function::NullaryPlus(fn(Context, &[String])) ?

Yah, @MayCXC, @laniakea64 is correct, by the time any variable gets to a function, it has already been turned into a string, so there's no way to know if it was a variadic parameter.
Changing this would be a huge change to the code.
I actually have a very wacky idea for how to fix this, but is such a huge undertaking that it is almost certainly not worth it.
The idea is this: Just currently has a simple and safe static type system, because everything is a string. However, lists of strings are not supported, which prevents things like quoting variadic arguments, and also prevents implementing a lot of things that people want. So, what you could do is make it so that every value is a list of strings, with all existing constructs producing a length-one list, with the exception of variadic arguments, which produce a variable-length list of strings. For backwards compatibility, all existing functions must behave the same as they currently do, which means space-joining the list to produce a single value, and then operating on that value, but then you can add new functions which can do something different, for example quoting, or doing something for each entry in the list.
But, like I said, this would be a massive code change, so probably isn't worth it.

The idea is this: Just currently has a simple and safe static type system, because everything is a string. However, lists of strings are not supported, which prevents things like quoting variadic arguments, and also prevents implementing a lot of things that people want. So, what you could do is make it so that every value is a list of strings, with all existing constructs producing a length-one list, with the exception of variadic arguments, which produce a variable-length list of strings. For backwards compatibility, all existing functions must behave the same as they currently do, which means space-joining the list

should i give it a shot and see if it's doable in like ~500LoC? you already have functions like shell that take a variable number of arguments, and parameters with ParameterKind::star have the needed list of strings for positional arguments. the grammar would just need ('*' | '+')? NAME in value, then a new field VariadicArgument in https://github.com/casey/just/blob/master/src/expression.rs#L10 . then https://github.com/casey/just/blob/d3bbde0c6049eb124d56fac396b670397e2c3977/src/thunk.rs#L62 can just handle two additional cases, a *NAME in a &[String] position, or a +NAME in a &str, &[String] position. VARGS is still just a string, so everywhere but function argument sequences should be able to ignore the change, and raise a parse error if a VariadicArgument value appears.

If you can do it simply, then why not, although I suspect you'll run into issues and it'll start to balloon. The core issue is that, by the time anything happens, the var arg is just a single string.


Resilience merge

• Critical load (enable-able)
• Reopt sizing with BTM pvsamv1 & pvwatts
	○ Weather file cannot be used for reOPT
	○ Dispatch is from perspective of load and is the value after battery internal, inverter and rectifier efficiencies
		§ SAM custom dispatch is from perspective of battery prior to losses
• Resilience metrics added if crit_load is present
	○ Msg in Electric Load Crit page
• Variables.h/.cpp
	○ Fix VarValue <-> var_data and VarTable <-> var_table
	○ Variables_test converting all types
• Invoke.h/.cpp
	○ Fix lk::vardata <-> var_data
	○ Invoke_test converting all types
	○ Update ssc_eqns

incorrect default changes removed


Add whatsnew entry for improved Info repr

Corresponding PR was already merged in #7451.

thx @cbrnr


Keep transparency png to tiff conversion

Hello,
Sorry If I misunderstood/misread the documentation, I tried to find an answer but I did not figure it out.
I am currently generating a background with transparency and composing it with multiple images at different positions with Sharp.

Background is in PNG
Images are in PNG
Output should be in tiff (conserving transparency)

See test with a single overlay:
const sharp = require('sharp')
const gd = require('node-gd')
const img = gd.createSync(200, 200)
const transparency = img.colorAllocate(255, 255, 255)
img.colorTransparent(transparency)
img.saveFile('test.png', (err) => {
 if (err) {
   console.log(err)
 } else {
   sharp('test.png')
   .tiff({quality: 100, force: false})
   .overlayWith('overlay.png', { gravity: sharp.gravity.center } )
   .toFile('test.tiff', (err, info) => {
       console.log('test.tiff saved')
     })
 }
})

Each time I'm doing this (only with tiff, it  works with png), the transparency is gone and I have a black bacground. How can fix this and keep transparency while exporting in tiff?

Hello, please see #594

Thanks you 👍


LibTrixi.jl does not pull in latest Trixi.jl version

When setting up libtrixi using libtrixi-init-julia, not the latest Trixi.jl version is installed, but v0.5.36. See e.g. https://github.com/trixi-framework/libtrixi/actions/runs/8964091186/job/24615337557#step:16:805
In the [compat] section we have
Trixi = "0.5.29, 0.6, 0.7"
and indeed Trixi can be upgraded afterwards without problems.
I tried to reproduce this with a LibTrixi.jl dummy package, which only has Trixi.jl as a dependency. I started with a fresh Julia project and ]dev <path>/LibTrixi.jl, which resulted in
Status `~/install/libtrixi-julia-test/Manifest.toml`
...
⌃ [a7f1ee26] Trixi v0.6.5 (<v0.7.13)

(The same happens with the real LibTrixi.jl package, i.e. ]add LibTrixi)
As indicated, Trixi.jl can be updated. However DiffEqBase is then downgraded:
⌅ [2b5f629d] ↓ DiffEqBase v6.145.2 ⇒ v6.143.0

Is this the reason why Trixi v0.6.5 was chosen in the first place? (The DiffEqBase compat entry for Trixi.jl was introduced in v0.6.6)
Starting again with  a fresh project and doing pkg> add Trixi in the first place directly installs  [a7f1ee26] + Trixi v0.7.13, and ]dev <path>/LibTrixi.jl afterwards succeeds without downgrading Trixi.jl.
So, should we just swap the order of installation?

I think the problem might be that we are requiring an older version of OrdinaryDiffEq (or DiffEqBase etc.) in Trixi.jl. Generally, I'd say it does not make sense to swap the order, since it could mean we might not get the latest LibTrixi.jl version. However, since this is particularly annoying, and Trixi.jl is the main package, can you please try to swap orders to see if it fixes things?

It does!


New repo for ServelessWorkFlow and Decisioning CoP

Type of repository request
Whether this request is a creation of a new repository, migration of existing repository, or deletion of a repository
Requested name for the repository
Name of the repository to create or location of existing repository to migrate.
Repository Description
Description applied to the newly created repository.
Associated CoP
The CoP this repository is associated with.
Admin Access
Name of the team(s) and/or user(s) that should have admin access on the newly created repository.
Write Access
Name of the team(s) and/or user(s) that should have write access on the newly created repository.
Read Access
Name of the team(s) and/or user(s) that should have read access on the newly created repository.
Additional details
Any additional information or context to provide for this request.

Review request:
cc: @redhat-cop/container-cop-core

Could you please create a repo called: serverlessworkflow-decisioning-cop.

@pamenon is this still a valid issue that you would like a new repo?

@sabre1041 No, everything related to this was done, so you can close it. Thanks for your help


Is there support for privacy manifest requirements from Apple?

Hi,
Is there support for privacy manifest requirements from Apple?
When trying to integrate Google Mobile Ads in a sample project, there is no entry related to Google Mobile Ads in the generated privacy report. Is that expected?
I see that a xcprivacy file was introduced on Nov 2023 with the following commit, but then the commit was reverted in Dec 2023.
Could we get an update on the latest status about the support for privacy manifest from Apple?

Hi @spqw, our next release 11.2.0 is expected to have to support for privacy manifest files.

Hi @spqw, our next release 11.2.0 is expected to have to support for privacy manifest files.

Do you know when that release is scheduled for?

It is live as of yesterday.

I've uploaded an app yesterday using 11.2.0 and got warnings about:

NSPrivacyAccessedAPICategoryDiskSpace
NSPrivacyAccessedAPICategoryUserDefaults

UserDefaults is expected also on my app, but the Disk Space I suspect is due to AdMob. I should also declare it on my app or the lib was already suppose to be sufficient?
(note the app I've uploaded had no Privacy Manifest)


Add 24hour.email domains

from: https://24hour.email/en
kinda.pw
mydot.fun
isnote.online

thanks, added


Storybook with TypeScript based application

I've created typescript based React app (with create-react-app) and added storybook there (by using getstroybook CLI command).
I've added webpack.config.js to define ts-loader to transpile my TypeScript code.
I've placed whole code here - https://github.com/sergeyzwezdin/storybook-with-ts
The problem is storybook building takes around 15 seconds with just single story. If I make the same for my real project it takes more than 20 seconds which is quite slow.
I guess this is because of both babel-loader and ts-loader build node_modules folder (I can see this process at console). Any way to avoid building node_modules.
P.S. I'm migrating application from @kadira/storybook to @storybook/react. With @kadira/storybook it worked much faster for me with the same codebase.

You don't have to double up on babel-loader and ts-loader. ts-loader can load javascript for you, and you're transpiling the Typescript down to ES5/commonjs modules anyways.
I'm not seeing anything that should make this so slow, exclude: /node_modules/ should already be excluding your node_modules.

Why did you remove the repository?


invalid

The package does not generate the private key and address correctly at all
check your example into https://iancoleman.io/bip39/ on bitcoin network

We just tested the key generation and derivation yesterday as part of our project and it works correctly.  We tested it against Bitcoin-Core and BDK.
Can you provide a specific test case ?

You must to create the address with an a derivation path like "m/44'/1'/0'/0/0"

I have the same problem, it doesn't generate the same private keys/addresses as
https://iancoleman.io/bip39/
I have also tried the seed in other HD wallets and it is still not the same keys.

Thanks, I'm already keeping an eye on it. Is it safe to send the seed or root key via rust bidings?

Thanks, I'm already keeping an eye on it. Is it safe to send the seed or root key via rust bidings?

yes, afaik.
rust cleans up after itself. the point of vulnerability is then the C pointer that dart is left with, which im pretty sure gets handled properly by the dart FFI library.


Documentation page for colormaps

As mentioned in https://github.com/napari/tutorials/pull/62#discussion_r430519300, our descriptions of colormaps is outdated. Since more layers can now use colormaps, it probably makes sense to make a single page describing them that we can link to.

see also issue 3597


More bug fixing related to index lists

*Catches the correct exceptions now
*Multiple spaces can be parsed correctly

Codecov Report

Merging #208 (da55166) into master (ba41159) will increase coverage by 0.59%.
The diff coverage is 45.16%.

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


design and QA callouts one click binding

Description
Fixed the
PR fixes following issue(s)
Fixes # (issue number)

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/build-deploy-preview env=release

/ok-to-test sha=447386131a49810b3a8c825b6c90ec4e5cf2ef3c

/ok-to-test sha=d9a0ab468ce0884c842c22a53b1a2dac0b6a2f1a

/ok-to-test sha=84af95ca891b320f55b673a16756d3dae8188923

/ok-to-test sha=d7a11713f3c7eb325aa8b3efa033def95dfde84a

/ok-to-test sha=8fc36c90425c9f1e096fc9ed4d63a9aed459ba6b

/ok-to-test sha=49fd5419e0828ce7595127067fd3bc16ea00cf5f

/ok-to-test sha=0f93ad2f44e98133b2bf07d0ca28fe46102be711

/ok-to-test sha=88bbf76bdf40d0e9d550f12af261b9c1550f3727

/ok-to-test sha=0e9b5af96ece9553deec32d599b7e4e730899044

/ok-to-test sha=cccfd73685e2ea6bdced82136e023e7d0fead099

/ok-to-test sha=801e1d81766b082fc1ced3b64efcdc8c393e71a3

/ok-to-test sha=eea0d26fdd663a3fabaa6825fee47021a9f92edd

2. cypress/e2e/Regression/ClientSide/OneClickBinding/TableWidget/mongoDB_spec.ts

@vsvamsi1 - Please check.. mongoDB_spec.ts has failed.

/ok-to-test sha=4f92e5142ca40c2ed462e240b209e0af42ce7185

cypress/e2e/Regression/ClientSide/OneClickBinding/TableWidget/mongoDB_spec.ts

@vsvamsi1 - Please check.. mongoDB_spec.ts has failed.

@Aishwarya-U-R ...that was a refactoring error i made from my end ....i fixed it right now

/ok-to-test sha=110c1b925d0700db0ccc2c2efa3ed3fe2a1d1e59

/ok-to-test sha=536fd43e9aacbf0db35761a5230debca3d6dcc12

/ok-to-test sha=cc69ee3157eab1d3c64269550250841b568460ca


Add accessors for all Toml variants

This allows users to coerce any TOML value into the type they expect it to be.
The test go over all variants except for Toml::Array since I couldn't figure out how to write one (arr = {key = "value"} ought to work, but doesn't).
I also wrote docstrings for all these methods.  I tended toward the language used in the TOML spec, though I fear that it might be confusing since the API uses language that contradicts the spec.

Thanks for the PR. I'll put non-panicking getters on my to-do list as well.


Add University BEST Sabel Berlin, Germany

Add University BEST Sabel Berlin, Germany

please provide the link to the page, describing long-term IT-related programs, that the university provides. Thanks!

obsolete request, please reply to reopen


Make the default value of renderFinalNewline the same on all platforms

Fixes #70126

:+1: Thank you!


Inconsistent nulling nested sub-chart values in v3.13.0, v3.13.1

This issue is related to https://github.com/helm/helm/issues/9027 which should been fixed in v3.13.0
However, looks like there is inconsistency where some nested sub-chart values are not nulled.
TL;DR
Nulling values remote sub-charts doesn't work, and it's still not possible to remove keys from them (remote means, during the packaging, they are referenced as dependency sub-charts with repository key).
But the sub-charts within the same repo during the packaging don't have that issue (null passed normally).
Details
In Camunda Helm chart, we have different types of dependencies (in-repo, remote, or nested), and some parts are nulled, and some are not.
Let's take this case:
The C8 chart depends on some in-repo and remote sub-charts, let's just focus on Elasticsearch sub-chart as an example:
Reproduce
Here is a minimal values file to reproduce the issue:
Create the custom values file:
# values-custom.yaml

# The vars according to upstream chart here:
# https://artifacthub.io/packages/helm/bitnami/elasticsearch/19.13.2#master-elegible-nodes-parameters
elasticsearch:
  master:
    podSecurityContext:
      fsGroup: null
    containerSecurityContext:
      runAsUser: null

Add Camunda repo:
helm repo add camunda https://helm.camunda.io

Template the chart using the custom file (you will see some irrelevant warnings could be safely ignored like coalesce.go:289: warning: destination for identity.postgresql.networkPolicy):
helm template demo camunda/camunda-platform \
    --version 8.3.0 \
    --values values-custom.yaml \
    --show-only charts/elasticsearch/templates/master/statefulset.yaml

The most important highlight here:
In the Pod securityContext: fsGroup: 1001 (not nulled, still default):
securityContext:
  fsGroup: 1001

In the Container securityContext: runAsUser: 1001 (not nulled, still default):
containers:
  - name: elasticsearch
    image: docker.io/bitnami/elasticsearch:8.7.1
    imagePullPolicy: "IfNotPresent"
    securityContext:
      runAsNonRoot: true
      runAsUser: 1001

And it's the same for any remote sub-chart (happens in Keycloak, and PostgreSQL).

Output of helm version:
version.BuildInfo{Version:"v3.13.1", GitCommit:"3547a4b5bf5edb5478ce352e18858d8a552a4110", GitTreeState:"clean", GoVersion:"go1.20.8"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.6", GitCommit:"741c8db18a52787d734cbe4795f0b4ad860906d6", GitTreeState:"clean", BuildDate:"2023-09-13T09:21:34Z", GoVersion:"go1.20.8", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.5+7d22122", GitCommit:"2fc599b5fd3f060dd20094b520f0f529fd2f52db", GitTreeState:"clean", BuildDate:"2023-06-07T20:30:17Z", GoVersion:"go1.19.9", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):  N/A

@aabouzaid are you sure it is caused by remote access to a chart? Have a look at https://github.com/helm/helm/issues/12488
I updated my reproduction steps there, adding repository: "file:///home/fedora/demo-remote/charts/subchart" to the dependency in the Chart.yaml, and then
$ ~/helm-v3.13.1/helm dependency update demo-remote/
Saving 1 charts
Deleting outdated charts
$ ~/helm-v3.13.1/helm package demo-remote/
Successfully packaged chart and saved it to: /home/fedora/demo-0.1.0.tgz
$ ~/helm-v3.13.1/helm template demo-remote/
---
# Source: demo/charts/subchart/templates/values.yaml
global:
  hash:
    key3: 13
    key4: 4
    key5: 5
    key6: 6
hash:
  key3: 13
  key4: 4
  key5: 5
  key6: 6
$ ~/helm-v3.13.1/helm template demo-remote/   --values demo-remote/values.yaml
---
# Source: demo/charts/subchart/templates/values.yaml
global:
  hash:
    key3: 13
    key4: 4
    key5: 5
    key6: 6
hash:
  key1: 1
  key2: 2
  key3: 13
  key4: 4
  key5: 5
  key6: 6

So it seems to me the issue is caused by using --values, not specifying a remote repository location.
If you can confirm this would be a duplicate of https://github.com/helm/helm/issues/12488

@rptaylor no, I'm not sure, it's just an observation.
I will try to put the vars in the default value file and see how it works.

I confirm Helm doesn't null the values from only if --values was spacified. So I'm closing this issue as it's a duplicate of https://github.com/helm/helm/issues/12488


CRITICAL: Wrong game closed

You closed the Denmark Game instead of France!
https://github.com/lsv/fifa-worldcup-2018/commit/f9da6a5a62db581a5fbdbd5b81110d71643963fd

@lsv please check

Should be fixed by #61


merge with main

Hi

Please rebase and clean up your PR
You have to make sure to preserve current functionality with same defaults and without degrading performance
(This PR can't be automatically merged by GitHub, which is not a good sign)

Sorry, I did not mean to try and merge my current work, I just found out that you have merge upstream with cli commands. I am almost finished creating the new classes for indepdentScatterChart*.  I'll send you a message when I think it is ready to merge and ask for advice on how to that because Ihave never done it before.

Basically you want your commits to be on a different branch - not on master - and of course use a rebase to squash and rename commits if you have too much noise in the branch.
Than create a PR. When you go to the home page of this repo it will suggest automatically creating a PR,


hdi screen UI fix

Codecov Report

Merging #240 (b1bf641) into main (95dd7c5) will decrease coverage by 0.40%.
The diff coverage is 59.74%.

@@            Coverage Diff             @@
##             main     #240      +/-   ##
==========================================
- Coverage   56.71%   56.31%   -0.41%
==========================================
  Files         221      222       +1
  Lines       27125    26979     -146
==========================================
- Hits        15385    15193     -192
- Misses      11740    11786      +46

Flag
Coverage Δ

gsagh
42.77% <29.16%> (-0.04%)
:arrow_down:

integration
43.47% <48.87%> (-0.40%)
:arrow_down:

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

Impacted Files
Coverage Δ

GsaGH/Components/1_Properties/CreateProfile.cs
80.00% <ø> (-0.08%)
:arrow_down:

GsaGH/Components/2_Geometry/EditElement3d.cs
25.37% <0.00%> (ø)

GsaGH/Components/5_Results/GetResults.cs
80.19% <ø> (ø)

GsaGH/Components/5_Results/NodeContourResults.cs
29.13% <0.00%> (ø)

...aGH/Components/5_Results/SelectResults_OBSOLETE.cs
38.58% <ø> (ø)

...mponents/5_Results/TotalLoadsAndReactionResults.cs
93.26% <ø> (ø)

GsaGH/Components/GraveyardComp/BaseReader.cs
0.00% <0.00%> (ø)

...omponents/GraveyardComp/CreateMember3d_OBSOLETE.cs
41.09% <0.00%> (ø)

.../Components/GraveyardComp/CreateProp2d_OBSOLETE.cs
23.63% <0.00%> (ø)

...Components/GraveyardComp/EditElement1d_OBSOLETE.cs
39.71% <0.00%> (ø)

... and 51 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Duplicated tests to be executed on workspace

Type: Bug

Create a workspace
Add two projects on it with their respective tests
Go to "Testing" section (flask icon) and discover tests from both projects.
Click on the "Run Tests" icon (two play icons one place below another) located in the upper part next to the TESTING title.
Below the filter it'll begin to run the tests up to finishing with the "Running tests, N/N passed (100%)" where N is the amount of tests from both projects.
Run tests again but this time from one of the projects clicking on the "Run Test" icon that appears once you hover on one of  the projects name.
The "Running tests"'s numbers now will be higher than initial N, being N+K where K is this selected project's amount of tests.
It'll be reset again to N once those tests have finished.

The expected behaviour would be to begin with N - K passed to reach again the desired and total N.
VS Code version: Code 1.70.0 (da76f93349a72022ca4670c1b84860304616aaa2, 2022-08-04T04:38:48.541Z)
OS version: Linux x64 5.15.0-46-generic
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz (8 x 1900)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
15.51GB (1.55GB free)

Process Argv
--crash-reporter-id 6e680e2a-6a43-41d5-8e91-5904f8b850ea

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

Extensions (19)

Extension
Author (truncated)
Version

increment-selection
alb
0.2.0

Bookmarks
ale
13.3.1

vscode-eslint
dba
2.2.6

gitlens
eam
12.1.2

EditorConfig
Edi
0.16.4

RunOnSave
eme
0.2.0

prettier-vscode
esb
9.5.0

randomeverything
hel
0.0.3

smarty
imp
0.3.0

python
ms-
2022.12.0

vscode-pylance
ms-
2022.8.20

jupyter
ms-
2022.7.1102252217

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.9

remote-containers
ms-
0.245.0

vscode-selfhost-test-provider
ms-
0.3.10

vsliveshare
ms-
1.0.5683

autodocstring
njp
0.6.1

vscode-yaml
red
1.9.1

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30542924
vsaa593:30376534
pythonvs932:30410667
wslgetstarted:30449410
cppdebug:30492333
pylanb8912:30545647
vsclangdf:30486550
c4g48928:30535728
d7fjc500:30543455
dsvsc012cf:30540253
azure-dev_surveyonecf:30545436

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.70.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Upgraded VSCode to 1.70.1 and the bug still persists

The total running tests is the sum of all test runs who have not yet finished. In the first screenshot in your issue, I see the progress bar still atop the Test Explorer view, which indicates that the extension didn't signal the run was finished. Thus when you ran more tests, they were added to the existing running test.
The test output terminal might have an indication as to why the run stalled. I tried to reproduce this by cloning pypika myself and didn't hit the same issue. But it does look like either a Python or extension issue, so I will transfer this over there...


Draft.

Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)
Related PRs
(If this PR adds or changes functionality, please take some time to update or suggest changes to the docs at https://developers.diem.com, and link to your PR here.)
If targeting a release branch, please fill the below out as well

Justification and breaking nature (who does it affect? validators, full nodes, tooling, operators, AOS, etc.)
Comprehensive test results that demonstrate the fix working and not breaking existing workflows.
Why we must have it for V1 launch.
What workarounds and alternative we have if we do not push the PR.

release binaries dependency change summary:
target packages:
  A consensus-notifications 0.1.0 (workspace, path 'state-sync/inter-component/consensus-notifications')
    * features: [none]

release binaries dependency change summary:
target packages:
  A consensus-notifications 0.1.0 (workspace, path 'state-sync/inter-component/consensus-notifications')
    * features: [none]

/canary

release binaries dependency change summary:
target packages:
  A consensus-notifications 0.1.0 (workspace, path 'state-sync/inter-component/consensus-notifications')
    * features: [none]

/canary

release binaries dependency change summary:
target packages:
  A consensus-notifications 0.1.0 (workspace, path 'state-sync/inter-component/consensus-notifications')
    * features: [none]

release binaries dependency change summary:
target packages:
  A consensus-notifications 0.1.0 (workspace, path 'state-sync/inter-component/consensus-notifications')
    * features: [none]

/canary

release binaries dependency change summary:
target packages:
  A consensus-notifications 0.1.0 (workspace, path 'state-sync/inter-component/consensus-notifications')
    * features: [none]

/canary

release binaries dependency change summary:
target packages:
  A consensus-notifications 0.1.0 (workspace, path 'state-sync/inter-component/consensus-notifications')
    * features: [none]

release binaries dependency change summary:
target packages:
  A consensus-notifications 0.1.0 (workspace, path 'state-sync/inter-component/consensus-notifications')
    * features: [none]

release binaries dependency change summary:
target packages:
  A consensus-notifications 0.1.0 (workspace, path 'state-sync/inter-component/consensus-notifications')
    * features: [none]

release binaries dependency change summary:
target packages:
  A consensus-notifications 0.1.0 (workspace, path 'state-sync/inter-component/consensus-notifications')
    * features: [none]


Add VolumeSnapshotContent APIs to snapshot pkg

Change Overview
Adds API support to operate on VolumeSnapshotContent.
Specifically, it adds a CreateContentFromSource and DeleteContent API.
This supports use cases where a namespaced VolumeSnapshot object
is not required.
Additional changes:

Return the snapshot class deletion policy from GetVolumeSnapshotClass
Modify Delete to also delete the underlying VolumeSnapshotContent.
This supports cases where the VolumeSnapshot is marked Retain
Fix a unit test bug which caused the test to fail on DigitalOcean (no
restore size set)

Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[ ] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[x] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test

Test Plan

[ ] :muscle: Manual
[x] :zap: Unit test
[ ] :green_heart: E2E

Little late but looks good.


CARDS-1807: Add support for specifying different selectors to use for serializing a subject's forms

CARDS-1807
To check:

in proms mode, create Patient Information and Visit Information forms for a patient/visit
PATIENT.data.dataOption:formSelectors=deep serializes all the answers for the Patient Information form, but does not list the visit subject
PATIENT.data.deep.dataOption:formSelectors= does not include answers, but includes the visit subject
PATIENT.data.deep includes both form answers and the visit subject

Setting different form selectors requires escaping the dot with %5C like:
/Subjects/41d2bbf3-54ff-42be-b44f-c85a470a7058.data.dataOption:descendantData=true.dataOption:formSelectors=-dereference%5C.deep.json.


Support FP8

Request description
I proposed an RFC for supporting FP8 to StableHLO and XLA. This issue tracks the effort to add the FP8 dtype to StableHLO.
/CC @burmako

Thank you for bringing this up! At the moment, we don't have a well-defined StableHLO RFC process (#196 is still in the works), so we might as well piggyback on the FP8 in XLA RFC in this case.
Once there is an outcome of the XLA RFC, let's come back to this issue and decide accordingly. As long as there is consensus, the actual changes in StableHLO are going to be easy - just add a new element type in the "Types" section of the spec and in the definition of HLO_Tensor in the dialect.

We have just landed support for f8E4M3FN and f8E5M2 element types in MHLO: https://github.com/tensorflow/mlir-hlo/commit/f9d277f903d20ca4a5af20c9088d9ce413d33dbc to start experimenting with FP8 support in XLA. Once/if the FP8 RFC is approved, we'll make a similar change to the StableHLO dialect.

The review period for the FP8 RFC has been extended to December 9. To quote @reedwm, "You are free to comment after that date but we may not be able to take into account your feedback. If there are no major objections to the design by that date, we will consider the RFC approved, otherwise we will schedule a design review meeting" (full comment).

The OpenXLA RFC has been approved yesterday. Will work on adding the corresponding FP8 types to StableHLO shortly.


Allow drawing menu at mouse position

Allows the radial menu to be drawn at the mouse position, instead of in the center of the node. Useful for large rectangular nodes or compound nodes.

Merged and published as 2.8.0

Thanks!


Detect open menu and blackout view

Hey,
What are some approaches that could be taken to blackout the current view controller when you open the menu?
I got this working when clicking the menu icon by just adding an overlay view to the topViewController and then removing it again when you close the menu. This doesn't work when using the default panGesture though which causes the view to be constantly blacked out.
Is there a simple way (I am missing) to detect that the menu is now open (or closed), not caring about how it happened?

Hi @slhodson969 , u can implement the delegate method of ECSlidingViewController from controller where need get the action:
`- (id)slidingViewController:(ECSlidingViewController *)slidingViewController
animationControllerForOperation:(ECSlidingViewControllerOperation)operation
topViewController:(UIViewController *)topViewController{
switch (operation) {
    case ECSlidingViewControllerOperationResetFromRight:
        NSLog(@"Menu Closed");
        break;
    case ECSlidingViewControllerOperationAnchorRight:
        NSLog(@"Menu Opened");
        break;
    default:
        break;
}
return nil;

}`
I hope it helps.


[SPARK-46798][Structured Streaming] Kafka custom partition location assignment (rack awareness)

This is rework of https://github.com/apache/spark/pull/44954
What changes were proposed in this pull request?
Add support for custom partition location assignment for Kafka sources in Structured Streaming.
Why are the changes needed?
Please see the design doc for greater detail and further discussion
SPARK-15406 Added Kafka consumer support to Spark Structured Streaming, but it did not add custom partition location assignment as a feature. The Structured Streaming Kafka consumer as it exists today evenly allocates Kafka topic partitions to executors without regard to Kafka broker rack information or executor location. This behavior can drive large cross-AZ networking costs in large deployments.
The design doc for SPARK-15406 described the ability to assign Kafka partitions to particular executors (a feature which would enable rack awareness), but it seems that feature was never implemented.
For DStreams users, there does seem to be a way to assign Kafka partitions to Spark executors in a custom fashion with LocationStrategies.PreferFixed, so this sort of functionality has a precedent.
Does this PR introduce any user-facing change?
An additional parameter will be accepted on the Kafka source provider. This parameter is provisionally named partitionlocationassigner. The parameter takes a class name, which when instantiated gives the Kafka source with user-provided Kafka partition location suggestions. The class should implement a new trait defined in this PR and described in the design document.
How was this patch tested?
Unit tests
Was this patch authored or co-authored using generative AI tooling?
No.

@rangadi tagging you here since you were in this conversation. Can you please review this PR?

@SubhamSinghal skimmed through. Overall I think this is a good direction.
Could you get reviews from your own team and spark-core person first? I like the idea from streaming point of view. FYI: @HeartSaVioR .

Thanks @rangadi. Not sure whom should I tag for spark-core, would you be able to tag relevant folks here?

Wow exactly what i was looking for. This is very beneficial on large deployments spanning across multiple AZs.
Really looking forward to see this feature in action.  @rschwagercharter @SubhamSinghal Awesome work!
Hoping it goes through all the way

I'll ask @nchammas since he's someone I know who is more of an insider here than I am. Who would be a good candidate from spark-core to take a look at this PR?

@HeartSaVioR - If you think this is a promising feature for Structured Streaming, could you take a look or tag another committer who is familiar with Kafka?

Whoops, I see Jungtaek was already pinged earlier. My apologies. Neil R. may instead take a look. (I happened to have a discussion with him offline. He will chime in here if/when appropriate.)

Yep, I'll help give this an initial review before we take Jungtaek's cycles.

@rschwagercharter @SubhamSinghal @neilramaswamy 🥇
Appreciating your effort on this issue - Any insight from your perspectives how to move on to promote that addition?

Kindly bumping this one again. Don't want to see it fall between the cracks after all the design and implementation contribution work @rschwagercharter have put into this :)
https://docs.google.com/document/d/1RoEk_mt8AUh9sTQZ1NfzIuuYKf1zx6BP1K3IlJ2b8iM/edit#heading=h.pbt6pdb2jt5c

Hi @unbalanced, I should be able to get to this in ~2-3 days. Please feel free to ping me again if I haven't reviewed by then.

@rschwagercharter, can you enable public comment-access on that doc? Or, at least, my email<EMAIL_ADDRESS>Thanks.

@rschwagercharter, can you enable public comment-access on that doc? Or, at least, my email<EMAIL_ADDRESS>Thanks.

Access granted @neilramaswamy. I've also opened up the doc for public comments.

@rschwagercharter - Thanks for the share.
@neilramaswamy - Kindly bumping this one again.

BTW, left a comment on that doc a few days ago in case you missed the notification from Google. The TLDR: I think that introducing imperative code here is a large enough change to raise some eyebrows from committers. They may even ask for a SPIP. We can continue the discussion on the doc or here.

Aha, I did miss that notification, so thanks for posting here as well. I'll continue that conversation on the doc.

@unbalanced Amazon could write their own plugin.  An example that comes to mind is the spark-sql connector for Kinesis. Plugins like this are often included as part of EMR, like the AWS glue extensions for Iceberg on Spark, but can often be added as a compile time dependency.
That said, I'm happy to write a first attempt at a plugin for AWS and host it on Github. My team at Charter would definitely see big cost savings, so the incentive would be fairly high. But, as mentioned above, I don't want to devote time to this effort and have it hung up because it's not done the way the spark community likes it to be done. So, I'm waiting on a spark community insider like @neilramaswamy to point the way forward.

@neilramaswamy can you please share your insight on how we should move on. Or could you point us at someone that can help finalize @rschwagercharter's contribution?

My guess is that Spark committers will likely raise some eyebrows over a design that prescribes an approach that requires users to write an imperative plugin (or rely on exclusively 3rd-party plugins). To be honest, I don't know the precedent here (for cloud-specific things), but that's just my guess. Let me ask some other Spark developers I know and see what they say.


Improve performance of health check and only perform it on hermes start

Closes: #1336
Description
This PR also adds a health-check command:
USAGE:
    hermes health-check <OPTIONS>

DESCRIPTION:
    Performs a health check of all chains in the the config

$ hermes health-check
Sep 16 21:54:03.360  INFO using default configuration from '/Users/coromac/.hermes/config.toml'
Sep 16 21:54:03.372  INFO [ibc-0] performing health check...
Sep 16 21:54:03.436  INFO [ibc-0] chain is healthy
Sep 16 21:54:03.437  INFO [ibc-1] performing health check...
Sep 16 21:54:03.443  INFO [ibc-1] chain is healthy
Success: performed health check for all chains in the config

For contributor use:

[x] Added a changelog entry, using unclog.
[ ] If applicable: Unit tests written, added test to CI.
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Updated relevant documentation (docs/) and code comments.
[ ] Re-reviewed Files changed in the Github PR explorer.

@romac the code lgtm. Couple of questions:
I've tested it with a config that has to chains (cosmoshub-4 and osmosis-1). In the cosmoshub chain config I deliberately set an invalid value for the max_tx_size but for osmosis is fine. So when running the command I see that the health-check errors out for one of them but not the other. Should this be a condition to fail to start the relayer or it's just for logging and an operator will have to check the log to identify an issue with the config?
hermes -c config.toml health-check
Sep 17 10:56:56.468  INFO [cosmoshub-4] performing health check...
Sep 17 10:56:56.829  WARN Hermes might be misconfigured for chain 'cosmoshub-4'
Sep 17 10:56:56.829  WARN     Reason:
   0: semantic config validation failed for option `max_tx_size` chain 'cosmoshub-4', reason: `max_tx_size` = 2097152 is greater than 90% of the genesis block param `max_size` = 200000

Location:
   /home/andy/.cargo/registry/src/github.com-1ecc6299db9ec823/flex-error-0.4.2/src/tracer_impl/eyre.rs:10

Backtrace omitted.
Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Sep 17 10:56:56.829  WARN     Some Hermes features may not work in this mode!
Sep 17 10:56:56.830 ERROR [cosmoshub-4] chain is unhealthy:
   0: semantic config validation failed for option `max_tx_size` chain 'cosmoshub-4', reason: `max_tx_size` = 2097152 is greater than 90% of the genesis block param `max_size` = 200000

Location:
   /home/andy/.cargo/registry/src/github.com-1ecc6299db9ec823/flex-error-0.4.2/src/tracer_impl/eyre.rs:10

Backtrace omitted.
Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Sep 17 10:56:56.833  INFO [osmosis-1] performing health check...
Sep 17 10:56:57.261  INFO [osmosis-1] chain is healthy
Success: performed health check for all chains in the config

Another question. Should the updated guide with the new command health-check be part of the PR ?

It's just for logging but I agree that we should clean up the log and not display the backtrace, just the error message.

Should the updated guide with the new command health-check be part of the PR ?

No, we currently do the guide updates in the release PR, because otherwise they show up before the feature is released. Hopefully once we have versioning we'll be able to do the guide updates in the PR directly.


Performing (SceneManager.GetActiveScene().name == SceneReference variable) returns false

putting the variable directly in a loadscene call works fine ex: SceneManager.LoadScene(scene) however when comparing using == returns false and using Debug.Log(scene) just outputs "SceneReference" in the console

nvm after looking through the script and a couple other issues I see that SceneReference only stores the path to the scene asset


Fix the unpivot test to correct behaviour of remove, Fix the data to align with it.

Remove expects an iterable,
wrapping values with a [] so that it doesn't list('value') by accident

Thanks @avishalom - I just kicked off the automated tests here

Closing in favor of @249


Memory requirements for 35000 cells (or more) and how to reduce them

Hello,
I am trying to run velocyto.py on the 10X aggregated output of 4 samples (>35.000 cells). I requested 400GB of memory and my job reached the memory limit after about 14h running. Is that expected for this number of cells? Is there anything I could do so that it requires less memory?
I will also mention that eventually I would like to run a 20 sample dataset of >140.000 cells.
Thanks in advance
Clara

Hi, if it's the case that bams sorted by cell barcode then by position, should the documentation for the CLI be updated to reflect this?
http://velocyto.org/velocyto.py/tutorial/cli.html#run-run-on-any-technique-advanced-use

Disregard, it appears that this has already been done
http://velocyto.org/velocyto.py/tutorial/cli.html#requirements-on-the-input-files

@lambdamoses - Would you mind posting how you did the sorting with samtools for your run10x please? Thank you so much.


man brew-cask is broken

Please follow the general troubleshooting steps first:

[x] Ran brew update and retried your prior step?
[x] Ran brew doctor, fixed as many issues as possible and retried your prior step?

Bug reports:
Since the integration of brew-cask into brew proper, man brew-cask does not work. This is because brew-cask.1 has moved:
scapeless:~ elyscape$ man brew-cask
No manual entry for brew-cask
scapeless:~ elyscape$ ls -l /usr/local/share/man/man1/brew-cask.1
lrwxr-xr-x  1 elyscape  admin  65 May 31 13:44 brew-cask.1@ -> ../../../Library/Taps/caskroom/homebrew-cask/man/man1/brew-cask.1
scapeless:~ elyscape$ ls -l /usr/local/Library/Taps/caskroom/homebrew-cask/man/man1/brew-cask.1
ls: /usr/local/Library/Taps/caskroom/homebrew-cask/man/man1/brew-cask.1: No such file or directory
scapeless:~ elyscape$ ls /usr/local/Library/Taps/caskroom/homebrew-cask/
CONDUCT.md           Gemfile.lock         ci/
CONTRIBUTING.md      LICENSE              developer/
Casks/               README.md            doc/
Gemfile              USAGE.md             tap_migrations.json
scapeless:~ elyscape$ find /usr/local -name 'brew-cask.1'
/usr/local/Library/Homebrew/cask/man/man1/brew-cask.1

Some code needs to be put in place to fix the brew-cask.1 symlink.

Fixed in https://github.com/Homebrew/brew/pull/768.


Fix unlinked note pins are invisible

Closes https://github.com/zeel01/pin-fixer/issues/11

Also closes #15


Invalid parameter custom_bin (launch_grpc)

After updating to pymapdl 0.59.2 I get some strange error message:
from ansys.mapdl.core import launch_mapdl

mapdl = launch_mapdl()

is causing an error:
TypeError: launch_grpc() got an unexpected keyword argument 'custom_bin'
which is caused by line 925 in launcher.py, as start_parm contains custom_bin:```
elif mode == 'grpc':
    port, actual_run_location = launch_grpc(port=port, verbose=verbose_mapdl,
                                            **start_parm)

interesting; I'll have a look at this

OK so it looks like there's a bit of a mix up.  This is actually fixed in the latest commits, but not in 0.59.2. I'm not sure why the changes didn't make it into the latest version.

The fix here is to either change the offending line and make a new release, or merge in main and do another release. I don't know which is more appropriate so I will leave that decision to @akaszynski for now, but this is an easy fix!

this is an easy fix!

True, but the bug is also a critical one. Maybe we should add an additional label "critical bug" ;) As far as I can see, pymapdl won't run for many users in the newest version, if they do not dare to mess inside the pymapdl source code. The reason why I didn't post a "solution" - I wasn't sure weather custom_bin is still meant to work, or if it wasn`t removed properly.

True, the fix is actually already in the master (now "main") branch, I'm more limited by not knowing how a release is done (yet). I'll find out as soon as Alex appears.
I've been thinking about making priority labels as well, so I'll go and do that now too

Pushing new release now.  ansys-mapdl-core==0.59.3 will be out in the hour.

Fixed https://pypi.org/project/ansys-mapdl-core/0.59.3/
Yanked 0.59.2.  Release got through CI/CD because we don't test the launcher in our CI/CD.


Made the security group an AWS deployment parameter

Before, when using the AWS deployment scripts (i.e. the Fabric-based ones), the security group was hard-wired to be "bigchaindb". This just makes it a parameter in the AWS deployment configuration file. This makes it easier to have a more secure security group, if you want one. I tried it and it works.

Current coverage is 92.47% (diff: 100%)

Merging #620 into master will not change coverage

@@             master       #620   diff @@
==========================================
  Files            22         22
  Lines          1209       1209
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1118       1118
  Misses           91         91
  Partials          0          0

Powered by Codecov. Last update 8fe034b...eff4446

:+1:


Download SVG / PNG does not include images / custom annotations

Description
When downloading a chart with the builtin "Download as SVG / PNG" feature custom images
(as seen in the official documentation: https://apexcharts.com/react-chart-demos/line-charts/line-chart-annotations/ )
are not included in the resulting image.
Steps to Reproduce
Try yourself in the official example: https://apexcharts.com/react-chart-demos/line-charts/line-chart-annotations/
download as png
instagram icon not included
Expected Behavior
include images
Screenshots
chart:

resulting png:

Reproduction Link
https://apexcharts.com/react-chart-demos/line-charts/line-chart-annotations/
Thanks for the awesome library!!

I am having the same issue :(

+1 - same issue

2 the same issue

+1

Has anyone found a solution to this?

+1

One workaround I have found is using data URIs directly instead of relying on file paths.
Here's an example of how you can do this:
annotations: {
  images: {
    path: 'data:image/svg+xml;base64,<YOUR_SVG_AS_BASE64>'
  }
}

Perhaps this could be solved in the apex library directly by converting these paths before initial rendering of the chart.

One workaround I have found is using data URIs directly instead of relying on file paths.
Here's an example of how you can do this:
annotations: {
  images: {
    path: 'data:image/svg+xml;base64,<YOUR_SVG_AS_BASE64>'
  }
}

Perhaps this could be solved in the apex library directly by converting these paths before initial rendering of the chart.

Thank you so much! This worked for me with PNG images!


password book

Description of the new feature / enhancement
Add a function to manage user names and passwords, and have one click to generate random passwords and save the function.
Scenario when this would be used?
When creating an account, use shortcut keys to quickly generate a password, save the password to the database, record the current focused application, and associate the password with the application.
When the app is logged in, enter the password through the shortcut key, and if there are multiple passwords, list the options.
Supporting information
No response

can use this?
https://keepass.info/

Yes, this software is similar to my request, I would like to keep in:
Save user name
Password New password
These two functions also add shortcut keys to make it easier to create and enter passwords.

No plans for powertoys to do this. Microsoft authentication app can do this as well as many others.


Required and optional dependencies should be clarified in the documentation

This is related to openjournals/joss-reviews#565
Although the dependencies are documented in setup.py, the purpose of all of them is not very clear, and the format may not be familiar to users who have not seen a setup.py file before. The dependencies and the features they enable should be clarified in the documentation.

I tried to elaborate on this here, what do you think, is it too terse? I can of course be more detailed.

This seems fine to me!


adds jsdoc to typescript for type alias declarations for types number and bigint

closed in favor of https://github.com/xddq/ts2typebox/pull/9


ᴵᵗ ʷᵃˢⁿ'ᵗ

should be all good to go !

Thanks @AnthonyLenglet 😄 Happy to drop features


Only check mainnet node on tests once

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2664

Relevant Lines:
2916

💛  - Coveralls


🐛 [birdnet-pi] build failed

Description
The latest build https://github.com/alexbelgium/hassio-addons/actions/runs/11541358429 failed, can't install addon due to missing manifest
Reproduction steps
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Addon Logs
https://github.com/alexbelgium/hassio-addons/actions/runs/11541358429

Architecture
amd64
OS
HAos

Thanks ! I'll look at it. It is a quite minor version : it just incorporates the latest upstream changes including the backup feature (not needed in HA)

New version pushed! BTW for info I'm not building anymore from Nachtzuster's branch directly but from a fork where I have listed here the additional elements : https://github.com/alexbelgium/BirdNET-Pi/blob/main/README.md
It is however fully compatible

I'll try another approach

Mmh not working too

All good now!


Issues with importing keras_nlp

A lot of my friends were trying out your notebook, and faced a common problem when importing keras_nlp. Often stating circular importing as a problem. The fix to this is as follows:

!pip uninstall keras keras-core keras-nlp
!pip install keras==2.15.0 keras-core==0.1.7 keras-nlp==0.6.3
Restart the session

Maybe we can add it as a comment in the notebook.

Thanks for letting me know. I think it is due to Keras V3 and V2 conflict issue. We can install them correctly by
!pip install —upgrade keras_nlp tensorflow
!pip install —upgrade keras

I'll add it on the code soon


⚠ Bofrost.at has degraded performance

In a34efdc, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1658 ms

Resolved: Bofrost.at performance has improved in 800e638.


[WIP] Upgrade AutocompleteJS to v1 & update related code (Top Navigation Desktop Only)

Summary of changes

Asana Ticket: Upgrade AutocompleteJS to v1 & update related code (Top Navigation Desktop Only)
When I initially worked on this ticket I wanted to use this upgrade task as a chance to rewrite the current OOP-driven mass of undocumented v0 AutocompleteJS vanilla JavaScript code to a cleaner, typed, documented structure that could also support any of our current types of search. I wrote some observations on how the searching-with-autocomplete experience works slightly differently in different parts of the website. But I ran out of time. :)
While most of the code to support location, project, and other searches is in fact implemented here, in terms of the UI, this PR only updates the top navigation bar search bar.

I am trying not to change the UI here, so I've re-skinned a default theme to match.
There are various known outstanding issues outlined here.

General checks

[x] Are the changes organized into self-contained commits with descriptive and well-formatted commit messages? This is a good practice that can facilitate easier reviews.
[ ] Testing. Do the changes include relevant passing updates to tests? This includes updating screenshots. Preferably tests are run locally to verify that there are no test failures created by these changes, before opening a PR.
[x] Tech debt. Have you checked for tech debt you can address in the area you're working in? This can be a good time to address small issues, or create Asana tickets for larger issues.

New UI, or substantial UI changes

[ ] Cross-browser compatibility is less of an issue now that we're no longer supporting IE, but changes still need to work as expected in Safari, Chrome, and Firefox.
[ ] Are interactive elements accessible? This includes at minimum having relevant keyboard interactions and visible focus, but can also include verification with screen reader testing.
[ ] Other accessibility checks such as sufficient color constrast, or whether the layout holds up at 200% zoom level.

New endpoints, or non-trivial changes to current endpoints

[ ] Have we load-tested any new pages or internal API endpoints that will receive significant traffic? See load testing docs
[ ] If this change involves routes, does it work correctly with pertinent "unusual" routes such as the combined Green Line, Silver Line, Foxboro commuter rail, and single-direction bus routes like the 170?

Replaced by #1781


Massive refactor of Repo management

@paetling The various functions for managing Dusty's idea of what a "repo" is were getting out of hand. I've consolidated all of that functionality into a class. This broke basically the entire app.
Plan:

Get this massive thing merged and hopefully don't break the entire app
Write some tests for the Repo class
Usability / consistency improvements around how things are calling this. We have a mix of "passing the repo path" and "passing the Repo object" right now.

good prioritization, all #1.

Also, Where are we passing repo objects around in the old code?

Repo objects don't exist in the old code, I changed some places to pass around objects but we are definitely still passing strings around in other places. We should standardize on objects.

@nrschultz MARKDOWN HAS FAILED ME

You said in your pr comment that in the old code (prior to this pr) we were passing around repo objects: Usability / consistency improvements around how things are calling this. We have a mix of "passing the repo path" and "passing the Repo object" right now.  I just do not see where that is happening?

"right now" meant "once this PR is merged"

ohh.  ok.

pr seems fine. like the standardization


how i can add mixins

i want to create mixins
https://vuejs.org/v2/guide/mixins.html
how i can add them, i try creating a folder, "mixins" and create a mixin "ExamleMixin"
when i import it into component i got error.
import ExamleMixin from '../../mixins/ExamleMixin'
it give me error
Module not found: Error: Can't resolve  '../../mixins/ExamleMixin'
i check with path and stuff its fine.
can anyone give me a example
thanks in adv

Use:
import ExamleMixin from '~/mixins/ExamleMixin'

@cretueusebiu buddy i try this, but
i found this
To install it, you can run: npm install --save ~/mixins/ExamleMixin


[Functions] Remove strong dependency on azure-functions-java-library

cc @soninaren
Right now any updates to annotations even adding new properties to existing annotations  require updating maven plugin
For example,  CosmosDBBinding.java is a copy of
CosmosDBTrigger.java.
Need to decouple library and plugin dependency. All the information needed for plugin should be coming from azure-functions-java-library

@jdneo / @Flanker32  Lets discuss this post GA.

@pragnagopa @jdneo Refactor done in pr #508, please have a review.
In this pr, i remove other binding classes except BaseBinding, attributes was get by java reflect and save to the map of Basebinding, i will get all attributes defined in annotation and save attributes which is different with its default value, besides, a serializer was created to keep the format of generated function.json.
For now adding new properties to existing annotations will not affect maven plugin, but remove an existing annotations will still not work. I store the type and direction of annotations in BindingEnum and save the relevance in BindingFactory, which import all annotations from java lib.
@pragnagopa

Is there any other way for us to get the type and direction of each annotation? If so, we could decouping the dependency between function lib and maven plugin.
Could you please update the function.json scheme? Schema could be much helpful in local validation and users could verify and update their code according to schema as well

https://github.com/Azure/azure-functions-java-library/issues/69


feat: port AlgebraicTopology.SimplexCategory

[x] depends on: #3266
[x] depends on: #3268
[x] depends on: #3281
[x] depends on: #3282

Introducing two lemmas Fin.ite_val and Fin.dite_val, the simplicial relations are now obtained in a slightly cleaner way as compared to mathlib. Everything is translated into equalities of natural numbers on a case by case basis using split_ifs, simp and linarith.

This PR/issue depends on:

leanprover-community/mathlib4#3266
leanprover-community/mathlib4#3268
leanprover-community/mathlib4#3281
leanprover-community/mathlib4#3282
By Dependent Issues (🤖). Happy coding!

This PR/issue depends on:

leanprover-community/mathlib4#3266
leanprover-community/mathlib4#3268
leanprover-community/mathlib4#3281
leanprover-community/mathlib4#3282
By Dependent Issues (🤖). Happy coding!

bors r+


Move fsnotify constraint to proper place

This is a follow-up of https://github.com/elm-lang/elm-platform/pull/73.
The constraint needs to be enforced already when installing the dependencies. Doing it later, when elm-reactor is built, is too late.

Makes sense, thanks!


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Make FlashNotification appear above Modal backdrop

Fixes #2188.
Increases the z-index of FlashNotification component so it's slightly above the Modal backdrop's z-index.

Fixed already


Improve identification of OpenSSL install root

This PR makes it easier to specify a custom install prefix for OpenSSL. Additionally, if there exists an OpenSSL installation from Homebrew on macOS, we'll try to use it by default.

Just a small note, because I was looking through this project and have had an issue with this previously: A more reliable and future-proof way to get the installation directory from Homebrew is to run the shell command brew --prefix openssl, which will return /usr/local/opt/openssl for 99.9% of installations.

Thanks for sharing your insight. Imho this is enough of a corner case that it does not warrant shelling out. The workaround added here covers most users, but we should not try to be exhaustive here. If we want to make every homebrew user happy, then we should think about macports too. Otoh, requiring -DOPENSSL_ROOT_DIR= is acceptable.


Implementation of data structure verification

Included is the complete implementation of both the one-dimensional
list and Merkle tree data structures (with both single leaf and all-leaf
verification for the Merkle tree structure).
The result of gas testing shows the following figures, for a list of 8
items:
i. verifyMessageArray (all items verified): 28505
ii. verifyMerkleAll: 29728
iii. verifyMerkleLeaf: 25423

Nice, thanks!
Could you run the gas estimates again and add numbers into a table for the following message counts please?
1, 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, 8192
That would be amazing.


gather addon configs and klusterlet configs

/cc @xuezhaojun

/hold
Merge after KlusterletConfig onboarded.

/unhold

Hi @dislbenn Please help take a review

/lgtm


Update and reorganize the README

@bugarela and I have paired on this PR to give the README a face lift.
We've...

streamlined the content
put in a fancier heading with navigation-like links
moved some stuff into other files
added an acknowledgement section
put in place a fun (temporary!) holiday example

Note:

The example will be replaced with something more distsys oriented (probably more succinct too) after the new year
The logo will be tweaked shortly

See the rendered README at https://github.com/informalsystems/quint/blob/707d80d1ddb6b91a67bcd1c4d587f72e92f6cf56/README.md

That was slightly jarring to me too. Now that you mention it, let's do add a section with a couple lines and a link, that way people don't get disoriented if they still want to be exploring the reader. I can add that in this evening.

Thanks all for the great reviews!
@bugarela :raised_hands:


Doubt

Description
Is this a brand new web application or do you guys implement something into cause when I cloned it . I am seeing a clean project with default screen.. I am new to open source and want to contribute.
Screenshots
No response

By clean project you mean no issues and pull requests are showing?

Yes it is going to be a brand new web app

yeah ok I got it just pushed my PR for the first time in the project .. let's see what happen


Google HTML tags issue

Hi,
Great tool, but I am having a small problem. I read, and it seems that Google has plain text and HTML formats. The default should be HTML. However, when I include
 for example, the translation returns "u003cbr/u003e". Here is my code:
foreach($parentCollection as $parentID) {     $parentProducts = Mage::getModel( 'catalog/product' )->load( $parentID->getId() );     $sku = $parentProducts->getSku();     $description_en = $parentProducts->getDescription();     $description_bg = shell_exec("translate/trans -b -e google \"$description_en\" :bg");     fputcsv($fp, array($sku, $description_en, $description_bg), ",");
Is there a workaround? Is there a setting I need to specify in regard to the HTML default support. Please advise! Thank you again for a wonderful translate tool!

I don't understand what your problem is.

I am sorry for the confusion. I appreciate your fast reply. Here is an example:

./trans -e google -b  en:bg "word"
u003cbru003e дума u003c / BR u003e

However, when using bing, there's no problem:

./trans -e bing -b en:bg "word"
думата

As you can see, when using Google, the translated text breaks the proper tagging. Moreover, sometimes, the text inside the tag (e.g. br) gets translated (as if it says not "br" but "bra"). Instead of getting

I get

u003c / BR u003e

Or I could also get this translated to, for example:

u003cbru003e u003c / сутиен u003e (like

I am sorry if I am not explaining this good enough. Let me know if you need more details.

Right now I am using quite the sed one-liner to replace strange tag occurrences:
sed -i -e 's/u003e/>/g' -e 's/u003c/</g' -e 's/< сутиен/<br/g' -e 's/& Nbsp/&nbsp/g' -e 's/< Бар \/ >/
/g' -e 's/< Се \/ >/
/g' -e 's/< Бъде \/ >/
/g' -e 's/< От \/ >/
/g' -e 's/< Бар >/
/g' -e 's/< Сутиен \/ >/
/g' -e 's/< примки Br\//
/g' -e 's/< Брато \/ >/
/g' -e 's/< бар \/ >/
/g' -e 's/<Бразилски \/  >/
/g' -e 's/< примки Br2 колан/
/g' -e 's/<Бразилски.  \/ >/
/g' -e 's/<Бразилски/
/g'
However, I would really appreciate it if the problem could be fixed somehow.
Thanks!

Thanks for your explanation in details. Short answer: Unlike Bing Translator, Google Translate API returns escaped Unicode (\u003c) instead of literal chars (<), thus those mysterious "u"-strings appear. Unfortunately AWK has no built-in method to convert between escaped Unicode characters and literal chars (because it's such an old-fashioned language), so there's no easy workaround on this without calling an external program.
I would suggest not trying to directly translate HTML tags via Google Translate; in most cases they're not even semantically valid. But for sure, this issue needs to be fixed anyway.

Regarding HTML tags: this is fixed by 1030f05, though general Unicode char escaping is not implemented.

I use the self-contained executable. The issue with < and > still exists there. Will that be updated too, or should I install the program the other way?

I use the self-contained executable ./trans. The issue with < and > still exists there. Will that be updated too, or should I install the program the other way?

Please report your ./trans -V.

It was 0.9.5. I updated it after your last reply, but it seems that I did it too soon. Thank you! Using 0.9.6 now, the problem no longer occurs.

Hello, I has been fixed for "<" and ">". Nice. But there is the same issue with "=" sign.
$  trans -b :en "ceci est un = texte < >"
this is a u003d text < >

Here is my version
$ trans -V
Translate Shell       <IP_ADDRESS>

platform              Linux
terminal type         xterm-256color
bi-di emulator        [N/A]
gawk (GNU Awk)        5.0.1
fribidi (GNU FriBidi) 1.0.8
audio player          [NOT INSTALLED]
terminal pager        less
web browser           xdg-open
user locale           C.UTF-8 (Emoji)
home language         emj
source language       auto
target language       emj
translation engine    google
proxy                 [NONE]
user-agent            Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/602.1 (KHTML, like Gecko) Version/8.0 Safari/602.1 Epiphany/3.18.2
ip version            [DEFAULT]
theme                 default
init file             [NONE]

This was reported in #429 and #420, fixed by d3e0836146addb62ba7b1b18e7bc17766460d5c3 (currently available only in develop branch).


Update GitHub Stats Project Links

Pull Request
TL;DR
Write a short description of the changes made in this pull request.
What changed?
List important changes here. Changes within a file should be an indented bullet point.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#35  👈
#34
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @JackPlowman and the rest of your teammates on  Graphite

Merge activity

Oct 4, 3:32 AM EDT: @JackPlowman merged this pull request with Graphite.


fixed bug with double negated preconditions. We now simplify the theory

This fixes the following bug:

into:

Please check if this is the correct transformation. Note that the original was negating the AND formula, so the precondition became OR of some double negated fluents, which then were handled incorrectly by the planner.

Can you clarify -- was the original incorrect, or just not handled by the planner you were using?

Read through the change -- not sure this works semantically. We want to negate the other precondition, and if it's a conjunction, that means indeed it turns into a disjunction. Without doing that, you're essentially saying that it's a failed action only if you can violate all of the domain2 preconditions for the action while satisfying all of the domain1 preconditions. We'd rather want to violate just one of the domain2 preconditions while satisfying the domain preconditions.
That make sense?

I tried to use the lor formula, but then tarksi would print it into an action embedding an or connective between each term, which defeats the purpose.
In the latest commit, I ended up adding a failed action for each precondition, by negating only one precondition at a time. This indicates exactly which precondition is triggering the error.

It may be that the original encoding was correct, but I couldn't understand which precondition was failing. Now I do :)

On a different note, many alignments fail due to students submissions being parsed well by the online solver but not by Tarski. We need to find a workaround to this exposing this as an autograder so they can make sure their model works well with Tarski too.

In the latest commit, I ended up adding a failed action for each precondition, by negating only one precondition at a time. This indicates exactly which precondition is triggering the error.

Very compelling. But I'm a bit torn. To truly know what's wrong, that's the best approach. To just give students a hint (e.g., in running a validation on a webserver where they don't get to see the reference domain being used), then perhaps it's too much info. Ultimately, having the choice might get us the best of both worlds. Two requests if you're up for it:

Make it a cmd-line option to go with the original mode (negate it all) -vs- the split mode (negate each precond and use multiple actions).
Put in the assertions required to ensure the approach is operating only on domains that make sense. If I have an arbitrary nesting, or an or in the preconditions, or whatever, then it will fail silently (I think?). Using the original planner handles these cases, so the check only needs to be there for the "split" option.

On a different note, many alignments fail due to students submissions being parsed well by the online solver but not by Tarski. We need to find a workaround to this exposing this as an autograder so they can make sure their model works well with Tarski too.

Ya, this is a major problem. I've kind of conceded to not solving it since I need to move to a different style of assessment for the course:

Many low-stakes instant-feedback assignments
Higher-stakes quizzes (from 2 to 3)
The p4pp will be hosted, and validation against the reference will be provided as instant feedback

Hosting seems like a good move to allow testing against Tarski and continuous feedback while developing their models.

Big-time agree. Think you can tackle 1+2 above? I'll get it server-wrapped for us from there (will be needed early 2023).

@nirlipo Any chance you'd like to make a move on the above? In the meantime, I've started picking away at the server setup...


Remove temporary files created by the fromUrl method

Running textract.fromUrl on Linux creates temporary files which are not removed after use. With extensive use, the /tmp folder can get filled up and might cause problems.

No response from the code owner. Closing PR.


Remark Lint escapes underscores in emoji

Running remark lint with the default configuration escapes underscores in GitHub-style emoji, e.g., :heavy_check_mark: .
Turning on pedantic mode, replaces the underscores with the emphasis character, e.g., :heavy*check*mark:.
Steps to reproduce:

Create a markdown file with :heavy_check_mark:
remark example.md -u remark-lint --output

Expected
File contains  :heavy_check_mark:
Actual
File contains  :heavy\_check\_mark:

Hey @benbalter, thanks for raising this issue, and the detail you put
into it :+1:
First, some background. remark
does the markdown parser. It can receive options, for example gfm, which
turns on support for tables and strikethrough, which is on by default,
and pedantic, which turns off some features available in most modern
markdown implementations, which is off by default.
remark-lint, on the other hand, is a plug-in working with remark
to highlight possible style violations or mistakes in markdown.
So, when you’re talking about “escapes” in the provided code, you’re
talking about remark (as that’s what generates the code).
A quick solution might be to turn off pedantic mode. I’m not sure if
that’s possible, but there’s often no need to use it. This would ensure
the underscores in “words” are not seen as emphasis.
Another alternative, which is kind-of hacky, is to set
emphasis: '_'.
A solution which is in the works is support through
remark-gemoji, but that
project is still in the works. What it does is turn :+1: into 👍.
We’re still figuring out what’s needed, and from your code (I see you’re
using remark for your site)
It seems like you just want gemoji shortcode detection, or do you also
want to render as (unicode) emoji, or to HTML images? Could you tell me?

Wow. @wooorm thanks for all the context. Suspected it might have been in remark, but wasn't sure the best place to start. Should I open an issue over on remark?

A quick solution might be to turn off pedantic mode. I’m not sure if
that’s possible, but there’s often no need to use it. This would ensure
the underscores in “words” are not seen as emphasis.

Turning off pedantic mode is what currently escapes the underscores. Turning it on, replaces whatever the emphasis character is, meaning, you can't have * for emphasis and use GitHub-style emoji. You can see my .remarkrc file here.

A solution which is in the works is support through
remark-gemoji, but that
project is still in the works. What it does is turn :+1: into 👍.
We’re still figuring out what’s needed, and from your code (I see you’re
using remark for your site)
It seems like you just want gemoji shortcode detection, or do you also
want to render as (unicode) emoji, or to HTML images? Could you tell me?

I saw remark-gemoji (my first attempt at a fix), but ideally, I'd like to keep the shortcodes in the markdown after linting (with the output flag set to true).
If this is a crazy edge case you don't want to support (or I'm doing something terribly wrong), feel free to let me know. Really liking using Remark to fix my Markdown (the primary way I write these days). :smile:

Should I open an issue over on remark?

You can keep it here, for now, I’ll open things in the correct places :)

Turning off pedantic mode is what currently escapes the underscores.

You’re right, that wouldn’t work indeed. Sorry!

ideally, I'd like to keep the shortcodes in the markdown after linting

OK, that sounds like a good use case, not at all edge case. I’ll coordinate with the creator of remark-gemoji to finish that project in a way that also enables authors to keep gemoji shortcuts into their documents.
For now, unfortunately, the only way to keep your gemoji shortcuts in place, would be to turn off the --output setting.

Really liking using Remark to fix my Markdown

Thanks, @benbalter, great to hear. Feel free to raise issues or ask me questions. You’re running remark over a huge amount of files, so there’s bound to be some problems, and I’d love to hear your experience and the things you run into.

If it helps, it appears to be more than just emoji, but any word with a mid-word-underscore (e.g., civic_hackers (possibly including those in code blocks as well, but I can't seem to recreate it).

code (in ticks) shouldn’t have this problem (as it doesn’t need escaping inside), but please share if you find an example of this!

Hey @benbalter, thanks for waiting.
I just pushed<EMAIL_ADDRESS>which  contains a fix for the escaping of underscores in words. But only when not in pedantic mode!.
This also includes your example of sinatra_auth_github > sinatra\_auth\_github, which now doesn’t cause escapes.
So, could you update to<EMAIL_ADDRESS>turn off pedantic mode, and let me know if that fixes your problems?

@wooorm :sparkles: That looks like it did it. Thanks again for an awesome project.

Great, good to hear! :)


propSetFriction is not working

Can't really understand why. Plus propGetFriction also acts weird

It only works on npcs.

Thank you


lwm2m: send_attempts field does not seem to be used?

Zephyr version: 2.6.0
Just grepped for send_attempts and it does not seem to be used anywhere. Just incremented. client.retries is checked, but not send_attempts. I am not sure if this 100% means retransmits are borked, but that does feel like a possibility :)

@tautologyclub You're referencing outdated code - send_attempts field was removed a few months ago, as being unused, the retransmission logic is based on retry field from struct coap_pending (https://github.com/zephyrproject-rtos/zephyr/blob/main/subsys/net/lib/lwm2m/lwm2m_engine.c#L4133). Works with no issue with recent master.

Retransmission logic on 2.6.0 works fine as well on my side.


How should electron build be handled?

I noticed in the package.json there does not seem to be any reference to actually packaging up electron builds for distribution.
I am currently trying to wire something up using electron-builder but wondered if there was something I was missing?
Cheers.

You can use electron-builder, maybe we should add it to package.json later

Have been doing a bit of digging, might even submit a PR if I can get it going nicely but the current directory structure will require 2 package.json's see this issue for what I am talking about.
Do you think it would be worth a re-structure or just dropping in a temporary one for now?

Yep, I think 2-package.json structure is good, I use this structure everywhere too. We can put a package.json inside ./app

Okay sweet as I will keep playing with this, and see if I can get something working nicely.

Pretty new to this stuff, is there any sample flow/package.json to for the app directory on how to compile a working app with electron-builder? I'm currently trying:
{
  "name": "appname",
  "version": "0.0.0",
  "author": "someone",
  "description": "something",
  "devDependencies": {
    "electron-builder": "^17.0.3",
    "electron-prebuilt": "^1.4.13"
  },
  "build": {
    "appId": "xyz.entity.some"
  },
  "scripts": {
    "postinstall": "install-app-deps",
    "pack": "build --dir",
    "build": "build"
  }
}

This creates a executable AppImage (and "linux-unpacked" folder) in the dist directoy, but when I try to execute it the following error is raised:
Error: Cannot find module '../build/config'


set default value & media link

set media title & alt based on filename
create media link when showing media info

thank!


CTIMS mechanism to validate existing CTML files - investigation

For CTIMS users, a process is needed to validate existing CTML files.
Many CTML files have been created manually. These need to be validated against the CTIMS schema for CTML.
Investigate options for achieving this goal:
API
Upload from CTIMS GUI
others.

one option to consider is https://github.com/23andMe/Yamale - open source python framework


L8 band name allocation is wrong

Just a comment, I found a mistake in the band rename sequence for Landsat 8, this affects indices retrievals.

Thank you for checking the code and bringing up this issue! Just to clarify, is this the line in question? https://github.com/yanghuikang/Landsat-LAI/blob/795779b1e7f4159fcab869b1e4453a5639ca8848/scripts/ee_Landsat_LAI_export_v0.1.1.py#L85
It seems to be working correctly, as ".compare()" returns 0 when the strings are identical. Just tested the code and the output looked alright.
Please feel free to let me know if I misunderstood your concern or if there are any further issues!


UI test：logout my electron app，app launch login page and app cannot quit

UI test：
1.logout my electron app，app launch to login page and app out of control
this code does not work:
if(this.app && this.app.isRunning())
{return this.app.stop();}

Have you tried putting code inside 'aftereach' ?

My problem has been solved. thank you ！


⚠ ClamAV has degraded performance

In a971e20, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 217 ms

Resolved: ClamAV performance has improved in 3122663.


fix(base-modal): add prop to allow the modal to move the focus to an element within it on open

EX-6755
Motivation and context
When opening modals (namely the MyHistory one) the focus could still be behind the modal, which is weird.
Type of change

[X] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that causes existing functionality to not work as expected)
[ ] Change requires a documentation update

What is the destination branch of this PR?

[X] Main
[ ] Other. Specify:

How has this been tested?
There are new unit tests for the new prop in the base-modal component.

good job!