do you get line numbers in your build errors?

Hi @zeekay,
I've been using this: https://github.com/coreytrampe/rollup-plugin-coffee-script, but got tired of not getting line numbers in error messages, and started to look into it again and noticed this repo.
So I gave yours a shot real quick, and I'm seeing the same thing. Are you getting line numbers? (I wonder if maybe I'm just missing something in my config.)
Thanks 🙂

@coreytrampe, rollup-plugin-coffee-script now supports line numbers, if you want to check it out


Ansible version documentation

I've had some issue running the deployment using ansible 1.8.4 (error with host_vars usage, etc.).  With <IP_ADDRESS> (latest today) everything works smoothly.  Would be good to indicate which version of ansible the team uses to validate/test.

1.8.4 here. What issues are you seeing?

TASK: [dnsmasq | configure dnsmasq for consul] ********************************
fatal: [tdeckers-26032015] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'ansible_default_ipv4'", 'failed': True}
fatal: [tdeckers-26032015] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'ansible_default_ipv4'", 'failed': True}

At that time I was troubleshooting another issue, and running a playbook against a single host.  So it's possible that it's a combination of things.

Here's one of the other changes I noticed with this new version.
One the controller nodes, first mesos gets installed.  No specific version is defined, so we get the latest.  It also seems to bring in marathon 0.8.1, the latest version.  Next, marathon is installed and a specific version is specified: 0.7.6.  Somehow it appears that ansible 1.8.4 didn't correctly downgrade marathon to 0.7.6.  With this new version of ansible that seems to work as expected.

@tdeckers we removed the 0.7.6 hardcoding in the 0.2-dev branch (which we are merging into master today). 0.8.1 rpms were not available when we cut 0.1, and we had issues with 0.8.0.

Cool.  For this issue, if you're validating with ansible 1.8.4, then there must be something else on my side that I'm messing up.  Feel free to close this issue.  I'll validate later with a fresh install and if I run into the same issues I'll reopen, and we can work on it then. Thx.

Closing per @tdeckers request.


Realm add(, update: true)/create(, _, update: true) removes existing child relationships

I am facing an issue where I am unable to keep existing child relationships after calling add(_, update: true) or create(_, _, update: true) functions to update the parent model. See the comments in the UserSync class.
I tried many different way how to achieve this, however without any success
Goals
The existing relationship tasks located in the user model should be present after updating the task model.
Expected Results
As described in the UserSync class comment (_user.tasks.count is 15 here), the model.tasks.count should be also 15 after calling add or create functions.
Actual Results
The model.tasks list on the user model is empty after calling both create and add functions
Code Sample
Class used for 'syncing' models
class UserSync: ISync {

    typealias Model = User

    func sync(model: User) {

        let realm = try! Realm()

        let inWrite = realm.isInWriteTransaction

        if !inWrite {
            realm.beginWrite()
        }

        let _user = realm.object(ofType: User.self, forPrimaryKey: model.id)

        // Persist tasks as they are not getting fetched with the user
        if let _user = _user {
            // _user.tasks.count is 15 here
            model.tasks = _user.tasks
        }

        realm.add(model, update: true)
        // model.tasks.count is 0 here

        // Attempt to use create(_, _, _) function with hope it will keep existing relationships - did not work
        // let _ = realm.create(User.self, value: model, update: true)

        if !inWrite {
            try! realm.commitWrite()
        }
    }

    func sync(models: List<User>) {

        let realm = try! Realm()

        try! realm.write {
            models.forEach { user in
                sync(model: user)
            }
        }
    }
}

User model:
class User: Object, ElementPreloadable, ElementImagePreloadable {

    dynamic var id: Int = 0
    dynamic var firstname: String = ""
    dynamic var lastname: String = ""
    dynamic var email: String = ""
    dynamic var password: String?
    dynamic var birthdate: String?

    var images = List<URLImage>()
    var imagesDeleted = List<URLImage>()
    var imagesNew = List<Image>()

    var currency: Currency?

    var tasks = List<Task>()

    override static func primaryKey() -> String? {
        return "id"
    }

    override static func ignoredProperties() -> [String] {
        return ["imagesDeleted", "imagesNew"]
    }

    func getImageMain() -> URLImage? {
        for image in images {
            if image.main {
                return image
            }
        }
        return images.first
    }

    func getSection() -> Int {
        return 0
    }

    func getId() -> Int {
        return id
    }

    func getURL() -> URL? {
        if let image = getImageMain() {
            return image.getResizedURL()
        }
        return nil
    }

    func getName() -> String {
        return "\(firstname) \(lastname)"
    }
}

Task model:
class Task: Object, ElementPreloadable, ElementImagePreloadable, ItemSectionable {

    dynamic var id: Int = 0
    dynamic var title: String = ""
    dynamic var desc: String = ""
    dynamic var price: Float = 0.0
    dynamic var calculatedPrice: Float = 0.0
    dynamic var location: String = ""
    dynamic var duration: Int = 0
    dynamic var date: String = ""
    dynamic var category: Category?
    dynamic var currency: Currency?
    dynamic var longitude: Double = 0.0
    dynamic var latitude: Double = 0.0
    dynamic var state: Int = 0
    dynamic var userId: Int = 0

    // Existing images
    var imagesExisting = List<URLImage>()
    // New images
    var imagesNew = List<Image>()
    // Images deleted
    var imagesDeleted = List<URLImage>()

    private let users = LinkingObjects(fromType: User.self, property: "tasks")
    var user: User?

    var matches = List<Match>()

    dynamic var notification: Notification?

    override static func ignoredProperties() -> [String] {
        return ["imagesExisting", "imagesNew", "imagesDeleted", "user", "tmpUser"]
    }

    override static func primaryKey() -> String? {
        return "id"
    }

    func getImageMain() -> URLImage? {
        for image in imagesExisting {
            if image.main {
                return image
            }
        }
        return imagesExisting.first
    }

    func getSection() -> Int {
        return state
    }

    func getSectionFieldName() -> String? {
        return "state"
    }

    func getId() -> Int {
        return id
    }

    func getURL() -> URL? {
        if let image = getImageMain() {
            return image.getResizedURL()
        }
        return nil
    }

    func getState() -> TaskOwnState {
        return TaskOwnState(rawValue: state)!
    }

    func getUser() -> User {
        return (user != nil ? user : users.first)!
    }
}

Realm framework version: 2.9.1
Xcode version: 9

List properties should always be declared as let properties, as assigning to them does not do anything useful. The correct way to copy all objects from one List to another is model.tasks.append(objectsIn: _user.tasks).

Yes you are right, this worked. Thank you!


preference data

As a developer, I want users to have preference page details inputted before finding matches, so that this data can be used for matching algorithm

[ ] #64
[ ] #69
[ ] #71


PERF: locationcodes.to_description causes the mapping file to be read from memory

Problem
For example: locationcodes.to_description is used in a pd.DataFrame().apply() function so that a column of descriptions can be constructed. This causes several million reads of the y92-mapping.pkl file, which is terrible for performance.
Demonstration
Call the function repeatedly several million times and measure how long it takes.
Solution
Store the mapping in memory so that it can be retrieved easily.
Tasks

[x] Allow to_description to use a mapping passed in as a parameter

Changes in #59 have (most likely) solved the problem. However, testing is required to determine that the reads have actually been eliminated. Additionally, it would be desirable to have better default behavior for get_mapping (see comment from #59)
These tasks will be added to the original comment of this issue.


[BUG] Model training using model.fit throws InternalError Exception encountered when calling layer "dot_product_interaction" (type DotProductInteraction)

Bug description

Model training using model.fit throws InternalError Exception encountered when calling layer "dot_product_interaction" (type DotProductInteraction) for both DLRM as well as two-tower model.
Steps/Code to reproduce bug

Please download the sample data and notebooks from the link
01-Building-Recommender-Systems-with-Merlin.ipynb should give more details of the error in cell 12 when we run model.fit

Environment details

Merlin version: 22.05 with latest branches pulled
Tensorflow version (GPU?): 2.9.1

Resolved on 22.06 container


BUG: DIMAP SEN products are shifted after orthorectification

As described in #50, orthorectifying SEN products leads to shift.
Tested on PLD and PLD Neo.
This needs more investigations.

Current workaroud:
If you can orthorectify the stack elsewhere, just set the ortho stack path as described here:

Here, if you want to orthorectify or pansharpen your data manually, you can set your stack here.

prod.ortho_stack = "/path/to/ortho_stack.tif"

In the DIMAP user guide it is written:

RPC is a generalised analytic model independent of the sensor data handling by the most current software. Users needing the highest level of accuracy (estimation greater than 3rd degree polynomial, block adjustment...) should prefer the rigorous sensor model (Primary product).

The rigorous model is described in section C.2 Using the Physical Model for the Primary Products and seems rather complicated.
I don't think I will implement such method for products not usually used in CEMS rapid mapping.
➡ However, a note about this must be added in the documentation (and VHR tutorial).
🚨 Anyone interested in implementing this is welcome (even a draft).


Runtime failed to provide system information

Already tried to reinstall app, meta software, checked that in the meta app runtime is set. What it cloud be? It did work...

This repository's issues page is intended for general support with the vrcfacetracking application. For more target support for specific hardware and modules, please seek assistance in the discord


[QUESTION] How should I share a working authentik OIDC configuration?

Question
I'm opening this up because I worked on getting authentik working with Dashy last night. I'm authenticating successfully and it's picking up groups successfully. I can hide pages/sections, etc based on authentik group membership.
The only thing I haven't figured out is how to differentiate admins and users. I am looking for information on that if you could share how I can do that in Dashy. Maybe assigning an OIDC group to a type: admin. Not sure if that is implemented or not.
How would you like this information shared with the community? I can open a PR against the docs and add it there if you'd like. Thank you in advance.
Category
Authentication
Please tick the boxes

[X] You are using a supported version of Dashy (check the first two digits of the version number)
[X] You've checked that this question hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

Hi
Thanks!
Yeah the best will probably be to add this to the authentication docs on the oidc section in a subsection examples -> authentik.
Feel free to clone make the changes, push and open a PR.
For the differation from admin and user I allow myself to ping @twsouthwick as he was so kind and made this PR.
Thanks!

Thank you. I hope there is a way differentiate. I'll open a PR with the documentation changes.

As the PR got merged, I'll close this.
Thanks again! ✨

Oh apologies, overlooked that it's also an issue, due to the nature of this thread and it being tagged as question, I'd rather create a new one, and directly tag twsouthwick

Done. https://github.com/Lissy93/dashy/issues/1675


Problem of researching a caste object with eloquent.

Hello
First thank you for your package, it helps.
In fact I have a problem with your package. I don't know how to search from an object. The object is caste as an array in my model, then I use the nested type of elasticsearch. The index, the mapping, the import everything works, but I don't get a result. Can you help me please.
Here is my mapping:
/**
* @var array
*/
protected $mapping = [
    'properties' => [
        'skills' => [
            "type" => "nested",
        ],
    ]
];

Here is my cast:
protected $casts = [
    'skills' => 'array',
];

Here is an example:
$job = $job->search($keywords);
$job = $job->whereIn('skills', ['{"text":"PHP","tiClasses":["ti-valid"]}']);
$job->paginate(20);

The real value if I'm not mistaken is [{"text": "PHP", "tiClasses": ["ti-valid"]}].
An array containing one or more objects.
Can you help me please.
Thanks

Hey there @Moussa-Ball

for this kind of searches, nested searches and aggregations I recommend you use something like the following package:
https://github.com/ongr-io/ElasticsearchDSL
It's very simple to construct queries there and then pass them in the searchRaw function.

Have you updated your index? I would be surprised if it is index like stirng.
please check yourmodel/_mappings in Kibana

It's a freelance website, I have to filter jobs etc. Everything works except the skills which are tags in an array so you know how it works.

It's complicated to say. ES use Char filter, tokenizers, and token filter. It does not always compare queries the way you imagine. Have you checked the above tips?


plugins/tmux-navigator: Add keymap config options

First time opening a PR here, so let me know if I've missed some etiquette.
Summary

New option tmuxNavigatorNoMappings maps to global tmux_navigator_no_mappings
New attrset keymaps maps keymaps to the various :TmuxNavigate* commands

Set of either enum or mapConfigOptions submodule (with some tweaks)

Future refactoring
I don't see why the various options should include the tmuxNavigator prefix; that is surely implied by being in the tmux-navigator plugin...
I also think that the null or 1 options could be refactored as bool options, to make more sense in nix...
I can open this as a separate issue/PR if it warrants discussion, or I could lump it into this PR if that's easier to review?

I don't see why the various options should include the tmuxNavigator prefix; that is surely implied by being in the tmux-navigator plugin...
I also think that the null or 1 options could be refactored as bool options, to make more sense in nix...
I can open this as a separate issue/PR if it warrants discussion, or I could lump it into this PR if that's easier to review?

IMO this PR should be reworked after the plugin is ported to mkVimPlugin. I've opened #1293 to do that.

Is this PR still relevant ? If so, it is necessary to rebase it on main as it has been a while ^^

cc @MattSturgeon

Unless I have some time to kill earlier, I'll take a look when I get back to the UK.
It'll probably need a rewrite due to #1293.

Could you rebase this on main please ?

So you chose the "list" approach which is definitely more straightforward to implement.
However, wouldn't be an attrs approach clearer for the user ?
keymaps.<action>.key = "<C-m>"; ?

So you chose the "list" approach which is definitely more straightforward to implement. However, wouldn't be an attrs approach clearer for the user ? keymaps.<action>.key = "<C-m>"; ?

I felt like a list was a better analogue for the underlying keymaps.
In particular, if a user wanted multiple "left" or "previous" binds, that wouldn't be possible with an attrsOf (either str submodule).
I'm still torn as to whether most/all of our plugin keybinds should be transitioning towards lists at some point, but that's way beyond the scope of this PR 😂

I felt like a list was a better analogue for the underlying keymaps.
In particular, if a user wanted multiple "left" or "previous" binds, that wouldn't be possible with an attrsOf (either str submodule).
I'm still torn as to whether most/all of our plugin keybinds should be transitioning towards lists at some point, but that's way beyond the scope of this PR 😂

Yes indeed, hard to choose.
I'm OK with this.


Implement an AugmentedJWT serializer/deserializer

To implement a token BackingStore for JWT we need the following:
new BackingStore[F, SecureRandomId, AugmentedJWT[HMACSHA256, UUID]] {
  def put(token: AugmentedJWT[HMACSHA256, UUID]): F[AugmentedJWT[HMACSHA256, UUID]] = ???
  def get(id: SecureRandomId): OptionT[F, AugmentedJWT[HMACSHA256, UUID]] = ???
  def update(token: AugmentedJWT[HMACSHA256, UUID]): F[AugmentedJWT[HMACSHA256, UUID]] = ???
  def delete(id: SecureRandomId): Eff[R, Unit] = ???
}

We need to serialize/deserialize the AugmentedJWT into a format that datastores can support.
My first thought is Circe encoders/decoders so we can go back and forth from a JSON string, but I'm open as long as there is some way to do it.

Hmm,
If you mean a circe instance, this is all possible, as every thing has its own way to be encoded.
However, it's hard to say exactly how people will serialize this. you could save an AugmentedJWT in a DB, a hash table on Redis by key, etc.
It's an interesting thing to think about. I'm unsure whether we need so much a default serializer, but rather some guidelines on how to serialize

@jarreds I will be closing this ticket. Here's my rationale:
A BackingStore for an AugmentedJWT or any Augmented field can be implemented in many ways, such as:

DB table with typed fields
Redis hash table with typed fields (at the driver level anyway, stringy in redis :sob: )
Some other in mem cache at the object level
Mongo in a Json..

Should I go on? It's hard to say how exactly to format it since it sort of depends on the user.
As far as a Json is concerned, there's no standard way to do it (that I'm aware of). The first two fields are json objects (base 64 URL-safe encoded), and the third is a base 64 URL-safe encoded signature. From there, you could choose say, typed keys with the sig as a hex string, or sig as an array of bytes... It really depends. If there is a standard json approach, I'd be happy to kick up the RFC tackle :D
Let me know if there's anything I can help you with, either here, or on gitter. Specifically though, I'm just unsure what a sane default is (if there is one).


[FLINK-34483][docs] Improve the documentation of 'state.checkpoints.dir' and 'state.checkpoint-storage'

What is the purpose of the change
'state.checkpoints.dir' and 'state.checkpoint-storage' are usually combined to configure the checkpoint location, and there some default behaviors are not adequately documented.

Checkpoint store / Checkpoint dir
Optional.empty()
A valid path

Optional.empty()
JobManagerCheckpointStorage without meta data persistence guarantees
FileSystemCheckpointStorage

'jobmanager'
JobManagerCheckpointStorage without meta data persistence guarantees
JobManagerCheckpointStorage with meta data persistence guarantees

'filesystem'
Illegal behavior
FileSystemCheckpointStorage

A class name
Customize checkpoint store
Customize checkpoint store

Brief change log

Add documentation for behaviors in various combinations of 'state.checkpoints.dir' and 'state.checkpoint-storage'.

Verifying this change
Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: ( no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: ( no )

Documentation

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

Thanks all for the review ~


Compile as a single binary

Just to cut down on the number of files we're shipping around. http://enclosejs.com?


Scrub error messages and add suggestions where appropriate

Tracking issue based on survey feedback. In general make sure that when error messages can give suggestions about how to fix the problem they should do so to assist the user.

Maybe we should add this as a requirement to the validation layer best-practices, in lieu of creating an issue that might conceivably remain open indefinitely?

@mark-lunarg yes, this should be standard practice going fwd. Where's best-practices doc? Special Considerations for Validation Layers of the CONTRIBUTING.md?


NLog Data provider: Add validation of data when setting up a configuration in user settings

will be managed in the centralized location for Analogy Data providers:
https://github.com/Analogy-LogViewer/Analogy.LogViewer.NLog/issues/2


Hyperion Segfaults on raspberry pi ZERO W with ws281x running archlinux

`Hyperion Ambilight Deamon (295)
Version   : V1.03.4 (brindosch-c750c41/dc6a602-1522918225
Build Time: Apr  5 2018 01:57:25
INFO: Selected configuration file: /etc/hyperion/hyperion.config.json
HYPERION INFO: ColorTransform 'default' => [0; 149]
HYPERION INFO: ColorCorrection 'default' => [0; 149]
HYPERION INFO: ColorAdjustment 'default' => [0; 149]
LEDDEVICE INFO: configuration:
{
"colorOrder" : "rgb",
"dmanum" : 10,
"freq" : 800000,
"gpio" : 18,
"leds" : 150,
"name" : "MyHyperionConfig",
"pwmchannel" : 0,
"type" : "ws281x"
}
whiteAlgorithm ::
INFO: Creating linear smoothing
HYPERION (CS) INFO: Created linear-smoothing(interval_ms=50;settlingTime_ms=200;updateDelay=0
EFFECTENGINE ERROR: no effects found, check your effect directories
EFFECTENGINE INFO: Initializing Python interpreter
INFO: Hyperion started and initialised
INFO: Json server created and started on port 19444
INFO: Proto server created and started on port 19445
INFO: Boblight server created and started on port 19333
Segmentation fault
`
ws281x example python scripts work fine

Did you find any solution?

Not sure if its a platform thing. I'm having segfault too. Using a pi 3 b+. I am trying to use around 450 leds. When i configure more then 250 leds I can't start hyperion. The setting "LEDS" does not matter. If I use a sum of 60 leds and this setting is 512, it works just fine. But when adding all of my leds (432). It doesn't work. So I've started deleting LED entries in the large array generated by hypercon. Around 250 items left then Hyperion starts.
{
"colorOrder" : "bgr",
"dmanum" : 10,
"leds" : 256, "name" : "Hyperion",
type"" : "ws281x"
}

Same issue for me with a raspberry pi 1B


Crashes on iOS simulator on MacOS images (AccessibilityControlExtension)

Description
Periodic crashes of processes on iOS Simulator, leading to UX tests failures, Processes crashing:

Prosesses in WebProcess pool (GPUProcess)
AccessibilityControlExtension - may of may not be related

Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] Ubuntu 24.04
[ ] macOS 12
[ ] macOS 13
[ ] macOS 13 Arm64
[X] macOS 14
[ ] macOS 14 Arm64
[ ] macOS 15
[ ] macOS 15 Arm64
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
https://identitydivision.visualstudio.com/IDDP/_build/results?buildId=1367703&view=logs&s=2b1cf740-7e83-5b38-9f56-89c750cf5d77&j=17b33f93-55d8-50b9-7cc6-cef868e6389b
Image version: 20240923.101
Is it regression?
Not sure
Expected behavior
Processes in WebProcess pool should not crash.
Actual behavior
Periodic crashes of processes on iOS Simulator, leading to UX tests failures, Processes crashing:

Prosesses in WebProcess pool (GPUProcess)
AccessibilityControlExtension - may of may not be related
crash_dumps_and_logs.zip

Repro steps
Run UI XCTest tests on iOS Simulator that involve WKWebView, for example - AAD or MSA sign-in. Periodically you will see failures due to GPUProcess process becoming unresponsive (likely a crash).

Hi @githubursul ,
We are looking into it. Will keep you posted.

Hi @githubursul New images have deployed this week 🎉
Could you please check and confirm if the issue still persist. If yes then could you please help us by providing more information to reproduce this issue?
Thank you.

Hi @githubursul Closing this issue for now, as no response on asked details for 3+ weeks.
Please open new issue if you are still facing similar issue with your workflows.
Thank you.


fix: oidc audience env variable was always read as a string

PT-1758 PT-1763.
Upgraded the django-environ.

KULTUS-API branch is deployed to platta: https://kultus-pr360.api.dev.hel.ninja :rocket::rocket::rocket:


Support request body inflate and gunzip when Content-Encoding header is appropriately set

If a client sends an HTTP request with "Content-Encoding" header set, co-body should be able to quickly pipe that to zlib and inflate the compressed request body prior to parsing the body.
I'd be happy to help and submit a PR, but I'd like to discuss how to implement first.  Any thoughts?  Is this something that needs to be done in raw-body or another lib?  raw-body needs the stream only, but each "buddy" in co-body needs the full HTTP request Object.  Might require a bit of refactoring?

I should also mention that the old Express body-parser lib supports HTTP request inflation:
https://github.com/expressjs/body-parser/blob/master/lib/read.js#L143-L176

SGTM
we can dep https://github.com/stream-utils/inflation

@coderhaoxin - I like it.  I'll submit a PR that modifies each "buddy" (i.e. lib/json.js) to use the inflation lib.

Just waiting for this to be merged...
https://github.com/stream-utils/inflation/pull/14

@bminer , @fengmk2

If a client sends an HTTP request with "Content-Encoding" header set, co-body should be able to quickly pipe that to zlib and inflate the compressed request body prior to parsing the body.

This PR should be reverted, as stated in #51, not all Content-Encodings are gzip. For example DeflateRaw and Brotli will make the parser fail and no body will be present.

@bminer can you fix @felixsanz's bug too?

@fengmk2 I think the inflate/decompress thing should be bundled in it's own middleware, like this:
app.use(bodyparser)
app.use(decompressBody) // some inflate middleware
// or app.use(brotli) <- decompress brotli bodies

This is a bodyparser, and that is the only thing that it should do. If the body is compressed or not I don't think it has anything to do with this middleware. It'll be a mess to support all encodings here (and the upcoming ones like the facebook's zstd).

I'm not so sure that I agree. If the HTTP body is compressed, the bodyparser should be able to decompress it in order to parse it. I see the argument for separate middleware, but gzip is the "standard".

Also deflate and gzip are supported by the inflation lib. Maybe Brotli can be added?

and what about deflateRaw? and zopli? and zstd? :/

Hmm, what errors do you get with an unsupported content encoding?

Nvm, looks like the inflation lib raises an "unsupported content encoding" error 415. Can you use a middleware to inflate the body and then set the content-encoding header to "identity"?

I can't inflate the body because there is no body :P The bodyparser here.
I should close the other issue and continue just here, right?

OK, here's my understanding co-body.  First, we inflate the req stream using the inflation lib.  Then, we pass that stream to raw-body to get the size-validated raw HTTP body Buffer.  Finally, the body is parsed using the logic in this lib.
The problem is that co-body expects req to be the stream from which the HTTP body should be read.  Rather, co-body should read from the inflated stream.  Is there a way in Koa to replace req with the stream returned from inflate(req)?
If not, it would be rather difficult to break the HTTP body inflation into a separate module.  Thus, the best way forward might be to add support for more compression algorithms into the inflation lib.  Right now, it supports zlib stuff, but it could be modified to add support for others.

@bminer As i said above, there is more compression methods than inflate/gunzip. You can't inflate a body that is not deflated. It's like trying to decompress a zip file with rar specific tools.
And i don't think modify the inflate lib is a good idea because inflate is inflate and brotli is brotli. Or at least the library should be renamed because naming it "inflate" when it decompress brotli is confusing as hell

@felixsanz - Fair point about the inflation lib being called "inflation".  Might be confusing if it supported brotli or zstd.  Maybe a better name would be decompress-stream?


Routing event fixes

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 0.10.999-cibuild0020410-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

Reverted all changes not related to fixes and addition of nameof

You can test this PR using the following package version. 0.10.999-cibuild0020432-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0020454-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]


chore: change repository structure

@hsgwa
I've confirmed that CARET_analyze works properly as well as previously. Could you check this PR ?
Best,


#1517 Fix ordered lists

What kind of change does this PR introduce?
This PR fixes #1517, where ordered lists would not correctly count and always keep the counter at 1. This issue has been introduced with #1487.
Additionally, tests have been added for ordered lists as well as sub-lists to avoid similar mistakes in the future.

Checklist:

[x] Unit Tests
[x] Documentation
[x] Update CHANGELOG.md
[x] Ready to be merged

Thanks.


Faker::Hacker.say_something_smart

Hi there! :) First, thanks for this awesome gem.
Related to Faker::Hacker.say_something_smart, the random phrases in general begin with a uppercase character, but some of the phrases begin just with a lowercase. It's just a cosmetic issue, but wanted to let you know.

Can you post an example of this? I can't replicate using ruby 2.3.
This is the relevant code, looks good to me.
https://github.com/stympy/faker/blob/master/lib/faker/hacker.rb#L24

I have noticed this happening as well.

@kivohin @kfrz @b264 As per my knowledge this issue is already resolved by @Newman101 in his commit. Can you please check it again. if still it present, then we will resolve it.
Thanks

@kfrz @SagareGanesh

See attached image for an example. I'm using faker v1.6.3 and Ruby v2.3.0.

@kivohin That'll be your issue. You can see here this issue was merged and fix as of July 25th #625 which is tagged v1.6.6 -- you should update your version of the gem and this will be resolved.

@kivohin try running bundle update faker -- or just bundle update to try to update everything.

@kfrz You're right! This has been fixed already, the strange thing is that I added the faker gem to my project 19 days ago on September 11, and it installed by default v1.6.3 without myself specifying any version, I don't know why really.
@b264 Yes! I used bundle update faker and it updated to v1.6.6 and now the issue isn't there anymore, thanks!


Document aggregator permissions

We now have 3: clusterAdmin, clusterRead, and namespaceAdmin (previously namespaced)
We need to make a docs page to describe them and the motivations/use cases for having them at all.

@johnSchnake I would like to work on it.

👍 Sounds great; just like the other doc PRs you put up:

put it under the 'main' set of docs, not a certain version (when we cut a new version it will get put there from now on)
Put up the PR for me to review, I'll help you wrap it up
Make sure it links to some main page. I think this could even go under the main README under known issues (e.g. if you have an issue with permissions in your cluster but you still want to run Sonobuoy ...). Just know that editing the readme is a bit different than other doc pages. You need to edit the README.md thats in the root of the project, not the README.md thats in the docs. Then run the ./scripts/sync_readme.sh script (I think thats the name, I could be off slightly). Its just weird because the README gets used by Github and the docs site, and the links have to be formatted differently for each.

@johnSchnake This is about the feature we added here. Looking forward writing document on it.
Thanks again

Correct; theres now:

clusterAdmin

clusterRead

namespaceAdmin (you had added it as namespaced, I changed the name after it got fixed up and the others were added. Just makes it more consistent).

clusterAdmin is the default. Able to do pretty much everything on everything. Most of these are required for the e2e conformance tests to work since they create/destroy namespaces, pods, etc etc

namespaceAdmin is just ability to do CRUD ops in a single namespace. Sonobuoy does not create the namespace so it needs to already exist and you have to run --skip-preflight to avoid Sonobuoy complaining about that. e2e tests WILL NOT work in this mode, they won't even start because it has startup logic that requires looking in kube-system and checking nodes. Daemonsets will also not work in this mode because we monitor them in a way that we require GET on /nodes so that we know which nodes were responding with results. Since we have NO cluster permissions, we can't get nodes, so we can't know which results to get or wait for, so we just ignore daemonsets.

clusterRead was a compromise between those two. Adds ability to GET any resource from the API so that the sonobuoy queries work OK, we are able to get nodes so daemonsets run fine, and e2e tests can technically start. We can't create namespaces so e2e tests can't run in this mode in any useful manner either. However, this may be a more reasonable mode to run less intrusive, custom plugins in. In this mode we don't create the namespace either so it has to be created first and sonobuoy run with the --skip-preflight flag.

Let me know if you have other questions about the feature.


no patterns matched tag="e26d790146cb"

Hi. I am using fluentd inside docker container. I am collecting logs from other docker containers and trying to stream logs into sqlite3. I am using fluent/fluentd:v1.5-debian-1 version of fluentd.
I downloaded sqlite3 plugin from here. https://github.com/cosmo0920/fluent-plugin-sqlite3
Here is my dockerfile
FROM fluent/fluentd:v1.5-debian-1

# Use root account to use apt
USER root

# Download sqlite3 and create a db file. Run sql script to build a table
RUN apt-get update && \
	DEBIAN_FRONTEND=noninteractive apt-get -yq install sqlite3 libsqlite3-dev

RUN mkdir /db
RUN touch /db/logging.db
COPY db.sql /db/
RUN /usr/bin/sqlite3 /db/logging.db < /db/db.sql

# Download sqlite3 plugins -> This is same as guidance here https://github.com/fluent/fluentd-docker-image
RUN buildDeps="sudo make gcc g++ libc-dev" \
 && apt-get update \
 && apt-get install -y --no-install-recommends $buildDeps \
 && sudo gem install fluent-plugin-sqlite3 -v 0.1.0 \ # download sqlite3 plugin
 && sudo gem sources --clear-all \
 && SUDO_FORCE_REMOVE=yes \
    apt-get purge -y --auto-remove \
                  -o APT::AutoRemove::RecommendsImportant=false \
                  $buildDeps \
 && rm -rf /var/lib/apt/lists/* \
 && rm -rf /tmp/* /var/tmp/* /usr/lib/ruby/gems/*/cache/*.gem

# copy the plugin into fluentd/plugins because it wasn't copied by gem install
RUN cp -r /usr/local/lib/ruby/gems/2.6.0/gems/fluent-plugin-sqlite3-0.1.0/ /fluentd/plugins

USER fluent

As you can see, I setup sqlite3 and downloaded the plugin. I copied the plugin into fluentd's plugins folder.
Here is my db.sql
CREATE TABLE LOGGING (
    container_name VARCHAR(20),
    container_id   VARCHAR (100),
    source         VARCHAR(20),
    log            TEXT
)

It literally creates one table.
And here is my conf file.
<source>
  @type forward
  port 24224
</source>

<match sqlite3.**>
  @type   sqlite3
  path    /db/logging.db
  table   logging
  columns container_name, container_id, source, log
</match>

Also, here is the docker logs of fluentd container
2019-06-03 07:10:02 +0000 [info]: parsing config file is succeeded path="/fluentd/etc/fluent.conf"
2019-06-03 07:10:03 +0000 [info]: using configuration file: <ROOT>
  <source>
    @type forward
    port 24224
  </source>
  <match sqlite3.**>
    @type sqlite3
    path "/db/logging.db"
    table "logging"
    columns "container_name, container_id, source, log"
    <buffer>
      flush_mode interval
      retry_type exponential_backoff
    </buffer>
  </match>
</ROOT>
2019-06-03 07:10:03 +0000 [info]: starting fluentd-1.5.0 pid=7 ruby="2.6.3"
2019-06-03 07:10:03 +0000 [info]: spawn command to main:  cmdline=["/usr/local/bin/ruby", "-Eascii-8bit:ascii-8bit", "/usr/local/bundle/bin/fluentd", "-c", "/fluentd/etc/fluent.conf", "-p", "/fluentd/plugins", "--under-supervisor"]
2019-06-03 07:10:03 +0000 [info]: gem 'fluent-plugin-sqlite3' version '0.1.0'
2019-06-03 07:10:03 +0000 [info]: gem 'fluentd' version '1.5.0'
2019-06-03 07:10:03 +0000 [info]: adding match pattern="sqlite3.**" type="sqlite3"
2019-06-03 07:10:03 +0000 [info]: adding source type="forward"
2019-06-03 07:10:03 +0000 [info]: #0 starting fluentd worker pid=15 ppid=7 worker=0
2019-06-03 07:10:03 +0000 [info]: #0 listening port port=24224 bind="<IP_ADDRESS>"
2019-06-03 07:10:03 +0000 [info]: #0 fluentd worker is now running worker=0
2019-06-03 07:10:04 +0000 [warn]: #0 no patterns matched tag="e26d790146cb"
2019-06-03 07:10:04 +0000 [warn]: #0 no patterns matched tag="e26d790146cb"
2019-06-03 07:10:05 +0000 [warn]: #0 no patterns matched tag="678704409bba"
2019-06-03 07:10:05 +0000 [warn]: #0 no patterns matched tag="678704409bba"
2019-06-03 07:10:05 +0000 [warn]: #0 no patterns matched tag="678704409bba"
2019-06-03 07:10:06 +0000 [warn]: #0 no patterns matched tag="678704409bba"
2019-06-03 07:10:06 +0000 [warn]: #0 no patterns matched tag="678704409bba"
2019-06-03 07:10:07 +0000 [warn]: #0 no patterns matched tag="678704409bba"
2019-06-03 07:10:13 +0000 [warn]: #0 no patterns matched tag="678704409bba"
2019-06-03 07:10:23 +0000 [warn]: #0 no patterns matched tag="678704409bba"
2019-06-03 07:10:42 +0000 [warn]: #0 no patterns matched tag="678704409bba"
2019-06-03 07:10:58 +0000 [warn]: #0 no patterns matched tag="678704409bba"
2019-06-03 07:11:18 +0000 [warn]: #0 no patterns matched tag="678704409bba"

Would you happen to know why I am having troubles? I literally have no clue why it doesn't work and debug hard to figure it out... I will appreciate any sort of help!

Turns out I didn't add a tag to my input stream. Closed

BTW, if you have a question or problem about a configuration next time, please post it to mailing list 😄
See  https://github.com/fluent/fluentd/blob/60e3a4c544256426afc37017290896709ad8bf47/CONTRIBUTING.md#got-a-question-or-problem

Don't use Github issue for asking questions

My bad!! I will use mailing list from the next time! Thank you for letting me know.


No instance_mask for the RedWood dataset?

Hi. Thank you for releasing such a wonderful work~
I'm trying to evaluate pretrained models such as CR-Net on the redwood dataset, and I have configured the dataset as required. However, when I  run  the evaluate code there is an error regarding the absence of instance masks? Do I need any additional processing for the RedWood dataset?
I'm looking forward to your reply!? looking forward to your reply.

I'll look into it tomorrow and see if I can reproduce the issue.

Thank you very much for your quick reply. After resetting the relevant code, I have successfully tested the RedWood dataset and also successfully tested my own model. Sorry to bother you, thank you again!

Great, happy to hear.


Default value of tracecback in the constructor to be ''

Currently the default value of traceback is None:
def __init__(self, stdout, stderr, traceback=None, rc=None):
And that value is only filled in if there is an exception in Sultan.run(); if the user unaware of that calls Result.print_traceback(), there's a general exception
TypeError: 'NoneType' object is not iterable

, coming from Result.__format_lines()'s iterator over the Result.traceback.
If the default is changed to an empty string, the exception won't occur and print_traceback() will behave like the other two print methods.

Wow, thank you for catching that. I'll review your both PRs within the next 2-3 days and get back to you.

This one is not PRed :), yet it's a one-liner.

This is resolved. Please use Sultan==0.7.1


[karma-esm] allow nodeResolve to be an object

The karma-esm docs have the nodeResolve type listed as a boolean, but the es-dev-server docs allow for the nodeResolve option to be an object with extra settings that get passed to the rollup plugin.  Is it possible to allow that object to be set in the karma-esm config?

I took a look at this, and it seems like although that type is listed as a boolean, it is indeed accepting an object that's getting passed through to the node-resolve plugin. This might not be an actual bug, but more a documentation error.

Indeed the docs should be updated.

we recommend @web/test-runner. If the issue persists there feel free to open an issue at https://github.com/modernweb-dev/web


Hooks release v0.1.8 breaks the build

Description
After upgrading hooks (under the hood) from version 0.1.7 to 0.1.8, the build process encountered a missing module error ( @react-native-community/clipboard ). This issue needs to be addressed to ensure that the package can be upgraded without causing build failures.
gluestack-ui Version
1.0.8
Platform

[ ] Expo
[X] React Native CLI
[ ] Next
[ ] Web
[ ] Android
[ ] iOS

Other Platform
No response
Additional Information

Hey @hristo87, Please try again issue is fixed now.

Confirm, its fixed! Thanks


RDK-29308 :support for custom http headers configured by Resident app - centrally configured to include user privacy flags

Reason for change: Propogated http headers to aamp injected bundle.
Test Procedure: monitor http request from aamp to check for http header for privacy.
Risks:Low
Signed-off-by: shripad bankar<EMAIL_ADDRESS>

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Question about database feature

At first thank you very much for your hard work.
Anyway I have a question whether do you plan to store longer history on any database (like Nightscout) for statistic's features or not ?

@tloczekt No, this is live data from CareLink everything is on your local computer I don't have any database. The one place I might is in active insulin time where it am missing the first x values where x is active insulin time * x and that would just be to show the beginning of the graph. You can save snapshots of interesting data (and reload later) from the Start menu and the program keeps 1 snapshot in case of a crash.


Research using MySQL views to aggregate metrics.

Maybe fork this package for an upstream dependency.  We would need to write tests and verify it works for our needs.
We could also implement this functionality in our project, independently of any upstream packages.

Research has found that using MySQL views diminishes performance over building queries normally.  It would also require more work to get them functional with the Django ORM.


40x & 50x Emissary Traces not categorised as ERRORS in Datadog

Describe the bug
We have 2 emissary ingresses running in our EKS cluster.
They are successfully integrated with a Datadog Agent pushing traces to our DataDog Backend.
We are now receiving the traces/spans in DataDog but their statuses are not being classified correctly - everything is classified as "OK".
According to Datadog support, this is an issue with how the Ambassador team sends the attributes with their traces.
This is the response we have gotten from DataDog Support :
...
It looks like the root issue is that Ambassador has made a mistake when implementing our tracing library that is causing error spans to not be properly marked.
To help you if you're interested in filing a bug report with Ambassador, my reasoning is below:

Currently, spans submitted by the Ambassador are being marked as errors, but are not following our conventions for how to mark the errors.
Spans from Ambassador are setting the span attribute @error to "true", where we expect the span tag status to be set to error and the error span tag to be set to 1 (you can see the difference between span tags and attributes [here](https://docs.datadoghq.com/tracing/trace_collection/tracing_naming_convention/#span-tags), to clarify further).
To fix this on their end, they can use the set_error method to automatically follow our conventions for flagging errors which you can see in our documentation on this here.
...

Links sent by DataDog:
https://docs.datadoghq.com/tracing/trace_collection/tracing_naming_convention/#span-tags
https://docs.datadoghq.com/tracing/trace_collection/custom_instrumentation/ruby/dd-api/#setting-errors-on-a-span
To Reproduce
Steps to reproduce the behavior:

Install Emissary - version below
Install Datadog Agent - version below
Connect traces to Datadog Backend via DD Agent
Check Traces

Expected behavior
We are supposed to see traces with HTTP error code 50x & 40x as errors. Instead they are being ingested as "OK" similar to 200 status codes.
Versions (please complete the following information):

Ambassador Emissary: v8.9.1
Datadog Agent: v3.70.1
Kubernetes environment - EKS v1.30

Please help. Thanks!

+1

Status code 101 flagged as ERROR

503 and 404 flagged as OK

emissary-ingress 3.9.1 is on envoy 1.27.2 which have this issue
tested using emissary-ingress 3.10.0-rc.0 which on envoy v1.30.3 fixed the issue

I see the last General Release has been Nov 20th 2023.
Do we know if there is any plan to make 3.10.0-rc.0 as a GR? Any timeline on that as we do not want to use RC in PROD.

Just wanted to check again if there has been any update on the GA release for v3.10.0?
Thanks!


Question: Can we change the audio channel to a file?

Is it possible when transcoding to select a media file. Eg: MP3 file? And replace/add the audio channel?

Currently this library does not support manipulation of video.
It just transcodes (compresses) it.

Thanks. No worries.


Msig Debot should allow custom msigs

Currently, msig debot checks the codehash of the multisig to make sure it's one of five specific implementations.
However, when using 24 hour msig for example, you usually make the change in the contract and compile it on your own, leading to the codehash sometimes being different (due to difference in compiler version).
This is the case with the Academy subgov msig for example. So they can't use the debot to sign transactions.
I suggest to either remove those checks, or allow the user to choose to use his msig even though it's not official.

Also I beliave it should be possible to invoke msig debot with passing custom payload


allow specification of required JWT claims

In researching JWT contents for CHRON-230, I came across consensus that specific claims are well worth checking for expected values, so this PR includes ability to have Chronicle check them accordingly before accepting a JWT. This work is enough separable from the main work for the ticket.
So, for instance, in testing with JWTs from Auth0, one might set JWT_MUST_CLAIM_ISS to one's Auth0 tenancy and JWT_MUST_CLAIM_AUD to the application API created therein. I also set JWT_MUST_CLAIM_AZP to the application's client ID. This is part of ensuring that the JWT was created for the use of Chronicle.
I avoided making any specific check mandatory, to cover for variations in deployment environment.

Part of my thinking in separating these from OPA policy rules, aside from performance, was that they are about if we believe the claims at all, whatever they are, and they may vary by authentication provider configuration, so environment variables will make it easier for the integrators to adjust for that. I was more comfortable with propagating the claims through various layers into Chronicle only if we already believed them, regardless of what they authorize the user to do.


Revert "Nokogiri <IP_ADDRESS> pre release"

Reverts alphagov/frontend#898
Nokogiri will be cutting an official release soon after more testing. This hacked together release is causing some developers issues with building Nokogiri, and the security vulnerabilities are no longer thought to be too severe.
Reverting all PRs that use this temporary release.
/cc @bradwright

I still think we should be going to v<IP_ADDRESS>, as without that we're exposed to the more severe CVEs.


$compile a string with  causes browser to load images.

I would expect the browser to not download the image, because I have not added anything to the DOM at this point. When I run this example in Chrome it does download the image.
If this is expected behavior, I cannot find anything in the documentation about it. This happens if using ng-src or using src, I see no difference either way.
I supposed that the current behavior is correct, but my issue is that the documentation doesn't explain why. Does calling $compile() modify the DOM? Does it explicitly call new Image when compiling a string containing ? Why does this happen? Is it creating nodes? elements? DOM? It could be documented better.

This is normal course of business for HTML, per https://html.spec.whatwg.org/multipage/embedded-content.html#the-img-element --- when the src attribute is set (either during parsing or via JS), a new request is made (which may result in fetching cached image data).
If you need the DOM to be inate, you could wrap it in a <template> element (at a cost of greater complexity and reduced browser support)

@caitp  Thanks, I'm clear on the spec about setting .src on an img element, I use that to preload images with new Image syntax. What clears it up for me is your last sentence. The compiler is creating document fragments (documentation for states its creating "templates" which is not so clear). I can see this now in the source code, $compile calls into jqLite, which calls document.createElement(). Makes sense now. This link was helpful to me - https://developer.mozilla.org/en-US/docs/Web/API/DocumentFragment


Some weird stuff incorrectly reported as Groff

https://github.com/matiasinsaurralde/facebook-tunnel/search?l=groff
https://github.com/matiasinsaurralde/facebook-tunnel/blob/b82adf540c9b8c8563f7caecde135ceb9b7a9592/gumbo/autom4te.cache/traces.1

Also:
https://github.com/danielmiessler/SecLists/search?l=groff
https://github.com/danielmiessler/SecLists/blob/6babb9ec9ad6f6b594380797b78b734500c1c453/URLs/urls_joomla_3.0.3
https://github.com/danielmiessler/SecLists/blob/6babb9ec9ad6f6b594380797b78b734500c1c453/URLs/urls_wordpress_3.3.1

Same as #2415.


Importing playlist on mobile data crashes app

Reproduce:
Import new playlist crashes and sends user back to main activity. This only happens when the user is on mobile data.

Task:
Change Line #150 of AddNewPopupSingleActivity.java
Dialog dialog = new Dialog(getApplicationContext());
to
Dialog dialog = new Dialog(AddNewPopupSingleActivity.this);

https://github.com/ErikNguyen20/TuneStacker/commit/dd4a2de3ede5fc2e68d2423c24f5eb99b608df46


uv pip install sometimes results in error: Cannot uninstall package; RECORD file not found at ...

When running
python -m uv pip install --system --prerelease=allow -r pyproject.toml
I am hitting the error:
error: Cannot uninstall package;
RECORD file not found at: C:\Users\{USER}\AppData\Local\Programs\Python\Python310\Lib\site-packages\catboost-1.2.2.dist-info\RECORD

Which seems to be a common error in other installation systems (ie. not uv specific):
https://stackoverflow.com/questions/68886239/cannot-uninstall-numpy-1-21-2-record-file-not-found
That said, if uv has any mitigation for this - that'd be great.
Using uv 0.1.16 on Windows 11

That's interesting, can you share more on the dependencies included to trigger this? If we can repro reliably, we can probably fix it.

Not sure what caused it, It may be that I killed a process mid-way through a pip install (I'm cautiously moving from pip to uv these days).
I tried pip uninstalling catboost (which succeded) but the issue remained when re running uv pip install
The solution was to navegate to
C://Users/{USER}/AppData/Local/Programs/Python/Python310/Lib/site-packages/
and rm -r catboost-1.2.2.dist-info/ which was empty

Ah, now the issue with catboost is solved, but I hit the same issue with matplotlib
error: Cannot uninstall package; RECORD file not found at: C:\Users\mkleinbort\AppData\Local\Programs\Python\Python310\Lib\site-packages\matplotlib-3.8.2.dist-info\RECORD

Ok, mostly managed to reproduce the issue

When running uv pip install to install a newer version of a package
and I hit the error described here: https://github.com/astral-sh/uv/issues/1491#issuecomment-1983615072
When I re-run the uv pip install I hit the error described here on the package on which the error (2) was hit
So I go and manually delete the {package}-dist-info/
now that package installation succeeds, but I hit the https://github.com/astral-sh/uv/issues/1491#issuecomment-1983615072 somewhere else and it continues so

I hope this will succeed once for all the packages and then become a quicker way to install new versions than pip

Ok, just FYI - it did work after 42 runs and re-runs of uv pip install
But it was worth it - now my "update dependencies" workflow has gone down from 4 minutes (via pip) to basically nothing

Ah interesting, so you're on Windows and you're hitting that even with the latest version. Hmm...

Ah okay, sorry, I misunderstood -- so you're hitting https://github.com/astral-sh/uv/issues/1491#issuecomment-1983615072 which is causing there to be "incomplete" packages in the site-packages, got it.


chore: create getter for contract address on deploy account

This change is

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

#411  👈
#410
#399
#398
#397
#396
main

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

Join @ArniStarkware and the rest of your teammates on  Graphite

No need for this PR.


[SPARK-20408][SQL] Get the glob path in parallel to reduce resolve relation time

What changes were proposed in this pull request?
This PR change the work of getting glob path in parallel, which can make complex wildcard path more quickly, the mainly changes in details:
1.Add new function getGlobbedPaths in DataSource, return all paths represented by the wildcard pattern, use a local thread pool to do this while the paths number expanded from patten lager than spark.sql.sources.parallelGetGlobbedPath.threshold. The local thread pool size controlled by spark.sql.sources.parallelGetGlobbedPath.numThreads
2.Add new function expandGlobPath in SparkHadoopUtil, to expand the dir represented by the patten, here we mainly reuse the logic in org.apache.hadoop.fs.Globber.glob().
How was this patch tested?
Add UT in SparkHadoopUtilSuite.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/430/
Test PASSed.

Test build #92243 has started for PR 21618 at commit 1068aa9.

@cloud-fan As our discussion in #17702, this is the reimplement for expanding the patten. Please have a look when you have time, thanks!

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/431/
Test PASSed.

Test build #92244 has started for PR 21618 at commit a702551.

Test build #92244 has finished for PR 21618 at commit a702551.

This patch fails Java style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92244/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/432/
Test PASSed.

Test build #92245 has started for PR 21618 at commit e210c13.

Test build #92245 has finished for PR 21618 at commit e210c13.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Test build #92243 has finished for PR 21618 at commit 1068aa9.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class SparkGlobber

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92245/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92243/
Test FAILed.

Test build #92250 has started for PR 21618 at commit e210c13.

Test build #92250 has finished for PR 21618 at commit e210c13.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92250/
Test FAILed.

Test build #92266 has finished for PR 21618 at commit 9b8a4b3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92266/
Test FAILed.

Test build #92305 has started for PR 21618 at commit f8bd814.

Test build #92306 has started for PR 21618 at commit c026a8c.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/462/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92306/
Test PASSed.

Test build #92305 has finished for PR 21618 at commit f8bd814.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92305/
Test PASSed.

gental ping @cloud-fan @gatorsmile

Test build #92758 has started for PR 21618 at commit d4add07.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/780/
Test PASSed.

Test build #92758 has finished for PR 21618 at commit d4add07.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/92758/
Test PASSed.

gental ping @cloud-fan @gatorsmile @kiszk

@kiszk @maropu Great thanks for your review and advise! I'll address them and resolve the conflicts ASAP.

Test build #95843 has started for PR 21618 at commit 1319cd3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2953/
Test PASSed.

Test build #95843 has finished for PR 21618 at commit 1319cd3.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95843/
Test FAILed.

retest this please

Test build #95851 has started for PR 21618 at commit 1319cd3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2960/
Test PASSed.

Test build #95851 has finished for PR 21618 at commit 1319cd3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95851/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3116/
Test PASSed.

Test build #96077 has started for PR 21618 at commit 95726e9.

Test build #96077 has finished for PR 21618 at commit 95726e9.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class SparkHadoopUtilSuite extends SparkFunSuite with Matchers with LocalSparkContext

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/96077/
Test FAILed.

Test build #96090 has finished for PR 21618 at commit 95726e9.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class SparkHadoopUtilSuite extends SparkFunSuite with Matchers with LocalSparkContext

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/96090/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4189/
Test PASSed.

Test build #97699 has started for PR 21618 at commit 95726e9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4196/
Test PASSed.

Test build #97726 has started for PR 21618 at commit 95726e9.

Test build #97735 has started for PR 21618 at commit 95726e9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4221/
Test PASSed.

Test build #97699 has finished for PR 21618 at commit 95726e9.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class SparkHadoopUtilSuite extends SparkFunSuite with Matchers with LocalSparkContext

Test build #97726 has finished for PR 21618 at commit 95726e9.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class SparkHadoopUtilSuite extends SparkFunSuite with Matchers with LocalSparkContext

Test build #97735 has finished for PR 21618 at commit 95726e9.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class SparkHadoopUtilSuite extends SparkFunSuite with Matchers with LocalSparkContext

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97726/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97699/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97735/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4242/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4253/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/4277/
Test PASSed.

Test build #97803 has finished for PR 21618 at commit 95726e9.

This patch fails to generate documentation.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class SparkHadoopUtilSuite extends SparkFunSuite with Matchers with LocalSparkContext

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97803/
Test FAILed.

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/15757/
Test PASSed.


Create a letsencrypt role and set up webhook certs

Create a role that can do letsencrypt certificate fetching and renewal
and set up the zuul server to proxy requests to the github webhook port
so github can do secure requests.
This is on the same port as the status.json which we might want to have
a look at.
Signed-off-by: Jamie Lennox<EMAIL_ADDRESS>

Build failed.

http://logs.bonnyci.com/check_github/BonnyCI/hoist/140/1486970948.38/ubuntu-hoist : FAILURE in 19s
http://logs.bonnyci.com/check_github/BonnyCI/hoist/140/1486970948.38/ansible-syntax : SUCCESS in 14s
http://logs.bonnyci.com/check_github/BonnyCI/hoist/140/1486970948.38/hoist-checks : SUCCESS in 21s

Build failed.

http://logs.bonnyci.com/check_github/BonnyCI/hoist/140/1487024691.42/bonnyci-run-check-multinode : FAILURE in 53s

Build failed.

http://logs.bonnyci.com/check_github/BonnyCI/hoist/140/1487026933.79/bonnyci-run-check-multinode : FAILURE in 1m 25s

:+1: looks good to me, but should get some more reviews before approving


Implement fullGetEnv function

as a wrapper to call g_fn.getenv and a manual parsing of environ
when scoping bash calling getenv("SCOPE_CONF_PATH") will return NULL

Ref: https://github.com/criblio/appscope/issues/401
Fixes: #1502

My init intentions after the discussion:

provide comment about the source of implementaiton fallback implementaiton of fullGetEnv
use fullGetEnv in every valid place in our code
get rid off g_fn.getenv and depend only on environ parsing directly - the fallback implementaiton


Issue35 Documentation added and rotational tests

Here I have modified the README.md file, adding documentation and Travis badget.
Besides I have made the tests for rotation programs. I have to mention that the tests passed, but on several occasions fail, I think that it is because some random number that is not taking the seed. But it's just a matter of readjusting the tolerance or running the test again.

Fix issues #35 #33 and #50


[FEATURE-REVIEW] Single Peer Connections

In this PR I want to propose to change our current approach to support Single Peer Connections.
Main advantage: reduce usage of UDP ports and time to subscribe to new streams.
Please, provide as much feedback as possible to this proposal!!

the two message flow  is the same.  maybe you refer the wrong image

good catch @notedit ! I've fixed it already.

@jcague will this change leave Multiple Peer Connections still working and add Single Peer Connection as an option? Also, wasn't clear to me after reading your diagrams if it will provide backward compatibility or not? Thanks and good work!

@zevarito yep, that's something that we should tackle in the document. Thanks for the heads up!

@aalonsog @lodoyun @notedit @zevarito I updated this document with further logic / architecture / comments, can you review it again and provide feedback, please?

In general I do like the direction you are proposing for this.
A couple of thoughts:

ErizoClient should be in charge of absorbing the implementation differences in the browsers. We could gradually enable single PeerConnection in different browsers as we implement it.

We should define in this stage a working policy for ErizoController. For instance, by default, the policy should try to keep rooms within the same ErizoJS whenever possible and evenly distribute the rooms evenly among the available ErizoJs processes. I know there are a million ways to optimize this but it's a start.

@lodoyun good catch! I just added a simple policy that could help us as a starting point and commented your first point in the document.

I'd like to finish this review on Monday if I don't receive more feedback/requests. We will be able to change it in the future whenever we find issues,
@jnoring any thoughts or feedback on this feature?

hi  @jcague    that means   we can use  multi  streams over on peerconnection  in  client side?

i see the  this planB  https://tools.ietf.org/html/draft-ietf-rtcweb-rtp-usage-26

it seems that  webrtc will support  Unified Plan.
https://bugs.chromium.org/p/chromium/issues/detail?id=465349


It crash so much v2

Plz, fix this, it crash every hour

Previous topic: https://github.com/processhacker/processhacker/issues/761#issuecomment-770621882

Update to the latest version v3.0.3779

After it crashes, create a memory dump for processhacker.exe and upload it:

To start with, I always keep it up to date
Here it's the dump file: ProcessHacker.rar

Did you create the dump before or after it crashed? There's no crash information in the dump and nothing invalid.

I've found the offending code that was causing that crash and was fixed in the latest nightly build r3859
Thanks for reporting it 👍


Move state handling into the webserver

The main goal of this PR is to fix issue #12, which it accomplishes by making the webserver report its current state (busy, command, etc) through a simple JSON API, so the browser is no longer responsible for determining when the printer is working.  This also allowed me to do some refactoring and simplification where it made sense in the context of my changes.  In particular I've:

Removed the delay(500) from state changes (on the esp32) since the web-ui no longer requires it to show a consistent state.
Consolidated the javascript logic that disables/enables input controls based on the "busy" state into a single method (to avoid duplication)
Moved the UI properties for #progress-bar and #size-helper from javascript into CSS (they get changed based on data attribute selectors)
Changed as much http request-based javascript as possible to use promises (ie the async/await/fetch syntax).
Changed the javascript status polls to only make a new request after the previous one finishes, which prevents requests from queuing up and hammering the webserver during transient disconnections.
Simplified the web server init code, which required updating the AsyncWebServer dependency.
Added some TODO's for areas where I intend to add funtionality later

To the best of my ability this makes no change to the appearance or effective styling of the web interface.  One benefit of this PR is that if the page is refreshed while printing its printing status will still be reflected after the refresh, ie preventing you from submitting a label until the previous one finishes.  In such a case it won't show the proper label text, but I intend to address that in follow-up PR's as it requires more substantial refactoring to be done cleanly.

This PR is showing some differences from changes that have already been merged into main, so I'm going to close this and re-create it.


newer version of fluentd tries to get pod metadata for nopod dummy alias?

Seeing a lot of nopod errors in the k8s logs whilst testing an update to the fluent/fluentd images (logs-dispatcher) - seemingly caused by https://github.com/uselagoon/lagoon-charts/blob/main/charts/lagoon-logging/templates/logs-dispatcher.fluent-conf.configmap.yaml#L281
Initial investigations show that the kubernetes_metadata_filter plugin gets updated - which may be to blame, but not sure if this can be avoided somehow?
https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter/compare/v2.10.0...v3.1.2#files_bucket
2022-11-09 02:59:05 +0000 [error]: #1 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/lagoon-core/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api
2022-11-09 02:59:05 +0000 [error]: #1 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/docker-registry-cache/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api
2022-11-09 02:59:07 +0000 [error]: #0 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/lagoon-core/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api
2022-11-09 02:59:07 +0000 [error]: #0 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/lagoon-core/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api
2022-11-09 02:59:08 +0000 [error]: #1 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/docker-registry-cache/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api
2022-11-09 02:59:08 +0000 [error]: #0 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/lagoon-core/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api
2022-11-09 02:59:09 +0000 [error]: #0 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/lagoon-core/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api
2022-11-09 02:59:09 +0000 [error]: #0 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/lagoon-core/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api
2022-11-09 02:59:10 +0000 [error]: #0 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/lagoon-core/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api
2022-11-09 02:59:11 +0000 [error]: #0 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/lagoon-core/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api
2022-11-09 02:59:11 +0000 [error]: #1 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/as-demo-shorter-branch-for-testing/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api
2022-11-09 02:59:11 +0000 [error]: #1 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/lagoon-core/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api
2022-11-09 02:59:12 +0000 [error]: #0 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/as-demo-shorter-branch-for-testing/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api
2022-11-09 02:59:12 +0000 [error]: #0 Exception 'HTTP status code 404, pods "nopod" not found for GET https://<IP_ADDRESS>/api/v1/namespaces/as-demo-shorter-branch-for-testing/pods/nopod' encountered fetching pod metadata from Kubernetes API v1 endpoint https://<IP_ADDRESS>:443/api

I'm not sure if there's anything we can do about this through configuration. The problem is that we only have a namespace name in the log record, and we are trying to enrich it with namespace labels. There is never any valid pod name in the log record. So to fix this error message I guess that either:

the k8s metadata plugin adds support for scraping namespace info only; or
we write a plugin that scrapes namespace info only, and use that instead.

The first option seems most realistic but not sure what the priority would be.

I looked into this a bit more, here is where this error message was bumped from debug to error.
I'll create an issue upstream to discuss if error is the correct level here


Ambiguity on word definition

From this section:

The core element of the protocol is the word, which is a sequence of zero or more characters delimited by any run of unquoted whitespace.

The definition of word here is ambiguous.  Is the empty unquoted string a word?  (Current implementations of the tokeniser say no, and, indeed, this is necessary to allow interpreting multiple-character whitespace runs as if they were one character.)  If so, is the empty quoted string a word?  (Current implementations say no, but this is almost certainly a bug, because it means we can't understand empty strings.)

Fixed ages ago.


Faster time to first job

There should be a wait_for_cluster function that polls till the cluster is running and a wait_for_workers function that runs an empty Slurm job with sbatch with the given number of workers.
Then, we should modify create_cluster to call wait_for_cluster and create_job to also call wait_for_cluster.
Finally, create_cluster should have an option to start with an initial number of workers. The # of workers should be converted into a # of nodes and used to initialize the cluster with that as a minimum number of nodes. Then, when the first job is run, the # of nodes is updated to be 0. This allows the cluster head node and job nodes to be created at the same time instead of one having to happen before the next. It means that the user has a much simpler onboarding expience: just call create_cluster with num_initial_workers specified, wait for it to return, and then run create_job and it should start the job in not more than a couple minutes. Total time to start a job should be not more than 15-20 minutes which is almost as good as the 5-10 minutes that Coiled has.

Relevant issue: https://github.com/aws/aws-parallelcluster/issues/3322
Also, in addition to wait_for_workers, there should also be a wait_for_job that will poll until a job is available. This will involve a backend f sending a message to the cluster which sends something to the client side indicating the availability of the job.
And to be clear, it's not enough for wait_for_workers to just launch off a job, it also needs to poll on the client side.

[ ] Implement wait_for_cluster
[ ] Modify create_cluster and create_job to call wait_for_clusters
[ ] Modify create_cluster to accept a minimum number of workers to always keep running on the cluster
[ ] Implement wait_for_workers

@cailinw Is this finished? If so can you update the checklist above and close this?

We did it!!! Awesome work @cailinw :tada:


Route is not recalculated when user is off route

It would be good to recalculate the route when user is off-route, as per the Mapbox rerouting documentation. Currently, locationManager.requestLocation() is called once, so handleLocationUpdate is only called once, which so the following directions calculation is done only once (when TrackableReadyToTrackEvent is fired), at the start:
        directions.calculate(options) { [weak self] (_, result) in
            guard let self = self else { return }
            switch result {
            case .failure(let error):
                self.handleErrorCallback(error: ErrorInformation(error: error))
            case .success(let response):
                guard let route = response.routes?.first else {
                    let errorInformation = ErrorInformation(type: .publisherError(errorMessage: "Missing route in Directions response."))
                    self.handleErrorCallback(error: errorInformation)
                    return
                }
                self.handleRouteCallback(route: route)
            }
        }

@lukasz-szyszkowski has said:
I confirm, it’s calculated on TrackableReadyToTrackEvent which is fired by TrackTrackableEvent and initially it’s called by this method:
func track(trackable: Trackable, completion: @escaping ResultHandler<Void>) {
    let event = TrackTrackableEvent(trackable: trackable,
                                    resultHandler: completion)
    enqueue(event: event)
}

┆Issue is synchronized with this Jira Task by Unito

I talked to @KacperKluka about AAT Android, and we agree the route recalculating mechanism should be resolved on the map provider SDK, in our case this is the Mapbox. In view of this, I'm closing this issue.
cc: @jamienewcomb @AndyNicks


Tell user better that his attempt to make a building edges squarer failed

Some times if the angles are too skewed, the "square" function in the context menu does nothing.
One has to keep a sharp eye to see if it really does something or does nothing.
Therefore I propose that some kind of signal be given to the user if it fails.
E.g., a unhappy face that floats up and disappears.

iD already gives visual feedback when the modified object is not even close to being rectangular.

However it is really a bit unobtrusive. Maybe this could be improved, but I don't really have any good ideas about it.

As @hikemaniac , iD already does this, if the object is really not at all "squarish".
If the object is "almost square" it can be difficult to tell whether the Square operation does anything, but I don't see that a serious enough issue that we need to spend development time on.  I think users can figure out whether something needs more squareness or not just by looking at it.

Ahh... I see what the case I am talking about is!
It is the case where we expect all four corners to be made into right angles.
And when we click, e.g., only A and B are made into right angles. But not C and D, because they are too far from being right angles.
Now if our eyes are only looking at A and B we will think the operation succeeded.
If we are only looking at C and D we will think the operation failed.
If we click again we will see nothing happening, so think something is wrong.
Anyway, never in out wildest dreams did we think "square the corners of this area" would only work on some of the corners!

Also if repeated operations do nothing, maybe do like the image you posted, saying that all the squaring possible has already been done.
As often we are operating on small objects and can't really be sure the operation has succeeded or not.


Update RenderBatch to use Mesh

Initial work updating the batching system so it uses the Mesh internally.
It still uses custom OpenGL to manage it and I put the Mesh in VertexBuffer as that was the easiest way to get it working. This can maybe be changed in the future.
I have tested this with OPENGL_33 on Linux by using it with the examples and everything seems to work the same. I could use help testing other configurations such as OPENGL_ES2 to make sure I have not caused any new OpenGL issues.

@ChrisDill Sorry, I'm not merging this change at this moment. Replacing current VertexBuffer with minimal required data by a Mesh structure with multiple useless data references for the batching mechanism, I think it complicates the code unnecessarily at this moment.


latest version not passing Arduino IDE compile phase

Hello. after the last pdates in the files, i cannot compile the project in Arduino IDE. Can You please check why?

What is the error? But i have an idea: I made some changes on the environment file as well, as i didn't liked the naming so much so i changed this as well. LewisSmallwood took over that changes. So i think this is the cause of your issue. Make sure you copy / paste the current example-environment file and adjust the settings for your wifi and also (new) hostname. Should work then.

Hi @LucianTothezan, sorry about this.
I have updated the example environment.h file to show the correct syntax for the network_settings.


🐛 Bug: jstz install: installer does not respect $ZDOTDIR

Description

jstz installer writes to ~/.zshrc, regardless of the actual value of $ZDOTDIR.

Observed behaviour
The installer assumes the .zshrc is always placed at $HOME/.zshrc, which is incorrect. While it is the default, if $ZDOTDIR is set, the configuration is placed at $ZDOTDIR/.zshrc.
Expected behaviour
The installer attempts to write the alias to $ZDOTDIR/.zshrc.
Steps to reproduce
From within zsh:
export ZDOTDIR=~/.config/zsh && mkdir -p ~/.config/zsh
source <(curl --proto '=https' --tlsv1.2 -sSf https://raw.githubusercontent.com/trilitech/jstz/main/scripts/install-jstz-cli.sh)

fixed by #475


Replace links to other vim plugins on github to links on vimawesome

@tbodt You're proposing we modify the links in README files so that links that would have pointed to the GitHub repository for another Vim plugin, would instead point to that plugin's vimawesome page?

Exactly.

This would be a really cool feature for users of the site and definitely provide a better overall experience (no leaving the site when browsing), but I would hesitate to introduce a change like this for two reasons:

It introduces additional technical complexity.

All links now need to be processed to check whether or not they point to plugins.
There are bound to be edge cases that the implementation breaks (e.g. a readme deep-linking to another project may be incorrectly identified as a plugin link).

Plugin developers may not expect this to happen and dislike their content being modified.

To address point 2, perhaps this could be opt-in for plugin developers? Would this be any different from developers linking directly to Vim Awesome in their readmes?

Yeah, it's a cool idea, thanks @tbodt for bringing it up!
However, I think it feels odd to modify the plugin author's content (@jonfato's point number 2). The way we present the README description, it feels obvious that it's being pulled directly from GitHub. I think it would be confusing for us to be modifying the content without any clear indication of what we're doing.
While it would be pretty slick, for now I think I'm 👎 for this idea.

Thanks for making the call @captbaritone , thanks for suggesting @tbodt


Add support for bucketed directories

This feature add support for environment variable CONFIG_BUCKETSIZE that tell the amount of characters used from the beginning of the file to create directories. By default it does not create directories.
Related to: https://github.com/src-d/borges/issues/180

It depends on: https://github.com/src-d/core-retrieval/pull/40

We may want to rebase this branch with the fixes from #40 to pass tests.


Fix typo in Phabricator URL in readme

The expanded URL was https://github.com/google/arc-proselint/blob/develop/phabricator.org instead of http://phabricator.org/.

I signed the CLA.

Hah, thanks!


feat: storage client implementation

This PR implements the storage client.
Major Features

The client and the server communicate via HTTP.
Whenever the client makes a GET request for a file, the server retrieves this file and transfers it back to the client, presumably all in parquet format.
All the data read and data transmission are done in a streaming manner to avoid memory issues.
The client decodes the parquet file and returns the data in form of arrow record batch, as the execution engine people requested.

TODOs

[ ] The server is not retrieving data from the storage manager now, as the API is not implemented yet. It just directly returns a local file. This needs to be addressed later.
[ ] The client is not reading anything from catalog either, as I have no idea what their API is. Need to discuss with them.
[ ] I have not found a way to decode parquet stream in the client. The current solution is to dump all data as a file into disk first, and then use some sort of stream builder to decode it. But I assume this will cause I/O overhead.

Codecov Report
Attention: Patch coverage is 75.51020% with 36 lines in your changes are missing coverage. Please review.

Project coverage is 77.31%. Comparing base (c5ccf8c) to head (e701b60).

Files
Patch %
Lines

storage-node/src/server.rs
73.91%
6 Missing and 12 partials :warning:

storage-client/src/client.rs
77.92%
7 Missing and 10 partials :warning:

storage-common/src/lib.rs
0.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #11      +/-   ##
==========================================
+ Coverage   75.73%   77.31%   +1.58%
==========================================
  Files          13       14       +1
  Lines        1261     1402     +141
  Branches     1261     1402     +141
==========================================
+ Hits          955     1084     +129
+ Misses        249      235      -14
- Partials       57       83      +26

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

I think I have addressed all comments above and finished the undone work (i.e. integration test). PTAL @xx01cyx @lanlou1554


shardingsphere  4.0.0 retrive very slow that sql script

Bug Report
For English only, other languages will not accept.
Before report a bug, make sure you have:

Searched open and closed GitHub issues.
Read documentation: ShardingSphere Doc.

Please pay attention on issues you submitted, because we maybe need more details.
If no response more than 7 days and we cannot reproduce it on current information, we will close it.
Please answer these questions before submitting your issue. Thanks!
Which version of ShardingSphere did you use?
	<dependency>
		<groupId>org.apache.shardingsphere</groupId>
		<artifactId>sharding-jdbc-core</artifactId>
		<version>4.0.0-RC1</version>
	</dependency>
	<dependency>
		<groupId>org.apache.shardingsphere</groupId>
		<artifactId>sharding-jdbc-spring-namespace</artifactId>
		<version>4.0.0-RC1</version>
	</dependency>

Which project did you use? Sharding-JDBC or Sharding-Proxy?
Sharding-JDBC
Expected behavior
want to complete in 3s
Actual behavior
14s
Reason analyze (If you can)
When i debug into code:
class=SQLExecuteCallback
method:execute0
line:T result = this.executeSQL(routeUnit.getSqlUnit().getSql(), statementExecuteUnit.getStatement(), statementExecuteUnit.getConnectionMode());
I found spent long
Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
init data->total size:1,0000,000
1.execute sql script:sql:SELECT SUM(size) as size_sum FROM table_test
spent: 26s
2.add properties:max.tolerate.time.difference.milliseconds:8 ->restart application
3.execute sql script:sql:SELECT SUM(size) as size_sum FROM table_test
spent:14s
Example codes for reproduce this issue (such as a github link).

also try the below version:

org.apache.shardingsphere
sharding-jdbc-spring-namespace
4.0.0

org.apache.shardingsphere
sharding-jdbc-spring-namespace
4.0.0

The result is same as the above.

May duplicate with #4231

@terrymanu there is something different from  #4231,insert is normal only retrive with sharding very slow,under my test,insert 100million/hour and retrive is normal without using sharding,So could you pls help?

@terrymanu
when i add:enablePrepareOnFirstPreparedStatementCall=true,it only has a little affect,but still slow

@ancientelves  only one sql with a sum opr?

@kimmking
yes,one sql.
for sharding:SELECT SUM(size) as size_sum FROM table_test_0 ......table_test_16
for single table:SELECT SUM(size) as size_sum FROM table_test
sharding performance is bad than single table
total size:1,0000,000

I got it and will try sooner.

@kimmking
waitting your response,my program will go live soon,so pls.
Thanks in advance.

I already run a demo for no sharding-jdbc to test 1M data for sum in a table or 16 tables with union, it takes both 170ms.
I will run sharding-jdbc case this afternoon. @ancientelves

@ancientelves
After discuss with @terrymanu , I find the key point about this issue.
The parameter max.connections.size.per.query in server.yaml is 1 by default. This means 16 sub query to each table one by one via a same connection.
In my case, the cost is 250ms by proxy sharding, and came down to 90ms by set the parameter to 8, better than only one table.
But a tip here : don't modify this parameter to a higher value in your production env, cause it maybe    exhausted your jdbc connections in datasource pool.

@kimmking
Thanks for your suggestion.Then I will check my program and table again.
BTW,don't modify this parameter to a higher value in your production env,if I set the param to 8 as your above,is it ok? or I should do a lower setup?

You can try 2.

@ancientelves  Does it take effect now?

@kimmking
Now it's normal.
Thanks for your help.

solved


Disallow type predicate as type assertion

Fixes #5731 by disallowing the construction for now.

@weswigham @ahejlsberg could you take a look since you commented on the original issue.

OK, the change is much smaller now.


Add Organization Resource

Description of changes:
These changes add the Organization resource into the project by removing it from the ignore section of the generator yaml and providing any necessary overrides.
This PR relies upon the #7 PR.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/ok-to-test

/test all

/retest all

/test organizations-kind-e2e

/test all


Would it make sense to pull out the serialization functionality into a similar protocol like the parsing?

Currently the JSONParsing.swift has some methods for serialization.
I would advocate making the serialization behavior run parallel to the parsing, in that there is a protocol for serialization, such that we could eventually write a custom serializer.

Closing due to inactivity and the general state of the repo.


Update lxml

Command to reproduce: poetry update

Codecov Report

Merging #534 (877d704) into master (2f91567) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #534   +/-   ##
=======================================
  Coverage   79.31%   79.31%
=======================================
  Files         176      176
  Lines       29250    29250
=======================================
+ Hits        23200    23201    +1
+ Misses       6050     6049    -1

Impacted Files
Coverage Δ

resqpy/model/_xml.py
91.41% <0.00%> (+0.27%)
:arrow_up:

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 2f91567...877d704. Read the comment docs.