wine64Packages.unstable: 8.14 -> 8.17

Description of changes
https://www.winehq.org/announce/8.17
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
23.11 Release Notes (or backporting 23.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.

Duplicate of #258171.

Closing as a duplicate.


feat: Add max session duration for IAM role

Description
Add ability to specify maximum session duration for the created role.
Motivation and Context
We're using this module to create all our services. In development, the developers assume the roles of the services to mimic the permissions they have. By default the sessions can have a maximum duration of an hour (3600 seconds) and that means that developers need to re-assume multiple times per day.
Breaking Changes
There should be no changes as the default remains the same.
How Has This Been Tested?

[x] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects
[x] I have executed pre-commit run -a on my pull request

Any hints on getting the checks green?

Still valid and waiting for review

@antonbabenko any chance of getting a review on this?

Still relevant

@antonbabenko any chance on getting this merged?

Please fix the CI by pinning the version of the VPC module to version ~> 3.0

Please fix the CI by pinning the version of the VPC module to version ~> 3.0

Done!

This PR is included in version 4.14.0 :tada:


Snake workspace 10/31

Might hold off on merging this and use it to work on the code a bit more

DO NOT make the merge with the latest commit. It comes with HELLA BUGS!!!! Bugfix first before merging to main.


Peering Request

Full Name
Alpha Networks Solution
ASN
132227
PeeringDB Integration

[X] My PeeringDB Entries are current
[X] Peer at ALL EXCHANGES (and skip the Peer Address(es) field below)

Peer Address(es)
No response
Multihop

[ ] Multihop Peering Request

Code of Conduct (TODO)

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

Hi,
Do you have a peeringdb entry? I can't seem to find it.

So sorry , it is as132337
https://www.peeringdb.com/net/24664
Get Outlook for iOShttps://aka.ms/o0ukef

From: Hans Kuhn @.>
Sent: Saturday, April 22, 2023 2:08:15 AM
To: routeviews/issues @.>
Cc: airsky98 @.>; Author @.>
Subject: Re: [routeviews/issues] Peering Request (Issue #76)
Hi,
Do you have a peeringdbhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.peeringdb.com%2Fsearch%3Fq%3D132227&data=05|01||a547d4becb004b2cca4808db42936169|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638176972985913379|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=IhyqxQVivP8B6MhlfODVuc3yQ%2BOMnUX3Jc2f2WZyeV0%3D&reserved=0 entry? I can't seem to find it.
—
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frouteviews%2Fissues%2Fissues%2F76%23issuecomment-1518173823&data=05|01||a547d4becb004b2cca4808db42936169|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638176972986069608|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=yCqpn0F94%2BVvKbiKu2tmffQLssYgfFTPNmuRjEAqSmg%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPPZMUXBUNIXRP4MI3LOTWDXCLEI7ANCNFSM6AAAAAAWWFE6XY&data=05|01||a547d4becb004b2cca4808db42936169|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638176972986069608|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=dsWa0YVyUzPjup3AqpLREIdwUJhTVawz0d8l3iHEljY%3D&reserved=0.
You are receiving this because you authored the thread.Message ID: @.***>


can not support https??

can not support https??

For what part of Ringo is this issue? Please specify.

sorry~ i just mean how do i use "ringo/httpclient" to send request with "HTTPS"

Works for me as expected:
https://gist.github.com/botic/437dfb79c5dcab88221c
Can you provide a short gist of your code which fails? Ringo has TLS/SSL support for the includes Jetty server (you have to config the server in the jetty.xml config) and in the HTTP client.

hi, i send a request "https://xxx.com" by ringo/httpclient and get a tip about cert
require('ringo/httpclient').request(url, option)
can i set cert in option?

does the website in question use a self-signed certificate? if yes it gets a bit more complex, as you need to create a java keystore with the certificate, otherwise java.net.URL used under the hood of ringo's httpclient won't accept it. as an example have a look at the http client used by rp, the ringo package manager client.

ok, i'll try it


Schedule Related

Is there any schedule about cross platform design especially for macbook? Or is there any schedule to support "Avalonia" project?

Hi,
Greetings from Syncfusion.
Currently, we don’t have any plans to integrate Syncfusion controls (Syncfusion Xamarin.Forms Essential UI Kit implemented involves the usage of Syncfusion controls) in Avalonia platform.
Please let us know if you need any other assistance.
Regards,
Yuvaraj.

Hi,
Greetings from Syncfusion.
Currently, we don’t have any plans to integrate Syncfusion controls (Syncfusion Xamarin.Forms Essential UI Kit implemented involves the usage of Syncfusion controls) in Avalonia platform.
Please let us know if you need any other assistance.
Regards,
Yuvaraj.

ok, thanks


[Feature Request] add Telegram bot support

Telegram support long polling and webhook, please consider add them

@tasi788 Thank you for your feature request.
But now, I don't need to support Telegram platform.
If you hope this feature strongly, please implement "telegram" package to https://github.com/ShotaKitazawa/minecraft-bot/tree/master/pkg/botplug so that fulfill this interfaces
and, New & Run in main as below.
https://github.com/ShotaKitazawa/minecraft-bot/blob/cf328f7c2bd125761a4a16e7a0f92ae42e8256a3/cmd/minecraft-bot/main.go#L158-L166


Some Code problem in the Unity 2018.3.0b1

Hi,
thanks for this great package, after I updated to the latest beta version of unity. these errors have emerged.
I don't know if you can take a look at them
thanks

It seems that the internal API of TMP has changed.
I try to get it fixed soon.
Regards.

This issue got fixed in 0d9629057d8d254885176172295cba4d273c5460 commit.
Check out latest release.
Cheers.


Fail to execute ninja on 32 bit system

I installed vcpkg today on a Windows 7 32bit system and tried to install gtkmm.
It failed to build libepoxy that is built with meson/ninja as it couldn't execute the ninja executable (sorry errors lost in scrollback on another machine)
A quick search brought up this issue https://github.com/ninja-build/ninja/issues/1339
That suggests the ninja binary that is downloaded by vcpkg is 64bit and to build your own if you need 32bit.
So I then:

installed downloaded ninja source
installed the official python distribution (and added it to PATH)
launched a Developer Command Prompt and navigated to the ninja source directory
built ninja with $ .\configure.py --bootstrap
Moved the resulting executable into the vcpkg root directory

It was then able to complete the build successfully.
I hope integrating a fix for this process into the vcpkg build system is somewhat trivial, as otherwise vcpkg seems like a great tool so far.

IMHO, because vcpkg is a developer tool, a limitation for 32-bit systems is reasonable.
Even when build on vcpkg tool set, resulted binary can run on 32-bit systems.
It is necessary to document it and warn users to use 64-bit systems or solve it with your procedure.

its a pity we that have a 32bit machine can't even get to try it

Official ninja.exe is 64-bit only.
On Windows, vcpkg no longer downloads ninja. To use ninja, use the binary from Visual Studio, or download your own copy.

I agree with linquize, please try above suggestions.


Android - ./gradlew bundleRelease not including ic_launcher_round from settings

On latest major version of react-native, ./gradlew bundleRelease followed by react-native run-android --variant=release results in an .apk file with default Android icon for ic_launcher_round (newer version of Android on installed device)
Can confirm that icons are included correctly:

And referenced in AndroidManifest.xml:
<application
    android:roundIcon="@mipmap/ic_launcher_round"
    android:icon="@mipmap/ic_launcher"
>
</application>

Running in debug mode via react-native run-android results in the correct icon being displayed on device after installation, but bundling/installing in release mode shows default android icon.
React Native version:
System:
    OS: macOS 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
    Memory: 1.38 GB / 16.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 8.3.0 - ~/.nvm/versions/node/v8.3.0/bin/node
    Yarn: 1.3.2 - ~/.nvm/versions/node/v8.3.0/bin/yarn
    npm: 5.3.0 - ~/.nvm/versions/node/v8.3.0/bin/npm
    Watchman: 4.7.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
    Android SDK:
      API Levels: 23, 24, 25, 26, 27, 28, 29
      Build Tools: 23.0.1, 26.0.1, 26.0.2, 27.0.1, 27.0.3, 28.0.3, 29.0.2
      System Images: android-28 | Intel x86 Atom_64
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>91312
    Xcode: 10.3/10G8 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.8.6 => 16.8.6
    react-native: 0.60.5 => 0.60.5

Steps To Reproduce

react-native init ...
Add icons (ic_launcher.png and ic_launcher_round.png) to src\main\res\mipmap-{size}dpi
Clean build via cd android && ./gradlew clean
Bundle Android .aab in release mode via ./gradlew bundleRelease
Install .apk on device via cd .. && react-native run-android --variant=release

Intended Outcome
App is installed on device and custom icon is displayed.
Actual Outcome
App is installed on device, but default android icon is displayed.
Additional information can be found on open question on StackOverflow:
https://stackoverflow.com/questions/57775250/react-native-0-60-ic-launcher-round-missing-for-release-bundle-build

I am having a similar problem, but the bundling is not including the index.android.bundle, which is sort of a huge problem... I can only include if I first run assembleRelease


Add builtin nodes discovery

Use pkg/discovery to provide nodes discovery between daemon instances.
The functionality is driven by two different command-line flags:
--discovery-backend and --discovery-address. It can be used in two
ways by interested components:

Externally by calling the /info API and examining the discovery
backend. The pkg/discovery package can then be used to hit the same
endpoint and watch for appearing or disappearing nodes. That is the
method that will for example be used by Swarm.
Internally by using the Daemon.discoveryWatcher instance. That is
the method that will for example be used by libnetwork.

Ping @abronan @mavenugo @vieux.

@icecrime is there a design doc that describes how this works? In particular, what is relationship with swarm?  I wasn't aware that we were headed towards a single daemon knowing about other daemons.

@duglin Unfortunately, I don't have a design doc: let me try to summarize in a few sentences.
Both Swarm and mutihost networking require nodes discovery. On the Swarm side, this is nicely done with a well delimited discovery package. The idea here is to take in this package at the Engine level, thus providing a single nodes discovery mechanism to rely on:

Swarm can query the Engine on the /info endpoint and learn about the discovery backend in use. By instantiating a discovery itself, it can then watch for nodes membership changes.
Libnetwork can use the daemon.discoveryWatcher field and watch for nodes membership changes.

This is an quick and easy way to provide such facility in the Engine. In the future, we could imagine exposing nodes membership changes as part of the /events API, or provide a new endpoint to get the list of known neighbor nodes.

This is broken because ./hack/vendor.sh magic is removing the stretchr/testify dependency. Go figure. (ping @jfrazelle)

I know how to fix PR will come when I get home
On Thursday, September 10, 2015, Arnaud Porterie<EMAIL_ADDRESS>wrote:

This is broken because ./hack/vendor.sh magic is removing the
stretchr/testify dependency. Go figure. (ping @jfrazelle
https://github.com/jfrazelle)
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16229#issuecomment-139425055.

Is pkg/discovery copy of some package or what? Why it uses testify at first place?

@LK4D4 this package is in swarm, we use testify in swarm.
As the ownership of this pkg is going to shift toward the engine, I'm fine with rewriting the test to look like the other docker/docker/pkg
As soon as it's moved, we are going to remove it from swarm and vendor this one.

Maybe we should look to releasing some cool libs under docker organization. Because as I see pkg is still unnoticed by community. Same for distribution/context btw.

+1 for under a separate repo.

@LK4D4 +1 to a spot for generic packages

Agree we need a better place for generic packages (I think @duglin had ideas about that).
I took the Swarm discovery package as it is with a few interface changes: the file, node, and token strategies are actually not used by the Engine. Do we have to fix as part of this PR?

PR is update and rebased to fix the broken tests (thanks @jfrazelle)!

As part of the concern on keeping this under pkg, we can still incubate this here and move this in a reasonable time frame under its own repository. We did this for swarm and libkv and it worked pretty well. This lets the time to migrate the tests and see how it works for both swarm and libnetwork.

+1 @abronan
Tests are still broken, probably related to vendor pruning (reping @jfrazelle, sorry).

+1 @abronan.

Rebased for latest libkv: this is ready for review.

But merge my PR first ;)
On Wednesday, September 16, 2015, Arnaud Porterie<EMAIL_ADDRESS>wrote:

Rebased for latest libkv: this is ready for review.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/16229#issuecomment-140909632.

@icecrime @abronan since the discovery supports kv backends, I think it is reasonable to specify the  supported versions of the backend kv. For example, discovery doesnt work with Consul 0.4x because of lack of session management. Minimum supported version is 0.5 I believe.

@icecrime This might be worth adding in the docs:
Minimum version for Consul is 0.5.0 because of the Session TTL mechanism which also includes the Delete behavior (which mimics zookeeper's Ephemeral nodes).
Minimum version for etcd is 2.0+ because libkv uses the 2.0.0 branch of  the go-etcd client (but this might change in the future regarding the evolution of the new client and the APIv3 support).
Minimum version for zookeeper is 2.4.5 although this might work with earlier versions but haven't tried myself.

@icecrime I would put it as a pretty hard requirement that the datastore configuration must be able to be changed after the daemon starts in a distro agnostic way.  I am just seeing this PR for the first time today, so I need to dig into the technical details.  I'm not sure how this will work but here is my use case.
Docker Daemon flags are configured in a distro specific way.  Ubuntu 14.04 v 15.10, RHEL, CoreOS, Arch, etc.  For a system like Rancher we don't force users into setting up their server in a specific way, so how docker gets installed is up to them.  Once they register the host with Rancher we would like to then join it to a cluster (--discovery-backend/--discovery-address).  The problem is that requires setting some distro specific config file and then some distro specific docker daemon restart.
We would like to be able to reconfigure the daemon and restart.  I think the easiest approach would be to allow somebody to POST to /info.  The delta between current config and POST config gets saved to a file /var/lib/docker/daemon-config.json or something like that.  The daemon then commits suicide (gracefully...) assuming that the daemon is running under a supervisor (upstart, systemd, etc).  Then on start daemon configs are read from the CLI and then also the daemon-config.json.

Had a discussion w/ @mavenugo on IRC for a different approach.  What I had suggested before was a totally generic daemon options approach, but we could just narrow this down to just the discovery backend changing.  So if the user has not configured the --discovery-backend/--discovery-address as a daemon option on the CLI we can then allow the user to POST to /info once to set it.  If the daemon was configured from the CLI that post should fail.  After the backend has been configured once it can't be changed from the API.
Once you change it throw the API docker should persist that change to disk and read it on the next startup.  If the CLI has a different configuration, CLI wins over persisted configuration.

@ibuildthecloud thanks for the summary. If we decide to do this, then narrowing down the scope to a specific case like this will help. I would also include --kv-store to the mix and will not use info endpoint for POST.

@mavenugo I still haven't dug into the technical details yet (to much talking about useless things and watching cats videos on youtube), so I don't know the differences between kv-store and discovery options.  But my use case is I need to configure clustered networking after the daemon started.

@ibuildthecloud sure. I dont think we should block this PR in order to support the enhancement request that you (and others made). In that light, this PR is good to go in my view.

so I don't know the differences between kv-store and discovery options. But my use case is I need to configure clustered networking after the daemon started.

Clustered multi-host networking needs the --kv-store (for states) & --discovery-address (to discover neighbors). --discovery-backend by default uses --kv-store option, but users can change it if they see a need. So, if you are pushing a PR, then please take care of these 3 options as configurable.

I'm very against the idea of making the damon self-restarting aware.
@ibuildthecloud you can use DOCKER_OPTS to set general options for the daemon. It looks like you want to impose hard requirements in docker because rancher users use different distros with different init systems. I'm sorry, but that's not docker's problem.

@calavera That's an odd response.  Your users use different init systems too?  Mind you DOCKER_OPTS is not read by Docker daemon but the distro specific init system.
Any ways, I don't care about the generic approach I proposed, that is fine if you don't want Docker to be self restarting.  I only care that I can configure the discovery and networking backends in a distro agnostic way.  I think this is a fair ask.  What I've loved about Docker thus far is that I don't have to care about the distro, so It would be nice to also not care about the distro in this regard too.  I will put in a PR and we can discuss there.

@ibuildthecloud @calavera shall we take this discussion to another proposal / issue ?
Multi-host networking depends on this PR & I like to unblock this PR to make progress.
@icecrime libnetwork integration with this PR is done and it works as expected.
Since this is mostly a package move from swarm discovery to docker and is being used by swarm for some time, I would request to merge this soon.
LGTM

@mavenugo agreed.  FWIW LGTM :simle:

@icecrime  @mavenugo I created an issue to discuss my proposal https://github.com/docker/docker/issues/16416, please comment.  If we can agree I'll quickly program it.

LGTM!

@icecrime couple of minor points identified while integrating with libnetwork.
We can resolve these in a subsequent PR while integrating with libnetwork (https://github.com/mavenugo/docker/commit/6a9432b3a1e1bd6c13121dabc6334d5a492d0057)

initialize discovery before initializing networking
fix --kv-store to use proper URL format with ://

this PR still LGTM.

Can we hold on merge a little bit? I'd like to review this as well

First pass design review:
This works exactly in the same way as in Swarm but, since the requirements are different, I'd like to raise a few points.
Background: Discovery was originally designed for Swarm to support different kind of discovery backends (K-V Stores, mDNS, file, token, ...). We realized it was error prone and this PR correctly addresses that issue by only supporting K-V Stores (or at least, that's what I got from skimming through).
Since the multi-backend-kind requirement is gone:

Interface Do we still need the the Discovery interface and all its abstractions?

Format The format in Swarm was kept dumb (ip:port string) because that was the only common ground we have between different kinds. I think it would be a mistake to adopt the same here. Instead, we should probably use a JSON object. On top of my head, it would contain a few fields such as ID, IP, APIPort, Version and Labels (to be discussed). I can defend each field independently but the most important thing is the split between IP and APIPort. Not all engines bind a TCP port, but they mostly have an IP address. Also, in the future we might have more than one port.

Complexity: Given the two previous points, I'd get rid of file, token and whatnot from the codebase. Also, I'd get rid of the generator.

Flags

--discovery-backend was probably a mistake on our side (consul://<ip>). It works well and all, until you factor in the different options the backends accept (TLS and store specific flags). I would maybe vote for something like --discovery-driver consul --discovery-opt ns.key=value (similar to --storage-driver / --execution-driver). Perhaps we'd need --discovery-endpoint?

--discovery-address: Given the previous comment, isn't this confusing? Is this the address of the discovery backend or the address the Engine should advertise? Also I'd probably go with two different flags (ip / port).

--discovery vs --kv (or so): Since it's always backed by a K-V Store, should we call this discovery? What if eventually we use that backend to store more than discovery (like libnetwork is doing)? Either we'll have two different flags (e.g. --discovery-driver and --kv-driver) which will be at best a repetition and at worst we end up using two different K/V stores at once, OR libnetwork will end up storing stuff on the discovery address, which is weird

/cc @icecrime @mavenugo @vieux @abronan @ibuildthecloud

Interface: I think it's elegant as it is, it's not like the interface was extremely rich.
Format: I'm not sure I understand correctly, are you suggesting we store a structure object in the discovery backend rather than a simple "ip:port" string? That seems like a reasonable change.
Complexity: we can ¯_(ツ)_/¯ given the package lives in pkg/, I'm not embarrassed that it provides more features than Docker Engine uses itself, but if we see no value to them in general I'm fine.
Flags: I agree that --discovery-address can be confusing... let's take some time to discuss a better UX.

Interface/Complexity: Not a blocker for me. I just wanted to point to the fact that the entire discovery package could be replaced by 2 libkv calls.

Format: Right now, discovery adds a key in the form of ip:port and no value. The key is directly sourced from --discovery-address. My suggestion would be to use something else as a key engine ID and store a structure object as value. ip:port is flawed because it implies that the engine is listening on TCP and has a port. Things such as libnetwork only need an IP and don't have any requirements on exposing the API Port. /cc @stevvooe: I think you had some feedback on the data object stored for discovery

Flags: I'm still unsure about this --discovery vs --kv thing. If we add discovery and libnetwork also uses --kv, it might get complicated. Right now we only have a couple of flags, but as soon as you add things such as TLS it will get complicated. e.g. --discovery-tls-cert <foo> --kv-tls-cert <foo> ... (there are 5 flags just for TLS, duplicated twice). Also, nasty things will happen if the user uses two different stores for discovery and kv (network splits could affect one but not the other)

Other than that, super happy about this PR

@aluzzardi in order to unblock libnetwork, we need to nail down the UX first as priority and we can work on the backend changes as we get more data.
I agree to your point on Format, as commented earlier : https://github.com/docker/docker/pull/16229#discussion_r39804647, libnetwork cares only for the host-ip and not the port.
Being a user-interface, making it as an object that carries multiple values (maybe in json format) will not be user-friendly. And hence I prefer the simple --discovery-address approach.
with regards to --kv-store, we certainly need a more generic kv-store-params which I think is out-of-scope for this PR. But, since discovery will make use of the --kv-store as its backend, it is certainly valid to identify a better UX.
Do you have any proposal that we can discuss ?

@icecrime the test failures are due to the invalid kv-store configuration outside of the experimental. this requires a fix from libnetwork to be vendored-in. I will push a PR to vendor-in latest libnetwork and that will unblock this PR.

Updated to take last discussions into account. Also rebased: with latest libkv/libnetwork change the tests should hopefully be green.

LGTM, let's address enhancements and documentation in other PRs (like for the /join and /leave endpoints).

Thanks @icecrime. LGTM.

@aluzzardi if you agree, we should merge this PR and that will unblock the dependent PRs. As discussed, the backend updates can be taken up in subsequent PRs.

LGTM as well

LGTM

\o/


ArgumentError

getting this error continuously when i am trying to run for facebook

what version are you using, and put in the code you tried as well

I am new in ROR and i am Using Lagotto 4.3 version , but continuously getting  "ArgumentError".

Now I am Getting Input/output error @ io_write -  for facebook . Please help me..

You are looking for help with Lagotto the application. This is a Ruby gem to use the API from that application. Go to https://github.com/lagotto/lagotto or http://discuss.lagotto.io/ -  closing


chore: add Makefile and a precommit check

A precommit check that runs golangci-lint, go test and go mod tidy to verify everything is clean and working.

Hi @wlynch, thank you for the feedbacks! This is ready for review again.


(maint) Add ability to create orphaned facts to dev utils tool

This adds the ability to create orphaned facts so we can test fact_path gc queries. There is still some work that needs to be done to consolidate all of this into one command. For the time being you need to run this tool twice in order to create the orphaned facts. Once like './pdb simulate 100 10 true' where the true flag creates the extra nested facts, followed by './pdb simulate 100 10' which will recreate the facts without the extra nested ones which results in the orphans being created.
There is also an issue where this script seems to hang after it has submitted it's facts. This appears to be unrelated to this pr and will be addressed later.

Test PASSed

CLA signed by all contributors.

Closing because pr is old and we already used this to test the orphaned fact path issue. I'll keep the branch hanging around if we ever need to revisit.


[EV-3557] Policy Recommendation Scope resource definition

Defines the policy recommendation scope resource
Product Version(s):

Calico Enterprise
Calico Cloud
Issue:

EV-3557
Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

@bmckercher123 Could you please add yourself as a reviewer?


Node ESM configuration w/ CJS & ESM build outputs

Inspired by my use case that led me to #57, I've made several TypeScript configuration changes to transition the package to an ES module, which builds CJS and ESM with types for greater compatibility across Node apps. This PR includes multiple new tsconfig.json files that extend the base and several package.json changes that provide entry points to the respective JS module types. Because there is no open issue for this change, I have avoided dependency upgrades and utilized the configuration options available with the current package.json versions of typescript, jest, & ts-jest.
Because the interoperability of both module types requires that the package become an ES module, I have replaced all require() with import within the src directory. The jest.config.js and .prettierrc.js configuration files adopt the .cjs extension to maintain their syntax and current functionality.
As it stands, I have not created any new tests and can only confirm that the previous test suite is still passing. I will continue to research best practices for transitioning a library from CJS to ESM/CJS compatibility, specifically to generate adequate tests demonstrating this PR is successful in its goal. Because the previous tests do not interact with the dist build (or any build for that matter), I would love any applicable guidance while I attempt to devise and draft relevant tests for each build output.
I understand these changes may also appear too broad in scope, so please feel free to request edits or ask for my justification in your review(s) for any specific choices. I appreciate your time and hope I can make meaningful contributions to this package, even if this PR is not the way.
For reference, my research took me through many sources and guides, but here are some of the most relevant:
tsconfig reference
microsoft/TypeScript: Dual ESM/CJS emit with tsc #54593
microsoft/TypeScript: Proposal: compute module format based on package.json visible to declarationDir/outDir #54546
blog-guide: Supporting CommonJS and ESM with Typescript and Node
ts-jest esm support

This looks great! I don't have any experience with converting to an ES module but I'll merge and play with it!

@coren-frankel I think I got this all working in v1.3.2!


[Suggestion]: Roughly Enough Professions 9.x

General Info

[ ] I would like to propose new content
[X] I would like to propose changes
[ ] I would like to propose another thing

Suggestion Description

The latest Roughly Enough Professions is for 1.18 not 1.19


Take default html path from markup

So, we will only specify the client.markup array and the default value of template.html will be client.markup[0].

:+1:

Under the authority of @adioo :stuck_out_tongue_winking_eye:
markup and a template html are two completely different things. markup makes resources available on the client. html in a template is just a reference to them. A more advanced builder in service will automatically add it to markup when added to a template OR restrict the choice of html to resources loaded with markup.


Rule packaging in modules

When rules are created, they then need to be distributed.
Packaging rules together in a module promotes reuse and provides a convenient distribution mechanism that already exists and is already used by IT pros.
Currently rules from a module can be used by adding the module path to the path parameter of Invoke-PSRule or Get-PSRule, but we can do better.

#17 should be completed first


Abandoned. Use this instead.

I'm sure you came here because it was the first thing on google you saw when searching for a draft.js wysiwyg editor.
What you will soon discover is that this project is abandoned, with no documentation, and the author also did not commit the source code used in the demo you also likely saw (running on a free tier heroku server).
Go here instead for a draft.js wysiwyg editior

He did commit the demo code. If you clone the repo, then cd into it, run npm install, and then run npm start, you should see the demo at localhost:3030

@willbryk720 I find that the source code is compiled and minified.


Allow placement labels to be applied to Gateways

What
As a gateway admin, I want to be able to chose to place a gateway on a set of clusters from my available clusters .
How
use an exact match placement label
kuadrant.io/placement: "key=value"
at a future point we may need more than this simplistic placement logic but this is lightweight.
When a placement is added, the controller needs to figure out which clusters names (secrets) this is selecting. It then needs to add a new label something like: kuadrant.io/<cluster>/placement.decision: "true" which the sync agent will watch for
Done

new placement label defined
new logic to find the cluster the label matches
new logic to add a placement decision to the gateway resource
new unit tests

An alternative here is to lean into the KCP ideas around placement
https://github.com/kcp-dev/kcp/blob/759f510165a012c28f24c2efbdfc2a258354a21b/config/crds/scheduling.kcp.io_placements.yaml
So allowing to target a resource type and place that resource type on clusters that match the label selectors


Documentation Request - Drop Retention Policies

Hi
Can you please explain on this site that dropping an existing retention policy will remove all data in the InfluxDB?
That fact isn't entirely clear and making it more apparent will help users avoid data loss.
Thank you very much!
Doug

@ifelsefi Thanks for the suggestion! This is definitely something that should be more clear.


Very high monthly costs (+USD 800) for extreme high hours of ECS vCPU/Memory

Dear development team,
I installed the Superset Partner Solution. However, from the moment I installed it, the application used an extreme high number of hours of memory/vCPU (+ 37,377 versus 10,000 hours) for ECS Fargate. I connected Superset with a Postgres database on Heroku, but just for testing the connection, nothing else (Superset was not used yet in production, doing queries or creating visualization traffic). So, basically, I just installed Superset, connected to a database and left it as it is (no queries or traffic of what so ever). And that created a AWS bill of USD +800 per month....  I asked AWS but they do not responded very informative. Could it be the installation settings that is causing the issue? Any help is appreaciated, maybe other encounter the same issues with ECS and this installation.

We're getting started here and taking your comment seriously. Did you ever figure this out?

Thanks for responding. No. Never. I searched everywhere, but as I am unfamiliar with AWS it was a total blackbox to me. I assume it has to do with CPU usage, but I was not able to detect where I could modify it and how to modify it. Whatever I switched off, the monthly AWS bill remained extremely high. In the end, I just stopped my account, too afraid to receive another +800 USD bill. Hope you can find the solution because it worked smoothly and the installation was not that difficult (except from some tweekings that I had to find out by trial and error).

Thanks @TreesforFood for taking the bullet and informing.
It would be great to have estimates from the authors or practitioners on cost benchmarks of the solution.

Hi @shivam01anand and @TreesforFood -
We are still in the prototyping phase for our implementation here. We are also using terraform to create the stack, allowing us to pass in existing arn id's and other resources to reduce duplication.
With that being said, there are some common-sense updates we made to the cloudformation template that included extracting:

All environment variables to parameters,
EC2 size values into parameters
ContainerUrl to a parameter
CreateCloudwatchDashboard to a parameter ("no", "yes")
Passing SupersetEnvironment (production/development) - This may actually result in cost-savings since the SupersetNodeTask is only created for the "development" build

We are currently running the regular deployment ("development") and overall, the price with minimal/no-usage is estimated around $18/day for the stack.
There's a handful of other parameters I've yet to extract, but those would likely be the vMem, vCPU values. If we can figure out what the minimum specifications are for each container, tweaking those to small/medium/large could net gain. I can share any updates if we make any progress, but that may not be for a month or so.

I was deploying the partner solution for a side project and yes, the expenses went through the roof. I have similar estimates than @dreilly-icf, $18 per day. This was not sustainable for a side project so now I'm going with typical EC2 approach.

Wow, thank you for pointing this out! I only just launched this stack and while waiting for it to come up saw this. I tried to understand the costs and this compute is probably the bulk of it. It launches all the ECS compute with Fargate so we can use their calculator to understand the costs: https://calculator.aws/#/createCalculator/Fargate
We can find the launch configurations in https://github.com/aws-ia/cfn-ps-apache-superset/blob/main/templates/superset-new-vpc-workload.template.yaml and look at the AWS::ECS::TaskDefinition resources defined in https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ecs-taskdefinition.html
From there I just plugged the numbers into the calculator for us-east-1. It calculated the costs for these resources as such:
(db + redis + superset + superset-init-cleanup + superset-node + superset-worker + superset-worker-beat)

$(9.01 + 9.01 + 170.13 + 18.03 + 144.17 + 170.13 + 170.13) = $690.61

I think superset-init-cleanup was off after the stack started up, so I think maybe you could reduce that number by $18.
The larger Fargate 4vCPU + 16 GiB Mem could maybe be replaced with similarly sized EC2 instances such as t4g.xlarge. That would be $98.11/mo On-Demand on the high end and easily lowered to $61.54 with 1 year EC2 Instance Savings Plan. (There are other plans to get it even lower.)
I'm not sure if we can 'simply' switch the AWS::ECS::TaskDefinitions to use those similarly sized EC2 instances, but that could save a ton and even more if you can get them right sized for your usage.


Make bucket name a function in object storage benchmark

Previously, the API-based object storage benchmarks could not be used when the run
stage was a separate PKB invocation than the prepare stage, because the run
stage depended on a variable defined in the prepare stage. This change
fixes that issue.

@stfeng @yuyantingzero please take a look.

If you follow the original code, you will see the bucket name is assigned to self.bucket_name at the prepare stage, and then later referred to by the run stage by reading from "self.bucket_name". This is the right paradigm and layering: the prepare stage creates a resource and saves the name, and the run stage should strictly depend on the name of the resource created and saved by the prepare stage, instead of coming up a name on the fly.
The real issue here is the benchmark spec "self" is not being pickled properly: looks like bucket_name is not being pickled properly to the JSON file representing this run, therefore if you invoke run() separately, you won't be able to read the bucket_name from the saved benchmark spec. We should either fix the pickling logic of benchmark spec so it saves bucket_name properly, or save the bucket_name to the "vm" object during the prepare stage (because every field of the VM object is pickled properly, that I'm pretty sure).
Actually I think saving the bucket name to the VM object is a better design, because it' will enable us to prepare different VMs that can target different buckets (e.g., each in a different region targeting their own regional buckets).
Thoughts? We can chat more about this.

I see your point about why generating bucket_name in the Prepare stage is good design. Therefore the issue is to pickle bucket_name properly.
The reason bucket_name is not being pickled right now is that it's not attached to the benchmark_spec object. It's attached to the provider-specific object that comes from OBJECT_STORAGE_BENCHMARK_DICTIONARY, which is not saved anywhere.
I think in the long run we might want a list of bucket_names attached to a VM, or even a more complicated state, because I can imagine wanting one VM to use more than one bucket, for instance to see the difference in latency to different providers. However, I think we can go ahead and attach the bucket name to the VM object now, and change it later if we need to. I'll push an updated PR soon.

@stfeng Please take a look. I tested the current patch by running the api_data benchmarks on GCP (for storage and VMs), doing each stage individually. It worked.

LGTM. thanks for the effort in testing and validating this.


Use Google default authentication

Because authentication is interactive in the google driver, it is broken by the new rpc plugin model.
Also users were complaining that there is no way to create machines non-interactively.
This PR introduce the usage of Google Default Application Authentication instead of an oauth interaction with the browser. It means that the experience is closer to what the users are used to with any
gcloud command.

@jeffmendoza @nathanleclaire Can you take a look please?

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "gce-default-auth" git@github.com:dgageot/machine.git somewhere
$ cd somewhere
$ git rebase -i HEAD~4
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Awesome.  Thanks for doing this.  Will take a look ASAP

You might need to rebase on https://github.com/docker/machine/pull/2088

Merged #2088

I'm not getting the cli args to go through:
$ docker-machine create --help --driver google
Usage: docker-machine create [OPTIONS] [arg...]

Create a machine.

Specify a driver with --driver to include the create flags for that driver in the help text.

Options:

   --driver, -d "none"											Driver to create machine with.
   --engine-install-url "https://get.docker.com"							Custom URL to use for engine installation [$MACHINE_DOCKER_INSTALL_URL]
...

$ docker-machine create --driver google --google-project my-proj gce
Error setting machine configuration from flags provided: Please specify the Google Cloud Project name using the option --google-project.

@jeffmendoza Do you have the docker-machine-driver-google plugin binary installed (i.e. in PATH)?

Update: In the code there's a block like
    if d.Project == "" {
        return fmt.Errorf("Please specify the Google Cloud Project name using the option --google-project.")
    }

but d.Project never gets set.  @dgageot what's the intended usage with this PR?

That has to be a rebase fumble!
Le lun. 26 oct. 2015 à 23:02, Nathan LeClaire<EMAIL_ADDRESS>a
écrit :

Update: In the code there's a block like
if d.Project == "" {
    return fmt.Errorf("Please specify the Google Cloud Project name using the option --google-project.")
}

but d.Project never gets set. @dgageot https://github.com/dgageot
what's the intended usage with this PR?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/pull/2087#issuecomment-151297118.

OK -- please make sure to fix and CC -- likewise please post some usage instructions.

I can't fix that tonight. Will check tomorrow. Sorry...
Le lun. 26 oct. 2015 à 23:29, David Gageot<EMAIL_ADDRESS>a écrit :

That has to be a rebase fumble!
Le lun. 26 oct. 2015 à 23:02, Nathan LeClaire<EMAIL_ADDRESS>a écrit :

Update: In the code there's a block like
if d.Project == "" {
    return fmt.Errorf("Please specify the Google Cloud Project name using the option --google-project.")
}

but d.Project never gets set. @dgageot https://github.com/dgageot
what's the intended usage with this PR?
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/pull/2087#issuecomment-151297118.

@nathanleclaire It should work now. /cc @jeffmendoza
To make it work, it needs gcloud to be installed.
gcloud auth login
docker-machine create --driver google --google-project my-proj gce1
docker-machine create --driver google --google-project my-proj gce2

@dgageot nice work!  just tested and this works perfect.
lgtm

@docker/machine-maintainers ptal

Hey @dgageot .  I am trying to test it but can't figure it out.  I have created a Google Cloud project named "baguette" and enabled the "VM Instances" sub-section.  I have also run gcloud auth login.  It tells me baguette is my default project.
But:
$ docker-machine create -d google --google-project baguette baggy
Running pre-create checks...
Creating machine...
Error creating machine: Error in driver during machine creation: You might have to run `gcloud auth login` to get the authorization credentials: googleapi: Error 400: Invalid value for project: baguette, invalid

Any ideas what's wrong?  I've run gcloud auth login many times.

Google always use project name when it should really be project id.
Baguette is not the project name
Le mer. 28 oct. 2015 à 00:22, Nathan LeClaire<EMAIL_ADDRESS>a
écrit :

Hey @dgageot https://github.com/dgageot . I am trying to test it but
can't figure it out. I have created a Google Cloud project named "baguette"
and enabled the "VM Instances" sub-section. I have also run gcloud auth
login. It tells me baguette is my default project.
But:
$ docker-machine create -d google --google-project baguette baggyRunning pre-create checks...Creating machine...Error creating machine: Error in driver during machine creation: You might have to run gcloud auth login to get the authorization credentials: googleapi: Error 400: Invalid value for project: baguette, invalid
Any ideas what's wrong? I've run gcloud auth login many times.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/pull/2087#issuecomment-151673456.

I still get issue using baguette-1111 which seems to be the project ID?
$ docker-machine --debug create -d google --google-project baguette-1111 baggy
Docker Machine Version: 0.5.0-rc3 (361b123)
Launching plugin server for driver google
Found binary path at /usr/local/bin/docker-machine-driver-google
Plugin server listening at address <IP_ADDRESS>:65128
() Calling RpcServerDriver.GetVersion
Using API Version 1
() Calling RpcServerDriver.SetConfigRaw
() Calling RpcServerDriver.GetMachineName
(baguette-1111) Calling RpcServerDriver.GetCreateFlags
Making call to close connection to plugin binary
Making call to close driver server
(baguette-1111) Calling RpcServerDriver.Close
Successfully made call to close driver server
Launching plugin server for driver google
Found binary path at /usr/local/bin/docker-machine-driver-google
Plugin server listening at address <IP_ADDRESS>:65132
() Calling RpcServerDriver.GetVersion
Using API Version 1
() Calling RpcServerDriver.SetConfigRaw
() Calling RpcServerDriver.GetMachineName
(baggy) Calling RpcServerDriver.GetMachineName
(baggy) Calling RpcServerDriver.DriverName
(baggy) Calling RpcServerDriver.GetCreateFlags
(baggy) Calling RpcServerDriver.SetConfigFromFlags
Running pre-create checks...
(baggy) Calling RpcServerDriver.PreCreateCheck
(baggy) Calling RpcServerDriver.GetConfigRaw
(baggy) Calling RpcServerDriver.GetConfigRaw
Creating machine...
(baggy) Calling RpcServerDriver.Create
(baggy) OUT | Creating host...
(baggy) OUT | Generating SSH Key
(baggy) OUT | Creating instance.
(baggy) OUT | Creating firewall rule.
Error creating machine: Error in driver during machine creation: You might have to run `gcloud auth login` to get the authorization credentials: googleapi: Error 404: The resource 'projects/baguette-1111' was not found, notFound

The error message changed. But I have no idea. I'll try with a brand new
project tomorrow
Le mer. 28 oct. 2015 à 01:33, Nathan LeClaire<EMAIL_ADDRESS>a
écrit :

I still get issue using baguette-1111 which seems to be the project ID?
$ docker-machine --debug create -d google --google-project baguette-1111 baggyDocker Machine Version: 0.5.0-rc3 (361b123)Launching plugin server for driver googleFound binary path at /usr/local/bin/docker-machine-driver-googlePlugin server listening at address <IP_ADDRESS>:65128() Calling RpcServerDriver.GetVersionUsing API Version 1() Calling RpcServerDriver.SetConfigRaw() Calling RpcServerDriver.GetMachineName(baguette-1111) Calling RpcServerDriver.GetCreateFlagsMaking call to close connection to plugin binaryMaking call to close driver server(baguette-1111) Calling RpcServerDriver.CloseSuccessfully made call to close driver serverLaunching plugin server for driver googleFound binary path at /usr/local/bin/docker-machine-driver-googlePlugin server listening at address <IP_ADDRESS>:65132() Calling RpcServerDriver.GetVersionUsing API Version 1() Calling RpcServerDriver.SetConfigRaw() Calling RpcServerDriver.GetMachineName(baggy) Calling RpcServerDriver.GetMachineName(baggy) Calling RpcServerDriver.DriverName(baggy) Calling RpcServerDriver.GetCreateFlags(baggy) Calling RpcServerDriver.SetConfigFromFlagsRunning pre-create checks...(baggy) Calling RpcServerDriver.PreCreateCheck(baggy) Calling RpcServerDriver.GetConfigRaw(baggy) Calling RpcServerDriver.GetConfigRawCreating machine...(baggy) Calling RpcServerDriver.Create(baggy) OUT | Creating host...(baggy) OUT | Generating SSH Key(baggy) OUT | Creating instance.(baggy) OUT | Creating firewall rule.Error creating machine: Error in driver during machine creation: You might have to run gcloud auth login to get the authorization credentials: googleapi: Error 404: The resource 'projects/baguette-1111' was not found, notFound
—
Reply to this email directly or view it on GitHub
https://github.com/docker/machine/pull/2087#issuecomment-151683552.

Thanks @dgageot

@nathanleclaire It works with my brand new cupcake-1112 project.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "gce-default-auth" git@github.com:dgageot/machine.git somewhere
$ cd somewhere
$ git rebase -i HEAD~8
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

@nathanleclaire I added a precheck for the project. This could give better feedback if the project is not found (for real of because of not using the project id) or when credentials are not valid.
I also updated the doc s/project name/project id/
Can you test again?

Sure thing

OK, my issue seems pretty clearly to be PEBKAC (mixing up my Google accounts).
Tried it and successfully created several instances.
Please rebase and squash, then: LGTM!

@nathanleclaire squashed! Thanks for your time.

LGTM :+1:


Closing for now as we have design docs scheduled that represent tickets such as https://github.com/celo-org/celo-monorepo/issues/382


Property naming rule reports anonymous object's instance variables should use the screaming snake case

Expected Behavior
ktlint should allows the camelCase properties in anonymous objects, for example,
interface MyInterface {
    fun myFunction()
}

fun main() {
    val myObject = object : MyInterface {
        private val name = "Example"

        override fun myFunction() {
            print("Hello, $name")
        }
    }
}

Observed Behavior
ktlint command fails with following output.
/tmp/MyInterface.kt:7:21: Property name should use the screaming snake case notation when the value can not be changed (standard:property-naming)

Summary error count (descending) by rule:
  standard:property-naming: 1

Steps to Reproduce
Put the above code at /tmp/MyInterface.kt, and run the following command:
$ ktlint --experimental /tmp/MyInterface.kt

Your Environment

Version of ktlint used: 0.49.1
Operating System and version: macOS Ventura 13.4

Both https://kotlinlang.org/docs/coding-conventions.html#property-names and https://developer.android.com/kotlin/style-guide#constant_names are describing the rules regarding constants:
Kotlin coding conventions:

Names of constants (properties marked with const, or top-level or object val properties with no custom get function that hold deeply immutable data) should use uppercase underscore-separated (screaming snake case) names

Android style guide:

Constants are val properties with no custom get function, whose contents are deeply immutable, and whose functions have no detectable side-effects. This includes immutable types and immutable collections of immutable types as well as scalars and string if marked as const. If any of an instance’s observable state can change, it is not a constant. Merely intending to never mutate the object is not enough.
...
Constant values can only be defined inside of an object or as a top-level declaration. Values otherwise meeting the requirement of a constant but defined inside of a class must use a non-constant name.

So the way I read above, the name property is a constant.

Thanks for reply, Paul.
I reconsidered the name filed in anonymous object, and concluded that I should define it as a constant as you pointed out, with following reasons,

the field doesn't need to be an instance field, but can be static field
its value can be defined at compile time, not runtime

So, I close this issue and change my code with companion object !
Regards,


Postgres Query Performance Suffering with relationJoins toggled on

Bug description
Upon enabling the relationJoins feature, we noticed significant performance degradation when join on our higher-volume tables.
How to reproduce
With a query of:
const ormQuery = (companyId: string, scenarioId: string) =>
    prisma.account.findMany({
        select: {
            parentEdges: {
                where: {
                    companyId,
                    scenarioId,
                },
                select: {
                    childAccountId: true,
                },
            },
        },
        where: {
            isDeleted: false,
            companyId,
            scenarioId,
        },
    });

We get
> ORM Query time: 196993.99ms
Accounts: 7800
Edges: 187200

This translates to the following generated query:
SELECT
  "t1"."id",
  "Account_parentEdges"."__prisma_data__" AS "parentEdges"
FROM
  "public"."account" AS "t1"
  LEFT JOIN LATERAL (
    SELECT
      COALESCE(
        JSONB_AGG("__prisma_data__"),
        '[]'
      ) AS "__prisma_data__"
    FROM
      (
        SELECT
          "t4"."__prisma_data__"
        FROM
          (
            SELECT
              JSONB_BUILD_OBJECT(
                'child_account_id', "t3"."child_account_id"
              ) AS "__prisma_data__",
              "t3"."company_id",
              "t3"."scenario_id"
            FROM
              (
                SELECT
                  "t2".*
                FROM
                  "public"."figure_formula_edge" AS "t2"
                WHERE
                  "t1"."id" = "t2"."parent_account_id"
                  /* root select */
                  ) AS "t3"
              /* inner select */
              ) AS "t4"
        WHERE
          (
            "t4"."company_id" = redacted
            AND "t4"."scenario_id" = redacted
          )
          /* middle select */
          ) AS "t5"
      /* outer select */
      ) AS "Account_parentEdges" ON true
WHERE
  (
    "t1"."is_deleted" = false
    AND "t1"."company_id" = redacted
    AND "t1"."scenario_id" = redacted
  )

An EXPLAIN plan on the above: https://explain.dalibo.com/plan/6ac93498ee8ad4c1

Note the 1.5 BILLION rows removed by filter
Note the 280 GB buffer usage

Important: When removing WHERE ("t4"."company_id" = redacted AND "t4"."scenario_id" = redacted) the query time speeds up comparable to the query below.

With a raw query of:
const rawQuery = (companyId: string, scenarioId: string) =>
    prisma.$queryRaw<
        { id: string; parent_edges: { child_account_id: string }[] }[]
    >`
        SELECT
            account.id,
            COALESCE(
                JSONB_AGG(JSONB_BUILD_OBJECT('child_account_id', figure_formula_edge.child_account_id)),
                '[]'
            ) as parent_edges
        FROM
            account
        LEFT JOIN
            figure_formula_edge
            ON account.id = figure_formula_edge.parent_account_id AND figure_formula_edge.company_id = ${companyId}::uuid AND figure_formula_edge.scenario_id = ${scenarioId}::uuid
        WHERE
            account.company_id = ${companyId}::uuid
            AND account.scenario_id = ${scenarioId}::uuid
        GROUP BY
            account.id
    `;

We get
> Raw Query time: 1255.28ms
Accounts: 7800
Edges: 187200

an EXPLAIN plan on the above: https://explain.dalibo.com/plan/39c27d5cd858cf31
Expected behavior
No response
Prisma information

model Account {
  id                          String                                @id @default(dbgenerated("uuid_generate_v4()")) @db.Uuid
  companyId                   String                                @map("company_id") @db.Uuid
  scenarioId                  String                                @map("scenario_id") @db.Uuid
  childEdges                  FigureFormulaEdge[]                   @relation("accountTofigure_formula_edge_child_account_id")
  parentEdges                 FigureFormulaEdge[]                   @relation("accountTofigure_formula_edge_parent_account_id")

  @@unique([id, companyId, scenarioId, isDeleted], map: "account_id_company_id_scenario_id_is_deleted_unique")
  @@unique([id, companyId, scenarioId], map: "account_id_company_id_scenario_id_unique")
  @@index([unitTableId], map: "account_unit_table_id_index")
  @@index([scenarioId], map: "account_scenario_id_index")
  @@index([id, companyId, scenarioId, isDeleted], map: "account_id_company_id_scenario_id_is_deleted_index")
  @@map("account")
}

model FigureFormulaEdge {
  parentId        String   @map("parent_id") @db.Uuid
  childId         String   @map("child_id") @db.Uuid
  createdAt       DateTime @default(now()) @map("created_at") @db.Timestamptz(6)
  updatedAt       DateTime @default(now()) @map("updated_at") @db.Timestamptz(6)
  companyId       String   @map("company_id") @db.Uuid
  parentAccountId String   @map("parent_account_id") @db.Uuid
  childAccountId  String   @map("child_account_id") @db.Uuid
  scenarioId      String   @map("scenario_id") @db.Uuid
  childAccount    Account  @relation("accountTofigure_formula_edge_child_account_id", fields: [childAccountId], references: [id], onDelete: NoAction, onUpdate: NoAction, map: "figure_formula_edge_child_account_id_foreign")
  child           Figure   @relation("account_monthly_figureTofigure_formula_edge_child_id", fields: [childId], references: [id], onDelete: NoAction, onUpdate: NoAction, map: "figure_formula_edge_child_id_foreign")
  company         Company  @relation("companyTofigure_formula_edge", fields: [companyId], references: [id], onDelete: NoAction, onUpdate: NoAction, map: "figure_formula_edge_company_id_foreign")
  parentAccount   Account  @relation("accountTofigure_formula_edge_parent_account_id", fields: [parentAccountId], references: [id], onDelete: NoAction, onUpdate: NoAction, map: "figure_formula_edge_parent_account_id_foreign")
  parent          Figure   @relation("account_monthly_figureTofigure_formula_edge_parent_id", fields: [parentId], references: [id], onDelete: NoAction, onUpdate: NoAction, map: "figure_formula_edge_parent_id_foreign")
  scenario        Scenario @relation(fields: [scenarioId], references: [id], onDelete: NoAction, onUpdate: NoAction, map: "figure_formula_edge_scenario_id_foreign")

  @@id([parentId, childId])
  @@index([childAccountId], map: "figure_formula_edge_child_account_id_index")
  @@index([childId], map: "figure_formula_edge_child_id_index")
  @@index([parentAccountId], map: "figure_formula_edge_parent_account_id_index")
  @@index([parentId], map: "figure_formula_edge_parent_id_index")
  @@index([childId, companyId, parentId], map: "figure_formula_edge__child_id_company_id__covering_index")
  @@index([companyId, scenarioId], map: "figure_formula_edge_company_id_scenario_id_index")
  @@map("figure_formula_edge")
}

Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: v21.6.1

Prisma Version
prisma                  : 5.7.1
@prisma/client          : 5.7.1
Computed binaryTarget   : darwin
Operating System        : darwin
Architecture            : x64
Node.js                 : v21.6.1
Query Engine (Node-API) : libquery-engine 0ca5ccbcfa6bdc81c003cf549abe4269f59c41e5 (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 0ca5ccbcfa6bdc81c003cf549abe4269f59c41e5 (at node_modules/@prisma/engines/schema-engine-darwin)
Schema Wasm             : @prisma/prisma-schema-wasm 5.7.1-1.0ca5ccbcfa6bdc81c003cf549abe4269f59c41e5
Default Engines Hash    : 0ca5ccbcfa6bdc81c003cf549abe4269f59c41e5
Studio                  : 0.495.0
Preview Features        : metrics, relationJoins

Hi @chris-basis, thanks for opening this issue.
Would you mind upgrading to<EMAIL_ADDRESS>and letting us know whether you still face the same kind of performance concerns?
Thank you.

Hey @jkomyno, looks like the same query plan on the newer version. Pasting the raw vs. generated query below. This looks like it aligns with
Prisma version: 5.9.1
prisma:query

        SELECT
            account.id,
            COALESCE(
                JSONB_AGG(JSONB_BUILD_OBJECT('child_account_id', figure_formula_edge.child_account_id)),
                '[]'
            ) as parent_edges
        FROM
            account
        LEFT JOIN
            figure_formula_edge
            ON account.id = figure_formula_edge.parent_account_id AND figure_formula_edge.company_id = $1::uuid AND figure_formula_edge.scenario_id = $2::uuid
        WHERE
            account.company_id = $3::uuid
            AND account.scenario_id = $4::uuid
        GROUP BY
            account.id

> Raw Query time: 1537.885498046875
Accounts: 7800
Edges: 187200

---

      SELECT
        "t1"."id",
        "Account_parentEdges"."__prisma_data__" AS "parentEdges"
      FROM
        "public"."account" AS "t1"
        LEFT JOIN LATERAL (
          SELECT
            COALESCE(
              JSONB_AGG("__prisma_data__"),
              '[]'
            ) AS "__prisma_data__"
          FROM
            (
              SELECT
                "t4"."__prisma_data__"
              FROM
                (
                  SELECT
                    JSONB_BUILD_OBJECT(
                      'child_account_id', "t3"."child_account_id"
                    ) AS "__prisma_data__",
                    "t3"."company_id",
                    "t3"."scenario_id"
                  FROM
                    (
                      SELECT
                        "t2".*
                      FROM
                        "public"."figure_formula_edge" AS "t2"
                      WHERE
                        "t1"."id" = "t2"."parent_account_id"
                        /* root select */
                        ) AS "t3"
                    /* inner select */
                    ) AS "t4"
              WHERE
                (
                  "t4"."company_id" = $1
                  AND "t4"."scenario_id" = $2
                )
                /* middle select */
                ) AS "t5"
            /* outer select */
            ) AS "Account_parentEdges" ON true
      WHERE
        (
          "t1"."is_deleted" = $3
          AND "t1"."company_id" = $4
          AND "t1"."scenario_id" = $5
        )

> ORM Query time:<PHONE_NUMBER>578125
Accounts: 7800
Edges: 187200

Could this potentially be related to https://github.com/prisma/prisma/issues/22596?

Hey @chris-basis,
Is there any way you could provide some kind of reproduction or more info about the statistics of your tables?
I've tried taking the datamodel you shared and seeded it with millions of rows. However, since the core issue seems to come from the filters on scenarioId and companyId, I'm failing to get a realistic reproduction where the filter filters enough rows to get to the perf issues you're seeing.
Thanks for the help 🙏

Hey there @chris-basis 👋🏼
Just pinging again: have you been able to look at @Weakky's comment above?
In order to proceed further, we need your help here. Thank you and hope to hear from you soon!

@apolanc have you checked out https://github.com/prisma/prisma/issues/22596? It contains reproductions + @chris-basis gave a thumbs up to my comment above mentioning it.

@BracketJohn I don't believe this issue to be related to #22596. @chris-basis basis is complaining about a query plan being slow. It's no longer the case for #22596 now that they've added an index. The query from #22596 takes 500ms instead of 300ms without relationJoins. The remaining time is overhead from the Query Engine, which we must improve but isn't related to OP's problem. Here we're talking about a query plan that takes 3mn on EXPLAIN ANALYZE.
I've spent significant time again trying to reproduce @chris-basis issue. I thought I had something at some point where the index scan would return 4.5M rows instead of 44k which was causing the heap scan to take forever, but after re-seeding it to test something, it no longer reproduces.
Here's the slow query plan: https://explain.dalibo.com/plan/e647aacea9h8hd31
And what I'm getting now without having changed anything: https://explain.dalibo.com/plan/07ffc1dhe3b5f3ed
@chris-basis I need further help to move this forward. I have setup this reproduction repo https://github.com/Weakky/repro-23139 so that you can have a look at what I'm doing. It may be that the mock data I'm seeding is not representative of your own. If that's the case, could you please edit the seed.ts file in a way that reproduces what you're seeing on prod?
Thank you

Hey @chris-basis  ,
Did you get a chance to have a look at my collegues comment? It'd be helpful for us to move your issue forward.
Without further information, we'll have to close this issue. Thank you 🙏


Extract contextual frames, perform IC with pybasic, and store target + IC frame in LanceDB

This PR addresses #43 by extracting contextual frames, perform IC with pybasic, and store target + IC frame in LanceDB. This work focuses on a limited set of data for development purposes, keeping concurrency in mind throughout to help prepare for #44 . Generally I also tried to be storage space conscious, removing files as they are no longer needed. I removed the earlier array storage work as it felt more appropriate to store image blobs instead (one could always extract the arrays afterwards).
To use pybasic in these changes I forked the repo under WayScience, created a branch from the submodule commit hash referenced in IDR_Stream, and modified the setup.py to be installable as a package (the exact reference may be found within the pyproject.toml file).
I'm attaching an example dataset created from this work here as a reference: example.zip.
Closes #43

Thanks @jenna-tomkinson for the review! There were a couple of comments which I left unresolved which I wanted to get your opinion on so I re-requested your review. Please don't hesitate to let me know if you have any questions / concerns.

Thanks @jenna-tomkinson ! Merging this in.


Angular Dependency

bower.json should specify a dependency on Angular so that utilities like main-bower-files can ensure that Angular is loaded before angular-local-storage.
(Until then, a manual override of the dependencies key is necessary in the bower.json of any project using this package.)

Also experiencing the same problem. Will submit a PR.


[IOTDB-4037] Change default query execute threads to cpu cores

Change default query execute threads to cpu cores and don't set up DataExchangeService in standalone mode.

Coverage decreased (-0.0003%) to 42.517% when pulling 9dd9e26290e4d04815eb7471046b5e06f8f649e7 on ThreadChange into 8f12321e75c1778ad1a9c4a9f9b7527893f3cf58 on master.


Create a Helm chart

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Please create a helm chart for this operator so it is easier for users to install and maintain.

There is already an Helm chart (though probably we don't have in the README)
@oliverbaehler added it.
https://github.com/gianlucam76/k8s-cleaner/tree/main/charts/k8s-cleaner

I will let @oliverbaehler answer that (I don't want to risk giving an incorrect answer)

@oliverbaehler I see from the log output of the github actions that the helm repo is this: oci://ghcr.io/gianlucam76/charts/k8s-cleaner
But I am not able to run helm repo add using this link. Is there a link I could use helm repo add or helm pull with? I need such a link so I can integrate this operator in our CI pipeline. Thanks.

helm install k8s-cleaner oci://ghcr.io/gianlucam76/charts/k8s-cleaner --version 0.4.0   -n k8s-cleaner --create-namespace

@gianlucam76 btw on the repo you can enable packages on the repo. Then the chart package it will be displayed on the right site of the repository


Improvement: Weird "my system" displayed in the message when there is a site issue

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?: New feature/ improvement
Reproducible in production?: New feature/ improvement
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @puneetlath
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1697552341198789
Action Performed:

Attempt it to sign in when there is site issue

Expected Result:
“We’re having trouble connecting to the server. Please try again.” or similar message should be displayed
Actual Result:
My system is currently undergoing maintenance. Check status.expensify.com for more details
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~017290771c8e759941
Upwork Job ID:<PHONE_NUMBER>230605824
Last Price Increase: 2023-10-18

@isabelastisser FYI this was on OldDot so will need to be Internal.

I don't think we would need C+ here right? It mentions OldDot.

Internal.

@AndrewGable are we currently working on this? Should I change this to monthly?

Weekly is fine, I should be working on it.

@puneetlath - Any suggestions on a better error message? It's coming from here:
https://github.com/Expensify/Web-Expensify/blob/21bc2d740290d1e52a11c66a7b25887884a166cb/homepage/js/signin.jsx#L1208

Maybe "Expensify" instead of "My system"?

How about something like:

We are having trouble connecting. Check status.expensify.com for more details.

And also making status.expensify.com a hyperlink.

The hyperlink is being a pain, the button below goes to status.expensify.com, is that good enough?

Works for me!

I'd just put a period on the end of the second sentence.

PR was deployed to production a week ago. All done


UC.3.2 Losing the game:  As a game I want to give the players an option to communicate when they lost the game, to end the game in the right moment.

Acceptance Criteria

[x] There should be a button to press which any user is able to press.
[x] When pressing the losing-button the game is ended and the round of the game is lost.
[x] When the game is lost all players should be informed and redirected accordingly.

Task List

[x] sopra-fs22-group-11/SoPra22-group11-TheGame-Client#7
[x] sopra-fs22-group-11/SoPra22-group11-TheGame-Server#104
[x] sopra-fs22-group-11/SoPra22-group11-TheGame-Client#8
[x] sopra-fs22-group-11/SoPra22-group11-TheGame-Client#9
[x] sopra-fs22-group-11/SoPra22-group11-TheGame-Server#107
[x] sopra-fs22-group-11/SoPra22-group11-TheGame-Server#108
[x] #145

191eb8f1aba6e9284d53bac651ab817e1cbd3cf1


No smooth animations

On one of my machines, there are now buttery-smooth animations that move components into view. On another machine, it's just a jerky jump. See below:
https://github.com/user-attachments/assets/43cd9eb6-cd1e-42a2-b601-25bfa217bf55
Both are MBPs with very similar specs

By any chance have you switched on "reduced motion" on the second machine, because we honor that flag if you've set it and we don't animate. Quick check: window.matchMedia("(prefers-reduced-motion: reduce)").matches

returns false

Well that's ... odd. Can you try again with tip-of-tree?

still don't see animations..  I wonder what's going on. Is there something I can check in DevTools to get glean insights?

Ok, so on the non-animating MBP, the value is always false, because it is only called from here:
https://github.com/breadboard-ai/breadboard/blob/f79278038e77235454ded92e9733aa5d8b12ee31/packages/shared-ui/src/elements/editor/graph-renderer.ts#L1618-L1622

The general difference between the two cases is whether we are creating new graphs or updating existing ones. In the case where we are creating new graphs we assume it's a tab switch or a board load where we wouldn't want to animate. All other cases, particularly around selections, are usually graph updates and we animate those. I'm not entirely clear why we would animate updates on one MBP but not another!

you will not believe this. It just started working for no reason. Can't repro anymore.

hmm and now it's back to no animations.

oh interesting! It only seems to skip animations when in this state:

I wonder if there's some math around the number of configs?...

Ah, it's because in that mode we swap graphs entirely so there's no animation. Initially I had the animation on when swapping between the boards and it was very jarring. So... WAI?

This mode is causing more issues than I'd like, so I'm going to remove it and find a better way to organize the Workspace.


kak-lsp doesn't pickup user config

I noticed that kak-lsp doesn't pickup my config at ~/.config/kak-lsp/kak-lsp.toml.
I've changed language.go part to use gopls instead of default bingo, however kak-lsp still launches bingo instead of gopls.
Version I use is master 05c8c4b.

Yes, there is a breaking change in master regarding the config location. Now kak-lsp tries to read kak-lsp/kak-lsp.toml under OS-specific config dir as described here https://docs.rs/dirs/2.0.1/dirs/fn.config_dir.html

Thank you!


Fix typo in 0011-inline-spirv.md

NumWorkgroups should be a uint vector with three components.

@s-perron tiny little typo fix

Added another typo fix in the builtin output section.


test: Integrate cmocka into autotools build, add basic test case for …

…device TCTI.
The current test layout I'm trying is a module (.c & .h file) in the
base test/ directory that is a collection of test functions for a
specific module of code from the tpm2.0-tss project. This test module is
named after the module it tests and the suffix '_test' is appended.
There should be NO dependency on the test framework in this module.
This test module is accompanied by a driver that sets up the test
framework with the tests from the module. This driver is given the name
of the module that it tests.
This resolves #18
Signed-off-by: Philip Tricca<EMAIL_ADDRESS>

Philip, I looked at this.  Doesn't look like it's actually testing anything yet.  I couldn't find anything in the build output that looked like a test ran.
But looks like a good first inroad to creating a test infrastructure.

Test cases are executed when 'make check' is run. I'll add a note about this in the INSTALL file.
As to whether or not the initial test I've added actually tests anything, that's a matter of what you think a test is. It's not testing anything at the scope that the current tpmclient / tpmtest do but that's intentional. The single test in this commit tests whether or not the device TCTI initialization function returns the proper size when the context parameter is NULL. If the call returns anything but the size of the TCTI structure the test case will fail.

Ok, I ran "make check", and it worked.  I had no issue with the test case you created, it was just that I wasn't seeing any test results.


healthsite geoname

As a user I would like to know the geonames associated with the latitude and Longitude of a location
Question:
Given that we are not collecting the 'physical address' of each location should we rather import the Geoname associated with the point?

Why has it been decided to exclude physical address?
On 8 November 2015 at 14:02, Mark Herringer<EMAIL_ADDRESS>wrote:

As a user I would like to know the geonames associated with the latitude
and Longitude of a location
Question:
Given that we are not collecting the 'physical address' of each location
should we rather import the Geoname associated with the point?
[image: location-data-sidebar]
https://cloud.githubusercontent.com/assets/38838/11020206/1e8b4f84-8610-11e5-98b7-509f621d6cad.png
—
Reply to this email directly or view it on GitHub
https://github.com/healthsites/healthsites/issues/281.


S3 storage

includes code necessary to support s3 for media (right now, xlsforms and survey attachments) as well as a management command to migrate data from local storage to s3

don't merge yet!


Support for Azure SAS (Shared Access Signatures)

Output of restic version
restic 0.9.5 compiled with go1.12.2 on linux/amd64
What should restic do differently? Which functionality do you think we should add?
Currently, Restic supports authenticating with Azure Storage Account credentials, but does not support Azure SAS (shared access signatures: https://docs.microsoft.com/en-us/azure/storage/common/storage-dotnet-shared-access-signature-part-1)
SAS is important as it allows granular, time limited, per-container permissions to be used, instead of using the storage account key which gives read/write over the entire account and all resources (including all containers, tables, queues and fileshares).
Currently, with Restic requiring the use of the storage account key, any secure deployment at scale is forced to create many separate storage accounts housing single containers. This is clearly not the intended way to use Azure storage.
Moreover, storage account names are within a global namespace, and have a limited charset, meaning creating many accounts can be a problem.
SAS support was added to Duplicity with minimal changes, which may mean the same would be true with Restic:
https://bazaar.launchpad.net/~duplicity-team/duplicity/0.8-series/revision/1179#duplicity/backends/azurebackend.py
What are you trying to do?
Use Restic on Azure with SAS, and avoid using the Storage Account "master key", making backup containers easier to manage.
Did restic help you or made you happy in any way?
Restic is great, easy to deploy and backed up by good documentation. I'm happy that this is my only significant problem so far.

You can workaround this by using rclone backend:
https://restic.readthedocs.io/en/latest/030_preparing_a_new_repo.html#other-services-via-rclone
rclone supports SAS authentication for Azure accounts and containers:
https://rclone.org/azureblob/#sas-url


⚠ ClamAV has degraded performance

In 3834625, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 247 ms

Resolved: ClamAV performance has improved in 45054af after 6 minutes.


[ISSUE #46] Refactor and split core module

Fixes #46

Split classes in core module to other modules
Move Spring Boot dependencies to common module
console must scan&depend core to use @Autowired

@githublaohu Do we need to consider the implementation classes from the core module as service beans when referencing them?


Removed UIAdditions Categories

This change is

Test to make sure none of the styles are messed up (especially on cells)

Reviewed 73 of 73 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion, all commit checks successful.

a discussion (no related file):
Test to make sure none of the styles are messed up (especially on cells)

Comments from Reviewable


More flexible job lock handlers

The current LockHandler requires module override to redefine (which is usually an anti-pattern). Would be good to be able to replace (or disable) the lock handler via an extender of some sort.

This is a duplicate of #93. Closing this one, and will need to unify the implementation.


Android Hermes - Reflect Error

To solve issue:
utils/sagaInjector and utils/reducerInjector files will update.

Issue fixed in release v0.0.5


Integration/Compatible instructions for OPNsense?

Currently I have an OPNsense installation with the wifibox ports installed. The guest boots and everything seems mostly ok, however I am configuring this for hostapd and am at a loss for what exactly is needed. I've added interface=wlan0 in wifibox's hostapd.conf, which was enough to get hostapd running in the guest, however hostapd_cli ping and other commands on the host result in timeouts.
I'm assuming it's because there is some sort of routing or additional network configuration that needs to happen on the host, but whatever it is it would need to not interfere with OPNsense's system configuration.
Ideally I could just start wifibox and then create a wireless interface from within the OPNsense web UI, but when I attempt that it complains that it couldn't create a wireless device for wifibox0 in AP mode or something to that effect.
Also, FWIW the Intel 9260 is otherwise working with the current version of wifibox with the most recent wifibox-alpine image on FreeBSD 13.0.

The hostapd_cli will only work from the host if the control sockets are enabled in hostapd.conf.  I am sharing you the configuration file I used for testing, maybe this helps:
ctrl_interface=/var/run/hostapd
ctrl_interface_group=0
interface=wlan0

ssid=<ssid>
country_code=<country_code>
channel=11
hw_mode=g

ieee80211n=1
ht_capab=[HT40-][SHORT-GI-20][SHORT-GI-40]

auth_algs=1
wpa=2
wpa_passphrase=<wpa_passphrase>
wpa_key_mgmt=WPA-PSK
rsn_pairwise=CCMP

macaddr_acl=0

The wifibox0 should be managed by wifibox as it has to be linked to the virtual machine via bridging.  There is no "AP mode", it appears as a virtual Ethernet interface on the host.  Unfortunately, I do not have any experience with OPNsense, so I do not have any understanding on how exactly the integration should work.


Tipset and TipsetKeys property tests

Summary of changes
Changes introduced in this pull request:

Add quickcheck tests for tipset and tipsetkeys using quickcheck

Reference issue to close (if applicable)

Closes
part of #1881, affected tasks have been marked complete
Other information and links

Good point @jdjaustin! :)

Probably nit, but @LesnyRumcajs has been asking me to put the struct and impl blocks under each property test module (i.e., so there is only one #[cfg(test)] for all the property test code), and the code is definitely a lot cleaner that way.

Not a nitpick at all, this makes sense. Fixing now


Update Composer dependencies (2020-11-05-00-04)

Visual regression test passed!
View the visual regression test report


Added github corner

Hii Mate. Added Github Corner on your efficient and useful website.

Yup sure

Good work @SarveshLimaye 👍🏻


chore: update repository template to 118b7850

Updated repository templates to https://github.com/ory/meta/commit/118b7850ed173d809e84acdf20fec1ff7273856f.

Coverage remained the same at 43.429% when pulling 4989fc2e40e7c3929e50eb7c5f51805bbee7aa63 on meta-08-31-20-12-13-28 into c52916ea66c86e8b77846220ae40a8b47c1643f8 on master.


OpenSCDP

The OpenSCDP project [1] provides a wide range of development tools for smart card applications. It also has support for JavaCard and is what we use to develop our own commercial JavaCard applets.
The project under the GPL and source is available in our own git repo at the CDN.
Andreas
[1] https://www.openscdp.org/

Hi, I'm happy to include your project(s). We can include either whole project under single entry, but given the variety of tools and repositories you have, I think the better option would be to link these under several separate entries so we can be more specific about the tool functionality.
Can you please help me with the suggestions (ideally, pull request)? I think it shall fit under 'Applet build, upload and management section'

Hi Andreas (@CardContact), would it be possible to provide links to repos you would like to include? Happy to do the actual insertion into proper format into this list


Edit Formatting Errors PPP

Codecov Report

Merging #270 (f50b21d) into master (0a961c6) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #270   +/-   ##
=========================================
  Coverage     67.38%   67.38%
  Complexity      693      693
=========================================
  Files           122      122
  Lines          2330     2330
  Branches        275      275
=========================================
  Hits           1570     1570
  Misses          639      639
  Partials        121      121

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 0a961c6...f50b21d. Read the comment docs.


web3j-kyber web3j integration layer

I'm working currently on a web3 based integration layer for the Defi Kyber Network (similar to the web3j-quorum approach). Is that something which you would be interested to potentially make it available as a web3j-kyber module as part of web3j?

Will post the question in the main web3j project


What is the expected outcome of the installation?

Description
I installed XVim. Now when I restarted Xcode, it did ask me if it wants to load that bundle. I pressed yes. But I do not understand what is expected from a users perspective further. How am I supposed to use this product? There is literally no documentation stating how to toggle the XVim plugin. Post my installation, literally nothing changed in the source window.

Check Console while starting Xcode. There's very likely a message or two there to help us figure out what's going on. If all goes well, your source window should behave like vim (starts in command mode, can use hjkl to move cursor around, has a status bar on the bottom that says -- INSERT -- when in insert mode, etc.).


Running multiple workers on a single box

I know that this was possible while using PHP workers or Python workers, but running 2 Node workers on a single box seem to pick up the same job as it's requested. Do you have any examples of code on running the same worker multiple times on a single box?

I'm doing this:

fn that returns a new worker
loop with how many workers I and
push worker into array

Seems to work fine


Vim9: crash when dividing by zero in :def function

Describe the bug
In Vim9 script, dividing a number by zero in a :def function makes Vim crash.
To Reproduce
Run this shell command:
vim -Nu NONE -S <(cat <<'EOF'
    vim9
    def Func()
        eval 1 / 0
    enddef
    defcompile
EOF
)

Vim crashes.
Expected behavior
Vim doesn't crash.
Environment

Vim version: 8.2 Included patches: 1-2374
OS: Ubuntu 16.04.7 LTS
Terminal: xterm(363)

Additional context

backtrace
valgrind log
asan log

BTW, I think that in Vim script legacy, 1 / 0 could be used to get the highest number the running Vim binary could handle.  Not sure whether 1 / 0 should do the same in Vim9 script, or just raise an error...

BTW, I think that in Vim script legacy, 1 / 0 could be used to get the highest number the running Vim binary could handle.  Not sure whether 1 / 0 should do the same in Vim9 script, or just raise an error...

Not sure whether 1 / 0 should do the same in Vim9 script, or just raise an error...

Returning VARNUM_MIN or VARNUM_MAX doesn't make any sense, the code in num_divide implies this value is supposed to be NaN-ish but it's not. A (quiet) NaN poisons the whole chain of calculation it's in while an arbitrarily large integer is simply treated as a regular number, leaving the user wondering where the bug is.

1 / 0 could be used to get the highest number the running Vim binary could handle

If that's the only use case for this I'd simply add a v:maxintvalue and call it a day, there's no reason for Vim9 script not to throw an error here.

Not sure whether 1 / 0 should do the same in Vim9 script, or just raise an error...

Returning VARNUM_MIN or VARNUM_MAX doesn't make any sense, the code in num_divide implies this value is supposed to be NaN-ish but it's not. A (quiet) NaN poisons the whole chain of calculation it's in while an arbitrarily large integer is simply treated as a regular number, leaving the user wondering where the bug is.

1 / 0 could be used to get the highest number the running Vim binary could handle

If that's the only use case for this I'd simply add a v:maxintvalue and call it a day, there's no reason for Vim9 script not to throw an error here.

I agree, it seems a bit weird to not raise an error here, considering that Vim9 is stricter in other areas.  I think it would make sense to raise a runtime error.  I found this while refactoring an indent plugin, where the author used 1 / 0 to represent infinity in a number assignment:
function! s:SubmatchCount(lnum, pattern, ...)
        let endcol = a:0 >= 1 ? a:1 : 1 / 0
        ...
endfunction

I agree, it seems a bit weird to not raise an error here, considering that Vim9 is stricter in other areas.  I think it would make sense to raise a runtime error.  I found this while refactoring an indent plugin, where the author used 1 / 0 to represent infinity in a number assignment:
function! s:SubmatchCount(lnum, pattern, ...)
        let endcol = a:0 >= 1 ? a:1 : 1 / 0
        ...
endfunction

8.2.2378 has fixed the issue; now 1 / 0 correctly raises an error.
However, something is inconsistent:
vim9
def Func()
    var x = 1 / 0
    echo x
enddef
Func()

E1154: Divide by zero

vim9
var x = invalid
echo x

E121: Undefined variable: invalid
E121: Undefined variable: x

vim9
var x = 1 / 0
echo x

E1154: Divide by zero
9223372036854775807

Notice that in the last snippet, and only in that one, x is assigned a big number.
I think x should not be assigned anything, and echo x should raise E121.

8.2.2378 has fixed the issue; now 1 / 0 correctly raises an error.
However, something is inconsistent:
vim9
def Func()
    var x = 1 / 0
    echo x
enddef
Func()

E1154: Divide by zero

vim9
var x = invalid
echo x

E121: Undefined variable: invalid
E121: Undefined variable: x

vim9
var x = 1 / 0
echo x

E1154: Divide by zero
9223372036854775807

Notice that in the last snippet, and only in that one, x is assigned a big number.
I think x should not be assigned anything, and echo x should raise E121.

8.2.2378 has fixed the issue; now 1 / 0 correctly raises an error.
However, something is inconsistent:
vim9
def Func()
    var x = 1 / 0
    echo x
enddef
Func()

E1154: Divide by zero

vim9
var x = invalid
echo x

E121: Undefined variable: invalid
E121: Undefined variable: x

vim9
var x = 1 / 0
echo x

E1154: Divide by zero
9223372036854775807

Notice that in the last snippet, and only in that one, x is assigned
a big number.
I think x should not be assigned anything, and echo x should raise E121.

Yes, continuing after the error is not right.  It requires passing an
extra argument.
--
hundred-and-one symptoms of being an internet addict:
194. Your business cards contain your e-mail and home page address.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

8.2.2378 has fixed the issue; now 1 / 0 correctly raises an error.
However, something is inconsistent:
vim9
def Func()
    var x = 1 / 0
    echo x
enddef
Func()

E1154: Divide by zero

vim9
var x = invalid
echo x

E121: Undefined variable: invalid
E121: Undefined variable: x

vim9
var x = 1 / 0
echo x

E1154: Divide by zero
9223372036854775807

Notice that in the last snippet, and only in that one, x is assigned
a big number.
I think x should not be assigned anything, and echo x should raise E121.

Yes, continuing after the error is not right.  It requires passing an
extra argument.
--
hundred-and-one symptoms of being an internet addict:
194. Your business cards contain your e-mail and home page address.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


[DECISION-271] Deal with null fields in Avro serialization

:shipit:

Comment accepted. Will treat it ASAP

Squashing and checks in progress.


Issue/622

Changes:

Added "required" and "read-only" labels to items
Enforce validation for minLength and maxLength
Make validation feedback for minLength and maxLength more intuitive
Expose invalidItems and responseIsValid hooks from questionnaireResponseStore

Known bugs:

Upon initialisation of form, invalidItems is set to 0 and responseIsValid is set to true. They will only become accurate when the form is edited. Will fix soon.
For required boolean items, not interacting with the checkbox will result in no answer (as intended). However, if the intended answer is false, user would have to check and uncheck the checkbox to register an answer.
For required items with calculated expressions, if the calculated value is 0, the value doesn't change and its answer is therefore not registered. Eager to fix but don't see an obvious solution.

Future tasks:

Would be nice to have a validateQuestionnaire() function to trigger invalid fields to be highlighted as red.

Resolves #622.


Add_logging_to_fact_dimension_join

Issue number
DATA-1737
Expected behaviour
Logging required
Actual behaviour
No logging
Description of fix
Added Logging
Other info
Added line to changelog

Replaced by other pull request (#28)