lowdown: add flag to disable the Darwin sandbox

This is a program written in a memory‐unsafe language that processes potentially‐untrusted user input. We shouldn’t disable upstream’s sandboxing mechanisms for all downstream consumers without good reason.
Although the sandbox API is officially marked as deprecated, it is used as the basis for the supported App Sandbox and it is extremely unlikely to ever be removed as it is used extensively throughout the OS for service hardening and by third parties like the Chrome sandbox. Nix itself uses it to sandbox builds, and its lack of support for nesting is why this caused problems in the first place. Instead, introduce a lowdown-unsandboxed package that can be used in the nativeBuildInputs of Nix builds, while keeping the sandboxed version of the program for general use. The name might not be ideal, as it remains identical to lowdown on non‐Darwin platforms, but I couldn’t think of a better one.
See: #125004
Closes: #346933

Things done

Built on platform(s)

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

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

[x] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.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.

nixpkgs-vet failure is spurious.

nixpkgs-vet failure is spurious.

that's correct, new entries to all-packages.nix that use callPackage are not allowed
instead you can do something like
 lowdown-unsandboxed = lowdown.override {
    enableDarwinSandbox = false;
  };

That’s not true; it doesn’t complain about callPackage ../by-name/ab/abcd { … }, which is still perfectly valid, and has different semantics in the presence of overlays. The tool just isn’t smart enough to tell that the path to the package expression is an existing one in this case.
It might be reasonable to use .override here anyway, but it’s not a genuine violation of the by-name ratchet checks.

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

1 package marked as broken and skipped:

clightning

13 packages failed to build:

libnixxml
nix-du
nix-plugin-pijul
nix-serve-ng
nixtract
sbomnix
sbomnix.dist
update-python-libraries
vulnix
vulnix.dist
vulnix.doc
vulnix.man
zon2nix

152 packages built:

appvm
attic-client
attic-server
bower2nix
bundix
cabal2nix
cached-nix-shell
cachix (cachix.bin ,cachix.doc)
certspotter
colmena
common-updater-scripts
crate2nix
crystal2nix
devenv
dub-to-nix
dydisnix
harmonia
hci
hci.doc
hercules-ci-agent
home-manager
lix
lix.dev
lix.devdoc
lix.doc
lix.man
lixVersions.lix_2_90
lixVersions.lix_2_90.dev
lixVersions.lix_2_90.devdoc
lixVersions.lix_2_90.doc
lixVersions.lix_2_90.man
lowdown
lowdown-unsandboxed
lowdown-unsandboxed.dev
lowdown-unsandboxed.lib
lowdown-unsandboxed.man
lowdown.dev
lowdown.lib
lowdown.man
lua51Packages.luarocks-nix
lua52Packages.luarocks-nix
lua53Packages.luarocks-nix
lua54Packages.luarocks-nix
luajitPackages.luarocks-nix
luarocks-packages-updater
luarocks-packages-updater.dist
nil
nim_lk
niv (niv.bin ,niv.data)
nix (nixVersions.nix_2_18)
nix-bundle
nix-direnv
nix-eval-jobs
nix-fast-build
nix-fast-build.dist
nix-index
nix-init
nix-inspect
nix-pin
nix-plugins
nix-prefetch
nix-prefetch-bzr
nix-prefetch-cvs
nix-prefetch-docker
nix-prefetch-git
nix-prefetch-hg
nix-prefetch-scripts
nix-prefetch-svn
nix-required-mounts
nix-required-mounts.dist
nix-serve
nix-template
nix-unit
nix-update
nix-update-source
nix-update-source.dist
nix-update.dist
nix-visualize
nix-visualize.dist
nix-web
nix.dev (nixVersions.nix_2_18.dev)
nix.doc (nixVersions.nix_2_18.doc)
nix.man (nixVersions.nix_2_18.man)
nixVersions.git
nixVersions.git.dev
nixVersions.git.doc
nixVersions.git.man
nixVersions.latest
nixVersions.latest.dev
nixVersions.latest.doc
nixVersions.latest.man
nixVersions.minimum
nixVersions.minimum.dev
nixVersions.minimum.doc
nixVersions.minimum.man
nixVersions.nix_2_19
nixVersions.nix_2_19.dev
nixVersions.nix_2_19.doc
nixVersions.nix_2_19.man
nixVersions.nix_2_20
nixVersions.nix_2_20.dev
nixVersions.nix_2_20.doc
nixVersions.nix_2_20.man
nixVersions.nix_2_21
nixVersions.nix_2_21.dev
nixVersions.nix_2_21.doc
nixVersions.nix_2_21.man
nixVersions.nix_2_22
nixVersions.nix_2_22.dev
nixVersions.nix_2_22.doc
nixVersions.nix_2_22.man
nixVersions.nix_2_23
nixVersions.nix_2_23.dev
nixVersions.nix_2_23.doc
nixVersions.nix_2_23.man
nixci
nixd
nixos-anywhere
nixos-generators
nixos-option
nixos-rebuild
nixos-shell
nixpkgs-hammering
nixpkgs-manual
nixpkgs-review
nixpkgs-review.dist
nixt
nixt.dev
node2nix
npins
nuget-to-nix
nurl
nvfetcher
prefetch-yarn-deps
python311Packages.nix-kernel
python311Packages.nix-kernel.dist
python311Packages.nixpkgs
python311Packages.nixpkgs.dist
python311Packages.pythonix
python312Packages.nix-kernel
python312Packages.nix-kernel.dist
python312Packages.nixpkgs
python312Packages.nixpkgs.dist
python312Packages.pythonix
sonarr
swiftPackages.swiftpm2nix
terranix
typescript-language-server
update-nix-fetchgit
vimPluginsUpdater
wp4nix
yarn2nix

I believe the failures are pre‐existing.

I switched to an override so that users overlaying lowdown will have their customizations applied to lowdown-unsandboxed, which is probably what most people would want.

@emilazy yes, you are correct, it should be allowed but i interpreted requirement as implementation, so it made sense to me that you can't add callPackage for non by-name imports

I think the actually reasonable thing that should have been done here is to make sandbox setup failure not fatal in lowdown. Disabling it completely isn't great, and nor is the current situation, where things like Lix which iirc use lowdown at runtime and at build time had their builds broken and also cannot use the sandbox (see: https://git.lix.systems/lix-project/lix/issues/547)

@lf- Sorry, I should have sent a change to the Lix flake.nix. However, it’s easy to fix, as you can see from the diff to the Lix and Nix expressions in this PR; lowdown already has to be listed separately for build‐ and runtime due to cross‐compilation, so the solution is to simply use lowdown-unsandboxed in nativeBuildInputs and lowdown in buildInputs. If you do that, there should be no issues, given that the Nixpkgs channel has advanced fine after this PR. I don’t think patching the upstream code to silently be less secure when sandbox fails to be created is a good idea for maintainability or security.

I think the Nix flake will also probably need fixing. I don’t think I’ll have time for that today, but maybe tomorrow if nobody beats me to it.

We can fix Lix but the problem is that it will break NixOS 24.05 assuming we don't put in funny feature detection code because -unsandboxed exists only on unstable. That's the real issue with this sort of change for stuff like Lix which needs to be compatible with both branches.

Does e.g.
{
  lowdown,
  lowdown-unsandboxed ? lowdown,
}:

…

work for you?

I am about to try that, but I think this is still fundamentally busted without any override, since we quite plausibly might test lowdown-using functionality in installCheckPhase. That being said, it does seem like the offending sandbox should only be applied to the CLI so maybe it's okay? It still gives me a bad feeling that tools have the potential to arbitrarily not work in the nix sandbox if someone puts the path to the CLI in a wrapper script or whatever.
And as for the sandbox setup failing being fatal, it should be changed to print a warning IMO. The sandbox isn't fundamental to it working properly, it's not that weird for it to be unavailable (just like Linux's user namespaces!), and we have very bad CI testing of the Nix sandbox on macOS in general, so it seems like it's likely to be a liability in the future. Or if it is going to be fatal at least there needs to be an env-var to override it or so and we will have another __darwinAllowLocalNetworking equivalent thing I guess.

It only applies to the CLI, yeah. I’m not really sure what override we could provide for install checks other than the option this already introduces to disable the sandboxing. The macOS sandbox just doesn’t support nesting AFAIK, so either you have code that never invokes the sandbox, test code other than what you install, or it can’t run in the sandbox. Lots of stuff doesn’t really work well in the macOS sandbox, ultimately, and we don’t have clear ways to fix that for many of them. But at least downstream derivations can make any of those possible choices after this PR.
I’m not sure what you mean about the sandbox setup being fatal and environment variables. It’s lowdown that fails to start up, not Nix.

We could make it so that lowdown-unsandboxed still tries to initialize the sandbox and fails gracefully, to improve the situation for unsandboxed Nix builds. I just didn’t bother doing it here, as this never worsens the security properties compared to before this PR, and it needed fixing for the Darwin rework anyway, but I’d be happy to review. It’d still be necessary to use lowdown-unsandboxed in nativebuildInputs.

I’m not sure what you mean about the sandbox setup being fatal and environment variables. It’s lowdown that fails to start up, not Nix.

Yes, so lowdown should not completely fail in a way that requires all package maintainers paying attention to macOS by having to have two separate versions of it in a way that cannot be correct for any dependents-of-dependents. This PR adds extra configuration in a way that only affects macOS and breaks builds in ways that may only happen in sandboxed Nix builds. Furthermore, it might only affect a second order consumer of lowdown: perhaps there is a lowdown wrapper script in nixpkgs; there is no way to correctly write that package, except by always using the unsandboxed variant, if that package can be used by any other packages at build time.
This whole configuration mess is solved by not having sandbox setup failure be fatal, either by requiring an override environment variable to allow that condition (which then just can be set by any second-order dependents), or by issuing a warning and proceeding anyhow.
The solution of having two packages adds more work to everyone on a platform that already has packages randomly break too much due to needing macOS-only changes. This is done in order to "improve security", which would also be achieved by just trying to enable the sandbox every time and just not dying if it doesn't work. I don't see there being any realistic case where even failing silently (let alone with a warning) would be a security issue; executing lowdown from a sandbox is basically only ever going to happen in a nix build, in which case you should not be processing malicious markdown docs. I don't see any conceivable case where the macOS sandbox state and markdown input would be controlled by an attacker without them simply having code execution already.

that may only happen in sandboxed Nix builds

They happen in all builds on macOS because the sandbox is unconditionally initialized; unsandboxed builds just use a minimal profile. It’s not possible to hold wrong here unless you don’t test on macOS at all. If an executable that wraps lowdown should itself be used in downstream Nix derivations, then lowdown-unsandboxed can be used in that one. I agree that in that case, lowdown-unsandboxed still trying to initialize the sandbox and allowing failure (perhaps with a warning) would be a security improvement from the state before and after this PR, and I’d be happy to review that change if it’s not too invasive a patch.
Previously, such packages would always be using the unsandboxed version on aarch64-darwin, so using lowdown-unsandboxed there would not be a regression from the state before this PR, which I kept minimal because some change was necessary as part of the extensive follow‐up work to the Darwin platform improvements in https://github.com/NixOS/nixpkgs/pull/346043 and I thought being explicit about intent was better than the approach of extending the previous bad stripping of the sandboxing to more platforms in https://github.com/NixOS/nixpkgs/pull/346933.
I really think that upstream should be making the decisions about how lowdown sandboxes itself, though, rather than us weakening it in ways that can potentially help an exploit chain. It’s probably a marginal case, but I think a pretty strong norm against doing patches to weaken upstream sandboxing is a good thing. If upstream is okay making it fail silently, then I’m okay with it too, but if not then I don’t think we should be making that decision.

The solution of having two packages adds more work to everyone on a platform that already has packages randomly break too much due to needing macOS-only changes.

FWIW, all this work is directly aimed towards making far more packages build out‐of‐the‐box on macOS and significantly reducing the maintenance burden of macOS support both in Nixpkgs and for downstream derivations, which it is already starting to pay dividends for even before making it out of staging. But I admit that it is sometimes hard to stay motivated in contributing to that work given the hostility.

Apologies for my frustration. I realize that I am currently a bit emotionally destabilized and burned out and I was very unreasonable in this thread. I will do my best to fix the conditions that led to this (chiefly trying to push back more on being the backstop maintainer) and do better in the future.
Thank you for your work in making it more maintainable, and I hope after we get through the growing pains, it will be easier to deal with.
I will file an issue upstream to get their input on possibly changing the sandbox setup design; it looks like a possible oversight.

Thank you; I sincerely do appreciate that. I know upstream backwards‐incompatibilities are frustrating, whether motivated by security or not, and I had made a mental note to check if I needed to mirror the changes in the Lix and Nix flakes that I neglected to follow up on. I also know that macOS support has been a persistent pain point for the ecosystem, and that both Apple decisions and Nixpkgs neglect have made it difficult to improve for a long time. I’m hoping that 24.11 and 25.05 will be vast improvements in the state of support, but I understand that a lot of people already feel fed up with the platform and that it’ll be on us to prove its newfound health.
FWIW, I agree that it seems relatively unlikely that a fail‐open approach to sandboxing could be a critical security failure, but when an upstream has explicitly written code to sandbox itself and fail if it can’t be initialized, I’m very hesitant to go against that more than is absolutely necessary. It’s hard to predict what states people will be able to direct weird machines into, and I don’t want a Nixpkgs decision to one day end up as one of the nodes in a chain like this. How exactly to handle sandboxing in programs that process untrusted user input isn’t our area of expertise, so I feel it is best to make any divergence upstream as localized as possible when we absolutely must do it because of technical limitations.
Sadly, in this case, that interacts with the limitations of Apple’s APIs in such a way as to force consumers to make explicit decisions about the trade‐off. I think in the absence of the upstream decision it’s better for us to expose the trade‐off so downstreams can decide what’s best for them, but it’s certainly an awkward situation.


Use core icons for some equipment

What are the description changes?

Just some minor formatting. Emphasized item names, added effect link to Grasp of Droskar, and cleaned up a healing link.


Fully Asyncio Support

I find #246 this issue so I wrote an asyncio support for thriftpy, and it can pass all the original test cases. Now you can use thriftpy like this:
######
# This is a thrift client
######
import thriftpy
import asyncio
from thriftpy.rpc import make_aio_client

echo_thrift = thriftpy.load("echo.thrift", module_name="echo_thrift")

async def request():
    client = await make_aio_client(
        echo_thrift.EchoService, '<IP_ADDRESS>', 6000)
    print(await client.echo('hello, world'))
    client.close()

######
# This is a thrift server
######
import asyncio
import thriftpy

from thriftpy.rpc import make_aio_server

echo_thrift = thriftpy.load("echo.thrift", module_name="echo_thrift")

class Dispatcher(object):
    async def echo(self, param):
        print(param)
        await asyncio.sleep(0.1)
        return param

def main():
    server = make_aio_server(
        echo_thrift.EchoService, Dispatcher(), '<IP_ADDRESS>', 6000)
    server.serve()

if __name__ == '__main__':
    main()

Yeah I think it can be merged smoothly, I just resolved the last little conflict file.

@wooparadog #299 Only support single transport, so it can be a smaller realization. But this pull request support both framed and buffered transport.

@hit9 Could you merge this PR?

Sorry but I am removed from this organization.

Whats the state of this PR???


createMonitor

Adds a high level watcher function with granular add, change, and remove events on files. Fixes #4

This should be ready on Thursday, and will give more of a chokidar type experience.


Separate sample tests into to a single folder

What

Separate tests into to a single folder
Extract reusable for all samples to do their own automation tests
Get folder structure ready for component+binding tests
This PR is one of 3 small PRs to create tests for component+binding:
Separate tests into to a single folder (This)
Create a mini sample for component+binding
Add tests for component+binding
Why

How Tested

Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

Do you plan to also move the e2e tests that are currently sitting in @internal/react-composites and their apps? We really should...

Yea, I was thinking of it, but it requires more works, I believe we can open a work item and set it as post-GA


Allow users to exclude some values from id and sanitized tag outputs

Overview

include terraform-docs
awscc user_agent
content changes described below for tag sanitization
reorganize tests into 1 file per example
write tests for optional attribute passing and reordering id

Previously tags were being populated for account, name, namespace, and env even if those variables weren't populated. This change allows you optionally include some or all parameters. Excluding all merely allows this module to sanitize tags for use with either aws & awscc. Including some creates an id that you can use as a naming prefix for resources.
By default the id is ordered as:
namespace-account-env-name
This order can be changed by updating var.id_order.
If you omit some values without changing var.id_order the same order will be preserved. For example, if account is not provided it will yield namespace-env-name.
tests:
--- PASS: TestFormattedTags (79.92s)
PASS
ok      github.com/aws-ia/terraform-aws-terraform/m/v2  80.091s

Open questions:

Previously the null_resource was used. From what I could tell, there was no specific reason to use this as the output value for tags, etc. I updated the code so we CAN use null_resouce (see below). Would like input as to if its ok to remove prior to merge
output attributes has been removed. Unsure of its usage since they were not appended to the tag output. Attributes can still be passed as a variable to be included in id. Willing to work this back in with some extra context on its purpose.

null_resource update if we actually need it
resource "null_resource" "default" {
  triggers = local.non_empty_vars_map

  lifecycle {
    create_before_destroy = true
  }
}

I converted this to draft, pending unit tests.

new unit tests included and i reorganized pre-existing tests:
PASS
ok      github.com/aws-ia/terraform-aws-terraform/m/v2  95.082s


Block access to domains

I have a Huawei AX 3 router and I often find myself blocking access to specific domains for specific devices or network-wide (e.g. youtube.com or bamgrid.com for Disney+ etc.) in order to control my son's TV watching. Instead of going to the router > Security Settings > Parental Control and manually adding/removing domains there, it would be a great feature to have it in this custom component. Adding domains to or removing them from a blacklist could be then automated easily.

Hi!
You can create the necessary filters in the router's Web UI, and turn them on or off from Home Assistant using these switches.
https://github.com/vmakeev/huawei_mesh_router/blob/master/docs/controls.md#website-filtering
Or do you fundamentally need to create/remove filters in the form of a HA service? This may not be very convenient, since it will require you to specify filter ids, since several filters can correspond to one URL

Hi!
If I understood you correctly, you are saying if I have under Security Settings > Parental Control > Website Filtering entries defined for which device which domain is to be blocked, I can create a switch in HA, which would turn on/off the corresponding switch in the router. If that's the case, I'm struggling with creating a switch. do you have an example of how a switch template would look like e.g. for a device named XYTV and the domain example.com?

Hi!
Sorry clicked the wrong button.
If I understood you correctly, you are saying if I have under Security Settings > Parental Control > Website Filtering entries defined for which device which domain is to be blocked, I can create a switch in HA, which would turn on/off the corresponding switch in the router. If that's the case, I'm struggling with creating a switch. do you have an example of how a switch template would look like e.g. for a device named XYTV and the domain example.com?

Just follow the documentation. You need to enable Website Filtering Switches in the advanced settings and the integration itself will create the necessary switches.
If something doesn't work out, let me know, we'll try to figure it out together

Thanks, missed the advanced settings part. This is what I was looking for.


Pressing the Modules button in the visualiser breaks the visualiser

Pressing the modules button in the visualiser causes the screen to go blank and all the buttons to not function anymore. Have to start the visualiser again to get it back to it's previous state.
Before:

After:

Same here.
Togelling from classes to modules view break the visualizer.
the only diff is that I can actually see the modules graph, tho I get stuck there every time ..


[RU] Translation update

We need a Russian speaker to review these changes. Do you know any speakers who could review?

I can review 😄 maybe @gbezyuk can help

Looks good to me ;)

Thanks @Alex-Sokolov  and @gbezyuk 😀


Share cookies

Someone have a lot of fb working cookies and wants to share litle of them <3 :D

why you need cookies if mass bots dont work LOL

Lol they actually work :p

help plz help to make fb mass work skype:David Ali plz :3

if someone want cookies, i will sell a lot of working ones. mail<EMAIL_ADDRESS>

go skype agariobotdev

@problemsofworld  they do work my friend, just need "nobanned" accounts

Anyone gives cookies free? skype: sejo.dedic4

Someome gives cookies free?  Or someone who knows how to play well to make clan? Skype: rafail.t

Skype : BrunoOlyver I have 6 or 7accounts more spawns with 20-30 mass help get more levels in this accounts  i am from Brazil (bad english)

Burno i help you reach levels if you share cookies with me ?

Yes :D, more can get the account banned

2 people is not that much, its like two people playing on one acc from diferent ip's

I have shared with rafa

sejo i have 30 tell your skype ill add you

your skype not working

@kurama129 Skype Name?

i got 90 tokens+ working go add skype : iTwiGXDev for fb bots help

Where did u get the acc from @Wartoz


Implement RPC authentication

I would like to transfer the following issue to the rusty-kaspa repo:

Currently, many nodes have RPC ports potentially open to the world
Some manner of authentication should be implemented to mitigate it
Suggested solution: gRPC supports authentication out-of-the-box: https://grpc.io/docs/guides/auth/

Source: https://github.com/kaspanet/kaspad/issues/1893
Only the auth method should probably ideally support wRPC, gRPC and all potential future protocols in a generic manner.

As per the original issue; it is preferable if the auth of a connection can be handled on a per call / notfification basis.

It should be handled by proxies, reference sofwares should be simple as much as possible i think

Starting to figure this out now


65 Medical text understanding PR

This PR fixes [issue link].
Description of changes
Describe what are the changes, and how they solve the problem.
Add example for medical text understanding which uses scispacy processor

Open new PR


Add some transitions/animations!

Currently, our site is a bit boring and it does not have any animations. Why don't we add one?

I'll be interested in adding some GSAP animations once a significant amount of PR has been merged. Anybody else is interested?

I've added branch issue-#25-animations. Feel free to clone the branch and jump in!

Lets team up! I know little about animations so look forward to learning :)

Great! Let's team up!


Vertical bounds a bit weird

Depending on aspect ratio, vertival scaling can be too high or low, simply need to just add some adjustments in our game aspect script

Now going to finish this once and for all, by dynamically changing our camera's box collider

Had to remove Player increasing size on level up to accomodate this, since the camera is a child of the layer :'(

Resoultion support is awesome :dancer:
via e49b4b9d4a0577031b43d6d39397a7c070f646b9


Maxwell 2D Initial mesh Settings

Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

Description of the bug
While try to enhance initial mesh settings in a 2D electrostatic, cannot:
1 - change the slider value to a higher value through the command:
M2D.mesh.assign_initial_mesh_from_slider(level=10)
the script runs without performing the change
2- if I need to switch to manual settings, I can set manual setting, but I do not find the property to access surface deviation values. I tried to reproduce what recorded in Iron Python scripts but with no success:
mesh_ims = M2D.mesh.initial_mesh_settings
mesh_ims['CurvedSurfaceApproxChoice'] = 'ManualSettings' # until here ok
#mesh_ims['SurfDevChoice'] = 2 # this appears in the IronPython, I tried with and without
mesh_ims['SurfDev'] = '0.01mm'
M2D.mesh.initial_mesh_settings.update() # manual setting activated, but value stays unchecked and greyed out
Note: in 2023R1 classic mesher for 2D was disabled, so it may be that the the method is not updated to the new window where some options are no longer available
Steps To Reproduce
see description above
Which Operating System are you using?
Windows
Which Python version are you using?
3.8
Installed packages
--

Hi @tizianrot ,
There are actually 9 available values for the initial mesh settings.

Available level values are from 1 to 9.

Hi @gmalinve,
thank this is helpful, how about the manual settings when I want to define i.e. a specific  surface deviation value?
Thanks and warm regards

Hi @tizianrot,
To assign the surface deviation you should use assign_surface_mesh_manual() method where you can specify as input the surf_dev input. You can specify float number with units here.
Please do let me know if that works for you.
Giulia

Hallo @gmalinve , the slider function works fine.
The other function works also fine with object assignment, actually I meant in the initial settings where it is applied to the whole model.
Thank you


CommandBox: update handleCommandEntered() for empty strings

Fixes #635.
Update handleCommandEntered() to return once an empty string is encountered.

Thanks for the PR @bchenghi Let's wait for a while to see if anyone can offer a review.

Thank you Prof Damith and Zhi Yuan for the comments. I have made the changes and updated the commit messages.

Hi, a little reminder from me. You should squash the two commit into one.

Thank you Wang Chao, I have squashed the two commits.

Thanks for the fix @bchenghi
Thanks for taking this PR through @Zhiyuan-Amos


feat(appmesh) : implementing mutual TLS  feature

Note:

this is for internal-review purpose only. I will submit the PR to main repo once I receive green from the team.
This review DOES NOT include changes on README file yet. README file needs to be updated to include mTLS implementation example.

This is the last part of the series to implement mTLS feature and closes #12733.
For the breakdown on series, please refer to
this comment.
Collaborators
@alexbrjo and @dfezzie. Thank you!
REV

Adding SDS certificate source to TlsCertificate and TlsValidationTrust.
Adding subjectAlternativeNames property to TlsValidation.
Adding certificate property to TlsClientPolicy
Adding validation property to TlsListener

Design Note:

Client certificates in a TLS Client Policy and server validation in a listener TLS configuration can only be sourced from SDS or File certificate. ACM certificate is currently not supported (ref)

when ACM certificate is selected, run-time error is thrown.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

REV2:

Reducing the repetitions on TlsValidationTrust property since all of them are guaranteed to have same property.
Converting the SubjectAlternativeNames to interface to avoid using the factory method.
Addressed nits

REV3:

Updating README file to include:

mTLS example
SDS certificate option under [Adding TLS to a listener](Adding TLS to a listener
) section

NOTE:

Subject Alternative Names change is *NOT explicitly called out in the README since I am thinking it is not a major feature. However, I did include subjectAlternativeNames property inside the mTLS example.


The bot cancels the trade after being "active for a while" even though it was active for only 18 seconds

Someone sent a trade to my bot and after 18 seconds of the trade offer being open the bot  cancels it for being active for a while (if there is a way to change this to 1 minute then please tell me)

send a trade offer to your bot
then wait 18 seconds or a bit longer
and see if it cancels the offer for being active for a while
-->

Should cancel the trade if it's open for more then 1 minute and not 18 seconds
Version: 3.5.2

If you have SDA (Steam Desktop Authenticator) open while your bot is on you might want to close it fully. If I remember correctly your SDA is polling data from Steam all the time which eventually leads into the "bug" you have occurring.

Welp... I don't think that's the main issue. I don't have my SDA opened at all but this problem occurred anyway. I always run pm2 logs then I am using my computer and when I was that thing happened, it triggered me to do some check on the coding, but I think it's most likely a problem with Steam or some module related to Steam. Idk I am just guessing.
This screenshot showed that the trade got canceled just 13k ms (13 seconds) after it's being processed. It also can get to only 8k ms (8 seconds).

My SDA is never open so I have no clue what the problem is, but this happens to someone else as well so I guess it's just needs fixing

I don’t think this is a bot issue, this happened on my main / to a few friends aswell when they tried to confirm the offer on their phones.
Offers just got canceled after confirming, both received and sent.
I’m guessing it is something with steam

I don’t think this is a bot issue, this happened on my main / to a few friends aswell when they tried to confirm the offer on their phones.
Offers just got canceled after confirming, both received and sent.
I’m guessing it is something with steam

I think it has something to do with Steam returning an old response so that the steam-tradeoffer-manager module thinks that the offer is old, when it was just made.


Fix a typo in dry run output

This PR fixes a tiny typographical error when eggs publish is ran with -d/--dry-run:
- log.info("The matched file were:");
+ log.info("The matched files were:");

LGTM, thank you for notifying this!


Test failure: npm ERR! Failed at the<EMAIL_ADDRESS>test:inner script.

SignalR tests failed. There is no additional console logging so I am not sure what exactly went wrong.
[16:22:48] :	 [Step 5/6]   SignalR               |   Time Elapsed 00:00:21.25
[16:22:48] :	 [Step 5/6]   SignalR               |   npm ERR! code ELIFECYCLE
[16:22:48] :	 [Step 5/6]   SignalR               |   npm ERR! errno 1
[16:22:48] :	 [Step 5/6]   SignalR               |   npm ERR<EMAIL_ADDRESS>test:inner: `npm run build && dotnet build && npm run test:local -- "--no-color" "--configuration" "Release"`
[16:22:48] :	 [Step 5/6]   SignalR               |   npm ERR! Exit status 1
[16:22:48] :	 [Step 5/6]   SignalR               |   npm ERR!
[16:22:48] :	 [Step 5/6]   SignalR               |   npm ERR! Failed at the<EMAIL_ADDRESS>test:inner script.
[16:22:48] :	 [Step 5/6]   SignalR               |   npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[16:22:48] :	 [Step 5/6]   SignalR               |
[16:22:48] :	 [Step 5/6]   SignalR               |   npm ERR! A complete log of this run can be found in:
[16:22:48] :	 [Step 5/6]   SignalR               |   npm ERR!     C:\Users\asplab\AppData\Roaming\npm-cache\_logs\2018-08-09T23_22_48_706Z-debug.log
[16:22:48] :	 [Step 5/6]   SignalR               | C:\b\w\33bdfc1cae7b2a38\modules\SignalR\build\repo.targets(46,5): error MSB3073: The command "npm run test:inner -- --no-color --configuration Release" exited with code 1.

http://aspnetci/viewLog.html?buildId=527443&buildTypeId=Releases_22xPublic_Win2012&tab=buildResultsDiv

cc @anurse @muratg

The error message is right above it:
C:\b\w\33bdfc1cae7b2a38\.packages\internal.aspnetcore.sdk\2.2.0-preview1-20180731.1\build\GenerateAssemblyInfo.targets(25,5): error MSB4062: The "Microsoft.AspNetCore.BuildTools.Sdk_GetAssemblyFileVersion" task could not be loaded from the assembly C:\b\w\33bdfc1cae7b2a38\.packages\internal.aspnetcore.sdk\2.2.0-preview1-20180731.1\build\..\tools\netcoreapp2.1\Internal.AspNetCore.Sdk.dll. Assembly with same name is already loaded Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask. [C:\b\w\33bdfc1cae7b2a38\modules\SignalR\src\Microsoft.AspNetCore.SignalR\Microsoft.AspNetCore.SignalR.csproj]

I've seen this before but I'm not sure what causes it and I haven't been able to repro it locally, I'll try again now. @natemcmaster have you seen this before?

I see. Closing as a duplicate of https://github.com/aspnet/Universe/issues/1311 then.


Hiding tooltip for a column isn't in insight returned from iframe

Steps to reproduce:

load data
hide a column for tooltip
get insights
There is no insight information on hiding a tooltip column.

How do I specify that a column should be hidden in the tooltip in the insight?

Can you try adding a tooltipExclusions string array to an options object passed to your load command?

That works!


Access to biomarker/data, api, and sparql

Please provide Daniall, Robel, Jonathon, Pat, and Karina access to
hive-lab/biochemistry.edu/biomarker/data
hive-lab/biochemistry.edu/biomarker/api
hive-lab/biochemistry.edu/biomarker/sparql

I don't think this is something I can do. I am not familiar with these.

Would this be a task for Robel, or someone else?
Daniel Lyman, PhD
Senior Research Associate
Cancer Biomarkers Project Lead, HIVE-Lab
MS in Bioinformatics and Biochemistry Program Coordinator
Department of Biochemistry and Molecular Medicine
School of Medicine & Health Sciences
The George Washington University
Ross Hall
2300 Eye Street N.W.
Washington, DC 20037
Phone lab:<PHONE_NUMBER>
MS Program Office hours: T/W 9:00am-5:00pm
On Thu, Jun 8, 2023 at 12:09 PM Hadley King @.***>
wrote:

I don't think this is something I can do. I am not familiar with these.
—
Reply to this email directly, view it on GitHub
https://github.com/biomarker-ontology/Biomarker-Database-Curation/issues/8#issuecomment-1582943068,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4WWYURATDB4N7ND334CTQDXKH2LBANCNFSM6AAAAAAYXMVESI
.
You are receiving this because you were assigned.Message ID:
@.***
.com>

Probably. I am not even sure what the paths you supplied are referencing. Where is that? What resource is it?

I'll reassigne to Daniall and Robel

Daniall
Please work with Robel on these issues.

Sean has been able to complete these and is working on sparql


Make plugin names anchors so that individual plugins can be linked to

Show para icon when hovering over header, in the same manner as
godoc.org does.

Hi @aeijdenberg. Thanks for creating this pull request. This is a useful feature to have. We found the link difficult to click and would love if you could either make the span bigger so that icon does not disappear or make the entire header (name with the version) as a link.

@Ema93sh - changed as suggested. Not sure why the build insta-failed - I don't think it's related to the content of this PR.

This looks great! Thank you very much for the good idea and the implementation!

Hi @aeijdenberg,
Thanks again for the contribution, and sorry to bother about something we thought was done, but it seems like angular does not play nicely with this sort of anchor tag.
For example, if you go to: https://plugins.cloudfoundry.org/#log-noise you will notice that we don't scroll down on the first page load, but after the page is loaded, then the link will start to work.
We started looking into this ourselves, but don't have the cycles to look into it further. If you have the time and inclination, we would welcome another PR.
Thanks!


Enhance documentation to explain addParams and dropParams functionality

Add notes on addParams usage
Example for max_tokens in addParams
Clarify dropParams functionality
Note default_params immutability
Update links to relevant sections

👍


UofT-DSI | Python - Assignment 2

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Added additional code to analyze the efficacy of a Hypothetical Arthritis Drug
What did you learn from the changes you have made?
This was my first time using Numpy and working with datasets on Python
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
I did consider not listing out "patient 1 - data" but I thought it made it more readable for the user
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Yes, I had difficulties with part 1 and displaying the appropriate data.
How were these changes tested?
Tested using the expected outputs in the assignment and used the file in excel to ensure the mean was correct.
A reference to a related issue in your repository (if applicable)
Checklist

[x] I can confirm that my changes are working as intended

Assignment marked.


Cannot get Light entity or device to register in HA

When I create a light device, I can see the config added to the MQTT server but it is never imported to HA, The Switch device works. Any ideas on how to fix this?

A simple example (You may need to change the MQTT default configuration)
https://github.com/shaonianzhentan/node-red-contrib-ha-mqtt/blob/main/examples/light/example-1.json


kubectx rename check if old_name is a valid ctx

Without this safeguard, when user runs kubectx NEW_NAME=OLD_NAME where
NEW_NAME is an existing context but OLD_NAME isn't, we end up deleting NEW_NAME
and not doing any renames (because OLD_NAME is not found).
Fixes #136.

Looks fine for me --> local tryout throws the expected error and doesn't delete my old context :)

Looks fine for me --> local tryout throws the expected error and doesn't delete my old context :)


Can you describe the inferance process?

Can you describe the inference process?  or Can you provide a script for inference?

Hi, the inference scripts have been provided in the subfolders of the three tasks. Please refer to segmentation.md, refer.md and depth.md for details.

Thanks


First pass of documentation in mdBook

Which issue does this PR close?
Closes #339.
Rationale for this change
The documentation is currently in sphinx, which is challenging to update (requires RST, not markdown) and has bad default settings for SEO/usability.  Migrating the documentation to mdBook will make it easier to build an amazing user guide.
What changes are included in this PR?
A folder that generates a mdBook documentation site.
Are there any user-facing changes?
No, this just changed the documentation.  No code changes.

mdBook generates docs that are really nice-looking.  Excited to collaborate on the team with next steps!

Thanks @MrPowers this looks like a great start. I left some feedback.

Thanks for the review @andygrove.  Feel free to comment with any other next steps and I'll be happy to continue updating this PR.

@MrPowers two more files need ASF headers:
NOT APPROVED: docs/mdbook/README.md (./docs/mdbook/README.md): false
NOT APPROVED: docs/mdbook/book.toml (./docs/mdbook/book.toml): false

Thanks @andygrove, made those updates.


Flow type definitions are not being found

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.
Seems like the Flow type definitions are not being found because the file which is being imported is called index.cjs.js and the definition file is called index.js.flow. If I copy the index.js.flow and rename it to index.cjs.js.flow then it works.
Here is the diff that solved my problem:
diff --git a/node_modules/react-native-fast-image/dist/index.cjs.js.flow b/node_modules/react-native-fast-image/dist/index.cjs.js.flow
new file mode 100644
index 0000000..71fac3a
--- /dev/null
+++ b/node_modules/react-native-fast-image/dist/index.cjs.js.flow
@@ -0,0 +1,71 @@
+// @flow
+
+import type { ViewProps } from 'react-native/Libraries/Components/View/ViewPropTypes'
+import type { SyntheticEvent } from 'react-native/Libraries/Types/CoreEventTypes'
+
+export type OnLoadEvent = SyntheticEvent<
+    $ReadOnly<{
+        width: number,
+        height: number,
+    }>,
+>
+
+export type OnProgressEvent = SyntheticEvent<
+    $ReadOnly<{|
+        loaded: number,
+        total: number,
+    |}>,
+>
+
+export type ResizeMode = $ReadOnly<{|
+    contain: 'contain',
+    cover: 'cover',
+    stretch: 'stretch',
+    center: 'center',
+|}>
+
+export type Priority = $ReadOnly<{|
+    low: 'low',
+    normal: 'normal',
+    high: 'high',
+|}>
+
+export type CacheControl = $ReadOnly<{|
+    immutable: 'immutable',
+    web: 'web',
+    cacheOnly: 'cacheOnly',
+|}>
+
+export type ResizeModes = $Values<ResizeMode>
+export type Priorities = $Values<Priority>
+export type CacheControls = $Values<CacheControl>
+
+export type PreloadFn = (sources: Array<FastImageSource>) => void
+export type FastImageSource = {
+    uri?: string,
+    headers?: Object,
+    priority?: Priorities,
+    cache?: CacheControls,
+}
+
+export type FastImageProps = $ReadOnly<{|
+    ...ViewProps,
+    onError?: ?() => void,
+    onLoad?: ?(event: OnLoadEvent) => void,
+    onLoadEnd?: ?() => void,
+    onLoadStart?: ?() => void,
+    onProgress?: ?(event: OnProgressEvent) => void,
+
+    source: FastImageSource | number,
+
+    resizeMode?: ?ResizeModes,
+    fallback?: ?boolean,
+    testID?: ?string,
+|}>
+
+declare export default class FastImage extends React$Component<FastImageProps> {
+    static resizeMode: ResizeMode;
+    static priority: Priority;
+    static cacheControl: CacheControl;
+    static preload: PreloadFn;
+}

This issue body was partially generated by patch-package.

I did a kind of hacky solution. I will look into just shipping ESM in a future release, which would resolve this.


Bosses that have cups versions track weirdly.

This happens with Hades II as well.

Closed by #13


Update search syntacx docs with details regarding AND/OR with multiple properties

The doc : https://docs.microsoft.com/en-us/nuget/consume-packages/finding-and-choosing-packages#search-syntax
when searching multiple properties, for example: https://api-v2v3search-0.nuget.org/query?q=id:OneDas tags:HDF&skip=0&take=20&prerelease=true&semVerLevel=2.0.0
there's an AND between properties.

Also, the docs page says "NuGet package search works the same on nuget.org, from the NuGet CLI, and within the NuGet Package Manager extension in Visual Studio." which is not accurate. Try searching for json+jquery in nuget.org and VS.


FrameTimeCode should be identic to itself when applying the resulting values to create a new FrameTimeCode

Hi !
Thank you for PySceneDetect.
I ran into issues where after some serialization the resulting time frame was not the expected one.
For example:
frame_time_code = FrameTimecode(61, fps=14)
seconds = frame_time_code.get_seconds()
time_code = frame_time_code.get_timecode()

...

FrameTimecode(seconds, fps=14).get_frames() == 60 # not 61
FrameTimecode(time_code, fps=14).get_frames() == 60 # not 61

I found the corresponding code with flooring (with int instead of round) :
https://github.com/Breakthrough/PySceneDetect/blob/f6c61dda5ddb2e1bc99471c5520cebe8a9ea7f59/scenedetect/frame_timecode.py#L227-L236
https://github.com/Breakthrough/PySceneDetect/blob/f6c61dda5ddb2e1bc99471c5520cebe8a9ea7f59/scenedetect/frame_timecode.py#L307
I ran into the following code which seems to indicate this is on purpose. What is the reason?
https://github.com/Breakthrough/PySceneDetect/blob/f6c61dda5ddb2e1bc99471c5520cebe8a9ea7f59/tests/test_frame_timecode.py#L114-L116
Have a nice day !

Hey @Wirg;
Thanks for looking into this.  It looks like some of the existing test cases are failing after your change (probably just a few off-by-one errors now), so will need to see why that is before merging #269 (thanks for the PR as well).  I'm not sure if this should be taken for v0.5 or not, as this could possibly be a breaking change, but I'd be happy to consider it for v0.6.
I ended up doing a similar workaround in v0.6 for the PyAV backend, so I think your change is correct.  Truthfully it's been quite a few years since I've touched FrameTimecode, so I can't really remember the intent behind these test cases you pointed out:
https://github.com/Breakthrough/PySceneDetect/blob/f6c61dda5ddb2e1bc99471c5520cebe8a9ea7f59/tests/test_frame_timecode.py#L114-L116
I may mark this as a known issue for v0.5, but bring your change in for v0.6.  Thanks for the report!

I've accepted your suggested solution for v0.6 (c5ac42b566a4c6d2c0ce64242a0cdf3b59bfe2c9) and it will be included in the next beta release, as well as v0.6.  I'm reluctant to merge this fix into v0.5 as it may constitute a breaking change for some existing applications.
TODO before closing this issue:

[X] Add identity unit tests as @Wirg suggested in #269
[ ] Update v0.5 changelog marking this as a known issue

Thanks for the fast answer!
I think it's ok for me, I agree with your reasoning. I may try the v0.6 branch then.

This is now available in the latest release of v0.6 (v0.6-rc0), feel free to give it a try!


I got this to work on Google Chrome and the new AI police

Hi! So I got your script to work on Google Chrome, and it's updated to adapt with the stricter AI that Google Colab has implemented March of this year. The previous scripts employed on medium and hackernoon don't work anymore. Now I don't know how wise it would be to make this open source, but hey, why not? Pull request, maybe?

Unless you're using some really questionable techniques, why not make it open source? XD
Though I'm not sure if I want to maintain this project further. You can maintain your own fork of this if you wish, the license allows for it. Ofcourse if you don't want that, you can send a PR, I'll merge it eventually.

You've convinced me; I'm sure this project is far from questionable. wink I'll send you a PR soon after I make sure it works on windows

@mathemusician don't mean to bother you, but any progress? xD


Modify daemon runtime options via sysconf

This adds the ability to modify the runtime options.
I haven't tested it on debian or gentoo.

Looks good to me. 👍
Thanks!
Merged.


Create new EVA evidence table in rewrite version

On the evidence page in the rewrite, can we please create a new data table that displays the EVA evidence data?
Example GraphQL API query
KIT and Piebaldism
Data table

Data table column
Disease/phenotype
Reported disease/phenotype
Variant
ClinVar ID
Functional consequence
Clinical significance
P-value
Literature

GraphQL API field
evidences.rows[x].disease.name
evidences.rows[x].diseaseFromSource
evidences.rows[x].variantRsId
evidences.rows[x].recordId
evidences.rows[x].variantFunctionalConsequence.label
evidences.rows[x].clinicalSignificance
evidences.rows[x].resourceScore
evidences.rows[x].literature

Sample data
Piebaldism
partial albinism
rs794726672
RCV000014859
Frameshift variant
Pathogenic
1e-7
1 publication

Please note that not all rows will have an entry in literature.
Within the data table, can we please do the following?

Link the value in the "Disease/phenotype" column to the relevant profile page in the Platform
Link the value in the "Variant" column to Ensembl using the following construct - http://www.ensembl.org/Homo_sapiens/Variation/Explore?v= + evidences.rows[x].variantRsId (e.g. rs5743289)
Link the value in the "ClinVar ID" column to the ClinVar website using the following construct - https://www.ncbi.nlm.nih.gov/clinvar/ + evidences.rows[x].recordId (e.g. RCV000014862)
Link the value in the "Functional consequence" column to the Sequence Ontology website using the following construct - http://www.sequenceontology.org/browser/current_svn/term/  + evidences.rows[x].variantFunctionalConsequence.id (e.g. frameshift variant)
Round the p-value to 3 decimal places
Use the literature drawer component used in other evidence tables (e.g. Gene2Phenotype) for rows with 2+ literature entries

QC checks

SOS1 (ENSG00000115904) and Noonan syndrome (Orphanet_648)
MXI1 (ENSG00000119950) and prostate carcinoma (EFO_0001663)
HTT (ENSG00000197386) and Huntington disease (Orphanet_399)

The identifiers.org prefixes to build the links are:

SO for sequence ontology
clinvar.record for clinvar RCV
dbsnp for rsid - this goes against Ensembl suggestion above. Just including here because it's the official service

Are we also going to display the review_status or star_rating in evidence.variant2disease.clinvar_rating?

Yes we are, but the above work is with the currently available data. Once we have 20.11 data we will add the columns.

With the latest iteration of the GraphQL API, can we please update the EVA evidence data table?

[ ] Update "Allelic requirement" column as previously, the field was a string evidences.rows[x].allelicRequirement; however, it is now an array called evidences.rows[x].allelicRequirements with an "s". Within the column, if there is only one entry in evidences.rows[x].allelicRequirements, please display the string. If there are two or more entries in evidences.rows[x].allelicRequirements, please list the entries in an unordered list. ** Please note that very often, this field will be null **

[ ] Remove the "P-value" column and replace with a column called "Score" and display the evidences.rows[x].resourceScore value and by default, sort the table by this column (descending order)

[ ] Ensure that the "Variant" column can accept null values

[ ] In the "ClinVar ID" column, please display the evidences.rows[x].studyId as the recordId field has been deprecated

[ ] The field evidences.rows[x].clinicalSignificance has become an array called evidences.rows[x].clinicalSignificances - please display the elements of that array in the "Clinical significance" column

[ ] In the "Confidence" column, map the strings returned by the API to ClinVar's star ratings

Number of stars
String returned by GraphQL API

four
practice guideline

three
reviewed by expert panel

two
criteria provided, multiple submitters, no conflicts

one
criteria provided, conflicting interpretations

one
criteria provided, single submitter

none
no assertion for the individual variant

none
no assertion criteria provided

none
no assertion provided

For the stars, please use the FontAwesome star-solid icon with the Open Targets Corporate Blue #3489ca

-[ ] please show the confidence string when hovering the stars, not to loose the extra granularity that the text message provides

As discussed:

[ ] Add reported disease/phenotype as tooltip in disease column. The tooltip content would be “Reported disease or phenotype:\n{diseaseFromSource}”
[ ] Add show more rows functionality to table.
[ ] Add empty stars as they do in clinvar
[ ] Also add the tooltip on-hover for entires with no stars
[ ] Remove score column
[ ] Implement logic to load everything when entries < n (1000?) but disallow search and pagination when entries > 1000


Rspamd 1.7.0

Rspamd 1.7.0 has been released. The most significant changes are:

Better machine learning support and embedding of Lua Torch
Language detection support based on ngramms and heuristics
New rspamadm configwizard command for a simple configuration setup
New statistics model for Redis backend allowing expiration and better analytics
Improved wizards for statistics conversion and management
Added automatic corpus test and rescoring utility based on Google Summer of Code 2017 project completed by @cpragadeesh
New Elasticsearch plugin
New experimental Reputation plugin

Since Rspamd 1.7, libfann module is deprecated in honor of Lua Torch. This tool allows more powerful neural networks processing.
:warning:
Rspamd has switched from the old layout of Redis storage where tokens were stored in two large hash tables: RSBAYES_SPAM and RSBAYES_HAM to a model where each token is stored separately : RS_<token_id> and 2 buckets S for spam hits and H for ham hits.
You can convert your old Bayesian statistics in Redis to the new schema using rspamadm configwizard statistic command.
docker exec -ti mailserver rspamadm configwizard statistic
docker-compose stop mailserver; docker-compose rm mailserver; docker-compose up -d

Info : you need enough RAM to perform this conversion.
:warning:
https://rspamd.com/announce/2018/03/12/rspamd-1.7.0.html
https://rspamd.com/doc/migration.html#migration-to-rspamd-170
https://github.com/vstakhov/rspamd/releases/tag/1.7.0
This new version is now available and ready in master branch (1.1-latest tag) and in 7 days in stable branch If everything works as expected.

I got this error when converting old statistics to the new schema :
docker exec -ti mailserver rspamadm configwizard statistic

You have configured new schema for BAYES_SPAM/BAYES_HAM but your DB has old data
Do you wish to convert data to the new schema?[Y/n]:
Expire time for new tokens  [default: 100d]:
converted OK elements from symbol BAYES_SPAM
converted 42386 elements from symbol BAYES_HAM
error converting metadata for symbol BAYES_SPAM
Conversion failed
No changes found, the wizard is finished now

Someone else has the same problem ?

Testing it right now...
Just a note for people upgrading from 1.6.x:

Until you convert your DB the webui is "broken" (bad gateway).

I'll see if its everything ok, then I'll do that ipv6 test again and I let you know about the results.

The master branch has been merged into v1.1-stable branch. Rspamd 1.7 is available for everyone.
Noticeable changes in stable version :

Feature : PostgreSQL support (added by @navossoc)
Update : Debian 9.4 (Postfix 3.1.8, ClamAV 0.99.4)
Update : Rspamd 1.7 (major release)

Don't forget to run docker exec -ti mailserver rspamadm configwizard statistic in order to convert your old Bayesian statistics.

Fix : Traefik backend port is not properly defined https://github.com/containous/traefik/issues/2993#issuecomment-372658641

Use traefik.port instead of traefik.backend.port

Fix : Vacation replies are not dkim signed https://github.com/hardware/mailserver/issues/227
Fix : Alias are not sending vacation replies https://github.com/hardware/mailserver/issues/227

Some news: https://github.com/vstakhov/rspamd/releases/tag/1.7.3
As you have mentioned on the issue #230, seems that memory leak has been fixed.


Request to join organization

Hi there!
I recently joined the company IRL and would love to join the Github org as well.
Name: Adam Vernon
Email<EMAIL_ADDRESS>Thank you!

Closing as there is an internal process now for this.


Enable configuring patches directory path

Currently, the path to the "patches" directory is hard-coded in PatchFileFactory. I want to use ".composer/patches" instead, and I expect others have similar requirements, so it would be helpful to enable configuring that somewhere.

I tried my hand at implementing this using an environment variable. If that is unacceptable for some reason, the alternative appears to be adding an optional parameter to the generate command. Please let me know what you think.

Thanks for the kickoff. The command option would be better indeed, as clear entry point of the value. Could you handle it?


Release .NET Clients version 1.0.0 to NuGet

Is your feature request related to a problem? Please describe
Since NuGet account is created, we would like to release the .NET clients from opensearch-net repo. Here is the list of packages and descriptions:

OpenSearch.Client -- Strongly typed interface to OpenSearch. Fluent and classic object initializer mappings of requests and responses. Uses and exposes OpenSearch.Net.
OpenSearch.Net -- Exposes all the OpenSearch API endpoints but leaves you in control of building the request and response bodies. Comes with built in cluster failover/connection pooling support.
OpenSearch.Net.VirtualizedCluster -- Provides a way to assert client behavior through a rule engine backed VirtualClusterConnection.
OpenSearch.Client.JsonNetSerializer -- OpenSearch.Client uses an internal serializer. This package enables serialization for your documents using your own custom Json.NET serializer

The artifacts are generated by this workflow: https://github.com/opensearch-project/opensearch-net/actions/workflows/release.yml
Describe the solution you'd like
Infra's help to release the packages to NuGet, please let me know if something is required
Describe alternatives you've considered
No response
Additional context
Linking release issue https://github.com/opensearch-project/opensearch-net/issues/14

@zelinh @prudhvigodithi Please proceed with publishing the client

[Triage] @zelinh already have some progress with nuget account setup, need a way to sign and publish the package
https://docs.microsoft.com/en-us/nuget/create-packages/sign-a-package
https://docs.microsoft.com/en-us/nuget/nuget-org/publish-a-package

@prudhvigodithi , @zelinh  what are the next steps on this ? thanks

Hey @anirudha and @joshuali925 let me know if you are ok with reserved prefixed as OSC and OpenSearch, so that glob patterns OSC.* and OpenSearch.* should also work.

@prudhvigodithi That should work. Since there are two prefixes, is it still possible to see them together in one place on NuGet? maybe by going to the owner/publisher profile, or search for OpenSearch, would both show up?

Hey @joshuali925 yes
Expecting something like
https://www.nuget.org/packages/OSC
https://www.nuget.org/packages/OpenSearch
https://www.nuget.org/packages/OpenSearch.Net

Hi Team,
Please keep us updated with the NuGet package release plan. We are eagerly waiting for it.

Hey @anandbprem working closely on this issue with Microsoft(nuget.org) and awsdotnet teams to get a reserved prefixes for OpenSearch and OSC, this includes getting three Glob patterns OpenSearch.* OSC.* OSC and creating a release flow to sign the generated dll's and update the nukpg packages securely. Multiple phases :)

Hey @joshuali925, following are the dll files generated when i run dotnet build OpenSearch.sln --configuration Release, Please let me know if i'm missing anything, we should be signing all generated dll's and run dotnet pack OpenSearch.sln --configuration Release --no-build to pack them into .nukpg file.
  OpenSearch.Net -> src/OpenSearch.Net/bin/Release/net461/OpenSearch.Net.dll
  OpenSearch.Net -> src/OpenSearch.Net/bin/Release/netstandard2.1/OpenSearch.Net.dll
  OpenSearch.Net -> src/OpenSearch.Net/bin/Release/netstandard2.0/OpenSearch.Net.dll
  OpenSearch.Net.dll -> src/Osc/bin/Release/netstandard2.0/OpenSearch.Net.dll
  OpenSearch.Net.dll -> src/Osc/bin/Release/net461/OpenSearch.Net.dll
  OpenSearch.Net.dll -> src/OpenSearch.Net.VirtualizedCluster/bin/Release/net461/OpenSearch.Net.dll
  OpenSearch.Net.dll -> src/OpenSearch.Net.VirtualizedCluster/bin/Release/netstandard2.0/OpenSearch.Net.dll
  OpenSearch.Net.dll -> src/Osc.JsonNetSerializer/bin/Release/net461/OpenSearch.Net.dll
  OpenSearch.Net.dll -> src/Osc.JsonNetSerializer/bin/Release/netstandard2.0/OpenSearch.Net.dll

  OpenSearch.Net.VirtualizedCluster -> src/OpenSearch.Net.VirtualizedCluster/bin/Release/netstandard2.0/OpenSearch.Net.VirtualizedCluster.dll
  OpenSearch.Net.VirtualizedCluster -> src/OpenSearch.Net.VirtualizedCluster/bin/Release/net461/OpenSearch.Net.VirtualizedCluster.dll

  Osc -> src/Osc/bin/Release/netstandard2.0/Osc.dll
  Osc -> src/Osc/bin/Release/net461/Osc.dll
  Osc -> src/Osc.JsonNetSerializer/bin/Release/net461/Osc.dll
  Osc -> src/Osc.JsonNetSerializer/bin/Release/netstandard2.0/Osc.dll

  Osc.JsonNetSerializer -> src/Osc.JsonNetSerializer/bin/Release/netstandard2.0/Osc.JsonNetSerializer.dll
  Osc.JsonNetSerializer -> src/Osc.JsonNetSerializer/bin/Release/net461/Osc.JsonNetSerializer.dll

From the existing .nupkg files i see just these ones:
OpenSearch.Net/lib/net461/OpenSearch.Net.dll
OpenSearch.Net/lib/netstandard2.0/OpenSearch.Net.dll
OpenSearch.Net/lib/netstandard2.1/OpenSearch.Net.dll
OpenSearch.Net.VirtualizedCluster/lib/net461/OpenSearch.Net.VirtualizedCluster.dll
OpenSearch.Net.VirtualizedCluster/lib/netstandard2.0/OpenSearch.Net.VirtualizedCluster.dll
Osc/lib/net461/Osc.dll
Osc/lib/netstandard2.0/Osc.dll
Osc.JsonNetSerializer/lib/net461/Osc.JsonNetSerializer.dll
Osc.JsonNetSerializer/lib/netstandard2.0/Osc.JsonNetSerializer.dll

but I'm not sure, @MaxKsyunz could you check which ones are needed? thanks

thanks @MaxKsyunz and @joshuali925
I do see another issue OSC.JsonNetSerializer.1.0.0.nupkg packages
Response status code does not indicate success: 409 (The package ID is reserved. You can upload your package with a different package ID. Reach out to<EMAIL_ADDRESS>if you have questions.).
I'm able to test sign and upload OpenSearch.Net, OpenSearch.Net.VirtualizedCluster, OSC
https://www.nuget.org/packages/OpenSearch.Net/
https://www.nuget.org/packages/OpenSearch.Net.VirtualizedCluster/
https://www.nuget.org/packages/OSC/
But not OSC.JsonNetSerializer can you please check if anything wrong with OSC.JsonNetSerializer?
Thank you

I think I got the error
OSC.JsonNetSerializer.1.0.0.nupkg
The package ID is reserved. You can upload your package with a different package ID
can we use a different package ID?
@joshuali925 @MaxKsyunz

Update: we renamed OSC and OSC.JsonNetSerializer to OpenSearch.Client and OpenSearch.Client.JsonNetSerializer respectively to avoid conflict

Hey @joshuali925 and @MaxKsyunz published the clients to nuget.org, please test/validate the clients, if required we can still unlist them from opensearchproject profile and republish them back again.
https://www.nuget.org/profiles/opensearchproject
Thank you.

@prudhvigodithi , the URL shared does not have any packages listed.

the packages were taken down as there were some issues found during testing and validation. @prudhvigodithi could you provide an update on current status please? thanks

@prudhvigodithi all we wanted to know is if the publish will happen in next couple of days or it would take more than a month to help us plan our dev work

Hey @INeerav @anandbprem the published packages were unlisted due to reported validation tests failure, @anirudha @joshuali925 are we good to republish the packages again? if so can you please share the 1.x version branch information.
Thank you

pending release processes for a final publish. thanks @prudhvigodithi

@joshuali925  any updates?

@joshuali925 Any updates?

@prudhvigodithi, @anirudha, @joshuali925 is there any update on when the nuget packages will be re-released please?

Hey @anirudha @joshuali925 just wanted to follow up again, can you post an update when you get a chance?
Thank you

currently in progress of security review

How long does it take to get this nuget package published? We really need this nuget package published.

currently in progress of security review

@joshuali925, @prudhvigodithi, @anirudha - is there anything I can do to help this process along?

All done! last friday :) finally! planning release activites to nuGet. we should have this posted in under week now.
@PaulDMendoza @jamesdoran

I posted the current status above, but I also want to acknowledge, and apologize for failing to provide a regular status update earlier. Thank you for your patience.

Thanks @anirudha!  Can you share what the remaining steps are before we can release?

We just shipped OpenSearch 1.0.0 .NET clients to nuget repo https://www.nuget.org/profiles/opensearchproject.

Thanks everyone. Much appreciated 🥳

Closing this issue as we have release .Net client 1.0.0 to NuGet.


Rework setting default shell by using chsh.  Do not rely on SQL.

Changes
Based on the request from @chrjorgensen I have reworked the setting of the default shell to use chsh.  SQL is no longer used.  Both chsh and bash have to be installed before code will check for default shell.
Description of change here.
Checklist

[X] have tested my change
[ ] updated relevant documentation
[X] Remove any/all console.logs I added
[X] eslint is not complaining
[ ] have added myself to the contributors' list in CONTRIBUTING.md
[X] for feature PRs: PR only includes one feature enhancement.

@beckhamrryyaann Did this conversation happen in a GitHub issue? What was the issue number for that? I am a bit out of the loop!

@worksofliam see link to the conversation.  It was on my previous pull request.
https://github.com/halcyon-tech/vscode-ibmi/pull/1134#discussion_r1136585794

@beckhamrryyaann LGTM!
@worksofliam Any comments on this?

@chrjorgensen Review incoming this week.

@beckhamrryyaann I reviewed and I am super happy with this! I really appreciate your PRs!
I just need you to fix the conflict (we had a big PR merged!), then I will retest again, and we should be good to merge it.
Thanks!

@worksofliam I have fixed the conflicts.....ready for review.


Add SOAP-BPNN

Hello, thank you for the effort!
So after our quick discussion today I wanted to leave here A proposal for a modular structure of the models, which might look like this, but it is clear that there is much to be discussed and improved.
So one suggestion might be:
We have a model class,
that consists of a feature layer an interaction layer and arbitrarily many "tasks".
The feature layer, either:

computes features from systems.
reads features from systems (in case of precomputed feats)

and:

does all the necessary computations to obtain, equivariant, or invariant atom-wise features from the systems.
(thinking about learnable radial basis or alchemical compression/message passing)

The interaction layer could be a simple MLP if nonlinearities are desired, to yield hidden representations.
The task layer takes atom-wise hidden representations and does something to them. A task consists of a regression/classification and an accumulation/aggregation layer.
The regression layer takes the hidden representations and
An aggregation layer can be a wrapper to the metatensor sample-wise operations utilities, but also more if it is a multi-center thing (ie dipole moments from partial charges or something)
class Model(nn.Module):
    #init not yet defined

    def forward(self, systems):

        feats = self.feature_layer(systems)
        hidden_repr = self.interaction_layer(feats, systems)

        output_dict = {}

        for task in self.tasks:
            #tasks need systems info -> ie positions for dipole moments
            output_dict[task.name] = task(hidden_repr, systems)

        # For training each task should come with defined response property computation methods, if desired

        if self.training:
            for task in self.tasks:
                #gets property from output_dict
                output_dict[task.response.name] = task.response(output_dict,systems)

        return output_dict

The loss itself could me a module map, that then gets an output_dict and computes the losses for the individual task, predictions plus losses from the response properties.
So in the case of an MLIP, the energy-task would consist of:
energy_task

regression layer (N_atoms, N_hidden) -> (N_atoms, 1)
aggregation layer (sum_aggregation)

energy_task.response

coming from Autograd, uses the positions from systems.

But that would also make it easy to define atomistic tasks, like:
chemical_shielding_task:

regression layer (Nhidden -> 1)
aggregation layer (pass-through) (no) aggregation

chemical_shielding_task.response

none

DOS task:

regression layer (Nhidden -> Nbins)
aggregation layer (mean - aggregation)

Feel free to comment below, if you have alternative suggestions or ideas.

that consists of a feature layer an interaction layer and arbitrarily many "tasks".
The feature layer, either:
computes features from systems.
reads features from systems (in case of precomputed feats)

One of the point in the discussion on Tue & Wed was that we would not impose such a structure to the models, instead each model would be free to do whatever they want.
It's not clear to me if you are suggesting this for the BPNN architecture or in general for all models in this repo.

Regarding the tasks/response API, this is very similar to ModelOutput and ModelRunOptions in https://github.com/lab-cosmo/metatensor/pull/405, which is likely how we will export the models. But the training part of the code should still be free to do whatever it wants!

This is a suggestion for the BPNN model only.

At least for now, it would be great if we could re-use what we use at evaluation. What is the strategy for handling different outputs, atomic outputs, equivariant outputs at evaluation? Should we try to impose something like the structure @bananenpampe proposed for all models? How do models train with multiple properties?
I would have this in a future PR and try to merge this first model ASAP (or as soon as it can handle forces)

Documentation preview: https://metatensor-models--7.org.readthedocs.build/en/7/


Flow - azure-activedirectory-identitymodel-extensions-for-dotnet v5.5.0

Type: Incorrect
Summary:
Flow - azure-activedirectory-identitymodel-extensions-for-dotnet v5.5.0
Details:
Update declared license to MIT.
Files originating with, or related to, azure-activedirectory-identitymodel-extensions-for-dotnet v5.5.0, "IdentityModel extensions for .Net." See https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet.
Resolution:
This material is licensed under the MIT License (see file /azure-activedirectory-identitymodel-extensions-for-dotnet-5.5.0/LICENSE.txt)
Affected definitions:

azure-activedirectory-identitymodel-extensions-for-dotnet 5810cd81dd3d7a802f111005f42990dc8ebb0aa7

Closing this since it looks like a duplicate of #3380.


Latest update caused extensions to fail installation

Issue Type: Bug
Trying to install new extenstions. (Atlassian and GitLens) Gives Notification saying "failed to install [insert program name here]" The notification window contains a Download Manually button option.  The manual download button starts downloading a VISX, but when installing, it fails saying "One or more extensions are for Visual Studio Code. Try installing them in Visual Studio Code." There are no failure reasons in the output window, or any way to get failure details.
VS Code version: Code - Insiders 1.46.0-insider (1d268b701376470bc638100fbe17d283404ac559, 2020-05-28T08:50:53.373Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz (8 x 3492)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.92GB (17.62GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (17)

Extension
Author (truncated)
Version

prettier-vscode
esb
4.7.0

vscode-pull-request-github
Git
0.16.1

vscode-peacock
joh
3.7.2

chat
kar
0.33.0

csharp
ms-
1.21.18

python
ms-
2020.6.81425-dev

remote-wsl
ms-
0.44.2

cpptools
ms-
0.28.1

powershell
ms-
2020.4.0

vsliveshare
ms-
1.0.2236

vsliveshare-audio
ms-
0.1.85

vsliveshare-pack
ms-
0.3.4

vscodeintellicode
Vis
1.2.7

vscode-arduino
vsc
0.3.0

vscode-icons
vsc
10.1.1

markdown-all-in-one
yzh
3.0.0

json
Zai
1.0.4

(1 theme extensions excluded)

Also seeing this on today's Insiders. Console logs:
extensionsActions.ts:263 Error: Cannot read property ‘isDefault’ of undefined
   (anonymous) @ extensionsActions.ts:263

Same as #98726, but that don't have info about problems with manual install.

/duplicate
#98726


Update images for Layercash.eth

Hi! What is your PR about?

[x] Update images for your space
[ ] Add custom domain for your space
[ ] Add alias for migrate your space
[ ] Add or edit a skin
~Edit your space with GitHub?~ (deprecated) Please migrate your space to ENS https://docs.snapshot.page/spaces/migrate
~Create your space with GitHub~ (deprecated) Create your space with ENS instead https://docs.snapshot.page/spaces/create

@layercash To update your fork with the remote version of snapshot-spaces you can try these GIT commands then commit your changes again.
git remote add upstream https://github.com/snapshot-labs/snapshot-spaces.git
git fetch upstream
git checkout master
git merge upstream/master


Not Localicated inner text of elements

Have to  be added Locatication inner calendar buttons texts etc.

Can you please elaborate? Not sure I understand what your issue is.


Content are blank

Heh bro, firstly, thank you for the good work. I'm trying to use your tool but not work as expected. The first pages are okay, but the another pages behind, most are blank or not enough(missing content). I tried slowly scroll but it still not load enough content. I tried with this: https://www.studocu.com/vn/document/dai-hoc-kinh-te-quoc-dan/chuyen-de-tot-nghiep/chuyen-de-thuc-tap-tot-nghiep-dai-hoc-kinh-te-quoc-dan/34130169
Did i do something wrong. Can you help me ?
Thank you. Love from Vietnam.

HI @dat02092k1 there is still this issue:
https://github.com/danieltyukov/studocuhack/issues/3
We are wrestling with, its quite a hard issue as studocu keeps patching the loopholes, so for now the blur page issue is still unresolved, you can star the repo and monitor it for updates


Remove StyleSheet dependency

PatternFly's StyleSheet functionality is being dropped from react-styles in v4. We use this heavily in Cost Management, but there is a security issue related to using Emotion.

This code includes

verified


Snakdy recipe missing required config

Required flag "config" missing: --config ./my-pipeline.yaml
Surrounding quotes needed around tag stringArray: -t="tag1,tag2,tag3"

Fixed in v1.7.7

Additionally, config/entrypoint for the Snakdy recipes needs to be provided as an "extra arg".
For example:
BUILD_EXTRA_ARGS: "--entrypoint=$[[ inputs.entrypoint ]]"


multiple images for same product

Dear Aosokin,
Thank you for the great job here, especially the detailed descriptions how to set-up the experiments and reproduce the results.
i just want to know can we give multiple images instead of image per product.
Thank You

Hi, thanks for the kind words!
The method itself supports only one class representative, however you can
give it two images as separate classes and then merge before NMS. We
implemented test time augmentation in the form of flips/rotations this way.
Best,
Anton
On Wed, Sep 2, 2020, 13:02 pranav318<EMAIL_ADDRESS>wrote:

Dear Aosokin,
Thank you for the great job here, especially the detailed descriptions how
to set-up the experiments and reproduce the results.
i just want to know can we give multiple images instead of image per
product.
Thank You
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/aosokin/os2d/issues/6#issuecomment-685539533, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQAQW33AGIE5JHMDR6WMNLSDYJ2JANCNFSM4QSZ6PCQ
.

thanks for clarifying.


Add CLI docs

Change Type
Addition
Proposed Changes
In one of my other issues (#298), im asking for a new cli command to be implemented, which was actually done. However i have noticed that there are no docs for the cli commands (correct me if im wrong). This is very suboptimal.

That PR has not been merged yet.

This pr has been merged, and it doesnt have anything to do  with it! big fan of your yt btw


Issues with Critic Network Loss in Policy Gradient Algorithms

I implemented policy gradient with 'qpg', 'rpg', and 'neurd' losses in the 'brps' game, but all of them failed and converged to the corner of the simplex [0, 1, 0].
It seems that the critic network couldn't approximate the true value properly. I think this might be because the sample weights weren't adjusted, as the samples follow the same distribution as the policy ((\pi)). When most of the actions come from a majority group, the loss from the minor actions seems to get ignored by the network.
I couldn’t find anyone reporting similar issues, and other implementations appear to work fine. Am I overlooking something? Any suggestions would be appreciated!

Hi @Pagl1acci,
What game?
My guess is that the learning rate(s) is/are too high.

Hi @lanctot.
It's 'brps', biased RPS. As said in the paper, if neuRD loss is used, the learning trajectories should resemble replicator dynamics. So it should run around the NE.

This one is with critic_lr = 0.001 and pi_lr = 0.001

This one is with critic_lr = 0.001 and pi_lr = 0.0001
The description in my original post about convergence to a point is not entirely accurate. For the latter one, now the q_value is [-20.2396,   0.1002,  -7.2484], and the \pi is [0.00443135, 0.98928986, 0.00627879]. Here, the action 2 should have the highest q_value which is about 4.72. However, the critic network seems very hard to capture that even after more steps.
Any thoughts on what might be going wrong? Thanks in advance for your insights!

We need more information to be able to reproduce.
Which policy gradient implementation? Did you base it on the kuhn_example.py?
Also

As said in the paper, if neuRD loss is used, the learning trajectories should resemble replicator dynamics

This could refer to several papers. Are you e.g. referring to the RPG paper, NeuRD paper, R-NaD paper?
Once we have more details we'll be better suited to help.

Thank you for your patient guidance.
I tried to use neuRD from https://arxiv.org/abs/1906.00190 on the biased RPS game. In this paper, neuRD is introduced as a one-line fix from the policy gradient algorithm, which I believe is presented in this paper: https://arxiv.org/abs/1810.09026. And I think policy_gradient.py follows this framework.
I used Torch version from open_spiel/python/pytorch/policy_gradient.py, as there is no neuRD loss implemented in the tf version. What I expect to see is something similar to the plot below: the trajectories of replicator dynamics in the same game setting.

Changing the loss type won't change too much. I tried 'rpg', 'qpg', and 'neurd'. The same issue can be also observed on the critic network.
Here is the code I used:
from open_spiel.python.pytorch import policy_gradient
game_name = 'matrix_brps'
env = rl_environment.Environment(game_name)
info_state_size = env.observation_spec()["info_state"][0]
num_actions = env.action_spec()["num_actions"]
agents = [
policy_gradient.PolicyGradient(
player_id=player_id,
info_state_size=info_state_size,
num_actions=num_actions,
loss_str="neurd",
hidden_layers_sizes=[32],
batch_size=64,
entropy_cost=None,
critic_learning_rate=0.001,
pi_learning_rate=0.0001,
num_critic_before_pi=8,
optimizer_str="sgd") for player_id in [0, 1]
]
policy_history_ = []
for episode_counter in range(1000000):
time_step = env.reset()
agent_output1 = agents[0].step(time_step)
agent_output2 = agents[1].step(time_step)
time_step = env.step([agent_output1.action,agent_output2.action])
for agent in agents:
agent.step(time_step)
if episode_counter % 512 == 0:
policy_history_.append(agent_output1.probs)


Remove CIDR limit on older kernels

On kernels lacking LPM maps, we generate code to simulate an LPM map. Due to the code generation aspect, we have to enforce an upper limit on number of matches. Some users have run into this limit. I suggest to fall back to a exact match hash table and generate all allowed IPs instead.

Just brainstorming on the design:

Have a single map for each IP version where the key is the prefix including the length.
We don't really need the longest prefix match, but might still do the lookups on any given address for all prefix lengths from longest to shortest, masking the packet's address to the given length and doing the lookup.
Looking up 128 times for IPv6 is very wasteful, so we probably should inline the prefix lengths that exist on the map to the program and only look up for those lengths. This implies that for an empty map we do no lookups.
Should do the above for IPv4 as well.

@jrajahalme thanks for the suggestions, I implemented the datapath side of this on a local tree. Seems like we can support up to about 90 prefixes with current code complexity and LLVM 7 code generation. Pretty straightforward patch on that side.
Need to put together the userspace plumbing for this though:

[ ] Switch L3Policy via CIDR{4,6}_{E,IN}GRESS_MAPPINGS to use a CIDR map of type BPF_MAP_TYPE_HASH
[ ] Track the prefixes in use and currently configured and define those in the BPF generation
[ ] Figure out how to signal warning to the user if the maximum supported number of prefixes is exceeded


[AIRFLOW-3163] add operator to enable setting table description in BigQuery table

Make sure you have checked all steps below.
Jira

[x] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-3163
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.

Description
This adds a BigQuery operator to allow setting a table description

Codecov Report

Merging #4003 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4003   +/-   ##
=======================================
  Coverage   75.49%   75.49%
=======================================
  Files         199      199
  Lines       15946    15946
=======================================
  Hits        12039    12039
  Misses       3907     3907

Continue to review full report at Codecov.

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

A different operator for setting table description? I don't think it is worth it. I am ok with having a param in BQ operators to add an optional description but definitely not a separate operator.

There is not a bigquery api exposed to set the description when you want to run a query and save the results to a table - which is the main reason I wanted this.
My flow is load data into staging tables -> aggregate data using sql and save the results to new table -> set table description on new table with metadata such as timestamp when aggregate was performed, source systems etc.
The other use case I want it for is to include metadata such as latest extract date or load date in history tables. This obviously changes each time new data is added to the table so can not be set at table creation time, and again there does not seem an api exposed to set description when adding data to an existing table.
I could change the existing operators to include a description parameters, and then call the hook to set the description after it has run, but it seemed simpler and more useful to add a new operator to set the description

@antxxxx I believe that most people add their etl_timestamp as a column to the table itself. In some scenario it's even the partition field of the table.
I think the better approach is to ask Google to add support for Description & Column description in their CLI commands. Currently it's supported only manually from the UI.
https://cloud.google.com/support/docs/issue-trackers
Once google will add this feature it will be possible to modify the Airflow Operator to support it.
I don't think there should be a separated operator just for this option.

PTAL @fenglu-g @tswast

I think I agree that this isn't general enough to warrant a whole operator. It would mean an explosion of operators if we provide one for every property of every resource.
Perhaps a "patch BigQuery table metadata" operator would be more appropriate? It could accept a dictionary of properties to update on the table resource. See: https://cloud.google.com/bigquery/docs/reference/rest/v2/tables/patch

Just thinking along here. We could extend the create table definition and add the description over there: https://github.com/apache/incubator-airflow/blob/master/airflow/contrib/hooks/bigquery_hook.py#L214-L284
The create table call supports supplying a description field: https://cloud.google.com/bigquery/docs/reference/rest/v2/tables#resource
We could template this field, so we can use created at: {{ ds }}. Thoughts?

@Fokko I am not explicitly creating a table - I am either loading into a new table or sending query results to a new table. With these methods you can not set the table description (this is a limitation of bigquery api)
@tswast Having an operator to update table metadata is a good idea. I think the only things you can actually update in a patch call are description, labels and expiration. Would you expect these as 3 specific parameters to the operator, or one parameter whose value is passed to the patch call?

It's also possible to

add columns to a table and make updates to schema descriptions. https://cloud.google.com/bigquery/docs/managing-table-schemas
update the encryption key if the table was already using an encryption key. https://cloud.google.com/bigquery/docs/customer-managed-encryption#change_key

Having a separate parameter for each property seems the most consistent with other operators, but I'm not opposed to having a single "table resource" parameter.


[ODS-4358] Remove EdFi_Ods_Empty_Template database

I moved Reset-EmptyTemplateDatabase function to Ed-Fi-ODS-Implementation\Application\SolutionScripts\InitializeDevelopmentEnvironment.ps1

All review comments are fixed now . Thank you !

There was a Cloud ODS build failure after the most recent commit. I'm re-running to see if that was a fluke. Currently running:
https://intedfitools1.msdf.org/buildConfiguration/EdFiBuilds_EdFi20_OdsCi_CloudOds_CloudODSCompileUnitTestPackage4x/85184?focusLine=0

Yes, this definitely breaks the Cloud ODS build. @vimayya we will need to fork Cloud ODS build into one just for version 5.0.0 and another for version 5.1.0. Which is a strong impetus toward version controlled settings 😁 . I'm making that change now.

Please update the new (5.1.0+) build configuration to reflect the changes in the script files.

Please update the new (5.1.0+) build configuration to reflect the changes in the script files.

@stephenfuqua  - I fixed the build issue for CloudODS . Thank you for your help!

All review comments are fixed now . Thank you !


fix encoding of the error code in the STOP_SENDING frame

Found by the QUIC interop runner when running against quicly.

Codecov Report

Merging #2222 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #2222   +/-   ##
=======================================
  Coverage   86.41%   86.41%
=======================================
  Files         106      106
  Lines        7692     7692
=======================================
  Hits         6647     6647
  Misses        782      782
  Partials      263      263

Impacted Files
Coverage Δ

internal/wire/stop_sending_frame.go
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[ip6] always enable ICMP6 filtering when forwarding to Thread

After #7187, we've observed MLDv2, RS and other ICMPv6 packets from the kernel forwarded to the Thread network. This is caused by the ICMP6 type check turned off by aFromNcpHost.
The PR turns ICMP filtering to always on when forwarding to the Thread network.

Can we have a test to make sure the issue does occur again?


chore(ci): remove EOLd versions from test matrix

Summary
According to https://docs.konghq.com/gateway/latest/support-policy/#older-versions there's a handful of versions that already reached EOL.
This PR removes them from the test matrix.
Full changelog

[Implement ...]
[Fix ...]

Issues resolved
Fix #XXX
Documentation

[ ] Link to the website documentation PR

Testing

[ ] Unit tests
[ ] E2E tests
[ ] Manual testing on Universal
[ ] Manual testing on Kubernetes

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 42.72%. Comparing base (51de016) to head (0a04f23).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #131   +/-   ##
=======================================
  Coverage   42.72%   42.72%
=======================================
  Files          75       75
  Lines        8820     8820
=======================================
  Hits         3768     3768
  Misses       4588     4588
  Partials      464      464

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Embedded listviews

got them completely working!

Tests?
:laughing:

dude, that would be great.   I really need to take a beat and see about adding tests.


Paket bootstrapper nuget download strategy usage with secure nuget feed (credentials)

Currently the bootstrapper as two strategy available to download the latest paket exe github or nuget.
With the nuget one it is not possible to use a secured nuget feed (one with credentials).
Would it be possible to add this option? This is already handled properly by paket.exe.
Maybe could we also try to find the nuget.config and if present get feed configuration in there. But this indeed would create a dependency with nuget.client which is not the best idea.

//cc @vbfox
Am Fr., 15. Juni 2018 um 09:36 Uhr schrieb Max<EMAIL_ADDRESS>
Currently the bootstrapper as two strategy available to download the
latest paket exe github or nuget.
With the nuget one it is not possible to use a secured nuget feed (one
with credentials).
Would it be possible to add this option? This is already handled properly
by paket.exe.
Maybe could we also try to find the nuget.config and if present get feed
configuration in there. But this indeed would create a dependency with
nuget.client which is not the best idea.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/issues/3255, or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNLoxV2UuhqxImaJft8YDA2MsTorSks5t82P3gaJpZM4UpIpp
.


Redis template

apiVersion: db.flanksource.com/v1
kind: Redis
metadata:
  name: redis-db1
spec:
  backup:
    bucket: postgres-backups
    schedule: "0 */4 * * *"
  cpu: 4000m
  memory: 8Gi
  replicas: 3
  storage:
    size: 200Gi
  parameters: {}

@moshloop Could you please assign this for me?


use goldmark to parse markdown

seems to be industry-standard, and maybe has more features that what i'm using (don't remember what i'm using it may already be goldmark lmao but i dont think it is)
to be migrated to goldmark:

[x] paragraph blocks
[x] media blocks
[x] link blocks
[x] footnotes
[ ] language markers
[ ] abbreviations
[ ] frontmatter

probably closes #82


What exactly is Graviti data platform? - graviti.com

Hi Ananth,
I read your newsletters about launching Data Founder Story and love the idea! I think our story might be a fit.
It was originally posted on our website blog:https://www.graviti.com/article/what-exactly-is-the-graviti-data-platform
Please let me know your thought about this article.
Thanks,
Taylor

Hi, @taylorlaw2013. Thanks for sharing the article. I think it will be good to review if you can add the "why" part of the story. We want to capture why the founder started a company and hear more personal experiences and how the product works.  Let me know if you could do your experience part too!


problem to install mjml in ubuntu machine

Describe the bug
Hey
I dont manage to install mjml in my ubuntu machine.
npm install mjml does not work
To Reproduce
I input "npm install mjml" and i get this error
WARN engine<EMAIL_ADDRESS>wanted: {"node":"^8.16.0 || ^10.6.0 || >=11.0.0"} (c/home/manuel
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>MJML environment (please complete the following information):

OS: [Ubuntu 18.04]

Any ideas of whqat can be the problem? thank you !

It looks like this is your first issue! Welcome to the MJML community!
It looks like this is an issue with fsevents which I thought was a MacOS only optional dependency.
What version of node are you using? I've been having issues with fsevents on node 14
You could also look into installing without optional dependencies --no-optional. Usually fsevents is an optional dependency

If you've installed nodejs through apt then it might be an old version of node. Can you do a node --version and try to upgrade to latest node version ?

@IanEdington  and @iRyusa thanks a lot! my node version is currently v8.10.0.
A while ago I tried to install this https://github.com/MarcL/markdown-to-mailchimp but i dont know if this is related

npm install mjml --no-optional
/home/manuel
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>npm WARN enoent ENOENT: no such file or directory, open '/home/manuel/package.json'
npm WARN manuel No description
npm WARN manuel No repository field.
npm WARN manuel No README data
npm WARN manuel No license field.

hmm. You'll probably need to update your version of node. https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions

The error message quite self explain here. Just create a new folder, do a npm init, and then you can npm install mjml inside it. Note that node 8 is really old you should update your node version because MJML isn't tested anymore with node 8

Thank you so much. i did an update and now it works!

👍


Disequality Constraints not Displaying Properly in Scenario Editor

They are appearing as "* A is not" and then not listing the alternatives.

There is a similar issue when testing for non-membership in a list. if the list is empty, it doesn't know how to display it.


[SPARK-49648][DOCS] Update Configuring Ports for Network Security section with JWS

What changes were proposed in this pull request?
This PR aims to update Configuring Ports for Network Security section of Security page with new JWS feature.
Why are the changes needed?
In addition to the existing restriction, Spark 4 can take advantage of new JWS feature. This PR informs it more clearly.
https://github.com/apache/spark/blob/08a26bb56cfb48f27c68a79be1e15bc4c9e466e0/docs/security.md?plain=1#L811-L814
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual review.

Was this patch authored or co-authored using generative AI tooling?
No.

Could you review this PR, @viirya ?

Thank you, @viirya !

Looks good to me.


Set minimum ovirt-engine REST API to version 4.2

Resolves: #1009 (initial check)
Additional work to refactor sagas can be done in future.

Changed the limit to 4.2 as per discussion with @michalskrivanek on #1009

@bond95 , @sgratch - Any issues with limiting master to >= 4.2 ovirt?