text:
how to reuse TcpStream code from src/sys/windows/tcp.rs ?

cc @alexcrichton @carllerche
I want to work with AF_BTH socket on windows OS,
to demonstrate what I am talking about here some code (blocking variant):
//create
let bt_socket: SOCKET = unsafe { socket(AF_BTH, SOCK_STREAM, BTHPROTO_RFCOMM) };
//skip error handling
let mut sock_addr = SOCKADDR_BTH {
      addressFamily: AF_BTH as USHORT,
      btAddr: bt_addr.into(),
      serviceClassId: RFCOMM_PROTOCOL_UUID,
      port: BT_PORT_ANY,
};
let sock_addr_ptr: *mut SOCKADDR_BTH = &mut sock_addr;
let err = unsafe { connect(socket, sock_addr_ptr as *mut SOCKADDR, mem::size_of_val(sock_addr) };

As I understand comments from lib.rs and windows mod.rs I basically need not only use windows::Binding to imlement mio::Eventd, but also starts I/O with overlapped structures on readiness request, so basicaly copy/paste code from windows/tcp.rs and modify for my need, am I right?
If so, do you accept PR that generalize windows/tcp.rs to any SOCK_STREAM and allow some kind of user defined connect and socket creation functions?

I'd recommend taking a look at mio-named-pipes which are named pipes for mio, which you'll also likely want to mirror. In general though yes, you'll want to copy code from tcp.rs and adapt it as appropriate, it won't ever be publicly exposed from mio itself.

@alexcrichton I looked at mio-named-pipes, looks a lot of code duplication
with mio/sys/windows, do you have plans refactoring?
For example, why not just call in Binding::register_socket/register_handle
approapriate schedule functions?

I don't think we are going to extract that as an official mio API. The main
reason is that it creates additional API surface to support and resources
are thin.
However. Feel free to extract those bits to another crate.
On Mon, Mar 27, 2017 at 8:40 AM Evgeniy Dushistov notifications@github.com
wrote:

@alexcrichton https://github.com/alexcrichton I looked at
mio-named-pipes, looks a lot of code duplication
with mio/sys/windows, do you have plans refactoring?
For example, why not just call in Binding::register_socket/register_handle
approapriate schedule functions?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/carllerche/mio/issues/578#issuecomment-289493070, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAYJCU3OFF5bzmAlkc-kOHBaVohMYWuks5rp9hbgaJpZM4MpV-4
.

Currently no I don't plan on deduplicating, I'd personally prefer the freedom to change TCP bindings in mio itself and then at my leisure update other bindings. Exposing an API as a public interface would require everything to change all at once (and would make it very difficult to change)

authors: Dushistov alexcrichton carllerche

repo: carllerche/mio


text:
Remove Selector/Io from public API

(discussed on IRC)

er, looks like this is needed as public for the Evented trait currently, will have to figure out something else later.

source: gharchive/pull-request

license: mit

license_type: permissive

license_source: bigquery


text:
🛑 Page Colombia is down

In 40bdcd9, Page Colombia (https://pinbus.com) was down:

HTTP code: 503
Response time: 345 ms

Resolved: Page Colombia is back up in 712d999.

source: gharchive/issue

repo: carlosmathiasen/pinbus-status

license: MIT

license_source: github-api


text:
Test Jira Remote Link

test with CCD-1 issue

CCD-1

repo: carlsberg/gh-releaser


text:
ref(consent): Polish how consents are displayed.

Please delete this line and the text below before submitting your contribution.

Thanks for contributing! If this contribution is for instructor training, please send an email to checkout@carpentries.org with a link to this contribution so we can record your progress. You’ve completed your contribution step for instructor checkout just by submitting this contribution.
Please keep in mind that lesson maintainers are volunteers and it may be some time before they can respond to your contribution. Although not all contributions can be incorporated into the lesson materials, we appreciate your time and effort to improve the curriculum.  If you have any questions about the lesson maintenance process or would like to volunteer your time as a contribution reviewer, please contact The Carpentries Team at team@carpentries.org.

Applied dropdown changes on the Actions required page

repo: carpentries/amy


text:
Top tabbed menus do not work on mobile

See a page like test Carpentries site or test Data Carpentry site.
On desktop, we see four tabs across the top (The Carpentries, Data Carpentry, Library Carpentry, Software Carpentry). On mobile, we only see The Carpentries, regardless of what site we are on.  It looks like it is supposed to have a drop down menu but that does not seem to work.

@maneesha is the prototype site still available so I can see how this worked on there? I may be using the wrong URL, but I'm not able to get there.

We don't know if it ever worked.  We were not able to test it until we had the packaged theme as we could not apply the theme to the other sites.
This is the original rendered site built from this repo that had theme & content bundled together.

Okay, I was hoping to see how the bootstrap / jekyll handled it. I'll add a simple dropdown

This dropdown is in place on mobile

This still seems a little buggy.
I can now get the drop down menu to show up, but for example:
From https://carp-new-website.netlify.app/, I click on the menu, get the dropdown menu.  I choose "Data Carpentry" and as expected am taken to https://dc-new-website.netlify.app/.  However, "The Carpentries" still displays.  If I click on the menu again, the dropdown flashes for a second, and then I am taken straight back to The Carpentries. Now I can again click on the menu and choose something else, and then the same thing happens.

@maneesha did you run a hugo mod get on all your projects? Seems like you need to get those themes updated as well..

@AdamChlan  I have updated the theme on all the project sites and am still seeing this behavior (on my actual phone and emulating various mobile devices using browser inspector).

Removing "Ready for Review" label as this needs work.

@regisphilibert any thoughts as to why the theme is not updating across all existing site?

Can you share your project's repos @maneesha ?

All three sites can be viewed starting from here () and using the tabbed navigation across the top.
Repos:

The Carpentries
Data Carpentry
Library Carpentry
Software Carpentry

@maneesha I can see the god.mod file reference to the theme is different on the two first repos:
The Carpentries: require github.com/carpentries/carpentries-hugo-theme v0.0.0-20240904125853-956418c4b68e // indirect
Data Carpentry:     require github.com/carpentries/carpentries-hugo-theme v0.0.0-20240830151959-f8a03802275f // indirect
I think the last part of the string is the commit hash.
Have you committed the two files updated by the hugo mod get command  as explained here ?

The theme has been updated on all four sites (repos above).  I am still experiencing the same behavior with the menu not working correctly.

Same behaviour would mean that it's only working on The Carpentries? And not working on all 3 other sites?
If yes, is the fontawsome (#21)  thing working on all 4 sites now?

I closed #21 because it turned in to being about mixed markdown/html content, and that has been resolved.

As for the menus on mobile, it still is not working.
Try going to any of the following sites on a mobile device or emulating a mobile device on desktop, and you'll see it always displays only "The Carpentries" on top.  Clicking on that usually gives the drop down menu and lets you successfully select one of the other sites, but then "The Carpentries" is still displayed.  Font styles change but "The Carpentries" menu display remains.

The Carpentries
Data Carpentry
Library Carpentry
Software Carpentry

Okay I will take a look

@maneesha I adjusted this menu so that the active site name is always on top, and acts as the trigger for the dropdown menu

Looks good, thanks!

authors: AdamChlan maneesha regisphilibert

repo: carpentries/carpentries-hugo-theme


text:
Base Interface Change

Here's a quick proposal for a change to our base interface... I've chatted with @rmfarrell, and he has also independently come up with this solution, as he's run into the same exact problem with our base interface.
Currently
Currently, our base interface is this:
{
    "success": true,
    "status_code": 200,
    "status_text": "OK",
    "error_details": [
        {
            "code": 1,
            "text": "Invalid email"
        }
    ],
    "content": {
        // ...
    }
}

I've not run into many problems with this base interface in use, but documenting this base interface in swagger is extremely repetitive, due to the lack of flexibility of json-ref (not to the fault of json-ref, it's just how it is).
Currently, for documenting an endpoint swagger documentation ends up looking like something like this:
get:
  tags:
  - Applications
  summary: Index
  description: Fetches and displays all applications.
  produces:
  - application/json
  responses:
    200:
      description: OK
      schema:
        type: object
        properties:
# ----------------------------------------
          success:
            type: boolean
          status_code:
            type: integer
          status_text:
            type: string
          error_details:
            type: array
            items:
              $ref: '#/definitions/ErrorDetail'
# ----------------------------------------
          content:
            type: array
            items:
              $ref: '#/definitions/Application'

Proposal
If we wrap all of the non-content information in a meta object, we'll be able to use a json-ref for all of its content.
{
    "meta": {
        "success": true,
        "status_code": 200,
        "status_text": "OK",
        "error_details": [
            {
                "code": 1,
                "text": "Invalid email"
            }
        ]
    },
    "content": {
        // ...
    }
}

Then our swagger for each endpoint would look something more like this
get:
  tags:
  - Applications
  summary: Index
  description: Fetches and displays all applications.
  produces:
  - application/json
  responses:
    200:
      description: OK
      schema:
        type: object
        properties:
# ----------------------------------------
          meta:
            $ref: '#/definitions/Meta'
# ----------------------------------------
          content:
            type: array
            items:
              $ref: '#/definitions/Application'

a bit of a digression but have we investigated (and subsequently dismissed) this existing spec - http://jsonapi.org/ ?

This might be totally too far of a tangent, but this seems like it would be a really great candidate for GraphQL ✨

@kylemac I've totally checked it out recently actually.
This change was largely brought back into my mind because of the readings from there.
Beyond the value of matching an existing specification, I didn't find any additional value in switching to match anything else from that spec (beyond this).

@BrandonRomano that's enough for me. just wanted to be sure we weren't looking past it

Nope, I still to plan to go through it again with a fine-tooth comb, and I will close out #7 once I end up doing that.
I did a high level sweep of it last week during some down-time

But, in short it felt the JSON API specification seemed to trade a lot of fluency for standardization, which IMO wouldn't be a win for us.  It was particularly specific on how you should define relationships and your data.

👍 from me. Makes sense

@tmilewski, thoughts?  Want to get a unanimous decision on this one before I go and do this

authors: BrandonRomano jescalan kylemac

repo: carrot/restful-api-spec


text:
SourcePlugin is not a function

I have my plugins set up as described in the README of this project, but I'm getting the following error:
/Users/frederikcreemers/dev/motocargo/frontend/webpack.config.js:34
            new SourcePlugin()
            ^

TypeError: SourcePlugin is not a function
    at Object.<anonymous> (/Users/frederikcreemers/dev/motocargo/frontend/webpack.config.js:34:13)
    at Module._compile (module.js:399:26)
    at Object.Module._extensions..js (module.js:406:10)
    at Module.load (module.js:345:32)
    at Function.Module._load (module.js:302:12)
    at Module.require (module.js:355:17)
    at require (internal/module.js:13:17)
    at module.exports (/Users/frederikcreemers/dev/motocargo/frontend/node_modules/webpack/bin/convert-argv.js:80:13)
    at Object.<anonymous> (/Users/frederikcreemers/dev/motocargo/frontend/node_modules/webpack/bin/webpack.js:39:40)
    at Module._compile (module.js:399:26)
```

I also got an unmet peerdependency when installing the sourceplugin:

    carte-blanche-source-plugin@0.1.0 requires a peer of carte-blanche@^0.1.0 but none was installed.

I'm using carte-blanche@0.2.3, so I suspect the source plugin has not been updated to the latest carte blanche v&ersion. Is this the problem, or am I doing something wrong?

Yeah that is a bug, we need to cut a new release! Meanwhile, can you see if new SourcePlugin.default() works?

authors: bigblind mxstbr

repo: carteb/carte-blanche


text:
🛑 Baliz is down

In 375027e, Baliz (https://baliz.cartelmatic.com/) was down:

HTTP code: 503
Response time: 623 ms

Resolved: Baliz is back up in 2db01a0 after 13 hours, 32 minutes.

repo: cartelmatic/upptime


text:
installation of 10 packages concurrently forces GKE control plane autoscaling

What steps did you take:
Reported from other users:
Installed kapp-controller (as a part of a larger product, TAP) on a new GKE cluster.
What happened:
During the installation, the Kubernetes control plane became unavailable for several minutes. This caused package installs to enter a ReconcileFailed state. Eventually, when the API server became available, packages reconciled again to completion.
What did you expect:
The installation works without any control plane unavailability.
Anything else you would like to add:

This identified behavior may happen on newly provisioned clusters that have not gone through GKE API server autoscaling (API server sizing in GKE is automatic, non-configurable, and is not determined based on size or number of nodes). Once GKE scales up the API server, the current install will continue and any subsequent installs succeed without interruption. Could this be improved by adjusting the kapp-controller's concurrency config (default is 10, what if we reduced it to 5)?
If it's difficult to replicate with minimal components (such as kapp-controller on its own), try larger distributions (such as TAP).

Environment:

kapp Controller version: v0.30.0 (latest)

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

I think a logical next step here would be two try and reproduce this with kapp-controller itself on GKE.
We should also test with TAP to verify any fix works as expected.

Could this be improved by adjusting the kapp-controller's concurrency config (default is 10, what if we reduced it to 5)?

A note here that this is current configurable via a kapp-controller flag: https://github.com/vmware-tanzu/carvel-kapp-controller/blob/1ad808d8909d49f0dff35ee49d285fb5f0e4693f/cmd/main.go#L25

@cppforlife filed a support ticket with GCP and this was the response:

GKE autoscales control plane -- not a configurable thing. so question becomes can we find that threshold (and potentially avoid hitting) after which GKE decides to scale.

One potential solution to this would be documenting kapp-controlller installation on GKE and advising to set concurrency to a lower amount (e.g. 5). This way we could still keep current default of 10.

^ do we know that 5 for example, "fixes" the behaviour?

I believe this is just the accepted behaviour of GKE. We cannot change it as the main nodes are scaled and managed by google. Anything further ? @cppforlife

authors: aaronshurley cppforlife danielhelfand neil-hickey

repo: carvel-dev/kapp-controller


text:
Project Initialized

I have created .NET C# library project and Unit Test Project for EF-Adapter.I can work more on as per the guidance.

@huazhikui @xcaptain @xgenvn @nodece please review.

It's just a project setup, doesn't contains implementations yet. The project structures looks fine, I think we can merge it first and let @AaqibAhamed add more features in the future.

It's just a project setup, doesn't contains implementations yet. The project structures looks fine, I think we can merge it first and let @AaqibAhamed add more features in the future.

Yes.You are right.I just initiated project setup.I will work in the future .

It's just a project setup, doesn't contains implementations yet. The project structures looks fine, I think we can merge it first and let @AaqibAhamed add more features in the future.
@hsluoyz @xcaptain
Once after the PR merged only I can work on  more.If any issue with this I can revoke without any conflict.

@hsluoyz I don't have merge permission for this project, can you merge it.

@xcaptain @hsluoyz please do the needful.Merge or Reject ?

I think it's better to have the working code PR directly.

authors: AaqibAhamed hsluoyz xcaptain

repo: casbin-net/EF-Adapter


text:
go get github.com/casbin/ent-adapter  error

go: downloading github.com/casbin/ent-adapter v0.0.2
go: downloading github.com/jackc/pgx/v4 v4.11.0
go: downloading github.com/mattn/go-sqlite3 v1.14.6
go: downloading github.com/jackc/pgconn v1.8.1
go: downloading github.com/jackc/pgtype v1.7.0
go: downloading github.com/mattn/go-sqlite3 v1.14.7
github.com/mattn/go-sqlite3
cgo: exec gcc: exec: "gcc": executable file not found in %PATH%

@closetool

repo: casbin/ent-adapter


text:
docs: add sdk intro page

Signed-off-by: sh1luo 690898835@qq.com

@sh1luo add screenshot pictures, give default values or example values for each field.

@sh1luo add screenshot pictures, give default values or example values for each field.

@hsluoyz ok, but where to store the screenshot picture file, static?

@sh1luo just inside this repo, see the user images: https://casbin.org/en/users

@sh1luo just inside this repo, see the user images: https://casbin.org/en/users

ok, working on it.

@sh1luo any update?

@sh1luo any update?

@hsluoyz Done.

repo: casdoor/casdoor-website


text:
WS-fed protocol

Greetings!
Please add WS-fed protocol for Outlook Web Access (OWA) and Sharepoint auth in casdoor.

@AleksEmel hi, can you give more details?

authors: AleksEmel hsluoyz

repo: casdoor/casdoor


text:
The pricing page not working properly

The Pricing page is not working properly neither: if we clic on any plan of the Pricing Page (even on the Demo site, or on a live site too), the link forward the return URL of the product, but not to the product page itself.
So, that makes it impossible to pay a subscription...

My mistake. User should create an account or login before to access to the product page...

Closed as resolved

authors: hsluoyz pzguillaume


text:
Colorpicker as component

Is there a way to get this as a component?
Where you can pass a onClick and a value

Yep! You can find more details here http://casesandberg.github.io/react-color/#create-helpers.
You can use just the Saturation component.

authors: KevinDenys casesandberg

repo: casesandberg/react-color


text:
PROPOSAL: Autogenerated Documentation

I'm thinking of two possibilities or simultaneous:
MINI (Just update a section of a markdown readme doc)
Allow Justfile to search though an existing markdown (or html document) and locate specific 'justfile' tag that allows just to do a replace operation on it. The replaced section is similar to when calling just --list but in a more detailed manner (e.g. expected arguments and examples)

recipes
description

build
build stuff

test
test stuff

Plus you could have each [build](JUSTDOC.md#build) recipes point to a JUSTDOC.md (if full documentation is enabled)
FULL (Create an entire autogenerated documentation page with all the recipes and how to use it)
Full autogenerated markdown documentation of every command that can be invoked by the user (Maybe with categories like, maintainers, developers, user etc...) based on the comments
- This would also provide the opportunity to creating a visual graph of dependencies of each recipes, so readers can at a glance see what each recipes will also trigger... (e.g. build will call 'environment_setup' and 'compile' and 'package'). (You might want to allow allow for marking some form of hashtag, so that we show only the most relevant connections. e.g. #buildsystem should not show the logger module, only connection to compile and other relevant recipes)
- Maybe clicking on a dependency module would also jump to that relevant recipes in the doc
graph TD;
    build-->environment_setup;
    build-->compile-->test;
    build-->package;

Discussed in https://github.com/casey/just/discussions/2030

Originally posted by mofosyne May 14, 2024
Maybe have <!-- just doc start --> start and end tags and replace it with an autogenerated document of all available commands?

@casey stance on this proposal

Generating a markdown document with all the commands would be super easy, so I wouldn't be opposed to it, but I would want to get some feedback that this was something that multiple users wanted. Could you create an issue? It's likely to get more comments as an issue, I think.

Not intending to implement this yet, so others are free to take the mantle of responsibility here.

There is a just --dump --dump-format=json | jq that outputs some json describing the Justfile. I'd suggest separating the concerns: a markdown documentation should be a separate tooling that consumes that json.
And I'd be rather curious to see a toy example of this experimented upon. I've got a similar situation: rustdoc generates json, and no text based (markdown or otherwise) for rust code documentation has been implemented, as far as I know. Being a terminal fundamentalist, whatever is done to generate markdown doc from that kind of json would interest me.
But I'd rather have that as a separate tooling from just. Some justdoc tool that would consume the json would fit my taste more than having that kind of code in just itself.

Yeah. I think the issue is that the Json format is not quite stable. Also a bit hard for me to interpret how I would format the content.
Could you write a hypothetical snippet markdown document of what would be useful? I think ideally we would have a quick reference table then sub section covering each command and what you can do with it or something.
It's clear we can't just show name but maybe we need to provide command examples or something.

@mofosyne Naively, I believe you should use jq to preprocess the json and leave it only a format that could fed to some kind of tera templating engine. I do not see the tera crate providing any kind of cli, but I believe a minimalistic piece of code that can be fed json from stdin and piped to an executable that puts it in some markdown template could perhaps hack the job away.
Pseudo-shell-code:
just --dump --dump-format=json | jq -r cat preprocess.jq | tera-executable markdown-template
Wrapping that up in some executable script.
My 2 cents.
But I'm not working on that at the moment.

If you're experimenting, you might look into writing a simple Pandoc "reader" in Lua. Here's an example.
A more direct approach JSON-formatted Pandoc AST directly, e.g. with this crate. If this were added to just it might look like this:
just --dump --dump-format=pandoc | pandoc --from=json --to=markdown > doc.md

I'd advise jless to dive into the json. Whether that be for just json output or (in my case, rustdoc json output).
https://github.com/PaulJuliusMartinez/jless

I've managed to make a justfile that reorders the json and outputs roff and texinfo using a tera cli crate for templating. Trying to make it a bit more self-contained, and it may help out.

Did someone say "quick and dirty"?  This shows the graph of dependencies, which I realized I really wanted, even though my justfile is fairly simple.
The subprocess.run(["open"... is specific to MacOS, but the rest should be portable.
(@mofosyne asked to see this)
import json
import subprocess
import tempfile

def main():
    json_output = subprocess.run(
        ["just", "--dump", "--dump-format", "json"],
        check=True,
        capture_output=True,
    ).stdout

    with tempfile.NamedTemporaryFile(suffix=".svg") as tmpfile:
        reader_proc = subprocess.Popen(["dot", "-Tsvg"], stdin=subprocess.PIPE, stdout=tmpfile)

        reader_proc.stdin.write(b"digraph G {")

        data = json.loads(json_output)
        recipes = data["recipes"]

        for recipe_name, stuff in recipes.items():
            dependencies = [d["recipe"] for d in stuff["dependencies"]]
            for d in dependencies:
                reader_proc.stdin.write(f'"{recipe_name}" -> "{d}"'.encode())

        reader_proc.stdin.write(b"}")

        reader_proc.stdin.close()
        reader_proc.wait()

        subprocess.run(["open", "--wait-apps", tmpfile.name])

Output from the above:

@offby1 attempted to replicate, but had to adjust it a bit
#!/usr/bin/env python3
# python3 dotgen.py | dot -Tsvg >> justfile.svg
import json
import subprocess

json_output = subprocess.run(
    ["just", "--dump", "--dump-format", "json", "--unstable"],
    check=True,
    capture_output=True,
).stdout

print("digraph G {")
data = json.loads(json_output)
recipes = data["recipes"]
for recipe_name, stuff in recipes.items():
    dependencies = [d["recipe"] for d in stuff["dependencies"]]
    for d in dependencies:
        print(f'"{recipe_name}" -> "{d}"')
print("}")

Rendered against, this just repo's justfile for extra example of how it looks like

Might need to think it though a bit more before using this, as it's not obvious how useful a graph would be in documentation context.

@offby1
Oh, but it works well with mermaid so that's a plus
#!/usr/bin/env python3
# python3 mermaidgen.py | mmdc -i - -o /tmp/output.png ; xdg-open /tmp/output.png
import json
import subprocess

json_output = subprocess.run(
    ["just", "--dump", "--dump-format", "json", "--unstable"],
    check=True,
    capture_output=True,
).stdout

print("graph TD")
data = json.loads(json_output)
recipes = data["recipes"]
for recipe_name, stuff in recipes.items():
    dependencies = [d["recipe"] for d in stuff["dependencies"]]
    for d in dependencies:
        print(f'    {recipe_name} --> {d}')

graph TD
    check --> fmt
    check --> clippy
    check --> test
    check --> forbid
    ci --> build-book
    polyglot --> _python
    polyglot --> _js
    polyglot --> _perl
    polyglot --> _sh
    polyglot --> _ruby
    pr --> push
    push --> check
    view-man --> man

#!/usr/bin/env python3
# python3 mermaidgen.py | mmdc -i - -o /tmp/output.png ; xdg-open /tmp/output.png
import json
import subprocess

json_output = subprocess.run(
    ["just", "--dump", "--dump-format", "json", "--unstable"],
    check=True,
    capture_output=True,
).stdout

data = json.loads(json_output)
recipes = data["recipes"]

print("# justfile autogenerated documentation")

print("## recipe list")
print("")

for recipe_name, stuff in recipes.items():
    if stuff["doc"] is not None:
        print(f"- `{recipe_name}`: {stuff['doc']}")
    else:
        print(f"- `{recipe_name}`")

print("")
print("## not simple recipes")

for recipe_name, stuff in recipes.items():
    if stuff["doc"] is None and len(stuff["parameters"]) <= 0 and len(stuff["dependencies"]) <= 0:
        continue

    print("")
    print("---")
    print("")

    recipe_name_sig = recipe_name
    if len(stuff["parameters"]) > 0:
        recipe_name_sig += "("
        for parameter_entry in stuff["parameters"]:
            recipe_name_sig += " " + parameter_entry["name"]
        recipe_name_sig += " )"

    print(f"## <a id=\"{recipe_name}\"> {recipe_name_sig} </a>")

    if stuff["doc"] is not None:
        print(stuff.get("doc", ""))

    if len(stuff["parameters"]) > 0:
        print("")
        print("### Parameters")
        print("")
        for parameter_entry in stuff["parameters"]:
            var_type = ""
            if parameter_entry["kind"] == "plus":
                var_type = " (one or more arguments)"
            elif parameter_entry["kind"] == "star":
                var_type = " (zero or more arguments)"
            default_value = ""
            if parameter_entry["default"] is not None:
                default_value = f' = {parameter_entry["default"]}'
            print(f'* {parameter_entry["name"]}{var_type}{default_value}')

    if len(stuff["dependencies"]) > 0:
        print("")
        print("### Call Graph")
        print("")
        print("```mermaid")
        print("graph LR")

        def call_graph_gen(recipe_name):
            if recipe_name not in recipes:
                return
            stuff = recipes.get(recipe_name)
            dependencies = [d["recipe"] for d in stuff["dependencies"]]
            for d in dependencies:
                print(f'    {recipe_name} --> {d}')
                print(f'    click {d} "#{d}"')
                call_graph_gen(d)

        call_graph_gen(recipe_name)
        print("```")

    print("")

Okay put in more effort to try and make a proof of concept justfile autodoc creator in this gist https://gist.github.com/mofosyne/fd6a43116c9e1e224ff1bd8f7068c662 . It should be usable now.
But I still hope we can integrate this into justfile so it's something that will always be available.
One thing I do notice, is we don't really provide a method to explain the meaning of each arguments.

authors: gl-yziquel mofosyne offby1 starthal

repo: casey/just


text:
Enable fish to complete recipes in modules

Hi, thanks for making just. One of the big reasons for me to use it is because of the completions. However, recipes in modules aren't completed at all (in fish), so I basically didn't use that feature.
I ended up writing the completions for that myself. I have them checked into my dotfiles now, so merging this PR isn't urgent for me. I thought I'd share it in case it is deemed useful for others.
It's quite a bit more verbose, but I didn't find a way to make it more concise without also making it more obtuse and hard to understand.
I should also say that this logic parses the output of:
just --list \
     --list-heading='' \
     --list-prefix='>' \
     --list-submodules

I might have missed some edge cases of that output format if it's related to a feature I personally don't use. For example, I haven't used groups so far, I only noticed my lack of handling [group_name] headers when I tried out my completions on the just repo itself. Recipe arguments and descriptions should be handled the same way as the existing completions.

Nice! Can you use just --summary instead, which doesn't have any formatting?

Wow, that's so much simpler! 👍
This approach does lose hints for the recipe arguments and description, but I don't think it's a big loss.

Hmm, it's unfortunate to lose recipe arguments and descriptions, but I do think overall it's an improvement to be able to complete recipes in modules.

authors: casey senekor


text:
sqs: each job handler gets its own trace

We want each sqs job handled to have its own trace. This previously
worked properly while we used jaeger, assuming that by submitting tasks
to the handler thread pool does not propagate any existing trace.
However, now that we switched to datadog, it actually automagically uses
code generation to propagate traces across asynchronous execution
boundaries. So now the receiver scheduling thread becomes one giant long
trace that includes every job.
See https://github.com/DataDog/dd-trace-java/tree/master/dd-java-agent/instrumentation/java-concurrent/src/main/java/datadog/trace/instrumentation/java/concurrent
This change forces a new root span for each job.

datadog scares me

repo: cashapp/misk


text:
Add websocket hot reloading

Adds websocket hot reloading for Android. Shaves 400-500ms off of hot reload times. For now leaving iOS as 500ms polling but will follow-up with another PR once that's working.
Note that right now there is no websocket on the server. This code will fallback to 500ms polling when we can't connect to a websocket, but also tries to make a websocket connection on each poll, in case the websocket is only down temporarily (e.g. in the case of a dev leaving emulator running, stopping hot reload server, then restarting, we want to make sure we always upgrade to websocket where possible to get the fastest speeds).

Looks like MockWebServer doesn't have proper support for testing websockets (or at least I couldn't figure it out), so I'll just merge and try to talk to Jesse when he's back to see if there's a different way to test this.

repo: cashapp/redwood


text:
Removing guard from execute block with action :nothing

This is fine, since "mkdir -p" and the "chmod" and "chown" commands are idempotent.

:+1:


text:
jetbrains EAP downloads fail with a 403

It seems you need to be logged in to download EAP versions of intellij, pycharm, etc.
$ brew cask install intellij-idea-eap
==> Downloading https://download.jetbrains.com/idea/ideaIU-142.4465.2-custom-jdk-bundled.dmg
######################################################################## 100.0%
curl: (22) The requested URL returned error: 403 Forbidden
Error: Download failed on Cask 'intellij-idea-eap' with message: Download failed: https://download.jetbrains.com/idea/ideaIU-142.4465.2-custom-jdk-bundled.dmg

Cask is working fine, this was either temporary or something in your setup.
Do you have a custom .curlrc? Because that is by far the most common cause.

No .curlrc that I can find, are there any other known causes?

Have you rechecked? Try rm -rf "$(brew --cache)"; brew update; brew cask install intellij-idea-eap.

trying that now, but the vanilla curl command isn't working for me either.
curl -Lv -O https://download.jetbrains.com/idea/ideaIU-142.4465.2-custom-jdk-bundled.dmg
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 54.225.64.222...
* Connected to download.jetbrains.com (54.225.64.222) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
* Server certificate: download.jetbrains.com
* Server certificate: thawte EV SSL CA - G3
* Server certificate: thawte Primary Root CA
> GET /idea/ideaIU-142.4465.2-custom-jdk-bundled.dmg HTTP/1.1
> Host: download.jetbrains.com
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 302 Moved Temporarily
< Server: nginx
< Date: Thu, 07 Jan 2016 01:37:31 GMT
< Content-Type: text/html
< Content-Length: 154
< Connection: keep-alive
< Location: https://d1opms6zj7jotq.cloudfront.net/idea/ideaIU-142.4465.2-custom-jdk-bundled.dmg
<
* Ignoring the response-body
{ [154 bytes data]
100   154  100   154    0     0    313      0 --:--:-- --:--:-- --:--:--   313
* Connection #0 to host download.jetbrains.com left intact
* Issue another request to this URL: 'https://d1opms6zj7jotq.cloudfront.net/idea/ideaIU-142.4465.2-custom-jdk-bundled.dmg'
*   Trying 205.251.203.145...
* Connected to d1opms6zj7jotq.cloudfront.net (205.251.203.145) port 443 (#1)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *.cloudfront.net
* Server certificate: Symantec Class 3 Secure Server CA - G4
* Server certificate: VeriSign Class 3 Public Primary Certification Authority - G5
> GET /idea/ideaIU-142.4465.2-custom-jdk-bundled.dmg HTTP/1.1
> Host: d1opms6zj7jotq.cloudfront.net
> User-Agent: curl/7.43.0
> Accept: */*
>
< HTTP/1.1 403 Forbidden
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Connection: keep-alive
< Date: Thu, 07 Jan 2016 01:37:31 GMT
< Server: AmazonS3
< X-Cache: Error from cloudfront
< Via: 1.1 a88de2be371f2603ffe3f00c013af6c4.cloudfront.net (CloudFront)
< X-Amz-Cf-Id: k7_5Dg8ni4WY5nvLYxU86kWozIwkEBqxkxe56kftWtNahkjBjcEvhA==
<
{ [249 bytes data]
100   243    0   243    0     0    184      0 --:--:--  0:00:01 --:--:--   184
* Connection #1 to host d1opms6zj7jotq.cloudfront.net left intact

blowing away cache has the same 403 result.

just for fun with wget
wget https://download.jetbrains.com/idea/ideaIU-142.4465.2-custom-jdk-bundled.dmg
--2016-01-06 17:42:00--  https://download.jetbrains.com/idea/ideaIU-142.4465.2-custom-jdk-bundled.dmg
Resolving download.jetbrains.com (download.jetbrains.com)... 54.225.64.222
Connecting to download.jetbrains.com (download.jetbrains.com)|54.225.64.222|:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://d1opms6zj7jotq.cloudfront.net/idea/ideaIU-142.4465.2-custom-jdk-bundled.dmg [following]
--2016-01-06 17:42:00--  https://d1opms6zj7jotq.cloudfront.net/idea/ideaIU-142.4465.2-custom-jdk-bundled.dmg
Resolving d1opms6zj7jotq.cloudfront.net (d1opms6zj7jotq.cloudfront.net)... 205.251.203.232, 205.251.203.141, 205.251.203.111, ...
Connecting to d1opms6zj7jotq.cloudfront.net (d1opms6zj7jotq.cloudfront.net)|205.251.203.232|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2016-01-06 17:42:02 ERROR 403: Forbidden.

Reopening in case some other maintainer can reproduce (I’m currently taking care of updating a bunch of casks, so can’t give this my full attention), but it is extremely likely it is only on your end.

I was unable to reproduce this issue on a clean install of OS X, so it looks like this is a local issue.

I can successfully curl and wget the url, for what it's worth.

@NorthIsUp closing the issue as it seems like you have gotten everything working. Let us know if that is not the case.

authors: NorthIsUp adityadalal924 vitorgalvao

repo: caskroom/homebrew-cask


text:
Add Inpad v0.1.0

If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked that the cask was not already refused in closed issues.

Ping @vitorgalvao RE https://github.com/caskroom/homebrew-cask/issues/28220.

Ping @vitorgalvao RE https://github.com/caskroom/homebrew-cask/issues/28220.

Consensus so far was 10 stars, so lets merge it.

Thanks for approving! Have a nice day. 😄

authors: Sarah-Seo miccal vitorgalvao


text:
Update tankix to 635

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as cdc5da86f47fbba55cf27262bcc2a37bcbaf7f61. Your contribution is still credited to you.

authors: giannitm vitorgalvao


text:
Add Godot Mono.app v3.0.2

Godot has a separated build which supports C# Mono runtime, add a new cask which supports the stable version of it.

Duplicate of https://github.com/caskroom/homebrew-cask/pull/44709

authors: Sposito commitay


text:
Update Sketch Beta.app to latest version

After making all changes to the cask:

[X] brew cask audit --download {{cask_file}} is error-free.
[X] brew cask style --fix {{cask_file}} reports no offenses.
[X] The commit message includes the cask’s name and version.

Thank you for your PR! Closing in favour of https://github.com/caskroom/homebrew-versions/pull/4363

authors: commitay vinkla

repo: caskroom/homebrew-versions


text:
Query Global State by Contract Package Hash.

About These Changes
This PR makes it possible to use contract package hashes when querying global state.
If you use a query path based on a contract package, the query will look for named keys in the latest version of the contract inside the contract package.

Modifies the query function in tracking_copy/mod.rs.
Introduces a new smart contract for testing: set-named-key-stored.
closes #1931

@EdHastingsCasperLabs : working as intended.

repo: casper-network/casper-node


text:
Exhaustive Pattern Matching in Deserialization

Description
Improves ToBytes/FromBytes implementations so they are less likely to have bugs in them. In particular, use enums and FromPrimitive to make sure we match on all cases of the *Tag constructor. This doesn't exactly fix everything, as implementors still need to add a *Tag variant, but I believe that seeing its lack in the ToBytes implementation will cause that. I had an idea like:
enum T<A, B, C> {
  A(A),
  B(B),
  C(C),
}

but I don't know how to make it repr(u8) only when A = B = C = (). Beyond that, there's the worse problem of not being able to specify the explicit numbers corresponding to each variant in this declaration. That may be fixed by the implicit derivation of FromPrimitive, haven't checked.
Risks
Any faulty modification of the serialization layer could lead to serious bugs in the Casper Network, its users' code, or in any of our tooling.
Issue
https://github.com/casper-network/casper-node/issues/2329

Closing due to work on consensus taking precedent.


text:
query-balance -> get-balance

casper-client query-balance does not exist, changed it to get-balance and tested successful.

Thanks for the PR, however the query-balance exists in the Rust client on the dev branch.  Generally the casper-client's dev branch is kept aligned with the casper-node's dev one and once the node undergoes an upgrade, the client's dev branch will be merged to main and a new client version published.
Thanks anyway, but I'll close this unmerged.


text:
Failed to train the APNet

Following the default procedure and parameter settings, I cannot train the APNet successfully.  For different latents input, the network always produces the same result, e.g. mean face.

I tried to print the output of each layer (as shown below). It seems the network has already collapsed.

@lubovbyc It seems the optimization collapsed. I'm not sure. Have you tried other losses, such as the PDC loss, VDC loss ? You may combine all losses or try another optimizer. If still bugging you, please share your generated data with me, I will try it on my server.

@lubovbyc Thanks for your sharing. I will check it immediately after the Sig Asia submission. Thanks for your patience.

@lubovbyc Hi.  I have tried to alleviate this. You can add more MLP layers for the APNet and use the PDC loss to improve robustness.

@cassiePython Thanks for your reply! I will take a shot and check if working.

@lubovbyc Hi. I have tried to alleviate this. You can add more MLP layers for the APNet and use the PDC loss to improve robustness.
Can you provide the details of change to avoid the collapse. I also get the mean face according to the default code.

@cassiePython Thanks for your reply! I will take a shot and check if working.

Do you get the correct results of APNet by the advice of author?  I meet the trouble same as you

I also struggle in finding the good results of APNet. Should I use the renderer, landmark loss as well?

@lubovbyc I am still confused with the problem. I did not find problem on my dataset. I attached the dataset with 4K images and the corresponding checkpoint. Please check whether it works on your device: https://portland-my.sharepoint.com/:u:/g/personal/cwang355-c_my_cityu_edu_hk/EWMWjP8DHtpEqvhLtZTyfr0BerKDVixlbx8zApUS3QTngA?e=GXsNKw.

I also struggle in finding the good results of APNet. Should I use the renderer, landmark loss as well?

Before using the pseudo gt to train the APNet, I have tried the combination of the rendered loss and the landmark loss. Unfortunately, I fail to train the APNet.
But I have not tried the WPDC loss plus the rendered loss and the landmark loss.

@lubovbyc I am still confused with the problem. I did not find this problem on my dataset. I attached the dataset with 4K images and the corresponding checkpoint. Please check whether it works on your device: https://portland-my.sharepoint.com/:u:/g/personal/cwang355-c_my_cityu_edu_hk/EWMWjP8DHtpEqvhLtZTyfr0BerKDVixlbx8zApUS3QTngA?e=GXsNKw.
Besides, first, please try adding the PDC loss.

Using the model and data provided by you, I still get the same face for different latent code. However, there is a change that the render face is not the mean face using your model.

@roundchuan
Can you get results like this:

@roundchuan Can you get results like this:

No, Just like this

@roundchuan Can you get results like this:

@roundchuan Can you get results like this:

No , all the render faces are the same. And I print the "param_lst" the output of APNet are all the same.

I also struggle in finding the good results of APNet. Should I use the renderer, landmark loss as well?

Before using the pseudo gt to train the APNet, I have tried the combination of the rendered loss and the landmark loss. Unfortunately, I fail to train the APNet.
But I have not tried the WPDC loss plus the rendered loss and the landmark loss.

The results are just like this follow your data and checkpoints.

@lubovbyc I am still confused with the problem. I did not find this problem on my dataset. I attached the dataset with 4K images and the corresponding checkpoint. Please check whether it works on your device: https://portland-my.sharepoint.com/:u:/g/personal/cwang355-c_my_cityu_edu_hk/EWMWjP8DHtpEqvhLtZTyfr0BerKDVixlbx8zApUS3QTngA?e=GXsNKw.
Besides, first, please try adding the PDC loss.

Using the model and data provided by you, I still get the same face for different latent code. However, there is a change that the render face is not the mean face using your model.

Thanks for your kind reply. can you attach constants.pkl as well? It seems that the file is omitted

TO ALL: Recently, I generate more datasets with different sizes (e.g. 4K, 6K, 1W, 2W), and find a local minimum (e.g. the mean face) will appear during training the APNet all the time on some datasets. Before fixing this issue, you can use my pre-trained model first: https://drive.google.com/drive/folders/1qNvRu8vLPD278FW7GS-I9p6-yxYhKZY9

authors: cassiePython hxngiee lubovbyc roundchuan


text:
Cast AI setup failing

HI Team,
We are seeing failure while setting up castai-agent as :

k logs -n castai-agent castai-agent-bc568646c-dpngq
time="2023-02-08T13:39:13Z" level=info msg="running agent version: GitCommit=\"0ebd8d1fa65524cebda49b791a4e9e4a1fceb0b2\" GitRef=\"refs/tags/v0.42.1\" Version=\"v0.42.1\"" version=v0.42.1
time="2023-02-08T13:39:13Z" level=info msg="platform URL: https://api.cast.ai" version=v0.42.1
time="2023-02-08T13:39:13Z" level=info msg="starting healthz on port: 9876" version=v0.42.1
time="2023-02-08T13:39:13Z" level=error msg="agent stopped with an error: healthz server: http: Server closed" version=v0.42.1
time="2023-02-08T13:39:13Z" level=fatal msg="agent failed: getting provider: configuring aws client: getting instance region: EC2MetadataRequestError: failed to get EC2 instance identity document\ncaused by: EC2MetadataError: failed to make EC2Metadata request\nrequest blocked by allow-route-regexp \"^$\": /latest/dynamic/instance-identity/document\n\n\tstatus code: 404, request id: " version=v0.42.1

Best Regards
Ganesh Kumar

Hi @ganesh-kumarmt, sorry for late reply. The metadata endpoint access is optional. You can override all the properties that we discover through the metadata by setting the appropriate environment variables. We have a short doc describing your situation here: https://docs.cast.ai/docs/troubleshooting#your-cluster-does-not-appear-in-the-connect-cluster-screen
In short, add these environment variables to the castai-agent deployment:
- name: EKS_ACCOUNT_ID
  value: "000000000000"    # your aws account id
- name: EKS_REGION
  value: "eu-central-1"    # your eks cluster region
- name: EKS_CLUSTER_NAME
  value: "staging-example" # your eks cluster name

Also, the agent needs access to the AWS EC2 API which it uses to correctly identify node life cycle (spot or on-demand). If you have disabled EC2 auth by default for pods, then you will need to provide the agent with a way to authenticate to the AWS EC2 service. It uses the official AWS SDK so any of the AWS supported auth mechanisms should work: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-envvars.html
FYI: AWS EC2 API access is optional but if you do not provide it, then we have no surefire way to determine the life cycle of the node and if you're using spots, then we will treat them as on-demand.

Thanks @saumas
we are good with Setup Now

authors: ganesh-kumarmt saumas

repo: castai/helm-charts


text:
Building for Mac with electron-builder

We are building our app using electron-builder, signing it for distribution outside the MAS and notarizing it.
As per the instructions in the readme we are VMP-signing before code-signing. We do this by using the afterPack hook which just calls your python script from a JS function. This hook should run before code-signing and by looking at electron-builder's output the order seems to be fine.
The problem is that when running the app for some reason Widevine doesn't seem to work.
Just by simply disabling the code-signing like this we get a working build which is able to use Widevine.
Anyone knows what we're missing here?

What kind of error are you seeing? Could it be the same error as in #38?

That was it! Disabling library validation like this:
<key>com.apple.security.cs.disable-library-validation</key>
<true/>

in the entitlements file solved the problem.
Maybe we should add this to the readme? I could send a PR tomorrow.

Indeed something for the README. I was actually meaning to add it after #38 but it got lost somewhere along the way. A PR would be nice, thanks!

Yes, someone should add this to the README.  We spent a day banging our heads on this issue until I found this post :)

authors: khwaaj nickdima toschlog

repo: castlabs/electron-releases


text:
Release 5.0.0-beta001

Can we release v5?
Any outstanding issues we need to look at?
/cc @stakx, @jonorossi

Sorry @stak accidentally tagged the wrong guy! Commuting and doing github on a mobile is apparently challenging - LOL

I think the MVC facility is not publishing it's symbols. :/

@fir3pho3nixx #346 is still assigned to the milestone in GitHub, happy for the milestone to be unassigned.
Did you want to release an official "5.0.0-beta1" to nuget.org to make sure everything with packaging works well giving you an easy chance to fix before final?
I don't think there is anything else I was expecting to be in 5.0, there is always more that can be done but there is no need to hold the ASP.NET Core facility up on that.

Forgot about that one! Do you mind if I have a quick refactor just to see how big this one is, if it is tiny we should definitely try and see if we can squeeze this one in. Let me get back to you.

After re-reading the issue I remember now.
We were going to solve #346 at the surface level API's using a "Cheshire the cat" pattern. Let me put a PR together with dotMemory profiler results because we agreed to using a "copy on write" strategy here. That will hopefully inform us as to whether we can include it in this release or whether we need to do more work achieve this.
V5 on hold PR.

Did you want to release an official "5.0.0-beta1" to nuget.org to make sure everything with packaging works well giving you an easy chance to fix before final?

Yes, please.
It also gives me a chance to start drafting the solution for https://github.com/danielpalme/IocPerformance/issues/81.
I would also like to delete the copy of this facility in our code base at work. Hoping our New Relic monitoring will give us some last chance saloon for clearing things up.

@generik0, @xhafan If you can also help me validate the beta I would appreciate it heaps.
Thanks for all your help so far.

@fir3pho3nixx i Can. I will intergrate tomorrow and let it burn :-)

@fir3pho3nixx, I'm on it ;)

Works like a charm. I tested it with the latest code from https://github.com/castleproject/Windsor, master branch (commit 81fbdf084d3b6e235ff54c4f29bbc8d93fd408ec).
In my app, the middleware is registered like this:
_windsorContainer.Register(
                Component.For<IUnitOfWorkFactory>().AsFactory(),
                Component.For<TransactionScopeUnitOfWorkMiddleware>()
                        .DependsOn(Dependency.OnValue<System.Transactions.IsolationLevel>(System.Transactions.IsolationLevel.Serializable))
                        .LifestyleSingleton().AsMiddleware()
);

Windsor then creates an instance of TransactionScopeUnitOfWorkMiddleware with IUnitOfWorkFactory injected into it.

Hi
What time is the release date of the new version?

@MAliM1988
We are investigating https://github.com/castleproject/Windsor/pull/420. Once that is done, I don't see anything holding us back.
Thanks for the interest :)

/cc https://github.com/castleproject/Windsor/issues/423

/cc https://github.com/castleproject/Windsor/issues/423

State of play:

API UX fail for WindsorRegistrationOptions in #423. Should be fixed before beta.
SomeFuckedUpShitInWindsorIWantToFix in #420. Not sure what we do with this can we see what happens with typed factories first. Will update the docs for #420.

State of play:

API UX fail for WindsorRegistrationOptions in #423. @MAliM1988 closed the issue so I am adding this to aspnet vNext here(https://github.com/fir3pho3nixx/Windsor/commit/14ad698c7df4eec8fa7c231807a622467e2bec11).
After this We are mulling over deprecating Resolve(object) because it is too general and causing problems with immutability.

State of play:

API UX fail for WindsorRegistrationOptions in #423. @MAliM1988 re-opened! Awaiting PR as per comment here.

Final commits are in for #420 and awaiting review, we have deprecated object/IDictionary as parameters for IWindsorContainer.Resolve in favour of using Arguments with static factory methods instead(https://github.com/fir3pho3nixx/Windsor/blob/deprecate-resolve-with-non-generic-dictionary/docs/arguments.md).

State of play:

API UX fail for WindsorRegistrationOptions in #423. A PR has been submitted to fix this #432.

Commits for #420 and have been reviewed, and need some changes from myself.

Final commits are in for #420. Just needs squishing.
Also done some more testing with disposables.
I think we are good to release now.

@jonorossi raised some issues that need addressing on #420. I also do not think the documentation is up to scratch either. I think we should release ASP.NET Core facility in the meantime. This simply needs more time.
@jonorossi do think we can do a pre-release?

waiting for windsor 5.0.0 release！

Hi, any news on a release? I'm keen to try the new aspnet core facility.

@tapmantwo, there's still one pending PR (#440) which needs to be merged first; quoting from https://github.com/castleproject/Windsor/pull/444#issue-222732311:

[...] I'll get this merged and we can push out a beta for 5.0 with the ASP.NET Core changes.

#444 is now merged.
@castleproject/committers (just you @stakx now) is everyone happy with a 5.0.0-beta001 release?

@jonorossi - (with my best Super Mario Brothers Luigi voice:) let's-a-go!

Ran into a problem with our build scripts, I guess we haven't released a beta in a while. Looking into it now.

obj\Release\netstandard1.6\Castle.Windsor.AssemblyInfo.cs(15,59): error CS7035: The specified version string does not conform to the recommended format - major.minor.build.revision [C:\projects\windsor\src\Castle.Windsor\Castle.Windsor.csproj]
obj\Release\net45\Castle.Windsor.AssemblyInfo.cs(15,59): error CS7035: The specified version string does not conform to the recommended format - major.minor.build.revision [C:\projects\windsor\src\Castle.Windsor\Castle.Windsor.csproj]

Tagged v5.0.0-beta001
Confirmed successfully pushed to nuget.org, except Castle.Facilities.AspNetCore which unfortunately someone ("buddalasunil") has published a fork and unlisted it with the version "4.1.0". I've emailed them to get ownership transferred, will keep everyone informed on progress. (https://www.nuget.org/packages/Castle.Facilities.AspNetCore/4.1.0)
Tweeted (will do once the last package is up)

We've now got ownership of Castle.Facilities.AspNetCore and it has been pushed.
Tweeted

Renamed this issue since it isn't the final 5.0.0 release. We'll create a new issue for that later once people have had a chance to play with the bits. Please get involved if you have problems or see areas for improvements.
Thanks again to everyone that contributed to this release.

Fantastic, thank you.

authors: MAliM1988 beginor fir3pho3nixx generik0 ghost jonorossi stakx tapmantwo xhafan

repo: castleproject/Windsor


text:
Raw Fiber photometry

Fixes #49

Ahh
One impact of your frozen dependency idea will inevitably be the merge conflicts that result - though I suppose in all cases you would delegate to the changes induced by the local branch?

One impact of your frozen dependency idea will inevitably be the merge conflicts that result - though I suppose in all cases you would delegate to the changes induced by the local branch?

Hmm, yeah merge conflicts are a bit annoying...
I don't really care about what happens to frozen_dependencies.txt on merge bc it's primarily for provenance: linking the environment to each commit. When I go back and checkout a past commit, I only need the dependencies to accurately reflect the run environment for that commit -- they don't need to persist across branches during the course of development.  With that in mind, maybe we could just delete frozen_dependencies.txt on merge to avoid conflicts?

authors: CodyCBakerPhD pauladkisson

repo: catalystneuro/datta-lab-to-nwb


text:
No nested functions

Preferable IMHO to recompute 'running_octave' lots of times than risk
shared namespaces.

Aye.
By the way, would it be advantageous (more efficient) to use exist('OCTAVE_VERSION', 'builtin') over the try/catch pattern?

I think once I timed the try-catch in a loop and it was negligible but unfort didn't record it anywhere,,, :(
Also, split out an is_octave() function?

That would be a good alternative to the one-liner :+1:

ok, I'll do it


text:
Outdated color format in themes

Catppuccin themes use an old color format (example: "button.secondary.background.pressed": "ccd0da40%"). This format is deprecated and it will stop working in one of the next Fleet releases. A correct format is described here: https://www.jetbrains.com/help/fleet/modifying-theme-settings.html#supported-color-formats

Thanks for bringing this up!
Will look into updating all the colours to match

This has now been fixed!

authors: davfsa drukarev

repo: catppuccin/fleet


text:
fix: swap guifg & guibg diff colors

Hello cattppuccin maintainer(s) & users, this PR is a question/idea/suggestion for an aesthetically improved diff highlights for vim (see below for the before/after screenshots).
Let me know if this is accepted and I can apply the change to the rest of the colorscheme files.
Here is the before:

And after:

This was done because, with plugins like  vim-fugitive, you can easily see the diff display, initially it was a bit like your PR, but then it changed with this pull request

I see.
I personally prefer the foreground over background highlighting, but at this point it's a matter of preferences.
Unless we want to support these use-cases with conditional logic exposed via flag variables (eg g:diff_fg_highlighting = 0|1, g:diff_bg_highlighting = 0|1 ...etc), I don't have a strong opinion either way and will leave it up to others to make a final decision.

repo: catppuccin/vim


text:
Improve compare cell highlighting and collapsing

As a frequent user, I want the cell highlighting and collapsing to be more clever, so that I can more efficiently identify similarities and differences between two processes. Specifically, it would be nice if the following were supported:

[ ] Holding down <shift> allows for highlighting more than one cell in a table, so that we can collapse two cells on the right hand side that correspond to one cell on the left hand side.
[ ] Selecting a cell should highlight cells in the other table which have the same unit and name
[ ] Selecting a cell should highlight cells in the other table whose absolute value of the amount field is within 2% of the source's absolute value of the amount field. We need absolute value because sometimes the sign is flipped but it is actually a corresponding exchange.
[ ] Double-clicking on a cell in one table should also highlight all other cells in the same table which have the same name and unit.

That's serious. 👍
Does this 'highlighting' mean the same as 'ready to collapse'? Or another type of marking, just visual?
Should these highlightnings to be made in different colors?
Should highlightnings 2 (by unit and name) and 3 (by similar amount) to be made simultaneously? Or we need to have different modes (by switch somewhere on the page) of highlights?
For (1): how should multiple selection be started and stopped? To start, the user has to click row with the shift key (at any time, despite whether there is already a selection, or not)? Should the 'multiple' mode revert to 'single' if all entries except one are deselected? To stop he just has to click next (uselected) row without shift pressed? Or it should just cancel 'multiple' mode? But, in this case, how should we finish multiple selections (to make selected rows 'collapsed')?

Does this 'highlighting' mean the same as 'ready to collapse'? Or another type of marking, just visual? Should these highlightnings to be made in different colors?

Visual marking to help users identify, should be a different color/pattern.

Should highlightnings 2 (by unit and name) and 3 (by similar amount) to be made simultaneously? Or we need to have different modes (by switch somewhere on the page) of highlights?

They can be simultaneous, the idea is to quickly see similarities in large lists of inputs (up to 50 on each side).

how should multiple selection be started and stopped?

I think a similar pattern to other multiple selections should be possible. Basically, once you start holding down <shift> you are in multiple-selection mode. When you let it go, and rows are selected, they are collapsed into the same group. Otherwise you are in the mode we have now, which also works great.
The double-clicking doesn't need to work in multiple selection mode, this is normally one process on the left hand side and N processes with the same name on the right hand side.
Not sure <shift> is the best, but it seemed like other modification keys could be problematic as they are already used for a lot.

This would be nice to have, but is not necessary for now. Marking as won't fix for the time being.

authors: cmutel lilliputten


text:
Update Rails version compatibility in the README

Looks like the gemspec should be updated to require actionpack >=4.2 as well

Thnaks @donv I'll look into the gemspec. I need to make a new release this month.

authors: donv straydogstudio


text:
My First PR commit

PR comments

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

Needs approval from an approver in each of these files:

OWNERS

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

:star: PR built and available in a preview environment cb-kubecd-bdd-sbhg-1586947493-pr-1 here


text:
chore: bdd-sbhg-1584634006 to 0.0.1

chore: Promote bdd-sbhg-1584634006 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


text:
chore: bdd-spring-1587638396 to 0.0.1

chore: Promote bdd-spring-1587638396 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


text:
Does not display for single inputs

Single inputs, like this:
{ "text": ["t","ewcom","producers","announced"] "label": 0, "prediction": 0, "attention": [0.17704035,0.7129273,0.23426278,0.53958344] }
Are not working. However, multiple inputs are working, such as:
[{ "text": ["t","ewcom","producers","announced"] "label": 0, "prediction": 0, "attention": [0.17704035,0.7129273,0.23426278,0.53958344] }, { "text": ["t","ewcom","producers","announced"] "label": 0, "prediction": 0, "attention": [0.17704035,0.7129273,0.23426278,0.53958344] }]

Nevermind. Enclosing a square bracket around a single input works. Closing issue.

repo: cbaziotis/neat-vision


text:
IAnnotationTransformer:  Class level @Test annotoation causes "transform()" method invocation multiple times.

TestNG version - 7.5
Java version - 17.0.2
Build tool - Maven, surefire plugin version 3.0.0-M5
IDE -InteliJ
When @Test annotation is set at class level and IAnnotationTransformer interface is implemented, transform() method gets invocated multiple times. I saw the same issue had been reported before and got fixed, but it appears again.
Here is my testng.xml file content attached.

The Test Class
@Test
public class SomeTestClass {

    public void someTest() {
        System.out.println("someTest");
    }
}

IAnnotationTransformer implementation class
public class AnnotationTransformer implements IAnnotationTransformer {

    @Override
    public void transform(ITestAnnotation annotation, Class testClass,
                          Constructor testConstructor, Method testMethod) {

        System.out.println(testClass);
    }
}

And here is the output:

If using @Listeners({AnnotationTransformer.class}) instead of add listeners in xml file,  the transform seems not work.

@bj-9527

using @Listeners({AnnotationTransformer.class}) instead of add listeners in xml file, the transform seems not work.

I think that's working as designed. The documentation may have not been updated to reflect this. This is because the annotation transformer needs to run before any other annotations are processed and so it cannot be supported via @Listeners annotation (Atleast that's the rationale I remember it having as)

OK, that's reasonable, thanks for clarification.
By the way, @David91 could you please share what's the expected behavior for this test

Hi @bj-9527
The expected behavior is that transform() method should be invoked once for the class "SomeTestClass".

@David91 - Couple of questions

Do you see the same behavior when @Test is used on top of methods than types ?
IAnnotationTransformer by its behavior only mentions to the users that it can be used to alter annotations, but I don't know/remember it guaranteeing that its going to get called only once. While this expectation is valid from a user, what I want to understand is that how is this affecting your test/project ?

The implementation is such that the transformer gets called multiple times at multiple phases etc., So this could perhaps be a bit of a tricky issue to solve.

Hi @krmahadevan

For method level @Test annotation transform() method works as expected. It gets invoked once
I don't say only once in any case, but in this case, there is only one @Test annotation on top of the class, so it should be invoked once for that class.
Also here is the description of the transform() method from TestNG official doc and it clearly describes when the method should be invoked.

@David91

For method level @Test annotation transform() method works as expected. It gets invoked once

Ok in that case, a class that has only 1 @Test method should also reflect the same behaviour. If that's not what is being seen then this for sure would be a defect.

I don't say only once in any case, but in this case, there is only one @Test annotation on top of the class, so it should be invoked once for that class.
Fair expectation. I believe that there's a defect lurking there somewhere which needs to be taken care of.

Also here is the description of the transform() method from TestNG official doc and it clearly describes when the method should be invoked.

Yes, that's correct. But it doesn't call out how many times would the transform be invoked, which is what I was alluding towards :)

repo: cbeust/testng


text:
:arrow_up: update scala-library from 2.13.5 to 2.13.8

Updates org.scala-lang:scala-library from 2.13.5 to 2.13.8.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #80.


text:
Bot should allow for removal from whitelists

The bot should allow users to be removed from the whitelist

The bot was originally designed to allow people to whitelist themselves so that they could be whitelisted to a communities server without an admin being online. If I added some removal system, it would entail also adding a permission system so that users couldn't un-whitelist people they didn't like, which isn't something I have the time to do.


text:
有没有感觉v7.0.0-beta.14.3图表配色不如之前版本好看？

请问有没有什么办法可以自定义颜色？

定义不了，为了让用户降低多个产品之间切换的感受成本，新版本的配色是和 Grafana 保持一致的

repo: ccfos/nightingale


text:
issue #21: minor fixes

Very trivial changes, e.g. typo fixes, deleting csv files for lecture 1 materials, etc..

By passing branch protection as this is very trivial change (and no reviewer yet)

repo: ccjeremylo/FinEng-in-IRFX


text:
Unable to utilize --stdout flag correctly

When using the cdk8s synth --stdout command line the words "Synthesizing application" appear in STDOUT prior to the valid kubernetes manifests. This is caused by util.ts line 43. The main issue here is when you expect the following to work:
cdk8s synth --stdout | kubectl apply -f -

What you wind up with is an errror:
error: error parsing STDIN: error converting YAML to JSON: yaml: line 2: mapping values are not allowed in this context

As a work around it is easy enough to do:
cdk8s synth --stdout | grep -v 'Synthesizing application' | kubectl apply -f -

However it seems easy enough to check if stdout and skip the console.log entirely. Curious what your thoughts are here, if this change is acceptable I will open a PR shortly.

Hi @crazed - makes sense to me to disable this printout when stdout is used. Would gladly accept a PR 👍

authors: crazed iliapolo


text:
fix: imports strip out enums with spaces

Fixes #108
When importing some CRDs, it's possible for enums to have spaces, which are currently getting stripped to minimize the potential security risks for code that is parsing and manipulating manifest definitions. To minimize the scope of the changes, I only allow-listed spaces (and not all kinds of whitespace characters), and only allow-listed them within values (and not in keys).

@iliapolo curious if you had a chance to revisit this yet?
My understanding is that the reviver option in JSON.parse is just one convenient way of performing transformations on objects before it gets returned. Since it doesn't provide the kind of granularity we want, would it be ok if we instead ran our own hand-written JSON transformer on parsed objects instead?
How the transformation works is open-ended, but one option could be to use a modified variation of the JSON reviver algorithm that provides (path, value) pairs instead of (key, value) pairs, which would resolve the limitations I brought up in https://github.com/cdk8s-team/cdk8s-cli/pull/109#discussion_r740534995

@Chriscbr

My understanding is that the reviver option in JSON.parse is just one convenient way of performing transformations on objects before it gets returned. Since it doesn't provide the kind of granularity we want, would it be ok if we instead ran our own hand-written JSON transformer on parsed objects instead?

Yes, thats exactly what we should do. Wanna give it a shot? I'm perfectly fine with just running JSON.parse without a reviver, and then running our own traversal (and mutation) logic on the parsed object.

Keep. We'd need to implement this using the approach mentioned here..

authors: Chriscbr iliapolo


text:
chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1340

Questions ?
Please refer to the Backport tool documentation


text:
chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 1799

Questions ?
Please refer to the Backport tool documentation


text:
Switch main repository branch from master to main

Description of the bug:

Reproduction Steps:

Error Log:

Environment:

Framework Version:
OS:

Other:

This is :bug: Bug Report

Keep

authors: Chriscbr campionfellin


text:
Submodule pages not rendered

Page of CDKTF Instance
URL= https://constructs.dev/packages/@cdktf/provider-aws/v/12.0.4?submodule=instance&lang=typescript
shows empty

Also applies to later versions and other submodules

It's been like this for a long time now
https://github.com/cdklabs/construct-hub/issues/1039

Because of this PR https://github.com/cdklabs/construct-hub/pull/1007

https://constructs.dev/packages/@cdktf/provider-aws/v/10.0.11/api/FlowLog?lang=typescript does not work I believe your internal tooling may have broken :( Thanks!
What is the URL of the page with the issue? https://constructs.dev/packages/@cdktf/provider-aws/v/10.0.11/api/FlowLog?lang=typescript
What did you do? I searched for cdktf provider aws and switched from version 9.x to 10.x
What did you expect to happen? I expected to see the docs page in a couple of seconds
What actually happened? The page doesn't load, it says
Documentation in typescript is still not ready for this package. Come back soon. If this persists, please let us know by creating an issue .
Web Browser Chrome
OS MacOS
Other information Happy to help to fix if you want

Waiting for deployment and re-processing to confirm.

Run into an issue with S3 requests being throttled.
Potential fix: https://github.com/cdklabs/construct-hub/pull/1438

It ended up being this PR that fixed the throttling: #1442
But fix is confirmed and will be rolled out to production over the next few days.

authors: ediv-3nets hamza-faethm mrgrain

repo: cdklabs/construct-hub


text:
Vim plugin is slow

So, i've been using the vim extension downloaded through the main VScode marketplace (due to proxy issues with the code-server API), but the vim plugin is really slow and a pain to use.
Does everyone else have this problem, or is this due to the vim package in the coder API being slightly different then the marketplace one?

It currently runs on the server. We'll be fixing this by allowing certain exts to run on the client. You can expect this soon.

Okay, no worries. Thanks!

I'm running a setup with over 100 packages. All other ones seem to work flawlessly. Only the vim package is keeping my setup from running on coder. It'd be amazing to see it working at a usable pace

The VSCodeVim plugin is rather slow because it listens to all keys and it runs on the server.
Until client-side extensions are ready, https://marketplace.visualstudio.com/items?itemName=jpotterm.simple-vim is a much faster option with some caveats (read the extension's description for a list).

Finally got around to implementing client-side extensions in latest master. :tada: I'm very interested in hearing any bug reports around that. Currently only vscodevim.vim is white-listed to run in the browser.

@code-asher I'm so excited to hear this, can't wait to try it out. Thanks!

authors: code-asher jakegt1 jasonharrison kylecarbs wende

repo: cdr/code-server


text:
Dev documentation changes: Add slot to fieldset

📇 User story
As a developer, I want to add documentation about a slot in the fieldset component so that other developers can understand how to use it effectively.
✅ Definition of Done / Outcomes

[ ] Done when the website documentation is updated to have information about the default slot
[ ] Done when storybook event and properties page has been updated to include the default slot

📜 Acceptance criteria

[ ] The purpose of the slot in the gcds-fieldset component should be clearly described.
[ ] The documentation should explain what a slot is in the context of the fieldset component.

📝 More info
Do we need content updates on the fieldset documentation to describe the usage for the slot?
This issue was raised by a user through our contact us feedback form.

re: ticket 19078

authors: alexadavidson daine

repo: cds-snc/design-gc-conception


text:
Dev: Update french "use case" tab name in md files

We noticed that the md files for the use case in the French components are named "case-dusage" It should be "cas d'utilisation" or "cas dutilisation" if the apostrophe isn't supported.

Fixed, see PR above.


text:
Add foundations to schema

Finally the foundations!

I understand that foundations are different than pillars, but you've gotta start somewhere.

Also, those enums >.<


text:
Get first parent with an Id on click

There is probably a much better way of doing this (and it might already be in the library), but I thought I would upload a PR for discussion.
I was finding the "targetId" less useful than I hoped, as it is often empty, unless I give an Id to every single element. In practice I usually want the first named parent which has an Id, so I added a quick function to get that.

Random thought -- I wonder for future-proofing if it would be worth returning a list of all non-null IDs, back to the root? It would be more data to pass back, but shouldn't be that much data (except for very deeply nested svgs with lots of IDs).

Thanks @ChrisJefferson for the PR.  This looks reasonable to me but I wonder if it's browser-dependent.  I mostly develop on Firefox.  What did you try it on?
I'm slightly worried this will lead to brittle code in some cases because drawsvg automatically adds ids as needed by things like Use.  Your second suggestion might work better.
I'd be happy to merge this or your second suggestion.  Let me know your thoughts.

Hi,
I've updated to now return all ids up to the parent root. I tested this works on chrome+firefox, and also in vscode's juypter notebook support.
This code should work everywhere, it's (assuming I haven't done anything stupid) fairly standard event handling code.
I include a demo below -- it's probably too long to be in the readme, I wanted to make it a decent length to make a few different groups with different ids. We can see from this that we can identify which group is clicked on, and also the group that group is contained in (and as the ids come as a list, it's easy to filter / check order, if one wishes).
I am already using this in my code (I'm making simple clickable puzzles, like Sudoku. Once it's a bit more polished I'll share a link), this seems to let me get what is clicked on fairly well.

import drawsvg as draw
from drawsvg.widgets import DrawingWidget

# Create drawing
d = draw.Drawing(4,4, origin='center', context=draw.Context(invert_y=True))
d.set_render_size(500)
c = {'g1': 0, 'g2': 0, 'g3': 0, 'text': 0}
group1 = draw.Group(id="g1")
d.append(group1)
group1.append(draw.Circle(0, 0, 1, fill='orange'))
group2 = draw.Group(id="g2")
group2.append(draw.Circle(0, 1, 1, fill='red'))
group1.append(group2)
group3 = draw.Group(id="g3")
group3.append(draw.Circle(1, 0, 1, fill='blue'))
d.append(group3)

text = draw.Group(id="text")
d.append(text)

def redraw():
    text.children.clear()
    string = f"Orange+Red: {c['g1']}, Red: {c['g2']}\nBlue: {c['g3']}, Text: {c['text']}"
    text.append(draw.Text(string, 0.2, -1, 1.8))
redraw()

# Create interactive widget and register mouse events
widget = DrawingWidget(d)
@widget.mousedown
def mousedown(widget, x, y, info):
    for id in info['targetParentIds']:
        c[id] += 1
    redraw()
    widget.refresh()
widget

Great.  I've been busy but I will merge and publish a new version as soon as I have some time.
I appreciate how active you've been! Would you be interested in creating a short documentation page that could be linked from the readme or the compiled documentation (as a separate PR)?  Any additional documentation you create while making your game would be helpful to other users.

Merged.  This feature is included in the new package version 2.2.0.

authors: ChrisJefferson cduck

repo: cduck/drawsvg


text:
File format conversion

Hello, I have a text version. RVM file, how do I convert that to a file that feeds rvmparser

Currently rvmparser only reads binary rvm files and writes rev files. So you cannot convert from text to binary using rvmparser.
Issues #63 and #64 address this, but nothing has been implemented yet.

Thank you for your answer. Can I directly convert the text file to binary

repo: cdyk/rvmparser


text:
use Bear 'add-text' action rather than automation to replace note text

The Bear action add-text takes a mode parameter that has a replace_all option. This replaces the contents of the note with the contents passed on the x-callback-url call. Using this approach rather than AppleScript is much faster, probably less-brittle, and doesn't require the Automation permission.
I've only lightly tested this on my own installation.

Good call! I did not know Bear had this particular feature.
I've lightly tested this on my own installation and it seems to work as expected. As a bonus, it seems to be faster, and as you've noted, this should reduce the permissions wrangling needed to get this project running.

authors: cdzombak dcreemer

repo: cdzombak/bear-backlinks


text:
🛑 tanecni-divadlo.cz is down

In b17ebf0, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 8cc45fa.

repo: cebreus/upptime


text:
🛑 tanecni-divadlo.cz is down

In 6e02245, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 9a66418.


text:
🛑 tanecni-divadlo.cz is down

In c8ecaa7, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 894e254.


text:
🛑 tanecni-divadlo.cz is down

In fe89610, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 9f13f50.


text:
🛑 tanecni-divadlo.cz is down

In 4e34f33, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in ffb80a9 after 3 minutes.


text:
🛑 tanecni-divadlo.cz is down

In ee5da19, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in c1214d5 after 3 minutes.


text:
🛑 tanecni-divadlo.cz is down

In f6782c3, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in f10d15b after 8 minutes.


text:
🛑 tanecni-divadlo.cz is down

In e1f11d3, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 558163f.


text:
🛑 tanecni-divadlo.cz is down

In 374cb67, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 19dbf4e.


text:
🛑 tanecni-divadlo.cz is down

In 9807cbc, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in a0f293f.


text:
🛑 tanecni-divadlo.cz is down

In d2251cc, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 98753d5.


text:
🛑 tanecni-divadlo.cz is down

In c1a206d, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 9502a72.


text:
🛑 tanecni-divadlo.cz is down

In 3d4c6e3, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in cc9eded.


text:
🛑 tanecni-divadlo.cz is down

In f4ac940, tanecni-divadlo.cz (https://www.tanecni-divadlo.cz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tanecni-divadlo.cz is back up in 7b5c0d4.


text:
🛑 CDN is down

In 79f7920, CDN (https://cdn.ceccun.com/cdynamic/captive) was down:

HTTP code: 522
Response time: 15461 ms

Resolved: CDN is back up in ce5078a.

repo: ceccun/status


text:
Cleaner file names

Wouldn't it be better to rename the files in the following way?
src/css-modules-compiler.js => src/compiler.js
src/css-modules-extractor.js => src/extractor.js
src/update-css-modules-imports.js => src/update-imports.js (or just src/updater.js for consistency)
bin/css-module-compiler.js => bin/css-modules-compiler.js
What do you think @cef62?

I think your naming is really better than the actual!


text:
CosmJS Transaction Decoding Incompatibility

Summary of Bug
CosmJS fails to decode blocks which contain "Pay For Blobs" type transactions, due to those transactions having a non-standard protobuf format.
Error: invalid wire type 6 at offset 38
    at Reader.skipType (node_modules/protobufjs/src/reader.js:377:19)
    at Object.decode (node_modules/cosmjs-types/cosmos/tx/v1beta1/tx.js:703:28)
    at Object.decode (node_modules/cosmjs-types/cosmos/tx/v1beta1/tx.js:382:47)
    at decodeTxRaw (node_modules/@cosmjs/proto-signing/build/decode.js:11:33)

This will likely hinder adoption as CosmJS is widely used to interact with Cosmos SDK-based chains.
Version
v1.0.0-rc17
Steps to Reproduce
Using this transaction from the mocha-4 testnet: https://celestia.explorers.guru/transaction/E369E8DCDC66E33DEC748B18B5E7203092F4D47D0E28B24F34DED3B296599CA8
import { decodeTxRaw } from '@cosmjs/proto-signing';
decodeTxRaw(Buffer.from('Cs0CCp8BCpwBCiAvY2VsZXN0aWEuYmxvYi52MS5Nc2dQYXlGb3JCbG9icxJ4Ci9jZWxlc3RpYTE3OHlmeHNuZ2cwcHBhdjMwcTd1anZrMms5MGo2MHoyajV6a3hqNhIdAAAAAAAAAAAAAAAAAAAAAAAAACVRklUZJVGSVRkaAXkiIDlyQrVAlX3r4kfLJGD4HTnmrZwZObqPets9NSjjg93MQgEAEmcKUQpGCh8vY29zbW9zLmNyeXB0by5zZWNwMjU2azEuUHViS2V5EiMKIQPKJy7Vb2UGw7or1J8cr4oOzm9KBTMNwe4Le0rIZSHy6RIECgIIARiUARISCgwKBHV0aWESBDc5ODAQtO8EGkBbXgq3TpZoDBM5yt5ycdfe1zPjnb3Y1w7vlL76nPejnSMqw2rS+RRc5YamiiIHhJLVJTA7fp0oBQjM2rq5JfxiEpkBChwAAAAAAAAAAAAAAAAAAAAAAAAlUZJVGSVRklUZEnkA8faHWX5A+pbDpfDV2gXSYAAAAAAAYXjaAFEArv+4TwD4TKD8Tf3eKe8QIDQw0CsZKVv4LyzGYKfQaTBK5ZBgdkSJ54P02eKgRxwQcHL6xCaJqS/B3LOT5J53GRWzuzLfpeVBroaHyfOEZS4eKMABAAD//4AsKXoBGgRCTE9C','base64'));

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Alternatively, the Tendermint block endpoint could be modified to unwrap the BlobTx into Tx before returning it.

this is an idea we can explore! thanks for the good rec @blorgon1 . We'd have to implement the "blobless" block in a separate endpoint to not also break some important downstream things ofc, but this seems like the simplest change.

closing this in favor of https://github.com/celestiaorg/celestia-core/issues/1136

repo: celestiaorg/celestia-app


text:
TempDir RemoveAll cleanup: unlinkat ... application.db: directory not empty

Context
We're trying to eliminate test flakes in this repo. A flake just occurred
--- FAIL: TestSquareSizeIntegrationTest (107.50s)
    square_size_test.go:47: setting up square size integration test
    network.go:48: tearing down testnode
    rpc_client.go:39: stopping tmNode
    rpc_client.go:45: tmNode has stopped
    rpc_client.go:99: removing addrbook.json
    rpc_client.go:99: removing genesis.json
    rpc_client.go:99: removing node_key.json
    rpc_client.go:99: removing priv_validator_key.json
    rpc_client.go:105: removing /tmp/TestSquareSizeIntegrationTest3506[33](https://github.com/celestiaorg/celestia-app/actions/runs/7143755872/job/19455934846#step:4:34)4195/001/.celestia-app/config
    testing.go:1225: TempDir RemoveAll cleanup: unlinkat /tmp/TestSquareSizeIntegrationTest35063[34](https://github.com/celestiaorg/celestia-app/actions/runs/7143755872/job/19455934846#step:4:35)195/001/.celestia-app/data/application.db: directory not empty

Occurrences

https://github.com/celestiaorg/celestia-app/actions/runs/7143755872/job/19455934846#step:4:27
https://github.com/celestiaorg/celestia-app/actions/runs/7189162265/job/19580189334#step:4:30

I would assume the other directories are also not empty, right?
Perhaps we need to apply:
https://github.com/celestiaorg/celestia-app/blob/e0edb4cf0d89a08c46c5634d653e44a77d1d517c/test/util/testnode/rpc_client.go#L39
to the data directory as well

Hmm can try that. So far the flakes are only for .celestia-app/data so I think your suggestion could resolve

authors: cmwaters rootulp


text:
[Not ready for review] doc: adds mempool reactor doc

Not Ready For Review
Part of #1080

Closing this PR in favour of its mirror which is based on the main branch.

repo: celestiaorg/celestia-core


text:
Metrics stop working within a few hours of node restart with v0.9.4 running as a bridge

Celestia Node version
0.9.4
OS
Ubuntu 20.04
Install tools
Running a self-compiled binary from the git tag 0.9.4
Others
Binary managed via systemd to run a bridge node with the standard flags that have worked for previous celestia node verions:
--metrics.tls=false --metrics --metrics.endpoint 127.0.0.1:4318
This points to an otel collector that exports local prometheus metrics whilst forwarding otel metrics on to the blockspacerace external endpoint.
Steps to reproduce it
Metrics show correctly via the otelcollector on a fresh restart of a node, as they have done for previous celestia-node versions. However within a few hours of running version 0.9.4 these simply stop being updated.
Expected result
Metrics should continue to be updated and exported whilst the celestia node is running
Actual result
Metrics stop working within a few hours of a restart (sometimes as soon as 30 minutes) and this triggers our "metrics absent" alerts on our Prometheus servers.
Relevant log output
No response
Notes
No response

Could you please give more information about what is "metrics absent" alert? Is it triggered when there are no metrics at all or some specific ones it is targeted at?

I can confirm that. My bridge just stops sending metrics to the otel-collector after a while.

Could you please give more information about what is "metrics absent" alert? Is it triggered when there are no metrics at all or some specific ones it is targeted at?

Our Prometheus server has alert rules configured that use the "absent_over_time" function for the 2 bridge metrics we are most interested in: celestia_incentivized_bridge_total_synced_headers and celestia_incentivized_bridge_head.
However, I can confirm that when the celestia bridge encounters this issue all metrics it usually exports are no longer present.

this issue also happen for full node

Does this happen only on 0.9.4? Can you try building the binary with reverted https://github.com/celestiaorg/celestia-node/pull/2175? It's the only patch that barely touched metrics since last release and maybe it broke something.

Does this happen only on 0.9.4? Can you try building the binary with reverted #2175? It's the only patch that barely touched metrics since last release and maybe it broke something.

Yes, we're only seeing this with 0.9.4. All previous versions we've used for blockspacerace have not displayed this issue.
We've built #2175 and got it running on our backup bridge node. There are fewer metrics being exported than other versions. I will keep an eye on it and provide an update if it suddenly stops exporting metrics like 0.9.4

Did you revert to https://github.com/celestiaorg/celestia-node/pull/2175 or reverted this commit only? Asking because it is important to exclude this one.

Did you revert to #2175 or reverted this commit only? Asking because it is important to exclude this one.

We've built the binary after running gh pr checkout 2175 which gives us the following commit:  96c16fea28fe10d7bf198c33a0b9a89ec828f9ee
It sounds like this is not what you require. Could you let me know which commit you want us to build please and I'll get it up and running?

@Pete-LunaNova Could you try to run latest main? It has a fix for deadlock that was blocking the async metric exporter.

@Pete-LunaNova Could you try to run latest main? It has a fix for deadlock that was blocking the async metric exporter.

No problem. I've built this and it is up and running on our backup bridge node, commit: 9baade4bd0300dabcd160c185e145a824c128e30.
I will keep an eye on it and let you know if it looks like the issue is solved or not.

I've not seen a failure in exporting metrics since starting this new version yesterday, so it looks like the issue has been fixed in the latest main. Thank you for your work on this, it's much appreciated :+1:
Is it safe to roll out this version to our primary bridge node or should we wait for a new release?

It is safe and expect the new version tmrw

authors: Pete-LunaNova Wondertan malise800 walldiss zekchan

repo: celestiaorg/celestia-node


text:
fix(share/discovery): memoize discovery trigger and limit FindPeers operation

Closes https://github.com/celestiaorg/celestia-node/issues/2258
Two cases were possible:

Sometimes, the discovery is not triggered, and memorizing triggers might help

It's an unconfirmed theory, and we are still determining if it fixes anything yet.
We considered a case with @walldiss, but it should not happen.

FindPeers can get stuck sometimes for an indefinite time and so forth stopping the whole discovery. We should stop and restart it.

@walldiss, pls test to reconfirm the fix works

I have run node with this PR and never seen stuck discovery since then

Codecov Report

Merging #2263 (6526eed) into main (e5efcb0) will increase coverage by 0.04%.
The diff coverage is 71.42%.

@@            Coverage Diff             @@
##             main    #2263      +/-   ##
==========================================
+ Coverage   50.56%   50.60%   +0.04%
==========================================
  Files         150      150
  Lines        9305     9281      -24
==========================================
- Hits         4705     4697       -8
+ Misses       4203     4187      -16
  Partials      397      397

Impacted Files
Coverage Δ

share/p2p/discovery/metrics.go
11.53% <50.00%> (+1.45%)
:arrow_up:

share/p2p/discovery/discovery.go
69.39% <75.00%> (-1.15%)
:arrow_down:

... and 3 files with indirect coverage changes

We discussed in sync that we don't want to merge the fix, we are not sure it is fixing anything, so we removed the buffer. We can continue testing to see if the discovery still gets stuck

authors: Wondertan codecov-commenter walldiss


text:
fraud: extend proof stucture

Resolves #827

In a private discussion with @Wondertan we agreed that better to name it HeaderHash. It will look more natural and will not confuse users. I agree with him. We are not working with blocks but with headers.


text:
Implement lockout on PIN attempts if there are several incorrect attempts

Expected Behavior
see discussion here: https://github.com/celo-org/celo-monorepo/issues/2574#issuecomment-581848492
Custom pin screen is currently vulnerable to brute forcing as we implement no lockout, explore options for this.
Current Behavior
PIN can be attempted without penalty until correct

@jeanregisser @nityas there is no description of what to show when the user fails, how many tries, and what to do if the user fails all the times
I'll start investigating how to lock the app if the user fails, but I'll need the rest of the information to finish the task

authors: Pedro-vk nityas

repo: celo-org/celo-monorepo