doc: update structure and adjust things in README.md

Signed-off-by: Allen Sun<EMAIL_ADDRESS>1.Describe what this PR did
This PR updates the structure in README.md and adjust pouch logo and so on.
We can feel the change of this file.
For user manual, we propose that we should divide into two parts: CLI manual and API munual, and more API related docs into docs/api directory.
2.Does this pull request fix one issue?
NONE
3.Describe how you did it
NONE
4.Describe how to verify it
NONE
5.Special notes for reviews
NONE

Update majority change request, PTAL @Letty5411
And thanks a lot for your careful review. 🌹

LGTM @allencloud


docs: fix broken image and change table style

Brief Information
This pull request is in the type of:

[ ] bug fixing
[ ] new feature
[x] docs

Related issues:

closed #413
closed #411

/approve


After  user applies a filter on Help Board, the user focus should be redirected to the  filtered post

Steps:

Navigate to https://rcv11.fightpandemics.xyz
2.Navigate to View Help Board
Scroll Down a few posts on Help Board
Click on Filters-> location
Enter 'Irvine' ->choose Irvine, CA 92602
6.Click View Result

Filtered Post goes to the top. But the user observes some scroll on the page but not redirected to the filtered post. (I can share video on slack)
Expected: User should be redirected to the filtered posts

@sheeba1 I'm not seeing the issue here. Can you share a video?

reproduced like in below gif.

@OzkanAbdullahoglu , thanks for reproducing it and adding to Git.(reproduced exactly  !).  Ididnt know how to add a video

@sheeba1 & @OzkanAbdullahoglu I can confirm this works with Firefox but not Chrome.
I was wondering if it is because the antd layout content is using non-standard ::--webkit-scrollbar pseudoelement? It works fine in Firefox using the main scrollbar so maybe if there's a way to disable it so it behaves similar in other browsers? I couldn't immediately see anything here: https://ant.design/components/layout/
OR if that doesn't work maybe just scroll to top when filters applied? https://developer.mozilla.org/en-US/docs/Web/API/Window/scrollTo

@sheeba1 & @OzkanAbdullahoglu I can confirm this works with Firefox but not Chrome.
I was wondering if it is because the antd layout content is using non-standard ::--webkit-scrollbar pseudoelement? It works fine in Firefox using the main scrollbar so maybe if there's a way to disable it so it behaves similar in other browsers? I couldn't immediately see anything here: https://ant.design/components/layout/
OR if that doesn't work maybe just scroll to top when filters applied? https://developer.mozilla.org/en-US/docs/Web/API/Window/scrollTo

stroll to the top can be a solution but I 'll dig a bit when I find the time, the first solution which you mentioned would be better I think.

Related - but #1372 also affects Firefox.


Artists cannot see his collection

His address: GyS1y23xkuFQZzBzbob3wVMkThc8bkfoEoGJQY1HPMZTPw4
An artist created two collections " math art " and "algorithm art" on Kusama (rmrk1). When he wanted to add NFTs to the collection - he cannot find them.

Can someone let me know what he should do next, or try to do? Where can be error?

His address: GyS1y23xkuFQZzBzbob3wVMkThc8bkfoEoGJQY1HPMZTPw4
An artist created two collections " math art " and "algorithm art" on Kusama (rmrk1). When he wanted to add NFTs to the collection - he cannot find them.

There is no collection named "math art" not "algorith art" on rmrk1.
And there has never been collection created by this account on this chain.

@roiLeo thank you for quick response. I appreciate 🚀.
Can you pls check again? The person just tried it again. Video proof:
https://github.com/kodadot/nft-gallery/assets/104380776/2fbaab8e-d240-442a-a23c-5338a617726e
Also, it should be there now:

Indexer issue

Soon disabling minting on rmrk1 & rmrk2? Not gud idea much in long-term


set cookie which with a specific path

I work a project with vue-router
the response from server get a set-cookie header
 'set-cookie': [ 'JSESSIONID=47BA62D1A1F9646BE03042C9D0D1479D; Path=/root/; HttpOnly' ]
router configuration
var router = new VueRouter({
  saveScrollPosition: true,
  history: true,
  hashbang: false,
  root: '/root'
})

how should I do to fit the server? make all requests take up that cookie in path /root

Try the https://github.com/vuejs/vue-router repo


Add a new way to display size (smaller)

What do you  think of an option like this?

Good idea! This can be a good start for proposing a "compressed mode" used for some layout like the exa -lG.

@Peltoche I know this got merged but I feel like short might be a better flag than small. What do you think? Should we change it to short?

@Peltoche I know this got merged but I feel like short might be a better flag than small. What do you think? Should we change it to short?

It's true that "short" seems semantically more correct to me. As the feature have not been released yet, we can change the name without problems so let's go for it.


[Core Graphics] Fix apinotes for CGPathCreateMutableCopy

What's in this pull request?

CGPathCreateMutableCopy and CGPathCreateMutableCopyByTransformingPath
have 'self' type of CGPath, and thus must be imported as members of
CGPath proper, not CGMutablePath. Does so by following common naming
conventions for producing mutable copies.
rdar://problem/26339788
Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

CGPathCreateMutableCopy and CGPathCreateMutableCopyByTransformingPath
have 'self' type of CGPath, and thus must be imported as members of
CGPath proper, not CGMutablePath. Does so by following common naming
conventions for producing mutable copies.

@swift-ci test


Drill Down

I was wondering if drill down could ever be a supported in Deneb?

Not easily, but it's not a 'no'. I've talked about the challenges we would have with implementing this in a visual like Deneb on Twitter last year. The thread goes into some detail but the feature request never eventuated, so it's good that we now have an issue to track against in the repo.
To surface that content up into a form that's a bit easier to follow:

Very much a sensible question, but one that can't be answered concisely! Have thought about it, but challenging to solve generically. Could definitely be done if building a viz from scratch using Vega, but hard to tackle in a visual like Deneb that needs a flexible dataset.
For a custom visual (or core visual), you can create the data roles ("fields"/"buckets"/"wells"...) that your visual dataset needs, and you can prescribe which of these are enabled for drill up/down. This is hard to predict from my end, and typically why I'd suggest falling back to bespoke dev here. The easiest comparison to make is that dataset for Deneb needs to work like a table visual, allowing a flexible number of columns, as each use case is going to be different. Tables don't support this.
Because visuals can only "see" the data that Power BI gives them at a given moment, rather than having knowledge of the data model (with good reason), it would put a lot of onus on the creator to add logic to their spec to determine if a column is currently visible.
This could either be through drill-down or expand. So there may be multiple cases to handle. We also don't know that the visual is drilled-down, just that we may have columns in our dataset or not. Not to say that I don't trust creators to handle this. Quite the opposite 😊
If I were to add this, I would need to create a special role for it, and would have to think hard about how it might need to work. If it's something you would like, you're welcome to create an issue in the GitHub repo - https://github.com/deneb-viz/deneb/issues - I wouldn't have an ETA, but if it's in the backlog, I can prioritise/plan to spend some time on exploring the possibilities and if I can find a nice way to manage it (plus document quirks, as it will require work from creator to handle effectively) then I will do my best to implement 😊

I still think that drilldown/expand is best handled in a dedicated custom visual, where full control over the data view is known, particularly as we don't have any APIs that can help us understand a hierarchy, or what level we're at. I'll keep this issue open for further comment and discuss, as there may be others who might have some direction on how we could handle this. I do have some makings of an idea that I will try to crystalise when I'm a bit more able to focus on defining the problem; this might not be for a while as I'm currently focusing any time I have spare on cross-highlight support work for 1.2/1.3.

Thanks @dm-p  - I didn't realise it was so complicated. FYI, Charticulator have a drill-down implementation but only for the stand-alone web app. I have asked the same question over there so will be interesting to see if they have any good ideas for how to approach this.

I'm hoping it's not going to be too complicated, but we might be limited - once I can focus some time on it, it may not be so challenging but I'll have to reserve judgement for now.
Indeed, that implementation for Charticulator will encapsulate the drilldown role and build the .pbiviz w/the necessary capabilities. I will include the pbiviz extension for the web app in my analysis, as there may be some learnings we can glean 👍

I think that for us to solve field parameters (#238), this (Drilldown) needs to be done first, as whilst drilldown can be orthogonal, when expansion is applied it only supports columns, and this is easier to work out from a generic perspective.
With field parameters, we need to consider the possibility that parameters can be columns, measures or columns & measures. By solving Drilldown + Field Parameters, we may then be able to understand calculation groups (if there are even use cases for them)😵💫
The initial proposal from my end as to how we support drilldown is as follows. The aim is to reduce ambiguity in the spec, when field names can be ever-changing based on user operations that we can't monitor from within the visual (as Power BI doesn't allow this). Happy to accept feedback or further thoughts, as I'd like to get this right the first time.

We add our 'known' fields to the Values role as normal. These will work as they do currently.

Expose a dedicated data role for drilldown fields (named __drilldown__ internally) that we can add a hierarchy to, e.g.:

Deneb doesn't know what's happening on the visual header - just the names of the fields being passed through by Power BI. We will create a dedicated field in the dataset for the drilldown category, named __drilldown__ and based on what Power BI gives us in the data view. This will behave as follows:

(If the visual is drilled-down) the current value for the field matching the role will be as expected.

Based on our above example, if Year is the current drilldown level then this will be 2021, 2022, etc.; Month would be Jan, Feb, etc.

(If the visual is expanded) multiple categories will be visible in the data view but will be concatenated (and formatted based on each individual column's specifier, if present).

Based on our above example, if we've expanded Both levels, then this will be 2021 Jan, 2021 Feb, 2022 Jan, 2022 Feb, etc.

The purpose of the __drilldown__ field being fixed, is to provide consistency; we do not know what the field name in our specification is going to be, as this will be governed in the visual header by the user and will depend on what they are doing. It will be complicated to build in conditional checks for whether a field is visible or not, so instead we can rely on the consistency of the __drilldown__ field proxying this on our behalf. For those who do want more detail...

Irrespective of either scenario above, we will provide the following additional objects in the Vega view:

A signal named pbiDrilldownColumns, which will be an array of the column names from the data view.

This is not generic, but can be used in situations like flatten transforms (Vega | Vega-Lite) to get the component fields rather than a concatenated representation, if the visual is expanded.
This can also help to extract the values for axis titles or tooltips when using expressions.
In our above example:

(If the visual is drilled-down) the value will be a single-element of the current column, e.g. ["Year"].
(If the visual is expanded) the value will contain all visible column names, e.g. ["Year", "Month"].

A column in the dataset named __drilldown_values__, which will be an array of formatted component values, in the same order as the columns in the pbiDrilldownColumns signal for reconciliation purposes.

This serves the same purpose as above, in that the user can choose to work with the component values, if they want to.
In our above example:

(If the visual is drilled-down) the value will be a single-element array of all columns in the expansion, e.g. ["2021"].
(If the visual is expanded) the value will contain all visible values in the expansion, e.g. ["2021", "Jan"].

How this may work from a template generation and consumption experience probably needs some more thought. My current approach is as follows:

We can flag in a template that a user had something in the __drilldown__ role and recommend that these are added.
We do not know how many columns may be present in the data role (or how many columns are in a supplied hierarchy). Power BI does not expose this; it only exposes the fields needed to fulfil the user's requirements.
Therefore, we can reliably say that N fields are required to match the original author's design; we could allow a creator to document this in the template via the export dialog, but would not be able to enforce it the other end. (when consuming)
Therefore, it would be recommended that to keep templates generic, the creator does not explicitly refer to field names when deserialising the above component arrays with transforms, otherwise this will be a known limitation.

Visual examples of the above scenarios
The dataset and signals would look similar to the following for a simple dataset of Country Code and Sales.

Year and Month fields present in the  __drilldown__ role, with drilldown at the Year level:

Country Code
Sales
__drilldown__
__drilldown_values__

CA
96,595,976
2021
[ "2021" ]

US
98,506,487
2021
[ "2021" ]

CA
201,187,376
2022
[ "2022" ]

US
157,727,860
2022
[ "2022" ]

pbiDrillDownColumns = [ "Year" ]

Year and Month fields present in the  __drilldown__ role, with drilldown expanded to the Month level (subset of data to indicate grain):

Country Code
Sales
__drilldown__
__drilldown_values__

CA
51,332,424
2021 Nov
[ "2021", "Nov" ]

CA
45,263,551
2021 Dec
[ "2021", "Dec" ]

US
73,812,668
2021 Nov
[ "2021", "Nov" ]

US
24,693,819
2021 Dec
[ "2021", "Dec" ]

CA
53,342,111
2022 Nov
[ "2022", "Nov" ]

CA
147,845,265
2022 Dec
[ "2022", "Dec" ]

US
83,258,881
2022 Nov
[ "2022", "Nov" ]

US
74,468,979
2022 Dec
[ "2022", "Dec" ]

pbiDrillDownColumns = [ "Year", "Month" ]

Looks sensible to me but given the complexity, this will only really become clear when actually using it. Is this how charticulator handles it?

No - noting that the Charticulator custom visual still doesn't support drilldown, I don't think that visuals exported from the online app handle this correctly when imported into Power BI. As such the proposal is an original approach to the challenge.
For visuals exported from the Charticulator web app, any columns flagged for drilldown will only take the lowest-level field of the hierarchy, meaning that whether you expand or drill down, the result is inconsistent with expectations, e.g.:
Top-level

Drill - 1 Level
Visuals as expected (ignore sort on Charticulator visual; it's more of a grain experiment).

Expand - 1 Level
In this setting, the distinct month values are re-aggregated by Charticulator, mirroring the behaviour of drilldown.

Expand - 2 Levels
In this case the grain is back to the same level, so the number of marks is consistent (again ignoring differences in how marks are scaled).

The way I'm proposing above for Deneb tries to ensure that granularity is preserved whether you're drilling down, or expanding. Note that with Vega, we can't conditionally assign a field's type in a scale (as there's no expression support for this property), so we would need to work with a consistent scale for all levels, but this isn't something that can be done in Charticulator either. We might be able to request this for Vega at some point, if it turns out that we might need it.
How the above proposal might look in a Vega-Lite spec:
{
  "data": { "name": "dataset"  },
  "mark": "bar",
  "encoding": {
    "x": { "field": "__drilldown__", "type": "nominal" },
    "y": { "field": "Sales", "type": "quantitative" }
  }
}

Because the __drilldown__ field would represent whatever the combination of the current visible hierarchy is (either one field for drilldown, or one-to-many for expansion), this would preserve the grain and represent the values as correctly as possible for the user/reader.
Repeated for the above scenarios (and using similar data to the above proposal):
Top-Level:

Drill - 1 Level

Expand - 1 Level

I've spiked up the first part of the challenge, and can share a bit more which will hopefully clarify further in a more visual manner. I'll use the editor so that you can see the dataset change also.
https://user-images.githubusercontent.com/10572054/169216861-0b55bba1-20bf-47bb-bca7-3a700e4621a9.mp4
As a quick walkthrough, you should be able to see:

Year and Month in the Drilldown data role
The initial __drilldown__ field in the dataset shows [Year], as this is the current level. The __drilldown_values__ array shows this value too.
Drilling the visual will change __drilldown__ to the [Month] value, and the __drilldown_values__ array will reflect this change also.
Expanding rather than drilling will show the concatenation of [Year] & [Month] in the __drilldown__ field, and the __drilldown_values__ array will change to have both entries.
We notice that the axis label is too mangled for the step width. Well, Vega will take arrays and start new entries on a new line, so we could change the x-encoding to __drilldown_values__ instead, and these will get 'wrapped' (as best as we can manage with SVG)
Values in these two columns are formatted based on their format specification from the data model

Note that I haven't tested hierarchies yet, and as stated above, a known limitation that axes/scales will need to be the same type, as these are not expression-driven in Vega.

Looks awesome - great work. We can then create a Multi-Line Axis Label as described here https://vega.github.io/vega-lite/docs/axis.html.

Absolutely! If you're using this structure, you may need to reverse the __drilldown_values__ to achieve what you need, but something like the following would work:
{
  "data": {"name": "dataset"},
  "mark": "bar",
  "width": {"step": 35},
  "encoding": {
    "x": {
      "field": "__drilldown_values__",
      "type": "nominal",
      "sort": null,
      "axis": {
        "labelAngle": 0,
        "labelExpr": "datum.value[1] === 'Jan' ? reverse(datum.value) : reverse(datum.value)[0]"
      }
    },
    "y": {
      "field": "$ Sales",
      "type": "quantitative"
    }
  }
}

I'm glad you could find a way! @dm-p

Thanks! I'm happy with the initial investigations.
One small change to the above (having done some dogfooding):

__drilldown__ will be the array-valued field
__drilldown_flat__ will be the concatenated version of all field values in the visible hierarchy, delimited with spaces

Additionally, the approach works with either hierarchies or multiple columns, and (provided that row context is preserved for interactivity scenarios), clicking a mark to drill will work, if this is selected in the visual header.
We still have to do the work around templating and auto-completion, to ensure that this is supported here. This is quite a large item to sort out properly.

Does the new Drill API released for July change anything @dm-p ?

Best I can tell is it will make it easier to identify fields that have the drill role applied (although we'd be doing this anyway through the proposed approach above with a role specifically for drilldown). The API is more focused on programmatically drilling from within the visual rather than from the header or context menu which could have some potential applications, but not within the scope of this work. If you can think of anything that could be useful, please feel free to create an issue for it :)

Hi #Daniel Marsh-Patricio, I wonder if this is something that already works in deneb, or not yet, because I don't know how to implement it.

Hi @cristobalsalcedo90 - the issue will be closed when drilldown is implemented. This is currently due to be delivered in v2.

@dm-p  .. Has there been any update on this feature?

I got a notification that someone had requested an update, but I don't seem to be able to see it anymore. If that person is still looking for an update, my last comment is still the latest source of information. The feature has not yet been implemented, and this issue will be closed when available.
For transparency, v2 is being worked on, and drilldown is integral to the design of how the dataset will be processed and managed. It is a significant change to the visual architecture, as are many v2 features. I do not have a concrete ETA, but I am dedicating as much of my free time as possible to the R&D of v2, checking off all the feasibility concerns and re-scoping as necessary so that we can try and get v2 delivered in as tight and focused manner as I can. Drilldown has passed the feasibility stages and is in scope.
I will communicate updates to the drilldown capabilities when v2 firms up, as this will need significant testing and validation from anyone who can spare time before we move it to GA.


Add TLS encryption to SMTP receiver

As of today the e-mail receiving server (for e-mail publishing) is only able to accept plain text connections.
I'd like to be able to use TLS encrypted (STARTTLS) connections, as notification contents might contain sensitive information.
As an option, I'd like to be able to make TLS mandatory on the server side, i.e. reject not encrypted connections via an config option in the server.yml.

Hi, any update on this. It seems that some services now requires a proper tls encryption to send the email so it is a block for me. I would like to work on this one if you think this FR makes sense


[CARBONDATA-1482] fixed the failing test cases of presto integration

1.builds are passing
2.added dependency for spark guava
3.throw exception in case carbondatastore creator is unable to load the data
4.fixed the timestamp issue due to which test cases are failing

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/168/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/44/

@chenliang613

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/798/

LGTM


Add docker buildx package

Starting with docker v23.0.0 , docker build containers using BuildKit by default.
If BuildKit is not installed, the legacy builder is automatically used.
Since the Legacy builders seems to be deprecated, it is necessary to install buildkit package.
https://docs.docker.com/engine/deprecated/#legacy-builder-fallback
zeroalphat<EMAIL_ADDRESS>

When we run docker build command, Buildkit is used.
Since there is no need to change the commands used when building the container, I don't see the need to update the documentation.


Descriptions: add description component

Please make sure these boxes are checked before submitting your PR, thank you!

[x] Make sure you follow Element's contributing guide (中文 | English | Español | Français).
[x] Make sure you are merging your commits to dev branch.
[x] Add some descriptions and refer relative issues for you PR.

挺好的啊


update: README.md

Updated README for a better looking visuals.
Preview:
https://github.com/SergioRibera/sss/assets/103959811/97ab0cb8-b29f-43f1-9082-069188558d47

This is amazing, thank you very much


Import object sequence does not work with blender > 4.0

The import object sequence script doesn't work with newer versions of blender. Replacing:
bpy.ops.import_scene.obj(filepath=filepath, split_mode="OFF") with  bpy.ops.wm.obj_import(filepath=filepath, split_mode="OFF") fixes the error however, it only imports 1 shape key (the last one selected).
Meaning animations with multiple frames only have their last frame imported.

You could try this script:
bl_info = {
    "name": "Import Obj Sequence",
    "author": "MarcusZ",
    "version": (1, 0, 3),
    "blender": (4, 0, 0),
    "location": "File > Import/Export",
    "description": "Import Obj Sequence",
    "doc_url": "",
    "support": "COMMUNITY",
    "category": "Import-Export",
}

import bpy
from pathlib import Path
from bpy.props import (
    BoolProperty,
    CollectionProperty,
    StringProperty,
)
from bpy_extras.io_utils import ImportHelper

class ImportObjSeq(bpy.types.Operator, ImportHelper):
    """Load an OBJ Sequence as absolute shape keys"""

    bl_idname = "import_scene.objseq"
    bl_label = "Import OBJ Seq"
    bl_options = {"REGISTER", "UNDO"}

    filename_ext = ".obj"
    filter_glob: StringProperty(default="*.obj", options={"HIDDEN"})

    files: CollectionProperty(
        name="File Path",
        description="File path used for importing the OBJ sequence",
        type=bpy.types.OperatorFileListElement,
    )
    directory: StringProperty()

    relative_shapekey: BoolProperty(
        name="Relative ShapeKey",
        description="Import shapes as relative shapekeys. Uncheck to import absolute shapekeys.",
        default=True,
    )

    def execute(self, context):
        filepaths = [Path(self.directory, n.name) for n in self.files]
        if not filepaths:
            filepaths.append(self.filepath)

        self.create_shapekeys(filepaths)

        return {"FINISHED"}

    def create_shapekeys(self, filepaths):
        from contextlib import redirect_stdout

        def import_obj(filepath):
            with redirect_stdout(None):
                active_object = bpy.context.active_object
                bpy.ops.wm.obj_import(filepath=filepath, use_split_objects=False)
                bpy.context.view_layer.objects.active = active_object

        # import first obj
        import_obj(str(filepaths[0]))
        main_obj = bpy.context.selected_objects[-1]
        main_obj.location = [0, 0, 0]
        main_obj.rotation_euler = [0, 0, 0]
        main_obj.shape_key_add(name=main_obj.name)
        for face in main_obj.data.polygons:
            face.use_smooth = True
        main_key = main_obj.data.shape_keys
        bpy.context.view_layer.objects.active = main_obj
        seq_len = len(filepaths)

        # import the rest
        for i, filepath in enumerate(filepaths[1:]):
            import_obj(str(filepath))
            current_obj = bpy.context.selected_objects[-1]
            current_obj.location = [0, 0, 0]
            current_obj.rotation_euler = [0, 0, 0]

            # join as shapes
            bpy.ops.object.join_shapes()
            print(f"{i}/{seq_len}", end="\r")

            # remove meshes
            current_mesh = current_obj.data
            # Check if there are any materials, this is for sequence exporting in the model exporter plugin.
            # Only the first frame has materials and the rest are blank by default, this massively speeds up importing
            if len(current_obj.material_slots) > 1:
                current_mat = current_obj.material_slots[0].material
                bpy.data.materials.remove(current_mat, do_unlink=True)
            bpy.data.objects.remove(current_obj, do_unlink=True)
            bpy.data.meshes.remove(current_mesh, do_unlink=True)

        if self.relative_shapekey:
            # set keyframes
            main_key.use_relative = True
            for i, key_block in enumerate(main_key.key_blocks[1:]):
                key_block.value = 0.0
                key_block.keyframe_insert("value", frame=i)
                key_block.value = 1.0
                key_block.keyframe_insert("value", frame=i+1)
                key_block.value = 0.0
                key_block.keyframe_insert("value", frame=i+2)

        else:
            # set driver
            main_key.use_relative = False
            fcurve = main_key.driver_add("eval_time")
            fcurve.driver.expression = "frame*10"

        # set start/end time
        bpy.context.scene.frame_start = 0
        bpy.context.scene.frame_end = seq_len - 1

def menu_func_import(self, context):
    self.layout.operator(ImportObjSeq.bl_idname, text="Obj Seq As Shapekey(.obj)")

def register():
    bpy.utils.register_class(ImportObjSeq)
    bpy.types.TOPBAR_MT_file_import.append(menu_func_import)

def unregister():
    bpy.utils.unregister_class(ImportObjSeq)
    bpy.types.TOPBAR_MT_file_import.remove(menu_func_import)

if __name__ == "__main__":
    register()

That worked thank you so much!

Actually this imports the models and shape keys correctly but does not import the materials. So the meshes are completely blank. In blender 3.1 the script was able to import all the shape keys for the mesh and the materials as well. Any ideas on why that may not be working?


Add Support for DFT Opset 20

I updated most of the code so that we can support DFT 20 but what is incomplete is the lowering... it seems like this will take much more work than expected.  Support for shape inference is added in this PR only.
So I am creating two issues

To support dynamic dimensions since currently we do not
Add support for the lowering so the backend tests will pass correctly.

Right now there are no models using DFT as far as I know. So we should be okay for awhile. Please let me know your thoughts, thanks!

I remember that only the support for shape inference is added in this PR. If it is true, please update the PR description.

I remember that only the support for shape inference is added in this PR. If it is true, please update the PR description.

@chentong319 Okay I updated the description.... anything else I should update?

@chentong319 I fixed up the lit tests for DFTV17. Let me know your thoughts. Thanks :)

@tungld Okay I think I got everything you asked... let me know your thoughts. Thanks!

@tungld What about now? :)

@jenkins-droid Test this please

@jenkins-droid test this please

Jenkins Linux s390x Build #14523 [push] Add Support for DFT Opse... started at 16:38

Jenkins Linux amd64 Build #14493 [push] Add Support for DFT Opse... started at 15:38

Jenkins Linux ppc64le Build #13518 [push] Add Support for DFT Opse... started at 16:48

Jenkins Linux amd64 Build #14493 [push] Add Support for DFT Opse... passed after 1 hr 4 min

Jenkins Linux s390x Build #14523 [push] Add Support for DFT Opse... passed after 1 hr 30 min

Jenkins Linux ppc64le Build #13518 [push] Add Support for DFT Opse... passed after 1 hr 59 min


db dump tool: include sql file extension (#4702)

Pull request opened by the merge tool on behalf of #4702

Merged into branches iso4 in ce5d5df62e465f1bb66e8abbc4377ca8f8aac005


[SPARK-46271][PS][TESTS] Remove unused properties in pyspark.pandas.tests.groupby.*

What changes were proposed in this pull request?
remove unused properties in pyspark.pandas.tests.groupby.*
Why are the changes needed?
just code clean up
Does this PR introduce any user-facing change?
no
How was this patch tested?
ci
Was this patch authored or co-authored using generative AI tooling?
no

Merged to master for Apache Spark 4.0.0.

@dongjoon-hyun thank you so much!


Systems - add component popup window when adding a new system

After adding a new system, the first time the add new component popup window appears, the dropdown selection box is null. The user is forced to create a new component to continue.

Confirmed on dev. After creating a new system for ORIS 147, K-7 the add new component dropdown contained all the components not associated with the system.

Verified by adding a new component at the location level and by comparing database entries to list in the dropdown.


Build Windows

When I try run hover build windows I awalys get this:
hover: Downloading engine for platform windows-release at version 2c527d6c7e70e2f51bca1a46f1174b250f84c5da...
hover: Failed to download engine: failed to get Content-Length header: strconv.Atoi: parsing "": invalid syntax
hover: Engine builds are a bit delayed after they are published in flutter.
hover: You can either try again later or switch the flutter channel to beta, because these engines are more likely to be already built.
hover: To dig into the already built engines look at https://github.com/flutter-rs/engine-builds/releases and https://github.com/flutter-rs/engine-builds/actions

The problem is the CI stopped, because there was no activity on the repo. I already pinged them, but the didn't answer. Maybe we should fork the repo so we can fix it @pchampio @GeertJohan ?

The problem is the CI stopped, because there was no activity on the repo. I already pinged them, but the didn't answer. Maybe we should fork the repo so we can fix it @pchampio @GeertJohan ?

I forked, do you have any idea how I can make him try to download from my rep instead of the original?

You need to change this line: https://github.com/go-flutter-desktop/hover/blob/master/internal/enginecache/cache.go#L312
You also need the actions to be running. I think you need to setup a secret for the actions and the force push so the actions start running. When they succed it should work.

You need to change this line: https://github.com/go-flutter-desktop/hover/blob/master/internal/enginecache/cache.go#L312
You also need the actions to be running. I think you need to setup a secret for the actions and the force push so the actions start running. When they succed it should work.

I go try, if works, I type here. Dude, ty, you are saving my job kkkkk

You need to change this line: https://github.com/go-flutter-desktop/hover/blob/master/internal/enginecache/cache.go#L312
You also need the actions to be running. I think you need to setup a secret for the actions and the force push so the actions start running. When they succed it should work.

Do you think it would not be easier to download the file from there manually and make the code do what it has to do with the local zip?

I don't understand

I don't understand

In the code it downloads the rep zip file and then uses it, it wouldn't be easier to download it manually and make the code instead of trying to download it, do what you have to do with it locally

Yeah you can download it manually, but why would you do that? The engine builds need to run anyway and changing the repo url is much easier.

Yeah you can download it manually, but why would you do that? The engine builds need to run anyway and changing the repo url is much easier.

I try it now but dont works, I think I do something wrong, I changed the code but when I run the command, show same mensage:

Are you on windows? I see there is this release: https://github.com/Bestfastfire/engine-builds/releases/tag/draft, but the actions need to set the proper tag for it

I think you tried uploading an old release and use that for hover? It may work, but also may result in problems.

I think you tried uploading an old release and use that for hover? It may work, but also may result in problems.

Ye, I did it, I have no idea how to proceed, I am totally a layman in go :/

I think you tried uploading an old release and use that for hover? It may work, but also may result in problems.

Well, I'm going to finish my project and give the client the debug version for now, it's working fine. If this problem ever resolves or I figure out how to do it, I create the release.

Forget it, I found a file picker plugin that works without the need for hover, https://pub.dev/packages/file_picker_cross, works well in the standard flutter release.

@jld3103 yea we can fork the engine build repo. I guess we have no choice choice. Too bad, it’s something else we have to maintain.

Actions are now running again, but still we might want to fork the repo to get more control over it.

Hi, is this issue has a quick fix?

Any other method to build windows release?

Actions are now running again, but still we might want to fork the repo to get more control over it.

@all check that your flutter engine version was compiled by rs-flutter. If it was missed due to the action been stoped, please try update your flutter branch. Or use the hover engine-version flag an pick a version available as a rs-flutter/engine-build release.

Master channel builds are now succeeding again. Hopefully the other channels will work soon.

Actions are now running again, but still we might want to fork the repo to get more control over it.

@ALL check that your flutter engine version was compiled by rs-flutter. If it was missed due to the action been stoped, please try update your flutter branch. Or use the hover engine-version flag and pick a version available as a rs-flutter/engine-build release.

how? can u explain please?

Beta builds are also working again.

Hi, I'm still facing this issue, and flutter version is 2.5, hover version is 0.46.6.

Hi, I'm still facing this issue, and flutter version is 2.5, hover version is 0.46.6.

I also have this problem. I seem to have found a temporary way.
Run hover with flutter 2.2.3

(go to flutter dir ,checkout use this tag).
2.5 is always invalid syntax .

@niuhuan Yeah flutter 2.2 works, it's not a good idea to stay with a lower version of flutter through.

flutter-rs/engine 's action has stop auto build long time ago, watch the fork repertoire build.
Try modify hover sources change engine download url , then build hover,

flutter-rs/engine 's action has stop auto build long time ago, watch forked repertoires build.
Try clone and modify hover sources, change the engine download url , then build hover.

I had.success download 2.5 engine,  but failed to build ( aot error)


Add image rotation (lower priority, server side, same view as cropping)  in the expanded view accessible from the carousel

What

[ ] Add server side image rotation, in the same view as server-side cropping, in the expanded view accessible from the carousel

[x] openfoodfacts/openfoodfacts-dart/issues/304
[x] openfoodfacts/openfoodfacts-dart/issues/309

Part of

#766

I believe we can close @monsieurtanuki


Better motivate why convolutions useful

In the convolution practice we should better motivate why convolutions are a useful.

@seabbs do you think is still an issue and if yes can you make any suggestions for improvement?

Will do


Loosen dependency on multi_json

The other datamapper gems depend mostly on multi_json 1.3.2
Example: https://github.com/datamapper/dm-serializer/blob/master/dm-serializer.gemspec
dm-types also depended previously on 1.3.2 https://github.com/datamapper/dm-types/commit/e541869dc05fdd707e8242ec8922873f75e50fc2

After I merge this https://github.com/datamapper/dm-types/pull/86 can you rebase/squash and push this PR again so that it runs in CI (now that I enabled PR runs again)?

yes I can do that, I also relaxed the multi_json dependency on dm-serializer
https://github.com/datamapper/dm-serializer/pull/46

Go for a rebase, I just merged the fix into master. Thanks @basex!

Sorry tpitale, there is not really a need to decrease this gem dm-types version required. The problem is with dm-serializer. I will rebase or create a new PR there.


offline/sim evaluation recommendations

Excited by the work, great paper and open release.
I am interested in testing some ideas that will involve pretraining (e.g. architecture changes, etc.), likely without access to a real-world setup, at least at first. Just starting to look at the codebase.
Curious about  recommendations for sim/offline evaluation. 1) For evaluation, any recs / best practices for separating datasets into train/test/validation, or holding out rt-x datasets. What seem to be the most useful proxies for real-world perf. 2) I saw there are provided examples for sim finetuning, are there any results that could be shared for simulated envs? Are there any sim envs that "work" for testing zero-shot eval in addition to finetuning?
Thanks!

Thanks for your interest and for the great question!
In general, there is no single offline metric that directly correlates to real world performance, as there are multiple factors that could determine the success rate of a rollout, i.e. besides tracking end-effector position and orientation w.r.t to ground-truth the timing of closing the gripper can be quite critical. But we plot many metrics during training that should provide a good overview.
We are actively looking into sim envs for exactly your use-case, stay tuned for some updates for the next release of Octo!


this actually builds!

this will actually test our trusty and xenial builds now. it doesnt yet do the 32bit build, but once it does all we'll have to do is change the version, wait for travis to build it, and then run the publish script. essentially push button

This is awesome @kevinkreiser !


perf(es/transform): Add inline annotation

Description:
<EMAIL_ADDRESS>LTO = false
Benchmarking es/full/all/es5: Collecting 100 samples in estimated 54.860 s (100 iterations)
Benchmarking es/full/all/es5: Analyzing
es/full/all/es5         time:   [525.54 ms 526.92 ms 528.33 ms]

<EMAIL_ADDRESS>LTO = false + #[inline(always)]
Benchmarking es/full/all/es5: Collecting 100 samples in estimated 53.857 s (100 iterations)
Benchmarking es/full/all/es5: Analyzing
es/full/all/es5         time:   [510.40 ms 512.59 ms 514.88 ms]

Related issue (if exists):

Oops I uploaded wrong files


Fix missing yaml module

Short Description: Missing yaml module, fixed by install pyyaml package.
Fixes:

Missing yaml module

Beat me by a few minutes 😄

sure.

my bad, please make another PR.


Keyboard shortcuts do not work.

Describe the bug
Keyboard shortcuts Shift+A mostly work all other do not work.
Steps to reproduce the bug
Steps to reproduce the unexpected/unwanted behavior:
Just start Gimel Studio
Expected behavior
A clear and concise description of what you expected/wanted to happen.
Application environment (IMPORTANT)

Application version: [ v0.5.0 beta]
Launch method: [ launched from Blender addon and launched normally and launched from shell]

System (please complete the following information):

OS: [ Linux Ubuntu]
Version [20.04LTS]

Additional context
Add any other context and notes about the problem here.

I have yet to figure out why this issue happens. It seems like it happens after the focus is lost for the node graph.


MWPW-122827 - [SEO] Report on 404s

log 404 in an Excel/gdocs sheet

Resolves: MWPW-122827
Note: it seems that tracking 404s should be done with Analytics tooling, not Milo (see the discussion in the ticket). In case the decision is revisited this draft can be used as a starting point.
Test URLs:

Before: https://main--milo--adobecom.hlx.page/?martech=off
After: https://seo-log-404--milo--adobecom.hlx.page/?martech=off

Closing because we're pushing this request to our analytics folks where it belongs.


Css linter

Change linter to on push instead of PR and fix CSS linters.

It feels like you're still doing 2 things here? Setting up the config and fixing the errors?


fix: esm build

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add content to the Configuration Reference chapter

@welcoMattic Thank you for a few fresh reviews on those old PRs!


Strictly check for supported version

With this commit we add a strict check whether the supplied
Elasticsearch version is supported. We check the
--distribution-version command line argument for validity but also
the automatically derived distribution version because the distribution
version doesn't have to be specified in all cases.
Relates #1107

@elasticmachine test this please

@dliappis thanks for your review. I've addressed your comments. Can you please have another look?


[Feature] Allow users to define static constants

Summary
User requested feature:

We will be picking this up as part of the JS editor


launch_bounds is bad on HIP, figure it out

Don't want to forget where we can get perf. #3604 #3615

see my comment for issue related to launch_bounds here: https://github.com/tinygrad/tinygrad/issues/3536#issuecomment-1978155206

the launch_bounds macro usage is incorrect for HIP kernel definitions. It's applied to the kernel function in a way that's specific to CUDA, not HIP. HIP uses attribute((amdgpu_flat_work_group_size(x, y))) directly on the kernel function.


Added story source to sidebar

This PR adds the Story source to the sidebar, because currently the Story source is not shown in sidebar.

@tuchk4 could you have a look at this one, please?

Thanks for your contribution.
I would like to try to keep docs as clean as possible. Meaning not rendering everything everywhere. Maybe we can add configuration what users would like to add to sidebar. What do you think?


soroban-cli: Replace all hex-encoded contract ids with strkeys

What problem does your feature solve?
Currently there are places we input/output contract ids as hex-encoded strings abcd1234.... But there are others, like contract Address params, where we input/output them as C... strkeys.
What would you like to see?
We should stop encoding contract ids as hex bytes, and always use C... strkeys for contract IDs. This would include when you deploy them, invoke them, etc...
We should do it sooner the better, so that tooling and contracts in the ecosystem can standardize on this.
Ensure any updates that may be required in:

[ ] soroban-docs
[ ] system-test

What alternatives are there?

Support both? This is tricky, as we would need to try parsing as a strkey, then parse as hex. And people might use BytesN for their contract params. And we would need to pick an output format anyway, so it'll be as confusing as it is now.
Use hex everywhere? But then it'll clash with Address type in the contracts, so there is a weird exception.

Discord conversation context
https://discord.com/channels/897514728459468821/1111673776317399103


Update scanamo-circe to 1.0.8

Updates io.laserdisc:scanamo-circe from 1.0.5 to 1.0.8.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.laserdisc", artifactId = "scanamo-circe" } ]

labels: library-update, semver-patch

Codecov Report

Merging #241 into master will not change coverage by %.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #241   +/-   ##
=======================================
  Coverage   47.68%   47.68%
=======================================
  Files          24       24
  Lines         281      281
  Branches        1        1
=======================================
  Hits          134      134
  Misses        147      147

Continue to review full report at Codecov.

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


Add Codable support from Swift 4 to simplify storing complex objects

With Swift 4 we have a new and shiny feature that would make saving complex objects into the User Defaults really simple. I know, the UserDefaults are not meant to be used for complex objects (that's what databases are for) but still sometimes there's a not too complex object (like the user settings) which might be more practical if it was saved as one object under one key instead of generating keys for any possible setting option.
For Storing the object it could be converted to JSON and saved as a plain String. I'd love to see this, there's even another library that already implements this, but I like the approach of SwiftyUserDefaults better (there you have to explicitly specify the type of the object for example): https://github.com/Nirma/Default

Big +1 on this.  This would be super helpful being able to store existing types we have that conform to Codable.

struct Test: Codable {
public var workId: Int?
}
extension DefaultsKeys {
static let test = DefaultsKey<Test?>("test")
}
extension UserDefaults {
subscript<T: Codable>(key: DefaultsKey<T?>) -> T? {
get {
guard let data = object(forKey: key._key) as? Data else { return nil }
        let decoder = JSONDecoder()
        let dictionary = try! decoder.decode([String: T].self, from: data)
        return dictionary["top"]
    }
    set {
        guard let value = newValue else { return set(nil, forKey: key._key) }

        let encoder = JSONEncoder()
        let data = try! encoder.encode(["top": value])
        set(data, forKey: key._key)

    }
}

}

@calismatest Would you mind creating a PR with this solution?
@sunshinejr I'm not sure, but it seems to me that you are the current maintainer of this repo now. What do you think about this feature?


libraries page's title on spanish site is mistranslated

https://p5js.org/es/libraries/
title of libraries' page on spanish version must be 'bibliotecas' instead of 'libraries'

fixed


rectify config[caCert] property name

rectify config[caCert] property name

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


Add usage of conda to the docs

A conda package has been created for lightkurve.  This is 100% fantastic, but we have to complete this as follows:

understand how to update the conda package when new versions of lightkurve are released;
document the release procedure in the docs;
document how to install lightkurve via conda in the docs.

@gully Can you look into adding the correct conda install lightkurve instructions to the installation guide in the sphinx docs, and also briefly explain the steps needed to update the conda package in the 'for developers' page of the sphinx docs?

Resolved by #344.  Thanks @gully !


Return InstanceId in metadata for protostore object

Codecov Report

Merging #66 (311dd65) into main (8f3e50e) will increase coverage by 0.01%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #66      +/-   ##
==========================================
+ Coverage   70.27%   70.29%   +0.01%
==========================================
  Files          13       13
  Lines        1497     1498       +1
==========================================
+ Hits         1052     1053       +1
  Misses        350      350
  Partials       95       95

Flag
Coverage Δ

unit-tests
70.29% <100.00%> (+0.01%)
:arrow_up:

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

Files Changed
Coverage Δ

pkg/protostore/protostore.go
68.01% <100.00%> (+0.11%)
:arrow_up:


⚠ Digital Ocean - https://status.digitalocean.com/ has degraded performance

In acdb792, Digital Ocean - https://status.digitalocean.com/ (https://status.digitalocean.com/api/v2/status.json) experienced degraded performance:

HTTP code: 200
Response time: 209 ms

Resolved: Digital Ocean - https://status.digitalocean.com/ performance has improved in 5e5e056 after 2 days.


NGINX recipe does not configure basepath

The actual yum mirroring works well I'm getting the files downloaded, but the nginx recipe only installs nginx and does nothing else...
Also it seems you are hardcoding the servername to 'servername' in the _nginx.rb
should read    variables(
nginx_servername: node['yumserver']['nginx']['servername']
)
this is the entirety of the nginx config that your recipe generates
server {
listen      80;
server_name servername;
access_log  /var/log/nginx/servername.access.log main;
location / {
root  html;
index index.html;
}
}

Looking at the source this may be a issue with the package in chef supermarket and fixed locally, trying from trunk

Good spot, do you want to submit the fixes yourself? If not I'm happy to get it done.

created the PR just now


MINOR: Fix typo in GettingStartedGuide

Codecov Report

Merging #1320 into master will increase coverage by 0.12%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1320      +/-   ##
==========================================
+ Coverage   53.81%   53.93%   +0.12%
==========================================
  Files         253      264      +11
  Lines       23367    23645     +278
  Branches     5225     5276      +51
==========================================
+ Hits        12575    12754     +179
- Misses      10792    10891      +99

Impacted Files
Coverage Δ

@here/harp-materials/lib/IconMaterial.ts
44.44% <0%> (-55.56%)
:arrow_down:

@here/harp-map-controls/lib/Utils.ts
46.15% <0%> (-23.85%)
:arrow_down:

@here/harp-omv-datasource/lib/OmvTiler.ts
50% <0%> (-16.67%)
:arrow_down:

@here/harp-utils/lib/ObjectUtils.ts
83.33% <0%> (-10.22%)
:arrow_down:

@here/harp-utils/lib/UrlUtils.ts
84.09% <0%> (-7.81%)
:arrow_down:

@here/harp-datasource-protocol/lib/Extruder.ts
8.33% <0%> (-5.96%)
:arrow_down:

@here/harp-lines/lib/TriangulateLines.ts
11.9% <0%> (-2.99%)
:arrow_down:

@here/harp-materials/lib/Utils.ts
81.42% <0%> (-1.91%)
:arrow_down:

@here/harp-utils/lib/Logger/ConsoleChannel.ts
69.23% <0%> (-0.77%)
:arrow_down:

...rp-mapview/lib/text/TextElementsRendererOptions.ts
100% <0%> (ø)
:arrow_up:

... and 27 more

Continue to review full report at Codecov.

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


Release on OperatorHub

Release the Kabanero Operator on OperatorHub.io

We've decided it's not appropriate to list this on operatorhub.io due to:

lack of upstream kubernetes support, which is a requirement for operatorhub.io
lack of a "one-click" install experience which makes it impossible to install this operator out of the catalog.


Continue to expand bptools preflagger like functionality

At the moment a subset of features from the preflagging stage in bptools have a direct equivalent in flint. Continue to build these out.
At the moment since only ao-calibrate is being used for bandpass calibration, these operations are only exposed to the solutions file. When other modes are incorporated they might need to be further expanded to leverage the measurement set. Hopefully not a lot though as it is intended that the input to these preflagger functions will be the gains and flags directly.
The flint_aocalibrate task should also be expanded to run just the preflagger so we can assess how well it is doing.

I have started to add bandpass smoothing to the bptools component of flint in the smoothbp branch. Something has gone off though, and it looks to be both producing different output from my testing (inspecting the solutions plotted) and has produced some terrible looking images. Will need to step through it.
I also see some other todos in the aocalibrate task around naming. I might take the time to try to fix those as well.

Have implemented some primitive smoothing functionality which has been merged in #30. It is not as sophisticated as what is in bptools, but seems to be working well.


Update node.js-webapp-on-azure.yml

Added prune --production in nodejs workflow.
https://msazure.visualstudio.com/Antares/_workitems/edit/14425099/

can we add the link to issue which this PR is fixing.

can we add the link to issue which this PR is fixing.

Done.


Point Docs Site to toolbox Subdomain

[x] Configure https://toolbox.daohaus.fun/ subdomain
[x] Switch the Vercel deployment to use the new DNS

https://toolbox.daohaus.fun/ is resolving
Need to merge changes from the develop into main

@jonathanprozzi

Merged develop into main -- will create a new PR into develop with my docs updates. This way we'll have the bulk up since it's now resolving @earth2travis

done! https://toolbox.daohaus.fun/

This is done!


Extension provided terminal links don't work when activating via tooltip

Ctrl+clicking the actual link works, clicking the tooltip link doesn't

This is working fine for the extension sample:

Ok it's working now for the GHPRI extension too


(Caused by SSLError(SSLError(1, '[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation disabled (_ssl.c:1007)'))

ERROR: Max retries exceeded with url: /he-thong-sieu-thi-dien-may (Caused by SSLError(SSLError(1, '[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation disabled (_ssl.c:1007)'))
OS: Ubuntu Server 20.04
Libraries: curl, requests, urllib

This work for me
https://github.com/Kong/insomnia/issues/4543#issuecomment-1126771807


Version incompatibility with Rails 8

I cannot update to yesterday's official release of Rails 8.0.0 due to minitest-rails's version requirements. Note: Rails 8.0.0.rc2 worked fine, but not Rails 8.0.0.
$ bin/rails test
Could not find compatible versions

Because every version of minitest-rails depends on railties >= 7.1.0, < 8.0.0
  and rails >= 8.0.0 depends on railties = 8.0.0,
  every version of minitest-rails is incompatible with rails >= 8.0.0.
So, because Gemfile depends on rails ~> 8.0.0
  and Gemfile depends on minitest-rails >= 0,
  version solving has failed.

Working on it...


BUG: Exception when using chunking with react-native on ios

Setting the chunkSize option while uploading with a react-native app on ios gives an error like this:
[native] Exception '*** -[__NSPlaceholderDictionary initWithObjects:forKeys:count:]: attempt to insert nil object from objects[0]' was thrown while invoking sendRequest on target Networking with params (
        {
        data =         {
            blob =             {
                "__collector" =                 {
                };
                blobId = "DEC847CE-F341-45D8-915A-EBCBCA612CCC";
                offset = 3145728;
                size = 1048576;
            };
            trackingName = unknown;
        };
        headers =         {
            "content-type" = "application/offset+octet-stream";
            "tus-resumable" = "1.0.0";
            "upload-offset" = 3145728;
        };
        incrementalUpdates = 1;
        method = PATCH;
        responseType = text;
        timeout = 0;
        url = <snip>
        withCredentials = 1;
    },
    28507
)

Cause
The crash is caused by the blob being freed prematurely. There's an open pr to fix this:
https://github.com/facebook/react-native/pull/31392
To Reproduce
I've made a minimal reproduction here:
https://github.com/samal-rasmussen/tus-js-client-slice-bug/tree/master
And applied the fix here:
https://github.com/samal-rasmussen/tus-js-client-slice-bug/tree/fix

I've opened this bug report just for tracking purposes. The underlying bug is actually in react-native.

Thank you very much for reporting this underlying bug in React Native. If I understand correctly, we cannot do much right now but wait for the bug to be resolved?

Yup. The actual underlying bug is in react-native and must be fixed there. I've just opened this issue here because the bug breaks a feature of tus-js-client, and so that the react-native devs can see that it has some actual effects on other projects :)

This has been fixed in react-native for a while now.


problem query builder, spaces in field name

Hi,
There seems to be a problem with the query builder. I do this:
Array
(
    [date] => 2012-01-03
    [Test] => 1.232452342809917355
    [Test XL] => 1.3423525
)

$this->db->insert('testing', $data);

will produce:

INSERT INTO `testing` (`date`, `Test`, `Test` `XL`) VALUES ('2012-01-03', 1.232452342809917355, 1.3423525)

It seems to be escaping spaces?

Hi @narfbg, in case of "insert" maybe the query builder should not escape the spaces within a field name? I'm not sure if some RDBMS support aliased field in INSERT statements or if there are other downsides.


ENH: Added QR solver using QR decomposition

This is a method for solving linear systems using QR factorization and back substitution. I found no solvers like this in numpy or scipy so when I build it I thought it might help others to have.

Reference issue
No solver if the matrix is m by n
What does this implement/fix?
It adds a QR decomposition solver using back substitution.
Additional information
I am still going through the contribution docs to make sure everything is okay. Let me know if I did something wrong. My commit message was wrong; it did not have a prefix. I hope that is okay.

Hi @Tsangares thanks for the PR. If you use scipy.linalg.lstsq with driver gelsy, gels it does what you are computing here for the general case. There are multiple steps you have that will not lead to an acceptable solution namely, first using a matrix inverse which is a no-go (it should use at least linalg.solve but then you don't need QR composition) and also matrix_rank which uses an SVD internally hence increasing complexity way above acceptable levels from a solver. Catching the correct number of zero rows is also a very nontrivial step which these low level routines provide already.
Alternatively if you want to use specifically QR factorization then you can use geqrf and work from there via calling trtrs. See https://stackoverflow.com/questions/21970510/solving-a-linear-system-with-lapacks-dgeqrf for an example. In summary, we also provide these low level LAPACK functions for individuals to cook up their own chain of linear algebra steps in an efficient manner. See https://docs.scipy.org/doc/scipy/reference/linalg.lapack.html for the list and let us know if you are missing any.

Thank you for your quick reply. I realize I titled this as a solution to non-square matrices, but I wrote this code originally when solving a system where all the coefficients are integers. All the lstsq methods seem to give a numerical result through optimization rather than an algebraic one. Here is what one of the a lstsq solutions looks like as an example using, gelsd, gelsy, gelss or dgels:

Here is using the QR-Decomp solver:

The QR-decomp find an algebraic or close solution given A is nxm. You can see from the last plot the solution at the top does not use all the rows in the matrix and results in integer coefficients. This allows me to further decompose the system with analysis. I do use the inbuilt QR decomp package, scipy.linalg.qr, from scipy which should be fast. Should I switch to implementing the LAPACK DORMQR?
I switched the np.linalg.inv for the linalg.solve. I am looking how to get the permutation matrix. I might be able to find the rank from the QR decomp, would that be sufficient or is this still not quick enough solver?

IIUC
The lapack functions like gelsy compute a minimum norm solution (similar to using pinv)
This solution is not "sparse" setting redundant parameters to zero.
IIUC, this is then the same or similar problem that we have with rank deficient design matrices in linear regression.
statsmodels and sklearn use pinv, Stata and R drop columns using some pivoting QR, i.e. set those coefficients to zero.
I guess it's only relevant in underdetermined systems, otherwise the LS solution is unique.

@josef-pkt I switched it for scipy.linalg.solve in #51e7bcded3851df7c2abf4366495ab746efc00b4

You can certainly do what you are doing but this is not a generic solver to be included in SciPy for reasons I mentioned above. One is that it is not really a solver but a script that performs factorization and rank selection and solving via the regular gesv hence discarding the structure of R and orthogonalilty of Q.
What you have in mind goes by the name rank-revealing QR factorizations. A standard QR factorization won't cut it. And in fact it is highly nontrivial. Note that it should work for all cases and not some integer entry matrices to be included in SciPy namespace.

through optimization rather than an algebraic one

It is still algebraic but comes with the additional property of being the minimum norm solution.

@ilayn Isn't the pivoting QR rank revealing with a cutoff on the diagonal elements of R?
I was playing with this recently, but didn't like much which columns were set to zero, i.e. the pivoting, permutation result. I have no intuition what would be dropped in this case.
(statsmodels will eventually be forced to add something like this for OLS because R and Stata users want it. Currently still undecided how to add it.)

No column pivoting QR (such DGEQP3 in LAPACK) is an alternative to rank revealing QR but they are not still water tight. I don't quite understand what the use case is could you cook up something? Why QR specifically and not LU or SVD?

OLS in statsmodels and linearregression in sklearn use svd/pinv. However that gives us the minimum norm solution if the system is underdetermined.
Most users would prefer setting some parameters to zero instead of the minimum norm solution.
Our case for this is: A matrix has more rows than columns, so would be overdetermined (LS solution) if column rank is full.
The perfect collinearity case is if some columns are linear combinations, i.e. no full column rank.
(I can try to find the examples that I used for pivoting QR, after cooking and dinner)

here's a baby example that I had used to look at pivoting qr
from scipy import linalg
a = np.random.randn(10, 4)
a[:, 2] = a[:, :2].sum(1)
a[:, 3] = a[:, :2].sum(1) + 1e-10 * a[:, 3]
q, r, p = linalg.qr(a, mode='economic', pivoting=True)
q, r, p

np.diag(r)
array([ 4.94094427e+00, -1.73703024e+00, -2.76238683e-10,  9.34178911e-16])

@josef-pkt What are you looking for? Maybe I can help.

@Tsangares  decision for statsmodels in how to add this and which version is still open.
We have a similar PR https://github.com/statsmodels/statsmodels/pull/6935
There are still many open design decisions how to add this to statsmodels, and, personally, I prefer the pinv minimum norm solution.
So I have not pushed for it yet, in spite of the frequent user requests.
However the code here is useful to us, except that I would base the cutoff based on diag(r) instead of svd matrix rank.
(We need more than just the solution of the QR solve, because we also need standard errors. So, statsmodels is not directly using the scipy or numpy linalg functions that throw away some of the needed intermediate computations. e.g. our pinv used in ols and other linear models keeps also singular values  https://github.com/statsmodels/statsmodels/blob/main/statsmodels/tools/tools.py#L255)

The sparse solution is also very desirable for compressed sensing and for some other fields. But by the way finding the sparsest solution for underdetermined systems is NP-hard.
Folks use basis pursuits and other techniques that I'm not very familiar with through L1 optimization instead of L2 like SVD based methods give (actually the problem is an L0 problem). I haven't checked the literature for that for some time now. But I think randomized QR pivoting is the hot take.
What I do remember is that column pivoting is reported as much less reliable than SVD and cost-wise it is not that far off from SVD. In fact, if you have integer systems I'd even consider solving them in a symbolic fashion with exact arithmetic.
But obviously, if you need it, you should do it. For SciPy I think a regular QR -> truncate -> solve_triangular + @ Q.T is a valid solution. I think it doesn't warrant for a complete new function in the public API because it is not general enough in my opinion (loosely held). And also truncation tolerance is tricky so if you would leave it to user then this is pretty much a custom script.

@josef-pkt I see you dislike how the permutation matrix dictates the solution as there are other solutions. I have been trying to find a solution set in this gist here but to no particular avail. Although, its a nice template if you want to mess with this QR.
What is this pinv minimal norm?
@ilayn I remove the inv and the call to matrix_rank so its just using QR decomposition with a pivot.
I see what you mean about this method being a specific method. Although, this is not the first time I have come across needing a solution like this and matlab and other platforms do have it.
I am happy to help though to find an optimal solution (no pun intended).

I am still trying to understand what the property of this solution is. Or what it is guaranteeing if compared to lstsq.

matlab and other platforms do have it.

Which command in matlab do you have in mind? Maybe that would clarify more things for me. Note that matlab move away from geqrf to geqrt very recently hence things might have changed.

I am still trying to understand what the property of this solution is. Or what it is guaranteeing if compared to lstsq.

matlab and other platforms do have it.

Which command in matlab do you have in mind? Maybe that would clarify more things for me. Note that matlab move away from geqrf to geqrt very recently hence things might have changed.

I am thinking rref then using the pivot to find a solution in a quotient space:
function B = rrefmodp(A, p)

%rrefmodp -- reduced row echelon form (mod p)
%   B = rrefmodp(A,p)
%
%[VdS 2012-aug-2]

%% compile the inverse look-up table.
I = zeros(1,p-1);
Ma = zeros(1,p-1);
for a = (1: p-1)
    Ma = mod(Ma+(1:p-1), p);
    I(a) = find(Ma == 1);
end

%% normalise A to take values in (0:p-1)
A = int32(A);
A = mod(A,p);

[m,n] = size(A);

%% main loop

% set pointers to next pivot
a = 1;
b = 1;

% row permutation
P = (1:m);

while ((a <= m) & (b <= n))
    % if next entry is zero...
    if (A(P(a),b) == 0)
        nzb = find(A(P(a+1:end),b));

       % if column is empty, advance column
       if isempty(nzb)
           b=b+1;
           continue
       end

       % else switch rows

       a2 = a + nzb(1);
       P([a a2]) = P([a2 a]);
    end

    % normalise row
    A(P(a), (b+1:end)) = mod(A(P(a), (b+1:end)) * I(A(P(a),b)), p);
    A(P(a), b) = 1;

    % clear remaining rows
    nzb_log = logical(A(:,b));
    nzb_log(P(a)) = 0;

    nzb = find(nzb_log);
    for c = 1: length(nzb)
        A(nzb(c), (b+1: end)) = A(nzb(c), (b+1: end)) ...
                                - (A(nzb(c),b) * A(P(a), (b+1:end)));
        A(nzb(c), (b+1: end)) = mod( A(nzb(c), (b+1: end)), p);
    end
    A(nzb_log, b) = 0;

    a = a + 1;
    b = b + 1;
end

B = A(P,:);

return

Thanks for the pr @Tsangares! I am think consensus here is we probably won't move forward with this but thanks for your contribution regardless

Thanks for the pr @Tsangares! I am think consensus here is we probably won't move forward with this but thanks for your contribution regardless

Hey, what did you all decide on the solver? Or is it still pending?


Add progress bar to refutation operations since they take a long time to run

Suggested by @sjgenco in #367
This would require

usage of tqdm at the appropriate places in the loop for refutation functions.
Adding tqdm as a requirement for DoWhy.

I'll start on this.

Okay, I've finished adding the progress bars to the refuters themselves. Now, I'm thinking about how to include options to silence them when not needed. I'm thinking to add a keyword argument to CausalRefuter.refute_estimate (like "disable_progress_bar" or smth). Then I probably also need to modify CausalModel.refute_estimate to have this argument also, so that users can silence the progress bars even if they aren't using the refuter object directly.
I will just do this if that works.

yes, that sounds good @leo-ware
In the spirit of avoiding double negatives, you may consider show_progress_bar={True/False} (True by default) instead of disable_progress_bar.
In addition, you can add any additional libraries used to the requirements.txt file.

I would be willing to work on this, we can add this to the estimator as well.

thanks, great to hear @yemaedahrav.  If you have any questions as you start implementing it, you can ping on the #refutations channel on Discord.

I have implemented this with the show_progress_bar={True/False} option. I have made the commit here. Once the other pull request is closed, I will create another PR for this.

Any updates on this?

I guess my PR https://github.com/py-why/dowhy/pull/567 addressed this, this issue can be closed


ksp crash

need help

This is a Windows Unity error dump file. It has nothing to do with KSCrash.


Container log improvements (2/n)

Ideas for improving container logs in the Uffizzi UI:

Add timestamps (maybe have on/off option)
Enable expand/collapse logs
Option to interlace logs of all containers in a deployment

Adding timestamps will require an additional option on the controller (on its existing log endpoint.)


What does "do not reimplement chaining" mean?

The first two examples are good because they provide reasonable alternatives to using the line break. But the third, I'm not sure what it means. How is the programming "implementing" chaining? Can we just suggest a Pythonic alternative instead?

Oh, thanks for this question!
I use several other languages and they all have some kind of chaining (or piping).
Like, js has:
some
   .first()
   .second()
   .finalize()

And elixir has:
some
|> first()
|> second()
|> finalize()

But, python is not suited for this kind of chaining. Instead I use this indentation:
some.first(
   param1, param2,
).second(
   keyword=value,
).finalize()

It allows me not to use \ to break lines. On the other hand when I have calls without any params: I ask myself if design is good enough. Because it looks and feels unpythonic.
I hope this illustrates my idea well enough! 👍

Thanks, this makes sense. I think the wording is just odd. Maybe instead of "do not reimplement chaining" it should just be "do not use for method chaining" and provide the alternative formatting you've given here.

I agree, this will be way more clear. Do you want to send a PR?


Addresses several minor warning messages during the build

What does this implement/fix? Explain your changes.
I compiled using clang and Python3. It's possible that neither are the default for other users, so I saw a couple of warning messages that looked easy to fix.
This includes two commits:

Close open file handles during build set-up (a6e8fa9), which addresses several "ResourceWarning:
unclosed file" when building under Python3
Address minor compiler warnings (af9a4fd), which addresses several trivial warning messages under clang.

Thanks Dan


Rename Generator

Description
This is a draft and a placeholder for what is to be added!
Comments are welcomed in the meantime.
What looks like the rename fonctionnality?

First the rename only work for the ddd librairies!
It has both a project selector and a rename input
Depending on the project we decide how to rename:
Domain: It moves all the libs in the domain to the new domain
Else: It renames only the lib to change name
Project JSON adapted accordingly
From:

To:

WHAT IS LEFT
Integrate a way to adapt config within the .eslint #30
Adding test
Refactors within the DDD Class
Fixes #10
Thank you for contributing to our NX-Generatorz repo!
:rocket:(づ｡◕‿‿◕｡)づ:rocket:

@MeatCow @MeatCow @MeatCow @MeatCow @MeatCow @MeatCow

Beautiful


Is there any option to crop selected image ?

Do we have option to crop selected image.

You can use other awesome libraries to achieve that once you have an image with you. It doesn't make sense to add crop functionality to this library when there are other great libraries which are doing that already. Sorry.


[SPARK-34011][SQL][3.1][3.0] Refresh cache in ALTER TABLE .. RENAME TO PARTITION

What changes were proposed in this pull request?

Invoke refreshTable() from AlterTableRenamePartitionCommand.run() after partitions renaming. In particular, this re-creates the cache associated with the modified table.
Refresh the cache associated with tables from v2 table catalogs in the ALTER TABLE .. RENAME TO PARTITION command.

Why are the changes needed?
This fixes the issues portrayed by the example:
spark-sql> CREATE TABLE tbl1 (col0 int, part0 int) USING parquet PARTITIONED BY (part0);
spark-sql> INSERT INTO tbl1 PARTITION (part0=0) SELECT 0;
spark-sql> INSERT INTO tbl1 PARTITION (part0=1) SELECT 1;
spark-sql> CACHE TABLE tbl1;
spark-sql> SELECT * FROM tbl1;
0	0
1	1
spark-sql> ALTER TABLE tbl1 PARTITION (part0=0) RENAME TO PARTITION (part=2);
spark-sql> SELECT * FROM tbl1;
0	0
1	1

The last query must not return 0	2 since 0  0 was renamed by previous command.
Does this PR introduce any user-facing change?
Yes. After the changes for the example above:
...
spark-sql> ALTER TABLE tbl1 PARTITION (part=0) RENAME TO PARTITION (part=2);
spark-sql> SELECT * FROM tbl1;
0	2
1	1

How was this patch tested?
By running the affected test suite:
$ build/sbt -Phive-2.3 -Phive-thriftserver "test:testOnly *CachedTableSuite"

Authored-by: Max Gekk<EMAIL_ADDRESS>Signed-off-by: HyukjinKwon<EMAIL_ADDRESS>(cherry picked from commit b77d11dfd942ee2164dde2f5c25c6aaed65c444c)
Signed-off-by: Max Gekk<EMAIL_ADDRESS>

@HyukjinKwon This is a backport of https://github.com/apache/spark/pull/31044 . I kept only v1 changes because v2 is not supported in 3.1.

@HyukjinKwon This is a backport of https://github.com/apache/spark/pull/31044 . I kept only v1 changes because v2 is not supported in 3.1.

Test build #133723 has started for PR 31060 at commit 42191fb.

Test build #133723 has started for PR 31060 at commit 42191fb.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38311/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38311/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38311/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38311/

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

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

Test build #133723 has finished for PR 31060 at commit 42191fb.

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

Test build #133723 has finished for PR 31060 at commit 42191fb.

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

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

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


Let adapter.add find connected socket

When a socket connects, it joins its own room, resulting in a call to adapter.add.
The adapter in turn should be able to find the socket by id.

Makes sense.

A comment would be in order considering the big semantic change a line change produced :D

Added in PR https://github.com/Automattic/socket.io/pull/2081


vGICv3 potential Issue and Improvement

@josecm @sandro2pinto
I was reading the code, and got the impression the Underflow condition of the Maintenance IRQ is not being used. Instead it is using this one:

ICH_HCR_EL2:

ICH_MISR_EL2:

Does this mean we are having a VM exit per EOId vIRQ which might be ineficient.
Can we improve it by dynamically changing the settings of ICH_HCR_EL2 with U bit ?
Example: Max 4 LRs supported.

Case1: When we have up to 4 vIRQs injected, we have the U bit cleared. No traps!

Case2: If there are more than 4 vIRQs, example 5 vIRQs. We add the 5th vIRQ to a sw pending list and set the U bit. This will trap when 3 vIRQs of the 4 LRs get deactivated. The hardware will automatically generate a maintenance IRQ to be possible for the hypervisor to inject the 5th vIRQ in a LR free room.

What do you think? Would that reduce the number of hypervisor traps?

We try to keep at least one pending interrupt in the LRs so an active one is spilled. In the case the guest EOIs it next, we need to get the maintenance interrupt to deactivate it.

I see, the spilled vIRQ only happens in overflow case. That's correct. It happened to have a old revision of the code from a year ago.  LGTM ;)