Make the tool cross platform (for MacOS, Linux, etc)

This simply replaces the hard coded windows paths (//) with proper cross-platform os.path.join invocations, e.g.
before
file_interface = os.path.join(root_path + "\\Assets\\GUI\\shaderConv.ui")

after
file_interface = os.path.join(root_path, "Assets", "GUI", "shaderConv.ui")

I am not sure why Github is showing the diff as so large. Perhaps it's because I edited the file on Linux whereas it was created on Windows.

Hi, Thanks very much for your interest and contribution. I was actually planning a refactor for this tool, The codebase is not at all up to standard. I would like to simplify this and maybe add more functionality.

Hi @SideswipeeZ you approved the change but you never merged it. Currently the tool doesn't work on Mac / Windows (unless you did some other change I'm not aware of).

Hi @SideswipeeZ you approved the change but you never merged it. Currently the tool doesn't work on Mac / Windows (unless you did some other change I'm not aware of).

Im not the one who approved this MR But ive merged it. If i get time ill refactor this whole codebase to clean it up to modern standard.


Still waiting for Handoff for Segments

Hi,
i am new in druid, and i have problem with running jobs, they newer finished if i run middlemanager on another host from all other services.
I have setup "distributed" cluster, it means i have run overlord,broker,historical and coordinator on same host, middleManager and tranquility on another. Also as deep storage i have used local storage (maybe problem here, i don't know) .
nothing strange in all logs, but when i open task log i see this message
2016-09-19T06:38:17,178 INFO [coordinator_handoff_scheduled_0] com.metamx.http.client.pool.ChannelResourceFactory - Generating: http://<IP_ADDRESS>:8081 2016-09-19T06:38:17,188 INFO [coordinator_handoff_scheduled_0] io.druid.segment.realtime.plumber.CoordinatorBasedSegmentHandoffNotifier - Still waiting for Handoff for Segments : [[SegmentDescriptor{interval=2016-09-19T04:00:00.000Z/2016-09-19T05:00:00.000Z, version='2016-09-19T06:05:27.854Z', partitionNumber=0}]]
or this message
2016-09-19T06:46:53,090 INFO [topic7-kafka-incremental-persist] io.druid.segment.ReferenceCountingSegment - Closing topic7-kafka_2016-09-19T06:00:00.000Z_2016-09-19T07:00:00.000Z_2016-09-19T06:06:53.047Z 2016-09-19T06:46:53,090 INFO [topic7-kafka-incremental-persist] io.druid.segment.ReferenceCountingSegment - Closing topic7-kafka_2016-09-19T06:00:00.000Z_2016-09-19T07:00:00.000Z_2016-09-19T06:06:53.047Z, numReferences: 0
strange things start here, i can see written data in caravel
user   count alice	   91955.0 bob	   91955.0 chist    91955.0
can somebody explain why my jobs when they running on host with all other services completes with SUCCESS, but when i running two different host they have never finished?
common.runtime.properties.txt
kafka.json.txt
runtime.properties.broker.txt
runtime.properties.coordinator.txt
runtime.properties.historical.txt
runtime.properties.middlemanager.txt
runtime.properties.overlord.txt

Fwiw, in clustered mode, deep storage needs to be configured to a distributed file system which is accessible by all the druid nodes. try changing your deep storage to hdfs or s3.

nishantmonu51, thank you for explain.
I have create user for druid, user for hdfs, copy all *-site.xml files to _common/, add hdfs storage path to my config files, and starting druid under druid user. Now, i have working "cluster" with two middlemanager and historical nodes.

I believe you need not restart your middlemanagers, It should get picked up for the new tasks since each task is a separate VM.
To make things more cleaner, You can also use the classpathPrefix property in the task and have versioned configs for your directoryStructure.
e.g. you can have a directory structure hadoopConfigs/v1 and when you make a change create a new directory hadoopConfigs/v2. and point new tasks to use the new classpath by setting classpathPrefix to hadoopConfigs/v2.

nishantmonu51 , thanks.


Update on custom data channels documentation

Docs Build status updates of commit 10ff868:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/holographic-remoting-create-player.md
:warning:Warning
View
Details

mixed-reality-docs/holographic-remoting-troubleshooting.md
:warning:Warning
View
Details

mixed-reality-docs/TOC.md
:white_check_mark:Succeeded

mixed-reality-docs/holographic-remoting-create-host-hl1.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-create-host.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-custom-data-channels.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-player.md
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-secure-connection.md
:white_check_mark:Succeeded
View

mixed-reality-docs/images/holographicremotingplayer-diag.png
:white_check_mark:Succeeded
View

mixed-reality-docs/images/holographicremotingplayer.png
:white_check_mark:Succeeded
View

mixed-reality-docs/holographic-remoting-create-player.md

Line 4: [Warning] Invalid value for author: 'nopohl' is not a valid GitHub ID
Line 160: [Warning] Text in the first line of Note/Section/Video is not valid. Will be rendererd to <blockquote>

mixed-reality-docs/holographic-remoting-troubleshooting.md

Line 4: [Warning] Invalid value for author: 'FlorianBagar' is not a valid GitHub ID

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


cvc5: 1.1.1 -> 1.1.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/cvc5/cvc5/releases.
meta.description for cvc5 is: A high-performance theorem prover and SMT solver
meta.homepage for cvc5 is: https://cvc5.github.io
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.2 with grep in /nix/store/4rqh6i8jcscnhg4842nk3aph46rb5csh-cvc5-1.1.2
found 1.1.2 in filename of file in /nix/store/4rqh6i8jcscnhg4842nk3aph46rb5csh-cvc5-1.1.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
cvc5

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4rqh6i8jcscnhg4842nk3aph46rb5csh-cvc5-1.1.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cvc5 https://github.com/r-ryantm/nixpkgs/archive/b4acd43269a29ee8f51db5841b35575a3f6564aa.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b4acd43269a29ee8f51db5841b35575a3f6564aa#cvc5

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4rqh6i8jcscnhg4842nk3aph46rb5csh-cvc5-1.1.2
ls -la /nix/store/4rqh6i8jcscnhg4842nk3aph46rb5csh-cvc5-1.1.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

cvc5

Maintainer pings
cc @shadaj for testing.

@wegank After this update, running cvc5 failed with error /nix/store/h5k9rqqwfkl416g7swzki574n2ph1br4-cvc5-1.1.2/bin/cvc5: symbol lookup error: /nix/store/h5k9rqqwfkl416g7swzki574n2ph1br4-cvc5-1.1.2/bin/cvc5: undefined symbol: _ZTIN4cvc56parser3CmdE.

That doesn't happen on my side. Are you running NixOS 23.11 or unstable?
$ /nix/store/h5k9rqqwfkl416g7swzki574n2ph1br4-cvc5-1.1.2/bin/cvc5
cvc5 1.1.2 assertions:off

Copyright (c) 2009-2023 by the authors and their institutional
affiliations listed at https://cvc5.github.io/people.html

That doesn't happen on my side. Are you running NixOS 23.11 or unstable?
$ /nix/store/h5k9rqqwfkl416g7swzki574n2ph1br4-cvc5-1.1.2/bin/cvc5
cvc5 1.1.2 assertions:off

Copyright (c) 2009-2023 by the authors and their institutional
affiliations listed at https://cvc5.github.io/people.html

...

I'm running unstable.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

stale pull request


Returned Self expanded to AsyncTrait?

G'Day!
I'm having an issue using futures::StreamExt and friends. I think the issue I have is due to the expanded macro having
Context
I'm deserialising objects from a DB. The method in my example returns a collection of itself Vec<Self> The macro expansion seems to turn this into Vec<AsyncTrait>. I included the error at the bottom even though I don't think its quite relevant. What is more relevant is the macro expansion.
Code
#[async_trait]
pub trait Db<'a>: Send + Sized + Deserialize<'static> + 'static {
    const COLLECTION: &'static str;

    async fn all(db: &'a Database) -> Vec<Self> {
        db.collection(Self::COLLECTION)
            .find(None, None)
            .await
            .unwrap()
            .filter_map(|item| async move { item.ok() })
            .map(|doc| async move { bson::from_document(doc).expect("Decode error") })
            .collect()
            .await
    }
}

Expanded macro
This is where things don't go as I would expect. The outer signature looks fine but the async fn defined inside has the return signature of Vec<AsyncTrait> which is my problem.
    fn all<'async_trait>(
        db: &'a Database,
    ) -> ::core::pin::Pin<
        Box<dyn ::core::future::Future<Output = Vec<Self>> + ::core::marker::Send + 'async_trait>,
    >
    where
        'a: 'async_trait,
        Self: 'async_trait,
    {
        // #[allow ... ]
        async fn __all<'a, AsyncTrait: ?Sized + Db<'a>>(db: &'a Database) -> Vec<AsyncTrait> { // Why was `Self` changed to `AsyncTrait`?
            db.collection(<AsyncTrait>::COLLECTION)
                .find(None, None)
                .await
                .unwrap()
                .filter_map(|item| async move { item.ok() })
                .map(|doc| async move { bson::from_document(doc).expect("Decode error") })
                .collect()
                .await
        }
        Box::pin(__all::<Self>(db))
    }

Source
I'm going to make a wild accusation and say that this behaviour comes from here but I don't know much about macros and TokenStreams and such. This looks like it might replace Self with AsyncTrait
Error
error[E0277]: the trait bound `Vec<AsyncTrait>: Extend<impl futures::Future>` is not satisfied
  --> mmt-db/src/lib.rs:16:9
   |
16 | /         db.collection(Self::COLLECTION)
17 | |             .find(None, None)
18 | |             .await
19 | |             .unwrap()
...  |
22 | |             .collect()
23 | |             .await
   | |__________________^ the trait `Extend<impl futures::Future>` is not implemented for `Vec<AsyncTrait>`
   |
   = help: the following implementations were found:
             <Vec<T, A> as Extend<&'a T>>
             <Vec<T, A> as Extend<T>>
   = note: required because of the requirements on the impl of `futures::Future` for `Collect<futures::stream::Map<futures::stream::FilterMap<mongodb::Cursor, impl futures::Future, [closure@mmt-db/src/lib.rs:20:25: 20:56]>, [closure@mmt-db/src/lib.rs:21:18: 21:86]>, Vec<AsyncTrait>>`
   = note: required by `futures::Future::poll`

Hopefully I've just made a silly mistake and you can point that out. Thanks for this awesome crate!
Grant

Hmmm. Maybe I've made a bit too much noise without thinking. I'm finally understanding how the macro works. Its supertrait is Db which makes more sense.
The real question I have is what does my error actually mean? I'm going to sleep on this. My original comment seems invalid now?

The error looks correct to me. You are trying to collect a stream of ?? into a Vec<Self> where ?? is whatever anonymous future type the async move block in map evaluates to, and is definitely not the same type as Self. Probably you didn't mean to put an async block there.

Thanks. Yep you were right. Barking up the wrong tree...


renderer-backend-egl: cast return value in get_native_display()

In the wpe_renderer_backend_egl_interface::get_native_display(),
explicitly cast the wl_display object to the EGLNativeDisplayType.
This should avoid compilation errors on rare EGL stacks that have
odd default EGLNativeDisplayType type definitions.

Cherry-picked into the wpebackend-fdo-1.6 branch as commit 925147d162a9326b428ad288da84955c6b0306c8.


[ARCTIC-917][HIVE]Fix bug: Data are written repeatedly after the Spark Executor failover

Why are the changes needed?

fix #917
Solution: handle orphan files when overwrite commit.
During spark overwrite is committing, the spark driver will list partition files for new creation partitions or partitions that have a new location, the spark driver needs to delete files which not exist in the overwrite operation added files set. This action will happen before the iceberg table commit.
Brief change log
Add a property: delete-untracked-hive-file (default=false)
How was this patch tested?

[x] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before making a pull request

Documentation

Does this pull request introduces a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @baiyangtx ,  The proposal we discussed a few days ago is different from this one. Is the modification here part of your proposal?

cc @baiyangtx , The proposal we discussed a few days ago is different from this one. Is the modification here part of your proposal?

Here is a solution for both spark and optimizer

I think this doesn't handle the unPartition table


TypeError: Attempted to load JSON module without specifying "type": "json" attribute in the import statement.

Hello, I'm trying to preview a quarto file, but I've encountered this error. This is my first time using quarto. I've followed the steps in this video
ERROR: TypeError: Attempted to load JSON module without specifying "type": "json" attribute in the import statement.

Stack trace:
    at async initYamlIntelligenceResourcesFromFilesystem (file:///usr/lib/quarto-cli/bin/quarto.js:82343:29)
    at async file:///usr/lib/quarto-cli/bin/quarto.js:78761:9
    at async initState (file:///usr/lib/quarto-cli/bin/quarto.js:78769:5)
    at async Command.actionHandler (file:///usr/lib/quarto-cli/bin/quarto.js:100593:5)
    at async Command.execute (file:///usr/lib/quarto-cli/bin/quarto.js:8017:13)
    at async Command.parseCommand (file:///usr/lib/quarto-cli/bin/quarto.js:7907:20)
    at async quarto (file:///usr/lib/quarto-cli/bin/quarto.js:118207:9)
    at async file:///usr/lib/quarto-cli/bin/quarto.js:118227:9
    at async mainRunner (file:///usr/lib/quarto-cli/bin/quarto.js:118111:9)
    at async file:///usr/lib/quarto-cli/bin/quarto.js:118218:5

[Process exited 1]

I've tried it out with this example too, and I'm getting the same result :(
BTW, Mason doesn't seem to install ◍ bash-language-server. Not sure if  I should do anything about it or if that's even related to this issue (I'm just a newbie with nvim).

Looks like an error coming from quarto itself, not Neovim, so the issue is better suited for https://github.com/quarto-dev/quarto-cli.

Sorry! I'll search there! Thanks for the response! :)


QueryMap doesn't conform to the set property naming style.

I have a feign client with spring boot app, that has a method signature like below - it uses SpringQueryMap to send URL parameters.
@PostMapping(path="/api/services/helper/reduce")
ResponseEntity<List<String>> filterSupply(
@SpringQueryMap FilterTripParams params,
@RequestBody List<String> supply_list);
The problem is mapped field names of the params are in the camel case while I expect them in the snake case since have spring.jackson.property-naming-strategy=SNAKE_CASE
Serialization and deserialization with the @RequestBody work as expected.
I would consider it a bug.

@Pilipets thanks for reporting this. Please provide a minimal, complete, verifiable example that reproduces the issue.

@Pilipets thanks for reporting this. Please provide a minimal, complete, verifiable example that reproduces the issue.

As claimed originally in the description, serialization for an object with @QueryMap annotation ignores set property naming strategy in the application.properties, and always uses camel case.
1.5 months of waiting, and I finally got a kind of response to the reported issue.
Keeping that in mind, I don't find it worth spending time for a workable example to wait months again before getting a response.

I was willing to support this thread and solve the problem, but at the moment of reporting the issue - not years after.
Close this issue as expected.

As claimed originally in the description, serialization for an object with @QueryMap annotation ignores set property naming strategy in the application.properties, and always uses camel case.
1.5 months of waiting, and I finally got a kind of response to the reported issue.
Keeping that in mind, I don't find it worth spending time for a workable example to wait months again before getting a response.

I was willing to support this thread and solve the problem, but at the moment of reporting the issue - not years after.
Close this issue as expected.

@Pilipets please be respectful. You opened an issue as we were completing a major release with a year's worth of work. Then many team members took time off over holidays. You have no concept of our lives outside of open source support.

@Pilipets please be respectful. You opened an issue as we were completing a major release with a year's worth of work. Then many team members took time off over holidays. You have no concept of our lives outside of open source support.

@spencergibb  My fault, agree - just emotions cause I don't have a working example anymore, but I had it then.

@spencergibb  My fault, agree - just emotions cause I don't have a working example anymore, but I had it then.

Thanks

Thanks


Entity not numeric

After today's update, 4 of the 5 disks do not report temperature anymore. Worked fine with 1.1.7.
Any idea, what changed here?
Ask any info you need, dear Tomaae ;-)

The sensors are present and working, they just do no display...

example of card code:
type: gauge
min: 0
max: 100
entity: sensor.omv_sda
severity:
  green: 0
  yellow: 65
  red: 70

Thanks in advance ;-)

Spotted a difference now with the one sensor, that is working. This one only reports temperature 59 °C.

The 4 which do not want to display report 54 (Min/Max 21/67) °C
How can we fix that?

yea, seems like those disks are displaying info in non-standard way. Not sure how, since only change in parsing logic was in uptime sensor.
can you send me diagnostic data from HA?

config_entry-openmediavault-503508233c2abd974064d473e2f398d1.json.txt

ok, that is interesting. we can certainly workaround this issue.
but this had to be a problem even before the update. cant imagine it happening due to update

Very strange then, as it really worked flawlessly for months ;-)

Is there something, I can do now, or just have to wait your investigation, @tomaae ? ;-)

I will fix it, no worries. Right now I'm working on something else, then I will get back to OMV integration.

No need to rush, I'm not in need to watch the temps of my HDD's continously :-D Having a life is still prior ;-) I just wanted to be sure, you are not waiting for more info from me...

No time for life ;) working on integration for NAS I use, I need it badly at this point

Leave TrueNAS, go back to OMV. Benefit for both of us. A already working integration and time for life :-P :-D :-D

No way, I'm much more satisfied with TrueNAS :P
And I have its integration already miles ahead of OMV one ;)

Can you try now? I have updated api parser to version I use now on TrueNAS project. It will auto convert variables to proper type, not sure how it will react to your issue tho.

Still the same :-(
config_entry-openmediavault-51025d4290f4bcb06e8fd3258e4eba37.json.txt
Thanks for your time ;-)

oki, can you try now?

Yes, that did the trick ;-)

excellent ;)


Noop HTTP Filter

When using ECDS to provide a filter configuration, it would be helpful to be able to provide a noop filter that would act as a passthrough. This would allow management servers to respond with a noop config most of the time and replacing it with another filter whenever necessary.
With the unified matching work and support for skipping filter execution this would be possible to express via an always true matcher that skips filter execution, but the need for an actual filter configuration (that would always be skipped) makes this a bit awkward.
Given that, it seems like registering the PassthroughFilter as a proper HTTP filter would be an easy way to provide this functionality.
Thoughts? @mattklein123

Another option would be to handle an ECDS response that doesn't contain a filter config as indicating that a noop filter should be used, though this seems less explicit.

Per your point, if the config is optimized down to always skip, can't we just remove the filter entirely?

Relying on the match tree to skip the filter is a bit awkward since we would still require a filter config to be specified.  Maybe we can make it possible to omit the filter config if the match tree can be reduced to "always skip"?
cc @htuch since Matt is out

Relying on the match tree to skip the filter is a bit awkward since we would still require a filter config to be specified.  Maybe we can make it possible to omit the filter config if the match tree can be reduced to "always skip"?
cc @htuch since Matt is out

@snowp can you share two example configs here (for posterity and also because I don't think I have the full context paged in)?

@snowp can you share two example configs here (for posterity and also because I don't think I have the full context paged in)?


chore: Release v1.13.0

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.13.0-alpha.3 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


simplify usage of curl

Thanks :)

I changed the other mention of curl in USAGE-GUIDE (https://github.com/awslabs/s2n/commit/94a137a1f916ee98495f16d2fa48b9766835d4a4)


unable to refer typings on Linux

on Linux latest version does not get the typings
probably because of case sensitive nature.
get below error.
/node_modules/ag-grid/main.d.ts(99,15): error TS2307: Cannot find module './dist/lib/rowControllers/inMemory/inMemoryNodeManager'.
on windows it is working fine as filename. folder name are not case sensitive.

sorry didn't saw the response


[Polymetis][WIP] Change move to policies to use controller updates

Description
Please include a summary of the change and link to an issue this PR fixes. Please also include relevant context. List any downstream components that might be affected by this change.
Fixes # (issue)
Type of change
Please check the options that are relevant.

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] Proposes a change (non-breaking change that isn't necessarily a bug)
[ ] Refactor
[ ] New feature (non-breaking change that adds a new functionality)
[ ] Breaking change (fix or feature that would break some existing functionality downstream)
[ ] This is a unit test
[ ] Documentation only change
[ ] Datasets Release
[ ] Models Release

Type of requested review

[ ] I want a thorough review of the implementation.
[ ] I want a high level review.
[ ] I want a deep design review.

Before and After
If this PR introduces a change or fixes a bug, please add before and after screenshots (if this is causes a UX change) or before and after examples(this could be plain text, videos etc ) to demonstrate the change.
If this PR introduces a new feature, please also add examples or screenshots demonstrating the feature.
Testing
Please describe the tests that you ran to verify your changes and how we can reproduce.
Checklist:

[ ] I have performed manual end-to-end testing of the feature in my environment.
[ ] I have added Docstrings and comments to the code.
[ ] I have made changes to existing documentation where needed.
[ ] I have added tests that show that the PR is functional.
[ ] New and existing unit tests pass locally with my changes.
[ ] I have added relevant collaborators to review the PR before merge.
[ ] [Polymetis only] I ran on hardware (1) all scripts in tests/scripts, (2) asv benchmarks.

Codecov Report

Merging #1137 (f330797) into main (39daf3b) will increase coverage by 18.45%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main    #1137       +/-   ##
===========================================
+ Coverage   15.88%   34.33%   +18.45%
===========================================
  Files         341      344        +3
  Lines       33557    33684      +127
===========================================
+ Hits         5329    11567     +6238
+ Misses      28228    22117     -6111

Impacted Files
Coverage Δ

test_utils.py
21.87% <0.00%> (ø)

tests/test_parallel.py
65.38% <0.00%> (ø)

tests/test_base_utils.py
98.55% <0.00%> (ø)

dialog/post_process_logical_form.py
29.23% <0.00%> (+1.53%)
:arrow_up:

memory/filters_conversions.py
62.19% <0.00%> (+5.20%)
:arrow_up:

dialog/dialogue_manager.py
87.80% <0.00%> (+6.09%)
:arrow_up:

memory/memory_nodes.py
88.91% <0.00%> (+8.06%)
:arrow_up:

shared_data_struct/rotation.py
57.14% <0.00%> (+8.16%)
:arrow_up:

interpreter/craftassist/interpret_modify.py
8.39% <0.00%> (+8.39%)
:arrow_up:

lowlevel/minecraft/small_scenes_with_shapes.py
8.39% <0.00%> (+8.39%)
:arrow_up:

... and 119 more


Preserve file uploads if conflicting field names.

Discussed in https://github.com/ciscoheat/sveltekit-superforms/discussions/91
When dataType = 'json', fields with the same keys as in the data are cleared to reduce post size. This can cause trouble if files are posted, which shouldn't be affected. When clearing the fields, skip all fields that are files.

Fixed in v0.6.18.


Topbar hover dropdown IOS scrolling issue

On IOS 7.1.1 Safari on IPad, go to demo page...
http://foundation.zurb.com/docs/components/topbar.html
... scroll down a couple of inches then tap a couple of inches under the "Item 1" dropdown on the first bar - it should activate. However far you scroll down, it can be activated by clicking that distance below it.
If you set is_hover to false, this fixes it, so a hack fix would be to write some javascript to check for touch and set the data_option accordingly.
This is surely something to do with the css :hover problems in ios. I only apply css :hover to descendants of the no-touch class. Perhaps this is all that's needed in the foundation css.
Please confirm on other IOS versions and other touch devices.

We added this to our "known issues" section in our planning board for the next version. A PR would be valuable to the community, otherwise It will be addressed then. You can see and vote on the proposed updates here: https://trello.com/b/QBPKlQqf/foundation-sites


String(number) does not return ${number} type

Bug Report

🔎 Search Terms

string constructor number type template literal
🕗 Version & Regression Information

4.2.3
⏯ Playground Link

Playground link with relevant code
💻 Code

const stringNumber: `${number}` = String(123)

🙁 Actual behavior
Error: Type 'string' is not assignable to type '${number}'.(2322)
🙂 Expected behavior
No error.
Why
String, according to ES (String(value), and ToString(argument)), uses toString method on passed in values, so ideally the fix should include only changes on Number interface, but currently it's String's def does not care about toString, so these two signature would have to be generic:
// lib.es5.d.ts
interface StringConstructor {
    new(value?: any): String;
    (value?: any): string;
}

And this one would need to be generic as well as the type of returned string would depend on the radix.
// lib.es5.d.ts
interface Number {
    toString(radix?: number): string;
}

This approach would make String easily extensible and compatible with template literal types, but I'm not sure how drastic of a change it is.
Most likely would be related to https://github.com/microsoft/TypeScript/issues/42996

For now, you can augment StringConstructor in your own projects to get this effect:
interface StringConstructor {
    <T extends number>(value: T): `${T}`
}
String(32); // <32>(value: 32) => "32" (+1 overload)

The radix case seems much more difficult.

Same issue exists with boolean and bigint as well.
Also generic overload doesn't always work in some cases, such as.
declare const foo: Promise<boolean>
foo.then(String) // gives the type Promise<string>
foo.then((foo) => String(foo)) // gives the type Promise<"true" | "false">

So currently I use this, to overcome the issue above:
interface StringConstructor {
  <T extends string | number | bigint | boolean | null | undefined>(value: T): `${T}`;
  (value: number): `${number}`;
  (value: bigint): `${bigint}`;
  (value: boolean): `${boolean}`;
}


Move navigation to the mobile header

Issue 14 https://github.com/near-daos/astro-ui/issues/91

no plans to implement


Bind String::humanize_size method

As suggested in #31993:

We could also consider exposing this method to scripts, so that projects that need to display file sizes can use it directly.

Exactly my use case. I want to compare different compression methods more easily.

Fails on macOS according to Travis:
core/variant_call.cpp:287:2: error: conversion from 'const Variant' to 'size_t' (aka 'unsigned long') is ambiguous
        VCALL_LOCALMEM1R(String, humanize_size);

These two would resolve this I think, but they're not compiled by default it seems:
https://github.com/godotengine/godot/blob/82b9557803f33521694587b6014645a05a814ecb/core/variant.h#L175-L178

I'd just change humanize_size to use int64_t.

Thanks!

What's the reason for NEED_LONG_INT existing? Isn't long long almost always 64-bit and int almost always 32-bit? This code existed before Godot was open source, so cc @reduz


Enable chaos target and capabilities JSON incomplete

The JSON section shown under "Enable chaos target and capabilities"  item (1) is incomplete and does not fit in with the context of item (2) --body @target.json
as such it is not possible to work through the example shown

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

ID: 1d31160e-c77b-86bb-4e9e-c5700c1cffa8
Version Independent ID: 8f5f736e-62d4-e97e-5415-0f83c41e5736
Content: Create an experiment that uses an agent-based fault with Azure Chaos Studio with the Azure CLI
Content Source: articles/chaos-studio/chaos-studio-tutorial-agent-based-cli.md
Service: chaos-studio
GitHub Login: @johnkemnetz
Microsoft Alias: johnkem

@andoius Thank you for your feedback . We will get this reviewed and updated as needed.

@andoius We have engaged the content team on this for reviewing the same and updating as necessary.

This issue has been resolved, can the owner please close?

gh close issue

#please-close


Example usage

Any chance you can add a bare bones "example usage" to the docs, i.e how to include it in node, format some code etc?
I assume it would be just calling prettier with this listed as a plugin, but that would be helpful to new users.

Yes, I will, in a similar way as https://github.com/prettier/plugin-python/blob/master/README.md
Currently, it wouldn't make sense to use the plugin for anything else than developing it, because it will break your code. I'm about to push a proper "alpha" in the coming days.
I'll leave this issue open until then.

No rush buddy, thanks for sorting it for us.

Done.


Remove optional ID features from required tests

If I understand it correctly, the Recursive references between schemas test uses an optional "id" feature. Implementations have to use "id" to resolve references from them to other documents, but aren't required to allow "id" to add a new address that incoming references can refer to.
Two questions:

Is this correct?

If so what do we do about it? I'd be happy to make a PR that changes that test so it doesn't use addressing by "id" if that's what we want to do.

Implementations have to use "id" to resolve references from them to other documents, but aren't required to allow "id" to add a new address that incoming references can refer to.

@seagreen are you referring to https://tools.ietf.org/html/draft-zyp-json-schema-04#section-7.2.4, specifically "An implementation choosing to support inline dereferencing SHOULD be able to use this kind of reference.  Implementations choosing to use canonical dereferencing, however, are not required to support it."
I think this distinction was dropped and IDs that change base URI must be supported in draft-06, it's all in RFC3986. @handrews?
So maybe it is ok to drop these internal IDs in draft4 test and use JSON pointers instead, in draft6 it can stay as is I think.

@seagreen @epoberezkin this test case has nothing to with inline vs canonical dereferencing.  Both of the id values in this test case are full URIs without fragments, which are usable via canonical dereferencing which MUST be supported.  Canonical dereferencing supports both internal and external references.
Unless @Julian disagrees, I think this should be closed without changing anything.

@handrews think I agree

@handrews: Thanks for the clarification!


Tomorrow.io free limit is too restrictive

Current free limits are:
Requests per second
3
Requests per hour
25
Requests per day
500
Aggressive caching is implemented, but 25 per hour is far too restrictive.

Need to investigate alternatives. A good source for weather apis can be found here.

Rate limit has been increased per hour to 499 requests

The new hourly rate limit is 499 requests, with a total of 500 per day


Multiplying Read/Writes for persistent PM2 services running longer than 3-5 days on MongoDB Serverless connections.

Bug description
So, this is a bit bizarre, but my average reads per second for my MongoDB serverless instance is ~275 on a fresh start (rebooted server). However, every 24 hours, around 11pm-12am (for the server), the reads per second doubles and then holds for the next 24hours, until it doubles and holds again.
The server runs Nginx, PM2, and Prisma 4.14.0, on a NextTS stack with tRPC. It's also running on an expressTS microservice that cranks every 5 minutes.
How to reproduce

Run application with pm2 start
Let the application run for 24-48 hours
Watch the mongoDB serverless monitoring logs.
To reset, you need to reboot the server.

Expected behavior
I expect the reads to stay consistent around the average of 275 per second.
Prisma information
/**
 * Instantiates a single instance PrismaClient and save it on the global object.
 * @link https://www.prisma.io/docs/support/help-articles/nextjs-prisma-client-dev-practices
 */
import { PrismaClient } from '@prisma/client'

const globalForPrisma = global as unknown as { prisma: PrismaClient }

export const prisma =
  globalForPrisma.prisma ||
  // new PrismaClient({
  //   log: ['query'],
  // }
  new PrismaClient()

if (process.env.NODE_ENV !== 'production') globalForPrisma.prisma = prisma

Environment & setup

OS: Ubuntu 20.04.6 LTS
Database: MongoDB Serverless
Node.js version: v18.12.1
Typescript version: v4.7.4

Prisma Version
Application:
prisma                  : 4.14.1
@prisma/client          : 4.14.1
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine d9a4c5988f480fa576d43970d5a23641aa77bc9c (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli d9a4c5988f480fa576d43970d5a23641aa77bc9c (at<EMAIL_ADDRESS>Format Wasm             : @prisma/prisma-fmt-wasm 4.14.0-67.d9a4c5988f480fa576d43970d5a23641aa77bc9c
Default Engines Hash    : d9a4c5988f480fa576d43970d5a23641aa77bc9c
Studio                  : 0.484.0

Microservice:
prisma                  : 4.15.0
@prisma/client          : 4.15.0
Current platform        : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 8fbc245156db7124f997f4cecdd8d1219e360944 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 8fbc245156db7124f997f4cecdd8d1219e360944 (at<EMAIL_ADDRESS>Format Wasm             : @prisma/prisma-fmt-wasm 4.15.0-28.8fbc245156db7124f997f4cecdd8d1219e360944
Default Engines Hash    : 8fbc245156db7124f997f4cecdd8d1219e360944
Studio                  : 0.484.0

What kind of traffic is your application handling? The level of that is constant through all this time?

What kind of traffic is your application handling? The level of that is constant through all this time?

Traffic is around 300 unique visitors a day, but around that time (midnight), activity should be or is near dead. The microservice cranks regardless every 5 minutes, and the table sizes don't move around too often. Nothing that would make sense as to a literal 2x in reads that sustains for the entire 24h until the next 2x in reads, which resets back to expected levels once the server is rebooted. Connections also increases by 3 every time that it multiplies and holds. Without understanding exactly what would dictate a new connection (NextJS Server worker, client, etc), I don't know if this is relevant.

Whats your benchmark tool or is it from atlas?

What kind of traffic is your application handling? The level of that is constant through all this time?

Traffic is around 300 unique visitors a day, but around that time (midnight), activity should be or is near dead. The microservice cranks regardless every 5 minutes, and the table sizes don't move around too often. Nothing that would make sense as to a literal 2x in reads that sustains for the entire 24h until the next 2x in reads, which resets back to expected levels once the server is rebooted. Connections also increases by 3 every time that it multiplies and holds. Without understanding exactly what would dictate a new connection (NextJS Server worker, client, etc), I don't know if this is relevant.

Is this really prisma relevant issue? You said in midnight there should be no traffic but your microservice still runs and doing some reads. It should be your microservice or you have continuous backup from atlas

If there is no traffic, and not scheduled jobs, then there should be no queries at all. Prisma does not run any queries by itself in general.

The microservice cranks regardless every 5 minutes

What does that mean, "crank"? What is triggering the microservice to do things if there is no traffic on the application?

If there is no traffic, and not scheduled jobs, then there should be no queries at all. Prisma does not run any queries by itself in general.

The microservice cranks regardless every 5 minutes

What does that mean, "crank"? What is triggering the microservice to do things if there is no traffic on the application?

Every 5 minutes, there's a scheduled job to run through the database and perform actions. This increases the load and traffic to a normal, expected level of "burst." The average, over hours of this cranking every 5 minutes and the application running, is around 275-300 sustained reads per second, with a 5 minute granularity. There are periods of time where this sustains for 24-48 hours without issue.
The issue is that this average literally doubles at specific times, so that the average sustained becomes 600, and then 1200, and then 2400, reads per second.
However, after taking a look at MongoDB monitoring dashboard, I've realized that the timezone is not set to local time. Therefore, it appears as though the "duplication" events are closer, time-wise, with when I push updates to the code and rebuild.
With this information, it seems as though the "duplication" events are occurring when I run pm2 stop [ID] and pm2 start [ID]. For some reason, this doesn't seem to kill whatever worker thread/process that the prisma client is running on. I don't really know it is possible that prisma could have multiple "duplicated" clients running the same exact reads when only 1, not stale, client should be getting triggered.

Prisma only runs with your code. Each time you call new PrismaClient() you get a new instance. When the code stops running, Prisma also stops running.
This sounds a bit like the old "deployment" still running while a new one is added, is that possible somehow?
We often see similar problems in serverless deployments. A new version of the app is deployed, but the old one keeps running and keeps connections open. Fortunately there is usually no traffic routed to the old ones any more, but that seems to be different in your case as the scheduled job seems to keep going.

Unfortunately, this isn’t a serverless application, only a serverless mongoDB collection. The application (and microservice) run on a hosted server, with Nginx and PM2. I also wanted to check and see if there were multiple processes that got duplicated on the hosted server (i.e. two next applications when running pm2 stop and start). However, there is only ever 1 nextJS process and 1 microservice process.

@Swertin as @janpio, prisma does not run any queries unless you tell it to.
Do you maybe know what kind of queries are send out to mongo instance in that time frame? Do they correspond to any queries in your application. The fact that it happens around 0pm also looks suspicious: could it be that some scheduling code somewhere does not handle 0 hour correctly?
In any case, as @janpio mentioned, Prisma does not run any queries unless instructed to. I am sorry, but so far it does not seem like there is a problem with Prisma in this case, but rather that something within your application/deployment goes wrong and causes the spike.
If you still beleive Prisma is the culprit, we'd like to ask you to provide an isolated example that we could run, if possible.
Thank you!

@Swertin Did you see the message from @SevInf? Without any activity on this issue, we would later close it as part of our issue process.

Hey @Swertin, without your input we cannot move this issue forward, so I am closing it. Please provide us with the missing information so we understand how to treat this, and we will happily re-open it.

hey @Jolg42 @millsp, apologize for missing this, the issue in my case was due to a bug where tRPC would initialize our local cache logic on the frontend, as it was a singleton class. The solution was to separate the cache logic away from Next, and run it as an express API, then just call the API routes rather than directly calling the methods.


Fix build on x86 32 bits.

These changes are enough to fix the build, and make test.py and BeMatched work (the latter crashed on exit thou, not sure if it does that on 64 bits too).
Not sure why these functions got the wrong values for int/uint vs int32/uint32, as the Haiku header files are pretty clear about those (and directly using int32/uint32 on the .cpp files here do work).
I've never used pybind11, so I might be talking gibberish, but maybe there's a way to make it understand and use Haiku's integer types?

I had used an automatic binding tool to kickstart my bindings so, as they say, all errrors are the fault of the previous programmer.

These changes are enough to fix the build, and make test.py and BeMatched work (the latter crashed on exit thou, not sure if it does that on 64 bits too).

It did that before as well :sweat_smile:

but maybe there's a way to make it understand and use Haiku's integer types?

Haven't looked into it at all, but, that would certainly be nice.

One question thou... do we really need/want to support Python 3.9?
While there's no rule written about it, I think that new ports/recipes should ideally only target versions starting with the current default Python version (3.10), unless there's a specific need to support older versions.

No reason to support Python 3.9, so, why not?

BTW, I also have a working HaikuPorts recipe for 32 bits (need to test it with these changes on 64 bits, to make sure I didn't break anything).

Ok, let's see if I can remember that you have a recipe... Maybe you can send me it in a pastebin or as a PR on my fork of haikuports?


Extractor for stream.me archived videos

Live streams are not supported
Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[x] New extractor
[ ] New feature

Description of your pull request and other information
Extractor for archived videos. Livestreams are somewhat different beasts, and I'm not sure when I'll get around to working on them, so I only submit this one for now.
PR #11520 have not had progress in a long time.
This closes #17673 .

@dstftw, anything that I should change or improve in this PR?

Start from reading coding conventions.

@dstftw, nevermind this PR. Feel free to close this one, and #11520 .
Stream.me is dead and it's not coming back.


Where do I find helm 3 charts?

As helm2 is deprecated I started to look for helm 3 charts instead of my currently used helm2 ones.
Where should I find those?
I only have encountered helm2 charts with apiversion 1.
Even on the helm hub: https://artifacthub.io/   I randomly search for a chart and it will be helm2 guaranteed.
Rancher's repo : https://github.com/rancher/helm3-charts    ,  no.. they are not helm3 but helm 2.
So where are the corresponding helm3 charts for the deprecated ones (for common public projects like psql,kafka,elasticsearch..etc)?

Helm v2 charts can also be installed in Helm v3.  A chart does not need to be updated to apiVersion: v2 unless it uses [CRDs](apiVersion: v1) which changed in Helm v3. Additionally, a chart can also be updated if the chart maintainer wishes to use the latest capabilities in Helm v3.

To clarify, it depends on the chart and chart maintainer if a chart with apiVersion: v2 is provided.
Hope this answers your question.

@hatharom It will likely be awhile before people switch to Helm v3 only charts. The reason for that is Helm v2 is still widely used and people want to support both for now. Helm v2 is going to hit the end of life for support and we are working to help people transition. I would hope that 6 months from now we see far more Helm v3 only charts.

closing as answered.

Thanks the responses.
I am aware of that chart version is depends on the chart maintainers.
But as I stated above I dig up the whole the web and couldn't find any Helm 3 chart.
Pretty strange..

@hatharom Here is a notice from Bitnami about updating to apiversion: v2: https://github.com/bitnami/charts#important-notice-helm-v2-eol-warning


Download/Print Stickerfile

Figma had a choice for what is written to the card (LNURLw/LNURLp) and what is printed on a sticker (LNDhub/LNURLp). This and the outputfile is missing.
If LNURLw is assumed to be mandatory to write its not supported by code yet.

fixed


[Feature]Role Based Access Control(RBAC) for Identity Server Console

Is your feature request related to a problem? Please describe.
Since we deprecating the carbon console, Role-Based Access Control(RBAC) for the Identity Server Console is an essential requirement we need to have in order to support the previous behavior.
Describe the solution you would prefer

Define the system APIs with scopes
Allow to assign scopes from those APIs to roles
Optionally have permission collections created for specific management tasks like application management, user management, etc.
The console should subscribe to those APIs and based on user roles(scopes), UI needs to be generated

Additional context
With https://github.com/wso2/product-is/issues/16344 and https://github.com/wso2/product-is/issues/16363, we have the necessary features to build the role-based access control for the console.

As per the feedback received following experience is agreed upon.

There will be a new section available in the Console to control the IDP aspect of the Console
In this new section you can configure roles for the Console
Role creation for the Console is as follows,

Provide the role name
Select the Console features(Ex: Application management[read|write], User management(read|write])
These will be available in tenant features and organization features


page 518 "Purchase Lines" - OnAferOnActionLine - Event Request

page 518 "Purchase Lines"
{
Caption = 'Purchase Lines';
Editable = false;
LinksAllowed = false;
PageType = List;
SourceTable = "Purchase Line";
layout
{
    area(content)
    {
        repeater(Control1)
        {
            ShowCaption = false;
            field("Document Type"; "Document Type")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the type of document that you are about to create.';
            }
            field("Document No."; "Document No.")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the document number.';
            }
            field("Buy-from Vendor No."; "Buy-from Vendor No.")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the name of the vendor who delivered the items.';
            }
            field("Line No."; "Line No.")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the line''s number.';
                Visible = false;
            }
            field(Type; Type)
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the line type.';
            }
            field("No."; "No.")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the number of the involved entry or record, according to the specified number series.';
            }
            field("Variant Code"; "Variant Code")
            {
                ApplicationArea = Planning;
                ToolTip = 'Specifies the variant of the item on the line.';
                Visible = false;
            }
            field(Description; Description)
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies a description of the entry of the product to be purchased. To add a non-transactional text line, fill in the Description field only.';
            }
            field("Location Code"; "Location Code")
            {
                ApplicationArea = Location;
                ToolTip = 'Specifies the code for the location where the items on the line will be located.';
                Visible = true;
            }
            field(Quantity; Quantity)
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the number of units of the item specified on the line.';
            }
            field("Reserved Qty. (Base)"; "Reserved Qty. (Base)")
            {
                ApplicationArea = Reservation;
                ToolTip = 'Specifies the value in the Reserved Quantity field, expressed in the base unit of measure.';
            }
            field("Unit of Measure Code"; "Unit of Measure Code")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies how each unit of the item or resource is measured, such as in pieces or hours. By default, the value in the Base Unit of Measure field on the item or resource card is inserted.';
            }
            field("Direct Unit Cost"; "Direct Unit Cost")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the cost of one unit of the selected item or resource.';
            }
            field("Indirect Cost %"; "Indirect Cost %")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the percentage of the item''s last purchase cost that includes indirect costs, such as freight that is associated with the purchase of the item.';
                Visible = false;
            }
            field("Unit Cost (LCY)"; "Unit Cost (LCY)")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the cost, in LCY, of one unit of the item or resource on the line.';
                Visible = false;
            }
            field("Unit Price (LCY)"; "Unit Price (LCY)")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the price, in LCY, of one unit of the item or resource. You can enter a price manually or have it entered according to the Price/Profit Calculation field on the related card.';
                Visible = false;
            }
            field("Line Amount"; "Line Amount")
            {
                ApplicationArea = Basic, Suite;
                BlankZero = true;
                ToolTip = 'Specifies the net amount, excluding any invoice discount amount, that must be paid for products on the line.';
            }
            field("Job No."; "Job No.")
            {
                ApplicationArea = Jobs;
                ToolTip = 'Specifies the number of the related job. If you fill in this field and the Job Task No. field, then a job ledger entry will be posted together with the purchase line.';
                Visible = false;
            }
            field("Job Task No."; "Job Task No.")
            {
                ApplicationArea = Jobs;
                ToolTip = 'Specifies the number of the related job task.';
                Visible = false;
            }
            field("Job Line Type"; "Job Line Type")
            {
                ApplicationArea = Jobs;
                ToolTip = 'Specifies a Job Planning Line together with the posting of a job ledger entry.';
                Visible = false;
            }
            field("Shortcut Dimension 1 Code"; "Shortcut Dimension 1 Code")
            {
                ApplicationArea = Dimensions;
                ToolTip = 'Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up in the General Ledger Setup window.';
                Visible = false;
            }
            field("Shortcut Dimension 2 Code"; "Shortcut Dimension 2 Code")
            {
                ApplicationArea = Dimensions;
                ToolTip = 'Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up in the General Ledger Setup window.';
                Visible = false;
            }
            field("ShortcutDimCode[3]"; ShortcutDimCode[3])
            {
                ApplicationArea = Dimensions;
                CaptionClass = '1,2,3';
                TableRelation = "Dimension Value".Code WHERE("Global Dimension No." = CONST(3),
                                                              "Dimension Value Type" = CONST(Standard),
                                                              Blocked = CONST(false));
                Visible = false;
            }
            field("ShortcutDimCode[4]"; ShortcutDimCode[4])
            {
                ApplicationArea = Dimensions;
                CaptionClass = '1,2,4';
                TableRelation = "Dimension Value".Code WHERE("Global Dimension No." = CONST(4),
                                                              "Dimension Value Type" = CONST(Standard),
                                                              Blocked = CONST(false));
                Visible = false;
            }
            field("ShortcutDimCode[5]"; ShortcutDimCode[5])
            {
                ApplicationArea = Dimensions;
                CaptionClass = '1,2,5';
                TableRelation = "Dimension Value".Code WHERE("Global Dimension No." = CONST(5),
                                                              "Dimension Value Type" = CONST(Standard),
                                                              Blocked = CONST(false));
                Visible = false;
            }
            field("ShortcutDimCode[6]"; ShortcutDimCode[6])
            {
                ApplicationArea = Dimensions;
                CaptionClass = '1,2,6';
                TableRelation = "Dimension Value".Code WHERE("Global Dimension No." = CONST(6),
                                                              "Dimension Value Type" = CONST(Standard),
                                                              Blocked = CONST(false));
                Visible = false;
            }
            field("ShortcutDimCode[7]"; ShortcutDimCode[7])
            {
                ApplicationArea = Dimensions;
                CaptionClass = '1,2,7';
                TableRelation = "Dimension Value".Code WHERE("Global Dimension No." = CONST(7),
                                                              "Dimension Value Type" = CONST(Standard),
                                                              Blocked = CONST(false));
                Visible = false;
            }
            field("ShortcutDimCode[8]"; ShortcutDimCode[8])
            {
                ApplicationArea = Dimensions;
                CaptionClass = '1,2,8';
                TableRelation = "Dimension Value".Code WHERE("Global Dimension No." = CONST(8),
                                                              "Dimension Value Type" = CONST(Standard),
                                                              Blocked = CONST(false));
                Visible = false;
            }
            field("Expected Receipt Date"; "Expected Receipt Date")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the date that you expect the items to be available in your warehouse.';
            }
            field("Outstanding Quantity"; "Outstanding Quantity")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies how many units on the order line have not yet been received.';
            }
            field("Outstanding Amount (LCY)"; "Outstanding Amount (LCY)")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the amount for the items on the order that have not yet been received in LCY.';
                Visible = false;
            }
            field("Amt. Rcd. Not Invoiced (LCY)"; "Amt. Rcd. Not Invoiced (LCY)")
            {
                ApplicationArea = Basic, Suite;
                ToolTip = 'Specifies the sum, in LCY, for items that have been received but have not yet been invoiced. The value in the Amt. Rcd. Not Invoiced (LCY) field is used for entries in the Purchase Line table of document type Order to calculate and update the contents of this field.';
                Visible = false;
            }
        }
    }
}

actions
{
    area(navigation)
    {
        group("&Line")
        {
            Caption = '&Line';
            Image = Line;
            action("Show Document")
            {
                ApplicationArea = Basic, Suite;
                Caption = 'Show Document';
                Image = View;
                Promoted = true;
                PromotedCategory = Process;
                PromotedIsBig = true;
                ShortCutKey = 'Shift+F7';
                ToolTip = 'Open the document that the selected line exists on.';

                trigger OnAction()
                var
                    PageManagement: Codeunit "Page Management";
                begin
                    PurchHeader.Get("Document Type", "Document No.");
                    PageManagement.PageRun(PurchHeader);
                    //NPO begin
                    OnAferOnActionLine(PurchHeader);
                    //NPO end
                end;
            }
            action("Reservation Entries")
            {
                AccessByPermission = TableData Item = R;
                ApplicationArea = Reservation;
                Caption = 'Reservation Entries';
                Image = ReservationLedger;
                Promoted = true;
                PromotedCategory = Process;
                PromotedIsBig = true;
                ToolTip = 'View the entries for every reservation that is made, either manually or automatically.';

                trigger OnAction()
                begin
                    ShowReservationEntries(true);
                end;
            }
            action("Item &Tracking Lines")
            {
                ApplicationArea = ItemTracking;
                Caption = 'Item &Tracking Lines';
                Image = ItemTrackingLines;
                Promoted = true;
                PromotedCategory = Process;
                PromotedIsBig = true;
                ShortCutKey = 'Shift+Ctrl+I';
                ToolTip = 'View or edit serial numbers and lot numbers that are assigned to the item on the document or journal line.';

                trigger OnAction()
                begin
                    OpenItemTrackingLines();
                end;
            }
        }
    }
}

trigger OnAfterGetRecord()
begin
    ShowShortcutDimCode(ShortcutDimCode);
end;

trigger OnNewRecord(BelowxRec: Boolean)
begin
    Clear(ShortcutDimCode);
end;

var
    PurchHeader: Record "Purchase Header";

protected var
    ShortcutDimCode: array[8] of Code[20];

//NPO begin
[IntegrationEvent(true, false)]
local procedure OnAferOnActionLine(var PurchHeader: Record "Purchase Header")
begin
end;
//NPO end

}

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Fail kudo init if version is unknown.

What this PR does / why we need it:
This hopefully should have no impact on developer workflows nor on how a (pre-)released build works. However in cases where a matching controller docker image does not exist, it will fail fast, rather than deploying a (potentially incompatible) controller from a docker image built for some earlier commit.
Implementation:

first, set pkg/version.gitVersion to a version string using $LDFLAGS only when a tagged commit is checked out (this will always be true for release builds). In other cases, set it to a sentinel value.
then refuse to kudo init unless the sentinel value is overridden explicitly.

Fixes #1549
Signed-off-by: Marcin Owsiany<EMAIL_ADDRESS>

PTAL, I:

changed the sentinel value as you suggested. I think it conveys the intent beter.
removed the exact flag name from the error message, and added a mention of "not released", since we probably want to use this as a hint that "maybe you should not be building this yourself" rather than triggering a knee-jerk reaction of using --version. If someone really wants to use it this way, they should be able to find the right flag from the kubectl kudo help init.


[Fixed]: captcha selection, copy paste, line break, and captcha blur issues

Pull Request Template
Description

fixed the captcha line getting breaked issue
fixed blur issue and made it more visible to the users
made captcha text black for dark mode for better visibility
disabled selection for the captcha text-field & disabled copy paste in the captcha field

Fixes #278
Type of change
Please delete options that are not relevant.

[x] 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)
[ ] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] 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
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

@777Prabhjot can you hide the captcha from dom

@Arnabdaz  done


Checkbox doesn't implement classes.root

Neither does Radio.  Input and Switch do.  RadioGroup does not, but it forwards on to FormGroup, which does.
If these components are meant to be drop-in compatible, then the names of the classes also have to be taken into consideration.

How is it a breaking change?  Just have a empty root class?

@eigood I have linked the WIP PR. It's a breaking change because the classes key is already used:
 export const styles = theme => ({
-  default: {
+  root: {
     color: theme.palette.text.secondary,
   },

I'm also noticing that 'input' class isn't provided across Select/Checkbox, but is on Input.  I'm trying to make flat design look more like a browser, with border and background/foreground stuff, without having to have a bunch of conditional stuff.


s/purgeInteval/purgeInterval

Use correct name for purgeInterval

This change is

I signed it!

Should I rebase onto current master?

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

/lgtm /approve

@kow3ns I rebased to master, what happens next?

@kow3ns I think somehow the bot does not recognize your review :(


P4RT: PacketIn: Update tests to use StreamChannelGetPackets()

P4RT Tests were previously using StreamChannelGetPacket() with time.Sleep() to get the PacketIn to client.
This is not a correct way to do it since, we are not validating whether all the packets that were sent as PacketOut are received or not.
By updating to StreamChannelGetPackets() we are receiving all the packets at once and also waiting for a specified amount of time to receive all the packets.
Additionally, we are also throwing an error if the expected number of packets doesnot match the actual received number of packets.
Some additional info for Google reviewers:

b23f8c84-2a81-42a8-940c-21d5fe8a924e
08bddddc-0449-4b73-962a-aa88d7b8e01c
ceb3b01b-8b36-4e87-9369-4cd677dbcd73

/gcbrun


Fcrepo 2757 - Split description and binary

JIRA Ticket: https://jira.duraspace.org/browse/FCREPO-2757
What does this Pull Request do?
Restructures how binaries are stored to separate description and fedora binary into separate classes, based on the following outline:
https://drive.google.com/file/d/1AEXRliMcBJUR1WFC6Z7cHKE4SEM4ykH5/view?usp=sharing
What's new?

FedoraBinary is now the class retrieved at the path /binary instead of NonRdfSourceDescription
NonRdfSourceDescription now refers to /binary/fedora:description and contains the description of the binary
Binaries and descriptions now return their own caching headers instead of each others.
Subject of triples from NonRdfSourceDescription nodes are translated to the uri of the binary
Updates converters to resolve to new paths for binaries, simplifies logic.
Introduces leafNode nodetype, which is a non-abstract hierarchyNode without children

How should this be tested?
Changes are tested by existing FedoraLdpIT and FedoraVersioningIT.  Otherwise, they can be tested with regular binary interactions:
curl -i -XPOST -H "Slug:test_binary" -H "Content-Type: text/plain" --data-binary "binarycontent" "http://localhost:8080/" -H "Content-Disposition: attachment; filename=\"file.txt\""

curl -iv "http://localhost:8080/test_binary"
# Content-Type: text/plain
# Content-Disposition: file.txt
# link<describedby>: http://localhost:8080/test_binary/fcr:metadata
# binarycontent

curl -iv "http://localhost:8080/test_binary/fcr:metadata"
# link<describes>: http://localhost:8080/test_binary
# <rdf including filename, size, mimemtype>

This is a large change, so I'd be happy if any other @fcrepo4/committers wanted to have a look before I press the shiny green button.


Add message bus resource

Add a coordination resource for sending messages between nodes. This should look something like Vert.x's event bus. A message bus resource will use the Copycat state machine to coordinate subscriptions and separately start a Client and Server on each node. If a resource is opened multiple times on the same node, they should share the same server. This may require some minor refactoring to the resource API such as adding a resource factory.

9bad5314209732dc0abe90bafc1fa575768c57a4


Linux executable

It would be nice if there was a Linux executable available for download.

yeah I would need that for updating my server to 1.20.1 and resetting the end and nether with better end and better nether enabled which requires modifying the level.dat file


Dylan/publisher-editor-tool

About💡
New SpacetimeDB "Publisher" tool, acting as a SpacetimeDB GUI for creating/managing identites/servers, publishing, and viewing the last result cache of your previous publish [through the tool].
Designed in UI Builder with high-level and low-level scripts, this is designed to be scalable and intuitive to change.
See media section @ bottom for screenshots.
Why❓
The user could learn all the CLI commands and nuances, but automation and streamlining for an in-editor tool just feels amazing for both onboarding and veterans.
New users are already learning both the client and server side - potentially even learning Rust, on top of things. This tool should significantly lower onboarding friction and overall lower the learning curve.
Features📜

Runs cross-platform CLI commands in the background and parses them into friendly results
Detects and cross-platform installs SpacetimeDB CLI if !detected
View list of servers|identities
Add server|identity
Change server|identity
Ensure identities are bound to servers (refresh on server change)
FilePicker for publish/to/module path
Publish result with DateTime, Host, IsOptimizedBuild
Detection of wasm-opt for optimization; show install button if !found (in post-publish result cache)
Regenerate local|testnet servers if 0 servers found
Cleanly-exited Process via cancel token support
Progress bars and status labels
CLI Error handling
Some persistence cache, but we mostly get live updates from the CLI
UX: Prettified, responsive design, Local validation, groups, focus/selectAll when applicable, status labels, integrity checks, top banner click links to docs, body wraped in scrollView, fonts and colors match docs, can dock to editor UI as a tab.

⚙ Editor tool only: This won't bloat builds.
⚙ Tested in Unity 2022.3.20 LTS
Flow➡
New User

Init -> Detects and installs SpacetimeDB CLI (with progress bar)
Server foldout is revealed, prefilling the dropdown (selecting CLI default) -> If no servers, regenerate local + `testnet
Identity foldout is revealed, prefilling the default identity -> If no identities, show the "new identity" group (nickname+email)
Publish foldout is revealed, prefilling module name with a suggested one based on your client project name (lowercase-dashified-swaps-client-with-server) -> Browse path via FilePicker
Ready to Publish

Returning User

[Within a few ms] Init -> Load servers + default -> Load identities + default -> Load Publish name/path persistence cache -> reveal Publish button -> If previous session result cache found, reveal that dropdown (optionally minimized, dependent on persistence)
Ready to Publish

Media🖼

Reveal Media
Ready to Publish (Same UI as Returning User Init)

SpacetimeDB CLI !Detected
(Image broke - will replace next shift)
Add new server|identity

Choose a server

Publishing

Published, Optimized

Published, !Optimized

Editor view from eagle eye perspective:

Testing / TODO
💡The scope of this PR was made with testnet in mind, although there are some local feats. Although there are TODOs below, these should likely move to a new PR for scope's sake.

Tested in Unity 2022.3.20 LTS dark theme with C# spacetime init vanilla Module

Rust modules may have different results due to different CLI parsing results.
TODO: I noticed there's sometimes a false positive error when "creating" (not updating) - I wasn't able to repro it lately
TODO: Sometimes on successful success, it'll show a false-positive isOptimized (logs show !isOptimized)
TODO: More local server handling. We currently can't start/stop the local server - this first PR is initially made more with testnet in mind
TODO: Users may get confused (as I did) when they switch servers (eg: testnet to local) and it asks to create a new identity: Users may shrug and think "Oh ok, 1 per server" -- but the user will likely enter the SAME username as the other server and get confused when it says "id already exists" (yet, none show).

Perhaps an easy workaround is to call it a "global" identity? ...but that may assume it'd work everywhere.

TODO: Publish results should be copyable (readonly Labels don't allow highlighting the text), either via a copy btn or swapping to a readonly TextField

⚠Small warning: I discovered the proper short-statement if() standards later. Currently, you'll find many:
if (!isSuccess)
    return;

rather than:
if (!isSuccess)
{
return;
}

TODO: Do we want to add this to the README?

Added -c support

Added spacetime generate support

feat: On vague err, iterate output for the real errs to display them (+ log separately for tl;dr):

💡I'm only adding new feats/fixes to improve upon what should already be expected to be here since I'm using it on another project. I'm essentially testing this by eating my own dogfood.

feat: Add advanced mode dropdown for debug mode (--skip_clippy, --debug); also nested existing clear database in here

fix: isOptimized checkbox/install btn fixes (previously desync'd)

TL;DR
At this point, it's been vigorously tested by eating my own dogfood in another project, fixing as I encounter issues or expected common features, completely skipping CLI and solely using Publisher.

^

📢 Converted to draft since I'm very close to finishing up localhost features. After this, you will not need to use any CLI for the average dev except for SQL lookups.

New localhost feats are in, and fixed a ton of onboarding issues -- now fully tested. I'll post new screenshots and update the feats next shift for the localhost feat sets

Finished localhost feats, tested thoroughly, tested as a new user, fixed regressions -- ready for review again.

⚠ Repro'd an error with the auto-fixer for localhost that I'll remove and handle more-gracefully tomorrow. Keeping as draft for 1 more day.


Please correct documentation

Self-signed cert needs to be generated by below command for the HDI cluster to provision correctly.
New-SelfSignedCertificate -Subject .contoso100.com -NotAfter $lifetime.AddDays(365) -KeyUsage DigitalSignature, KeyEncipherment  -Type SSLServerAuthentication -DnsName ".contoso100.com","contoso100.com"
Errors encountered if not done via above command
,"ErrorCode":"DomainNotFoundInActiveDirectory","ErrorMessage":"Domain contoso100.com not found in the Active Directory."

com.microsoft.util.RetryException: com.microsoft.DomainOperationNonRetryableException: An SSL exception occurred while trying to communicate with the Active Directory. Make sure the certificate associated with the Active Directory is valid.

Caused by: java.security.cert.CertificateException: No subject alternative DNS name matching contoso100.com found.

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

ID: 41c4b68f-055e-3983-68dd-fc37c3f72da9
Version Independent ID: 0008043c-8703-85b4-ff09-3a087a65c29b
Content: Configure Secure LDAP (LDAPS) in Azure AD Domain Services
Content Source: articles/active-directory-domain-services/active-directory-ds-admin-guide-configure-secure-ldap.md
Service: active-directory
GitHub Login: @eringreenlee
Microsoft Alias: ergreenl

@aravish Thank you for your feedback! Could you link the URL of the documentation you were following? That way, we can pass your feedback to the appropriate content author.

https://docs.microsoft.com/en-us/azure/active-directory-domain-services/active-directory-ds-admin-guide-configure-secure-ldap

PowerShell script to be updated with below
$lifetime=Get-Date
New-SelfSignedCertificate -Subject .contoso100.com   -NotAfter $lifetime.AddDays(365) -KeyUsage DigitalSignature, KeyEncipherment
-Type SSLServerAuthentication -DnsName ".contoso100.com","contoso100.com"

@MarileeTurscak-MSFT please assign to me.

We reported this issue to the HDI team. They informed us this problem is resolved. Wildcard certificates always begin with an asterisk (*).
#please-close

It is worth mentioning that even if you do generate self-signed certificate using the command above, you can still face the very same error if the vnet you are deploying to is not configured with the IP-addresses of DNS servers for AADDS. I ran into this even though I had vnet peering with AADDS vnet configured.


Using width of parent element and adapting height to it

I would like to achieve that the mediaelement uses the full width that is available in the parent element. The height should be automatically adapted so no black borders are visible and the complete video is visible.
With older versions of mediaelement this was possible by setting css width and height of the <video> element to 100% and setting enableAutosize = false. This does not work anymore.
Since I assume that this most probably was not the correct way to do so, I would like to ask how to do this correctly.
Neither reading the documentation of stretching nor trying to understand the code really helped me to understand what is happening here. Is there any configuration option to achieve this?

Stretching as none and the enableAutosize as false must help you; if not please provide a Fiddle to check your issue and I’ll try to check it as soon as I can

Oh I see what's going on. Something is bypassing the stretching and setting the width of the container ahead of time. I'll check this and let you know when ready

Have you used stretching as responsive or fill for your task?

I used the demo file and added to the #container selector a specific width and I didn't see any issues with it

I found a bug when checking the native dimensions, so the responsive dimensions now should be properly set now; please download the master branch and let me know using the stretching as responsive

Sorry for the late answer. The solution for the bug you found fixed my problem. Many thanks for your quick and great help!

You are welcome. Glad it solved your issue. Please star the project to support it


feat- Added Bengali translation

I've made sure that the name of the app is pronounced the same as "Tracing Paper" even in the Bengali Language.
Short description of what this resolves
#46 Translated App to Bengali
Changes proposed in this pull request

created bn.json

registered bn.json in i18n.js.

Hey @Abhijit-Dixit ,
Thank you!
David


fix(fab-buttons): vertically align icons inside fab buttons

added .mat-fab & .mat-mini-fabto the vertical align definition of buttons

Caretaker note: do a global run for this one, be on the lookout for screenshot failures