perf: Add command to disable pull to refresh on crosswal

Type: perf
Platform: android 4.2 webview
Hello guys, i succeeded to run crosswalk on my android device, i notice that the pull to refresh used in chrome is also active on crosswalk and that is not correct for an application that should behave like a native one, i looked for a command to disable this and i found --disable-pull-to-refresh-effect.
i don't know how to inject this command to be used in crosswalk build.

Greetings @Rakonda!
My sensors indicate that I require more information in order to assist you.

Can you provide a detailed description of this issue?
How would a robot go about replicating this issue?
On which platform does this happen occur? (iOS, Android, all, etc.)
On which platform versions does this occur? (Android 4.2, iOS 8, all, etc.)
Is this an issue with the Ionic Framework or Ionic CLI?

Additionally, providing a codepen that replicates the issue is extremely helpful.
If you wish to get help using the framework itself, I recommended visiting the forum, where many humans will be able to offer wisdom and advice.
Thank you for allowing me to assist you.

Hey,
you need make a commad line file named "xwalk-command-line" and put it under assets folder of the apk with the format: xwalk --disable-pull-to-refresh-effect

Greetings @Rakonda!
My sensors indicate a reply was requested, but we have not received one yet, I am using my robot powers to close this issue. However, if you are still experiencing this issue, please feel free to reopen it by creating a new issue, and include any examples or necessary information.
Thank you for allowing me to assist you.


⚠ Bofrost.lu has degraded performance

In ea0f22d, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1740 ms

Resolved: Bofrost.lu performance has improved in 1286c44 after 6 minutes.


Github actions for more connectivity!

Closes #95

Auto comment on issue Closed and Opened
Auto comment on PR mergs
Auto comment on PR raises

Using this workflows makes you'r repo more interactive ! @rohitinu6
Note: Add all the labels and assign me to this PR !!

Proof:
Issue open and close:

PR raise and  merged:

@c0sm0void merge it!!

@smog-root have you gone through the comments and required changes?

@c0sm0void what changes??

@c0sm0void what changes??
everything is working perfectly!! fine!

Well everything not fine. You haven't read my comments.

@c0sm0void kindly assign this PR to me! there some issues in my leaderboard profile!


refactor(check-port): return found port

This will allow the angular cli to simply run on a different port in case the current port is occupied. This is super way more useful than receiving a warning from the angular-cli the port is in use.

The current behavior is intentional.  If the user specifies a specific port and it is not available, something is wrong.  This is especially important in test and CI scenarios.
Also, the behavior attempting to be achieved here is already available by passing “0” as the desired port.

I’m unsure if the cost outweighs the benefits. How many people want the process to exit when the port is not found versus how many want to simply use the cli to serve their application.
I didn’t know about the port 0 flag, that’s useful. But I personally think the default behavior should have been different.


Fix links to demo and docs

Rendered view
Replace offirgolan with ember-cp-validations in URLs
Note that link to v.3 docs is still broken as rawgit.com no longer works
Resolves #707 .
Tasks:

[x] Updated documentation

Merging since the current failures are expected and worked on in separate PRs.


Add Lucy Rust

@lpil not sure if you're accepting new Lucy logos on the branding page, if not then please feel free to close this :)

@lpil so strange - I didn't see it until I tried to zoom in and find what you were looking for. The act of zooming made it jut out for me.
I've just pushed a fix, seems to be fine now.


bring latest of 0.6.0 of main branch to fluent2token

Platforms Impacted

[x] iOS
[x] macOS

Description of changes
git merge main all the way up to commit 31d9cf71fc8d69b8f8e2f75b7b121e47ec9a3cea
Commit: 85953611cb93a3eac94a277da3d68634a1030144 clean merge with no conflict
Commit: 3edbaa60220ed9bea7a6ed9e05f5a08923d23e4f dealing with merge conflicts
Verification

Make sure macOS test app build and run
Quickly go through CCB, Avatar, AvatarGroup, TabbleViewCell, Other Cells, IndeterminateBar, Notification

Pull request checklist
This PR has considered:

[ ] Light and Dark appearances
[ ] iOS supported versions (all major versions greater than or equal current target deployment version)
[ ] VoiceOver and Keyboard Accessibility
[ ] Internationalization and Right to Left layouts
[ ] Different resolutions (1x, 2x, 3x)
[ ] Size classes and window sizes (iPhone vs iPad, notched devices, multitasking, different window sizes, etc)
[ ] iPad Pointer interaction
[ ] SwiftUI consumption (validation or new demo scenarios needed)
[ ] Objective-C exposure (provide it only if needed)

Microsoft Reviewers: Open in CodeFlow

Do we want to update the description with links to the commits that this PR brings in?


Add all scanned products to a list in a couple clicks

Problem
I was in the supermarket and scanned all the yoghurts in my store, to then add them all to a list. To look up later what the best ones were. I had to add them one by one after I scanned them all
Proposed solution
Ability to add all items that are currently still present on the 'search' screen to a list in one go.

Not sure what you mean exactly with the "search" screen.
That said, I believe that:

if you go to "history", you'll see all your recent products - in your case, all your recent yoghurts
a long click on one product will trigger the multi select mode
for the moment, you can only compare the products from there. If you could add selected products to a list instead, that would solve the issue, wouldn't it?

"If you could add selected products to a list instead, that would solve the issue, wouldn't it?"
Yes, that's what this issue is about.
I meant that in the 'search' tab (middle tab in the bottom of the app) (the main screen where you scan barcodes). If you scan a bunch of products there. So then you have 'compare x products' in the top right of your screen.
To add all those x products to a list. In one action

OK, I don't scan, that's why I didn't understand what you meant.
I don't like this screen either, but that's another story.
The problem with that particular screen is that we cannot put that many buttons; that would clog the display.
And the current choice is: "clear" and "compare all".
Instead of "compare all", we could go to a list page - where we could compare, select all, select none, copy to clipboard, copy to a local list.
That's a matter of UX choice. @teolemon your opinion on the subject?

Yes, adding a third button would be overkill,  instead we could just add a "Save as list" button in a 3 dot menu on the comparison screen

@M123-dev The thing is that

the "compare" screen is different from the "product list" screen
it does not propose multi-selection mode
it's not very intuitive to go to a "compare" screen in order to "copy to clipboard selected barcodes"

That said, we could imagine implementing the "..." with "copy to clipboard" and "copy to another list" in both compare screen and product list screen.
I had a go with the "history" screen (a "product list" screen), and added 2 features in the "..." ("Clear" was already there).
The idea would be to open the multi-selection mode for both "Copy to clipboard" and "Copy to another list"

@thibaultmol Would that suit your needs?
@M123-dev Please work on that!

I scanned 150+- yoghurts. That'd be 150 clicks (to select every product from the history) + a couple more.
But I think your solution would work BUT on the 'scan' screen you get when you click 'compare'. Since that would then automatically include all products from that scanning session

I guess if the plan is inded to have the ... menu which has the ability to add items to a list combined with the 'select all' button. Then yeah, that would solve this.
(glad the limit of 25 wasn't implemented. it's up to the user to decide how many items he wants to be selected all at once in my opinion)

@thibaultmol this issue should be fixed by now. There is a button for it in the compare page. If there is something missing feel free to reopen


Output directory?

Hi - I have limited space on my drive, so do my VM building on an external one. Would you accept a PR to add output_directory attributes that are settable via variables?

Certainly! I would possibly use a feature like that as well.


CI is not running tests

Today I have a PR that is not validated, this is the error on GitHub actions.
Basically GitHub is believing that this is a website only change and it is not performing tests

It happened at least in those two Pull requests:
https://github.com/apache/pulsar/pull/9448
https://github.com/apache/pulsar/pull/8590

This issue has been reported as https://github.com/apache/pulsar-test-infra/issues/12 . It's a bug in https://github.com/apache/pulsar-test-infra/blob/master/diff-only/entrypoint.sh .
The diff-only solution doesn't work well together with shallow clones. Because of performance and efficiency, the Pulsar workflows use a shallow clone of last 25 commits. That doesn't work together with diff-only solution when there are more than 25 commits in the PR.
This must be fixed asap. However, the diff-only solution is not necessary at all. There's a "paths-ignore" feature in GitHub Actions that makes the diff-only solution obsolete. I'll create a PR to make that change.

Changes to eliminate diff-only action completely in pulsar workflows: https://github.com/apache/pulsar/pull/9527
Fix to the bug in diff-only action: https://github.com/apache/pulsar-test-infra/pull/16

What's the status of this issue?


Hello !
No I haven't. I'm not familiar with lambdas, why would it cause a problem ?

If it requires a single statically-linked binary, than I recommend using the HiGHS solver, which is statically linked by default (in highs-sys).

I've pushed a demo here - if you have time would appreciate your thoughts.
The current error is this when using the Docker:
error: linker `x86_64-linux-musl-gcc` not found
  |
  = note: No such file or directory (os error 2)

error: aborting due to previous error

error: could not compile `hello_lp`

To learn more, run the command again with --verbose.

And also:
rustup target add x86_64-unknown-linux-musl

CROSS_COMPILE=x86_64-linux-musl- cargo build --release --target x86_64-unknown-linux-musl

The error seems to point vaguely to highs cpp


CSS styling from evitaDB docs in evitaLab markdown renderer

In evitaLab we use markdown renderer (https://github.com/markdown-it/markdown-it) for rendering schema descriptions and entity property values. Currently, the renderer renders only base HTML without any CSS styling, therefore it's not pretty and not much usable when the markdown source in more complicated. Also, we would like the rendered markdown to match styling from evitaDB docs.
After some discussion with @MiroslavAlt, the simplest way to implement this right now, will be to copy needed CSS classes from evitaDB docs into evitaLab. In future, we may consider publishing some CSS lib with the common classes, but for now this copying should be enough. More so because we need only subset of what evitaDB supports, as in evitaLab there is only plain markdown without custom React components.
Note: before we can realize this, we need to finish the entity property value detail, because there is implementation of the new markdown renderer.
cc @MiroslavAlt

Solved in #48.


2 Animations issues with blender 3.1.2

hello there,
I found another 2 animation issues, again frustrating because of blender versions.
the following issues are existing when exporting from blender 3.1.2 while they do not exist when exporting the same file from blender 3.2
Issue 1) - Blender bones constraints
given a rigged mesh (skinned mesh) like a human body, which is using blender bone constraints, for example IK constraint or Child of bone constraints (which are essential for animation making), the exporter is ignoring the baked NLA and showing me the T-pose (completely ignoring the constraints and the pose from blender)

Exporting the same identical file with blender 3.2 instead, the human is in the right pose and the animation is working

This is currently blocking my workflow, after I got the animation mixing issue solved (reported to you in the other thread you already resolved, the solution was to use blender 3.1.2).
Using blender 3.1.2 version I do not have the mixing NLA issue anymore but have now this new blender constraints issue which is even worse making animations not usable
This is where the constraints are located in Blender:

A few additional info:

I tried baking the NLA with visual keys and deleted all constraints from the armature (still does not work even if it should).
I tried with single NLA and multiple NLA stack, also with a default_State NLA
it's working fine with blender 3.2, so the issue is clearly blender 3.1.2 and not the model

Issue 2) - Animation with scale
Given a skinned mesh like a simple sphere rigged to a bone:

If that central bone has a scale animation from 0.1 to 1 size, (imagine an inflating balloon going from little to big and the big position is the default pose), the exporting results looks wrong in game using blender 3.1.2
The animation in game starts from scale 1 to 10x (from the big position to an even bigger one which is not existing in blender)
Exporting the same file with blender 3.2, the animation will look correct, inflating from 0.1 scale upto 1.0 size (from the tiny balloon to the default size one).
We are forced to work with Blender 3.1.2 because it comes with more benefits when using the Asobo exporter but... some stuff like these animation issues are unfortunately a big limitation.
Hopefully we can get a quick fix to all these animations issue, I really need them to work.
Thank you

is there any debug activity going on? any chance to get the issue above fixed soon?
I hope in a quick fix, this is important to keep moving with projects.
Thank you.

Hello !
Can you send me your Blend files to get the repro ?
Thank you

Hello !
Can you send me your Blend files to get the repro ?
Thank you
Animations_Issues_report.zip

Hello Y-khodja,
I have just created the 2 blend files that recreate the error and relative package file to test in game.
The 2 issues are explained in the post above. Just as a reminder, if you export with blender 3.1.2 the animations won't work correctly in game while if you export with blender 3.2, these will work correctly.
We are forced to use Blender 3.1.2 because it is the current supported version and it comes with additional advantages, unfortunately with this version we have animations issues that can't be solved, hopefully you can drop us a fix soon.
Thank you

We have released a new version of the exporter supported by Blender 3.3 you should use this one from now on as it's intended for an LTS version of Blender.

Hello !
Can you send me your Blend files to get the repro ?
Thank you
Animations_Issues_report.zip

Hello Y-khodja,
I have just created the 2 blend files that recreate the error and relative package file to test in game.
The 2 issues are explained in the post above. Just as a reminder, if you export with blender 3.1.2 the animations won't work correctly in game while if you export with blender 3.2, these will work correctly.
We are forced to use Blender 3.1.2 because it is the current supported version and it comes with additional advantages, unfortunately with this version we have animations issues that can't be solved, hopefully you can drop us a fix soon.
Thank you

We have released a new version of the exporter supported by Blender 3.3 you should use this one from now on as it's intended for an LTS version of Blender.

Hello !
Can you send me your Blend files to get the repro ?
Thank you
Animations_Issues_report.zip

Hello Y-khodja,
I have just created the 2 blend files that recreate the error and relative package file to test in game.
The 2 issues are explained in the post above. Just as a reminder, if you export with blender 3.1.2 the animations won't work correctly in game while if you export with blender 3.2, these will work correctly.
We are forced to use Blender 3.1.2 because it is the current supported version and it comes with additional advantages, unfortunately with this version we have animations issues that can't be solved, hopefully you can drop us a fix soon.
Thank you

Hello Y-Khodja,
thank you for mentioning the new exporter.
I am now running tests with 3.3 and relative msfs exporter version.
good and bad news:
the good news is that the 2 issues listed above are working with 3.3 version
the bad news is that other things that were working with before are now causing "export fail", that means the main project is not exportable anymore with 3.3.
I am going to try to isolate the issue and report them as a separate 3.3 threads.
The first one i found is that the export failes when a specific animation "action" exists in the blend file even if not exported (this is exporting with 3.1.2)


[sui-execution] Introduce Executor interface

Description
This will be the uniform interface through which requests are made to the MoveVM within nodes.  It allows us to easily bundle multiple versions of the VM, adapter, natives and verifier into node software, and switch between them according to protocol config.
Dynamic Interfaces
This change requires making previously static generics into trait objects, or shifting where the dynamism/ownership lies.

Access to execution will be via the new Executor trait object.
TemporaryStore's access to the backing store (now via the BackingStore grouping trait).
ObjectRuntime previously took a Box<dyn ChildObjectResolver>, now it's just a &dyn ChildObjectResolver.
Execution engine's access to the store (now via the ExecutionState grouping trait).
Type layout resolver's access to modules/packages etc (now via the TypeLayoutStore grouping trait).
LinkageView's access to the sui resolver traits is now via a trait object.

Some of these traits group multiple other traits, so extra functions have been added to do explicit conversion (e.g. from the vtable for an A + B trait object to the vtable for an A or a B trait object).
Other Changes

InMemoryStorage::new returns Arc
Don't save native functions in ExecutionComponents -- create fresh, each time (hides native function related types in execution layer)
Re-order function parameters for execution functions (only in newly introduced execution layer, will push this change down into execution implementations in a follow-up PR) to group together similar parameters.
genesis-related crates fully ported over to execution crate.
sui-replay fully ported over to execution crate.
De-nested implementation of get_object_read and get_past_object_read on AuthorityState.
sui-move/src/unit_test creates a lazy TEST_STORE instead of relying on the ObjectRuntime to keep the store alive.
sui-replay's LocalExec implementation of all the various backing store traits return SuiError instead of LocalExecError (now that we use dynamic dispatch, the error type needs to be standardised).
get_package_objects and get_packages helper functions on BackingPackageStore were previously default implemented trait functions, but they have turned into free functions.  This is because they are lifetime generic, and this interfered with the ability to use this trait (or any trait derived from it) as the basis of a trait object.
Removed temporary_store::empty_for_testing and ::with_input_objects_for_testing as unused, rather than port them (which would have been complicated and messy).
Replaced execute_transaction_to_effects with execute_transaction_to_effects_impl, to avoid doubling up the number of functions in the new Executor interface.

Test Plan
sui$ cargo simtest
sui$ env SUI_SKIP_SIMTESTS=1 cargo nextest run

Also manually test replay tool on a recent transaction digest:
sui/crates/sui-tool$ cargo run replay --rpc https://fullnode.testnet.sui.io:443 tx -t <digest>

I am not clear how this deals with multiple versions and I guess that is still to come.

answering myself, maybe here you mean over different epoch (and it must be that way) in which case the single VM per epoch store makes sense

I am not clear how this deals with multiple versions and I guess that is still to come.

Yes that's right, it's still to come -- the way it will work is throuh the executor function in sui-execution/lib.rs -- this function will eventually read an execution version from ProtocolConfig, and based on that, it will pick the implementation of dyn Executor that it returns.

This PR also made me realize the difficulty behind this issue (and maybe it is a difficulty for me only) which is that the VM and the Executor have totally different lifetimes.

I'm not sure I follow on this one -- Executor and VM are intended to have the same lifetimes, for the reason that you mention in your follow-up:

answering myself, maybe here you mean over different epoch (and it must be that way) in which case the single VM per epoch store makes sense

And for this reason, I kind of hold the opposite view to below (i.e. that it's easier to version the VM with the executor together, rather than separately).

on one hand that makes me happy because, as you know, I think multiple version of a VM for the same "executor" are realistic and we should do them (I know later), on the other hand versioning a VM together (or as a side effect) of the "executor" (adapter) seems hard.

With the work to remove Session etc, the line between the VM and the rest of the adapter layer is going to blur even further to the point where it will become less useful to version them separately because the adapter is so small.


[FLINK-1666] [FLINK-1903] [FLINK-3233] Refactor expression keys.

Unify usage of expression keys: FLINK-1666
Unify supported key expressions (incl. support for partitioning on atomic types: FLINK-3233)
Remove removal of duplicate keys: FLINK-1903
Unify checks for sort keys
Add more tests for SelectorFunctionKeys and ExpressionKeys
Fixed most compiler warnings in touched files

Sorry for merging several issues in this PR.
FLINK-1903 and FLINK-3233 are fixed as a side effect of FLINK-1666.

Any feedback for this PR? Otherwise, I'll merge it tomorrow.

I will merge this PR


Removed unsupported String.prototype.repeat() (IE fix)

Fixed https://github.com/lindell/JsBarcode/issues/155

Thanks again for the contribution :)


Interpolate column-level jinja in compiled manifest

Describe the bug
dbt supports the specification of jinja code in most parts of the schema.yml spec. In some (many?) places, interpolated jinja does find its way into dbt's SQL output, but the manifest contains the uncompiled source inputs.
Let's instead make sure that the compiled manifest contains compiled output for the columns key in compiled node objects.
Steps To Reproduce
# schema.yml
version: 2
models:
    - name: debug
      columns:
          - name: var('company_name')
            tests:
                - unique

This correctly runs a test against a column called abc:
dbt test --vars 'company_name: abc'

This renders a column called var('company_name') in the docs site:
dbt docs generate --vars 'company_name: abc'

In the manifest.json file, I see:
            "columns": {
                "var('company_name')": {
                    "name": "var('company_name')",
                    "description": "",
                    "meta": {},
                    "data_type": null,
                    "tags": []
                }

Whereas I would instead expect to see:
            "columns": {
                "company_name": {
                    "name": "company_name",
                    "description": "",
                    "meta": {},
                    "data_type": null,
                    "tags": []
                }

I think we can throw away the source-code level jinja here -- I'd expect to see the interpolated value, not the source var call, in the manifest.json file.
The output of dbt --version:
dev/octavius-catto

See also: https://github.com/fishtown-analytics/dbt-docs/issues/82

Closing this one -- we should add a constraint in the future that does not allow jinja in column names in the schema.yml spec. These fields should be treated as non-rendered plaintext.


Add ability to package a list of paths instead of single one

Changelog

Adds the ability to submit a list of str include paths to upload to the git packager (Tested)
Same for PackageArchive (though not fully tested)

similar change merged in #117


Updated example queries

Pointing customers to new Log Analytics query UI experience. Removed queries which are available in the Log Analytics query UI. Updated slightly the description.

@eva-seydl : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@eva-seydl : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@eva-seydl : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@eva-seydl : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Remove version: Peppy.Osu! version 2023.914.0

https://github.com/microsoft/winget-pkgs/issues/152768#issuecomment-2102735187

Resolves #152768

Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/ppy/osu/releases/download/2023.914.0/install.exe
OK
(Automated message - build 882)


netmaker: 0.20.5 -> 0.20.6

Description of changes
full changelog: https://github.com/gravitl/netmaker/releases/tag/v0.20.6
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 251134 run on aarch64-linux 1

2 packages built:

netmaker
netmaker-full


Add support for WGS84

I'm thinking in adding support for spherical GCS and WGS84 first and then we can discuss a properly GCS framework to build upon it. On the way at #1
About the API, I'm thinking in something like that:
package main

import (
        "os"
        "fmt"

        "github.com/NeowayLabs/gis/layer"

        // imports below add support for geojson and KML decoding
        _ "github.com/NeowayLabs/gis/encoding/geojson"
        _ "github.com/NeowayLabs/gis/encoding/kml"

        "github.com/NeowayLabs/gis/gcs"

        _ "github.com/NeowayLabs/gis/gcs/wgs84"
        // Uncomment line below to add support for SIRGAS 2000
        //"github.com/NeowayLabs/gis/gcs/sirgas2000"
)

func main() {
        shape, crs, err := layer.Open("./features.kml")
        if err != nil {
                fmt.Fprintf("Failed to load layer: %s\n", err.Error())
                os.Exit(1)
        }

        fmt.Printf("Loaded layer using CRS: %s", crs)

        shape2, err := gcs.Transform(shape, crs, "SIRGAS2000")
        if err != nil {
                // Uncomment the SIRGAS2000 import to work
                fmt.Fprintf("Failed to transform layer: %s\n", err.Error())
                os.Exit(1)
        }
        geojsonContent, err := geojson.Encode(layer)
        if err != nil {
                fmt.Fprintf("geojson encoder error: %s\n", err.Error())
                os.Exit(1)
        }
        fmt.Printf("%s\n", geojsonContent)
}

What do you guys think? @OctavioBR @vitor-tyburski @rzanato

I find well designed (and cool) your API but I think we would not need so much translation between different coordinate systems. At first let's stick to the simplest GCS, then when we get to support WGS84, we could stop maintaining others... Thoughts?


Segment MetaData mismatch between API's

The Creation Time Millis value received for a realtime segment from /segments/<table_name>/metadata API is not aligning with the value received from/segments/<table_name>/<segmant_name>/metadata API . I assume they denote the time when the segment started consuming .
Value received  for a segment from /segments/<table_name>/metadata :
{
    "segmentName": "segment_name",
    "schemaName": null,
    "crc":<PHONE_NUMBER>,
    **"creationTimeMillis":<PHONE_NUMBER>377,**
    "creationTimeReadable": "2023-05-29T21:03:03:377 UTC",
    "timeColumn": "timestamp",
    "timeUnit": "SECONDS",
    "timeGranularitySec": 1,
    "startTimeMillis":<PHONE_NUMBER>000,
    "startTimeReadable": "2023-05-28T21:01:39.000Z",
    "endTimeMillis":<PHONE_NUMBER>000,
    "endTimeReadable": "2023-05-29T21:02:26.000Z",
    "segmentVersion": "v3",
    "creatorName": null,
    "totalDocs": 1946111,
    "custom": {},
    "startOffset": "1498385432",
    "endOffset": "1500331543",
    "columns": [],
    "indexes": {},
    "star-tree-index": null
  },

Value received  the same segment from /segments/<table_name>/metadata :
{
  "segment.realtime.endOffset": "1500331543",
  "segment.start.time": "1685307699000",
  "segment.time.unit": "MILLISECONDS",
  "segment.flush.threshold.size": "2500000",
  "segment.realtime.startOffset": "1498385432",
  "segment.end.time": "1685394146000",
  "segment.total.docs": "1946111",
  "segment.realtime.numReplicas": "2",
  **"segment.creation.time": "1685307748436",**
  "segment.index.version": "v3",
  "segment.crc": "1641778138",
  "segment.realtime.status": "DONE",
  "segment.download.url": "<deepstore_path>"
}

The first metadata is returned from the server local metadata; the second metadata is returned from the ZK.
The creation time for the server local metadata is when the segment is created (consuming segment being committed and sealed), while the creation time for the ZK metadata is when the consuming segment being created. That is the reason why you see about 1 day difference between these 2 timestamps

Thanks @Jackie-Jiang  for the clarification. Should we enhance the first API to have a different naming convention for this property, say "segmentCommitedTime" to make it more explicit, as it kind of confuses ?

The creation time within the segment metadata (stored in the segment file) is the time when the segment is created. The creation time within the ZK metadata is the same as segment metadata for pushed segment, but different for consuming segment. We can consider always making the ZK metadata the same as segment metadata, or add a segment.realtime.creation.time to differentiate with the physical segment creation time

add a segment.realtime.creation.time to differentiate with the physical segment creation time

Thanks. This is more effective. I'll work on this change. Please assign this to me


Help appreciated to return back data from program HWTHRCVX to main program

Hi everybody,
I don't feel at ease with the pointers I guess, and I haven't found the way to get the data back from the RCVX program to the main program, that you have in the sample for POST method : SYS1.SAMPLIB(HWTHXCB2)
I can display the data of ret-data-ptr(J) in the Consume-Next-Response-Data paragraph, but then, I haven't found the way to set the data to the main program.
Can you help me setting correctly this ?

In the sample, recv-callback-udata is defined in WORKING-STORAGE SECTION. This matches with the recv-user-data structure declared In the LINKAGE SECTION of the HWTHRCVX callback.
In a program where you wish to save the received data, before starting the connection  you could allocate some storage and save the address of that area in your own pointer field within recv-callback-udata. Inside the callback, you can then copy from the ret-data-ptr(j) to your storage.
You probably also will need a "maximum capacity" field passing in that user callback area, with associated logic in the callback to prevent buffer overwrites.
If you are saving an offset in the user data structure, use a pointer to a pic 9(8), rather than declaring a pic 9(8) in the userdata itself. If I recall correctly, the callback routine takes a copy at the time of the HWTHSET operation and supplies that copy on every RCVX callback invocation. Updating anything in recv-user-data within the callback will not behave as expected.

Hello Ian, thanks for your help.
I've found how to get back the data, manipulating pointer and address of field was not my cup of tea haha.

That's good news @Thibaut69 - thanks for the feedback.
Agreed about COBOL pointer manipulation - never my first choice! :-)


The linked RFC is obsolete

The Readme linked RFC is obsoleted by https://tools.ietf.org/html/rfc8288
I'm reading it through and will try to understand the main differences to see if this still complies.

I've looked through the new RFC and, based on examples, this still complies; I'm gonna close it out and update the README.


Updates Mermaid docs

Fix the code snippet.
Updates sample image to make it compatible with dark and light modes.
Adds instructions to render the diagram source code.

👍, let's hold until the release of the Runme kernel that supports it.


Feature: added google analytics code

follow #479
account owner: @EvanDotPro
access: @gianarb

Thank you, @ins0!

thanks @localheinz


the connection failed

The wallet did not link successfully after jumping to the app，and will not return to the app。

Hi, I can't really help you without more information. I suggest you try the example app with the WalletConnect testing wallet and see if it works.

The issue is likely caused by the bridge servers taken offline with V1 sunset. If not, please reopen and provide more information.


Local Implementation of SWE agent does not work inside local Machine! (Local issue & Local repo)

Describe the bug
I am trying to resolve the issue of my project on my local machine. This is what I have done.
I cloned the SWE agent repo and put the keys.cfg and just hit ./setup.sh to run it (docker successfully ran).
After that, I pasted this command to run:
python3.9 run.py --model_name gpt4 --data_path "\\wsl.localhost\Ubuntu-20.04\home\uzair\swe-agent\data_path" --repo_path "\\wsl.localhost\Ubuntu-20.04\home\uzair\swe-agent\repo_path" --config_file config/default.yaml --per_instance_cost_limit 2.00 --apply_patch_locally

Whereas, datapath = \wsl.localhost\Ubuntu-20.04\home\uzair\swe-agent\data_path (This is my directory, there I have txt file named issue, inside this text file I asked issue to resolve).
Repo_path = \wsl.localhost\Ubuntu-20.04\home\uzair\swe-agent\repo_path   (This directory contains the test.py file which has issues on it.)
The problem is when I try to paste this command >
python3.9 run.py --model_name gpt4 --data_path "\\wsl.localhost\Ubuntu-20.04\home\uzair\swe-agent\data_path" --repo_path "\\wsl.localhost\Ubuntu-20.04\home\uzair\swe-agent\repo_path" --config_file config/default.yaml --per_instance_cost_limit 2.00 --apply_patch_locally

It shows some errors. Attached for you to look at this. I am not sure where I am mistaken or if your repo has issues. Am I giving paths correctly?

Steps/commands/code to Reproduce
python3.9 run.py --model_name gpt4 --data_path "\wsl.localhost\Ubuntu-20.04\home\uzair\swe-agent\data_path" --repo_path "\wsl.localhost\Ubuntu-20.04\home\uzair\swe-agent\repo_path" --config_file config/default.yaml --per_instance_cost_limit 2.00 --apply_patch_locally
Error message/results

System Information
I am using windows base subsystem Linux having core i7 8 gen, 16 gbs ram.
Checklist

[X] I'm running with the latest docker container/on the latest development version
[X] I've searched the other issues for a duplicate
[X] I have copied the full command/code that I ran
[X] I have copied the full log file/error message that was the result (if applicable)
[X] I have enclosed code/log messages in triple backticks (docs) and clicked "Preview" to make sure it's displayed correctly.

The error message here is unfortunately very unclear, because data_path can handle a lot of different inputs.
But your mistake is probably that you point data_path at a directory, rather than a text file with a problem statement.
Our new documentation now has a concrete example for using local repos/files that you can try.

Btw, please don't put screenshots of error messages, just copy them as text!


Birth By Sleep BBSx extractor

I am missing some kind of documentation regarding the .DAT archives.

I am missing some kind of documentation regarding the .DAT archives.

Ooops. I will do that. Do not accept the PL before that then

Documentation written B-)


Fix assertion in test_type_engine_binary_idl

Why are the changes needed?

The assertion on main is not always true, and pytest raises this warning:
/home/runner/work/flytekit/flytekit/tests/flytekit/unit/core/test_type_engine_binary_idl.py:608: SyntaxWarning: assertion is always true, perhaps remove parentheses?
  assert (type(inner_dc), InnerDC) # type: ignore

What changes were proposed in this pull request?

This PR fixes the assertion to actual check the types.

Learn from you again, thank you @thomasjpfan


feat!: add support for string slices

Add support for str in prevision for https://github.com/FuelLabs/sway/pull/4778
Checklist

[x] I have linked to any relevant issues.
[x] I have updated the documentation.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] I have added necessary labels.
[x] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[x] I have requested a review from the relevant team or maintainers.

How does this interact with/nullify #1042?

How does this interact with/nullify #1042?

I was also wondering about this. It seems like your work on #1042 is for a feature that already exists in the language. And what @IGI-111 is working on is for a future feature. Not sure how these two features interact in the compiler, or if one replaces the other.
@IGI-111, let us know your thoughts.


Feature Request: Summon

We have a Summon streaming API implementation which many customers have enjoyed. The new third party apps API authentication doesn't support streaming API authentication, so users lose the ability to use Summon.
It would be great to add Summon to the new vehicle command protocol so it covers the full range of vehicle controls.

Summon with the Apple Watch has always been clutch. Sad to see this functionality go. Would be amazing to have it back again and before the next holiday update.

Please restore this

It is very unfortunate that Smart Summon cannot be run on other apps. I hope it returns to normal as soon as possible.

Tesla's own summon feature is not so finished - Tessie had refined that functionality and it should be available to Tesla owners and NOT restricted by Tesla Corp.

Bring it back to Tessie so we can do it from our watches.  All the stooopid people who shouldn’t have FSD since they’re dumb are ruining it for the rest of us, causing Tesla to restrict implementation & more aggressive development.  I think those drivers should’ve
_never_traded in their Volvos’!


Ability to return from preview mode using  key

Added code to app/controllers/editor.coffee so that if <Esc> key is pressed in preview mode, Springseed returns from preview mode. Thought this functionality would be useful.

Thanks!


B901: Misses yield sub-expresisons

A very contrived example but B901 misses yield expressions where they're not the expression of a ExprStmt.
def get_file_paths(file_types: Iterable[str] | None = None) -> Iterable[Path]:
    dir_path = Path(".")
    if file_types is None:
        return dir_path.glob("*")

    for file_type in file_types:
        (yield a for a in dir_path.glob(f"*.{file_type}"))

Note: we should make sure that we don't traverse into any lambda expressions...

hmm, I only tested with our parser. nested yield expressions are definitely valid :)

Okay, found one
async def main():
    await (yield x)

Here's another function that is a generator function with a return statement and is not flagged by B901:
def f():
    x = yield
    print(x)
    return 42

This is a generator function that you can send values into:
>>> def f():
...     x = yield
...     print(x)
...     return 42
...
>>> y = f()
>>> next(y)
>>> y.send('foo')
foo
Traceback (most recent call last):
  File "<python-input-13>", line 1, in <module>
    y.send('foo')
    ~~~~~~^^^^^^^
StopIteration: 42

Sending valued into a generator is, like returning values from a generator, quite an advanced feature. So if I saw a function like this in code review, I would assume the user knew what they were doing. That doesn't feel like a very principled reason not to emit B901 on it, though; maybe we should. Not sure.

Hi @MichaReiser @AlexWaygood  can I help you fix this issue ?

Sure. You can find the code for this rule in this file
https://github.com/astral-sh/ruff/blob/b7e32b0a18487e8c9813e0d189d7a5d625ff5c3f/crates/ruff_linter/src/rules/flake8_bugbear/rules/return_in_generator.rs

Thanks @MichaReiser excited to work on this !


Update nexus_upload action to allow for flexible nexus mount paths and enable logging

Addresses issue: https://github.com/fastlane/fastlane/issues/1303 by allowing the Nexus mount path to be provided as part of the endpoint parameter.
Note: This would be a breaking change to anyone using the nexus_upload action previously. It will require them to explicitly add /nexus to the end of their endpoint parameter. I believe this is the best course for this fastlane action but if others feel strongly the other way I can modify the change to include an optional nexus_path parameter that would default to /nexus.
Also addresses issue https://github.com/fastlane/fastlane/issues/1304 by enabling logging based on the verbose parameter.

@xfreebird as the original author of the nexus_upload action, just wanted to make you aware of this PR.

@chrisgibbs Thanks !
Regarding of mount path, I wasn't aware of that. But would prefer not to break the compatibility.
I think the best approach would be to add a new optional option named mount_path, that by default would be nexus.
In this way the plugin wont break for current users, and you'll fix your issue.
What do you think ?

@chrisgibbs Thanks for the ticket and contribution! :+1:
I agree with @xfreebird's proposal here around making sure existing users of the action keep functioning as before.

@xfreebird @mfurtak Sounds good. I'll make the necessary changes.

Ok, should be good to go now.

Looks great to me - just left one small comment. How's it look to you @xfreebird?
After that, if you can squash down to one commit, I think we can get this in! :+1:

@mfurtak It looks good, thanks !

Merged as #1325


Update go information

Initial support for WASM is incoming https://go-review.googlesource.com/c/go/+/102835

Go lang document has been updated


Version documentation through release tags

("Version" is a verb here)
Is your feature request related to a problem? Please describe.
Our documentation tracks the repo's master branch, so when a feature has been pushed to master but has not yet been released, it will confusingly appear in documentation but not in any released version of ddev.
Describe the solution you'd like
ReadTheDocs supports versioned documentation by tracking tags, which will allow us to effectively stage changes to documentation until features are released publicly. This will also allow users to find documentation corresponding to the version of ddev they're using if it's not the most current version.

Yay @andrewfrench - Could you get the keys to the kingdom on this from @tannerjfco and this will be an excellent move. We probably should figure out how to use the company paid readthedocs instead of (free?) account we're using.

Yes, this seems like a great time to consolidate into one paid account. I tried chasing down the ddev readthedocs instance and just ended up very confused, but it sounds like @tannerjfco's the guy to talk to.


Adhoc tests are not updating the summary markdown

The adhoc recipe is not using the run_test step and it is not updating the summary markdown.

Fix in this CL: https://flutter-review.googlesource.com/c/recipes/+/12161


Font fixes

This PR addresses the following jira issues: 992, 997, and 1003.

Made text size same for narrative and tabular
Renamed "Pathology Results" section to "Pathology"
For issue 1003, after talking with @gregquinn2001 , @Dtphelan1 , @jafeltra , and Edwin, removed italics and instead made the section identifiers have a horizontal line to separate the sections. Decreased weight of section and column headers

Pull requests into Flux require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable (N/A) and :white_check_mark:.
Submitter:
Running the Application

[x] Manually tested in Chrome
[x] Manually tested in IE

Documentation

[x] This pull request describes why these changes were made
[x] Recognizes any potential shortcomings/bugs in the description
N/A Cheat sheet is updated
N/A Demo script is updated
N/A Documentation on Wiki has been updated
N/A Additional technical components and libraries are documented and added to wiki as needed

NoteParser

N/A Note parser has been updated if structured phrases change

Code Quality

[x] 4-space indents - convert any tabs to spaces
N/A Use public class field syntax for binding functions - ex. handleChange = () => { ... };
[x] Code is commented

Tests

[x] Existing tests passed
N/A Added UI tests for slim mode
N/A Added UI tests for full mode
N/A Added backend tests for fluxNotes code
N/A Added note parser examples to test new functionality

Reviewer 1: Name

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2: Name

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Looks good to me! All the issues in the jira items are fixed and all the tests pass!


Saving to iOS Photos - or a more easily accessible directory

This is possibly a feature request - or just, generally, whether you have any insights on saving the resultant gif locally in a directory that can be accessed on-device

https://gist.github.com/yosun/61413dd247ce52ae9807eb93c9b673ea
https://gist.github.com/yosun/89f256b66141ec914e2b54c66c91c798

Not sure if I should submit a pull request to add save to Photos Gallery iOS plugin - but gist is above for anyone who needs it


Improve the UI of the "empty" state for lists

I think we need to scope this out more. What exactly do we mean by improving it? Need to figure out what would better then we can design it and update the lists.


Hot can extract text data from the  tag ?

Example:
`

 John

`
I have to extract name of the person "John".

element.text() is not able to extract  tag. Jsoup does not read  tag then what should I do?

Can you post your HTML again using Code formatting? It disappeared so it's hard to tell what you want to achieve.

(I fixed @sarika34's formatting.) Yes, element.text() will get it. I don't know what is giving you the impression that jsoup doesn't read the font tag? You can see that it does here: https://try.jsoup.org/~j7sto8f5whimg_0n1W6pEowh4rc
Please post a testable code snippet if you're still having issues.


REQ: Connect to a remote mycroft instance via websockets

This would allow paring with a remote instance of mycroft in the same manner as the android client.

Will add support for IP and Port number in the next release or so.

Awesome :)
Sent on the go with Vodafone
-------- Original message --------From: Rahul Mehra<EMAIL_ADDRESS>Date: 21/4/17  11:55 am  (GMT+10:00) To: lolstring/gnome-shell-extension-mycroft<EMAIL_ADDRESS>Cc: chrisvella<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [lolstring/gnome-shell-extension-mycroft] REQ: Connect to a remote mycroft instance via websockets (#2)
Will add support for IP and Port number in the next release or so.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/lolstring/gnome-shell-extension-mycroft","title":"lolstring/gnome-shell-extension-mycroft","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/lolstring/gnome-shell-extension-mycroft"}},"updates":{"snippets":[{"icon":"PERSON","message":"@lolstring in #2: Will add support for IP and Port number in the next release or so."}],"action":{"name":"View Issue","url":"https://github.com/lolstring/gnome-shell-extension-mycroft/issues/2#issuecomment-296011842"}}}

Hey.
I have updated this git with remote ip support. I am not pushing this just yet to extensions.gnome.org.
You can download the zip of the extension from the DIST folder and install it from tweak tools.
If you face any errors let me know. I am keeping this open for another day in case an error pops up.


Coding error - incorrect test

The condition https://github.com/DVBProject/DVB-I-Reference-Client/blob/ebe7e23d1cec96174e9ff530ca46941e800df2ff/frontend/hbbtv/dialog.js#L27 seems to be incorrect-there is no variable q defined

Not a bug


unable to get kill-ring to work in vi-mode

First, thank you! such a great plugin!!
The kill-ring works out-the-box on emacs mode but unable to on vi-mode, is there a way?
Thanks again!

Yes, there is a way, but I need to implement it first. Coming soon.™ 🙂

All right, it's there. Enjoy!

If you use my software on a regular basis, please consider sponsoring me. 🙂

Thank you @marlonrichert !!!
I have a problem, was wondering if it is the same for you too?
~ ❯ zsh -f        # No Configs.
% bindkey -v   # Vi Binds.
% source ~/zsh-edit/zsh-edit.plugin.zsh  # Awesomeness!
# add to killring:
% aaa<ESC>yy
% bbb<ESC>Vy
% ccc<ESC>dd
% ddd<ESC>Vd
# Bindings:
% bindkey -M vicmd '^Y' yank-pop    # Ctrl+y
% bindkey -M vicmd '^[y' reverse-yank-pop    # Alt+y
% <ESC><C-Y>
aaa  bbb  ccc  ddd

Looks great! but unfortunately, subsequent keypresses (Ctrl+y/Alt+y) do not cycle the killring,  but if I was to:
# Map "y" to "yank" instead of "vi-yank":
bindkey -M vicmd y yank

It will work perfectly!, only problem is thay emacs "yank" doesnt accept vi motions.
Thank you again for adding vi support, its really appreciated!

unfortunately, subsequent keypresses (Ctrl+y/Alt+y) do not cycle the killring

As mentioned in the Readme, pressing (reverse-)yank-pop by itself merely shows the current contents of the kill ring. It doesn't insert anything.
 After that, you can cycle through the kill ring with yank-pop and reverse-yank-pop.


[2.5] Update OKE cluster driver.

This PR is a 2.5 back-port of this PR.

https://github.com/rancher/rancher/issues/29124
https://github.com/rancher/rancher/issues/29724


default support for ptex ?

With the graphics.cfg as maintained here you get an error from:
\documentclass{article}

\usepackage{graphicx}
%\usepackage[dvipdfmx]{graphicx}

\begin{document}

abc

\includegraphics{example-image.pdf}

\end{document}

Should this graphics.cfg detect ptex and variants and default to dvipdfmx ? (@aminophen )

Same for upTeX.

Sigh, I posted this to the wrong place, I'll move to graphics-cfg..


Documentation for 2019.4

Need to update documentation for FastReport.OpenSource 2019.4. Use DocFX to build documentation. Also try to build a PDF.

Task list:

[x] Fork, clone and obtain a copy of documentation and FR repo.
[x] Build a new documentation for reference
[ ] R&D for PDF plugins for DocFX
[x] Try to create PDF documentation for FastReport.OpenSource

Related links:
Documentation
DocFX

FastReports Documentation.pdf
ClassReference Documentation.pdf


Improved detecting SPFx React projects solving #968

Improved detecting SPFx React projects solving #968

Coverage remained the same at 100.0% when pulling 9f74c8220e7d6343717a87c4fc0687422cff683d on waldekmastykarz:fix-spfx-upgrade-182 into 9c2b66553399a2db863b63352f2f84f662cb7d61 on pnp:dev.


How do I add this library to my angular2 app?

I imported this lib in my webpack bundle and declared it into my component with
declare let InfoBubble: any;

@Christopher2K can you show a demo code

I've downloaded the info bubble.js file. I put it in one of my public folder and imported it in my main.ts


Utilize pre-defined annotation keys from OCI Image Format Specification

The OCI Image Format Specification defines a set of annotation keys that can be used to attach metadata (like the source of an artifact, or the build timestamp) in a standardized manner to a container image (or OCI artifact).
Some of these are interesting to Kargo to improve (for example, build time instead of push time for sorting), enrich (for example, determining the source of a container image for other registries than GHCR), or further extend the metadata we gather for an image artifact which is part of a Freight.
As the adoption of this is quite mature 1, 2, I think it would be wonderful to see if and how we can better utilize these within Kargo.

I especially like the potential to use this to connect the dots from an image back to the repo with the source the image was built from.

That's indeed also one of the use cases I had in mind myself.
The other one, is starting to use org.opencontainers.image.created instead of the (push) timestamp we receive from the registry when we order by build time. The advantage of this, is that these annotations can be transferred to any other registry, which could prevent potential issues when people move to e.g. an in-cluster mirror or a different registry host.

I think this feature can be as simple as surfacing OCI metadata into the freight. Then, other Kargo features (https://github.com/akuity/kargo/issues/2830, https://github.com/akuity/kargo/issues/821) will take advantage of that metadata as UI or git commit features.


pyproj and owslib to be removed from the depencies?

Since the CSWSearch plugin isn't used by EODAG as WEKEO isn't supported.

This is related to:

#104: because a QGIS plugin may crash due to these dependencies, see https://github.com/qgis/QGIS-Enhancement-Proposals/issues/202#issuecomment-787512133
#94 and #15, because even if CSWSearch plugin is not used for the moment, some other providers like CEDA may need it in the future.

What can be done for the moment is to temporally remove these dependencies and the CSWSearch plugin, as the QGIS plugin should be a great feature.
And if we decide to support CEDA, or another provider using CSW, then we should update the CSWSearch plugin to make it work with QGIS.

pyproj was removed from OWSLib >=0.27.1 dependencies, and also from eodag in #1021


Support to track the timestamps at a per-filter basis

Issue Template
Title: Support to track the timestamps at a per-filter basis, including plugin filters
Description:
Envoy does not record the timestamps at each filter level. It will be very helpful to debug the request latency bottleneck if we know following information at each filter: the request arrival time, request departure time, response arrival time and response departure time.

This seems a reasonable generalization of what RequestInfo tracks today and could be done in HCM.

Agreed this sounds very useful perhaps on an opt-in basis.

As per offline conversation, I think it's worthwhile thinking about this at the connection level as well.

So, how's the matter going? Is there any improvement or implementation on that?
I would be helpful if can record fine-grained duraton in downstream connection/stream, such as filter and router.

So what exactly do we want, a log print happens on every entrance and exit of HTTP filters to track per request/response, or a histogram for statistics?

@zhxie I think both would help

Log to debug a specific request
histograms to see how a specific filter is doing over a period of time
We recently had a production incident due to a slow running filter and it was difficult to debug and find the cause with out these logs/metrics.


NPE while reading Multiple Partitions

Hi Guys, we have integrated spark-acid library into our production pipeline and recently started facing an issue while reading data from a lot of partitions. Below is the stack trace -
Caused by: java.lang.NullPointerException 	at org.apache.hadoop.conf.Configuration.<init>(Configuration.java:820) 	at org.apache.hadoop.mapred.JobConf.<init>(JobConf.java:440) 	at com.qubole.spark.hiveacid.rdd.HiveAcidRDD$.getJobConf(HiveAcidRDD.scala:457) 	at com.qubole.spark.hiveacid.reader.hive.HiveAcidPartitionComputer$$anonfun$2.apply(HiveAcidPartitionComputer.scala:73) 	at com.qubole.spark.hiveacid.reader.hive.HiveAcidPartitionComputer$$anonfun$2.apply(HiveAcidPartitionComputer.scala:69) 	at scala.collection.Iterator$$anon$11.next(Iterator.scala:410) 	at scala.collection.Iterator$class.foreach(Iterator.scala:891) 	at scala.collection.AbstractIterator.foreach(Iterator.scala:1334) 	at scala.collection.generic.Growable$class.$plus$plus$eq(Growable.scala:59) 	at scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:104) 	at scala.collection.mutable.ArrayBuffer.$plus$plus$eq(ArrayBuffer.scala:48) 	at scala.collection.TraversableOnce$class.to(TraversableOnce.scala:310) 	at scala.collection.AbstractIterator.to(Iterator.scala:1334) 	at scala.collection.TraversableOnce$class.toBuffer(TraversableOnce.scala:302) 	at scala.collection.AbstractIterator.toBuffer(Iterator.scala:1334) 	at scala.collection.TraversableOnce$class.toArray(TraversableOnce.scala:289) 	at scala.collection.AbstractIterator.toArray(Iterator.scala:1334) 	at org.apache.spark.rdd.RDD$$anonfun$collect$1$$anonfun$13.apply(RDD.scala:945) 	at org.apache.spark.rdd.RDD$$anonfun$collect$1$$anonfun$13.apply(RDD.scala:945) 	at org.apache.spark.SparkContext$$anonfun$runJob$5.apply(SparkContext.scala:2101) 	at org.apache.spark.SparkContext$$anonfun$runJob$5.apply(SparkContext.scala:2101) 	at org.apache.spark.scheduler.ResultTask.runTask(ResultTask.scala:90) 	at org.apache.spark.scheduler.Task.run(Task.scala:121) 	at org.apache.spark.executor.Executor$TaskRunner$$anonfun$10.apply(Executor.scala:402) 	at org.apache.spark.util.Utils$.tryWithSafeFinally(Utils.scala:1360) 	at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:408) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at java.lang.Thread.run(Thread.java:748)
All our tables are Hive ACID tables and our partitions have a two-level nesting based on date and are created dynamically. The read works perfectly fine if we execute it in smaller chunks. Has anyone faced this issue?

Hi @adiu19, Seems like some bug in boradcasting Jobconf. Can you set this config to really high value so that it bypasses this code path spark.hiveAcid.parallel.partitioning.threshold ? This should be set more than your number of partitions.

@amoghmargoor thanks a lot, this worked. Are we planning to address this bug in any upcoming release?

@adiu19 yeah will take a look at it for next release. thanks for reporting. Just curious - which company do you work for ?

@amoghmargoor looks similar to the kryo serialization  issue.

@maheshk114 in that case i believe it should have failed without the flag being disabled too. but anyways a good point to consider. @adiu19 Can you check if you guys were using Kyro on your end ?

@amoghmargoor : we aren't using Kyro on our side.


Version tags

Hi Paul,
I am preparing to package your extensions on postgres.pm – would it be possible to tag releases in this repo? This makes it so much easier to pick up releases automatically.

Oh yes, I should be doing that. I tagged the last few versions. Let me know if you need more.

Thanks! Looks like agg_for_vecs got tags, but not this repo yet

I see tags. Can you look again?

Can see them now. Maybe github ui was lagging to show these when I checked
first.
Thank you!
On Wed, Dec 4, 2024, 11:46 a.m. Paul A Jungwirth @.***>
wrote:

I see tags. Can you look again?
—
Reply to this email directly, view it on GitHub
https://github.com/pjungwir/aggs_for_arrays/issues/5#issuecomment-2516185574,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAADRAKPN7IJF5U5VXLJQ32D2CIZAVCNFSM6AAAAABS6Z2NBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJWGE4DKNJXGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


chore(master): release 2.1.41

:robot: I have created a release beep boop
2.1.41 (2024-04-04)
Bug Fixes

deps: update dependency cycle/database to v2.10.0 (eac4e1e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-stripe-webhooks/releases/tag/v2.1.41 :sunflower:


bug: build vite-ssg error document is not defined

steps
pnpm  create valaxy
pnpm build

It means you must set a fixed URL like https://example.com/ for config.url .

config.url is a URL can be visited in network. Otherwise, '/' makes no sense for RSS.


feature: allow join project across domain

这个 PR 实现什么功能/修复什么问题:
改进：keystone增加选项allow_join_projects_across_domains, 为true时允许任意域的用户加入任意域的项目，默认为false。

是否需要 backport 到之前的 release 分支:

release/3.4
release/3.5

/cc @zexi @yousong
/area keystone

Codecov Report

Merging #8771 (f10267b) into master (bb6882f) will increase coverage by 11.90%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #8771       +/-   ##
===========================================
+ Coverage    5.94%   17.84%   +11.90%
===========================================
  Files         818       88      -730
  Lines      127129     8848   -118281
===========================================
- Hits         7553     1579     -5974
+ Misses     118898     7096   -111802
+ Partials      678      173      -505

Flag
Coverage Δ

aFlag
17.84% <ø> (+11.90%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/compute/regiondrivers/ucloud.go

pkg/compute/models/loadbalanceracls.go

pkg/mcclient/options/routetables.go

pkg/cloudcommon/db/opslog.go

pkg/monitor/tsdb/driver/influxdb/query.go

pkg/compute/models/guestdisks.go

pkg/appsrv/fetch.go

pkg/util/iproute2/route.go

pkg/keystone/models/regions.go

pkg/mcclient/options/loadbalanceragents.go

... and 718 more

Continue to review full report at Codecov.

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


[add] capture browser console logs on rspec

Coverage decreased (-7.7%) to 70.665% when pulling 9ca637614b3558b3b33065f23f6a9e07b9d8c77d on sunny4381:features/capture-browser-console-log-on-rspec into 1131f3f9626c98c541ac823c869e9a64500d4341 on shirasagi:master.


Direct (non-maven) downloads of lombok.jar should no longer be hosted at googlecode.

Migrated from Google Code (issue 622)

Migration done in e453c2fafab13c066a7260434f0c08f61e437c8b, 315671e79d118de718ae53b664878dd168f70ca2, e437ff4d3c84102092d6da0f1478cc54fcd84844, et al. I suggest you create a new issue for the download counter if you still want it.


remove/refactor get_run_critical_tests, use CI instead

see
https://github.com/abapGit/abapGit/issues/3953
https://github.com/abapGit/abapGit/pull/3711
zcl_abapgit_persist_settings=>get_instance( )->read( )->get_run_critical_tests( )

done, closing


Release 23.4

coverage: 91.049%. remained the same
when pulling b90d05955b444e8f6e6b03b020aa94b18fcda6c4 on release/23-4
into 7ee08be189293f07e75d2d249501564754a3833c on main.


Cannot install watchdog timeout on STM32WB

Describe the bug
iwdg_stm32_install_timeout does not return because it is stuck inside while (LL_IWDG_IsReady(iwdg) == 0) loop.
It looks like k_uptime_get_32 returns the same value for every call.
Please also mention any information which could help others to understand
the problem you're facing:

STM32WB55 clocked by PLL (based on HSE), with enabled tickless kernel (LPTIMER with LSE).
CONFIG_WDT_DISABLE_AT_BOOT is enabled.
After adding 3 NOP instruction to (mentioned above) while loop timeout is properly detected.
For some reasons busy timeout polling with k_uptime_get_32 does not work well.

To Reproduce
Steps to reproduce the behavior:
Build with IWDG enabled and with CONFIG_WDT_DISABLE_AT_BOOT configuration option set.
Try to run application.
Expected behavior
iwdg_stm32_install_timeout should return with -EINVAL error.
Impact
showstopper
Logs and console output
Environment (please complete the following information):

OS: Linux
Toolchain Zephyr SDK, 0.14.1
Commit SHA d92e3b88bacc6e6fc1b6222421ef4accdf2d574e

Additional context
During call to iwdg_stm32_install_timeout the IWDG is disabled because LL_IWDG_Enable was never called before and then LL_IWDG_IsReady will always return 0.
LL_IWDG_Enable was not called before because of CONFIG_WDT_DISABLE_AT_BOOT is set.
It means that present implementation may be incorrect because LL_IWDG_Enable will be called during wdt_setup which (according to documentation) will happen after call to wdt_install_timeout.

@r2r0  could you please check if PR #44989  helps

Thanks @FRASTM - in fact this PR removes the trigger of described problem.
After applying #44972 CPU leaves the while loop and the timeout hangout is avoided but it is still present.

When you build the samples/subsys/task_wdt with CONFIG_WDT_DISABLE_AT_BOOT=n
(by default in the prj.conf  the CONFIG_WDT_DISABLE_AT_BOOT is 'y')
the timeout is installed during the initialisation of the device, with the same sequence as in install_timeout

Unfortunately blocking of while loop is visible only very rarely when console and debugger (even without breakpoints installed) are connected. When it happens then it looks that also LPTIM ISR is not working.
After power cycling problem disappears (usually) for long time.
Because I am not able to consistently reproduce problem then I will close this issue for now.
BTW> @FRASTM  would it be possible to advance merging of the #44972, please.


Slow deserialization

Hello, I did some benchmark against Bond vs a bunch of other binary serializers and the results are fascinating.

Bond produces the smallest payload and has the fastest deserialization speed by some margin, but is also the slowest at serialization (almost 2x slower than BinaryFormatter in this case).
Was this a design decision to optimize for payload size and deserialization speed so in a simple client-server setting you're optimized for the server side of the equation? But doesn't this start to break down in the increasingly popular service-oriented architectures where there are a lot of server-to-server communications?
Love to hear your thoughts on this.

Thanks for adding Bond to your benchmark.
The likely cause of slow serialization in this test is this line. OutputBuffer by default uses 64 KB initial buffer size, which is often a good choice in real world services but obviously bad for a micro benchmark with 40 byte payload: the serialization time is dominated by allocation of 64 KB buffer which in .Net results in zeroing out the memory.
To measure actual serialization cost you can configure the the OutputBuffer to a smaller initial size. You don't need to know the exact size, it will reallocate if necessary, but for the best performance you should try to tune it such that you avoid both over-allocation of initial buffer and too much reallocation required to grow.
See also: tuning Bond performance.

Thanks, that made a huge difference!

which brings up another related question - are you using a buffer pool already? wouldn't that mitigate the cost of constantly allocating large arrays (with the 64kb default)?

Pooling is often a good strategy. However it involves a lot of policy decisions, like threading and locking, which are better left to the higher level code. OutputBuffer is intended to be a flexible, low level implementation of IOutputStream optimized for raw write speed to a managed memory (OutputPointer is the equivalent for unmanaged memory).
I took the liberty to rename your issue to "Slow serialization" to better reflect your original problem - this way it will be more helpful to others in the future.

@sapek not sure if the lifespan of the buffer is known, but if is can use System.Buffers ArrayPool<byte>.Shared.Rent() and ArrayPool<byte>.Shared.Return() ?

The buffer contains serialized data, so the lifetime is controlled by the application.
An implementation of IOutputStream on top of ArrayPool<byte> probably would be useful in some cases.

Please feel free to reopen if you have other related questions.


This plugin is a monster, just one issue!!

This thing is an absolute beast sortable. I was on the lookout for a lightweight one after scratching interactJS because it's literally over 60KB's... This plugin is amazing!
Anyways, my issue is.. I have a rpg inventory system, and I like to use block sizes with item dimensions. So, everything works fine with this plugin except for when you got un-even height css boxes.  Take a look:
The code:
function qs(expr){return document.querySelector(expr)}
var container = qs('.ITEST');
var sort = Sortable.create(container, {
  animation: 350,
  draggable: ".draggable",
});

THE CSS:
 .draggable{
    color: #fff;
    margin: 1px;
    float: left;
    display: inline-block;
}
.ITEST{
	width:425px;
    height:400px;
	margin:auto;
	border:1px solid grey
}

I created a jsfiddle here to better help explain my issue: http://jsfiddle.net/g8o0upLq/9/
The problem lies when dragging the red squares, they move correctly, but they do not stack vertically ontop of each other but horizontally. This creates unwanted extra white space underneath. Is this an issue with the plugin, or CSS itself? I have tried to set the same height for all divs, but with no luck.
Edit: I also posted this on SO as well: http://stackoverflow.com/questions/30422279/how-to-adjust-a-floating-div-based-on-its-height-and-surroundings

Bump, any update guys? :dancers:

Do I understand correctly that you want this:
+——+ +——+
|  | |  |
|  | +——+
|  | +——+
|  | |  |
+——+ +——+

If so, there library is not designed for such tasks.

 This script is much better and can be just as powerful as gridster if this feature could be implemented.

Alas, this is a very specific task, it can not be solved in the usual drag'n'drop.

Alrighty, Thanks RubaXa, bummer :(

This is the maximum that possible to squeeze out of the CSS:
http://jsbin.com/xudilasasi/1/edit?css,js,output


Confront number HPOs across languages

Write a test to check that the number of HPO terms present in prompts in different languages is the same, i.e. that if a term is not known in a non-English language, the prompt is not simply generated without that specific term.

The answer is no. The below branch shows following results with phenopackets store release 0.1.19 (with 6682 phenopackets):
https://github.com/monarch-initiative/phenopacket2prompt/tree/only_prompts_with_all_translations
es   6577
it    4915
de  4915
zh  6242 (chinese)
tr   4940
nl   3807


Added team scope to alias command

When working in a team other than a personal team, scope needs to be supplied to the alias CLI command when using an explicit token. If not, CLI will try to perform the alias on your personal account, even if it's excluded from the token scope, resulting in a "You don't have access to the domain -.app under USER" error.
Reported by someone facing the same issue here: https://github.com/orgs/vercel/discussions/3477#discussion-5467326
Added the token scope and incremented the patch version to resolve.

v1.2.2 has been published! https://marketplace.visualstudio.com/items?itemName=Vercel.vercel-deployment-extension


possibility to add costum scripts to the new iso?

is there any way to add some custom script that will be exucuted by the iso once booted? would be a dope feature, btw super cool tool thank you!

I think this would fall under #256. It's not exactly cleanup but could be used in the same way I think. So in short, currently there is not, but maybe in the future! For now I would just pre-prepare the image with what you want it to do on boot before shutting it down.
Glad you are enjoying the tool 😄


Select setting image with CRA

Hi
I built my App using CRA and im having problems loading images to Options in the component Select.  Is there a way to make this happen?

This question is not related to SUIR at all, please use Stackoverflow for questions.
import jennyImg from './avatar/jenny.png'

const option = {
  text: 'Jenny Hess',
  value: 'Jenny Hess',
  image: { avatar: true, src: jennyImg },
}


Build out the Python AWS CDK for Deployments

Okay our deployment to alpha customer (individual 1)... was 'suboptimal', it really underscored the need to have some nice built in AWS deployments.
Lets look at the latest Python Tooling around deployments and use that

(AWS Account) Deploy_AWS_Sageworks_Sandbox
(Docker) Deploy_Dashboard
(Docker) Deploy_Development_Sandbox

References:

https://www.tinystacks.com/blog-post/aws-cdk-vs-cloudformation/

I've started this a tiny bit (basically just cdk init) in this directory sageworks/aws_stuff/sageworks_sandbox


clear polling queue when starting new operation

Currently, we trust that the polling reconciliation function will remove the instance from the polling queue after it finishes the operation. However, we can't assume that the poller will always finish. If someone removes the finalizer of an instance with a deprovision in progress, the resource will be forcibly deleted but the polling queue will not be reset, so a subsequent provision of an instance of the same name will take a long time before starting to poll. This clears the polling queue before starting a new operation, just in case the reconciler wasn't able to do it beforehand.

LGTM


Update Agda to 2.6.3 to Prevent Emacs "agda-mode compile" Error

https://github.com/plfa/plfa.github.io/blob/51c71b2ad10fa7b0d921bb11fd3a5553588f012c/README.md?plain=1#L66
The readme instructs new users to install Agda <IP_ADDRESS>. Following along the instructions as written, I received the following compile error:
 ~ % agda-mode compile
Loading quail/latin-ltx...

In toplevel form:
.cabal/store/ghc-9.2.4/Agd-<IP_ADDRESS>-e8b2c246/share/emacs-mode/agda2-mode.el:1308:2: Error:  docstring wider than 80 characters
Unable to compile the following Emacs Lisp files:
  ~/.cabal/store/ghc-9.2.4/Agd-<IP_ADDRESS>-e8b2c246/share/emacs-mode/agda2-mode.el

I am running GNU Emacs 28.2 on Mac OS Ventura 13.1.
One of the changes made in Agda 2.6.3 is to reduce the docstrings to be shorter than 80 characters, as seen in this commit. Running agda-mode compile succeeds with version Agda 2.6.3.
My suggestion is to recommend users install Agda 2.6.3 rather than <IP_ADDRESS>. Will this cause any foreseeable issues? Thanks!

No, PLFA compiles with 2.6.3 just fine. If you're happy to submit a pull request updating the version, I'd be happy to merge it. Otherwise, I'll get to that eventually.

See: https://github.com/plfa/plfa.github.io/actions/runs/4227084954/jobs/7341200625

#833


openbao: Build with native go compiler

What's the justification?

What's the justification?

That's how upstream builds it and there's no need for any CGO features.

there's no need for any CGO features.

In fact there is: https://pkg.go.dev/net#hdr-Name_Resolution. With CGO the native, glibc based resolver is used, which do support more features than the go based resolver. While this is not relevant for the majority of the users, disabling CGO doesn't provide much benefit either. Upstream might be inclined to disable CGO to produce a static binary that's easier to redistributed, but that's never a problem with nix.

With CGO the native, glibc based resolver is used, which do support more features than the go based resolver.
Ah, TIL.


Snapshot vs image

This seems like a basic question but I can't find an answer in these documents.
What is the difference between a snapshot and an image? You can create both from a disk, and use both to create VMs.
"A managed VM image contains the information necessary to create a VM, including the OS and data disks."
(from this page)
"A snapshot is a full, read-only copy of a VHD. "
(from https://docs.microsoft.com/en-us/azure/virtual-machines/windows/snapshot-copy-managed-disk)
These are the definitions provided, but the image creation doc shows how to create images from disks or, indeed, from snapshots. What are we adding when we do so? When creating a VM from either of these resources, it seems like we still have the freedom to specify the size, location, and so on.

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

ID: c95cf419-74ae-f6d1-5c3e-01f988fdd9c4
Version Independent ID: 6dfe7480-2c45-2be9-3f3d-8ee97f62cc62
Content: Create VM from a managed image in Azure
Content Source: articles/virtual-machines/windows/create-vm-generalized-managed.md
Service: virtual-machines-windows
GitHub Login: @cynthn
Microsoft Alias: cynthn

Thanks for the question! We are investigating and will update you shortly.

@dcbrown16 A VM Image contains an OS disk, which has been generalized and needs to be provisioned during deployment time.  OS Images today are generalized.  This is meant to be used as a “model” to quickly stamp out similar virtual machines, such as scaling out a front-end to your application in production or spinning up and tearing down similar development and test environments quickly.
A Snapshot contains an OS disk, which is already provisioned.  It is similar to a disk today in that it is “ready-to-use”, but unlike a disk, the VHDs of a Snapshot are treated as read-only and copied when deploying a new virtual machine.  A snapshot is a copy of the virtual machine's disk file at a given point in time, meant to be used to deploy a VM to a good known point in time, such as check pointing a developer machine, before performing a task which may go wrong and render the virtual machine useless.

Thanks @Karishma-Tiwari-MSFT , that will be very helpful in communicating to our customer for this case!

@v-maroge An image of a virtual machine is a copy of the VM which encompasses the full definition of virtual machine’s storage, containing the OS disk, all data disks, data files and applications.  It captures the disk properties (such as host caching) you need in order to deploy a VM in a reusable unit.

@v-maroge Does that answer your question?

@Karishma-Tiwari-MSFT The applications that are also contained in the image, will the they also be generalized (I'm imagining something like initialization), or will the data(or settings) in the application also be saved at the point the image was created?

Yes, that would be correct.
Thanks for sharing your feedback. Since this ask is not a doc issue, we will now close this. If there are further questions regarding this matter, please reach out to Azure forums and we will gladly continue the discussion.


Web build fails on Emscripten 3.1.58

Tested versions

Reproducible in 4.3.dev (780e1a50408360cf0cf93c0b55b59e9d7b4ad0b1)
Reproducible in 3.6.beta (after including #91151 so recent Emscripten can be used)

System information
Fedora Linux 39 (KDE Plasma) - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 7600M XT (RADV NAVI33) () - AMD Ryzen 7 7840HS w/ Radeon 780M Graphics (16 Threads)
Issue description
Emscripten never fails to disappoint with breaking Godot every other release.
I tested the latest 3.1.58 and our Web editor build is broken (this is with closure compiler, but it fails the same without).
/usr/bin/node /home/akien/Godot/toolchains/emsdk/upstream/emscripten/node_modules/.bin/google-closure-compiler --compilation_level ADVANCED_OPTIMIZATIONS --externs /home/akien/Godot/godot/platform/web/js/engine/engine.externs.js --js /home/akien/Godot/godot/platform/web/js/engine/features.js --js /home/akien/Godot/godot/platform/web/js/engine/preloader.js --js /home/akien/Godot/godot/platform/web/js/engine/config.js --js /home/akien/Godot/godot/platform/web/js/engine/engine.js --js_output_file /home/akien/Godot/godot/bin/godot.web.editor.wasm32.engine.js
Install file: "misc/dist/html/logo.svg" as "bin/.web_zip/logo.svg"
Install file: "misc/dist/html/manifest.json" as "bin/.web_zip/manifest.json"
Install file: "misc/dist/html/offline.html" as "bin/.web_zip/offline.html"
Creating 'bin/godot.web.editor.wasm32.service.worker.js'
Install file: "bin/godot.web.editor.wasm32.service.worker.js" as "bin/.web_zip/service.worker.js"
Building compilation database compile_commands.json
progress_finish(["progress_finish"], [])
/home/akien/Godot/godot/platform/web/js/engine/features.js:75:4: WARNING - [JSC_TYPE_PARSE_ERROR] Bad type annotation. type annotation incompatible with other annotations. See https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler for more information.
  75|    * @typedef {{ threads: boolean }} SupportedFeatures
           ^

/home/akien/Godot/godot/platform/web/js/engine/features.js:76:12: WARNING - [JSC_UNRECOGNIZED_TYPE_ERROR] Bad type annotation. Unknown type SupportedFeatures
  76|    * @param {SupportedFeatures} supportedFeatures
                   ^

0 error(s), 2 warning(s), 73.6% typed
Linking Static Library core/libcore.web.editor.wasm32.a ...
Ranlib Library core/libcore.web.editor.wasm32.a ...
Linking Program bin/godot.web.editor.wasm32.js ...
em++: warning: -pthread + ALLOW_MEMORY_GROWTH may run non-wasm code slowly, see https://github.com/WebAssembly/design/issues/1271 [-Wpthreads-mem-growth]
cache:INFO: generating system asset: symbol_lists/4b07af37ace67ce59deb12f4d95eee632ec0a8c4.json... (this will be cached in "/home/akien/Godot/toolchains/emsdk/upstream/emscripten/cache/symbol_lists/4b07af37ace67ce59deb12f4d95eee632ec0a8c4.json" for subsequent builds)
cache:INFO:  - ok
wasm-ld: warning: function signature mismatch: unztell
>>> defined as (i32) -> i64 in core/libcore.web.editor.wasm32.a(file_access_zip.web.editor.wasm32.o)
>>> defined as (i32) -> i32 in core/libcore.web.editor.wasm32.a(unzip.web.editor.wasm32.o)
Creating 'bin/godot.web.editor.wasm32.wrapped.js'
Install file: "bin/godot.web.editor.wasm32.wasm" as "bin/.web_zip/godot.editor.wasm"
Install file: "bin/godot.web.editor.wasm32.worker.js" as "bin/.web_zip/godot.editor.worker.js"
scons: *** [bin/.web_zip/godot.editor.worker.js] bin/godot.web.editor.wasm32.worker.js: No such file or directory
scons: building terminated because of errors.
[Time elapsed: 00:06:08.446]

The missing godot.web.editor.wasm32.worker.js is actually generated in the root folder of the repo, instead of the bin folder.
It works fine with Emscripten 3.1.39, so it regressed somewhere in between.
Steps to reproduce

Install Emscripten 3.1.58
Build with scons p=web target=editor

Minimal reproduction project (MRP)
n/a

The regression comes from 3.1.58 itself, I built successfully with 3.1.57.
This change sounds pretty relevant:
Multi-threaded builds no depend on a separate .worker.js file. This saves on code size and network requests. In order to make this change go smoothly, without breaking build systems that expect a worker.js, emscripten will generate an empty .worker.js to give folks time to transition their deployment scripts. In -sSTRICT mode, this empty file will not be generated. (#21701)

https://github.com/emscripten-core/emscripten/blob/main/ChangeLog.md#3158---042324
@adamscott @Faless

Multi-threaded builds no depend on a separate .worker.js file. This saves on code size and network requests. In order to make this change go smoothly, without breaking build systems that expect a worker.js, emscripten will generate an empty .worker.js to give folks time to transition their deployment scripts. In -sSTRICT mode, this empty file will not be generated. (#21701)

While this change isn't the reason for the build failure (see #91202), it's something we indeed need to track, and IMO a very welcome change from upstream since it makes load time faster (one less fetch).
I wonder if/when we could bump to 3.1.58 as the minimum version and do some cleanup in our threaded load/export paths.

Seems like the issue is caused by a bug upstream fixed via https://github.com/emscripten-core/emscripten/pull/21830 (which will be in 3.1.59).

Thanks for checking! This is a wontfix then, as there's little point trying to workaround a bug only present in one release.
We can still fix the warnings as you've started doing though.
There's also this one that might be worth a look:
wasm-ld: warning: function signature mismatch: unztell
>>> defined as (i32) -> i64 in core/libcore.web.editor.wasm32.a(file_access_zip.web.editor.wasm32.o)
>>> defined as (i32) -> i32 in core/libcore.web.editor.wasm32.a(unzip.web.editor.wasm32.o)


Schema registry base authentication

Use case:
Produce a message using a schema registry server that has base authentication enabled.
Proposed solution: https://github.com/marcosandremartins/rest-producer/pull/8

Closed with https://github.com/marcosandremartins/rest-producer/pull/8


Deploy to a Server

Rasa version:
Rasa-X 0.19.0
Python version:
Python 2.7.15rc1
Operating system (windows, osx, ...):
Ubuntu 18.04
Issue:
When trying to setup Rasa X on an ubuntu 18.04 server. The ansible playbook failed to run. This is due to a formatting issue in rasa_x_playbook.yml. Updating the following section:
  - name: Create the directory for the database persistence
      file:
        path: /etc/rasa/db
        state: directory
        mode: 0750
        owner: 1001
        group: root

To the following resolved the issue.
  - name: Create the directory for the database persistence
    file:
        path: /etc/rasa/db
        state: directory
        mode: 0750
        owner: 1001
        group: root

Content of configuration file (config.yml):
N/A

Content of domain file (domain.yml) (if used & relevant):
N/A

Thanks for raising this issue, @wochinge  will get back to you about it soon.

@nkane2898 Thanks for finding and fixing this! That's already fixed for the next release.
I'll keep it open so others can see it.


App Id depending platform

Feature Request
Ionic Info
Ionic:

   ionic (Ionic CLI)  : 4.4.0 (/opt/node-v8.10.0-linux-x64/lib/node_modules/ionic)
   Ionic Framework    : ionic-angular 3.9.2
   @ionic/app-scripts : 3.2.1

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : android 7.1.4
   Cordova Plugins       : cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 1.2.1, (and 18 other plugins)

System:

   Android SDK Tools : 26.1.1 (/home/genaro/Android/Sdk)
   NodeJS            : v8.10.0 (/opt/node-v8.10.0-linux-x64/bin/node)
   npm               : 6.4.1
   OS                : Linux 4.18

Describe the Feature Request
I've developed an app for Android which is already in the Play Store since a year ago. This week I was asked for upload the app to App Store, to my surprise the id already exists! So I had to make a new branch just to change the id for iOS. It would be so cool if We could define the app id (as the version and related info) in the config.xml file specifing the platform.
Describe Preferred Solution
As we can define hooks, icons, resource-file by platform, It would be nice to define the id too.
Thanks in advance and sorry about my English

Thanks for your issue and the time reporting it. Unfortunately your issue is not related to Ionic. Instead this is something that concerns Apache Cordova.
After a short search I found this -> https://stackoverflow.com/questions/19069674/cordova-is-it-possible-to-have-different-app-ids-for-android-and-ios-platforms
I hope this will help you :)

Thank you so much!


Complete Documentation

[ ] Quickstart - Article on docs.microsoft.com that is similar to but expands on the README content
[ ] Conceptual - Long-form documentation like Quickstarts, Tutorials, How-to guides, and other content on docs.microsoft.com

@kaerm
Closing as this belongs to PM team.

Reassigning per conversation with @kaerm

Closing this. If this is still required, let's file a new issue.


can not install HAMi on AWS EKS

Please provide an in-depth description of the question you have:
What do you think about this question?:
Environment:

HAMi version: 2.4.1
Kubernetes version:  v1.29.11-eks-56e63d8
Others:

helm install hami hami-charts/hami --set scheduler.kubeScheduler.imageTag=v1.29.11 -n hami
Error: INSTALLATION FAILED: chart requires kubeVersion: >= 1.16.0 which is incompatible with Kubernetes v1.29.11-eks-56e63d8

The version v1.29.11-eks-56e63d8 is not a standard semantic version, so it cannot be recognized by Helm. To resolve this issue, there are two approaches:

Directly remove or comment out the kubeVersion field in charts/hami/Chart.yaml

# kubeVersion: ">= 1.16.0"

Use --set kubeVersionOverride=true when installing the Helm Chart to bypass the Kubernetes version check.

helm install hami hami-charts/hami --set kubeVersionOverride=true

The version v1.29.11-eks-56e63d8 is not a standard semantic version, so it cannot be recognized by Helm. To resolve this issue, there are two approaches:

Directly remove or comment out the kubeVersion field in charts/hami/Chart.yaml

# kubeVersion: ">= 1.16.0"

Use --set kubeVersionOverride=true when installing the Helm Chart to bypass the Kubernetes version check.

helm install hami hami-charts/hami --set kubeVersionOverride=true

Since there is no user-managed kube-scheduler component in AWS EKS clusters, should I install the HAMi kube-scheduler or only the vgpu-scheduler-extender?

I have not installed HAMI on AWS EKS before. Normally, both components need to be installed:

kube-scheduler will register a scheduler extender with the cluster.
vgpu-scheduler-extender handles the actual scheduling requests.

The version v1.29.11-eks-56e63d8 is not a standard semantic version, so it cannot be recognized by Helm. To resolve this issue, there are two approaches:

Directly remove or comment out the kubeVersion field in charts/hami/Chart.yaml

# kubeVersion: ">= 1.16.0"

Use --set kubeVersionOverride=true when installing the Helm Chart to bypass the Kubernetes version check.

helm install hami hami-charts/hami --set kubeVersionOverride=true

❯ helm install hami ./hami -n hami --set scheduler.kubeScheduler.imageTag=v1.29.11 --set kubeVersionOverride=true
Error: INSTALLATION FAILED: chart requires kubeVersion: >= 1.16.0 which is incompatible with Kubernetes v1.29.11-eks-56e63d8

❯ k get po
NAME                              READY   STATUS             RESTARTS      AGE
hami-admission-patch-4shvn        0/1     CrashLoopBackOff   4 (22s ago)   113s
hami-scheduler-69fbc99df7-6x87p   1/2     Error              4 (64s ago)   119s

Normal   Scheduled  9m1s                    default-scheduler  Successfully assigned hami/hami-scheduler-69fbc99df7-6x87p to ip-10-170-85-172.us-west-2.compute.internal
Normal   Pulling    9m1s                    kubelet            Pulling image "registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.29.11"
Normal   Pulled     8m50s                   kubelet            Successfully pulled image "registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.29.11" in 10.5s (10.5s including waiting)
Normal   Pulled     8m50s                   kubelet            Container image "projecthami/hami:v2.4.1" already present on machine
Normal   Created    8m50s                   kubelet            Created container vgpu-scheduler-extender
Normal   Started    8m50s                   kubelet            Started container vgpu-scheduler-extender
Normal   Created    8m6s (x4 over 8m50s)    kubelet            Created container kube-scheduler
Normal   Started    8m6s (x4 over 8m50s)    kubelet            Started container kube-scheduler
Normal   Pulled     7m12s (x4 over 8m49s)   kubelet            Container image "registry.cn-hangzhou.aliyuncs.com/google_containers/kube-scheduler:v1.29.11" already present on machine
Warning  BackOff    3m59s (x23 over 8m48s)  kubelet            Back-off restarting failed container kube-scheduler in pod hami-scheduler-69fbc99df7-6x87p_hami(93fb46b5-13a4-4cd6-9df4-124c311a45fb)
❯ k logs pod/hami-scheduler-69fbc99df7-6x87p
Defaulted container "kube-scheduler" out of: kube-scheduler, vgpu-scheduler-extender
Usage:
kube-scheduler [flags]
Misc flags:
  --config string            The path to the configuration file.
  --master string            The address of the Kubernetes API server (overrides any value in kubeconfig)
  --write-config-to string   If set, write the configuration values to this file and exit.

Secure serving flags:

I can run 2.4.1 in EKS 1.24 ,but can not scheduler pod
NAME                                                       READY   STATUS    RESTARTS   AGE
hami-device-plugin-757j9                       2/2        Running            0          47m
hami-device-plugin-tcb5z                       2/2        Running            0          18m
hami-scheduler-7b4dcdcb9c-j5btq       2/2        Running            0          27m


Add rename plugin to change VersionTemplate name

Currently, user can not build testng locally because of Version.java can't be found.

So, how do you explain Travis is doing it without problem?
BTW, if you run a mvn compile, Version.java will be avaible.
And fyi, Maven will be removed soon.
:-1:

Hi,
I have no idea why your Travis will work, it depends on how you verify your
job, at least it not work for me and another person in mail list.
Based on the configuration of maven, it will not work. And it not work
indeed in my side.
Yeah, I guess so, but anyway, it is just a small improvement for maven
users.
Br,
Tim
2015-05-20 11:23 GMT+02:00 Julien Herr<EMAIL_ADDRESS>
So, how do you explain Travis is doing it without problem?
BTW, if you run a mvn compile, Version.java will be avaible.
And fyi, Maven will be removed soon.
[image: :-1:]
—
Reply to this email directly or view it on GitHub
https://github.com/cbeust/testng/pull/693#issuecomment-103821120.

Ok, I've just seen your message on the mailing list and I didn't notice the change of the version file with 0730d08ad0b4812c5b2a798729cb7b6cc618dc9b before.
:+1: even Maven will be removed.
And Travis is working because it uses Gradle.

Thanks very much
Den 20 maj 2015 17:43 skrev "Julien Herr"<EMAIL_ADDRESS>
Ok, I've just seen your message on the mailing list and I didn't notice
the change of the version file with 0730d08
https://github.com/cbeust/testng/commit/0730d08ad0b4812c5b2a798729cb7b6cc618dc9b
before.
[image: :+1:] even Maven will be removed.
And Travis is working because it uses Gradle.
—
Reply to this email directly or view it on GitHub
https://github.com/cbeust/testng/pull/693#issuecomment-103932730.

Thank you both for looking into that! Merging this, but I might remove maven support altogether some time in the future.
In the meantime, having both builds work is certainly a good idea, so thanks @wutingbupt !


docs: Ionic changelog apparently not updated

Type: docs
Ionic Version: 2.x
Platform: all
Hi, everybody. Apparently, the github changelog has not been updated since 2017-8.

What do you mean? Looks fine to me: https://github.com/ionic-team/ionic/blob/master/CHANGELOG.md

Hello! Thank you for opening an issue with us!
Closing this as the Ionic Framework changelog has been updated several times since 2017-8.
@fbalbinoribeiro - if you are seeing something different, can you please supply a link as to what you are looking at?
Thank you for using Ionic