feat(updatecli): retrieve Maven version from VM template

Fixes https://github.com/jenkins-infra/docker-inbound-agents/issues/18
Ref:

https://github.com/jenkins-infra/jenkins-infra/pull/2216
https://github.com/jenkins-infra/helpdesk/issues/2986#issuecomment-1154194054

I don't know why updatecli can't find the common.yaml file in the cloned jenkins-infra/jenkins-infra repository:
$ updatecli diff --config ./updatecli/updatecli.d --values ./updatecli/values.yaml --debug

+++++++++++
+ PREPARE +
+++++++++++

Loading Pipeline "updatecli/updatecli.d/maven.yml"

SCM repository retrieved: 2
DEBUG: stage: git-clone

DEBUG: stage: git-clone

DEBUG: cloning git repository: https://github.com/jenkins-infra/docker-inbound-agents.git in /var/folders/z6/xykmq_m902n_7v4j8sxhzkdm0000gn/T/updatecli/jenkins-infra/docker-inbound-agents
Enumerating objects: 880, done.
Counting objects: 100% (270/270), done.
Compressing objects: 100% (115/115), done.
Total 880 (delta 181), reused 202 (delta 145), pack-reused 610
fetching remote branchesEnumerating objects: 137, done.
Counting objects: 100% (115/115), done.
Compressing objects: 100% (70/70), done.
Total 137 (delta 67), reused 85 (delta 45), pack-reused 22
DEBUG: cloning git repository: https://github.com/jenkins-infra/jenkins-infra.git in /var/folders/z6/xykmq_m902n_7v4j8sxhzkdm0000gn/T/updatecli/jenkins-infra/jenkins-infra
Enumerating objects: 21120, done.
Counting objects: 100% (750/750), done.
Compressing objects: 100% (104/104), done.
Total 21120 (delta 695), reused 667 (delta 646), pack-reused 20370
fetching remote branchesEnumerating objects: 5729, done.
Counting objects: 100% (5729/5729), done.
Compressing objects: 100% (3190/3190), done.
Total 5729 (delta 4400), reused 3601 (delta 2434), pack-reused 0

++++++++++++
+ PIPELINE +
++++++++++++

######################
# BUMP MAVEN VERSION #
######################

SOURCES
=======

getMavenVersionFromVMTemplate
-----------------------------
DEBUG: stage: git-checkout

DEBUG: checkout branch "updatecli_", based on "production" to directory "/var/folders/z6/xykmq_m902n_7v4j8sxhzkdm0000gn/T/updatecli/jenkins-infra/jenkins-infra"
DEBUG: branch 'updatecli_' doesn't exist, creating it from branch 'production'
DEBUG: branch "updatecli_" successfully created
ERROR: ✗ the yaml file "hieradata/common.yaml" does not exist
Pipeline "Bump Maven version" failed
Skipping due to:
        sources stage:  "the yaml file \"hieradata/common.yaml\" does not exist"

Any idea @dduportal ?

I don't know why updatecli can't find the common.yaml file in the cloned jenkins-infra/jenkins-infra repository:
$ updatecli diff --config ./updatecli/updatecli.d --values ./updatecli/values.yaml --debug

+++++++++++
+ PREPARE +
+++++++++++

Loading Pipeline "updatecli/updatecli.d/maven.yml"

SCM repository retrieved: 2
DEBUG: stage: git-clone

DEBUG: stage: git-clone

DEBUG: cloning git repository: https://github.com/jenkins-infra/docker-inbound-agents.git in /var/folders/z6/xykmq_m902n_7v4j8sxhzkdm0000gn/T/updatecli/jenkins-infra/docker-inbound-agents
Enumerating objects: 880, done.
Counting objects: 100% (270/270), done.
Compressing objects: 100% (115/115), done.
Total 880 (delta 181), reused 202 (delta 145), pack-reused 610
fetching remote branchesEnumerating objects: 137, done.
Counting objects: 100% (115/115), done.
Compressing objects: 100% (70/70), done.
Total 137 (delta 67), reused 85 (delta 45), pack-reused 22
DEBUG: cloning git repository: https://github.com/jenkins-infra/jenkins-infra.git in /var/folders/z6/xykmq_m902n_7v4j8sxhzkdm0000gn/T/updatecli/jenkins-infra/jenkins-infra
Enumerating objects: 21120, done.
Counting objects: 100% (750/750), done.
Compressing objects: 100% (104/104), done.
Total 21120 (delta 695), reused 667 (delta 646), pack-reused 20370
fetching remote branchesEnumerating objects: 5729, done.
Counting objects: 100% (5729/5729), done.
Compressing objects: 100% (3190/3190), done.
Total 5729 (delta 4400), reused 3601 (delta 2434), pack-reused 0

++++++++++++
+ PIPELINE +
++++++++++++

######################
# BUMP MAVEN VERSION #
######################

SOURCES
=======

getMavenVersionFromVMTemplate
-----------------------------
DEBUG: stage: git-checkout

DEBUG: checkout branch "updatecli_", based on "production" to directory "/var/folders/z6/xykmq_m902n_7v4j8sxhzkdm0000gn/T/updatecli/jenkins-infra/jenkins-infra"
DEBUG: branch 'updatecli_' doesn't exist, creating it from branch 'production'
DEBUG: branch "updatecli_" successfully created
ERROR: ✗ the yaml file "hieradata/common.yaml" does not exist
Pipeline "Bump Maven version" failed
Skipping due to:
        sources stage:  "the yaml file \"hieradata/common.yaml\" does not exist"

Any idea @dduportal ?

Smells like a bug in updatecli in the way SCM are handled in the github source: the debug log show a branch updatecli_ without suffix.
WDYT about using the text file from GitHub (like https://github.com/jenkins-infra/shared-tools/blob/main/updatecli/updatecli.d/hashicorp-tools.yml#L28) ?
Would avoid the "heavy" git clone

Would avoid the "heavy" git clone

Using github as source, not as heavy as git, I didn't needed the extra memory anymore 😃

Use packer images as source instead of jenkins-infra

Inversed, ready to merge

Superseded by https://github.com/jenkins-infra/docker-inbound-agents/pull/67


[WIP] DAG Model interface

This is a draft PR introducing a Model type that stores and makes use the model graph.
The main type introduced here is the Model struct which stores the ModelState and DAG, each of which are their own types. ModelState contains information about the node values, dependencies and eval functions and DAG contains the graph and topologically ordered vertex list.
A model can be constructed in the following way:
julia> nt = (
               s2 = (0.0, (), () -> InverseGamma(2.0,3.0), :Stochastic),
               μ = (1.0, (), () -> 1.0, :Logical),
               y = (0.0, (:μ, :s2), (μ, s2) -> MvNormal(μ, sqrt(s2)), :Stochastic)
           )
(s2 = (0.0, (), var"#33#36"(), :Stochastic), μ = (1.0, (), var"#34#37"(), :Logical), y = (0.0, (:μ, :s2), var"#35#38"(), :Stochastic))

julia> Model(nt)
Nodes:
μ = (value = 1.0, input = (), eval = var"#16#19"(), kind = :Logical)
s2 = (value = 0.0, input = (), eval = var"#15#18"(), kind = :Stochastic)
y = (value = 0.0, input = (:μ, :s2), eval = var"#17#20"(), kind = :Stochastic)
DAG:
3×3 SparseMatrixCSC{Float64, Int64} with 2 stored entries:
  ⋅    ⋅    ⋅
  ⋅    ⋅    ⋅
 1.0  1.0   ⋅

At present, only functions needed for the constructors are implemented, as well as indexing using @varname. I still need to complete the integration with the AbstractPPL api. TODO:

[ ] condition/decondition,
[ ] sample
[ ] logdensityof
[x] pure functions for ordered dictionary, as outlined in AbstractPPL

Feedback on Model structure welcome whilst I implement the remaining features!

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

56 of 65 (86.15%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+4.05%) to 81.111%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/simpleppl.jl
56
65
86.15%

Totals

Change from base Build<PHONE_NUMBER>:
4.05%

Covered Lines:
146

Relevant Lines:
180

💛  - Coveralls

No substantive comments other than that this is cool! May do a review later when I get more time.

I think all the necessary functions needed for dictionary-like iterations are now supported.
There was a problem with the adjacency matrix function in that it didn't support nodes that had only one input. I've added a fix for this but it's not totally type stable so still working on it.

Just FYI: Julia now provides a standard way of obtaining argument names of methods:
julia> f = (x, y) -> println(x, y)
#3 (generic function with 1 method)

julia> args = Base.method_argnames(first(methods(f)))
3-element Vector{Symbol}:
 Symbol("#self#")
 :x
 :y

julia> args[2:end]
2-element Vector{Symbol}:
 :x
 :y

Maybe we can make use of this, and provide an alternative Model constructor with less verbose arguments:
julia> nt = (
               s2 = (0.0, () -> InverseGamma(2.0,3.0), :Stochastic),
               μ = (1.0, () -> 1.0, :Logical),
               y = (0.0, (μ, s2) -> MvNormal(μ, sqrt(s2)), :Stochastic) # (:μ, :s2) can be extracted using code above.
           )

We can keep the verbose version as the internal API, and export the simpler version to users.

Thanks for pointing that out @yebai, that would be much nicer. Is that just in Julia 1.7?

Thanks for pointing that out @yebai, that would be much nicer. Is that just in Julia 1.7?

It works for Julia 1.6 too. But I haven't checked lower Julia versions.

@yebai I've merged ModelState and DAG together into one GraphInfo type. I've also just replaced the Model type with GraphInfo. Now when you call the Model constructor it returns a GraphInfo type. Is that ok or do you think it is better to have a dedicated Model type with field g::GraphInfo?

@PavanChaggar thanks, let's still keep a dedicated Model type. We might add more fields to Model later. In addition, it is more consistent with the Model type in DynamicPPL, which we could bring closer in the future. In my mind, model = CodeInfo + GraphInfo/VarInfo, where CodeInfo is not yet introduced but could represent the model AST/IR.

Let's also rename simpleppl.jl to graphinfo.jl.

I'd still like it to go into a separate submodule, so that it's clear that this is the part for one, concrete implementation.

bors r+


Selection Of Multiple  Column By Pressing CTRL

Multi Column Selection
The Multiple row need to be selected on Press by CTRL & Mouse Click . And Range Must Be Multi Range , So The Multiple range can be selected and can be selected for highlight or Making Other Functionality for example Colors For The Specific Row/ Columns , Making Font Size Specific Row/ Column.
Which edition of ReoGrid is targeted

C# , WPF

It is greate if have function.


WIP: Porting to support Terraform v0.12

Because of breaking issue between v0.11 and v0.12 this change would require some level of version forking.  The port needs more testing and the docs will need to be updated to reference the correct version number for the future module.
This v0.12 version can be tested by creating a local module much like the example in the project and changing the path to reference the folder.

Thanks @haysclark for this PR! I’ll have a look at this and read up on the Terraform 0.12 differences this afternoon.

Removing WIP, everything is working well for me locally.

Removing WIP, everything is working well for me locally.
/assign wwwil

@haysclark Sorry for my delay responding to this, all looks pretty good to me! If you can resolve the review items about subnet comments and the version in the README I think it should be good to merge.
/ok-to-test

I'm going to need to update the version of Terraform used in our Prow testing too!

Thanks @haysclark for your contribution! Sorry this took so long to get merged, was finished off and merged in this PR so I'm going to close this.


Move UWPCapabilityUtility to editor assembly

Overview
Part of https://github.com/microsoft/MixedRealityToolkit-Unity/issues/3952
This script is only usable in the editor, so it's being moved into an editor-only assembly.
Also allows us to remove the #if UNITY_EDITOR wrapping the entire file.

/azp run

/azp run


Fixes off-by-one error and changes drop_last for Cracks

The off-by-one error in make_dataset in the VideoLoader was causing us to drop the last sample of our datasets.

Increases samples available for the training set from 90 -> 91
Increases samples available for the testing set from 10 -> 11

Changing drop_last=True to False allows for the full dataset to be utilized for training.

Increases training set from 80 -> 91
Increases test set from 8 -> 11

Since our cracks dataset is small, I think it would be best to use the full training set for each epoch.

These changes look good. The make_dataset change is valid. Regarding the drop_last=True however, I believe the data is still being used by the models. Since our sequences are shuffled in the batches, drop_last batch removal shouldn't be significant over 200 epochs. I think the only "noticeable" item it changes is the number of output sequences on inference.
Some things to observe when changing the drop_last to False: how are the models implementing any form of batch normalization? By inputting a smaller batch size, are we inputting data that is significantly more adjusted than the other batches? How is this going to impact the gradient updates at the end of the batch?
It's definitely worth testing to see how the results change, in the future it might be worthwhile to consider adding this as an argument to the parser so that it can be changed by command line.

Regarding the drop_last=True however, I believe the data is still being used by the models. Since our sequences are shuffled in the batches, drop_last batch removal shouldn't be significant over 200 epochs. I think the only "noticeable" item it changes is the number of output sequences on inference.

Yes good point! You're right the data still gets used by the models, after multiple epochs, but the full dataset isn't used in any single epoch. It's a good point though, so I tested setting drop_last=False and True for the training data loader for SimVP and ConvLSTM.
In both models, the MSE decreased when setting drop_last=False by 8 and 7 (ie, a tiny improvement). I think this is probably because it ends up doing one additional gradient update every epoch rather than because we include the last partial batch. I think it'll make more intuitive sense to increase the number of epochs rather than rely on the (possibly unpredictable) effect of setting drop_last=False, so I'll revert that change for the training dataloader.

Some things to observe when changing the drop_last to False: how are the models implementing any form of batch normalization? By inputting a smaller batch size, are we inputting data that is significantly more adjusted than the other batches? How is this going to impact the gradient updates at the end of the batch?

I don't think the smaller batch size would impact our results much because our dataset is pretty similar throughout, and if we follow the convention of using batch sizes that are powers of two for our 91 samples, we never end up with the last batch being significantly smaller than the other batches--- but this is feeling hand wavy, so aiming for consistency and dropping the last partial batch seems like to would be better 👍

It's definitely worth testing to see how the results change, in the future it might be worthwhile to consider adding this as an argument to the parser so that it can be changed by command line.
👍

tldr; I'll change the drop_last back to True for the training dataloader. Thanks for the thoughtful feedback! 😄


Multiple image overlay support??

Hi,
I was wondering if it is possible to have multiple panoramic overlayed on top of each other in the same scene??

This isn't directly supported, but it should be possible to implement using the API by first compositing the images on a separate <canvas>. If the overlay doesn't need to change after loading the panorama, you can use the <canvas>'s toBlob method to create a Blob object and call URL.createObjectURL on it to get an object URL to pass to Pannellum. If it needs to change, set the dynamic: true configuration option and pass the <canvas> object directly (see Video.js plugin for example); you'll probably want to use the setUpdate method to make selectively turn on and off updating to make things more efficient.

I managed to get the drawing using a dynamic canvas working, thank you.
I was wondering if I could set up scenes to use the dynamic canvas so that I could do the drawing in a different canvas attached to another scene then fade that scene in?

You should be able to configure two different scenes to use two different <canvas> elements and switch between them like you would for normal images (I haven't tested this). After switching, you'll need to manually turn updating back on using setUpdate unless you set dynamicUpdate: true in the configuration (this was added in a05721198901cf2554e560f5029184ee897b4fc1, after the last release).

I did try that, but when I call loadScene to switch the scenes, it does not appear to work (the loading bar appears and just stays there with no progress)

You previously needed to manually call setUpdate to fix that (the dynamic scene support was developed in the context of the Video.js plugin, which does that on its own).
The need for the manual call to setUpdate was an oversight, which I addressed in 1b92bf32b4b35ea0327cae022f658759c1f843fd.


Unclear which part of long lines is being pointed to

With long lines that are wrapped, it's unclear which part of the line is being pointed to.
Here's a screenshot, as an example:

And as text:
Error: gen_completions::deser::kdl::duplicate_flag (link)

  × Error encountered while deserializing
  ╰─▶ Error encountered while reading command information
   ╭─[test.kdl:2:1]
 2 │     flags {
 3 │         "-h" "--very long string in between to make it span multiple lines aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" "-h" {
   ·         ──┬─                                                                                ──┬─
   ·           │                                                                                ╰── duplicate flag
   ·           ╰── already given here
 4 │             desc "foo bar baz"
   ╰────

As you can see, when my terminal wraps that long line, it can be hard to tell where exactly the span is pointing. Is there a way to underline or highlight the text covered by those spans? I checked out GraphicalTheme, but that doesn't seem to have a way to configure this. I guess I could write my own ReportHandler based off of miette's, but that would take effort.
If such a feature doesn't exist in miette but the maintainers are fine with adding it, I could try implementing it. Apologies if someone's asked about this already, but I couldn't find any issues.

#20 is possibly related. My understanding of the idea with #20 is that we could trim snippets horizontally similar to the way we're currently trimming them vertically (by only rendering a few context lines around the span).
In your example, I'm imagining that might look something like this:
Error: gen_completions::deser::kdl::duplicate_flag (link)

  × Error encountered while deserializing
  ╰─▶ Error encountered while reading command information
   ╭─[test.kdl:2:1]
 2 │     flags {
 3 │         "-h" "--very long string ··· aaaaaa" "-h" {
   ·         ──┬─                                 ──┬─
   ·           │                                    ╰── duplicate flag
   ·           ╰── already given here
 4 │             desc "foo bar baz"
   ╰────

I think having an option in GraphicalTheme to highlight spans by swapping the fg/bg colors or with ansi underlines would be useful, even if the issues with long lines are solved another way. There was a great blog post I saw a while ago that recommended fg/bg swap as the default way to format compiler errors because it has a better shot at handling things like bidi text or misprediction of character display widths. I don't fully agree that it should be the default, but think it would be a good to support as an option. Unfortunately, I couldn't find the original post :(


dataset

Thank you for sharing the project. Can you provide a link to download the training dataset? Thank you very much

Unfortunately I could not find datasets with people smoking so I used images from the sample video (labeled around 30%)


Selected service ID is not the valid one when reaching orders.create()

Hi!
A part of the implementation that was previously working and is no longer working is the selection of services, specifically baggage.
meta: { status: 422, request_id: 'F1FXLmKy-Q5QFmIAb2yB' },
errors: [
     {
       	type: 'validation_error',
       	title: 'Linked record(s) not found',
      	source: [Object],
     	message: "Field 'id' contains ID(s) of linked record(s) that were not found in your account",
    	documentation_url: 'https://duffel.com/docs/api/overview/errors',
   		code: 'not_found'
	}
]

Since we call the GetOffer endpoint multiple times to check that the flight is still available, it is understandable and to be expected that the ID of the services will change. The problem is that in this case, when doing the retrieval of selected services, we are using the last Offer received with its corresponding services.
In this case, the services to be added to the booking are:
 [{"id":"ase_0000AU9mw1Siuc9ifftYY7","quantity":3}]

Below, in order of extraction, are all the services that we received in the Offers. The last one would be the GetOffer before CreateOrder(), and, consequently, the Offer.services that we use to obtain the ID to use in this flight.
[
  [
    {
      "type": "baggage",
      "total_currency": "EUR",
      "total_amount": "72.67",
      "segment_ids": [
        "seg_0000AU9mYFlZSEOU53adhG",
        "seg_0000AU9mYFlZSEOU53adhI"
      ],
      "passenger_ids": ["pas_0000AU9mYDWFoCxB6yPNXn"],
      "metadata": {
        "type": "checked",
        "maximum_weight_kg": 23,
        "maximum_length_cm": null,
        "maximum_height_cm": null,
        "maximum_depth_cm": null
      },
      "maximum_quantity": 3,
      "id": "ase_0000AU9mq2Jgp5UJaDobSa"
    },
    {
      "type": "baggage",
      "total_currency": "EUR",
      "total_amount": "61.31",
      "segment_ids": [
        "seg_0000AU9mYFlZSEOU53adhG",
        "seg_0000AU9mYFlZSEOU53adhI"
      ],
      "passenger_ids": ["pas_0000AU9mYDWFoCxB6yPNXn"],
      "metadata": {
        "type": "checked",
        "maximum_weight_kg": 15,
        "maximum_length_cm": null,
        "maximum_height_cm": null,
        "maximum_depth_cm": null
      },
      "maximum_quantity": 3,
      "id": "ase_0000AU9mq2Jgp5UJaDobSb"
    },
    {
      "type": "baggage",
      "total_currency": "EUR",
      "total_amount": "36.32",
      "segment_ids": [
        "seg_0000AU9mYFlZSEOU53adhG",
        "seg_0000AU9mYFlZSEOU53adhI"
      ],
      "passenger_ids": ["pas_0000AU9mYDWFoCxB6yPNXn"],
      "metadata": {
        "type": "carry_on",
        "maximum_weight_kg": null,
        "maximum_length_cm": null,
        "maximum_height_cm": null,
        "maximum_depth_cm": null
      },
      "maximum_quantity": 1,
      "id": "ase_0000AU9mq2Jgp5UJaDobSc"
    }
  ],
  [
    {
      "type": "baggage",
      "total_currency": "EUR",
      "total_amount": "72.67",
      "segment_ids": [
        "seg_0000AU9mqEdbIBUnebCdsi",
        "seg_0000AU9mqEdbIBUnebCdsl"
      ],
      "passenger_ids": ["pas_0000AU9mqCNDi7CkdDWX4N"],
      "metadata": {
        "type": "checked",
        "maximum_weight_kg": 23,
        "maximum_length_cm": null,
        "maximum_height_cm": null,
        "maximum_depth_cm": null
      },
      "maximum_quantity": 3,
      "id": "ase_0000AU9mqOtGGo07agqAN6"
    },
    {
      "type": "baggage",
      "total_currency": "EUR",
      "total_amount": "61.31",
      "segment_ids": [
        "seg_0000AU9mqEdbIBUnebCdsi",
        "seg_0000AU9mqEdbIBUnebCdsl"
      ],
      "passenger_ids": ["pas_0000AU9mqCNDi7CkdDWX4N"],
      "metadata": {
        "type": "checked",
        "maximum_weight_kg": 15,
        "maximum_length_cm": null,
        "maximum_height_cm": null,
        "maximum_depth_cm": null
      },
      "maximum_quantity": 3,
      "id": "ase_0000AU9mqOtGGo07agqAN7"
    },
    {
      "type": "baggage",
      "total_currency": "EUR",
      "total_amount": "36.32",
      "segment_ids": [
        "seg_0000AU9mqEdbIBUnebCdsi",
        "seg_0000AU9mqEdbIBUnebCdsl"
      ],
      "passenger_ids": ["pas_0000AU9mqCNDi7CkdDWX4N"],
      "metadata": {
        "type": "carry_on",
        "maximum_weight_kg": null,
        "maximum_length_cm": null,
        "maximum_height_cm": null,
        "maximum_depth_cm": null
      },
      "maximum_quantity": 1,
      "id": "ase_0000AU9mqOtGGo07agqAN8"
    }
  ],
  [
    {
      "type": "baggage",
      "total_currency": "EUR",
      "total_amount": "72.67",
      "segment_ids": [
        "seg_0000AU9mqEdbIBUnebCdsi",
        "seg_0000AU9mqEdbIBUnebCdsl"
      ],
      "passenger_ids": ["pas_0000AU9mqCNDi7CkdDWX4N"],
      "metadata": {
        "type": "checked",
        "maximum_weight_kg": 23,
        "maximum_length_cm": null,
        "maximum_height_cm": null,
        "maximum_depth_cm": null
      },
      "maximum_quantity": 3,
      "id": "ase_0000AU9mviFwbCawxgkYDM"
    },
    {
      "type": "baggage",
      "total_currency": "EUR",
      "total_amount": "61.31",
      "segment_ids": [
        "seg_0000AU9mqEdbIBUnebCdsi",
        "seg_0000AU9mqEdbIBUnebCdsl"
      ],
      "passenger_ids": ["pas_0000AU9mqCNDi7CkdDWX4N"],
      "metadata": {
        "type": "checked",
        "maximum_weight_kg": 15,
        "maximum_length_cm": null,
        "maximum_height_cm": null,
        "maximum_depth_cm": null
      },
      "maximum_quantity": 3,
      "id": "ase_0000AU9mviFwbCawxgkYDO"
    },
    {
      "type": "baggage",
      "total_currency": "EUR",
      "total_amount": "36.32",
      "segment_ids": [
        "seg_0000AU9mqEdbIBUnebCdsi",
        "seg_0000AU9mqEdbIBUnebCdsl"
      ],
      "passenger_ids": ["pas_0000AU9mqCNDi7CkdDWX4N"],
      "metadata": {
        "type": "carry_on",
        "maximum_weight_kg": null,
        "maximum_length_cm": null,
        "maximum_height_cm": null,
        "maximum_depth_cm": null
      },
      "maximum_quantity": 1,
      "id": "ase_0000AU9mviFwbCawxgkYDQ"
    }
  ],
  [
    {
      "type": "baggage",
      "total_currency": "EUR",
      "total_amount": "72.67",
      "segment_ids": [
        "seg_0000AU9mqEdbIBUnebCdsi",
        "seg_0000AU9mqEdbIBUnebCdsl"
      ],
      "passenger_ids": ["pas_0000AU9mqCNDi7CkdDWX4N"],
      "metadata": {
        "type": "checked",
        "maximum_weight_kg": 23,
        "maximum_length_cm": null,
        "maximum_height_cm": null,
        "maximum_depth_cm": null
      },
      "maximum_quantity": 3,
      "id": "ase_0000AU9mw1Siuc9ifftYY7"
    },
    {
      "type": "baggage",
      "total_currency": "EUR",
      "total_amount": "61.31",
      "segment_ids": [
        "seg_0000AU9mqEdbIBUnebCdsi",
        "seg_0000AU9mqEdbIBUnebCdsl"
      ],
      "passenger_ids": ["pas_0000AU9mqCNDi7CkdDWX4N"],
      "metadata": {
        "type": "checked",
        "maximum_weight_kg": 15,
        "maximum_length_cm": null,
        "maximum_height_cm": null,
        "maximum_depth_cm": null
      },
      "maximum_quantity": 3,
      "id": "ase_0000AU9mw1Siuc9ifftYY9"
    },
    {
      "type": "baggage",
      "total_currency": "EUR",
      "total_amount": "36.32",
      "segment_ids": [
        "seg_0000AU9mqEdbIBUnebCdsi",
        "seg_0000AU9mqEdbIBUnebCdsl"
      ],
      "passenger_ids": ["pas_0000AU9mqCNDi7CkdDWX4N"],
      "metadata": {
        "type": "carry_on",
        "maximum_weight_kg": null,
        "maximum_length_cm": null,
        "maximum_height_cm": null,
        "maximum_depth_cm": null
      },
      "maximum_quantity": 1,
      "id": "ase_0000AU9mw1Siuc9ifftYYB"
    }
  ]
]

In the list I concentrated for better readability all the times we received services, and as you can see the user's selection matches the last Array of available services.
It should be noted that as booking token for the Order we are using the ID of the last Offer extracted.
Thanks!

Hey @godoyLeonardo! Sorry for the delayed response here. That's a tough one, thanks for sharing that context! We'd need to dig pretty deep to see what ID caused the mismatch. They will change for every offer and they are specific the combination of passenger and segment. Could I recumbent you to try out using our ancillaries component to generate your order creation payload?

Hey @godoyLeonardo! Sorry for the delayed response here. That's a tough one, thanks for sharing that context! We'd need to dig pretty deep to see what ID caused the mismatch. They will change for every offer and they are specific the combination of passenger and segment. Could I recumbent you to try out using our ancillaries component to generate your order creation payload?

Hey! no worries.
At the moment the bug is apparently gone, it only lasted a couple of days and disappeared after I reported it through Slack.
On the other hand, the component looks quite useful, at least for the seat selection part. Is it expected to be used for other services in the future?
And as far as baggage is concerned, we are already managing it through our own interface, so there are no major problems in that aspect. The only "detail" that I have not been told if you have solved, is the possibility of combining different baggage quantities and services in the same order for the same passenger. This was not possible a few weeks ago as I reported on issue #704.

At the moment the bug is apparently gone, it only lasted a couple of days and disappeared after I reported it through Slack.

I'm glad it's fixed! And yep, feel free to reach out on Slack too, if you ever get blocked on things.

Is it expected to be used for other services in the future?

Absolutely! We've set it up in a way that makes it super easy to add new ancillaries. We'll be adding our protection product to it very soon. And to opt into it, all you need to. do it specify which services you'd like to display (note the services attribute).

is the possibility of combining different baggage quantities and services in the same order for the same passenger.

There are constraints around service quantities. You'll find that each of the offer.available_services includes a maximum_quantity.Also note that services are specific to particular segments and passengers, that's given by the lists segment_ids and passenger_ids.  So as long as these constraints are respected, you should be able to create an order with any combination of services. Does that make sense? For example...
If an offer has the following services:

ase_1 -> 15kg checked
ase_2 -> 23kg checked
ase_3 -> carryon 10kg

The only valid combinations are:

[], [ase_1], [ase_2], [ase_3], [ase1, ase_3], [ase2, ase3]

I'm gonna close this one up for now. But, of course, please let us know here or on slack if there's anything else we can answer or help with :)


Base config isn't giving for any ore money.

*Detailed description of the issue: Not every ore is giving money. In my case Iron and Copper are give money but no diamond ore

CONFIG SECTION (DELETE IF NOT RELEVANT):
Base config

---

**Jobs version:**  <IP_ADDRESS>

**Server Type (Spigot/Paper/etc):** Paper

**Server Version (using `/ver`):** git-Paper-519 (1.19.4)

**Relevant plugins (Delete if this isn't needed):** Essentials and Vault

It all depends on your jobs setup, keep in mind that you might have block protection enabled which prevents from players being able to place and brake same block over and over again. Additionally players in creative will not receive payments by default. Other than this most common blocks should pay out by default, some newer ones might be needed to be added into jobs actions list.

I used the default config and checked all blocks. I could fix the wood job but diamond ores are not working with the default miner job.


[EMB-154] Add gravatar style

Purpose
Fixes gravatar w/o border-radius
Follow-up from #119 🎩@baylee-d
Summary of Changes
Adds required style to gravatar and rename the class to match conventions
Side Effects / Testing Notes
N/A
Ticket
https://openscience.atlassian.net/browse/EMB-154
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md

Coverage remained the same at 22.045% when pulling 8b7728b7061faaaa7df88023ef0430f6be30654a on binoculars:fix/gravatar-style into b76f112931e66f9dc9abda71c2a9c45d897002b1 on CenterForOpenScience:develop.


[QUESTION] - Recommended resources to learn how to create a new vocabulary

Description
There are resources around that web that document how to create a new vocabulary, but I would be interested if there are any in particular you would recommend, thanks.

If you are referring to how to create a new vocabulary in OML, then I am working now on this [issue (https://github.com/opencaesar/oml/issues/3) in this sprint, which will help with that. Please follow it to get updates.
If you are referring to how to create a new vocabulary in OWL, then the OWL Functional Syntax is a good reference.


Add Resource Request: Open Access Button

What is the resource called?:
Open Access Button
What is the link to the resource?:
https://openaccessbutton.org/
Please provide a short description of the resource (1-3 sentences):
Free, legal research articles delivered instantly or automatically requested from authors.
Which step of the research cycle does the resource belong to?:
Project start
If possible, please provide the exact path where you want this resource to go?:
Open (i.e., everything in the resource is free and open to use)

Where exactly under Project start?

Literature!
On Thu, 25 Jul 2024 at 17:41, Alexandros Kastrinogiannis <
@.***> wrote:

Where exactly under Project start?
—
Reply to this email directly, view it on GitHub
https://github.com/IGOR-bioDGPs/ARIADNE/issues/42#issuecomment-2250725448,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHQL44ZZYUZAXUP3AAWCHVTZOEMB3AVCNFSM6AAAAABLN2SDF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJQG4ZDKNBUHA
.
You are receiving this because you were assigned.Message ID:
@.***>

Added


New Blynk server

hi Alex,
my Node-red since yesterday was not connecting to Blynk - Public Cloude -
and as per @dmitry the server is changed to blynk-cloud.com , the new websocket URL is
ws://blynk-cloud.com:8082/websocket
here is Dmitry post

updated on github,
thanks
alex

On 26 May 2016, at 16:38, Mohammed Lotfy<EMAIL_ADDRESS>wrote:
hi Alex,
my Node-red since yesterday was not connecting to Blynk - Public Cloude -
and as per @dmitry https://github.com/dmitry the server is changed to blynk-cloud.com , the new websocket URL is
ws://blynk-cloud.com:8082/websocket
here http://community.blynk.cc/t/cloud-blynk-cc-host-is-no-longer-supported/6264/70?u=scropion86 is Dmitry post
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub https://github.com/tzapu/node-red-contrib-blynk-websockets/issues/8

is those changes will automaticly reflict to npm as my node-red is hosted on IBM bluemix and the online editor is not allowing me to change blynk-websockets.html file , so i have to update the node from npm.

New default port changed!
http://community.blynk.cc/t/0-23-0-0-23-1-server-port-changes/12373
Plain WebSockets port : 8082 -> 8080 (merged with HTTP API); Since 0.23.0.
SSL WebSockets port : 8081 -> 9443 (merged with HTTPS API); Since 0.23.0.

ws://blynk-cloud.com:8080/websocket it is?

No, the correct url is: ws://blynk-cloud.com:8080/websockets
see pull #18


Streamlined code examples in readme

Provided a complete, drop-in code in the first example

Added comments to ... in other examples

[ ] package.json:version has been updated with npm version patch (or major/minor as appropriate)

[ ] @brainhubeu/react-carousel version has been updated in docs-www/package.json to the same which is in package.json:version

Also, cause this PR affects only docs, I don't think we have to bump any package.json version.
Not sure whether it will pass CI pipeline, but let me double check that. After that, I think it's ready to merge 👍

@MrHuds0n @damian-brainhub
AFAIK versions need to be bumped in order to publish new docs

@intercaetera
Can I ask you to fill in this form https://docs.google.com/forms/d/1tfRs1Io49tJBwz-06aDnz8hrJ3WySJTi45y4k6hHGaQ ?


New tutorial series improvements

Tracking issue for possible improvements to Wagtail’s new tutorial series, which soft-launched last week.
Customize homepage

[ ] Add a wireframe or information architecture diagram reflecting the site’s page structure (feedback by @cnk)
[ ] Rewrite Using on_delete=models.SET_NULL ensures’s "preserving their data entries" to be clearer (feedback by @cnk)

Set up site menu for linking to the homepage and other pages

[ ] Recipes / blog post on "ways to create menus in Wagtail" to address this frequently asked question (feedback from @cnk)

Contact page

[ ] Describe the fields added by AbstractEmailForm (feedback from @cnk)

AbstractEmailForm defines the fields to_address, from_address and subject

Deployment

[ ] Add more options (PythonAnywhere? CodeRed?) (feedback from @cnk)

Is this issue open to work on? Do you require any help with the documentation? Thanks...

@nandini584 this issue is assigned to members of the core team so I assume they will be resolved by theem.
However, if you're up for it, could you try to do the new tutorial end to end and then see if there are any items of feedback, typos or questions that come up?
It's viewable on the latest version of the docs here - https://docs.wagtail.org/en/latest/tutorial/index.html
You can either use the form linked on the docs or add a comment here or if it's just small fixes, create a PR.

Sure i am interested in doing it. @lb-

Feedback from @shyusu4: when following the documented CodeRed Cloud instructions at the end of the tutorial, it’s not clear how to proceed. The documentation only offers SFTP as an option. The first step is to connect to the project's server but when I try I get this error<EMAIL_ADDRESS>Permission denied (publickey). Connection closed.


LUCI infra failure on "Linux Android Scenarios" try job for flutter engine PRs

There were a couple of PRs like: https://github.com/flutter/engine/pull/21179, where this job resulted in an infra failure. This will likely end up blocking autorollers.
cc: @cbracken

@iskakaushik can you please share the link to the failing task? from the PR link seems like it succeeded

https://ci.chromium.org/p/flutter/builders/try/Linux Android Scenarios/1243

This is a duplicate of https://github.com/flutter/flutter/issues/65803


Asset detail page always links to latest library version

Browser
No response
Description
Asset detail pages have a link with the version that takes you up to the library. That link should be version aware.
If you're viewing an asset with no specified version:
https://next.carbondesignsystem.com/assets/carbon-charts-angular/latest/area-simple
The version properly takes you to library with no version:
https://next.carbondesignsystem.com/assets/carbon-charts-angular
We should keep that as-is, but if we detect that there's a version in the URL:
https://next.carbondesignsystem.com/assets/carbon-charts-angular/v0.55.1/area-stacked
Then the version anchor should take you to that version:
https://next.carbondesignsystem.com/assets/carbon-charts-angular/v0.55.1
Potential solution
For that link, just remove the asset slug so if it has a specified version in the URL, it's still there.
Steps to reproduce

Go here https://next.carbondesignsystem.com/assets/carbon-charts-angular/v0.55.1/word-cloud
Click v0.55.1
It takes you latest which is v0.57.0 https://next.carbondesignsystem.com/assets/carbon-charts-angular

Expecting https://next.carbondesignsystem.com/assets/carbon-charts-angular/v0.55.1

Hey team! Please add your planning poker estimate with ZenHub @alisonjoseph @francinelucca


Expose --require and --loader hook from this module.

Would be great if the require and loader hooks from the other esbuild-kit modules were exposed from this top level one. In some scenarios I wan't to use the main tsx bin, but still the others are handy and it'd be nice if I didn't have to install other modules.
I was thinking it should be as simple as adding a exports to this module that with the import condition would expose the loader and otherwise would expose the require hook such that you could:
node -r tsx
node --loader tsx

as an example of where this is useful:
mocha -r tsx

:tada: This issue has been resolved in version 3.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

For any future visitors here: when switching from ts-node/register, use just tsx directly (tsx/register doesn't exist).

It's also documented here:
https://github.com/esbuild-kit/tsx#nodejs-loader

Ah, nice! I was searching for register, which explains why I didn't find it in the docs :)


Multiline cell in ng-grid 2.0.7 / angularjs nggrid

I'm trying to show data in multiple lines in one of the cells, is this possible with ng-grid?
I have a column called ' Related' which is initially empty when the grid loads. Users can select a row and add new relations which shows in the Related column. I want the column to expand to show relations upto 6 relations and then it should go to the next line when the 7th relation is added, like shown in the html table example below.

Has anyone tried anything similar? My auto width is also not working at this point

Two parts to it:

Set the rowHeight to a larger value.  Note that all rows have to have the same height, so you need to decide how many lines you want and set the rowHeight appropriately.  You cannot have dynamic row heights per row.

Set the cellTemplate so that it supports multiline.  In my application I'm using:

Your mileage may vary on that, it's been a while since I did it and I think it's a little flaky.

I've tried setting the rowHeight to 200px and when the grid renders it sets the row height to 200px which is a lot of empty space. And it looks like there is no way to set dynamic rowheight :(
Also, My Related column gets cut off and it seems like I cannot achieve what I need.
Thanks Paul!

You have to set the cellTemplate on the related column to allow wrapping, something like the cellTemplate I showed above.

Dynamic row heights are not possible due to virtualization. Non-dynamic but custom row heights are being covered in this issue, mostly: #2759. Closing this as a duplicate of that.


Add a AutoFlip demo with a single worker.

Please be free to comment, this is similar as the previous pull request but with a single worker.


Console error when using arrow keys in a mat-select with a mat-option without value.

What is the expected behavior?
When selecting a "no value" or "null value" mat-option with keyboard, no error appears in the console output.
What is the current behavior?
When selecting a "no value" or "null value" mat-option with keyboard, an error appears in the console output.

main.5b2eef94be108354fa6e.js:1 ERROR TypeError: Cannot read property 'viewValue' of undefined

NB : no problem when selection is done with mouse click.
What are the steps to reproduce?
Error is appearing in angular material documentation web site :
https://material.angular.io/components/select/overview#getting-and-setting-the-select-value

Open browser console
Select "Option 1" with mouse
Use up arrow key to select the "empty mat-option" (None)
Look the console output

Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 7
Material 7.3.1
Tested with Chrome and firefox
Is there anything else we should know?

Will be fixed in the next release by https://github.com/angular/material2/pull/15160.


Support for Groq and Local AIs

Kudos on this project! I'd love to see support for local models and Groq in future releases.

too much work for me


Update iot-hub-csharp-csharp-device-management-get-started.md

fixed a typo

@phigax : Thanks for your contribution to the Azure documentation! The author, @JimacoMS2, has been notified to review your proposed change.

#sign-off
Thanks for catching this @phigax -- much appreciated!


feat(CLI): add dxf-to-svg cli command

Implements a cli command to convert dxf to svg.
Additionally the dependencies have been updated.

The Travis build failed but it was a spurious issue, restarted & passed. Will merge now and create a new release.
Thanks for the contribution!

Releases in 3.3.0


Adding a Hard Link entry type for Tar

Hi,
I need to be able to add Hard Link entries in a Tar Archive.
In the current code TarEntry has a TarFilePart, TarFilePart has a TarHeader, TarHeader has an EntryType property where probably a HardLink type can be specified but TarFilePart, TarHeader and EntryType are all inaccessible from the client code.
Even if they were, there is no property which will have the Link file name.
Am I missing anything here or the SharpCompress library does not support writing Hard Link entries to a Tar archive?
Regards,
Mayank

I'll have to revisit the Tar code.  I can't remember I properly implemented Hard Links or not.  I do know Tar is one of the more incomplete implementations in sharpcompress.

Is there a chance you may revisit this issue? Storing Hardlinks in TAR is its unique feature and the reason may people actually select TAR over other archivers - it makes dramatic difference when the data contain many duplicate files.

It is unlikely I'll be doing anything with sharpcompress myself between a young family and work.
Accepting pull requests though!


EAGLE-1079 - Fix checkstyle issues in antlr module

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[EAGLE-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

LGTM, thanks for fixing style check


Timestamp localization

This PR is based on issue #483 and #193.
It adds localized timestamp underneath the different BarCharts by using the date-fns format() function. This defaults to p, the localized format, and other formats can be set per locale. For example, en-US will keep the current default of ha. If no locale is set, the en-US format will be used.
In order to fix some visual bugs with almost overlapping labels underneath the BarChart showing events, autoSkipPadding: 1 has been added to the options of Chart.js. This will cause Chart.js to more frequently 'skip' a label to preserve readability. The precise timestamp can still be seen in the tooltip by hovering over the bars itself.
Regarding this tooltip, I haven't provided a way to localize these yet. This would probably necessitate some slight refactoring of lib/lang.js and/or getTooltipFormat() in components/metrics/BarChart.js.

Love the new time notations, is it possible to get the tooltips fixed as well?

Love the new time notations, is it possible to get the tooltips fixed as well?

Certainly possible, I suppose getTooltipFormat() in the BarChart component could be changed:
function getTooltipFormat(unit) {
    switch (unit) {
      case 'hour':
        // return 'EEE ha — MMM d yyyy';
        return 'EEE p — PPP';
      default:
        // return 'EEE MMMM d yyyy';
        return 'eee PPP'; // Or 'PPPP'
    }
  }

This would produce the following:
Dutch:
zon 21 februari 2021
zon 13:00 - 21 februari 2021
English:
Sun February 21st, 2021
Sun 1:00 PM - February 21st, 2021
etc.
This does assume, however, that the order of items is the same in every locale (probably not). In that case, you'd need to add or change a function in lib/lang.js to allow overwriting this as well on a per locale basis.
I could look into this somewhere in the coming week, if I have time somewhere.


[Feature]: Add ability to pass config to presets

🚀 Feature Proposal
With v29 deprecating ts-jest in globals, it's now nearly impossible to both use a preset and pass options. Presets are just recipes and extending them should be trivial. To pass options, we currently would have to copy the recipe (which mostly defeats the purpose), and then add our custom options, or do some crazy remapping of the preset values, adding our config that way.
It's actually pretty surprising to me that this was released with no way to extend presets, and the docs have both a page for Presets and a page for Options, and the two cannot be made to work together.
This could be accommodated by add a withOptions function on each preset that's basically a factory for creating the preset with the options merged in.
const { jsWithTs } = require('ts-jest/presets')

///
{
  transform: jsWithTs.withOptions(opts).transform,
}

If there's a better way, I'd love to hear it. Thank you.
Motivation
My motivation is to make it trivial to add options to presets, thereby making them useful again in cases where a tsconfig path or some other option needs to be adjusted.
Example
No response

This feature is now available under https://kulshekhar.github.io/ts-jest/docs/getting-started/presets#advanced
The documentation is not yet nice so any suggestions are welcome. Thanks :)


Cannot add Nested Blocks without using Inline Blocks

Description
I am currently working with blocks in the TinaCMS sidebar. I would like to have nested blocks. Is this possible without using inline blocks?
I have a CardDeck block that consists of multiple Card blocks. However, when I click on the plus button in the CardDeck block, it does not display any options for blocks to add:

Steps to reproduce
I can't link the project as it is private, but here is my code for the fields portion of the CardDeck block. I thought because I have 'card-block' in the templates, that the card block would be added as an option with the plus sign:
fields: [
{
name: ‘cards’,
label: ‘Cards’,
component: ‘blocks’,
templates: {
‘card-block’: CardBlock,
},
}
],
When I go to the admin panel and click on the Card Deck block, I get to the screenshot provided.
Expected result
I would like to click on the plus button and see Card as an option of a block to add
Actual result
When I click on the plus button, there are no options displayed of blocks to add
Environment
Tinacms Package Versions
+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>
Tools

Tool
Version

browser
Chrome

os
Windows 10

node
12.19.0

npm
6.14.8

Yes I was going to make an issue for this too. "Cannot add block to nested block field in sidebar (+ button does nothing)"
The first/root block field works fine

I noticed this recently as well. I checked the HTML in dev tools and saw that the list was populated correctly, but the opacity was 0. I think the + button just sets the opacity to 1:
https://github.com/tinacms/tinacms/blob/62e2105fb26878b2c618b0048812cd48c681b3a1/packages/%40tinacms/fields/src/plugins/BlocksFieldPlugin.tsx#L327-L333
I think the visible state is somehow flipping back to false on open.

Adding to the intrigue, if you expose the neighboring panel (the root, if you will), then you can trick it into opening.

For clarity, the Cards panel has the CSS top property increased such that the Page Sections field of another panel is exposed.


Chat bot

Describe the project you want to add with tech stack
Chat bot with floating button option, which will help the user to add this chat bot in any already existing website.
Tech Stacks used are - HTML, CSS, Vanilla JS, API
Expected behavior
Can answer any question as it fetches info from openAI APP
Screenshots (optional)

please assign this issue to me

I would like to work in this project. Can you Please assign me in this project this is my first open source contribution and would like to work in this.

please assign me this issue under GSSoC'23.


Cmd readmes

Changes
Adding some cmd/* READMEs on how those binaries work. #895 added some documentation on cmd/pullrequest-init, I thought it would be good to add for the others. This PR only covers cmd/bash, cmd/creds-init and cmd/entrypoint.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide
for more details.

Manually updating CLA: continuing woes around redhat employee CLAs


Type text to currently focused input

The typeText action requires an element, but it would be nice to just text into any element that is currently focused. That way we can test certain workflows where the input should autofocus. Is there a way to do this already?

Could you please elaborate? Do you mean sending keyboard clicks in the responder chain? What are you looking to achieve/test? As I see it, this can most useful for testing iPad keyboard shortcut support, such as CMD+C, CMD+V, etc.

@abdulkhaliquem9 adding a testID would find the inputText even if it was autofocused. However, since the library you are using doesn't have a testID, if I were you, I would either implement the component from scratch without needing the library or just fork the library and add a testID to make it easier but yeah not ideal.

@Eyesonly88 got a solution for this issue on Android.
await element(by.type('android.widget.EditText')).typeText('08902\n');
Currently Detox test case fails if we pass 'TextView', and throws error to pass the full class name.


Improve the reliability of the state of VMs

The idea is to mix the /vms resource (link to the Cloud API) and informations returned by NodeExecutors (SlipStream Client) when they are doing periodical requests to the SlipStream Server.

Doesn't apply anymore


[ServiceBus] add custom endpoint support

Port relevant changes from Event Hubs. Most of work was done in core-amqp. This PR just
needs to connect the client options with the underlying connection context.

Packages impacted by this PR
@azure/service-bus
Issues associated with this PR
#21574

API change check for @azure/service-bus
API changes have been detected in @azure/service-bus. You can review API changes here
API changes
+     customEndpointAddress?: string;


Fixes report bug navigations for iPad

Adds NewIssueTableViewControllerDelegate  to settings view controller
Navigate to Issues view controller after submitting new issue from "Report a bug"
Present new issue view controller with formsheet style so it can work fine on iPad

Closes #468 , #469 and #467

Awesome @rizwankce!


Allow pipelines to provide input for other pipeline variables

Solve the general problem of "this pipeline requires me to provide a variable value, that I don't have yet" by allowing pipelines to "expose" their capability to provide output that matches the required input of a different pipeline.
Example
Let's take this example:

Say I want to use the "List Feature Flags" pipeline (second one), and it requires me to provide a customer UUID. However, I currently only have a customer email at my disposal.
Let's imagine there to also be a "Find Customer UUID" pipeline that accepts either an email address or a customer name, and returns the matching UUID.
I can now:

open the Find Customer UUID pipeline (this is assuming I know this pipeline exists),
enter the customer's email address,
run the pipeline,
copy (#17) the returned UUID output,
close this pipeline,
open the List Feature Flags pipeline,
paste the copied UUID,
and run the pipeline.

Proposed Solution
It would be great if we can programmatically proof that there is a relationship between these two pipelines, by adding some extra metadata to the output of pipelines, which can be linked to the input needed by other pipelines.
One possible solution I'm thinking of:

When creating a pipeline, you can optionally name the output of each step in that pipeline.
The output of a pipeline equals the output of the last step in a pipeline, and so the output name of a pipeline equals the one used in the last step
When opening a different pipeline, and it asks for a variable named Customer UUID, the system will search for one (or more?) pipelines for which the output name is set to that same name.
It will then suggest to you this other pipeline
What happens then in terms of UI, moving back and forth between pipelines, I'm not sure about.

Here's an example of how such a help message could be displayed. In this case, the field is for the Customer UUID variable in the "List Feature Flags" pipeline, and there is another pipeline called "Find Customer UUID" which has its output name set to Customer UUID:

side note on the second point in the proposed solution:
We can optionally simplify this part by defining the output on the pipeline itself, instead of the steps and then picking the last step in a pipeline. However, this is error prone, because step ordering might change, or new steps might be added, at which point the output might no longer match.
I think it's safer to set the output names on the steps themselves. This also provides more composability in the future, when we work on a UI for creating new pipelines, using step templates, for example.
Design Goals
The above proposal is one possible solution, but there are more. In general, I'd like to try and find a solution that matches these goals:

composable – using existing features (or features already proposed elsewhere), little to no new concepts/data structures required
simple – fits well in the UI, is not confusing to use, should be self-explaining
generic – should solve the overarching problem of "I need to provide a value that I don't know yet"
safe – no automated pipeline runs without explicitly triggering them

Given this:

When creating a pipeline, you can optionally name the output of each step in that pipeline.

Perhaps this can be combined with https://github.com/blendle/automaat/issues/22:

[...] allowing steps to define an output attribute, which determines to which temporary variable the output is assigned.

So, a step would define its output name as Customer UUID, and within the task that the step belongs to, you can reference that output in the template (#23) as {{ var['Customer UUID'] }}, and if that step is the last output of the task, when opening other tasks that have the input variable named Customer UUID, a link will be provided to the other task that has this variable as its output.
I'm not 100% sold on the idea yet (there's maybe a bit too much coupling between the features, which goes beyond the desired composability), but it seems possible to do this...

One thing that could make this work is:

A step output variable cannot exist already within the same task (neither as a task variable nor another similarly named step output variable).
This makes sense, because if Task A accepts Variable 1 as input, then it doesn’t make any sense to have a step in that task output the same variable name (that would mean the step didn’t add any “value” to the task result).
By adding this constraint, it becomes impossible to have duplicate variable names, giving more clarity to what’s going on, and allowing us to use the {{ var['Variable 1'] }} notation.
This constrained is checked when the task is created.

After thinking on this some more, I no longer think it makes sense to combine #22 and this issue.
I've written the new design thoughts in #22 for that issue, and will write the ones for this issue below.

Here's the current design I've come up with:

We introduce a new step_output_advertisements table (to be bike-sheded, variable_value_advertisements?).
This has the data (id, step_id, variable_name) (variable_name to be bike-sheded, key?).
It has a uniqueness constraint on (step_id, variable_name).
Whenever a task requires input variable X, it will look in this new table to see if there are any advertised variable names matching X.
If there are, the UI shows a list(dropdown?) of task names providing the relevant variable values somewhat similar to the UI mock-up above (although how this works in the UI is still undecided).

There are several advantages I can see by using this design:

It solves my main concern of merging #22 and this feature ("there's maybe a bit too much coupling between the features, which goes beyond the desired composability").

It composes nicely with the current data model of tasks with multiple steps.

It prevents data consistency invariants which cannot be enforced on the data storage level (i.e. removing a step with advertised output does a cascade delete to remove that advertised output).

It allows a single task to provide multiple advertised output values. For example if a task has a step that fetches the Customer UUID and it also fetches the Customer First Name in another step, that task can now be used to provide programmatic access to both those variable values.

There is no coupling between internal variables names (#22) used within a task, and any named advertised output. You cannot break one, by changing the other.

You are no longer required to use the final output of a task (so the last step in a task) as the advertised output.
This point is significant, because of this (very common) pattern:

You have a task that finds a customer UUID based on a provided email address. You add some "pretty printing" to the output of the task. In this case, your task could look like this:

Step 1 reads the provided {{ var['Customer Email'] }} variable value, and uses the SQL Query processor to fetch the relevant customer UUID.
Step 2 uses the Print Output processor to print the final output of the task as Customer UUID: {{ var['Customer UUID'] }}\n\nRemember to [use this customer information responsibly][link to data protection document], thank you..

.
The output of Step 1 is interesting to other tasks that require a customer UUID as their input variable value. The output of Step 2 is useless for programmatic access, but meant for humans to read.
By allowing Step 1's output to be advertised, we can provide both programmatic access to the relevant data, and make the final output of this task more significant for the person running the task.

A single variable name can be provided by multiple steps (in different tasks). For example, the variable Customer UUID could be provided by a task named Find Customer UUID by Email and one named Find Customer UUID by Username, allowing the person needing this value to decide which one to use, based on the data available to them.
On this point, a design consideration is to show both the task name and description in the dropdown, because both of these tasks might be named "Find Customer UUID", but their description might mention "Searches for a customer UUID based on their {email address,username}"

A first step towards this has been implemented in the web client in 57ae000bb6129847b976123466fe8d5950b902db.
A "direct link" will be added to another task, if any step within that task advertises itself as a value provider for a variable in the active task:

If more than one task can provide the variable, a drop-down menu is shown instead:

Clicking on the link will open the other task. Other than that, no other integration/automation is added yet. You still need to copy the output of the other task, and move back to the previous task to continue.
(this issue will remain open until the whole loop is implemented and there is as little friction as possible)

Clicking on the link will open the other task. Other than that, no other integration/automation is added yet. You still need to copy the output of the other task, and move back to the previous task to continue.

This last part is simplified as of fd2db24dc8dfa9f541dd25fa569a13f66e9772f5.
When you navigate to another task from the current task, clicking the "Back" button now moves you back to the first task. This works for infinitely nested tasks. Once you are back at the original task, clicking "Back" returns you to the home page.

There's another thing to consider here.
Say for example I want to find the Customer UUID based on some value that might return multiple results (such as seaching by Family Name).
In this case, if Task A provides this functionality, it can provide you with a value for the Customer UUID in Task B, but it can return multiple results, and will not always return a single result.
In these cases it can still be useful to be linked to task A, but there can't be any automation (#33), you'll have to use your own judgement which result to pick (and copy/paste that result over).
We might potentially want to enhance the current variable advertisement functionality introduced in 3d45e615ffad14eedadc9d9019f4efe1c7a82bca to allow an advertiser to mark the advertisement as something that can be used automatically (so a single value), or something that has to be picked manually (a set of values, or a value that doesn't match exactly what you'd need for this variable, but can be copy/pasted or inferred from it).


docfd: 5.1.0 -> 6.0.0

Description of changes
https://github.com/darrenldl/docfd/releases/tag/6.0.0

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

1 package built:

docfd


[1.16] IF is marked as supporting 1.16.3, 1.16.4 on CurseForge but requires Forge 36.0.1+, which is 1.16.5 only.

On CurseForge, the latest release of Industrial Foregoing is marked as supporting Minecraft 1.16.3, 1.16.4, and 1.16.5 but the required Forge version (36.0.1+) is only available for 1.16.5, making the game fail to load when used in 1.16.4. Either the Forge requirement needs to be dropped lower or the CurseForge metadata needs to be adjusted, since many launchers rely on CurseForge metadata being correct to determine compatibility (such as GDLauncher).
This is made even more confusing given that the filename still contains 1.16.4.
Industrial Foregoing Version:
industrial-foregoing-1.16.4-<IP_ADDRESS>-7ac4a96
Titanium Version:
titanium-1.16.4-3.2.5
Crashlog If Applicable (Upload to pastebin/gist):
N/A.

Fixed thanks!

Fixed thanks!


Add TotalAppointment command feature

Codecov Report
Patch coverage: 2.63% and project coverage change: -0.12 :warning:

Comparison is base (837c7ee) 31.42% compared to head (62a6dff) 31.31%.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #107      +/-   ##
============================================
- Coverage     31.42%   31.31%   -0.12%
  Complexity      503      503
============================================
  Files           185      187       +2
  Lines          3920     3934      +14
  Branches        395      397       +2
============================================
  Hits           1232     1232
- Misses         2631     2645      +14
  Partials         57       57

Impacted Files
Coverage Δ

...main/java/seedu/address/commons/core/Messages.java
0.00% <ø> (ø)

...ddress/logic/commands/TotalAppointmentCommand.java
0.00% <0.00%> (ø)

...java/seedu/address/logic/commands/UndoCommand.java
0.00% <ø> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
34.04% <0.00%> (-0.75%)
:arrow_down:

...ss/logic/parser/TotalAppointmentCommandParser.java
0.00% <0.00%> (ø)

...address/model/service/appointment/Appointment.java
0.00% <0.00%> (ø)

...va/seedu/address/logic/commands/StackUndoRedo.java
26.08% <20.00%> (+8.94%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


jaeger search result is unusual

According the gif upon.
We can see the trace time of results change often.
So the result would lose some traces sometimes.
But We want to see the nearest traces timely.
And I ensure that there is no more trace produce (beacuse this is just a test env).
I think it's strange~

I observed that running the all-in-one ✋ Is it expected since it's meant to be more of a temporary / development solution?

Looks related to: https://github.com/jaegertracing/jaeger-ui/issues/57
@molon if you increase the "Limit Results" to something like 1000 and repeat this, do you see the same thing happening?

@black-adder Thanks  for reply.
https://github.com/jaegertracing/jaeger-ui/issues/57

I see - the memstore implementation likely doesn't provide stable search, because it uses hash maps internally. It's doable, but doesn't seem too important.

This is the problem. :)


Added persistent_queue capability to Azure Monitor Exporter

Description:
Added a new config item to support the QueueSettings values.
Extended the exportHelper.New[Metrics|Logs|Traces]Exporter call to pass in the QueueSettings config, thus enabling persistent_queue for this exporter.
Link to tracking Issue:
Fixes issue #25859
Testing:
Documentation:
Added sending_queue config items to README.md's configuration section.

Poor branch name - closing to reopen with a more accurate name.


Is this not already a part of Refined Storage?

We only have the Refined Storage mod installed, but I see a wireless crafting grid is already available. Does this mod add something new, or am I otherwise misunderstanding?
Thanks for the great mod!

We only have the Refined Storage mod installed, but I see a wireless crafting grid is already available. Does this mod add something new, or am I otherwise misunderstanding?
Thanks for the great mod!

It adds a "Wireless CRAFTING Grid" while Refined Storage adds everything but the crafting grid (eg. grid, Fluid grid, crafting monitor)

is there a way to add infinite range and cross dimension ?


Change NGINX countdown timer to pretty one

Just to make all countdown timers looks the same...

Hi @anton-kasperovich I admire your dedication to consistency!  Only one small concern with this, TOOL_SLEEP_TIME = 30 seconds, so you are increasing the NGINX sleep from 5 to 30 with the above change.
Would this be better?
until [[ $(curl -I -s -u ${INITIAL_ADMIN_USER}:${INITIAL_ADMIN_PASSWORD_PLAIN} http://${TARGET_HOST}/|head -n 1|cut -d$' ' -f2) == 200 ]]; do pretty_sleep 5 Nginx; done

(I tested it).

Hi @kramos , on my environment, there's not much difference, as it's sleeps more than ~60 seconds, but it looks like on Travis CI it's a bit faster and totally make sense to revert to 5 seconds sleep. Good point, updated this PR.

LGTM

LGTM.


Updates after changed pod template

Currently we just inspect the version suffix of the base image to determine whether all containers are in sync. We can change the entire pod template though and it the new resource field in the Prometheus TPR we actually do.
So we'd need something like pod_template_hash labels like Deployments use eventually.
It's all still up in the air how the PetSet controller will provide updates later on. If it will also use that label, we will be conflicting again.
Possibly we'd just do a an on the fly hash for now or simply track all mutable template fields until it's figured out what the PetSet controller will do.

I updated a Prometheus resource to add an externalUrl config. The statefulset was updated to add the command -web.external-url line argument, but the (single) pod was not recreated with the new argument. I had to manually delete the pod, which was them recreated with the new command line argument.
Is this problem caused by the issue you raise @fabxc?
I also notice that the creationTimestamp for the statefulsets and pvcs created by prometheus-operator are always null, that seems incorrect?

StatefulSets are targeted to get rolling updates in 1.7, so we will just wait for that to land.

So rolling deployments have indeed landed in 1.7 and StatefulSets can be fully mutated without any errors. However, to automatically rollout these changes the Pods still have to be deleted manually, or we have to implement using the actual rolling deployments the StatefulSet now offers.


Update virtual-network-test-latency.md

updating update command for Ubuntu

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


WIP: tracing: Use Jaeger operator (with operator in istio-init)

This is a slight variation of #9508 to overcome an issue reported by @jmazzitelli when attempting to uninstall istio - the operator is removed before having a chance to cleanup the instance (i.e. jaeger in this case) that it has created.
So this will be a general problem that will be faced if using operators from helm.
Solution being demonstrated here is to move the operators under the istio-init folder, along with the setup of the CRDs.
To try it out:
kubectl create namespace istio-system
helm template install/kubernetes/helm/istio-init --name istio-init --namespace istio-system | kubectl apply -f -

wait for definitions to be available (current check is just for crds using kubectl get crds | grep 'istio.io\|certmanager.k8s.io' | wc -l, so might need to be made more general to cover operators
helm template install/kubernetes/helm/istio --name istio --namespace istio-system --set tracing.enabled=true | kubectl apply -f -

use istio are before..... and then cleanup:
helm template install/kubernetes/helm/istio --name istio --namespace istio-system --set tracing.enabled=true | kubectl delete -f -

and eventually
helm template install/kubernetes/helm/istio-init --name istio-init --namespace istio-system | kubectl delete -f -

A jaeger-operator service still seems to remain, but that is likely a bug in the operator which we'll fix.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: objectiser
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: mandarjog
If they are not already assigned, you can assign the PR to them by writing /assign @mandarjog in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sdake Would this approach, of moving the operator deployment into istio-init work for you?

@objectiser: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
cab0f4d872c537748cc5156fb614ff01f4d67919
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@objectiser: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
cab0f4d872c537748cc5156fb614ff01f4d67919
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-integ-k8s-tests.sh
cab0f4d872c537748cc5156fb614ff01f4d67919
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Closing as seems better to follow approach used in #13407, to assume operator has been installed previously, and make the helm install use of it optional dependent on certain values.


Better check for PoGo running

Sometimes PoGo stops working even though it's opened and the frontmost app, so a better approach would be to check if PoGo is actually doing something. Those functions check the last log time of GC and then checks if it's more than 5 minutes in the past. We can further tweak that time frame in the future.
#include <asl.h>
#include <time.h>

int pogo_work_state(time_t log_time)
{
    time_t current_time = time(NULL);
    return (difftime(current_time, log_time) > 300);
}

time_t get_last_log_time()
{
    aslclient client = asl_open(NULL, "com.gocheats.jb", 0);
    aslmsg query = asl_new(ASL_TYPE_QUERY);
    asl_set_query(query, ASL_KEY_SENDER, "com.gocheats.jb", ASL_QUERY_OP_EQUAL);
    aslresponse response = asl_search(client, query);
    aslmsg msg;

    time_t last_time = 0;
    while ((msg = aslresponse_next(response)) != NULL)
    {
        const char *time_str = asl_get(msg, ASL_KEY_TIME);
        time_t time_val = (time_t)strtoll(time_str, NULL, 10);
        if (time_val > last_time)
        {
            last_time = time_val;
        }
    }

    aslresponse_free(response);
    asl_free(query);
    asl_close(client);

    return last_time;
}

Was hoping we wouldn't have to do this.  Your code looks correct so hopefully I'll only need to do a little testing.

Still want to investigate this but one core issue I have seen is the launchDaemon stopping with a non-zero exit code. Pretty sure calling the killall binary is one of the issues since kernbypass blocks that process.
Will have a new update out in a few days that hopefully improves the monitoring aspect. It's been more stable on my four test devices the last 24hrs.
If this is still an issue after that update I'll look into monitoring the log.


@ApiParam allowableValues multiple comma separated values

I would like to have these values for @ApiParam(allowableValues

projects
issueTypes
issueTypes,projects

But since all values are separated at comma, the third compound value is not working and gets split at the comma (obviously).
Is there any way to specify a value containing a comma for @ApiParam(allowableValues ?
thx

Hi, did you manage to fix this?
@ApiParam(value = "vars", required = true, allowableValues="projects, issueTypes")
this seems to accept any value in Controller.

no i used some placeholders
@ApiParam(allowableValues = "projects,issueTypes,projects;;;issueTypes", required = false, value = "You can specify one or more keys as comma separated list")

and the maven-replace plugin to replace it after the maven plugin producing the swagger.json had run
            <plugin>
                <groupId>com.google.code.maven-replacer-plugin</groupId>
                <artifactId>replacer</artifactId>
                <version>1.5.3</version>
                <executions>
                    <execution>
                        <!-- EXECUTE RIGHT AFTER SWAGGER!!! -->
                        <!-- NOTE: since Maven 3.0.3, for two plugins bound to the same phase, the order of execution is the same as the order in which you define them in the pom.xml!!! -->
                        <!-- http://maven.apache.org/ref/3.3.3/maven-core/lifecycles.html -->
                        <phase>compile</phase>
                        <goals>
                            <goal>replace</goal>
                        </goals>
                    </execution>
                </executions>
                <configuration>
                    <includes>
                        <include>${basedir}/src/main/resources/api/swagger.json</include>
                        <include>${basedir}/target/swagger.json</include>
                    </includes>
                    <token>projects;;;issueTypes</token>
                    <value>projects,issueTypes</value>
                </configuration>
            </plugin>

Which produces the result I want:
       {
          "name" : "expand",
          "in" : "query",
          "description" : "You can specify one or more keys as comma separated list",
          "required" : false,
          "type" : "string",
          "enum" : [ "projects", "issueTypes", "projects,issueTypes" ]
        }

Your solution will only produce atomic results

you wasted my time!


mkosi-full: 20.1 -> 20.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for mkosi-full is: Build legacy-free OS images
meta.homepage for mkosi-full is: https://github.com/systemd/mkosi
meta.changelog for mkosi-full is: https://github.com/systemd/mkosi/releases/tag/v20.2
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 20.2 with grep in /nix/store/29qcis8cfd7jfqf5m9na3knmq424dqx5-mkosi-20.2
found 20.2 in filename of file in /nix/store/29qcis8cfd7jfqf5m9na3knmq424dqx5-mkosi-20.2

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
mkosi
mkosi-full

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/548277d4c8d17bbc34ba75d2f9840831331ba0bf#mkosi-full

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/29qcis8cfd7jfqf5m9na3knmq424dqx5-mkosi-20.2
ls -la /nix/store/29qcis8cfd7jfqf5m9na3knmq424dqx5-mkosi-20.2/bin

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

2 packages built:

mkosi
mkosi-full

Maintainer pings
cc @malt3 @katexochen for testing.

Duplicate of https://github.com/NixOS/nixpkgs/pull/283108


runtime error: invalid memory address or nil pointer dereference

While Running I got this error message after the latest update
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x85fde2d]

goroutine 2791 [running]:
/wa-api/whatsapp.(*WaHandler).HandleError(0xa9a8280, 0x88d5000, 0xab28b38)
        /home/beshoo/go-wapi/wa/whatsapp/handle_error.go:28 +0x6d
created by github.com/Rhymen/go-whatsapp.(*Conn).handleWithCustomHandlers
        /root/go/pkg/mod/github.com/!rhymen/go-whatsapp@v0.1.1-0.20200408093540-2f227c53b44f/handler.go:183 +0x166

What is going on?

After some debug i note this is the error which returns
Error connection to WhatsApp servers failed: websocket: close 1006 (abnormal closure): unexpected EOF
But why lib is forcing to fail?

@beshoo I've similar problem, but my problem it's when i tried to send a message, because my form doesnt' print the qr code and session doesn't start. Do you connect your golang code with data base or graphic interface (html,web,etc) ?
thanks and srry for my english


error on ubuntu 18.04

[Error: SQLITE_ERROR: /home/parikh/greymarket/node_modules/sqlite-vss-linux-x64/lib/vss0.so.so: cannot open shared object file: No such file or directory]
Using npm/node. Why is there the extra .so appended there?

The extra .so gets appended by SQLite because the original attempt at loading vss0.so fails. It most likely fails because the linux sqlite-vss builds are compiled on Github Actions runners, and the earliest ubuntu build I can access is 20.04, because 18.04 was deprecated. Also Ubuntu 18.04 reached end of life recently, so it'll be tricky to justify supporting it.
Unfortunately, your best bet currently is to compile sqlite-vss yourself and load it in manually.


Description of key -s have diametrically opposed description with reality

Describe the bug
-s, --secret-name string   name of a Kubernetes Secret in the argocd namespace containing Vault configuration data in the argocd namespace of your ArgoCD host (Only available when used in ArgoCD). The namespace can be overridden by using the format <namespace>:<name>
But the plugin uses namespace:name like this name:namespace
To Reproduce
cat /tmp/manifest.yaml | argocd-vault-plugin generate -s argocd230rc:argocd-vault-plugin-clientdemo -

cat /tmp/manifest.yaml | argocd-vault-plugin generate -s argocd230rc:argocd-vault-plugin-clientdemo -
Error: secrets "argocd230rc" is forbidden: User "system:serviceaccount:argocd230rc:default" cannot get resource "secrets" in API group "" in the namespace "argocd-vault-plugin-clientdemo"

Expected behavior
Option -s parses secret in another namespace as declared
Additional context
argocd-vault-plugin version
argocd-vault-plugin v1.7.0 (cfd17486e894c9df5a8aa342967e164e800e16f8) BuildDate: 2022-01-25T15:53:59Z```

We are aware of the issue https://github.com/argoproj-labs/argocd-vault-plugin/issues/287 and there has been a fix implemented. We just need to release it.

Issue has been fixed here https://github.com/argoproj-labs/argocd-vault-plugin/releases/tag/v1.8.0


Adding Quill-Application-Types (Quats) to AST

Here's the brief summary:

Many features are not possible to implement in Quill without having a proper type-system i.e. every Ident knowing it's type. This includes proper handling of booleans in SQL databases which do not support true/false values (#1685).
Query Expansion with Spark does not work properly when tuples are used, this is because Spark needs to select aliases of inner queries by name instead of by an expansion the way regular SQL does (i.e. in ExpandNestedQueries). Issues #1843 and #1912 are symptoms of this.
As it is, ExpandNestedQueries is buggy. For example, a subquery with .nested will not always include every needed field in the super-query select expansion . Additionally, ExpandNestedQueries has never been able to properly expand things like escaped clauses. For example, the Oracle functionality to escape all clauses starting with the "_" character still does not properly work .
The phase RenameProperties has become very complicated as a result of having to propagate schemas of embedded objects, a mechanism called "Schema Protraction" has been created to address this issue but it substantially adds to the knowledge-debt of this phase. It has had a continual stream of issues due to its complex nature here and with the added complexity, it is becoming unmaintainable.
Many phases such as ExpandDistinct are hard to reason about because they do not adhere to any notion of type-fullness. This has caused things like #1628.
In order to provide a way forward, a basic Quill-specific type system must be introduced which can incorporate more and more use-cases in the future. Not all Quill query transformation functionality should be replaced at the same time as that would be too great an impact. Rather, an evolutionary strategy going forward should be introduced (metaphorically speaking, think Introns/Exons in flagella that took everything to the next level ;-)).

Here's the slightly longer version. I have been maintaining Quill for several years now and as I began fixing some complex issues, a pattern seemed to emerge where more and more problems began to arise as I introduced more and more complex behaviors to remedy various bugs. At some point, I realized that Quill can only be stabilized if the space of possibility of the AST itself is substantially reduced.
More specifically, unless we introduce some notion of types into AST, we will never be able to expand subqueries correctly, treat expressions correctly, or even alias/rename clauses correctly. This problem most notably manifests itself in ExpandNestedQueries and RenameProperties where we have built very, very complex machinery to unfold parent-queries into sub-queries in order to understand what is actually going on. As I piled more and more complexity into this machinery in order to fix existing bugs, more and more bugs appeared on the horizon and at some point, I realized that I was proverbially chasing my own tail. Trying to expand sub-queries based on things selected from super-queries is a fundamentally flawed proposition. We need to know what fields an alias actually has inside of it to get this kind of expansion correct.
To make matters worse, strange behaviors began to emerge. In order to fix tuple handling in quill-spark, I had to treat every single kind of SelectValue Ident as a tuple which required prefixing things with "_1" which where single-value selections. Queries would start or stop working of .nested was applied to contexts that seemed to make no sense. Much of this resulted from relaxing restrictions about the kinds of expressions that infix and express (see #1534) which added to the variety of nested-ASTs possible, which then caused a multitude of nested query expansion bugs like #1864 and #1905.
Reflecting on various approaches to types, a bare minimal strategy was chosen. Every AST node will have a .quat field that represents it's Quill-Application-Type. Since most AST elements merely reflect their inner types, only things like Ident, Infix, and several others actually need to have a Quat-type directly inferenced from the parser. Things like FlatMap(a,b,c).quat for example are just c.quat.
For now, I have decided to only introduce  three Quat-Types with the intention of adding more (e.g. Booleans) in the future. The are:
Quat.Product
  Representing both Case Classes and Tuples. The latter which will have all their fields as _1, _2 etc...

Quat.Value
  Representing values (e.g. which can potentially be encoded/decoded). Since checking this requires
  summoning encoders over and over again which is compotationally expensive a "rule of thumb" can
  be introduced that treates anything which is not a case class type, a type-bounds type and/or things
  that are final as a Quat.Value. This may need to be refined in the future and various caches may also
  need to be added.
  (Currently there is a type->quat cache but a encoder cache may also be needed)

Quat.Null and Quat.Generic
  These are needed to represent types whose values are not fully known yet. Typically they should be
  "filled in" by beta reduction of various transformation phases.

Fixes #1912, #1913, and paves the way for many others.
(Continue reading below)

Adding Quats to the Quill AST is a very large endeavor because all of the transformation phases now need to synthesize Quat-Type-correct trees. ApplyMap for example needs to replace Map-subtrees and reduce various Idents, these now need to be typed as Quat Tuples.
In SymbolicReduction, the AttachToEntity phase can no longer arbitrarily use an "x" alias to synthesize an unused Ident because this can and will conflict with "x" aliases from outer FlatMap nodes, causing the Normalization to think that they belong to those outer clauses. For this reason, I have made AttachToEntity create an Alias which uses a UUID (i.e. so it is not guaranteed to conflict with anything) and I have added a final stage in AvoidAliasConflict Normalization to change it back to "x" or the first free x[1-9]+ Ident available.
I have left ExpandJoin alone despite a desire to re-write it. Since this phase introduces aliases that technically don't exist in the functional code (i.e. the Scala equivalent of the Quill transformation), I have decided to leave it alone for now. The following gist presents an alternative implementation that is type-safe. (More details are presented in the Comments there).
I have decided to add a check to BetaReduction that makes sure that any reduction of one Ast element into another has a corresponding Quat that can actually be reduced. That is to say, for any beta reduction (x:Ast) -> (y:Ast), the y.quat must be equivalent or a sub-type of x.quat. Since it is impractical to implement a whole inheritance hierarchy into Quats, I have decided to use the duck-typing paradigm instead and make sure to check that if y.quat contains all of the fields of x.quat, the replacement can indeed be done. The one exception to this is if either x.quat or y.quat are Quat.Generic or Quat.Null. In this case, the Quat of the Beta Reduction will be whatever quat (of either x or y) is more concrete. If one of these Quats is a Quat.Product that has nulls or generics inside, this rule is applied recursively.
In general, I have tried to add various comments to Transformation phases that I have found particularly difficult to understand (e.g. the first case in Symbolic reduction, some ApplyMap cases etc...). This by no means is a complete coverage but should provide the beginnings of a documentation body of Quill internals.

One note about AST changes. In things like Ident it is important to exclude the Quat construct from the hashcode/equals methods that BetaReduction relies on since Quat.Generic or Quat.Null (or even a sub-type Quat.Product) can be reduced to/from an Ident that should match (i.e. because it has the same alias). For this reason, I have introduced elements such as IdentId into the AST. These are strictly responsible for only the equals/hashcode methods of things like Ident so that it is properly treated in beta-reduction.
Another important thing to mention is the performance impact of such a change. I have profiled the QuatMaking class which parses Scala AST into a Quat in order to detect macro slowness. The best indication of whether a Type is actually a Quat.Value is actually to check if there is an Encoder for that type. Since it is a very large performance impact to attempt summoning an encoder for every single Scala Ident's q"$id".tpe, I have decided to check this only in a last resort and also treat any final class as a value class. A Encoder only needs to be summoned in the event that there is a type-boundary element in order to clearly indicate that the plugged-in expression should be polymorphic.
Additionally, since when resolving a generic parameter, the asSeenFrom command needs to be used (and this is also quite slow), a cache of what Quats have been generated from what Types has been added.

One other consequence of using reflection to produce Quats is that this needs to be done from the Dynamic API as well as the static one. The Dynamic API relies on ClassTags as opposed to Type tags and generally has looser restrictions on types since fewer inferences are possible as type-erasure has already happened. For this reason, the phase RepropagateQuats has been introduced which takes Quats from Entities inside AST elements such as Map(a,b,c) and FlatMap(a,b,c) writing them into the Idents (i.e. from a to b variables in the example above). This has been added to translateDynamic in ContextMacro.

Thank you for your work here @deusaquilus, it is remarkable. A very smart approach, clearly based on your backgrounf maintaining the tool for quite some time, which to address most of our current problems, while paving Quill's future! 👏
Given the amount of knowledge you have gathered, I would suggest to open loads of issues regarding the addition of other Quats (and probably there are many more related changes). I believe it will help to spread the knowledge among current maintainers/contributors and possibly welcome new ones, assuming it would be a good amount of new  issues and possibly some of them could be labelled as "good-first-issue".

@juliano

I would suggest to open loads of issues regarding the addition of other Quats

Here's a post which is hopefully the 1st of many. This is how to fix booleans in SQL Server and Oracle:
https://github.com/getquill/quill/issues/1685#issuecomment-662275696


Can we tag latest commits?

Description:
When I update via Carthage 0.18.1, I get the following error:

$ carthage update --platform macOS
*** Fetching OAuthSwift
*** Checking out OAuthSwift at "1.1.0"
*** xcodebuild output can be found in /var/folders/jr/lhvt2ks57fg_fwtz8mnmwxr80000gn/T/carthage-xcodebuild.FHfXl7.log
*** Building scheme "OAuthSwiftOSX" in OAuthSwift.xcworkspace
/Users/rryan/.../Carthage/Checkouts/OAuthSwift/Sources/OAuthSwiftHTTPRequest.swift:142:42: warning: expression implicitly coerced from 'String?' to Any
/Users/rryan/.../Carthage/Checkouts/OAuthSwift/Sources/OAuthSwiftHTTPRequest.swift:143:55: warning: expression implicitly coerced from 'String?' to Any
/Users/rryan/.../Carthage/Checkouts/OAuthSwift/Sources/OAuthSwiftHTTPRequest.swift:142:42: warning: expression implicitly coerced from 'String?' to Any
/Users/rryan/.../Carthage/Checkouts/OAuthSwift/Sources/OAuthSwiftHTTPRequest.swift:143:55: warning: expression implicitly coerced from 'String?' to Any
/Users/rryan/.../Carthage/Checkouts/OAuthSwift/Sources/OAuthSwiftHTTPRequest.swift:142:42: warning: expression implicitly coerced from 'String?' to Any
/Users/rryan/.../Carthage/Checkouts/OAuthSwift/Sources/OAuthSwiftHTTPRequest.swift:143:55: warning: expression implicitly coerced from 'String?' to Any
/Users/rryan/.../Carthage/Checkouts/OAuthSwift/Sources/OAuthSwiftError.swift:137:53: warning: expression implicitly coerced from 'Error?' to Any

In diagnosing this, it appears that these have been fixed in commits subsequent to the last tag. Can we please add a new tag when we do fixes so that Carthage will grab these. If you don't tag it, Carthage won't grab it.
When I forked it and added a tag bumping the revision number, as shown below, it got the latest and greatest:

$ git tag -a 1.1.1 -m "Version 1.1.1"
$ git push --tags

When I did that, and then changed the Cartfile to point to my fork, it worked fine.
I can submit this as a pull request, but it seems that incrementing the revision number should just be part of every commit.
OAuth Provider (Twitter, Github, ..):
N/A
OAuth Version:

[ ] Version 1
[ ] Version 2

OS (Please fill the version) :

[ ] iOS :
[x] macOS :
[ ] tvOS :
[ ] watchOS  :

Installation method:

[x] Carthage
[ ] CocoaPods
[ ] Manually

Library version:

[x] head
[ ] v1.0.0
[ ] v0.6
[ ] other: (Please fill in the version you are using.)

Xcode version:

[x] 8.1 (Swift 3.0)
[ ] 8.0 (Swift 2.3)
[ ] 7.3.1
[ ] other: (Please fill in the version you are using.)
[ ] objective c

done
thx