Question about the aspect detection task

Hi, thank you very much for providing this interesting paper.
I have a question regarding the aspect detection task. In the paper, it says you fine-tuned the BERT model with the new aspect-annotated data (i.e., the output of the crowd sourcing), but why do you use ipa in the script to detect aspects for the downstream task? Did these two models (the fine-tuned BERT-large and the ipa.aspect) give the same results? If not, is it possible for us to have the BIO-tagged data and the checkpoint of the final BERT model? We hope to replicate your experiment in aspect detection.  Many thanks in advance for your time. :)

Hi, thanks! Sorry for the late reply, I missed the notification.
What exactly do you mean with ipa? I used the BERT-base model (large was just too slow for so much data) to detect aspects for the downstream task. I don't have the model weights anymore, but it's pretty fast to train a BERT base version on the dataset (just use HF's AutoModelForTokenClassification).
You can download the aspect detection dataset (and the the silver labeled CommonCrawl/Reddit data) from here: https://tudatalib.ulb.tu-darmstadt.de/handle/tudatalib/2329.

Hi, thank you very much for your reply!
Sorry for my typo - it should have been API. In the aspect_detection.py, I noticed there is no BERT model used but just an api from Argumentsearch.com.  So I'm not very sure if you used the fine-tuned BERT model to detect the aspects for the downstream task. I apologise if I misunderstood it. :)
Also in the paper you said the BERT-large gave a better result in aspect detection (section 3.2), but why didn't you use the fine-tuned BERT-large for the downstream task? And may I know why you used the dataset with two different split methods? I totally understand the motivation of cross-topic data, that is, to see if the model could give proper result with new topics, but I didn't quite get the motivation for the in-topic data. I would really appreciate it if you could provide some of your opinions!
Sorry I asked too many questions. Many thanks in advance for your kind help. :)

Ah, right, I forgot about that. After I trained the model I added this route in the argumentsearch API to make it easier for people who want to reproduce the results or just detect aspects in arguments. The model hosted there is the BERT base model mentioned in the paper. If you want to use it, you can just register at https://api.argumentsearch.com.
I didn't use BERT large because it's much slower and we had to classify millions of sentences. And the difference in F1 macro was "only" 1.2pp. With regard to the split, we just wanted to provide fixed data splits for both scenarios so future work would take these and make results comparable. There are a lot of datasets out there that come without splits and it's really hard to compare performance on them between works. There are valid scenarios where you'd only need performance on the topics you see at training.

I see. It makes sense! Thank you very much. Everything is clear now. :)


[SILGen/DI] InitAccessors: Fix handling of nonmutating set when type has other stored properties

The original change supported only the case where all stored properties were controlled
by an init accessor but when other fields were involved SILGen would emitted copies of
loaded "self" for each setter application which is redundant and due to the fact that the
setter was escaping.
These changes make partial application of the setter non-escaping which means that
"self" can be borrowed instead of copied.
Resolves: https://github.com/apple/swift/issues/67827

@swift-ci please test

@swift-ci please test source compatibility

@swift-ci please build toolchain macOS

@swift-ci please test source compatibility release

@swift-ci please test source compatibility debug

This failure in distributed actors looks unrelated but I am going to wait for main branch suite run to complete.

Thanks @xedin for fixing this. Would it be possible to get this fix into the 5.9.x branch/release as well?

Unfortunately I think it might be too risky of a change for 5.9.x but I'll see what I can do.

Hello @xedin, I tried your fix out in the latest Xcode 15.3 beta (15E5178i), and it seem to work fine for the examples I reported, but if I change them slightly to include e.g. let constant it fails to compile again Variable 'self._count' used before being initialized:
struct Test {
    let id: UUID
    private var _count: Int

    var count: Int
    {
        @storageRestrictions(initializes: _count)
        init {
            _count = newValue
        }
        get {
            _count
        }
        nonmutating set {
            // Update store
        }
    }

    init(id: UUID, count: Int) {
        self.id = id
        self.count = count // << Variable 'self._count' used before being initialized
    }
}

I will take a look!

Hm, var id doesn't work either, var and let result in the same SIL so it must be something in DI that I haven't accounted for.

Interesting. Switching UUID to Date also fails.

Right, I think both Date and UUID are big enough to force indirect access to the Test, this is something we didn't account for because for that a copy of Test has to be allocated.

I think I figured it out, the problem is not actually SILGen, it's Sema because it generates a load from "self" of count though it shouldn't be doing that. There is a special handling of that for property wrappers but not for init accessors, I should be able to fix this tomorrow.

Here is the fix - https://github.com/apple/swift/pull/71248

@xedin I tested the above with the latest Xcode beta, and it seems to work, but if I modify it slightly it still fails with the same error (the below is a closer match to my macros is generating its code).
struct Test {
  let id: UUID
  private var _count: Int

  var count: Int
  {
    @storageRestrictions(initializes: _count)
    init {
      _count = newValue
    }
    _read {
      yield _count
    }
    nonmutating _modify {
      var val = _count
      yield &val
    }
  }

  init(id: UUID, count: Int) {
    self.id = id
    self.count = count // << Variable 'self._count' used before being initialized
  } // << Return from initializer without initializing all stored properties
}


Fix links to not point to the old repository anymore.

Every instance of "leios/algorithm-archive" is being replaced with "algorithm-archivists/algorithm-archive".

@leios What's up with version_control.md2? Is this file important/used?

@julianschacher That was a mistake. It can definitely be deleted. Thanks!

@leios Do you want to delete it or should I just include it in this PR?

I think it's fine to add it to this one

Should we leave a link to the discord server in the how to contribute chapter?

Why not? The discord server is the place the main AAA discussion happens. It's also nicer to write there about something, that would otherwise spam a PR. Like a discussion about a detail, etc.
Aside from that, it doesn't hurt to have more people on Discord. It shouldn't be a requirement of course, but it should be a good option.


Make a Team account

And mention in the bio who the admins/mods are.
Forward team email to all 3.

@blaine @mattwynne: What should the @handle be of the "team" account? We can't change the name in the future.

@blaine @mattwynne: What should the @handle be of the "team" account? We can't change the name in the future.

Why not?
I'd start with admin@ just because that's a common convention, but not fussed either way.

+1 for admin or maybe admins?
Sent from Outlook for iOShttps://aka.ms/o0ukef

From: Blaine Cook @.>
Sent: Thursday, December 8, 2022 2:45:10 PM
To: nelson-social/community @.>
Cc: Matt Wynne @.>; Mention @.>
Subject: Re: [nelson-social/community] Make a Team account (Issue #1)
@blainehttps://github.com/blaine @mattwynnehttps://github.com/mattwynne: What should the @handlehttps://github.com/handle be of the "team" account? We can't change the name in the future.
Why not?
I'd start with admin@ just because that's a common convention, but not fussed either way.
—
Reply to this email directly, view it on GitHubhttps://github.com/nelson-social/community/issues/1#issuecomment-1343469629, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAAEWPGQLFOGUN6BHWX7WLLWMJQHNANCNFSM6AAAAAASXMZC44.
You are receiving this because you were mentioned.Message ID: @.***>
We hope you found this email of interest; however, click here if you wish to unsubscribehttp://www2.smartbear.com/SubscriptionCenter.html?utm_source=outlook&utm_medium=email&utm_content=emailsig or manage your email preferences. Privacy Policy.https://smartbear.com/privacy/
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

@mattwynne: I don't think Mastodon will let me rename users.

Done!

Nice one!Can you share the login details with me and @blaine? Maybe you already did and I missed the memo?

Well, I was thinking that it would allow us to:

Fiddle about with the server rules settings etc. and tweak the about page copy.
See when we get DMs or mentions to that account so it doesn't all fall to you.

I don't want a shared admin account (too much ambiguity), I can promote your @matt account to admin, tho? And use the @admin just for DMs.

Fiddle about with the server rules settings etc. and tweak the about page copy.

Can you keep a log of what settings you change?

matt is now an admin
admin is now a regular user

OK that works, thanks!

Can you keep a log of what settings you change?

👍
My only question now is what we should say to people about how to contact "us" if they have a question or moderation complaint or whatever. Should we tell them to DM this @admin account? Send an email to<EMAIL_ADDRESS>I just want to make sure that if someone does contact us, we'll get the message!

I guess the email works? We could use follow-requests, so people can't just DM the admin account, but still see the bio with our names and email.

OK, I've used the email in the copy for #16.
What are "follow-requests"?

I have not used these. It would certainly prevent from us not seeing DMs in the admin account.

Or maybe we make a pinned post on that account with instructions on how to contact us.
Annoying that you must-have an "owner" and that's a single account.


langchain{-community,core,text-splitters}: update

Description of changes

python3Packages.langchain-core: 0.2.37 -> 0.2.38
https://github.com/langchain-ai/langchain/releases/tag/v0.2.38
python312Packages.langchain-text-splitters: 0.2.2 -> 0.2.4
https://github.com/langchain-ai/langchain/releases/tag/langchain-text-splitters==0.2.4
python312Packages.langchain: 0.2.15 -> 0.2.16
https://github.com/langchain-ai/langchain/releases/tag/v0.2.16
python312Packages.langchain-community: 0.2.15 -> 0.2.16
https://github.com/langchain-ai/langchain/releases/tag/langchain-community==0.2.16

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 340049 run on x86_64-linux 1

2 packages marked as broken and skipped:

khoj
khoj.dist

4 packages failed to build:

python311Packages.langgraph
python311Packages.langgraph.dist
python312Packages.langgraph
python312Packages.langgraph.dist

60 packages built:

open-webui
open-webui.dist
pentestgpt
pentestgpt.dist
python311Packages.langchain
python311Packages.langchain-aws
python311Packages.langchain-aws.dist
python311Packages.langchain-azure-dynamic-sessions
python311Packages.langchain-azure-dynamic-sessions.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-huggingface
python311Packages.langchain-huggingface.dist
python311Packages.langchain-mongodb
python311Packages.langchain-mongodb.dist
python311Packages.langchain-openai
python311Packages.langchain-openai.dist
python311Packages.langchain-standard-tests
python311Packages.langchain-standard-tests.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langchain.dist
python311Packages.langgraph-checkpoint
python311Packages.langgraph-checkpoint-postgres
python311Packages.langgraph-checkpoint-postgres.dist
python311Packages.langgraph-checkpoint-sqlite
python311Packages.langgraph-checkpoint-sqlite.dist
python311Packages.langgraph-checkpoint.dist
python312Packages.langchain
python312Packages.langchain-aws
python312Packages.langchain-aws.dist
python312Packages.langchain-azure-dynamic-sessions
python312Packages.langchain-azure-dynamic-sessions.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langchain-huggingface
python312Packages.langchain-huggingface.dist
python312Packages.langchain-mongodb
python312Packages.langchain-mongodb.dist
python312Packages.langchain-openai
python312Packages.langchain-openai.dist
python312Packages.langchain-standard-tests
python312Packages.langchain-standard-tests.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
python312Packages.langgraph-checkpoint
python312Packages.langgraph-checkpoint-postgres
python312Packages.langgraph-checkpoint-postgres.dist
python312Packages.langgraph-checkpoint-sqlite
python312Packages.langgraph-checkpoint-sqlite.dist
python312Packages.langgraph-checkpoint.dist

python3Packages.langgraph is broken, but this is not a regression and I plan to fix it in #340036 after this is merged.

Result of nixpkgs-review pr 340049 run on aarch64-darwin 1

2 packages marked as broken and skipped:

khoj
khoj.dist

8 packages failed to build:

python311Packages.langgraph
python311Packages.langgraph-checkpoint-postgres
python311Packages.langgraph-checkpoint-postgres.dist
python311Packages.langgraph.dist
python312Packages.langgraph
python312Packages.langgraph-checkpoint-postgres
python312Packages.langgraph-checkpoint-postgres.dist
python312Packages.langgraph.dist

56 packages built:

open-webui
open-webui.dist
pentestgpt
pentestgpt.dist
python311Packages.langchain
python311Packages.langchain-aws
python311Packages.langchain-aws.dist
python311Packages.langchain-azure-dynamic-sessions
python311Packages.langchain-azure-dynamic-sessions.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-huggingface
python311Packages.langchain-huggingface.dist
python311Packages.langchain-mongodb
python311Packages.langchain-mongodb.dist
python311Packages.langchain-openai
python311Packages.langchain-openai.dist
python311Packages.langchain-standard-tests
python311Packages.langchain-standard-tests.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langchain.dist
python311Packages.langgraph-checkpoint
python311Packages.langgraph-checkpoint-sqlite
python311Packages.langgraph-checkpoint-sqlite.dist
python311Packages.langgraph-checkpoint.dist
python312Packages.langchain
python312Packages.langchain-aws
python312Packages.langchain-aws.dist
python312Packages.langchain-azure-dynamic-sessions
python312Packages.langchain-azure-dynamic-sessions.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langchain-huggingface
python312Packages.langchain-huggingface.dist
python312Packages.langchain-mongodb
python312Packages.langchain-mongodb.dist
python312Packages.langchain-openai
python312Packages.langchain-openai.dist
python312Packages.langchain-standard-tests
python312Packages.langchain-standard-tests.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
python312Packages.langgraph-checkpoint
python312Packages.langgraph-checkpoint-sqlite
python312Packages.langgraph-checkpoint-sqlite.dist
python312Packages.langgraph-checkpoint.dist

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

8 packages marked as broken and skipped:

khoj
khoj.dist
open-webui
open-webui.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist

4 packages failed to build:

python311Packages.langgraph
python311Packages.langgraph.dist
python312Packages.langgraph
python312Packages.langgraph.dist

54 packages built:

pentestgpt
pentestgpt.dist
python311Packages.langchain
python311Packages.langchain-aws
python311Packages.langchain-aws.dist
python311Packages.langchain-azure-dynamic-sessions
python311Packages.langchain-azure-dynamic-sessions.dist
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-huggingface
python311Packages.langchain-huggingface.dist
python311Packages.langchain-mongodb
python311Packages.langchain-mongodb.dist
python311Packages.langchain-openai
python311Packages.langchain-openai.dist
python311Packages.langchain-standard-tests
python311Packages.langchain-standard-tests.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langchain.dist
python311Packages.langgraph-checkpoint
python311Packages.langgraph-checkpoint-postgres
python311Packages.langgraph-checkpoint-postgres.dist
python311Packages.langgraph-checkpoint-sqlite
python311Packages.langgraph-checkpoint-sqlite.dist
python311Packages.langgraph-checkpoint.dist
python312Packages.langchain
python312Packages.langchain-aws
python312Packages.langchain-aws.dist
python312Packages.langchain-azure-dynamic-sessions
python312Packages.langchain-azure-dynamic-sessions.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langchain-huggingface
python312Packages.langchain-huggingface.dist
python312Packages.langchain-mongodb
python312Packages.langchain-mongodb.dist
python312Packages.langchain-openai
python312Packages.langchain-openai.dist
python312Packages.langchain-standard-tests
python312Packages.langchain-standard-tests.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
python312Packages.langgraph-checkpoint
python312Packages.langgraph-checkpoint-postgres
python312Packages.langgraph-checkpoint-postgres.dist
python312Packages.langgraph-checkpoint-sqlite
python312Packages.langgraph-checkpoint-sqlite.dist
python312Packages.langgraph-checkpoint.dist

You have test failures:
       > FAILED tests/test_pregel.py::test_repeat_condition - AssertionError: assert [+ received] == [- snapshot]
       > FAILED tests/test_pregel.py::test_nested_graph_xray - AssertionError: assert [+ received] == [- snapshot]

These look like implementation tests instead of true unit tests, so I would suggest disabling them. Possibly also file a bug on the source repos.
I also suggest merging #940036 into this and adding langchain-core to the update script. I'll go look at the langchain and langsmith release logs and see if we should add additional packages to the update script.

Ok, I merged both PRs into this one and bumped langgraph to 2.19.
However, it complained about not being able to import psycopg_pool, so I added psycopg.pool to the dependencies.
However, now many tests fail with:
psycopg.errors.InsufficientPrivilege: permission denied to create database

In https://github.com/NixOS/nixpkgs/pull/340036#issuecomment-2334597102, were you suggesting to add langchain-core to the update script of langgraph ?
langchain-core already has a custom update script

Ok, I merged both PRs into this one and bumped langgraph to 2.19. However, it complained about not being able to import psycopg_pool, so I added psycopg.pool to the dependencies. However, now many tests fail with:
psycopg.errors.InsufficientPrivilege: permission denied to create database

As far as I can tell, that would have to be reworked into a passthrough test. Personally, I'd disable those tests for now.

Personally, I'd disable those tests for now.

Good for me, done.

Result of nixpkgs-review pr 340049 run on aarch64-darwin 1

2 packages marked as broken and skipped:

khoj
khoj.dist

8 packages failed to build:

python311Packages.langgraph
python311Packages.langgraph-checkpoint-postgres
python311Packages.langgraph-checkpoint-postgres.dist
python311Packages.langgraph.dist
python312Packages.langgraph
python312Packages.langgraph-checkpoint-postgres
python312Packages.langgraph-checkpoint-postgres.dist
python312Packages.langgraph.dist

60 packages built:

open-webui
open-webui.dist
pentestgpt
pentestgpt.dist
python311Packages.langchain
python311Packages.langchain-aws
python311Packages.langchain-aws.dist
python311Packages.langchain-azure-dynamic-sessions
python311Packages.langchain-azure-dynamic-sessions.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-huggingface
python311Packages.langchain-huggingface.dist
python311Packages.langchain-mongodb
python311Packages.langchain-mongodb.dist
python311Packages.langchain-openai
python311Packages.langchain-openai.dist
python311Packages.langchain-standard-tests
python311Packages.langchain-standard-tests.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langchain.dist
python311Packages.langgraph-checkpoint
python311Packages.langgraph-checkpoint-sqlite
python311Packages.langgraph-checkpoint-sqlite.dist
python311Packages.langgraph-checkpoint.dist
python311Packages.langgraph-sdk
python311Packages.langgraph-sdk.dist
python312Packages.langchain
python312Packages.langchain-aws
python312Packages.langchain-aws.dist
python312Packages.langchain-azure-dynamic-sessions
python312Packages.langchain-azure-dynamic-sessions.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langchain-huggingface
python312Packages.langchain-huggingface.dist
python312Packages.langchain-mongodb
python312Packages.langchain-mongodb.dist
python312Packages.langchain-openai
python312Packages.langchain-openai.dist
python312Packages.langchain-standard-tests
python312Packages.langchain-standard-tests.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
python312Packages.langgraph-checkpoint
python312Packages.langgraph-checkpoint-sqlite
python312Packages.langgraph-checkpoint-sqlite.dist
python312Packages.langgraph-checkpoint.dist
python312Packages.langgraph-sdk
python312Packages.langgraph-sdk.dist

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

8 packages marked as broken and skipped:

khoj
khoj.dist
open-webui
open-webui.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist

62 packages built:

pentestgpt
pentestgpt.dist
python311Packages.langchain
python311Packages.langchain-aws
python311Packages.langchain-aws.dist
python311Packages.langchain-azure-dynamic-sessions
python311Packages.langchain-azure-dynamic-sessions.dist
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-huggingface
python311Packages.langchain-huggingface.dist
python311Packages.langchain-mongodb
python311Packages.langchain-mongodb.dist
python311Packages.langchain-openai
python311Packages.langchain-openai.dist
python311Packages.langchain-standard-tests
python311Packages.langchain-standard-tests.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langchain.dist
python311Packages.langgraph
python311Packages.langgraph-checkpoint
python311Packages.langgraph-checkpoint-postgres
python311Packages.langgraph-checkpoint-postgres.dist
python311Packages.langgraph-checkpoint-sqlite
python311Packages.langgraph-checkpoint-sqlite.dist
python311Packages.langgraph-checkpoint.dist
python311Packages.langgraph-sdk
python311Packages.langgraph-sdk.dist
python311Packages.langgraph.dist
python312Packages.langchain
python312Packages.langchain-aws
python312Packages.langchain-aws.dist
python312Packages.langchain-azure-dynamic-sessions
python312Packages.langchain-azure-dynamic-sessions.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langchain-huggingface
python312Packages.langchain-huggingface.dist
python312Packages.langchain-mongodb
python312Packages.langchain-mongodb.dist
python312Packages.langchain-openai
python312Packages.langchain-openai.dist
python312Packages.langchain-standard-tests
python312Packages.langchain-standard-tests.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
python312Packages.langgraph
python312Packages.langgraph-checkpoint
python312Packages.langgraph-checkpoint-postgres
python312Packages.langgraph-checkpoint-postgres.dist
python312Packages.langgraph-checkpoint-sqlite
python312Packages.langgraph-checkpoint-sqlite.dist
python312Packages.langgraph-checkpoint.dist
python312Packages.langgraph-sdk
python312Packages.langgraph-sdk.dist
python312Packages.langgraph.dist

Result of nixpkgs-review pr 340049 run on x86_64-linux 1

2 packages marked as broken and skipped:

khoj
khoj.dist

68 packages built:

open-webui
open-webui.dist
pentestgpt
pentestgpt.dist
python311Packages.langchain
python311Packages.langchain-aws
python311Packages.langchain-aws.dist
python311Packages.langchain-azure-dynamic-sessions
python311Packages.langchain-azure-dynamic-sessions.dist
python311Packages.langchain-chroma
python311Packages.langchain-chroma.dist
python311Packages.langchain-community
python311Packages.langchain-community.dist
python311Packages.langchain-core
python311Packages.langchain-core.dist
python311Packages.langchain-huggingface
python311Packages.langchain-huggingface.dist
python311Packages.langchain-mongodb
python311Packages.langchain-mongodb.dist
python311Packages.langchain-openai
python311Packages.langchain-openai.dist
python311Packages.langchain-standard-tests
python311Packages.langchain-standard-tests.dist
python311Packages.langchain-text-splitters
python311Packages.langchain-text-splitters.dist
python311Packages.langchain.dist
python311Packages.langgraph
python311Packages.langgraph-checkpoint
python311Packages.langgraph-checkpoint-postgres
python311Packages.langgraph-checkpoint-postgres.dist
python311Packages.langgraph-checkpoint-sqlite
python311Packages.langgraph-checkpoint-sqlite.dist
python311Packages.langgraph-checkpoint.dist
python311Packages.langgraph-sdk
python311Packages.langgraph-sdk.dist
python311Packages.langgraph.dist
python312Packages.langchain
python312Packages.langchain-aws
python312Packages.langchain-aws.dist
python312Packages.langchain-azure-dynamic-sessions
python312Packages.langchain-azure-dynamic-sessions.dist
python312Packages.langchain-chroma
python312Packages.langchain-chroma.dist
python312Packages.langchain-community
python312Packages.langchain-community.dist
python312Packages.langchain-core
python312Packages.langchain-core.dist
python312Packages.langchain-huggingface
python312Packages.langchain-huggingface.dist
python312Packages.langchain-mongodb
python312Packages.langchain-mongodb.dist
python312Packages.langchain-openai
python312Packages.langchain-openai.dist
python312Packages.langchain-standard-tests
python312Packages.langchain-standard-tests.dist
python312Packages.langchain-text-splitters
python312Packages.langchain-text-splitters.dist
python312Packages.langchain.dist
python312Packages.langgraph
python312Packages.langgraph-checkpoint
python312Packages.langgraph-checkpoint-postgres
python312Packages.langgraph-checkpoint-postgres.dist
python312Packages.langgraph-checkpoint-sqlite
python312Packages.langgraph-checkpoint-sqlite.dist
python312Packages.langgraph-checkpoint.dist
python312Packages.langgraph-sdk
python312Packages.langgraph-sdk.dist
python312Packages.langgraph.dist

Note: Build failures on Darwin are coming from a database test problem in python312Packages.langchain-checkpoint-postgres. Filed #340224 to fix.

Got some issues with langchain:
        >
┃        > tests/unit_tests/test_imports.py::test_import_all
┃        >   /build/source/libs/langchain/tests/unit_tests/test_imports.py:24: LangChainPendingDeprecationWarning: langchain.indexes.prompts will be removed in the future.If you're relying on these prompts, please open an issue on GitHub to explain your use case.
┃        >     mod = importlib.import_module(module_name)
┃        >
┃        > tests/unit_tests/utils/test_openai_functions.py::test_convert_pydantic_to_openai_function
┃        >   /build/source/libs/langchain/tests/unit_tests/utils/test_openai_functions.py:12: LangChainDeprecationWarning: The function `convert_pydantic_to_openai_function` was deprecated in LangChain 0.1.16 and will be removed in 1.0. Use langchain_core.utils.functi…
┃        >     actual = convert_pydantic_to_openai_function(Data)
┃        >
┃        > -- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
┃        > --------------------------- snapshot report summary ----------------------------
┃        > 1 snapshot passed.
┃        > ============================= slowest 5 durations ==============================
┃        > 1.81s call     tests/unit_tests/test_imports.py::test_import_all
┃        > 0.44s call     tests/unit_tests/indexes/test_indexing.py::test_cleanup_with_different_batchsize
┃        > 0.18s call     tests/unit_tests/agents/test_agent.py::test_runnable_with_multi_action_per_step
┃        > 0.12s call     tests/unit_tests/smith/evaluation/test_runner_utils.py::test_arun_on_dataset
┃        > 0.12s call     tests/unit_tests/test_imports.py::test_import_all_using_dir
┃        > =========================== short test summary info ============================
┃        > FAILED tests/unit_tests/retrievers/document_compressors/test_chain_filter.py::test_llm_chain_filter - AssertionError: assert [Document(metadata={'a': 1}, page_content='Candlepin bowling is popular in New England.'), Document(metadata={'c': 3}, page_content=…
┃        >
┃        >   At index 1 diff: Document(metadata={'c': 3}, page_content='The moon is round.') != Document(metadata={'b': 2}, page_content='Candlepin bowling balls are smaller.')
┃        >
┃        >   Full diff:
┃        >     [
┃        >         Document(metadata={'a': 1}, page_content='Candlepin bowling is popular in New England.'),
┃        >   -     Document(metadata={'b': 2}, page_content='Candlepin bowling balls are smaller.'),
┃        >   +     Document(metadata={'c': 3}, page_content='The moon is round.'),
┃        >     ]
┃        > ==== 1 failed, 593 passed, 96 skipped, 12 deselected, 32 warnings in 8.31s =====
┃        For full logs, run 'nix log /nix/store/c83xklb3z7l0jqwrikrrwfaqq2q2py1z-python3.12-langchain-0.2.16.drv'.
┣━ Dependency Graph:
┃

False alarm, I updated master branch again and it worked.


cannot install g++

Your Windows build number
win10
1607
14393.10
Steps / commands required to reproduce the error
dyn@DELL:/etc/apt$ sudo apt-get install g++
sudo: unable to resolve host DELL
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
g++ : Depends: g++-4.8 (>= 4.8.2-5~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
dyn@DELL:/etc/apt$ sudo apt-get install g++-4.8
sudo: unable to resolve host DELL
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
g++-4.8 : Depends: gcc-4.8-base (= 4.8.4-2ubuntu1~14.04) but 4.8.4-2ubuntu1~14.04.3 is to be installed
Depends: gcc-4.8 (= 4.8.4-2ubuntu1~14.04) but 4.8.4-2ubuntu1~14.04.3 is to be installed
Depends: libstdc++-4.8-dev (= 4.8.4-2ubuntu1~14.04) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

It turns out that the mirror I used caused it.
deb http://mirrors.163.com/ubuntu trusty main restricted universe multiverse
deb http://mirrors.163.com/ubuntu trusty-updates main restricted universe multiverse
deb http://mirrors.163.com/ubuntu trusty-security main restricted universe multiverse

Also, to fix the initial error, delete or move /etc/hosts.  It should be fixed automatically.

This problem is caused by ubuntun mirror of 163.com

Closing as unrelated.

thank! I also solved this problem by changing the source.


ls using pagination

Test shows that this is very slow - or at least, calling ls on the bucket
every time a new file is created is very slow.
Fixes #17  (but not the final solution, I suspect)

Build sometimes times out for py2 - shows how slow calling _ls when creating 1200 keys. Perhaps should have an option to turn off refresh=True temporarily while creating/changing files.


Can't Send MBC

I can't send my mbc, it always says "transaction broadcast failed :(" and in the column it says "tx-size (code 64)"

Hello, try to send smaller amount

Thanks for the answer, thats work.


V0.10.0

I would like to discuss with Sat the best way to integrate multiversions in current broker implementation.  I've fixed tests and relocated apiversions information in connection structure.

FYI: I had to rebase to master as the history was quite polluted which meant doing a force push.

Yes. Sorry about this. I've decided that it makes sense to rebase this branch on the master because it touches the same pieces of code and it is much easier to rebase it now than to continue to work on it and make painful rebase later.

@e-max Can we close this?

Yep, I've already added everything from here in the current driver


adding densenet on cifar10 implementation

Example implementation of DenseNet on CIFAR10. Example is 100-Layer DenseNet-BC (k=12). Growth rate is 12.

DenseNet, DenseNet-BC and DenseNetFCN (Tiramisu DenseNet) are all part of Keras Contrib - https://github.com/farizrahman4u/keras-contrib/blob/master/keras_contrib/applications/densenet.py
DenseNet / DenseNet-BC also several pretrained weights for certain configurations.
@fchollet Perhaps the DenseNet models (not FCN type) should be added to core Keras since they offer more functionality?

Perhaps the DenseNet models (not FCN type) should be added to core Keras since they offer more functionality?

In what way do you think of adding them?

@fchollet Adding them as an application, similar to the MobileNet application.
DenseNets and DenseNet-BC are models with several configurations. They were kept in Contrib because the accompanying weights for certain configurations from the paper weren't available in Keras, but now that the weights are available, it would be better to add them to core Keras.
Considering that DenseNets we're the SotA model for ImageNet in 2016, it would be beneficial to have them in the core repository for easy access. Contrib has far fewer users than Keras overall, if the number of PRs and star ratings are an indicator.
However, that would make this PR somewhat redundant.

If and when the contrib DenseNet makes into keras/applications, I can make changes and a new PR. For the meantime, end users might want to see how densenet is implemented in keras on a dataset like cifar10 that can be easily understood and ready to run. This PR would be useful in that case.

I'd recommend keeping DenseNet in keras-contrib until a memory efficient implementation is supported by tensorflow. https://github.com/tensorflow/tensorflow/issues/12948

Also, if any version is to be merged I'd recommend the keras-contrib version. It is very well written, supports ImageNet weights, and has been tested and debugged by several people over a period of at least 6 months. Sorry about that @roatienza.

I recommend keeping DenseNet in keras-contrib only until a memory efficient implementation is supported by tensorflow as described in tensorflow/tensorflow#12948.

Also, if any DenseNet implementation is to be merged, I recommend the keras-contrib version. It is very well written, supports ImageNet weights, and has been tested and debugged by several people over a period of at least 6 months. Sorry about that @roatienza.

Both very reasonable suggestions.

I've been hoping for a shared tensor allocation to properly implement the memory efficient DenseNet. Hopefully the TF devs respond. I too agree that the contrib models be kept in Contrib for the time being.
Once cuDNN 7 is used in the next TF version, hopefully both shared allocations and grouped convolutions will be supported in TF.

conclusion: use densenet in contrib


653 | ref (cli codegen): custom template naming

What is the reason for this?

This may be confusing because we have another thing called a "template"

This may be confusing because we have another thing called a template, used in the cli create command

@Niraj-Kamdar what do you think ?

This is subcommand for the codegen, and I think it would be obvious in this context , and having it named custom-script would be more confusing since we expect mustache template here. Also, we use --custom option here.

This has been recently changed to --script here: https://github.com/polywrap/monorepo/blob/6d1f0983d305bcc6c763d11c8e35d73b37418f3c/packages/cli/src/commands/codegen.ts#L39
Let me know if you feel this is not a good name. Going to close this PR for now.


what is the diffence between dataset CORA-ML and Cora

I note that the CORA-ML differs in feature and node number with cora dataset  used by other papers

That version of CORA-ML was introduced here https://arxiv.org/abs/1707.03815.
It was later used also here https://arxiv.org/abs/1810.05997
which is the paper that we use for our comparisons.
On Fri, Apr 10, 2020 at 5:32 AM zhoulikeda<EMAIL_ADDRESS>wrote:

I note that the CORA-ML differs in feature and node number with cora
dataset used by other papers
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/spindro/AP-GCN/issues/3, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADSVXGOKUCWWPWDG7TBND6TRL2HNHANCNFSM4MFGCMXQ
.


csv-invert: Perf improvments!

Avoiding unneeded reallocation of a slice in sequence_chunker.go saves
about 15% of the runtime (a bit under a minute of the 6 minutes spent
inverting a list of about 1.5B entries). Tweaking the main loop that
processes list entries to avoid some map assignments, lookups, and
allocations saves another 15% or so, resulting in an overall savings
of about 2m on the 6m runtime of our test workload (as run on my
laptop).
Towards #3690

PTAL

well, the win will be less, now, that the sequence_chunker.go change is put off to another patch. But, still we should get about a 15% improvement


Falco on GKE/COS -  Unable to download Kernel headers

Describe the bug
Using official Helm chart and enabling eBPF on a GKE cluster, the Kernel headers cant't be downloaded because they are not found in  https://dl.bintray.com/falcosecurity/driver
How to reproduce it
Install Falco using helm chart on a GKE cluster (1.16.13-gke.401) running COS instances and enable ebpf as defined in the documentation.
Expected behaviour
falco-driver-loader should download the kernel headers and falco services should start properly.
Current behaviour
The service failed to start because the kernel header can't be found on https://dl.bintray.com/falcosecurity/driver
* Setting up /usr/src links from host
* Running falco-driver-loader with: driver=module, compile=yes, download=yes
* Unloading falco module, if present
* Trying to dkms install falco module with GCC /usr/bin/gcc
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"
* Running dkms build failed, couldn't find /var/lib/dkms/falco/2aa88dcf6243982697811df4c1b484bcbe9488a2/build/make.log (with GCC /usr/bin/gcc)
* Trying to dkms install falco module with GCC /usr/bin/gcc-8
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"
* Running dkms build failed, couldn't find /var/lib/dkms/falco/2aa88dcf6243982697811df4c1b484bcbe9488a2/build/make.log (with GCC /usr/bin/gcc-8)
* Trying to dkms install falco module with GCC /usr/bin/gcc-6
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"
* Running dkms build failed, couldn't find /var/lib/dkms/falco/2aa88dcf6243982697811df4c1b484bcbe9488a2/build/make.log (with GCC /usr/bin/gcc-6)
* Trying to dkms install falco module with GCC /usr/bin/gcc-5
DIRECTIVE: MAKE="'/tmp/falco-dkms-make'"
* Running dkms build failed, couldn't find /var/lib/dkms/falco/2aa88dcf6243982697811df4c1b484bcbe9488a2/build/make.log (with GCC /usr/bin/gcc-5)
* Trying to load a system falco driver, if present
* Trying to find locally a prebuilt falco module for kernel 4.19.112+, if present
* Trying to download prebuilt module from https://dl.bintray.com/falcosecurity/driver/2aa88dcf6243982697811df4c1b484bcbe9488a2/falco_cos_4.19.112%2B_1.ko
curl: (22) The requested URL returned error: 404 Not Found
Download failed, consider compiling your own falco module and loading it or getting in touch with the Falco community
Tue Oct 27 15:50:32 2020: Falco version 0.26.1 (driver version 2aa88dcf6243982697811df4c1b484bcbe9488a2)
Tue Oct 27 15:50:32 2020: Falco initialized with configuration file /etc/falco/falco.yaml
Tue Oct 27 15:50:32 2020: Loading rules from file /etc/falco/falco_rules.yaml:
Tue Oct 27 15:50:33 2020: Loading rules from file /etc/falco/falco_rules.local.yaml:
Tue Oct 27 15:50:34 2020: Unable to load the driver.
Tue Oct 27 15:50:34 2020: Runtime error: error opening device /host/dev/falco0. Make sure you have root credentials and that the falco module is loaded.. Exiting

Environment

Falco version: 0.26.1
System info:
Cloud provider or hardware configuration: GKE
OS: COS
Kernel: 4.19.112+
Installation method: kubernetes

Additional context
The https://dl.bintray.com/falcosecurity/driver/2aa88dcf6243982697811df4c1b484bcbe9488a2 directory does not contain any kernel headers for COS.

Thanks for reporting this @nhuray !
We're in the process of fixing this up (see #1460 )
Also, during tomorrow's community call we'll schedule with the community a hotfix 0.26.2 release of Falco containing such fix.

Thanks @leodido,
Do we have an ETA for #1460 ? Or could you point the documentation to build the kernel module for COS ?

Hi @nhuray ! You can't use the kernel module on COS - the only working way in there is the eBPF probe.
How did you enable eBPF?from what I see in the logs you are using the kernel module.

Hi @fntlnz
I enabled it using the Helm charts setting value ebpf.enabled: true.
Here is my values.yaml file:
# Default values for Falco.

image:
  registry: docker.io
  repository: falcosecurity/falco
  tag: 0.26.1
  pullPolicy: IfNotPresent
  pullSecrets: []

docker:
  enabled: true
  socket: /var/run/docker.sock

containerd:
  enabled: false
  socket: /run/containerd/containerd.sock

resources:
  # Although resources needed are subjective on the actual workload we provide
  # a sane defaults ones. If you have more questions or concerns, please refer
  # to #falco slack channel for more info about it
  requests:
    cpu: 100m
    memory: 512Mi
  limits:
    cpu: 200m
    memory: 1024Mi

extraArgs: []
nodeSelector: {}
affinity: {}

rbac:
  # Create and use rbac resources
  create: true

podSecurityPolicy:
  # Create a podSecurityPolicy
  create: false

serviceAccount:
  # Create and use serviceAccount resources
  create: true
  # Use this value as serviceAccountName
  name:

fakeEventGenerator:
  enabled: false
  args:
    - run
    - --loop
    - ^syscall
  replicas: 1

daemonset:
  # Perform rolling updates by default in the DaemonSet agent
  # ref: https://kubernetes.io/docs/tasks/manage-daemon/update-daemon-set/
  updateStrategy:
    # You can also customize maxUnavailable, maxSurge or minReadySeconds if you
    # need it
    type: RollingUpdate

  ## Extra environment variables that will be pass onto deployment pods
  env: {}

  ## Add aditional pod annotations on pods created by DaemonSet
  podAnnotations: {}

# If is behind a proxy you can set the proxy server
proxy:
  httpProxy:
  httpsProxy:
  noProxy:

# Set daemonset timezone
timezone:

# Set daemonset priorityClassName
priorityClassName:

ebpf:
  # Enable eBPF support for Falco
  enabled: true # required for GKE: https://falco.org/docs/third-party/#gke

  settings:
    # Needed to enable eBPF JIT at runtime for performance reasons.
    # Can be skipped if eBPF JIT is enabled from outside the container
    hostNetwork: true

auditLog:
  # true here activates the K8s Audit Log feature for Falco
  enabled: false

  dynamicBackend:
    # true here configures an AuditSink who will receive the K8s audit logs
    enabled: false
    # define if auditsink client config should point to a fixed url, not the
    # default webserver service
    url: ""

falco:
  # The location of the rules file(s). This can contain one or more paths to
  # separate rules files.
  rulesFile:
    - /etc/falco/falco_rules.yaml
    - /etc/falco/falco_rules.local.yaml
    - /etc/falco/k8s_audit_rules.yaml
    - /etc/falco/rules.d

  # If true, the times displayed in log messages and output messages
  # will be in ISO 8601. By default, times are displayed in the local
  # time zone, as governed by /etc/localtime.
  timeFormatISO8601: false

  # Whether to output events in json or text
  jsonOutput: true

  # When using json output, whether or not to include the "output" property
  # itself (e.g. "File below a known binary directory opened for writing
  # (user=root ....") in the json output.
  jsonIncludeOutputProperty: true

  # Send information logs to stderr and/or syslog Note these are *not* security
  # notification logs! These are just Falco lifecycle (and possibly error) logs.
  logStderr: true
  logSyslog: false

  # Minimum log level to include in logs. Note: these levels are
  # separate from the priority field of rules. This refers only to the
  # log level of Falco's internal logging. Can be one of "emergency",
  # "alert", "critical", "error", "warning", "notice", "info", "debug".
  logLevel: warning

  # Minimum rule priority level to load and run. All rules having a
  # priority more severe than this level will be loaded/run.  Can be one
  # of "emergency", "alert", "critical", "error", "warning", "notice",
  # "info", "debug".
  priority: debug

  # Whether or not output to any of the output channels below is
  # buffered.
  bufferedOutputs: false

  # Falco uses a shared buffer between the kernel and userspace to pass
  # system call information. When Falco detects that this buffer is
  # full and system calls have been dropped, it can take one or more of
  # the following actions:
  #   - "ignore": do nothing. If an empty list is provided, ignore is assumed.
  #   - "log": log a CRITICAL message noting that the buffer was full.
  #   - "alert": emit a Falco alert noting that the buffer was full.
  #   - "exit": exit Falco with a non-zero rc.
  #
  # The rate at which log/alert messages are emitted is governed by a
  # token bucket. The rate corresponds to one message every 30 seconds
  # with a burst of 10 messages.
  syscallEventDrops:
    actions:
      - log
      - alert
    rate: .03333
    maxBurst: 10

  # A throttling mechanism implemented as a token bucket limits the
  # rate of Falco notifications. This throttling is controlled by the following configuration
  # options:
  #  - rate: the number of tokens (i.e. right to send a notification)
  #    gained per second. Defaults to 1.
  #  - max_burst: the maximum number of tokens outstanding. Defaults to 1000.
  #
  # With these defaults, Falco could send up to 1000 notifications after
  # an initial quiet period, and then up to 1 notification per second
  # afterward. It would gain the full burst back after 1000 seconds of
  # no activity.
  outputs:
    rate: 1
    maxBurst: 1000

  # Where security notifications should go.
  # Multiple outputs can be enabled.
  syslogOutput:
    enabled: false

  # If keep_alive is set to true, the file will be opened once and
  # continuously written to, with each output message on its own
  # line. If keep_alive is set to false, the file will be re-opened
  # for each output message.
  #
  # Also, the file will be closed and reopened if Falco is signaled with
  # SIGUSR1.
  fileOutput:
    enabled: false
    keepAlive: false
    filename: ./events.txt

  stdoutOutput:
    enabled: true

  # Falco contains an embedded webserver that can be used to accept K8s
  # Audit Events. These config options control the behavior of that
  # webserver. (By default, the webserver is enabled).
  webserver:
    enabled: true
    listenPort: 8765
    k8sAuditEndpoint: /k8s-audit

  # Possible additional things you might want to do with program output:
  #   - send to a slack webhook:
  #     program: "\"jq '{text: .output}' | curl -d @- -X POST https://hooks.slack.com/services/XXX\""
  #   - logging (alternate method than syslog):
  #     program: logger -t falco-test
  #   - send over a network connection:
  #     program: nc host.example.com 80

  # If keep_alive is set to true, the program will be started once and
  # continuously written to, with each output message on its own
  # line. If keep_alive is set to false, the program will be re-spawned
  # for each output message.
  #
  # Also, the program will be closed and reopened if Falco is signaled with
  # SIGUSR1.
  programOutput:
    enabled: false
    keepAlive: false
    program: mail -s "Falco Notification"<EMAIL_ADDRESS>    # program: |
    #   jq 'if .priority == "Emergency" or .priority == "Critical" or .priority == "Error" then
    #     { attachments: [{ text: .output, color: "danger" }]}
    #   elif .priority == "Warning" or .priority == "Notice" then
    #     { attachments: [{ text: .output, color: "warning" }]}
    #   elif .priority == "Informational" then
    #     { attachments: [{ text: .output, color: "good" }]}
    #   else
    #     { attachments: [{ text: .output }]}
    #   end' | curl -d @- -X POST https://hooks.slack.com/services/xxxxxxxxx/xxxxxxxxx/xxxxxxxxxxxxxxxxxxxxxxxx

  httpOutput:
    enabled: false
    url: http://some.url

  # Falco supports running a gRPC server with two main binding types
  # 1. Over the network with mandatory mutual TLS authentication (mTLS)
  # 2. Over a local unix socket with no authentication
  # By default, the gRPC server is disabled, with no enabled services (see grpc_output)
  # please comment/uncomment and change accordingly the options below to configure it.
  # Important note: if Falco has any troubles creating the gRPC server
  # this information will be logged, however the main Falco daemon will not be stopped.
  # gRPC server over network with (mandatory) mutual TLS configuration.
  # This gRPC server is secure by default so you need to generate certificates and update their paths here.
  # By default the gRPC server is off.
  # You can configure the address to bind and expose it.
  # By modifying the threadiness configuration you can fine-tune the number of threads (and context) it will use.
  grpc:
    enabled: false
    threadiness: 0

    # gRPC unix socket with no authentication
    unixSocketPath: "unix:///var/run/falco/falco.sock"

    # gRPC over the network (mTLS) / required when unixSocketPath is empty
    listenPort: 5060
    privateKey: "/etc/falco/certs/server.key"
    certChain: "/etc/falco/certs/server.crt"
    rootCerts: "/etc/falco/certs/ca.crt"

  # gRPC output service.
  # By default it is off.
  # By enabling this all the output events will be kept in memory until you read them with a gRPC client.
  # Make sure to have a consumer for them or leave this disabled.
  grpcOutput:
    enabled: false

customRules: {}
  # Although Falco comes with a nice default rule set for detecting weird
  # behavior in containers, our users are going to customize the run-time
  # security rule sets or policies for the specific container images and
  # applications they run. This feature can be handled in this section.
  #
  # Example:
  #
  # rules-traefik.yaml: |-
#   [ rule body ]

integrations:
  # If Google Cloud Security Command Center integration is enabled, Falco will
  # be configured to use this integration as program_output and sets the following values:
  # * json_output: true
  # * program_output:
  #     enabled: true
  #     keep_alive: false
  #     program: "curl -d @- -X POST --header 'Content-Type: application/json' --header 'Authorization: authentication_token' url"
  gcscc:
    enabled: false
    webhookUrl: http://sysdig-gcscc-connector.default.svc.cluster.local:8080/events
    webhookAuthenticationToken: b27511f86e911f20b9e0f9c8104b4ec4
  # If Nats Output integration is enabled, Falco will be configured to use this
  # integration as file_output and sets the following values:
  # * json_output: true
  # * json_include_output_property: true
  # * file_output:
  #     enabled: true
  #     keep_alive: true
  #     filename: /tmp/shared-pipe/nats
  natsOutput:
    enabled: false
    natsUrl: "nats://nats.nats-io.svc.cluster.local:4222"
  # If SNS Output integration is enabled, Falco will be configured to use this
  # integration as file_output and sets the following values:
  # * json_output: true
  # * json_include_output_property: true
  # * file_output:
  #     enabled: true
  #     keep_alive: true
  #     filename: /tmp/shared-pipe/nats
  snsOutput:
    enabled: false
    topic: ""
    aws_access_key_id: ""
    aws_secret_access_key: ""
    aws_default_region: ""

  # If GCloud Pub/Sub integration is enabled, Falco will be configured to use this
  # integration as file_output and sets the following values:
  # * json_output: true
  # * json_include_output_property: true
  # * file_output:
  #     enabled: true
  #     keep_alive: true
  #     filename: /tmp/shared-pipe/nats
  pubsubOutput:
    enabled: false
    topic: ""
    credentialsData: ""
    projectID: ""

# Allow Falco to run on Kubernetes 1.6 masters.
tolerations:
  - effect: NoSchedule
    key: node-role.kubernetes.io/master

scc:
  # true here enabled creation of Security Context Constraints in Openshift
  create: true

# Add initContainers to Falco pod
extraInitContainers: []


Fixes: #1131, Enable graceful sidecar kill

Changes
Fixes: https://github.com/tektoncd/pipeline/issues/1131

Adds a boolean flag ForceTerminationDisabled to the Sidecar struct to enable users to avoid sidecar termination when all the steps are finished in the pipeline.
By default, it still does the forceful termination of SideCar using the Nop image (tianon/true)
The idea is, there can be cases where the sidecar needs to do some processing and upload work when the Taskrun is done/completed. A sidecar should not be interrupted and the termination of the Sidecar can be delegated to the user injecting it in those cases.

Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
    - Added a new configuration to the Sidecar struct. The boolean flag `ForceTerminationDisabled` can be set to true if you don't want your sidecar to be terminated automatically by Tekton when all steps in a task run is complete.

/kind feature
/ok-to-test

Thanks for this @shahnewazrifat ! I think this feature makes a lot of sense - ages ago with got some feedback from the Prow folks that they'd like this kind of functionality as well ( @ cjwagner )
I could see making a TEP for this as well, since it does feel like a new feature and there might be some scenarios to explain (e.g. timeouts) but since that's the only thing I can think of I could see going ahead with this without a TEP as well, does anyone have a preference @afrittoli @vdemeester @sbwsg @ImJasonH @dlorenc @pritidesai ? (and @skaegi had mentioned trying to mirror the proposed sidecar functionality as well)
One request I have is to change the name of the flag slightly, to make it so that the name is worded as a positive (vs negative - i.e. I think disabled: false is a bit confusing). maybe instead of ForceTerminationDisabled it could be something like TerminateAfterSteps / ForceTerminate or the opposite WaitForSidecar etc.

Thanks for this @shahnewazrifat ! I think this feature makes a lot of sense - ages ago with got some feedback from the Prow folks that they'd like this kind of functionality as well ( @ cjwagner )
I could see making a TEP for this as well, since it does feel like a new feature and there might be some scenarios to explain (e.g. timeouts) but since that's the only thing I can think of I could see going ahead with this without a TEP as well, does anyone have a preference @afrittoli @vdemeester @sbwsg @ImJasonH @dlorenc @pritidesai ? (and @skaegi had mentioned trying to mirror the proposed sidecar functionality as well)
One request I have is to change the name of the flag slightly, to make it so that the name is worded as a positive (vs negative - i.e. I think disabled: false is a bit confusing). maybe instead of ForceTerminationDisabled it could be something like TerminateAfterSteps / ForceTerminate or the opposite WaitForSidecar etc.

Pleasure @bobcatfish ! Totally love this community.
Yes, I was even thinking about going a bit further and make it the default behaviour for sidecars. I.e., auto termination will only happen when specified.  Keeps running.
I don't think many users are aware of this force termination if they didn't deep dive into the docs.
Re: the flag name 😄  I got confused myself couple of time, so yeah. forcerTerminate sounds reasonable to me.
Thank you so much for the feedback!

I could see making a TEP for this as well, since it does feel like a new feature and there might be some scenarios to explain (e.g. timeouts) but since that's the only thing I can think of I could see going ahead with this without a TEP as well, does anyone have a preference @afrittoli @vdemeester @sbwsg @ImJasonH @dlorenc @pritidesai ? (and @skaegi had mentioned trying to mirror the proposed sidecar functionality as well)

I think I would definitely see value in having a TEP for this indeed :upside_down_face:

Thanks for this @shahnewazrifat ! I think this feature makes a lot of sense - ages ago with got some feedback from the Prow folks that they'd like this kind of functionality as well ( @ cjwagner )
I could see making a TEP for this as well, since it does feel like a new feature and there might be some scenarios to explain (e.g. timeouts) but since that's the only thing I can think of I could see going ahead with this without a TEP as well, does anyone have a preference @afrittoli @vdemeester @sbwsg @ImJasonH @dlorenc @pritidesai ? (and @skaegi had mentioned trying to mirror the proposed sidecar functionality as well)
One request I have is to change the name of the flag slightly, to make it so that the name is worded as a positive (vs negative - i.e. I think disabled: false is a bit confusing). maybe instead of ForceTerminationDisabled it could be something like TerminateAfterSteps / ForceTerminate or the opposite WaitForSidecar etc.

I chose one similar to WaitForSidecar 😄
Using waitForTermination since we're already inside Sidecar struct. Sidecar.WaitForTermination felt good
Let me know what you feel!
Thanks for the great idea. Almost missed it! The double negative was confusing to me even when writing tests 🤕

I'm going to propose that we table this PR until the TEP, https://github.com/tektoncd/community/pull/191, is resolved and merged.  We can reopen once that's happened and pick up the review then.
If anyone disagrees, please feel free to come back and reopen.


Connection unavailable every evening about 6...8 pm?

I recently observed, that the connection status changes to unavailable every evening about 6...8 pm. It changes to available again about 2 am. In case of unavailabilty also the Skoda APP reports unavailabilty of vehicle data. See screenshot of one entity ("white areas" mark periods of anavailabilty):

Does anyone observe the same behaviour and has hints for changing the behaviour (maybe configuration topic)?
Thank you very much

We've received reports about this, and it seems to be related to restrictions being imposed by VAG on how often you can poll data.
As a workaround, you could try increasing the polling interval

Thank you very much for the reply. Now I have changed the polling interval from 60s to 90s and will check, if the behaviour is different. Btw. is there any mechanism to initate polling of data by automation e.g. in case of starting charging by HA?

There currently is not, but this would be a great feature request!

So weird. I'm not having these issues at all ...
Poll frequency = 30 (seconds)

I believe this issue is isolated to the old API which is why Enyaq owners won't be affected.

Update: After changing the polling interval from 60s to 90s there was no period of unavailability last night!
Thank you very much.


Update styles for checkbox-card and radio-button-card CSS-only components

https://www.figma.com/file/xZ0IW0MJO0vnFicmrHiKaY/Components-Post?type=design&node-id=22630%3A6660&mode=design&t=hsWpJcoKNKUVkNkD-1
### Tasks
- [ ] https://github.com/swisspost/design-system/issues/2686

Component has been updated already


Add the RPM of the cars in the segments displays

I am testing the plugin in assetto corsa with F1 cars and will add suggestions that I find will be useful. Cheers

Should now be there in 0.9.0.


ast contained unexpected data: unexpected type *ast.InterfaceType: &{5772478 0xc00029c600 false}

$ go generate
2024/10/10 18:16:20 flutter-go-bridge generator
2024/10/10 18:16:22 Parsing
2024/10/10 18:16:22  - Package github.com/openimsdk/openim-sdk-core/v3/open_im_sdk_callback
2024/10/10 18:16:22    - File F:\1024\flutter_openim_sdk\openim-sdk-core-3\open_im_sdk_callback\callback_client.go
2024/10/10 18:16:22    - File F:\1024\flutter_openim_sdk\openim-sdk-core-3\open_im_sdk_callback\callback_go_sdk.go
2024/10/10 18:16:22 Processing
2024/10/10 18:16:22  - Type Base
2024/10/10 18:16:22 ast contained unexpected data: unexpected type *ast.InterfaceType: &{5772478 0xc00029c600 false}
exit status 1
callback_client.go:15: running "go": exit status 1
exemple:
type Base interface {
OnError(errCode int32, errMsg string)
OnSuccess(data string)
}

Hi, this is expected as the generator currently doesn't support interfaces. An alternative would be to use static functions where possible.


Media Controller / Title / Subtitle / Artwork Customisation

Hi,
using media3-rc01 the title, subititle, artwork somehow get extracted (i think from icy info) from exo player and is being placed. but this also means it overrides any custom title, subtitle or artwork the developer has set programtically to the mediaitem in for example Android Auto usage, but also in the notification.
I have tried extending a DefaultNotificationProvider overriding the contentTitle en contentText, but it only grabs those values if it otherwise can't fill it. And it only works for media notifications but not for the actual media controller in Android Auto for example.
see my screenshot:

and my code:

what stands out is that the ContentText is respected. This is because my icy stream does not provide artist information. however the contentTitle is not respected because the stream provides it's own. To me this looks like some kind of race condition or im not adjusting the notification and mediacontroller information correctly.
As a developer i would i ideally override some kind of MediaControllerMetadataProvider and in this class i would override the function that would respect certain pieces of meta information for the controller. I also think MediaController and Notification should be handled the same way. I think this was actually the case aswell in media2.

He, quite complicated case :). I can not repro this behaviour I'm afraid.
When I set properties in MediaMetadata of the MediaItem then I can not repro this in the demo app or the session demo app (with notification). Values from the MediaItem have precedence for me.
I think to verify you could do new MediaMetdata.Builder().setTitle("Item title").setArtist("Item artist").build() and use that with your media item. That's what I've done and I've seen the values on API 30/33. LMK if this works.
I tried an ICY stream and an MP3 file with ID3 tags.
To rule out some complications that make things a bit difficult: Starting from Android 13/API 33 the System UI media notification (mini player) is primarily using values from the media session metadata of the platform media session. The screenshot you posted seems to be from API 33 I think. On this API level, the values from the DefaultMediaNotificationProvider would be used as a fallback only. I think on lower API devices/emulators, you'd see the values from your subclass of DefaultMediaNotificationProvider.
In the Android 13/API 33 case, the Media3 MediaMetadata object that the session receives from ExoPlayer [1][2] via onMediaMetadataChanged(MediaMetadata) is converted to a legacy MediaMetadataCompat from which the values are read by SystemUI to populate the notification/mini player. If I'm not mistaken,  the keys METADATA_KEY_DISPLAY_TITLE|METADATA_KEY_TITLE and METADATA_KEY_ARTIST are used.

what stands out is that the ContentText is respected

I think in your code snippet, I'd flip the values and use metadata.title as ContentTitle and metadata.subtitle as ContentText for clarity. The ContentTitle is the slightly larger line in the notification I think. What is respected then, is the ContentText with value metadata.title.
The behaviour you see could be explained by testing on Android 13 with an MediaItem of an ICY stream that sets either MediaMetadata.title and/or MediaMetadata.displayTitle but_not MediaMetadata.artist. The System UI would take the title and use it on the first line. The missing artist would fallback to  ContentText of the media notification provider.
[1]  https://github.com/androidx/media/blob/release/libraries/exoplayer/src/main/java/androidx/media3/exoplayer/ExoPlayerImpl.java#L1900
[2]
https://github.com/androidx/media/blob/release/libraries/exoplayer/src/main/java/androidx/media3/exoplayer/ExoPlayerImpl.java#L2938
[If I'm not mistaken] https://android.googlesource.com/platform/frameworks/base/+/master/packages/SystemUI/src/com/android/systemui/media/MediaDataManager.kt#677
[converted] https://github.com/androidx/media/blob/release/libraries/session/src/main/java/androidx/media3/session/MediaUtils.java#L549


Fix NSInternalInconsistencyException in - [ARModernArtworkInfoViewController aspectRatioConstraintForImageView:image:], line 100

Version: 2.4.4 (2015.10.15) | sy.art.folio
Stacktrace
ARModernArtworkInfoViewController;aspectRatioConstraintForImageView:image:;ARModernArtworkInfoViewController.m;100
ARModernArtworkInfoViewController;updateWithArtwork:;ARModernArtworkInfoViewController.m;92
NSArray(ObjectiveSugar);each:;NSArray+ObjectiveSugar.m;51
ARModernArtworkInfoViewController;updateWithArtwork:;ARModernArtworkInfoViewController.m;85
ARModernArtworkInfoViewController;viewWillAppear:;ARModernArtworkInfoViewController.m;55
Reason
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Multiplier is not finite!  That's illegal.  multiplier:nan'
Link to HockeyApp

https://rink.hockeyapp.net/manage/apps/74977/crash_reasons/69448883

Fixed in 2.5.5


stake: correct handling of validator updates

Prior to this commit, setting validators with enabled: false did not trigger state updates.

Rebased without the test run since the CI hung for some reason and won't be cancelled (??)


Consider using ᚬ for "o"

Both ᚢ and ᚬ can be used to transcribe "o". See if the latter seems popular

Seems ᚢ was used even for clear "o" s, like in "Thor". Let's keep it the way it is.


year 53606 is out of range

When running
aws cognito-idp create-user-pool-client --user-pool-id local --client-name client --endpoint http://auth.localhost
with .cognito/config.json
{}

I get this error:
year 53606 is out of range

My docker-compose looks something like this:
auth:
  image: jagregory/cognito-local:3.1.2
  container_name: auth
  restart: always
  ports:
    - 9229:9229
  labels:
    - "traefik.enable=true"
    - "traefik.http.routers.auth.rule=Host(`auth.localhost`)"
    - "traefik.http.routers.auth.entrypoints=web"

Does this look familiar? Thanks!

FYI
aws cognito-idp create-user-pool-client --user-pool-id local --client-name client --endpoint http://<IP_ADDRESS>:9229

has the same effect

Got the same error.  Are you using Python's Boto3?  It seems that Python API expects the time returned from the service to be in seconds since epoch, but cognito-local returns time in microseconds.

Ah weird, thanks for investigating this. I'm only using Node which must be more tolerant of the date format. I see @rafael-ladislau has created a PR to resolve this so I'll get that merged.


Could you add a license to your repo?

My organization would like to use and modify some of your scripts, but the absence of a license prevents us from doing so. Could you add one?
Thank you!

Done. I just want to officially note here that most of these haven't been updated in some time and I no longer advocate for using many of the - but feel free to borrow what you like.
https://github.com/opragel/OSX_Scripts/blob/master/LICENSE.


Issue With Perms

I gave my members the perm archoncrates.crate.use or archoncrates.command.use but it still says 'You do not have the permission to open/use a virtual crate

Make sure you are using the correct permission for the correct version of the plugin.

What is the correct permission for v17.3

Here is a list of all permissions for v17.3

Access
Permission

COMMAND_HELP
archoncrates.command.help

COMMAND_REMOVE
archoncrates.command.remove

COMMAND_INFO
archoncrates.command.info

COMMAND_KEYS
archoncrates.command.keys

COMMAND_VKEYS
archoncrates.command.vkeys

COMMAND_CRATES
archoncrates.command.crates

COMMAND_FILES
archoncrates.command.files

COMMAND_UPDATE
archoncrates.command.update

COMMAND_CREATE
archoncrates.command.create

COMMAND_CREATE_VIRTUAL
archoncrates.command.create.virtual

COMMAND_RELOAD
archoncrates.command.reload

COMMAND_CRATE
archoncrates.command.crate

COMMAND_KEY
archoncrates.command.key

COMMAND_KEY_ALL
archoncrates.command.key.all

COMMAND_VIRTUAL_KEYS
archoncrates.command.vkey

COMMAND_VIRTUAL_KEYS_ALL
archoncrates.command.vkey.all

COMMAND_REMOVE_VIRTUAL_KEY
archoncrates.command.remove.vkey

COMMAND_HISTORY
archoncrates.command.history

COMMAND_VOUCHER_NEW
archoncrates.command.voucher.new

COMMAND_VOUCHER_REDEEM
archoncrates.command.voucher.redeem

COMPLETE_TAB
archoncrates.completetab

OPEN_CRATE_WITH_ANY_KEY
archoncrates.crate.open.any

OPEN_CRATE
archoncrates.crate.open

OPEN_VIRTUAL_CRATE
archoncrates.crate.open.virtual

VIEW_PRIZES
archoncrates.view.priszes

BREAK_CRATE
archoncrates.event.break.crate

SIGN_USE_BUY
archoncrates.sign.use.buy

SIGN_CREATE_NORAML
archoncrates.sign.create

SIGN_CREATE_VIRTUAL
archoncrates.sign.create.virtual

SIGN_BREAK
archoncrates.sign.break

My e=tester can't open the virtual crate in v17.3 even tho i gave him the command OPEN_VIRTUAL_CRATE

*tester

Can you also set a percentage of the person getting a certain item?

Take a look at these videos, they may help you
https://www.youtube.com/watch?v=70hsPdsd_LA
https://www.youtube.com/watch?v=Bo5_5b9-xY4


Handle Next Gen MCAS as a separate assessment

What does this do?

Handles new "Next Gen" MCAS data. This new format has a new range for scaled scores (400 to 600) and new performance levels.
This PR includes a migration to detect and update "Next Gen" MCAS records by checking which range their scaled scores fall into.
It also updates the McasRow importer class to detect future "Next Gen" MCAS records that come through from X2.

How does the UI change?
School Overview

If the majority of students in the filters have most recent "Next Gen" MCAS scores, the School Overview shows the "Next Gen" performance levels as filters. For example, 9th graders will have "Next Gen" scores as their most recent since the last time they took MCAS was at the end of 8th grade, and "Next Gen" was administered in grades 3-8.

If the majority of students in the filters have most recent old MCAS scores, the School Overview shows the old performance levels as filters.

Student Profile

New charts to show "Next Gen" scores, scales, and categories when a student has "Next Gen" results. (Since there's only one Next Gen score per student in the database these graphs show points right now instead of lines.)

Homeroom

The homeroom view doesn't change.

Issue

Fix  #1171.

Change list

[x] Add new model for "Next Generation" MCAS
[x] Add fake data generator with new "Next Generation" scaled scores
[x] Add new chart to Student Profile if relevant data is present
[x] Update School Overview page
[x] Update Homeroom Roster page
[x] Update Student Report
[x] Update X2AssessmentImporter code to correctly classify incoming MCAS data from X2
[x] Write migration to re-assign "Next Generation" student assessments
[x] Fix spec
[x] Add more spec coverage for areas that need it
[x] QA against real data locally
[x] Add screenshots of UI and explanations about changes to PR
[ ] Deploy, run migrations, and triple-check in IE

Deployment plan: plan is to deploy Wednesday evening after school hours so that @snoopyuri can do manual QA around the Next Gen MCAS data before principals/teachers see it the next day.

Deploy going smoothly so far! Running Student.update_recent_student_assessments in prod to get those fresh fresh data points!


Added python version of Sally + Fixed some of your markdown violations

I know.. even markdown has rules, don't ask.
Anyways this is my python version, you can try it out yourself before you commit it to your repo I think it works pretty well and I am pretty happy that it is ready now. It can also do OCR already, everything should work fine, try it out and let me know if you like it :)

Outsiders perspective: I'd highly recommend splitting the ai functionality into a cog and also using .env files (making sure to gitignore them). I also recommend you to use python venvs and freeze your dependencies to a requirements.txt. (you can use CarlBot as an example)
This is also highly applicable for the C# implementation in the context of .env. Keeping secrets in a .cs file that is tracked by git is a recipie for disaster :).

I'll do that, I got another repo open for it anyways, so far I actually had no problems running it without a venv since the packages that I use don't get major updates that could break them. I'll look into it tho, id love to make it even better

So I implemented your Idea with the .env file here, it works quiet nicely, thanks for the advice. I also mentioned you and your bot in my repo :)
I did not implement the cog thing (yet, I might do that too soon, depends on how bored I'll get) because I would need to rewrite my entire code to use classes and I don't really see the reason for my bot to use cogs, since I only listen to messages and then execute functions based on them, aka I don't have many commands nor listeners. Something that I am unfamiliar with is also if I need to make my other functions async or if they just work as they are. I did not test wether the history list I use gets messed up when lots of people use it at once ( and I don't know if using async fixes that ), so if you have any more info on that for me then that would be awesome :) ( I don't have too much experience with discord bots and async functions )

yeah I would just make a new repo, I thought about it and there's no way I'd put all this python code in here especially since I just updated everything on the c# side I would never want to have some outdated confusing .py code sitting around in files un-updated confusing people

I did and I am also updating things ofc


Were you able to reproduce results?

HI, can you also share the training statistics? That would be very helpful.

I checked that the model converges. But I couldn't afford to train it around for a long time.

@sooftware For how many number of epochs did you check for? and on what dataset?

KsponSpeech which contains 1,000 hours of Korean speech.
I experiment with 7~8 epochs.

@sooftware Did you test and see the WER? or just trained it?

Korean usually calculate CER. I got a 20-30 CER. loss was continuing to converge.

@sooftware Thanks for the update.

@sooftware can you share your training script and the hyperparameters?

Refer this repository

@sooftware Thanks.


CA - 2 (TWO) Production Errors (Last Mile Failures)

Problem statement
Production Errors on 1/2/2023
What you need to know
Example 1: ca-dph.elr-saphire

To do

Assign to an Engineer to Investigate
Resubmit?

sftp check passed. These can be resent @sliu1000

resubmission completed

@Jcavallo7 @sliu1000 To confirm, resubmission went through no problems? I can close this?


Choosing a device out of .list() doesn't work - "cannot move out of borrowed content"

fn start_capture(index: usize) -> () {
    let devices = pcap::Device::list().unwrap();
    let chosen = devices.iter().nth(index).unwrap();//last unwrap gets rid of Option
    println!("Chosen {:#?}:", chosen);
    let mut cap = chosen.open();
}

When compiling this rust complaines on the chosen.open() line saying "cannot move out of borrowed content". Why is this so? Shouldn't open() take a reference to self (&self) instead of taking ownership (self)?
I am trying to let the user select an interface from the existing list and capture on that.

Looks like you'd probably want to use Vec::remove(), it takes an index and returns the object from that position as an owned one.
Here's your snippet with my modifications
fn start_capture(index: usize) -> () {
  let mut devices = pcap::Device::list().unwrap();  // devices needs to be mutable, since we're stealing from it
  let chosen = devices.remove(index);  // no bounds checking though, be careful!
  println!("Chosen {:#?}:", chosen);
  let mut cap = chosen.open();
}

Another workaround is to use Capture::from_device(device_list[3].name.as_ref()) like below.
    let device_list = Device::list()?;
    for (i, d) in device_list.iter().enumerate() {
        println!("{} = {:?}", i, d);
    }
    // let _ = Capture::from_device(device)
    // let device = Device::open()?;
    // let device = Device::from(device_list[0].name.as_ref());
    // println!("device = {:?}", device);
    // let mut cap = device.open()?;
    let mut cap = Capture::from_device(device_list[3].name.as_ref())?
        .promisc(true)
        .snaplen(64)
        .open()?;

    if let Ok(packet) = cap.next() {
        println!("received packet! {:?}", packet);
    }

Add derive(Clone) to struct Device might increase usability.

Does this need fixing within pcap itself or are the solutions provided sufficient (in which case the issue can be close)?

Does this need fixing within pcap itself or are the solutions provided sufficient (in which case the issue can be close)?

It's an ergonomistic issue and I'd like to investigate.


Fix loc issue

This is how the article currently show in the localized versions:

I think the changes I made would fix that.

This PR doesn't cover all the articles with this problem, but covered most of them.

@JasonCard after we merge this PR, can you make sure to follow up and see if the issue is addressed for loc? Thanks.

@mairaw @Youssef1313 Thank you for working on this fix. Yes, I'll follow up to check if this issue is resolved.

@mairaw, seems like this didn't fix the issue. :cry:
This is strange because https://docs.microsoft.com/fr-fr/dotnet/framework/configure-apps/file-schema/runtime/ (and many others) renders correctly and the only difference I could find is the backslash thing.
https://github.com/dotnet/docs/blob/master/docs/framework/configure-apps/file-schema/runtime/index.md.
cc: @JasonCard

@Youssef1313 @mairaw I'm sorry for the delayed update on this. I was monitoring for this fix to publish for loc, but after investigation found that all of our localized update commits to dotnet/docs loc repos were failing since 11/12. We've found the root cause, but having difficulty resolving the issue, so currently working on a workaround to have all affected files committed and published by Monday. Will update.

@Youssef1313 @mairaw It's fixed now, although MT engine is adding an extra space before closing brackets, so I will follow up to see if that can be fixed on MT engine side:

@Youssef1313 @mairaw We have a question, are the escape/backslash chars () before the opening brackets (<) necessary? If those are removed, then those elements will be blocked from translation. If those are needed, then we can request for feature to update our transformer to block them even in those cases.

yes, they are; otherwise, they are not rendered @JasonCard
Compare here on the preview:
Look like it will render:
with the escape:
<configuration>
without the escape

This is how it was written:

Thank you for confirming. I will request for a feature to update our transformer to block those even with the escape char, so no fix is needed on your end. Will update on this.

@mairaw Would it be possible to use the inline no-loc md extensions like below?
# :::no-loc text=”<specifiedPickupDirectory>"::: Element (Network Settings)
[**:::no-loc text=”<configuration>":::**](../configuration-element.md)\
cc @mayast

Can you do one as a test @JasonCard?

@mairaw Okay, I've opened this PR as test https://github.com/dotnet/docs/pull/16079.


fix hostname calculation when using services

fixes #5450
Signed-off-by: Marcos Lilljedahl<EMAIL_ADDRESS>

I'll wait for @vito's comments before addressing tests failures.

@sipsma Unfortunately I don't think that's an easy change, because the llb.Hostname has to be added alongside all the other llb.RunOptions that go into creating the Container.FS that is evaluated by Container.Start. It's the same reason I had to jump through hoops in #5322.
I'm not sure if anyone is even making use of this aspect of the API, and there's an easy workaround (just call WithExposedPort with a bogus value), and the long-term fix is #5322, so I think this is probably OK to just merge for now.
However it also seems worth considering rolling back the core/host.go changes in #5346; it seems like that could have smaller fallout since it's for a heavily experimental feature anyway (dagger do).

Unfortunately I don't think that's an easy change, because the llb.Hostname has to be added alongside all the other llb.RunOptions that go into creating the Container.FS that is evaluated by Container.Start. It's the same reason I had to jump through hoops in https://github.com/dagger/dagger/pull/5322.

@vito Ah right, I remember that whole saga of hoop jumping now, thanks, makes sense.

However it also seems worth considering rolling back the core/host.go changes in https://github.com/dagger/dagger/pull/5346; it seems like that could have smaller fallout since it's for a heavily experimental feature anyway (dagger do).

Yeah I agree that's an option worth considering too, kind of a hard call. But one thing I'm just realized is that the hostname setting might actually break other stuff besides this particular issue involving local LLB.
For example, if you had c.Container().From("image:tag1") and c.Container().From("image:tag2"), but it turns out that tag1 and tag2 actually point to the same digest, then even though the LLB digests differ, buildkit will internally resolve them and cache based on the resolved sha rather than tag. But if we always set hostname on an exec from the LLB digests, then that caching wouldn't be possible anymore (right? double check my thinking here).
So if that's correct then that's probably an argument for this patch.
One other small benefit of not setting hostnames every time is that it allows buildkit to re-use network namespaces for the execs. No clue if that's really much of a benefit outside extremely high load scenarios though, just worth mentioning.

Yeah that's all accurate. Those are also more scenarios where it'd be great if we could get the actual cache key out of Buildkit somehow.
Either way we won't be setting hostnames all the time in the long run since #5322 changes it so that only the service gateway execs set a hostname, so I'm fully onboard with that already. Only trying to identify which "quick fix" would result in fewest complaining users. :P In all likelihood both will be 0, so let's :shipit:

Those are also more scenarios where it'd be great if we could get the actual cache key out of Buildkit somehow.

Agreed, or with the thing you figured out yesterday at least we could the individual resolved op digests and construct our own "DAG digest" out of them even if Buildkit won't give you that. It still wouldn't be perfect since it wouldn't account for buildkit's ability to selectively run cache based hashes for some ops, but it would be much closer

closing in favor of https://github.com/dagger/dagger/pull/5468. Thx @vito


Figure out how to handle departures with no SIDs

Some airports (KPDT, there are probably others) don't have any departures but do have an initial altitude. Gotta handle that somehow so the initial altitude helper text will still show from those airports.
Probably have to add an airportCode field to the departures, then have a way to have a catch-all departure that will match anything.

KMWH

Make a new table for extended airport information and then just include that in the airport information that's returned in the flight plan. Then that can be checked on the client side and if it is there just show the text.


Support Bitbucket.org repositories in vscode.dev

It should be self-describing from the title, but it'd be great if more support for different github repository sites would be supported in vscode.dev (open a remote repository) to open things up a bit more. Thanks for considering!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

Are there any updates?


fix(all/chineseanime): Update baseUrl + add StreamVid extractor

Closes #2977
^ Actually it doesn't, because playlist-utils got slightly trolled recently, but everything should work well after un-trolling playlist-utils :+1:
Checklist:

[ ] Updated extVersionCode value in build.gradle for individual extensions
[x] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[x] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[ ] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio
[ ] Have removed web_hi_res_512.png when adding a new extension

won't it need to go override 9?

won't it need to go override 9?

What

won't it need to go override 9?

What

what jmir merged is override 6 and current latest version was 14.8 so it actually got downloaded I suppose

hence whoever updated extensions under this 1h won't get your fix

won't it need to go override 9?

should have been 7

won't it need to go override 9?

should have been 7

yeah didn't know this new multi-lib/theme stuff


Feature Request: kubeip helm chart

Is your feature request related to a problem? Please describe.
instead of people creating their own way to automate the installation of kubeip ... please provide a helm chart.
Describe the solution you'd like
Fast and easy way to deploy kubeip to my environment via helm chart.

KubeIP v2 is deployed as DaemonSet, the YAML is pretty simple and needs to configure target nodes with nodeSelector or affinity. I see no reason to create Helm chart for this.


Update local docs in the paragon repo

PRs:

https://github.com/openedx/paragon/pull/3078
https://github.com/openedx/paragon/pull/3075


feat: extensions

This pull request adds an Extension system to Chameleon as a replacement for the half-broken module system.

Are the extensions' #onEnable methods called when post loaded?

Doesn't look like it, I'll fix that and test it before merging


Models are displayed too large / floating on iOS 17.5

Description
On iOS 17.5.1 we observe two issues on iOS:

Models are displayed too large.
It looks like the models are "floating" above the ground.

We did not observe these issues in prior iOS versions.
Both issues can be seen in the following videos:
https://github.com/user-attachments/assets/1e1a2431-c02e-4fa8-be00-513096f17d21
https://github.com/user-attachments/assets/069b5ec0-d48e-415f-8c1c-393faa7a03be
Note that the closet in the background is exactly 200 cm, like the astronaut is supposed to be.
Tested on multiple iOS devices. On Android everything looks fine. Movie clips are from an iPhone 13.
Live Demo
https://modelviewer.dev/examples/augmentedreality/#ar
Version

model-viewer: v3.5.0

Browser Affected

[x] Chrome
[ ] Edge
[ ] Firefox
[ ] IE
[x] Safari

OS

[ ] Android
[x] iOS
[ ] Linux
[ ] MacOS
[ ] Windows

AR

[ ] WebXR
[ ] SceneViewer
[x] QuickLook

@AdaRoseCannon Looks like a Quick Look floor-finding regression?

Please file an issue via Feedback Assistant and include the videos.


[GRANT] Epic for Arbitrum GRANT - GMX Short Funding Bot

@fieldtheory123 is the grant done?

https://www.notion.so/volumefi/EPIC-06-14-24-GMX-grant-application-GMX-Short-Funding-Bot-2ea9d913cc95460595f7416f81b48130


Use CocoaTouch framework with Cocoapods 0.36

Update project to use frameworks.
http://blog.cocoapods.org/Pod-Authors-Guide-to-CocoaPods-Frameworks/
Pending final release of CocoaPods 0.36

Hi Jesse I've just read the article about the new pod framework, is there anything that us users have to do to cope with the update?

@Antairez - No, everything should be ok! :+1:
If not, I'll put it in the release notes. :smile:

v7.0 now works with cocoa touch frameworks.


Is there a GPU support for local LLM's?

Hi and thank you for your work!
I wonder if it is possible to use GPU for local LLMs "from the box" or should I build and run server of llama.cpp to make it happen?
CPU inference is slow even when using all of my 32 threads...

Thank you for a quick response! I'll try building llama.cpp from source.
Closing the issue.

i think need write this instruction in README


Bump version in gulp task

Flow

Read package.json
Parse version with npm/node-semver
Bump
Update package.json and dist/package.json
Package and archive as zip
Create release with version
Upload zip

Implement at https://github.com/minodisk/markn/blob/v0.0.4/gulpfile.coffee#L94-L130