How to mimic Postman setting "Add authorization data to Request Body/Request URL"

Description:
Hi, I am using POSTMAN to execute a  GET OAuth1 request. It works nicely in Postman
I am now  trying to execute this call using OAS, but cannot achieve this.
I fail to mimic the "Add authorization data to Request Body/Request URL" setting you can set in postman. The request only works if i use that setting. See here

When i use this option, the authorization data (parameters) are added to the Request URL as query parameter.
Is there an option to do this in OAS?
Thanks a lot
OAuth Provider? (Twitter, Github, ..):
Woocommerce
OAuth Version:

[x ] Version 1
[ ] Version 2

OS (Please fill the version) :

[x] iOS :
[ ] OSX :
[ ] TVOS :
[ ] WatchOS  :

Installation method:

[ ] Carthage
[ ] CocoaPods
[x ] Swift Package Manager
[ ] Manually

Library version:

[ ] head
[x ] v2.0.0
[ ] v1.4.1
[ ] v1.2.1
[ ] v1.2 (Swift 4.0)
[ ] v1.0.0
[ ] v0.6
[ ] other: (Please fill in the version you are using.)

Xcode version:

[ ] 11.x (Swift 5.1)

[ x] 10.x (Swift 5.0)

[ ] 10.x (Swift 4.1)

[ ] 9.3 (Swift 4.1)

[ ] 9.0 (Swift 4.0)

[ ] other: (Please fill in the version you are using.)

[ ] objective c

Hi, sorry for bothering. Got it. Thanks a lot, great framework!


Chart install page for monitoring shows [object Object]

Once this issue is fixed:https://github.com/rancher/dashboard/issues/5248 you'll see this:
Go to Cluster Tools -> V2 Monitoring install
The Version select input show '[object Object]' - see below:

This should be tested alongside #5248


Macronize support non-integer nodes

Before posting a feature request

[X] I have searched existing GitHub issues and documentation to make sure the feature request and relevant resolutions do not already exist.

Feature details
It would be useful to extend the capabilities of the EGraph Macronize function to non-$\mathbb{Z}^3$ nodes. Currently, there is an unexpected behaviour of this function for certain egraphs (see code below)
Implementation
Not at the moment
Additional context
To reproduce undesired behaviour, run the following:
EG = EGraph([((-0.2519, 0.436, 0.0), (-0.4875, 0.0045, 0.0)), ((-0.2519, 0.436, 0.0), (0.2433, 0.4243, 0.0)), ((-0.2519, 0.436, 0.0), (-0.2519, 0.436, 1.0)), ((0.5017, -0.0012, 0.0), (0.2433, 0.4243, 0.0)), ((0.5017, -0.0012, 0.0), (0.2449, -0.4258, 0.0)), ((0.5017, -0.0012, 0.0), (0.5017, -0.0012, 1.0)), ((-0.2516, -0.4327, 0.0), (-0.4875, 0.0045, 0.0)), ((-0.2516, -0.4327, 0.0), (0.2449, -0.4258, 0.0)), ((-0.2516, -0.4327, 0.0), (-0.2516, -0.4327, 1.0)), ((0.0032, -0.0051, 0.0), (-0.4875, 0.0045, 0.0)), ((0.0032, -0.0051, 0.0), (0.2433, 0.4243, 0.0)), ((0.0032, -0.0051, 0.0), (0.2449, -0.4258, 0.0)), ((0.0032, -0.0051, 0.0), (0.0032, -0.0051, 1.0)), ((-1.0, 0.0024, 0.0), (-0.4875, 0.0045, 0.0)), ((-1.0, 0.0024, 0.0), (-1.0, 0.0024, 1.0)), ((0.4967, 0.8702, 0.0), (0.2433, 0.4243, 0.0)), ((0.4967, 0.8702, 0.0), (0.4967, 0.8702, 1.0)), ((0.5012, -0.8726, 0.0), (0.2449, -0.4258, 0.0)), ((0.5012, -0.8726, 0.0), (0.5012, -0.8726, 1.0)), ((-0.2519, 0.436, 1.0), (-0.4632, 0.0009, 1.0)), ((-0.2519, 0.436, 1.0), (0.2333, 0.4009, 1.0)), ((-0.2519, 0.436, 1.0), (-0.2519, 0.436, 2.0)), ((0.5017, -0.0012, 1.0), (0.2333, 0.4009, 1.0)), ((0.5017, -0.0012, 1.0), (0.2332, -0.4057, 1.0)), ((0.5017, -0.0012, 1.0), (0.5017, -0.0012, 2.0)), ((-0.2516, -0.4327, 1.0), (-0.4632, 0.0009, 1.0)), ((-0.2516, -0.4327, 1.0), (0.2332, -0.4057, 1.0)), ((-0.2516, -0.4327, 1.0), (-0.2516, -0.4327, 2.0)), ((0.0032, -0.0051, 1.0), (-0.4632, 0.0009, 1.0)), ((0.0032, -0.0051, 1.0), (0.2333, 0.4009, 1.0)), ((0.0032, -0.0051, 1.0), (0.2332, -0.4057, 1.0)), ((0.0032, -0.0051, 1.0), (0.0032, -0.0051, 2.0)), ((-1.0, 0.0024, 1.0), (-0.4632, 0.0009, 1.0)), ((-1.0, 0.0024, 1.0), (-1.0, 0.0024, 2.0)), ((0.4967, 0.8702, 1.0), (0.2333, 0.4009, 1.0)), ((0.4967, 0.8702, 1.0), (0.4967, 0.8702, 2.0)), ((0.5012, -0.8726, 1.0), (0.2332, -0.4057, 1.0)), ((0.5012, -0.8726, 1.0), (0.5012, -0.8726, 2.0)), ((-0.2519, 0.436, 2.0), (-0.4875, 0.0045, 2.0)), ((-0.2519, 0.436, 2.0), (0.2433, 0.4243, 2.0)), ((0.5017, -0.0012, 2.0), (0.2433, 0.4243, 2.0)), ((0.5017, -0.0012, 2.0), (0.2449, -0.4258, 2.0)), ((-0.2516, -0.4327, 2.0), (-0.4875, 0.0045, 2.0)), ((-0.2516, -0.4327, 2.0), (0.2449, -0.4258, 2.0)), ((0.0032, -0.0051, 2.0), (-0.4875, 0.0045, 2.0)), ((0.0032, -0.0051, 2.0), (0.2433, 0.4243, 2.0)), ((0.0032, -0.0051, 2.0), (0.2449, -0.4258, 2.0)), ((-1.0, 0.0024, 2.0), (-0.4875, 0.0045, 2.0)), ((0.4967, 0.8702, 2.0), (0.2433, 0.4243, 2.0)), ((0.5012, -0.8726, 2.0), (0.2449, -0.4258, 2.0))])
print(EG.number_of_nodes()) # it's 30
MEG = EG.macronize(True)
print(MEG.number_of_nodes()) # gives 121 as opposed to 120.

How important would you say this feature is?
2: Somewhat important. Needed this quarter.

Any volunteers? @BestQuark, are you planning to bravely go for this as the next task yourself?

Hi @nariman87, not yet. I am still working in other tasks 😅


interfaces: interface_configure($reload = true) and rc.linkup(start) are counter-productive

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
Judging from #6671 and a couple of logs I got when Netmap is involved bringing devices down when starting up restarting connectivity restarting all services (despite nothing being available yet) and then doing this for each interface is wasting a lot of computing time and doesn't help to bring the system back into a workable state. Most of the time IPv6 is the one that fails to reload properly because if this (especially radvd on the LAN side breaking tracking).
To Reproduce
Suricata on IPS mode for WAN on startup brings down dhcp6c and restarts it, but blocks the main IPv6 renew event from going through correctly. On LAN it's slightly better, but tracking can break (radvd starting in the wrong spot in rc.linkup). PPPoE brings even more fun into the mix but I only have logs and nothing concrete.
Expected behavior
Ideally rc.linkup should not disrupt operation, but I can see this being an unfixable situation.
Describe alternatives you considered
Reducing the reload behaviour on rc.linkup and being able to batch the reload of attached services (see $reload = true switch)
Screenshots
N/A
Relevant log files
Private submissions by multiple users.
Additional context
Seems to have gotten worse since 23.7, but code has always been problematic since fork and not much has changed on it.
Environment
23.7.x

I think the root cause for most of this madness are services binding on non static addresses. The boot issue might be fixable, but pulling the plug on an interface with many vlans will likely still be problematic (and caused by the same thing).
Maybe the best first step is collecting the services which still depend on this behavior and assess if a common workaround can be identified (at least for the services we offer).

Pressing issue with static addresses is fixed hereby. Another follow up ticket will be published soon.


TODO: Module I/O

Since this module wraps all image capture and detection - it should spit out a simple list of detected objects for consumption by other node-red modules, e.g.
[
  { key: "person", value: 2 }
  { key: "cellphone", value: 2 }
]

@bleggett - So goal is to produce a simple list for consumption by other future node-red modules.  As background, here's an example response currently produced for three bananas.
[{
    "detections": [
        {
            "bbox": [
                38,
                608,
                529,
                1003
            ],
            "class": "banana",
            "score": 0.9932200908660889
        },
        {
            "bbox": [
                255,
                332,
                768,
                703
            ],
            "class": "banana",
            "score": 0.9972244501113892
        },
        {
            "bbox": [
                55,
                52,
                566,
                443
            ],
            "class": "banana",
            "score": 0.998857855796814
        }
    ],
    "image": "/9j/4AAQSkZJRgABAQAAAQABAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRofHh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwhMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAARCAQAAwADASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDo5lAC5PV3X8xVNiwtCckFX29ff/69XrvAcLnGJgc/UVSJ3K6n+Lb39xXGdZsREeSh/wBjpiqYz/ZsyYyV3gfnmrI/1MYBzgGq+AYLvb6t/KmIHibGDjZskY/Tg1NcMz3EM2QMk9O1R35K6bFt4LIQf++TgUkxKx2bngNwR+Gf...",
    "things": [
        {
            "thing": "banana"
        },
        {
            "thing": "banana"
        },
        {
            "thing": "banana"
        }
    ]
}

Along with the original detections member produced with all the detail, had added the rendered image member with bounded boxes and the things member in particular for consumption of the Node-RED inventory flow.  In particular the things member lists each thing instance separately so the inventory flow subtraction/difference node could perform this difference.  It currently requires this form to do an "individual" difference of things/items.
We could add another member to the existing response to further summarize the objects as you've listed.  Had shifted to the terms thing and count as a more user friendly terms.  If we want to add this, would we want something like:
{
  "detections": ...,
  "image": ...,
  "things": ...,
  "thing-counts": {
    [
      { "thing": "person", "count": 2 },
      { "thing": "cellphone", "count": 2 }
    ]
  }
}

Thoughts?

@jbondpk That makes sense - there can be the simple, top level summary fields, and then a details property at the top level that expands into the full result set you have there.


Planned puzzles masterlist

If you would like to see a puzzle added that is not listed here, add a comment on this issue.
At this time, I am only accepting puzzles that are ≤5D and can be built and simulated using current features. That means:

Euclidean N-dimensional space
only flat cuts
no deleted pieces
only doctrinaire turns
no multi-core

I will check off puzzles in this list once their production-ready implementation is merged into the v2.0 branch.
Must-have for v2.0
This is the list of puzzles that I know people will want in v2.0 and have minimal complications. Namely: they are all doctrinaire, have few enough axes that we can reasonably name all the twists, and exist in 3D or 4D.
Nearly all of these are waiting on #53
3D

[x] N^3 Rubik's Cube generator

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

[ ] AxBxC cuboid generator

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

[x] N-gon face-turning prism generator (at various layers of n-gon and various layers of prism)

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

[x] N-layer Skewb generator

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

[x] N-layer Megaminx generator

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

[ ] N-layer Pyraminx generator

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

[ ] N-layer Halpern-Meier Tetrahedron generator

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

[x] N-layer Face-Turning Octahedron generator

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

[x] Dino Cube

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

[x] Compy Cube (pronounced like "chompy cube")

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

4D

[x] N^4 Rubik's Hypercube generator

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

[ ] AxBxCxD hypercuboid generator

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

[ ] {A}x{B} duoprism generator

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

[ ] N-layer simplex generator (at various cut depths)

[ ] Piece types
[ ] Colors (order + defaults)
[ ] Notation
[ ] Twist gizmos
[ ] Twist directions
[ ] Axis order
[ ] Puzzle name
[ ] Metadata & tags

Shortlist
These puzzles will be possible to implement in v2.0 but have lower priority. They will be added as they are implemented.
3D

[x] Deep-cut face-turning dodecahedra

[x] Pyraminx Crystal
[x] Starminx
[x] Curvy Starminx
[x] N-layer Pentultimate generator

[ ] Vertex-turning icosahedra

[ ] N-layer Tutt's Icosaminx generator
[ ] N-layer Icosamate generator

[ ] Regular Astrominx

[ ] Dino Dodecahedron (also called Rediminx)
[ ] N-layer Tuttminx generator
[ ] N-layer Trajber's Octahedron generator
[ ] N-layer (name TBD) Vertex-Turning Octahedron
[ ] N-layer Dino Octa generator
[ ] F-Skewb

4D

[ ] Megaminx prism generator (at various layers of megaminx and various layers of prism)
[x] Facet-Turning 24-cell
[ ] N-layer Trajber's 16-cell (vertex-turning; shapemod of 3^4) generator
[ ] Ridge-Turning Hypercube
[ ] Demi N^4 generator
[ ] Facet-Turning 120-cell

5D
These are waiting on #54

[ ] N^5 Rubik's Hypercube
[ ] AxBxCxDxE hypercuboid generator

Deeper face-turning dodecahedra: pyraminx crystal, (curvy) starminx, (master) pentultimate

N-layer skewb generator

"Trojber's" 16 cell (3^4 shape mod, vertex turning 16 cell)

120-cell seems like a gaping omission. Or are its 120 grips too much for "few enough axes that we can reasonably name all the twists"?

Hypercuboids are omitted for 4d for some reason when they are listed for 3 and 5d

Good point! I've added FT 120 to the shortlist

N-layer icosamate/astrominx generator
Facet-turning 120-cell

If we have FTO we might as well have cubeoctahedron as well (but that may be slightly too obscure?)

I'm not sure it needs an Astrominx generator in that sense. What I meant was the mf8 Astrominx, also called Regular Astrominx, which is the 3-layer version of the Icosamate.

Tuttminx generator

Facet-turning 24 cell for the record

antiprism generator

F-skewb (could be made N-layer, as far I know that has never been done)
Cheese (prisms where the equatorial axes' cuts pass through the origin)
N-layer This octahedron generator
Rediminx/Dino Dodecahedron (also known as Starminx I but sometimes Starminx I is the face-turning one)

Postponing Cheese because we want a general cheese generator, and some cheeses jumble. (e.g., octagonal 2-layer cheese has 2^3 + 45-degree turns)

https://alpha.twizzle.net/explore/?puzzle-description=d+v+0.74 AJ Bauhinia II

https://twistypuzzles.com/app/museum/museum_showitem.php?pkey=3784 https://youtu.be/gZRgOm0U3Wg?si=MHTzjssNbvCZTEl2 Generator (tho as previously discussed, I am aware that puzzles like this would not be feasible in 2.0)

I've added checkboxes for the tasks remaining for all the must-have puzzles & generators. Notation, twists directions, and metadata & tags require more HSC features, but the rest can be checked off before then. Once a puzzle is totally done, its version in the Lua file should be set to 1.0.0.

Hi,
Any progress on Facet-Turning 24-cell? I should put it this way: I would like to help to build 24-cell puzzles, but I wonder if you already have any plans on the implementation, or any specific directions. If so, then I would be happy to follow them.
For now, I don't have a clear picture on how to do it, but I have read through wikipedia: 24-cell and 24-cell related threads in MC4D Archive, so at least the geometry is not alien to me.
Finally, some background of me:

A simple PR to this software was accepted.
I got interest in hypercubing (but not yet speed solving, not sure if I will ever get into that realm), so I started a project back in 2022/Q3, in which I

Solved 2x2x2x2 using MC4D
Created 4D skewb (vertex-turned hypercube) from pure web GL, and solved it.

I wasn't familiar with Rust when I sent the PR, but I just finished a project that implements a boardgame, so it is not weird to me now. Still, this project uses some features that are beyond my current knowledge, but I think they will be understandable sooner or later.

@NonerKao I'm glad you'd like to contribute! I have excellent news: the FT 24-cell is already implemented, and you can play with it on the v2.0 branch, although there's no way to scramble or save progress so I wouldn't recommend solving it.
All the puzzles are written in Lua. The API documentation is here, and should be very nearly up-to-date. The FT 24-cell is already implemented in this file. Here's what's left to be done:

Name for each cell. The code can be generated using the built-in "Puzzles → Dev Tools → Lua Generator" then "Load Orbit" and select the orbit of 24 colors, then rename and reorder them. Ideally we want prefix-free names (e.g., if there is a color named FR, then there should not be a color named F).
Color system with default colors. See lua/symmetries/hypercubic.lua for an example. Relevant docs are here and here. The existing puzzle already has some colors assigned, but it's using an older format that will break when reordering cells.
Piece type names. There is a standard for these names that @milojacquet has developed, but even just isolating each piece type would be helpful. I plan to add tools in the program for identifying piece types, but for now you have to do it manually. See ft_cubes.lua for an example.
Tags (properties like "cell-turning," "shallow-cut," "24-cell," "doctrinaire"). I'm currently implement this in Rust and expect it to be done within a week or two.
Twist notation. This is not yet implemented in Rust, but I will do it soon.

1, 2, and 3 are things you can do now if you would like to. 4 and 5 are things I will do as part of updating all the puzzle files once the Rust side is complete. Piece types in particular are something that almost all of the current puzzles are missing, and would be very helpful. The relevant docs are here.
Most of the work at this stage in development is in Rust, and I have strong feelings about how it should be implemented. The good news is that individual puzzles are very straightforward to implement, and I plan to add more tools to make it as easy as possible. The hardest part is naming the colors, twist axes, and piece types.


Use Nerdbank.GitVersioning

⚠ This pull request depends on #299, and will be substantially simplified once that PR is merged. ⚠
Overview
This change uses Nerdbank.GitVersioning to automatically version the assemblies and packages as work progresses in the repository.
Deployment
Deploying a release to NuGet is much simpler after this change is applied. After setting up an environment (see next part), here are the steps to release a build:

After merging a pull request to master, locate the AppVeyor build you want to release
Open the Image: Visual Studio 2017; Configuration: Release job for the build (this is the only job containing the full set of correct artifacts for release)
At the top of the AppVeyor page, click Deploy
Select the NuGet (coverlet) environment and deploy
After deployment succeeds, create and push a tag in the repository

Creating the environment
💡 This is a one-time setup process, after which you can use the environment any time you want to make a new coverlet release.

Log in to AppVeyor and go to the Environments tab (at the top, next to Projects)
Create a new environment
Select NuGet as the deployment provider
In your NuGet profile, create a new API key, and scope the key to coverlet.*
Back in AppVeyor environment setup apply the following:

Environment name: NuGet (coverlet)
API key: Copied from step (4)

Click Add environment to create the environment

@tonerdo This is now rebased. As you can see, the builds produced by each AppVeyor build now have a unique version number, making it tremendously easier to prepare/manage releases. You will only rarely need to update version numbers in the project, and when you do, it will be limited to changes in version.json.

/cc @AArnott in case he wants to put a copy of the instructions above somewhere for future users. 😄

I'm torn. The doc looks well written, but it doesn't really have anything to do with NB.GV itself. But maybe as a new AppVeyor-specific suggestions doc linked from https://github.com/AArnott/Nerdbank.GitVersioning/blob/master/doc/cloudbuild.md ?
@sharwell would you be willing to send such a PR

@tonerdo Conflicts are resolved again

Thank you @sharwell, will take a look in a couple

Superseded by #425


required fields mechanism broken for list objects?

I have a file collection with the following collection config:
{
      name: "termine",
      label: "Termine",
      file: "content/termine/_index.md",
      fields: [
        {
         name: "title",
         label: "Titel",
         required: true,
         widget: "string",
        },
        {
          name: "events",
          label: "Termine",
          label_singular: "Termin",
          widget: "list",
          required: false,
          collapsed: true,
          fields: [
            {
              name: "title",
              label: "Bezeichnung",
              widget: "string",
              required: false,
            },
            {
              name: "date",
              label: "Datum/Startdatum",
              widget: "datetime",
              required: false,
              ...DateFormat,
            },
            {
              name: "enddate",
              label: "Enddatum",
              hint: "Für mehrtägige Veanstaltungen, nur sichtbar wenn eingestellt",
              widget: "datetime",
              required: false,
              default: "",
              ...DateFormat,
            },
            {
              name: "location",
              label: "Ort",
              widget: "string",
              required: false,
            },
          ],
        },
      ],
    },

As you can see, every single one of the list fields have required: false set. But still, when trying to add a new list item I get the error message that some required fields in the list are empty when publishing.

Before 3.3.6 it always displayed 'No value' for the list entry summary, so I thought that was the problem, but with 3.3.6 everything looks correct, still not allowing me to publish though.

Same here,
a temporary fix is after you get the error message, refresh the admin page and wait till till the save state is loaded, now you can publish.


[flash_ctrl/dv] flash_ctrl_host_arb behavior around RMA request

I debugged one of the flash_ctrl_host_arb failures in nightly regressions and noticed the following.
The flash_ctrl_host_arb test issues software operations before requesting for RMA.
The hardware behavior for such an operation is to complete the software operation before switching to RMA.
When switching into RMA however, the hardware clears the program and read FIFOs to ensure leftover information does not interfere with subsequent RMA entry.
This specific behavior causes a problem for the test if the operation issued right before RMA were a read. The read completes correctly and deposits all the data into the FIFO.  But before the test has a chance to read out all the data from the FIFO, it is cleared by the RMA entry behavior.
This is actually working as intended.  The RMA sequence wants the operation to gracefully complete, but it does not make any assumption someone will actually empty the FIFO.  We also cannot put such a condition in hardware as that would imply a stalled CPU may prevent entry into RMA, which might be the reason we want to go into RMA to start with.
For now, I've changed the test slightly such that on the last operation before RMA request it only checks "half" of the expected read.  This is still vulnerable to timing and may be flaky, but is more realistic than trying to check all the read conent.

@cindychip
@weicaiyang
FYI


CTD when choosing gem for yellow gem socket

When using the compiled desktop version of the 28. November, i get a crash to desktop(CTD) shortly after choosing a gem for the yellow socket in the Settings tab.
As a workaround i tried to put the gems in the config file. I had success, the additional stats are shown in the left stat window. Unfortunately, simming gear apart from weapons does not work anymore. If i press the button all sim buttons are greyed out but nothing else happens (also no CPU usage). Personal DPS Sim with chosen gear works.
Also, after manually editing the config file, i no longer experience CTDs

Hey, thanks for your feedback! :)
Can you please try to reproduce the issue with the newest version and give us feedback after?
-Sules

Hey, thanks for replying so fast!
i did reproduce the issue withthe newest version with the following steps:
compile new version
settings was not overwritten, so i deleted the gem IDs in settings.json
start sim
choose my gear
choose gems for sockets (8 str, 4 str 4 crit, 4 str 6 sta, relentless)
unmark divine wisdom in talents
choose 2/3 sanctified jugdement
crash
that crash only happens if i do choose gems before
Thanks for looking into that issue!
-Equeslucis

I can sadly not reproduce this.
Can you either post how your settings.json looks like before you start the sim and/or post the stacktrace / error massage?

Sules

settings.zip
i do not know where to find the stracktrace/error message

Is it only happening with the specific gear you select?
So if you dont select your gear and ceep it at default, dose this also happens?
If it dose not happen, it would be great if you could post the gear you are selecting :)

Nope, also happens with other gear.
Also, this time it already crashed when choosing a red gem

Nope, also happens with other gear. Also, this time it already crashed when choosing a red gem

Can you please try to reproduce this issue in the release version?
https://github.com/TheSorm/RetSim/releases/tag/release

Bug does not occur anymore in the release version


Feature/emoji multiple words

Aims to close #10
Changed the translation word check in utils/reactMessage.js by considering an eventual array of words.
The english translation is updated to use whether halloween or pumpkin for the same emoji.
EDIT: sorry I misunderstood "ca", it should be fixed now :+1:

Wow thanks for this one !


36 change pe phone

Closes #36.

Peer educator can change their phone number from the settings screen.

Codecov Report

Merging #99 into develop will decrease coverage by 0.01%.
The diff coverage is 3.17%.

@@            Coverage Diff             @@
##           develop     #99      +/-   ##
==========================================
- Coverage     5.15%   5.14%   -0.02%
==========================================
  Files           64      65       +1
  Lines         6669    6749      +80
==========================================
+ Hits           344     347       +3
- Misses        6325    6402      +77

Impacted Files
Coverage Δ

lib/database/beans/ARTRefillNotDoneReason.dart
7.31% <ø> (ø)
:arrow_up:

lib/screens/EditPatientScreen.dart
0% <ø> (ø)
:arrow_up:

lib/database/DatabaseExporter.dart
0% <ø> (ø)
:arrow_up:

lib/components/RequiredActionContainer.dart
0.97% <ø> (ø)
:arrow_up:

lib/screens/PatientScreen.dart
0.18% <0%> (ø)
:arrow_up:

lib/state/PatientBloc.dart
28.57% <0%> (-4.77%)
:arrow_down:

lib/screens/SettingsScreen.dart
0% <0%> (ø)
:arrow_up:

lib/components/RequiredActionBadge.dart
0% <0%> (ø)
:arrow_up:

lib/utils/VisibleImpactUtils.dart
0.43% <0%> (-0.01%)
:arrow_down:

lib/screens/ARTRefillNotDoneScreen.dart
0% <0%> (ø)
:arrow_up:

... and 5 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 18a409f...a2db598. Read the comment docs.


ORA-01406 fetched column value was truncated

Python: 3.6 64bit
pyodbc: 4.0.21
OS: Windows Server 2016
DB: Oracle 12
driver:

Issue
Hi,
I am using pyodbc with python to fetch some data from oracle database. Just recently, when fetching a relatively big column, I have encountered exception: "ORA-01406 fetched column value was truncated". I have been looking into the issue, everyone says that I need to increase the size of the fetch buffer but I have no idea how to do that. I have looked into pyodbc documentation and there was a cursor method "setoutputsize" which is not supported as they claim, anyway, I have given it a try and used it to alter the output size but the exception persists. Any Idea is appreciated.
Thanks

Also asked on Stack Overflow here.

How big is "relatively big", exactly? What is the datatype?
A quick search reveals the fetch buffer size is configured here: https://docs.oracle.com/database/121/ADFNS/adfns_odbc.htm#BABGBICJ

Closed due to inactivity. Feel free to re-open with current information if necessary.


feat: export text file filesystem plugin

Summary

Please summarize your changes, describing what they are and why they were made.

...
Changelog
- Please write a list of changes

Relevant Issues
Closes #4244
...
Testing
Platforms

Please select any platforms where your changes have been tested.

Desktop

[ ] MacOS
[ ] Linux
[ ] Windows

Mobile

[ ] iOS
[ ] Android

Instructions

Please describe the specific instructions, configurations, and/or test cases necessary to test and verify that your changes work as intended.

...
Checklist

Please tick all of the following boxes that are relevant to your changes.

[ ] I have followed the contribution guidelines for this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or modified tests that prove my changes work as intended
[ ] I have verified that new and existing unit tests pass locally with my changes
[ ] I have verified that my latest changes pass CI workflows for testing and linting
[ ] I have made corresponding changes to the documentation

Android works like a charm 100 champagne
I just have trouble with iOS. Every time I try an export I get this message:

I tried to debug the saveTextFile method but it doesn't run into the break point, so I can't say for sure if this is a plugin problem or not. XCode and Safari log doesn't really show an error or something useful either thinking I will investigate this further.

🕵🏼 Would be nice if we could fix that notification that looks like is missing an argument to display the account alias


AzureCommunicationChat GA Feedback

Addressing some of the comments here: https://github.com/Azure/azure-sdk-for-ios/pull/851
New swiftinterface based off these changes here: https://github.com/Azure/azure-sdk-for-ios/pull/925

[X] Update trouter classes to structs
[X] Add missing docs for public methods
[X] Update Trouter package to beta5 (tested in signaling app)
[X] Review things that are public if they should be internal (IdentifierSerializer is internal)
[X] Review naming consistency - request, options, result
[X] Document M1 support (Added note in README that references #787 )

@tjprescott looks like Smoketest is failing because it can't find latest trouter package - is there anything I need to change in the smoketest example?

Changes look good to me!


[Move devex] Implement more readable crash data (e.g., stack traces)

At this point, the stack trace and related crash data printed upon a failure are not very readable beyond the immediate point of failure. Hopefully we can improve on that.
┌── simple_auction_test ──────
│ error[E11001]: test failure
│     ┌─ ./../../framework/sources/TestScenario.move:252:13
│     │
│ 232 │     fun remove_unique_object<T: key>(scenario: &mut Scenario, signer_address: address): T {
│     │         -------------------- In this function in 0x2::TestScenario
│     ·
│ 252 │             abort(EEMPTY_INVENTORY)
│     │             ^^^^^^^^^^^^^^^^^^^^^^^ Test was not expected to abort but it aborted with 3 here
│
│
│ Call Stack:
│     [0]<PHONE_NUMBER>000000000000000000000000000000::AuctionTests::simple_auction_test
│
│         Code:
│             [117] ImmBorrowLoc(9)
│             [118] Call(11)
│             [119] CopyLoc(17)
│           > [120] CallGeneric(13)
│             [121] StLoc(1)
│             [122] ImmBorrowLoc(1)
│             [123] ImmBorrowField(FieldHandleIndex(0))
│
│         Locals:
│             [0] { { {<PHONE_NUMBER>00000000000000000000000000FACE }, [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 8], 0 }, [], [0, 2, 3, 5, 7, 9, 12, 15] }
│             [1] -
│             [2] -
│             [3] -
│             [4] -
│             [5] -
│             [6]<PHONE_NUMBER>00000000000000000000000000ABBA
│             [7] -
│             [8] -
│             [9]<PHONE_NUMBER>00000000000000000000000000FACE
│             [10]<PHONE_NUMBER>00000000000000000000000000CAFE
│             [11] -
│             [12] -
│             [13] -
│             [14] -
│             [15] -
│             [16]<PHONE_NUMBER>000000000000000000000000000ACE
│             [17] (&) { { {<PHONE_NUMBER>00000000000000000000000000FACE }, [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 8], 0 }, [], [0, 2, 3, 5, 7, 9, 12, 15] }
│             [18] -
│
│
│     [1]<PHONE_NUMBER>000000000000000000000000000002::TestScenario::remove_object<0x0::AuctionTests::SomeItemToSell>
│
│         Code:
│             [3] StLoc(1)
│             [4] MoveLoc(0)
│             [5] MoveLoc(1)
│           > [6] CallGeneric(12)
│             [7] Ret
│
│         Locals:
│             [0] -
│             [1] -
│
│
│ Operand Stack:
│
└──────────────────

IMO we should remove the string stacktrace from VMError and replace it with something like stack_trace: Option<Vec<(Option<ModuleID>, FunctionDefinitionIndex, CodeOffset)>> (probably want a struct here).
Then we can use the source map to point these back to source files

This has been addressed in https://github.com/diem/move/pull/195


Async Create hanging while publishing observable

Consider the following code:
var xs = Observable.Create<Unit>(async o =>
{
    await Task.Delay(10);
    o.OnError(new Exception());
}).Replay().RefCount();

xs.Subscribe(x => Console.WriteLine(x));
xs.Subscribe(x => Console.WriteLine(x), ex => Console.WriteLine(ex.Message));
await xs.DefaultIfEmpty();

The sequence above doesn't throw any exceptions and never completes.
I made the following observations:

Removing the first subscription enables error propagation - exception is thrown in Subscribe context (last line)
Removing .Replay().RefCount() enables error propagation - exception is thrown in Subscribe context (last line)
Removing await Task.Delay(10) enables error propagation - exception is thrown in OnError call (within Create method). Surprisingly, switching two Subscribe methods makes exception thrown at Subscribe context (last line).

That being said, I am asking whether the following issues are by design:

Observable sequence in the above scenario never being completed
The fact that exception is sometimes thrown inside Create method, and other times - at Subscribe context.

If this is by design, what would you recommend as a workaround? How do I publish my sequences so that all of my clients (observers) can safely handle exceptions in this case? Current behavior seems so arbitrary, especially for library writers. It also makes debugging very painful. Please advise.

Hopefully this is the same kind of issue.    It seems that the behaviour when you do Observable.Create(async obs =>  has changed.  As an example, what is the final state of the bools in this code?
bool started = false;
bool message = false;
bool completed = false;
bool disposed = false;
var obs = Observable.Create<bool>(async observer =>
{
    started = true;
    await Task.Delay(1);
    observer.OnNext(true);
    return Disposable.Create(() =>
    {
        disposed = true;
    });
})
var sub = obs.Subscribe(x => message = x, () => completed = true);

Answer is it depends on if you're debugging or not, and how long you wait, but the change is that in 4.1 this observable completes and disposes itself which it didn't before.
I appreciate that this may be bad code for some good reasons, and I've found more sensible ways to do what we're trying to do, but having hunted though the changelogs and searched the docs, I wanted to check whether this was always bad but just happened to work, or whether this is a deliberate change in order to support something else.

When do you expect the bools in the code to be in a consistent final state? Once you subscribe, the notifications that will eventually set your bools will fire asynchronously (possibly not even that, as you may have observed when debugging). You can't assume the bools to have any determined state after Subscribe completes.
The observable completing is by design, it has been subject of some debate but the behaviour hasn't changed from 4.0 to 4.1. What's important is that OnNext happens before OnCompleted. You might add some code to assert that
If you continue to experience strange behaviour, please provide a failing unit test asserting your expectation.

Thanks very much for the clarification :)

@yuramag Could you please provide a working example with some assertions (a unit test in the best case) to clarify your expectation?

@yuramag @antichaosdb Can you confirm this is fixed with v4.1.2 ?

The issue is still present. Unfortunately, behavior is not predictable. Consider the following test:
[TestMethod]
public async Task TestRx1()
{
    const int timeout = 5;

    var xs = Observable.Create<Unit>(async o =>
    {
        await Task.Delay(timeout);
        o.OnError(new Exception());
    }).Replay().RefCount();

    xs.Subscribe(x => Console.WriteLine(x), ex => Console.WriteLine(ex.Message), () => Console.WriteLine("Completed"));

    var completion = Task.Run(async () => await xs.DefaultIfEmpty());
    completion.ContinueWith(x => Console.WriteLine($"Eception: {x.Exception.Message}"));

    await Task.Delay(timeout * 2);

    Assert.IsTrue(completion.IsCompleted);
}

I expect the assertion to always pass, which happens half of the time. Sometimes though I am getting exceptions printed out and assertion failing.

Your assertion is definitely incorrect. It's a task, it's run asynchronously, even with a delay, you just can't make that assumption.

Well, I agree that it is not entirely correct. I was just trying to test around hanging on await of xs. Consider these two tests:
[TestMethod]
public async Task TestRxPasses()
{
    var xs = Observable.Create<Unit>(async o =>
    {
        await Task.Delay(5);
        o.OnError(new Exception());
    }).Replay().RefCount();

    xs.Subscribe(x => Console.WriteLine(x), ex => Console.WriteLine(ex.Message), () => Console.WriteLine("Completed"));

    await xs.DefaultIfEmpty();
}

[TestMethod]
public async Task TestRxHangs()
{
    var xs = Observable.Create<Unit>(async o =>
    {
        await Task.Delay(5);
        o.OnError(new Exception());
    }).Replay().RefCount();

    xs.Subscribe(x => Console.WriteLine(x));
    xs.Subscribe(x => Console.WriteLine(x), ex => Console.WriteLine(ex.Message), () => Console.WriteLine("Completed"));

    await xs.DefaultIfEmpty();
}

The last one never ends!

That's due to the first call to Subscribe, which doesn't observe the exception but only rethrows it. That'll break the whole chain, every operator will unsubscribe from it's source and you won't get anything out of xs again. It's unrelated to that specific overload of Create. This code doesn't terminate as well:
[TestMethod]
public async Task TestRxHangs()
{
    var xs = Observable.Create<Unit>(o =>
    {
        Task.Delay(5).ContinueWith(_ => o.OnError(new Exception()));
        return Disposable.Empty;
    }).Replay().RefCount();

    xs.Subscribe(x => Console.WriteLine(x));
    xs.Subscribe(x => Console.WriteLine(x), ex => Console.WriteLine(ex.Message), () => Console.WriteLine("Completed"));

    await xs.DefaultIfEmpty();
}

What bothers me is that these two semantically equivalent tests behave differently - one passes, but the other does not:
[TestMethod]
[ExpectedException(typeof(Exception))]
public async Task TestRxPasses2()
{
    var xs = Observable.Create<Unit>(o =>
    {
        o.OnError(new Exception());
        return Disposable.Empty;
    }).Replay().RefCount();

    xs.Subscribe(x => Console.WriteLine(x));

    await xs.DefaultIfEmpty();
}

[TestMethod]
[ExpectedException(typeof(Exception))]
public async Task TestRxHangs2()
{
    var xs = Observable.Create<Unit>(async o =>
    {
        Task.Delay(1).ContinueWith(_ => o.OnError(new Exception()));
        return Disposable.Empty;
    }).Replay().RefCount();

    xs.Subscribe(x => Console.WriteLine(x));

    await xs.DefaultIfEmpty();
}

Again, if you believe that this is expected by design, I won't argue.

The first one is synchronous, you get the exception directly on subscription. The second is asynchronous, so the test won't observe the exception, but the subscription chain still will be broken (standard Rx operators unsubscribe and clean up when a downstream-call to OnError throws). As a rule of thumb, don't use the Subscribe-extension that doesn't handle exceptions because you might just run into situations just like this, which is especially harmful if the observable is shared through Replay and RefCount.

The analysis by @danielcweber on this thread is correct. I'm not sure if there's still anything actionable with this issue given that the behavior is as intended?

Users run into the implications of that convenience-error-rethrowing-Subscribe-extension all the time. The framework should maybe, in addition to Obsolete, define an attribute YesItsThereButNoReallyYouDontWantThisInYourCodeAttribute ;-)


Fix broken Travis builds

I think the credentials issue was that it was not decrypting them to the right place. This fixes that as well as adds documentation for next time the credentials need to be updated.
Also unskips the previously broken tests, and skips a couple that are now broken.
See build: https://travis-ci.org/google/clasp/builds/431920165

[x] npm run test succeeds.
[x] npm run lint succeeds.
[x] Appropriate changes to README are included in PR.

Cool! Makes sense. Let's see if it works.


Create upstream issues for open CVEs

Our current implementation of harbor-config-operator contains a lot of CVEs coming from upstream. We should create issues in the relevant upstream repositories to update those dependencies.
Upstream repos:

harbor
harbor-operator

https://github.com/giantswarm/harbor-config-operator/blob/5d68753be09e142b6e37d641c9da26a05b1cd4c0/.nancy-ignore

https://github.com/goharbor/harbor-operator/pull/985

sonatype-2019-0890 - https://github.com/goharbor/harbor/pull/17899


WIP: Pfe jump links

Demo page:
https://deploy-preview-858--happy-galileo-ea79c4.netlify.app/elements/pfe-jump-links/demo/

@Djfaucette Did you need me to create any further design documentation for this or are you all set?

@coreyvickery I think I'm good. If the demo link matches expectations and you don't need anything from me I think we're set.


s

Rancher versions:
rancher/server or rancher/rancher:
rancher/agent or rancher/rancher-agent:
Infrastructure Stack versions:
healthcheck:
ipsec:
network-services:
scheduler:
kubernetes (if applicable):
Docker version: (docker version,docker info preferred)
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Steps to Reproduce:
Results:

accidentally created an issue (via keyboard shortcuts somehow??). Please ignore and delete.


(3.7.0) Buying a damaged svt-40 from flea market comes with 100 durability always

General information:
Project issue is for:
Server
Expected result:
Durability needs to be matching with flea offer.
Actual result:
Durability comes 100/100
How to reproduce:

open flea market
search for svt
buy a damaged svt-40

Attachments

2023-08-16[21-17] (0).png (1908 KiB)
2023-08-16[21-18] (0).png (1963 KiB)
server-2023-08-16-21.log (35 KiB)
2023.08.16_18-13-20_<IP_ADDRESS>.25800 traces.log (74 KiB)

Originally written by CZPZ

Fixed with: https://dev.sp-tarkov.com/SPT-AKI/Server/commit/54059e01e4ca45d710e045378ef5dbb45cc88f44

Originally written by chomp

Fixed with release: https://discord.com/channels/875684761291599922/875707166244360254/1141449450468937758

Originally written by CZPZ


faster reduce operations on cuda using cupy

More than 10x faster reduce operation by doing them on GPU with cupy
Experiment result notebook.
┆Issue is synchronized with this Jira Task by Unito

This can be closed, as transformers perform the reductions in native TF/Pytorch, which takes advantage of CUDA, if on GPU. @JoanFM


Test alerts not showing up in Slack channel

Testing the webhook via curl works, however on the Test Endpoint button it succeeds but no message is received.
This was tested in both HA mode and Standalone

possible related to https://github.com/rancher/opni/issues/1621

The issue is caused by a blocking channel that is never read.


Data changing between .rmd and .html file

I finished Lab 01 and knitted the .html file. However, when I reviewed my answers, all of the solutions to the codes had changed. For Question 1, my answer in the .rmd script is a significantly smaller number than the answer that appeared in the .html file. All of my other numbers are off as well. I also noticed that when finding the amount of parcels and vacant lots in each neighborhood for questions 5 and 6, my .rmd script is missing a few of the neighborhoods that are showing up in the .html file. How do I fix this?

Try re-running the chunks in your RMD file starting from the place where you load the data.
Just guessing here from your description (I would have to see the RMD to confirm), but you likely altered your data in your RMD file through inter-active coding, then did not include those steps in the final file.
The answers embedded in your RMD file represent the results from the last time you ran a chunk.
The knitted HTML version will start at the top and run chunks sequentially (not always the case when you are in interactive mode). The HTML version will likely be correct. Your RMD version probably has a "ghost in the machine".
Reload your data and run the chunks in order, I bet the answers converge.

It's similar to the problem:
( 6 + 4 ) / 2  does NOT equal 6 + 4 / 2

I downloaded the template again and started over. This time I ran all the codes correctly from the start and the results in the .rmd and .html files matched. Thanks for the tip!


init.sql is not executed if data volume exists during mysql start up

Refer to this thread https://stackoverflow.com/questions/38504257/mysql-scripts-in-docker-entrypoint-initdb-are-not-executed/52715521

Issues where we closed by suggesting workarounds for these:
https://github.com/linkedin/datahub/issues/1620#issuecomment-609837480
https://github.com/linkedin/datahub/issues/1588#issuecomment-597421836

Closing due to inactivity


fix: re-enable unicode-case feature on regex

Originally I was going to file an issue for this, but I figured I can just quickly PR the fix. Below is the bug report that this pre-emptively fixes. This broke due to #526.

Describe the bug
When compiling against master, lettre now panics when parsing addresses.
To Reproduce
use std::str::FromStr;

fn main() {
    lettre::message::Mailbox::from_str("Example <example@example.com>").unwrap();
}

Expected behavior
Addresses parse without panicking.
Environment (please complete the following information):

Lettre version: 7f384bc
OS: any

Additional context
thread 'async-std/runtime' panicked at 'called `Result::unwrap()` on an `Err` value: Syntax(
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
regex parse error:
    ^(?i)[a-z0-9.!#$%&'*+/=?^_`{|}~-]+\z
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
error: Unicode-aware case insensitivity matching is not available (make sure the unicode-case feature is enabled)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
)', /home/build/.cargo/git/checkouts/lettre-53652803723a9045/7f384bc/src/address/types.rs:79:70

Looks to me like unicode-case needs to be enabled.

Good catch! Thanks for the PR

Good catch! Thanks for the PR


Include cheatsheet for release process

Summary
Include cheatsheet for release process
Details and comments

Thank you @jesus-talavera-ibm ! I have another question apart of the one made on the code: the process to do the first release of the version is the same than when we add patches?

Yes, the only difference is that minor versions are done in main branch and patches are done in stable/x.x branch. In minor version there is an "extra" step which is creating the stable/x.x branch too

Thank you!


Added slice fix and specced

'slice' was being pluralized to 'slice', similar to 'mice' and 'lice'.
However, the plural of slice is slices.

Not particularly sure why the python 2.6 version failed


When "agg_trade" is running, I can't terminate the program using Ctrl+C. Is there any solution to this?

from binance.websocket.spot.websocket_stream import SpotWebsocketStreamClient
def on_message(_, _message):
print(_message)
my_client = SpotWebsocketStreamClient(on_message=on_message)
my_client.agg_trade(symbol="btcusdt")

Have you considered closing the connection using the method my_client.stop() like in the example?

Have you considered closing the connection using the method my_client.stop() like in the example?

Yes, I know about my_client.stop(), but what I want is for the program to keep running until I manually close it, not to stop automatically after a set time. How can I make it so that I can decide whether it should close at any time after the program starts running?

What exactly happens when you Ctrl+c? Which os are you using?

What exactly happens when you Ctrl+c? Which os are you using?

I run the program in the terminal of VSCode on Windows. After pressing Ctrl+c, the program continues its previous running state, constantly fetching the latest data from a remote server and printing the data on the screen. This terminal cannot respond to any other operations.

You can wrap your program in a try-except block to catch the KeyboardInterrupt and close the connection cleanly when Ctrl+C is pressed.
import logging
from binance.lib.utils import config_logging
from binance.websocket.spot.websocket_stream import SpotWebsocketStreamClient
config_logging(logging, logging.DEBUG)
def message_handler(_, message):
logging.info(message)
Initialize the client
my_client = SpotWebsocketStreamClient(on_message=message_handler, is_combined=True)
try:
# Subscribe to a single symbol stream
my_client.agg_trade(symbol="bnbusdt")
print("Streaming started. Press Ctrl+C to terminate.")
# Keep the program running
while True:
    pass

except KeyboardInterrupt:
print("\nCtrl+C pressed. Stopping the client...")
my_client.stop()


Handle backend issues

#1466 and #1463 have both emerged because the testnets are not reliably producing blocks. The app does not realize this currently, and does not yet handle this behaviour well, this results in bad/misleading error messages. We need to define measures to handle these scenarios somehow.

Closing favoring #1603


dm list needs to be read-after-write consistent across a cluster

in order to reliably script against a multi-node dotmesh cluster (like smoke.sh attempts to do) we need read-after-write consistency, in particular:

dm push to one node
dm list on another node

needs to show the result of the push immediately after the push completes.
currently, for historical reasons, dm list enumerates the fsMachines on the node where the request lands. while this sort-of works, it's eventually consistent because it depends on fsMachines being created and started on all nodes in order to show up in the enumeration. it would be better for dm list to go directly to etcd and read from the registry, this way it will always return fresh information.
it should be possible to make it a lot faster while we're at it, fixing https://github.com/dotmesh-io/dotmesh/issues/337.

we could start by consulting the local cache of the registry, and only if that doesn't improve the smoke tests go to etcd on every list.

Perhaps it doesn't.
dm list calls DotmeshRPC.List, which is a near-duplicate of DotmeshRPC.AllDotsAndBranches, although the latter operates through a slightly different mechanism; both are based on the caches we get from etcd rather than fsmachines, so should be pretty up-to-date.
However, using dm list to test for existence of a dot on a random node is, perhaps, an anti-pattern - dm list does a whole lot more work than is necessary for that. Better to run dm dot show DOTNAME, which returns a shell status code of success (dot exists) or failure (dot doesn't exist or something else went wrong), and retry a bit to overcome latency in etcd updates. dm list can be improved in many ways, but this use case is best handled in other ways,


Nuxt3 proxy infinite loading

Hello everyone!
I'm trying to use nuxt3 api hooks for SSR, but gets always infinite loading and 404 after this. I see the request in the console but nothing happens. It works fine with client side requests, but not with SSR.

My nuxt config is:

Wouldn't a 404 indicate that it cant reach the url/path you're entering?

When access to the page throw link directly it doesn’t work. But when navigate throw router, it works fine.
The difference is that in first case request sending on the server side. In the second in client side.

I want to migrate to proxy but cannot figure out how to do this;(

Second example. The same code here but with {server: false}. All works fine! Without this parameter fall into infinite loading. I think that 404 is instead 408 in nuxt3. That's why it happens.

But in total I still have the problem to use Proxy for server side api requests.

Yea I can see that it isnt working with nuxt3's fetch. It's working with the axios module so you could use that, I haven't really looked into nuxt's isomorphic fetch to really give a solution for that so your alternative is to use the axios module.

But then what is proxy reason? If I will include baseUrls everywhere then i don't need to use proxy:D

The global intercept serves as a way to handle proxy requests under a domain for a specific path or multiple paths, you're free to change and alter where and how that interceptor works. This is in context for the axios module. You will have to figure out how you want to handle that. As it stands there's no global interceptor for the isomorphic fetch. so you will have to manually put in the domain for the baseURL for $fetch everytime you're using it:
$fetch('<path>', { baseURL: '<domain>' })


Broken GetFeatureInfo examples

I'm seeing frequent transparent tiles in the tiled GetFeatureInfo example:

And the image layer version of the same gets frequent 504s.
When these examples do load, the cursor changes described don't happen because the responses are missing CORS headers.

I've addressed the CORS issue in https://github.com/openlayers/ol3/commit/5295a22e76b1b3d57d06c75adef20dd956f42ed1#diff-2986a0d19c9f6451163c5d53f6a4e87aR11 (as part of #4420).  Not sure if it is possible to address the 504 and transparent tile issue.

yes demo.boundlessgeo.com has been acting very funny lately

Fixed: demo.boundlessgeo.com is up again


New CONTRIBUTING.md

Purpose

A contributing guide to help establish project wide standards for contribution

Proposed Changes

[ADD] A new contributing guide

Issues

N/A

Testing

In-development

@riverma - I made a bunch of edits to CONTRIBUTING.md, have a look when you get a chance.  I removed a few sections, and reorganized it a bit.  The main content that I worked on is all under the last section, "Development Guides".


Remove console output

It would be great if you can disable the console log in the javascript module... this is a great library and I want to use it in a production environment (and therefore this console outputs are confusing for the customer).

Available in v1.0.2


Improvements to VTOL and FlightCore guide

Changes the quotes in the VTOL guide to be asterisks, as well as make the image for right clicking a mod display properly on gitbook.
Fixes grammar in the FlightCore guide's Settings section

Also forgot to mention but I'd use both quotation marks and italics when talking about button names etc, i.e.

_"Example button name"_

This is because italics on its own can be hard to detect for people with poor eye sight.

I'll try to split them from now on, just didn't want to spam pr's
Will add the underscores now

I'll try to split them from now on, just didn't want to spam pr's

haha, yeah I get the concern and yet as counter-intuitive as it might seems it's actually the preferred approach as smaller individual changes are a lot easier (and therefore faster) to review. So spam away as much as you want <3


update homepage

New homepage

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: raghukapur9:white_check_mark: aashaykapoor:x: aashaykapoor-bimaplanYou have signed the CLA already but the status is still pending? Let us recheck it.


Bump Dependencies #2677634266

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/2677634266

These versions changes are merged with https://github.com/wso2/product-is/pull/14253


Enhance Reference Object verbiage to add clarity for $ref fragments

          > Section [Reference Object](https://github.com/OAI/sig-workflows/blob/main/versions/1.0.0.md#reference-object), field `$ref` says

This MUST be in the form of a URI.

Which is only half of the truth: the fragment part - if present - apparently MUST be in the form of a JSON Pointer URI Fragment Identifier Representation.
Otherwise how is an implementation supposed to interpret the fragment part?

@ralfhandl I'll look to update the media type registrations to specify JSON Pointer as the fragment identifier mechanism, and add some additional text also into the section to clarify
Originally posted by @frankkilcommins in https://github.com/OAI/sig-workflows/issues/49#issuecomment-1864691304

See also:

https://github.com/OAI/sig-workflows/issues/49#issuecomment-1838274076
https://github.com/OAI/sig-workflows/issues/49#issuecomment-1839830427

@frankkilcommins RFC 6901 specifically states that JSON Pointers are not the fragment syntax for application/json, and RFC 8259 does not define any fragment syntax.
This, of course, has not stopped people from treating JSON Pointer as a universal JSON fragment syntax, because in practical terms one is needed and that's the one that makes sense.  I've never figured out how to make this RFC-compliant, except perhaps by saying that implementation should "cast" application/json to application/whatever+json and then apply the fragment.  I've never tried to get that through a formal standards body, though.
But technically you MUST use a +json media type that defines that fragment syntax.
The proposed YAML RFC, which is nearing publicaton as a numbered RFC, does define JSON Pointer as a fragment syntax for application/yaml, although it is not automatic for +yaml media types and must be defined in each one.


MRG: Fixes from LGTM

Mostly trivial fixes from LGTM except:

One in spectral.py where I realized there was a bunch of cruft related to sig_pos_end that could be eliminated, and the code made more DRY.
Modernized connectivity tests to utilize pytest.mark.parametrize
Moved lengthy spectral_connectivity explanation to Notes.
Fixed some XXX's in mne/gui to actually probe the pyface toolkit being used.
Commented out code in mne/io/bti that used to live in a if False:  # XXX : reminds us to support this as we go block.

This pull request introduces 9 alerts and fixes 53 when merging a9cb593f638f5616c71b798d1269158ab3b9429b into f7bb2ef4a40bf3bc3e20c82feba145e0e6e35aac - view on LGTM.com
new alerts:

6 for Signature mismatch in overriding method
3 for Variable defined multiple times

fixed alerts:

37 for Variable defined multiple times
6 for Unused local variable
3 for Signature mismatch in overriding method
3 for Unreachable code
1 for Redundant comparison
1 for Constant in conditional expression or statement
1 for Comparison of identical values
1 for Implicit string concatenation in a list

Comment posted by LGTM.com

This pull request fixes 50 alerts when merging 48c7421a91af81c51b3ab1a29fe386f680a9046d into 57d33722dc80a5065444031068cac94c73aa9568 - view on LGTM.com
fixed alerts:

37 for Variable defined multiple times
6 for Unused local variable
3 for Unreachable code
1 for Redundant comparison
1 for Constant in conditional expression or statement
1 for Comparison of identical values
1 for Implicit string concatenation in a list

Comment posted by LGTM.com

This pull request fixes 50 alerts when merging 48c7421a91af81c51b3ab1a29fe386f680a9046d into 57d33722dc80a5065444031068cac94c73aa9568 - view on LGTM.com
fixed alerts:

37 for Variable defined multiple times
6 for Unused local variable
3 for Unreachable code
1 for Redundant comparison
1 for Constant in conditional expression or statement
1 for Comparison of identical values
1 for Implicit string concatenation in a list

Comment posted by LGTM.com

This pull request fixes 50 alerts when merging b1b21298f36a9abd6e07ac351b2309d25d7dcede into 57d33722dc80a5065444031068cac94c73aa9568 - view on LGTM.com
fixed alerts:

37 for Variable defined multiple times
6 for Unused local variable
3 for Unreachable code
1 for Redundant comparison
1 for Constant in conditional expression or statement
1 for Comparison of identical values
1 for Implicit string concatenation in a list

Comment posted by LGTM.com

apart from this commented code, we could merge.

This pull request fixes 50 alerts when merging 4632b1a84f3c4c8ee6b9b4fbacc61698015753cb into b757ff19c5556e328111661a304d46dff279d818 - view on LGTM.com
fixed alerts:

37 for Variable defined multiple times
6 for Unused local variable
3 for Unreachable code
1 for Redundant comparison
1 for Constant in conditional expression or statement
1 for Comparison of identical values
1 for Implicit string concatenation in a list

Comment posted by LGTM.com


Feature | Make visage less restrictive & ReactNative support

Issue description
ReadyPlayerMe is just amazing, but the fact that visage only works for React apps is very restrictive!
The main motivation for creating this issue was about me trying to use some internal features on ReactNative.
I've read the internal code and understand some components will not work on ReactNative cause they depend on the DOM, but many resources can still be used and should be importable.
Resources like:

Services
Some components like:

Bloom
FloorReflection
Lights
Models
etc

Eventual solution
Having a ReactNative support will be great! or importing more resources (like the above-listed resources).

I really wanted to implement the eye-blinking support for my model, but I had to copy the useIdleExpression service/hook in my code to achieve this. would be much easier if it was importable.

I'd appreciate contributing to this one, let me know if a PR from me will be welcome.


xwallpaper: remove libseccomp dependency

Motivation for this change
libseccomp has been upgraded to 2.5.0, which xwallpaper currently does not support. Luckily this dependency is optional, so for now I've simply removed it, making the application usable again.
Also ran nixpkgs-fmt on the file, as this looks a lot nicer IMO.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 97364 1

1 package built:
- xwallpaper

Program can at least print out help message.
[nix-shell:~/.cache/nixpkgs-review/pr-97364]$ xwallpaper
usage: xwallpaper [--screen <screen>] [--daemon] [--debug] [--no-randr]
  [--trim widthxheight[+x+y]] [--output <output>] [--center <file>]
  [--focus <file>] [--maximize <file>] [--stretch <file>] [--tile <file>]
  [--zoom <file>] [--version]

LGTM except that your code commit should follow the required convention.
https://nixos.org/manual/nixpkgs/stable/#submitting-changes-making-patches

I think the commit messages are correct? It's just there's two, one to drop the dependency and one for formatting. Which is sometimes helpful if you want to review things clearly.

@IvarWithoutBones If you could also please open a backport PR to release-20.09 (I'm not sure if this is broken on 20.03 too?) it would be great https://github.com/NixOS/nixpkgs/blob/master/.github/CONTRIBUTING.md#backporting-changes.

@IvarWithoutBones If you could also please open a backport PR to release-20.09 (I'm not sure if this is broken on 20.03 too?) it would be great https://github.com/NixOS/nixpkgs/blob/master/.github/CONTRIBUTING.md#backporting-changes.

Sure, PR for 20.09: #97547
This currently isnt needed for 20.03, as this still has a compatible version of libseccomp.


Misc issues for 1.5.0 release

[x] Improve Travis run; assertions enabled? => covered by separate testrunner now
[x] Build target or script to generate the index page footprint and startup RAM figures based on config YAML files (now done manually which is hard to reproduce and opaque) => covered by testrunner

I'm pruning the in-progress issues for 1.5.0 to ensure the release is done during April.

I'm not really sure the checklist above can be completed in 7 days... ;-)

That's why I'm shuffling issues :)

Bullet points not covered in 1.5.0 are now separate issues or pulls.


[dtests] Added few Negative tests

Added few of the negative scenarios as part of HIP dtests.

Raised #1735 after addressing the review comments. So, closing this.


Auto scroll in tree view

This PR adds the following feature. When an oracle for a workspace clicks on the "Entire Tree" nav button, the tree that is opened will automatically scroll down to that workspace. Also, the workspace is now highlighted so there's a visual indication it's the active workspace.

There's one aspect of this PR that I hope can be improved upon. Currently, if you scroll to the active workspaces while workspaces above it (above it on the tree view page, not above it in the tree structure) are still loading, then, as these workspaces, load the active workspace moves out of the correct position.
My approach to this issue is to just add a 3 second delay. After the active workspace part of the tree view loads, we wait 3 seconds for additional workspaces to load, and then scroll to the active workspace.
This won't work when the loading takes longer than 3 seconds, and when it takes less than 3 seconds the user is just waiting for no reason. If we knew when the workspaces "above" the active workspace had finished loading, then we could just wait until this occurred before scrolling the active workspace. But this information is non-trivial to obtain, since all the workspaces fetch information from the GraphQL server independently.

I can see the 3 seconds thing as a reasonable trade-off. In the longer term, I wonder as browsers develop scroll anchoring capabilities it might resolve itself straight forwardly and not need any workarounds? https://developer.mozilla.org/en-US/docs/Web/CSS/overflow-anchor/Guide_to_scroll_anchoring

Great let's stick with the 3s delay and we can revisit it if need be.


Add unit test to confirm envvar overwrite of Cloud SDK settings

There are many ways to set the current project in the Cloud SDK. One way is to set an environment variable. We should add a unit test to confirm that our method of shelling out to the Cloud SDK to gather configuration data picks up on settings specified via environment variable.

Test is now added with https://github.com/GoogleCloudPlatform/google-cloud-powershell/pull/431.


Support matchers in a monorepo setup

We are using tflint for linting a repository with multiple independent (in terms of state) stacks. Our GitHub action loops over all of those stacks (using --force) to gather all findings.
It seems like anntotations are not using the full path of the affected terraform file, so those are not visible in the GitHub UI:
Notice: main.tf:23:26: Notice - "default.mysql5.6" is default parameter group. You cannot edit it. (aws_db_instance_default_parameter_group)
Error: main.tf:16:26: Error - "mysql57" is invalid engine. (aws_db_instance_invalid_engine)

The main.tf file is actually global/cdn/content/main.tf in this example. Would it be possible to configure the problem matcher to support a monorepo structure?
Might be related to https://github.com/terraform-linters/setup-tflint/issues/19

We plan to add --chdir and --recursive flags in v0.44.
https://github.com/terraform-linters/tflint/pull/1612
https://github.com/terraform-linters/tflint/pull/1622
When using these, the output path will be a relative path from the original working directory.

Thanks for the quick reply @wata727 , looking forward to v0.44

v0.44 has been released.
https://github.com/terraform-linters/tflint/releases/tag/v0.44.0


[Bug] Trace Profiling

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache SkyWalking Component
OAP server (apache/skywalking)
What happened

When I use skywalking performance analysis, there is obviously less time in the details
My code is as follows

The following is the waiting time for log printing

What you expected to happen
The time consumption in the list should be consistent with that in the thread stack, and should not be so different
How to reproduce
code：

task:

oap和ui：9.1.0
agent：8.11.0
Anything else
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

You checked Yes I am willing to submit a PR!. Does this mean you know what is happening?

You should check the sampling snapshot the agent collected. This should be a good start, https://skywalking.apache.org/docs/main/latest/en/guides/readme/#profile

No update after reporting.


[SPARK-8185][SPARK-8188][SPARK-8191][SQL]function datediff, to_utc_timestamp, from_utc_timestamp

This PR is based on #7643 , thanks to @adrian-wang

Merged build triggered.

Merged build started.

Test build #39331 has started for   PR 7847 at commit 85cdd21.

Test build #39331 has finished for   PR 7847 at commit 85cdd21.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class FromUTCTimestamp(left: Expression, right: Expression)
case class ToUTCTimestamp(left: Expression, right: Expression)
case class DateDiff(endDate: Expression, startDate: Expression)

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #39332 has started for   PR 7847 at commit 3011f39.

Test build #39332 has finished for   PR 7847 at commit 3011f39.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class FromUTCTimestamp(left: Expression, right: Expression)
case class ToUTCTimestamp(left: Expression, right: Expression)
case class DateDiff(endDate: Expression, startDate: Expression)

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #39334 has started for   PR 7847 at commit 22d8a8c.

Test build #39334 has finished for   PR 7847 at commit 22d8a8c.

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

Merged build finished. Test FAILed.

FYI:
https://github.com/apache/hive/blob/master/ql/src/java/org/apache/hadoop/hive/ql/udf/generic/GenericUDFDateDiff.java#L73
hive are casting strings in datediff to date/timestamp in UTC timezone.

@adrian-wang I understand you concern, our goal is to be Hive compatible at our best, not follow the implementation details in Hive.
For datediff, these expression should be have the same results:
select datediff('2015-05-06', '2015-05-05')
select datediff(cast('2015-05-06' as date), cast('2015-05-05' as date))
select datediff('2015-05-06 00:00:01', '2015-05-05 23:59:59')
select datediff(cast('2015-05-06 00:00:01' as timestamp), cast('2015-05-05 23:59:59' as timestamp))

This is the behavior in MySQL and MS SQL Server, correct me if it's not.
But in Hive, the fourth one is different, kind of silly, I think we should not follow that. We also break the compatibility already (returning different type).

cc @yhuai @rxin

Test build #1274 has started for   PR 7847 at commit 22d8a8c.

Test build #1274 has finished for   PR 7847 at commit 22d8a8c.

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

Merged build triggered.

Merged build started.

Test build #39376 has started for   PR 7847 at commit 74333d7.

Test build #39376 has finished for   PR 7847 at commit 74333d7.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class FromUTCTimestamp(left: Expression, right: Expression)
case class ToUTCTimestamp(left: Expression, right: Expression)
case class DateDiff(endDate: Expression, startDate: Expression)

Merged build finished. Test PASSed.

I'm going to merge this, if there is something we could improve, could do it later.

Thanks for the hard work here.
Did this land in documentation yet? I searched for it at https://spark.apache.org/docs/latest/sql-programming-guide.html but didn't find any reference yet.
Someone is asking if there is a way to extract different granularities of the time unit from Spark SQL DateDiff(). Such as milliseconds vs. days vs. months.  I suppose we could with simple division if the DateDiff returns milliseconds units, and divide by 1000 and 60 and 60 up to hours units and again by 24 up to days units.
If we only return days units in the difference, the result would be rounded (losing hours and seconds precision) so multiplying x24x60x60 to get seconds is going to be extremely lossy.
I think folks are used to the SQL Server implementation of DateDiff (where you provide the DatePart unit), as opposed to the Hive DateDiff and MySQL implementation which seems to return only rounded day parts. https://msdn.microsoft.com/en-us/library/ms189794.aspx
Appreciate any advice, or point me to the right forum. Sorry to bother ~ Jason

@JasonWHowell docs go out with releases and none has occurred since this was committed, but looks like it will go in 1.5


Accordion-3 updated

closes #2053

@RavindraP04 , please review it

Congrats @Laxmankohar 🎉, your PR got merged. To be eligible for the swags from ClueLess.
Don’t forget to star this repository. ⭐


Added snow slabs and snow shoes

Contains
Added snow shoes and snow slabs (1/8, 1/4, 1/2) for #2406
How to test
For snow slabs

Open the command console
Type in 'give snowslabeight'
You will receive the 1/8 snow slab
Do the same for (1/4, and 1/2) slabs, by typing 'give snowslabhalf' and 'give snowslabquarter'
You will receive the respective snow slabs in your inventory

For snow shoes

Open the command console
Type in 'give snowshoe'
The snow shoe will appear in inventory

Outstanding before merging
If anything. You can use neat checkboxes! Feel free to delete if not needed

[ ] Add snowshoe functionality
[ ] Add stacking for snow slabs

Shouldn't this be a mod?
/me is entirely for removing all 'content' from the engine

Heya @ashley-hu good to see another round of stuff from your group :-)
I can confirm the new blocks work - nice job!

However, this time through we're going to have to do a little bit more work, which hopefully will work alright with your course. Often in open source you'll end up with some old issue that has drifted a bit away from how things work in the present, and this is one of those cases. It came up a bit in discussion earlier when I explained about how the "add risk of falling when climbing in snow" part of the issue is obsolete as climbing isn't currently a thing :-)
Stuff we need to look at here:

You see how you're affecting 14 files, but have 53 listed commits, including a bunch involving other work you've done that's not relevant to this PR? Merging this as-is would add a lot of messy history to our project, which is bad. There are two ways to fix this

git rebase - this is a technical, fast, and clean option, but it is also tricky and I do not recommend it unless one or more of you is very comfortable with Git :-) In either case I encourage you to read up on it, try some of the GitHub or other tutorials on Git, and maybe play with it in a local duplicate copy of your workspace - rebase is one way you can really break your workspace if you aren't sure what you're doing, but Git makes it super easy to work on a copy
Simply start a clean branch and copy paste the few related files in, commit once, push to GitHub, and make a new PR (closing this one). This is my recommendation, due to another reason as well. Read on! :-)

You don't need a unique texture for each block. By default a SomeName.block file will look for a SomeName.png texture, but as you've done elsewhere you can use block attributes to just point to the same snow texture for every block. So you can delete the duplicate files (or if copy pasting into a new branch just skip those files)
Use "eighth" in each relevant place to indicate 1/8, not "eight"
I'm not sure what the "Lightsnow" block is for, it isn't quite configured right. What's the goal with it?
Same story with the slabStack.prefab which is empty, so adding it doesn't actually do anything :-) You don't need to have one at all, you can just take out that part of the definition. If that's part of a future effort to make stacking work that's cool but should wait until then, generally it is frowned upon to add incomplete work.
For the snowshoes there are a few issues

It might be tricky visually showing the right kind. It looks like you added boots not Snowshoes but it might just be hard to get the icon made right. Feel free to try in a 32x32 pixel size instead if the added detail help make them more visually distinct. If existing artwork is being reused we need to know how it is licensed and ideally add a link somewhere to credit the author.
@OvermindDL1 is right, we don't really want content in the engine repo and that's another problem with the old issue - back when it was created this was a fine place to put content but now it is not :-) I should have mentioned that more in the rebooted issue. The slabs could live here in Core at least for now (easy to move later), they'd be useful, and I'm surprised we didn't have any yet. A better home
for the snowshoes would be https://github.com/Terasology/Equipment which could also expose you to module development (one day the slabs might move to StructuralResources). Might be best to guide via chat but if you run groovyw module recurse Equipment then gradlew idea you should get that source added locally
You added the snowshoes into an item atlas, but for one-off items like that it is way better supplying it as an independent image file plus the associated .prefab which would also later be a way to help define the custom functionality. Again the Equipment module should show you a lot of examples on how to do that :-)
Adding the actual logic to the snowshoes is indeed quite a bit more complicated. Another part of open source is to better direct things over time. Since the rebooted snow issue is poorly written even now we can try to address a few things here then re-submit new issues elsewhere where they fit better and close the original as partially completed. So try to submit a separate PR with the snowshoe graphic to the Equipment module and after that's merged we can work on writing up a better feature request there on adding the logic later.

We could also write up an issue somewhere on making snow "stack" better (probably like ingots, swapping to larger slabs) or even make weather effects make snow blocks grow over time (even if you just trigger the functionality with a console command for now)
Let me know if all that makes sense, any questions you have, and which approaches you're interested in following. As usual chat is probably easier when we can find each other online at the same time :-)

Sorry we haven't been responding, we have exams and graduation in the next two weeks, but I will definitely take another look at the texture (I made it, thought it was inspired by the Minecraft diamond boots, so not entirely sure how licensing would work in this case) and making Snowshoes equipment instead of an item. We were actually planning to make the snowshoes look like snowshoes from the get go and I made a bunch of textures:

but we thought they looked like tennis racquets so we opted for boots instead, but with 32x32 pixels I think i'll have more room to make it look better so I'll work on that when I can. Our class is over so we may or may not be working on this project as actively anymore but we want to at least finish what we started so we'll get to it as soon as we can!

Thanks for the update, best of luck with your exams! You're more than welcome to keep contributing but no obligation nor rush, we'll be here a long time :-)
And yeah true snowshoes are tricky!

Hey @dorasun @ashley-hu,
Just wanted to check in on if this has had any updates or if you're still planning on working on this in future?


"Missing user or char file !

Placed in correct directory full of core_char .dat files but says there are none...

It could be because EANM couldn't reach CCP's servers. Have you tried again after a few hours/days ?
I have very little time to look into it currently, sorry.

Closing due to inactivity.


False positives with CIS Benchmark IOSXE 17 defaults (e.g. 2.1.4 Set no service dhcp)

Hi,
I have a problem with CIS Benchmark 2.1.4 Set 'no service dhcp' (Automated)
It looks like the benchmark is a bit naive and the defaults of Cisco of showing dhcp service has changed somewhere in time.
The CIS benchmark states this:
Audit:
Perform the following to determine if the DHCP service is enabled:
Verify no result returns
hostname#show run | incl dhcp

There are 2 problems with this. First of all, no service dhcp shows up in the output, where the benchmark expects it to be empty.
router1#show run | incl dhcp
no service dhcp
 ip address dhcp

Secondly, virtual cloud based routers may have an IP address assigned by DHCP. This is the second dhcp occurency in the output above and will result in failure of the check also.
router1#show run interface gigabitEthernet 1
!
interface GigabitEthernet1
 ip address dhcp
end

The good news is, only the check from the CIS benchmark is incomplete. The benchmark is fortunately quite clear about the expected configuration. The configuration is correct, but the check is not.
One of the following command can be used to check the configuration and will probably be more version independent:
router1#show running-config all | include service dhcp
no service dhcp
router1#show running-config all | include no service dhcp
no service dhcp

I am using a virtual Cisco 8000V with IOS XE 17.13.1a
Please advise.
Thanks,
Jan

The CIS benchmark for no service dhcp has a reference link to an IOS 16 document. I expect the actual verification commands were not updated for IOSXE 17. There are more problems. These are some fixes for the issues I identified so far. They still check what the CIS benchmark requires to be done, so not changes there.
audit_ios17.py / no service dhcp
    # general_parsers.compliance_check_with_expected_empty_output(connection, "show running-config | include dhcp", "2.1.4 Set 'no service dhcp'", 1, global_report_output)
    general_parsers.compliance_check_with_expected_output(connection, "show running-config all | include no service dhcp$", "2.1.4 Set 'no service dhcp'", 1, global_report_output)

audit_ios17.py / no ip identd
    # general_parsers.compliance_check_with_expected_empty_output(connection, "show running-config | include identd", "2.1.5 Set 'no ip identd'", 1, global_report_output)
    general_parsers.compliance_check_with_expected_output(connection, "show running-config all | include no ip identd", "2.1.5 Set 'no ip identd'", 1, global_report_output)

audit_ios17.py / no service pad
    # general_parsers.compliance_check_with_expected_empty_output(connection, "show running-config | include service pad", "2.1.8 Set 'no service pad'", 1, global_report_output)
    general_parsers.compliance_check_with_expected_output(connection, "show running-config all | include no service pad$", "2.1.8 Set 'no service pad'", 1, global_report_output)

Some more:
audit_ios17.py / no ip bootp server
    # general_parsers.compliance_check_with_expected_empty_output(connection, "show running-config | include bootp", "2.1.3 Set 'no ip bootp server'", 1, global_report_output)
    general_parsers.compliance_check_with_expected_output(connection, "show running-config all | include no ip bootp server$", "2.1.3 Set 'no ip bootp server'", 1, global_report_output)

audit_ios17.py / no ip source-route
    # routing_parsers.compliance_check_source_route(connection, "show running-config | include ip source-route", "3.1.1 Set 'no ip source-route'", 1, global_report_output)
    routing_parsers.compliance_check_source_route(connection, "show running-config all | include no ip source-route", "3.1.1 Set 'no ip source-route'", 1, global_report_output)

Hi Jan,
I'll look into this sometime next week. Although the tool is very agnostic to the benchmark document command recommendation, I do agree they have some mishaps. I'll run through your recommendations on my lab next week.

Hi Jan,
Sorry for the delayed fix -- I've been busy studying for a certification exam. I've patched the script with your recommendations. It should now accurately detect the specified services. The expected empty output parser is also modified to handle the "no" prefix properly.
def compliance_check_with_expected_empty_output(connection, command, cis_check, level, global_report_output):
    command_output = ssh_send(connection, command)
    if not command_output:
        compliant = True

    elif command_output.split(" ")[0].lower() == "no":
        compliant = True

Thank you for the fix recommendations. I've added you to the README "Special Thanks To" section for your contributions :D I really appreciate it.


Fixed typo (mangement)

Docs Build status updates of commit 48284a3:
:clock10: Full build: the average full build time is 72 min(s) 38 sec(s), this is based on the last 351 build(s) for this repository.

Docs Build status updates of commit 48284a3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/sql.md
:white_check_mark:Succeeded
View (azure-java-stable) View (azure-java-preview) View (azure-java-legacy)

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


Can't upgrade to Laravel 11

Hello !
I can't upgrade to Laravel 11 with the v5.1 of this package because laravel 11 need symfony/mailer:^7.0 but it is lock to ^6.0 in composer.json
 therobfonz/laravel-mandrill-driver 5.1.0 requires symfony/mailer ^6.0 -> found symfony/mailer[v6.0.0, ..., v6.4.4] but the package is fixed to v7.0.4
Maybe juste upgrade the composer.json ?
Thanks you !

Done: https://github.com/luisdalmolin/laravel-mandrill-driver/releases/tag/6.0.0


[win32] Use initial cursor size when hiding or showing it

By doing this the users get their original cursor style back when Rich gives control back to the terminal, rather than a "full size" one
Fixes #2333
Type of changes

[x] Bug fix
[ ] New feature
[ ] Documentation / docstrings
[ ] Tests
[ ] Other

Checklist

[x] I've run the latest black with default args on new code.
[ ] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[ ] I've added tests for new code.
[x] I accept that @willmcgugan may be pedantic in the code review.

Description
Before the fix:
We can see the cursor is no longer the same (converted to a "thick" one) after Rich gives control back to the terminal:
https://user-images.githubusercontent.com/722388/173618989-275d0802-fc29-4830-8c19-e63bd3c9b401.mp4
After the fix:
Cursor-after-Rich is well and truly the same than cursor-before-Rich:
https://user-images.githubusercontent.com/722388/173619377-9db1605d-a6fb-4df2-aad4-a50b4b873a69.mp4

Codecov Report

Merging #2339 (49aa015) into master (14d47c9) will decrease coverage by 3.15%.
The diff coverage is 90.44%.

@@            Coverage Diff             @@
##           master    #2339      +/-   ##
==========================================
- Coverage   98.88%   95.72%   -3.16%
==========================================
  Files          73       73
  Lines        7629     7701      +72
==========================================
- Hits         7544     7372     -172
- Misses         85      329     +244

Flag
Coverage Δ

unittests
95.72% <90.44%> (-3.16%)
:arrow_down:

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

Impacted Files
Coverage Δ

rich/_export_format.py
100.00% <ø> (ø)

rich/_win32_console.py
3.06% <0.00%> (-88.43%)
:arrow_down:

rich/cells.py
100.00% <ø> (ø)

rich/live.py
97.90% <40.00%> (-2.10%)
:arrow_down:

rich/console.py
96.69% <96.03%> (-2.10%)
:arrow_down:

rich/_inspect.py
100.00% <100.00%> (ø)

rich/_wrap.py
100.00% <100.00%> (ø)

rich/box.py
100.00% <100.00%> (ø)

rich/control.py
100.00% <100.00%> (ø)

rich/progress.py
92.76% <100.00%> (+0.03%)
:arrow_up:

... and 9 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 d28e636...49aa015. Read the comment docs.


Remove squirrel after open change log.

Distracting me. We need to re-open the Atom that it has disappeared.

Thanks for the suggestion! This looks like a duplicate of https://github.com/atom/release-notes/issues/36 though - please subscribe there for updates.


Enable bootstrap.sh to determine OS and version on its own

Following up offline.

In reply to:<PHONE_NUMBER>


add namerefs to avoid command substitution subproc for function output assignment

Adds a way to use namerefs to avoid command substitution assignment for function output.

namerefs are good fun. Thanks for the PR.


Add .command_used to errors thrown by the parser

Supersedes #649

I had to fix the auth manipulating the error and fixed #427 while at it.

This should be ready to merge.


Remove empty check from ScannerService::fix

foreach deals with empty arrays very well 👌🏻
1 million loops in 25 ms instead of 20 ms with empty.

Thank you @szepeviktor !


Add Signal social button

What does this PR Change?

Adds Signal social button

While this does not address an existing issue, Signal recently added support for usernames, which will benefit those that use the Starlight theme and wish to publicly link their Signal profile.

Hello! Thank you for opening your first PR to Starlight! ✨
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any issues you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Vercel 🤩

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.