Set host environment value as build args

fix #160

[x] Add module
[x] Implement
[ ] Update README

Pull Request Test Coverage Report for Build 996

23 of 31 (74.19%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.4%) to 90.999%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

domain/model/docker/types.go
4
6
66.67%

domain/model/docker/docker_impl.go
19
25
76.0%

Totals

Change from base Build 994:
-0.4%

Covered Lines:
1102

Relevant Lines:
1211

💛  - Coveralls


Android-Java: 1.4 Configuring AVD and Using Phone for the Same

Description ->
To Configure the AVD (Android Virtual Device) in Android Studio and to
Use our Smartphone for the same (if you are not having enough RAM on your device).

@Rohit-2602 Can I start work on this ?
As this is also important to know :)

@ananddasani  yes sure 😀

Please keep these steps in mind while creating a pull request:

Your Contributing file should be in this directory Android_Development/Java/ with the file name starting from 1.4 for instance 1.4 Configuring Android Virtual Device (AVD)
Note:- If you have multiple files to commit then add a tag at the beginning of your file name like 1.4.1, 1.4.2 etc
Create a new branch and push your PR on Android_Development_With_Java branch.
Pull request should contain only one commit
Note: If you have multiple commits then squash your commit.

Can I work on the documentation part on how to configure AVD in android studio?? @VikasPandey121

@KishkinJ10 It's already assigned to me.
You can start working on other issue :)

@ananddasani  can you please give a progress update about the issue and if you are facing any problem feel free to ask.

@VikasPandey121 assign me

Okay @LegendSumeet, I am assigning this issue to you.

@Rohit-2602 If no one is working on this issue I want to work on this issue please assign this to me manually
Saket Sagar
Batch-1
Documentation

Sure, I am assigning this issue to you. You can begin contributing to this issue.


Splunk entities group we are unable to filter only active entities using splunk app for infrastructure

Hi All,
kindly help to add only active entities in kubernetes splunk entities group setup
we are able to get all the entities such as active and inactive entities but our requirement is only to group active entities.
while trying to group the entities with status it is throwing error . Kindly help here to achieve the same.

Even i am facing the same issue not found any solution yet.

Hi @sharlin7 are you refering to an app's use of the data sent? Can you please provide more details as to whether you are referring to something you feel needs to be done at the collector side, or something you need from the Splunk query side...


Side by side

Get this working. It's a common use case for a drake developer.

Off the table for now.


Add Support for Importing Data into Comments

Have you considered adding support for importing data into your Comments plugin?
An example use case would be migrating ExpressionEngine comments into a Craft install that is using the Comments plugin for comments.
I noticed that you added an issue over in the Comments repo: https://github.com/engram-design/Comments/issues/63

This has now been implemented as part of the Feed Me Helpers repository. Download the commentshelper and install as a regular plugin.
Please also note you'll need the latest master of the comments plugin.


Add attribute protocol_version into default target group

what

Add attribute protocol_version to default target group

why

This attribute is mentioned in docs for lb_target_group https://registry.terraform.io/providers/hashicorp/aws/3.61.0/docs/resources/lb_target_group#protocol_version

Hi @ArtemKorchunov
This arg was added in v3.27.0 so we'll have to bump the minimum AWS provider version as well.

Hi @joe-niland. I see, so I am going to close this pr for now as I suspect that bumping up min version is not something that you would like to do for just one attribute. Correct?

Hi @ArtemKorchunov
Sorry, I was not clear.
It's fine to bump the provider (to an extent) because we'll also bump the version of this module so as not to break consumers' modules, assuming they've used version pinning.
I just meant you can make that change in versions.tf and then we can run the tests.

@joe-niland Sure thing, here it is.

/test all

Thanks for your contribution @ArtemKorchunov


Ban appeal

Just a couple of minutes ago I was banned from the server for swearing. Me and my friend were messing around with signs in our base/house.  I honestly thought I was still in our town chat because I wouldn't just say something like what I said in the global chat. I'm honestly sorry for not paying more attention to what chat I was talking in, and if you do decide to unban me I will make sure that never happens again. I also got banned for ban evading because I went on the server with my alt right after I was banned, I was asking about speaking to a mod and what I should do now my main account got banned. But before I got an answer I was banned instantly. I'm sorry for both things and hope you believe me and trust this will never ever happen again.

sorry, I forgot to add my IGN. It's Smeuner

You were ban evading, that's why your second account was banned. You could have easily simply checked the discord for information on how to appeal.
As for the original ban, you were caught by the autobanner for saying the word 'faggot', which is why it was an instant ban. This is a failsafe to prevent users to spam on first join. I will unban your main account in the coming 5 minutes. Please remember that some words, like that one, are filtered.


[nrf noup] subsys: ipc: workaround endpoint register thread deadlock

This change works around the issue with the semaphore timeout during the Bluetooth HCI driver initialization when the bt_enable function is called in the context of the System Workqueue thread. This issue only affects platform that use the IPC service and its ICBMsg backend (e.g. the nRF54H20 DK target).
The bt_enable function, when called in the System Workqueue context, results in a deadlock, as the waiting semaphore of the Bluetooth HCI driver times out:
bt_hci_driver: Endpoint binding failed with -11
During the Bluetooth HCI driver open operation in the context of the bt_enable function, the driver code waits using the semaphore for the endpoint binding process of the IPC service module to finalize. The issue occurs when the waiting occurs in the System Workqueue context. The ICBMsg backend from the IPC service schedules a system work during the endpoint registration, in which it finalizes the binding operation

also in the System Workqueue context. As the Bluetooth HCI driver with its wait operation keeps the System Workqueue context busy, the endpoint binding cannot be completed by the ICBMsg backend before the HCI driver semaphore timeout.

This change is a temporary workaround solution to streamline the development of applications for the nRF54H20 DK target that use the App Event Manager module and operate in the System Workqueue context (e.g. nRF Desktop application). The proper solution is planned for the Bluetooth initialization process that will replace the current workaround.
Ticket for a more long-term solution:
https://nordicsemi.atlassian.net/browse/NCSDK-27318

This is acceptable as temporary solution. The long therm solution requires reusing dedicated work queue from the ICMsg module. I will implement it later in the upstream Zephyr.

Great, please make sure to revert this change when you bring the proper solution upstream (to NCS)

why not fromlist?

Upstream PR is available here:
https://github.com/zephyrproject-rtos/zephyr/pull/72377

This is acceptable as temporary solution. The long therm solution requires reusing dedicated work queue from the ICMsg module. I will implement it later in the upstream Zephyr.

I don't think the ICMsg module should expose workqueues. It's not the responsibility of the ICMsg module. ICMsg should be about passing messages between processors.
If we want to have a shared IPC workqueue, we should extract it from ICMsg and create a new module like ipc_workqueue or icmsg_workqueue used by both ICMsg and icbmsg, and potentially other IPC users. We would need to clearly define when blocking of this workqueue is permitted to avoid deadlocks like the one being fixed here.

I don't think the ICMsg module should expose workqueues. It's not the responsibility of the ICMsg module. ICMsg should be about passing messages between processors. If we want to have a shared IPC workqueue, we should extract it from ICMsg and create a new module like ipc_workqueue or icmsg_workqueue used by both ICMsg and icbmsg, and potentially other IPC users. We would need to clearly define when blocking of this workqueue is permitted to avoid deadlocks like the one being fixed here.

I agree that taking work queue into some common module is the best approach. Looking at the current implementation of ICMsg and ICBMsg, we should assume that this new shared work queue cannot be blocked.
With that assumption in mind, the "bounded" callback of ipc_service becomes problematic. If we call it from our new work queue, we must clearly state that user cannot block in the "bounded" callback of ipc_service. If we redirect the callback to system work queue, we will end up with the same dead lock, because "bounded" callback from ipc_hci cannot be called from system work queue as kapi-no pointed out at the beginning of this PR.


[c++] Implement DynamicThreadPool in-terms-of event engine

This looks probably fine, given that the default EventEngine uses an auto-scaling thread pool at the moment. It might be worth watching performance metrics when this change is landed. LGTM once the test failures are addressed.


rclone: 1.47.0 -> 1.48.0

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

nix-review pr 63524 passed
changes LGTM :+1:

@GrahamcOfBorg test rclone
@GrahamcOfBorg test nextcloud

@GrahamcOfBorg build rclone

@GrahamcOfBorg test nextcloud.basic

Thanks!  (sorry about the noise)


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-25-main" workflow

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

Questions ?
Please refer to the Backport tool documentation


Remove tests for databases other than postgres

Describe the bug
As we will be going with postgres, we can remove tests for mysql and sqlite from the tests.yml under github workflow.

This should be part of https://github.com/fossasia/eventyay-tickets/issues/29


Finalise book categories.

We need to finalize the categories for all the books we have in our library.

@abhi1203 @PrateekNarang can you give your suggestions for categories.

@pankaj-ag I believe this is complete. Please confirm (and close).

I was waiting for Prateek to test, but I think we close this one and open a new issue if something came up later.


FATA[0003] failed to initialize project with version "3-alpha": exit status 2

Bug Report
What I am expecting:
operator-sdk init --domain=example.com --repo=github.com/example/memcached-operator
Writing scaffold for you to edit...
Get controller runtime:
$ go get<EMAIL_ADDRESS>Update go.mod:
$ go mod tidy
Running make:
$ make
go: creating new go.mod: module tmp
go: found sigs.k8s.io/controller-tools/cmd/controller-gen in sigs.k8s.io/controller-tools v0.3.0
/home/sadique/go/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..."
go fmt ./...
go vet ./...
go build -o bin/manager main.go
Next: define a resource with:
What i am getting:
operator-sdk init --domain=example.com --repo=github.com/example/memcached-operator
Writing scaffold for you to edit...
Get controller runtime:
$ go get<EMAIL_ADDRESS>Update go.mod:
$ go mod tidy
Running make:
$ make
go: creating new go.mod: module tmp
go: found sigs.k8s.io/controller-tools/cmd/controller-gen in sigs.k8s.io/controller-tools v0.3.0
/home/devraj/go/bin/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..."
go fmt ./...
go vet ./...
runtime/cgo
cgo: exec gcc: exec: "gcc": executable file not found in $PATH
Makefile:51: recipe for target 'vet' failed
make: *** [vet] Error 2
Error: failed to initialize project with version "3-alpha": exit status 2
Usage:
operator-sdk init [flags]
Examples:
Scaffold a project using the apache2 license with "The Kubernetes authors" as owners
operator-sdk init --project-version=2 --domain example.org --license apache2 --owner "The Kubernetes authors".

Try this GOPROXY=https://proxy.golang.com,direct and GOPROXY=direct

Sounds like a go environment problem. Regardless, the init command no longer runs make (in the next release).

Sounds like a go environment problem. Regardless, the init command no longer runs make (in the next release).

What can i do to solve the environment issue because i did what i can.

Sounds like a go environment problem. Regardless, the init command no longer runs make (in the next release).

But it's working fine for me and we have the same environment.


Fix bug in slicing into container adapter

This bug was found at SasView Contributor Camp while trying to integrate Tiled with the sasdata loader.
The first commit reproduces the error by extending an existing test:
E           TypeError: unsupported operand type(s) for +: 'int' and 'NoneType'

It also adds a new test, which does not exercise the bug, but nonetheless adds useful coverage to this general area of functionality.
The second commit fixes the bug.

Merging this to un-block some export work, but any post-merge review is still welcome!


feat: HashMap.toList_map_fst

This PR adds the lemma toList_map_fst : m.toList.map Sigma.fst = m.keys for m a (raw or standard) DHashMap, and the same theorem but with Prod.fst for (raw or standard) HashMap.

From my understanding you would have to do the following based on what is written in Internal.Defs

* `toList_map_fst` in `DHashMap/Internal/RawLemmas` should presumable be using `simp_to_model`, but I don't understand how to make that work

simp_to_model needs to know how m.1.keys and m.1.toList look on lists like length_keys_eq_length_keys in Internal.WF.
Probably like: m.keys = List.Keys (toListModel m)and m.toList = toListModel m
After proving that you would need to add them to queryNames in Internal.Raw and add (h: m.1.WF) to your theorem. Then you should be able to use simp_to_model.

* `toList_inner` in `HashMap/RawLemmas` and `HashMap/Lemmas` is brute force. How can I avoid proving this twice? How am I meant to structure this?

You have to prove the result for toList and const.toList in Raw0 and afterwards you use these results directly in all other classes.

@jt0202, thanks for your explanation. Along with some advice from Markus I think I understand better. Would you mind taking a look at this version?


BIA-809 Update SchoolDim view and test data

This PR addresses the issues that were found when previously looking at the SchoolDim view when the Postgres tests were added and they showed that there was not enough data present to properly test out that the different conditions in the view were actually being met.
What ended up being done was:

Add an additional EdOrg and related address data for testing, along with a new test to test out the filtering that should be done on this EdOrg Address
Update the join between edfi.EducationOrganizationAddress and edfi.EducationOrganizationAddressPeriod  to include the missing column EducationOrganizationId . Without this part of the join, it was causing duplicate records to show up when they did not exist, often leading to incorrect data being presented in the SchoolAddress part of the statement.
A test that was named for not having an end date was renamed, since the data it was asserting on had an end date.

After the initial work for this was submitted, additional data changes were made to remove extra address/addressperiods for an EdOrg and add missing AddressPeriods for an EdOrg that was causing tests to pass/fail inconsistently, due to the top 1 used in the OUTER APPLY part of this view that would pull one or the other address. These changes were only made in DS32 and  Postgres since the extra addresses were only added there, and not in DS31 or DS2.

I found a couple of scenarios not covered in our tests:

For DS 3.1, DS 3.2 and postgres, when I comment out the first condition of this join, no tests fail.

INNER JOIN edfi.EducationOrganizationAddressPeriod

And then the same on this clause:

AND DescriptorConstant.ConstantName = 'Address.Physical'

I did the same deep testing for DS 2, but it looks good.


Check Create Child

Create child has some issues with address and it is unable to create a child.

Story link
#20 Story

Done under https://github.com/ita-social-projects/OoS-Backend/pull/150


Token not being sent in AJAX requests

Hi guys,
I recently updated my Ember app from Ember 1.13.13 to Ember 2.18.2, with<EMAIL_ADDRESS>and<EMAIL_ADDRESS>I use JWT for authentication.
My app does not use Ember Data & Ember Data models. We have a lib called api.js that makes AJAX requests to our API. This is a sample of the implementation of the call:
// api.js
return $.ajax({
   url: `${API_ENDPOINT}${url}`,
   type: method, // POST, GET, PUT, DELETE
   contentType: 'application/json',
   dataType: 'json',
   data: JSON.stringify(params),
   xhr() {
	const xhr = $.ajaxSettings.xhr();
	// [...] Some code for upload requests
	return xhr;
   }
})

Note: This lib is just an object with some methods imported in routes, controllers, etc. It is not an Ember service or something like (one of the next steps after the migration to Ember 2.18.2 is transform this lib into a service).
ember-simple-auth and ember-simple-auth-token configuration in environment.js:
{
        'ember-simple-auth': {
		store: 'session-store:local-storage',
		authorizer: 'authorizer:token',
		crossOriginWhitelist: ['*']
	},
	'ember-simple-auth-token': {
		refreshAccessTokens: true,
		timeFactor: 1000,
		tokenPropertyName: 'token',
		refreshTokenPropertyName: 'token',
		refreshLeeway: 300,
		tokenExpireName: 'exp',
		serverTokenEndpoint: ENV.API_HOST + '/' + ENV.API_NAMESPACE + '/users/login',
		serverTokenRefreshEndpoint: ENV.API_HOST + '/' + ENV.API_NAMESPACE + '/users/login/refresh',
		identificationField: 'user_name',
		passwordField: 'password',
		authorizationPrefix: 'Bearer ',
		authorizationHeaderName: 'Authorization',
		headers: {}
	}
}

Before I updated Ember and auth packages, the header Authorization: Bearer [token] was automatically injected into all authenticated requests. After the update, only the login request works correctly, and all requests after it were not sending the Authorization header.
I read in the ember-simple-auth README that authorization will not happen automatically for all requests the application issues anymore. So i looked for alternatives to work around this problem on the internet and read a suggestion to use Authorizers. But ember-simple-auth is deprecating Authorizers. So i found here a suggestion to extend the application adapter from DataAdapterMixin, and defining the property authorizer: 'authorizer:token'. Here's my application adapter:
// app/adapters/application.js
import DS from 'ember-data';
import DataAdapterMixin from 'ember-simple-auth/mixins/data-adapter-mixin';
import config from '../../config/environment';

export default DS.JSONAPIAdapter.extend(DataAdapterMixin, {

	authorizer: 'authorizer:token',

	host: config.API_HOST,

	namespace: config.API_NAMESPACE,

	shouldReloadAll() {

		return true;
	}
});

Apparently correct but still not working. It's as if Ember did not use this adapter to make the requests.
My solution: I changed my api lib to add the header Authorization: Bearer [token] into the ajax options if the user is authenticated. It worked.
My problem: When ember-simple-auth-token calls the API to refresh token, the Authorization header is not being sent, causing the user's session to be invalidated when attempting to update the token.
Any ideas? I've been breaking my head a few days ago to try to solve this.
Thanks.

@jzcorrea You can overwrite the refreshAccessToken method to get the behavior you desire:
import { merge } from '@ember/polyfills';
import JWT from 'ember-simple-auth-token/authenticators/jwt';

export default JWT.extend({
  refreshAccessToken(token) {
    return new Promise((resolve, reject) => {
      const headers = merge(this.headers, {
        'Authorization': `Bearer ${token}`
      });
      this.makeRequest(this.serverTokenRefreshEndpoint, {}, headers).then(response => {
        try {
          const sessionData = this.handleAuthResponse(response);
          this.trigger('sessionDataUpdated', sessionData);
          return resolve(sessionData);
        } catch (error) {
          return reject(error);
        }
      }).catch(error => {
        this.handleTokenRefreshFail(error.status);
        return reject(error);
      });
    });
  }
});

@fenichelar Thanks! I'll do this as soon as I upgrade to version 4.0.1. :call_me_hand:


What does concurrency mean in context of multiple servers? And what does watchStuckJobs do?

If I run Kue on multiple servers all connected to the same Redis instance, what does the concurrency value mean? Let's say I have 2 servers, and I run queue.process('email', 20, function(job, done){...}) on each server. Does that mean each server will handle 20 jobs, for a total of 40? I'm thinking with the use of BLPOP that this is correct.
Let's say, to make sure I'm clear, that one server's code has concurrency set to 20, and another at 30. Does that mean there's a total of 50 jobs running at a time? Because another theory my teammates and I had was that it would basically use the max between the concurrency numbers, so in this example, 30 total.

Would you be willing to explain what queue.watchStuckJobs(interval) does? I see it issue some huge command to Redis that I don't understand.

Let's say, to make sure I'm clear, that one server's code has concurrency set to 20, and another at 30. Does that mean there's a total of 50 jobs running at a time?

Exactly.

Would you be willing to explain what queue.watchStuckJobs(interval) does? I see it issue some huge command to Redis that I don't understand

It was trying to fix a race-condition bug inside kue, however this is deprecated now


docs(firebase_core): fix link to new docs in the banner of the old docs

Description
https://user-images.githubusercontent.com/24459435/169665246-6c002e65-a3f0-4e3a-b106-35ed48726b82.mov
Related Issues
Closes #8730
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Should I apply the suggest changes?

https://github.com/firebase/flutterfire/runs/6597244911?check_suite_focus=true
Looks a bit odd 🤔

Oh, no, ignore that and I'll fix it in a followup.


[Dark] Selected text is invisible

Describe the bug
The selected text is invisible
To Reproduce
Steps to reproduce the behavior:

Open any project
Try to search for some value
Select the text in any input

Screenshots

Application:
WebStorm  2022.1

Can you try the latest and see if that fixes the issue: https://plugins.jetbrains.com/plugin/14799-atom-one-theme/versions/stable/173510

@espositocode seems to be fine now. Thanks!


Customer dashboard « forgotten password » feature do not work.

Customer dashboard « forgotten password » issue
On our tested page: https://blog.lesieur.name/espace-membres/
When you click on « Customer dashboard », you click on « J'ai oublié mon mot de passe », you field input with «<EMAIL_ADDRESS>» or «<EMAIL_ADDRESS>», you click on « OK » button : nothing will be produce, and no email will be send. In the console.log you will see :

In this example I clicked twice time on « OK » button.
Try to reset the Template email to first configuration
We have not change the Template Email for « FORGOT PASSWORD » but we have tested to reset it to see if that solve the issue. In back-office, page https://app.snipcart.com/dashboard/email-templates, part « FORGOT PASSWORD » we have clicked on « EDIT » button, then on next page, we have clicked on « RESTORE DEFAULT » button and then, we have clicked on « SAVE & EXIT » button.
After new test, we have always the same issue.
We use the french fr.js file : https://blog.lesieur.name/espace-membres/
More details here with another bug : https://github.com/snipcart/snipcart-localization/issues/54

Thanks for the report.
A recent change in the handling of default email templates introduced the bug, it has been fixed.

Tested and all is good now. Thx.


Cannot find module './technical-preview-badge.svg?sprite' from<EMAIL_ADDRESS>

While writing unit test I am getting this error . I am using following packages
"@bentley/ui-abstract": "^2.18.4",
"@bentley/ui-components": "^2.19.6",
"@bentley/ui-core": "^2.19.6",

See setup-test.js entry that is used to avoid this issue in unit tests.


Some fixes and improvements

This looks very good, the additions are nice and the improvements were very much needed 👍
I am not going to test this extensively (haven't done much c#/osu! related in a while) so as far as I am concerned, this looks good to merge.
Just to make sure, is this PR finished? Just give me a heads up and I'll go ahead and merge.

I am not going to test this extensively (haven't done much c#/osu! related in a while) so as far as I am concerned, this looks good to merge.

I have tested repositories manually, got expected results and nothing crashed.

Just to make sure, is this PR finished?

Yes, this PR is finished, i have nothing to add to it at least in near future.

Merged, thanks a lot! h:smile:


Make control connections more persistent

topology: make control connection more persistent
After this series, trying to read topology metadata does
not ever end on its own - instead, the function retries
in an infinite loop. It's the caller's responsibility to
eventually stop waiting and abort - right now it is done
after 60 seconds (our hardcoded refresh period), but we
should also consider making it configurable.
Fixes #398
Tested manually by providing bogus known addresses and observing logs.

[x] I have split my patch into logically separate commits.
[x] All commit messages clearly explain what they change and why.
[ ] I added relevant tests for new features and bug fixes.
[x] All commits compile, pass static checks and pass test.
[x] PR description sums up the changes and reasons why they should be introduced.
[x] I added appropriate Fixes: annotations to PR description.

I'm closing it for now as invalid - if we ever have issues with control connections dying too eagerly, we can revisit the idea.


Track source as fileuri when reporting dependencies

Currently we don't point to where the dependencies are coming from, which could be a useful piece of information. We should track and report that. We should also change the Location field in the dependency.Dep to match Location in the rest of the code base (ie it should point somewhere in the codebase) and find a different term to report what it currently gathers for java (or add it to an extras field for arbitrary metadata)

@fabianvf Did you just mean pointing to where the dependency is declared (pom.xml, go.mod) or you meant where it's actually used?

Where it's declared

Location can be renamed to Type maybe?


Update ViewportTexture path relative to its local scene instead of the Viewport owner

Currently, ViewportTexture::_setup_local_to_scene retrieves the Viewport a ViewportTexture points to like this:
Node *vpn = p_loc_scene->get_node_or_null(path);

That is, the path stored within the ViewportTexture is assumed to be relative to its local scene.
But in the function Viewport::_update_viewport_path, which is used to maintain a valid path, the path is set relative to the owner of the Viewport. The local scene of the ViewportTexture and the owner of the Viewport don't have to be the same. This is for example the case if the owner of the Viewport is an editable instance (editable_children enabled).
This PR fixes the behaviour of Viewport::_update_viewport_path and updates the path to be relative to the local scene. Please note, that while the behaviour is correct now, Viewport::_update_viewport_path is still not always called when it needs to be. One example is when you instantiate a scene that contains a ViewportTexture and enable editable_children on it. The path should be updated now but it isn't. It will be wrong until you either set it manually again or cause Viewport::_update_viewport_path to be called.
This fix is crucial because if you suffer from this issue, the ViewportTexture path will be set invalid whenever you open the scene that contains the ViewportTexture and you have to reassign the ViewportTexture path whenever that happens...
Partly fixes:
https://github.com/godotengine/godot/issues/96816
https://github.com/godotengine/godot/issues/87809
https://github.com/godotengine/godot/issues/74331 (This is a very generic issue. ViewportTexture has so many issues, that it is difficult to know which one this is about)

Fixes #98117


Problems with receiving messages

Receiving messages works right after initialization.
When restarting the app and receiving a message after that it doesn't work anymore. In the logs I can see the Android code is definitely called.
When the app is in background or closed, receiving a message also doesn't work (same as above with receiving on the Android side).
Maybe these  are actually the same problem, I suspect the callback is just never called for some reason.
I tried the embedded FOSS FCM and nfty distributors, both have the same problem and from the logs I collected I'm very confident this problem is distributor independent.
I will try to investigate it a little bit and see if adapting stuff from https://github.com/firebase/flutterfire/blob/master/packages/firebase_messaging/firebase_messaging/android/src/main/java/io/flutter/plugins/firebase/messaging/FlutterFirebaseMessagingBackgroundService.java helps.

Hey👋
I'm really excited to see a Nextcloud w/ UP app. I will try to look at what might be going wrong today/tmrw.
(I'm sure @p1gp1g's android expertise will be helpful if they have time to look too)

I'm pretty sure something like https://github.com/OneSignal/OneSignal-Flutter-SDK/pull/464 is needed for this to work. Afaict most of that code is copied from https://github.com/firebase/flutterfire/tree/master/packages/firebase_messaging/firebase_messaging/android/src/main/java/io/flutter/plugins/firebase/messaging.
So how can we coordinate this? I can put some time into implementing this, but I don't want to do the work if someone else is already working on it. If you want to fix it then do it, because then I can continue working on other stuff for the notifications in the app.

I did some small refactoring and now at least the notifications work on subsequent runs. Background still not working.

FluffyChat also uses UP, so maybe I can check what they are doing, because I guess that works.

What tests did you do ? Because the example (and fluffychat) definitely work in background and/or closed ?

What do you mean with tests? My implementation just doesn't work. I didn't try the examples yet, because as I said in the second comment I don't want to duplicate efforts if someone is already working on it. I will check the examples now.

LOL example works in background. Then I'm pretty sure I know what is wrong. The documentation just doesn't help a lot. I'll make a PR towards it to fix it.

I though you did some tests with the example and you had trouble to receive message with the app in background or closed.
PR to improve our doc are very welcomed :)

Somehow I now don't receive the messages at all already on the Android side (looking at the logs). Message definitely arrives at the distributor.

I just always get GCM     : broadcast intent callback: result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE pkg=de.provokateurin.harbour (has extras) } in the logs. That it is cancelled seems to be the problem.

Yes I'm trying the foss distributor. I can temporarily switch to the non-foss, but I need to use the foss one to publish on f-droid. I don't think the non-foss will help though, because I have the same problem when using nfty. I'll try anyway.

Tried the same with the non-foss distributor. I don't think any of this is related to the distributor that is used.

You should try with ntfy then. I don't know if the GCM message is related to your problem but it is definitely dependent on Google Services.
Do not forget to wipe data of your app sometime, there might be using introduced in development, not wiped after code changes.
I can give a look at your code if it can help. You must receive notifications in background :)

ntfy also doesn't work in the background

i kinda suspect another plugin is making problem at this point

i'll just add all the plugins with native android code to the example app and see if it breaks.

adding the plugins didn't break it.
with nfty i get this log and nothing after that:
07-18 20:51:19.759  5631  5653 D NtfyUpDistributor: Sending MESSAGE to de.provokateurin.harbour (token=836ca154-e396-4785-8a36-02e99a793ed0): {"subject":"ppOeSO5z5ok6/44urMYGRue1ZbwgbnAGkGqIM4S0LpWRSpXCYmFEfvx6+qirYAuBvffos9h9paZXIxO0vbEG22f3ec/T1tY7ndZQh7D+Zqq81Kc/YI2diAzGffXX7Q9hpFlaF51rgHzzYP4lsQwFGkFdh+pUEBIgf9OydBiEokt+kWX3LzABIOECVL1jeR2vLiaf8chDbl/EBw0idGhvO2567pDMkU8URUAPCCvzR1gLLDuEKk06bqWFIaoVDfxnhYULntXsIkGGIXRDc01AF6Au6mGfga1RcAVsZ35rJiiicDjnkZrtN48vU6jGYbpYlXbRRkvOgh7Xxg8chAaENw==","signature":"Lj3+J6OtbGjRIRaQHisWMAZz3k7dTkWHD04bVZpeGZMf6X5vNGbK/tJvZKVjf2ZNdFZsCOEdnszQd+Km73dQxonC6ChMVfb8+Cgci3hEDnKR29LN4XG8R+ilL6fsSI74Pp2WWQAXVAC4eehWLATnuM925se4RvMP5cOoEQUUvDvTlM+heXONrYHRAkzmoCPp4CThD2wUkX2bdbhQnWtvLsxrkwObf8LdKu6WjKcza0LbabIvpg3vDhx7zSBwnUN82Q10OW0EN/iwiTb0aNtunIryAdBje5+mzj/D0NpHlykeC3I3WbmN41LQnuzJAzjOd5Ie8gOB0y5ngDyg0Wz5GA==","priority":"normal","type":"alert"} (752 bytes)}

so i think the broadcast intent is never received. idk why this happens now and used to work before.

Can you set a breakpoint around there https://github.com/UnifiedPush/android-connector/blob/main/connector/src/main/java/org/unifiedpush/android/connector/MessagingReceiver.kt#L19 ? And/or check your shared pref

removing all plugins from my app also doesn't fix it.
i'm kind of out of ideas what it could be tbh.

I don't know, I haven't seen your code. Maybe you could share it so I can check that. Did you do any change android side ?

The code is in the MR linked at the top. I have some local changes. I'll try on last time and then you can take a look.

I pushed the code. Hopefully you can find something. I just recreated the android folder from scratch and added my changes on top, but also no luck.

You don't need to look at all the changes. packages/harbour/ is the app. All the other changes are related to forwarding push messages from Nextcloud and so on.

Can you set a breakpoint around there https://github.com/UnifiedPush/android-connector/blob/main/connector/src/main/java/org/unifiedpush/android/connector/MessagingReceiver.kt#L19 ? And/or check your shared pref

How can I do that? I don't even know how to include the connector from local sources.

sorry for being so annoying, this is probably the worst bug i ever had because it doesn't make any sense :see_no_evil:

No problem, I'll try your code to check that soon ! :)

i tried adding the android-connector from local sources, but just can't get it working :(

my time of developing native android apps and fiddeling with java and kotlin is just too long ago. i need help from someone with more expertise in that field

@p1gp1g did you have a chance to look at my code? i tried some other stuff, but nothing helped at all

So I gradually add the code again and I got it working now. Really no clue what was wrong. I'll push my code later when I got it all working.

It works pretty well now that it's reliable :D

wow it's broken again. what i noticed is that i can close the app in release mode and the notifications still arrive as long as i don't stop the flutter run command. in the app settings i can see the app is not running in the background as it should:

when i now open the app again and close it, i receive the notifications and also can press the force stop button. so is suspect this is something with the broadcast receiver getting killed for some reason.

so i think flutter run just kills the app completely instead of only closing the visible window. that would explain why the app isn't even running in the background. that would mean there is no issue with UP at all, just bad DX from flutter.

So if you build a (non debug) apk, it works fine?

when i now open the app again and close it, i receive the notifications and also can press the force stop button. so is suspect this is something with the broadcast receiver getting killed for some reason.
that would mean there is no issue with UP at all, just bad DX from flutter.

That's great to hear!
We should document this somewhere. I'll test this with other apps and create an FAQ section on the Flutter page on the website if this keeps on happening (weird that I never noticed it, but I guess when testing I leave the app open longer than I keep flutter run running usually)

i've fully integrated the notifications in my app now. no more issues so far other than the one i discovered. expect the feature to land in the app very soon!


[MLLIB] Change x_i to y_i in Variance's user guide

Variance is calculated on labels/responses.

Test build #27885 has started for   PR 4740 at commit 673317b.

This patch merges cleanly.

+1

Test build #27885 has finished for   PR 4740 at commit 673317b.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class CheckAnalysis

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/27885/
Test PASSed.

Merged into master and branch-1.3.


Release of version <IP_ADDRESS> of SqlServerDsc

Releasing version <IP_ADDRESS>

This change is

Codecov Report

Merging #1286 into master will decrease coverage by <1%.
The diff coverage is 92%.

@@           Coverage Diff           @@
##           master   #1286    +/-   ##
=======================================
- Coverage      98%     97%    -1%
=======================================
  Files          34      35     +1
  Lines        4171    4323   +152
=======================================
+ Hits         4111    4220   +109
- Misses         60     103    +43


BayesDB falls over when passed some really tiny values

It results in a NaN logscore.  Most tiny values are OK, so it may be a cancellation or roundoff error.
E.g.
from bayeslite.bayesdb import bayesdb_open
bdb = bayesdb_open()
bdb.sql_execute('CREATE TABLE D (c float)')
bdb.sql_execute('INSERT INTO D (c) VALUES (-1.0010415476e-146)')
# bdb.sql_execute('INSERT INTO D (c) VALUES (0)')
bdb.execute('CREATE GENERATOR D_cc FOR D USING crosscat("c" numerical)')
bdb.execute('INITIALIZE 1 MODELS for D_cc')
bdb.execute('ANALYZE D_cc FOR 1 ITERATIONS WAIT')

Results in
---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)
<ipython-input-168-ba232d0a75d6> in <module>()
----> 1 import codecs, os;__pyfile = codecs.open('''/var/folders/8w/h52wthts2gl7kn2sx3g5nql00000gn/T/py614324xn''', encoding='''utf-8''');__code = __pyfile.read().encode('''utf-8''');__pyfile.close();os.remove('''/var/folders/8w/h52wthts2gl7kn2sx3g5nql00000gn/T/py614324xn''');exec(compile(__code, '''/tmp/tst.py''', 'exec'));

/tmp/tst.py in <module>()
      6 bdb.execute('CREATE GENERATOR D_cc FOR D USING crosscat("c" numerical)')
      7 bdb.execute('INITIALIZE 1 MODELS for D_cc')
----> 8 bdb.execute('ANALYZE D_cc FOR 1 ITERATIONS WAIT')

/Users/alx/Google Drive/alien/probcomp/bayeslite/bayeslite/bayesdb.py in execute(self, string, bindings)
    220             bindings = ()
    221         return self._maybe_trace(
--> 222             self.tracer, self._do_execute, string, bindings)
    223
    224     def _maybe_trace(self, tracer, meth, string, bindings):

/Users/alx/Google Drive/alien/probcomp/bayeslite/bayeslite/bayesdb.py in _maybe_trace(self, tracer, meth, string, bindings)
    228         if tracer:
    229             tracer(string, bindings)
--> 230         return meth(string, bindings)
    231
    232     def _qid(self):

/Users/alx/Google Drive/alien/probcomp/bayeslite/bayeslite/bayesdb.py in _do_execute(self, string, bindings)
    269         else:
    270             raise ValueError('>1 phrase in string')
--> 271         cursor = bql.execute_phrase(self, phrase, bindings)
    272         return self._empty_cursor if cursor is None else cursor
    273

/Users/alx/Google Drive/alien/probcomp/bayeslite/bayeslite/bql.py in execute_phrase(bdb, phrase, bindings)
    464             max_seconds=phrase.seconds,
    465             ckpt_iterations=phrase.ckpt_iterations,
--> 466             ckpt_seconds=phrase.ckpt_seconds)
    467         return empty_cursor(bdb)
    468

/Users/alx/Google Drive/alien/probcomp/bayeslite/bayeslite/metamodels/crosscat.py in analyze_models(self, bdb, generator_id, modelnos, iterations, max_seconds, ckpt_iterations, ckpt_seconds)
   1036                     assert diagnostics['logscore'][-1][i] is not None
   1037                     assert not math.isnan(diagnostics['logscore'][-1][i]), \
-> 1038                         'bad X_L before %r after %r' % (X_L, X_L_list_0[i])
   1039                     assert 0 < len(diagnostics['num_views'])
   1040                     assert 0 < len(diagnostics['column_crp_alpha'])

AssertionError: bad X_L before {'column_partition': {'assignments': [0], 'counts': [1], 'hypers': {'alpha': 1.0}}, 'column_hypers': [{'mu': -1.0010415476e-146, 's': 2.2250738585072014e-308, 'r': 1.0, 'fixed': 0.0, 'nu': 1.0}], 'view_state': [{'column_component_suffstats': [[{'sum_x': -1.0010415476e-146, 'sum_x_squared': 1.0020841800214032e-292, 'N': 1.0}]], 'row_partition_model': {'counts': [1], 'hypers': {'alpha': 1.0}}, 'column_names': [u'c']}]} after {u'column_partition': {u'assignments': [0], u'counts': [1], u'hypers': {u'alpha': 1.0}}, u'column_hypers': [{u'mu': -1.0010415476e-146, u's': 2.2250738585072014e-308, u'r': 1.0, u'nu': 1.0, u'fixed': 0.0}], u'view_state': [{u'column_component_suffstats': [[{u'sum_x': -1.0010415476e-146, u'sum_x_squared': 1.0020841800214032e-292, u'N': 1.0}]], u'row_partition_model': {u'counts': [1], u'hypers': {u'alpha': 1.0}}, u'column_names': [u'c']}]}

What else did you try to conclude that 'most tiny values are OK'?
This setup satisfies the hypotheses of https://github.com/probcomp/crosscat/issues/85.

The following script records 46 failures out of 200 experiments:
import pylab
pylab.ion()
from bayeslite.bayesdb import bayesdb_open
bad = []
for i in pylab.arange(.999, 1.001, 0.00001):
    print i
    try:
        bdb = bayesdb_open()
        bdb.sql_execute('CREATE TABLE D (c float)')
        bdb.sql_execute('INSERT INTO D (c) VALUES (%g)' % (-1.0010415476e-146*i))
        # bdb.sql_execute('INSERT INTO D (c) VALUES (0)')
        bdb.execute('CREATE GENERATOR D_cc FOR D USING crosscat("c" numerical)')
        bdb.execute('INITIALIZE 1 MODELS for D_cc')
        bdb.execute('ANALYZE D_cc FOR 1 ITERATIONS WAIT')
    except AssertionError, e:
        assert any('bad X_L before' in a for a in e.args)
        bad.append(i*-1.0010415476e-146)

pylab.hist(bad, bins=100)
pylab.show()

@alxempirical You have an insert 0 commented out, which would nix the bug 85 connection. Can you give us a little more history on that?

The test does not fail if you insert a single 0 into the table (as opposed
to some of the other values), that's all.
The possible connection to #85 is unclear to me, as the sufficient
statistics are nonzero, according to the AssertionError reports.
Best,
Alex
On Tue, Mar 29, 2016 at 9:48 AM, Gregory Marton<EMAIL_ADDRESS>wrote:

@alxempirical https://github.com/alxempirical You have an insert 0
commented out, which would nix the bug 85 connection. Can you give us a
little more history on that?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/probcomp/bayeslite/issues/388#issuecomment-202900883

The values don't have to be particularly tiny after all.  The example also fails with -0.00114661120796

And for larger values, they all fail.

Here is an example with two values inserted into the table.
bdb.sql_execute('INSERT INTO D (c) VALUES<PHONE_NUMBER>.4),<PHONE_NUMBER>.25)')

Failure is
AssertionError: bad X_L before {'column_partition': {'assignments': [0], 'counts': [1], 'hypers': {'alpha': 1.0}}, 'column_hypers': [{'mu':<PHONE_NUMBER>.0783334, 's': 7423.711238379478, 'r': 0.5484124898473131, 'fixed': 0.0, 'nu': 2.0}], 'view_state': [{'column_component_suffstats': [[{'sum_x':<PHONE_NUMBER>.25, 'sum_x_squared': 8.718957972462767e+18, 'N': 1.0}, {'sum_x':<PHONE_NUMBER>.4, 'sum_x_squared': 8.718957252868305e+18, 'N': 1.0}]], 'row_partition_model': {'counts': [1, 1], 'hypers': {'alpha': 1.2030250360821166}}, 'column_names': [u'c']}]} after {u'column_partition': {u'assignments': [0], u'counts': [1], u'hypers': {u'alpha': 1.0}}, u'column_hypers': [{u'mu':<PHONE_NUMBER>.5233335, u's': 3445.7815188027907, u'r': 0.6299605249474366, u'nu': 1.2311444133449163, u'fixed': 0.0}], u'view_state': [{u'column_component_suffstats': [[{u'sum_x':<PHONE_NUMBER>.25, u'sum_x_squared': 8.718957972462767e+18, u'N': 1.0}, {u'sum_x':<PHONE_NUMBER>.4, u'sum_x_squared': 8.718957252868305e+18, u'N': 1.0}]], u'row_partition_model': {u'counts': [1, 1], u'hypers': {u'alpha': 2.0}}, u'column_names': [u'c']}]}

Here's an example with 10 values:
bdb.sql_execute('INSERT INTO D (c) VALUES (32003.9998936), (32004.0002834), (32003.999974), (32003.9998355), (32004.0003761), (32003.9997346), (32003.9999356), (32004.0003391), (32004.0002069), (32003.999385)')

I think these multi-value examples reflect a different bug, though.   I think crosscat is having a hard time with the fact that the variance is so low relative to the mean.  Probably some kind of pre-analysis massaging is in order (e.g, zeroing the mean.)

Although, here's an example of a failure case with mean / variance < 1e5:

I think that must be a break down in the prior.  Again, zeroing the mean would likely help, here.

We could probably do better by using Welford's algorithm for incrementally computing normal sufficient statistics, which stores the mean and n*var instead of the sum and the sum of squares or similar.  This would require figuring out the changes to the math in the continuous component model, its sufficient statistics, and the updates to the hyperparameters.
I'm not sure it's the right thing -- I haven't looked closely enough to be sure what goes wrong in update_continuous_hypers in all cases -- but it is a plausible place to investigate.  We have code in bayeslite to compute Welford's algorithm, in src/stats.py.

https://github.com/probcomp/bayeslite/commit/d2376c134942f40b3305cdf972be708e7404f25a


Allow configuration by an URL

Allows you to configure the Influx client with an URL, eg:
InfluxDB::Client.new url: "tls://user:pass@myhost/mydb"

I like the idea, because it enables the configuration to be a single environment variable.
However, I find the merge_url method a bit too magical (for the lack of a better word). It mutates its argument, which I don't expect from Ruby methods (it's technically not an error, but unexpected).
How about something like this?
def initialize(opts = {})
  if opts.key?(:url)
    opts.merge! options_from_url URL.parse opts[:url]
  end
  # ...
end

def options_from_url(url)
  {}.tap do |opts|
    opts[:host] = url.host
    opts[:port] = url.port if url.port
    # etc.
  end
end

This makes #options_from_url easier to test as well (speaking of... do you mind adding a context block to spec/influxdb/config_spec.rb?)

On another note, InfluxDB only speaks HTTP(S) and UDP, so I'd prefer the URI scheme to reflect that (i.e. %w[http https upd].include?(uri.scheme)).
Another addition could be a mapping of the client options to URI query parameters, for example:
cli = InfluxDB::Client.new url: "https://localhost:8083/foodb?denormalize=true"
# instead of
# InfluxDB::Client.new url: "https://localhost:8083/foodb", denormalize: true

thus enabling all configuration to be made with a single environment variable.
This might be out of scope for this PR, though. Feel free to leave this part out :-)

No, thank you for the feedback! Will work on it next week.
On May 28, 2017 22:37, "Dominik Menke"<EMAIL_ADDRESS>wrote:

On another note, InfluxDB only speaks HTTP(S) and UDP, so I'd prefer the
URI scheme to reflect that (i.e. %w[http https upd].include?(uri.scheme)).
Another addition could be a mapping of the client options to URI query
parameters, for example:
cli = InfluxDB::Client.new url: "https://localhost:8083/foodb?denormalize=true"# instead of# InfluxDB::Client.new url: "https://localhost:8083/foodb", denormalize: true
thus enabling all configuration to be made with a single environment
variable.
This might be out of scope for this PR, though. Feel free to leave this
part out :-)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/influxdata/influxdb-ruby/pull/188#issuecomment-304538637,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAK_Ti2amqIjWAtV8aFxEHSpIzLyKbyCks5r-dsWgaJpZM4NhTbv
.

It has been a while. Are you still working on this?

I can, sorry, other things came in between ..
On Jun 28, 2017 08:09, "Dominik Menke"<EMAIL_ADDRESS>wrote:

It has been a while. Are you still working on this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/influxdata/influxdb-ruby/pull/188#issuecomment-311565683,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAK_Tqet0SkV99cPyJTbyPfFl3jOv0phks5sIe4jgaJpZM4NhTbv
.

thus enabling all configuration to be made with a single environment variable

I have implemented this now, and... well... Let's say the Config class needed some major refactoring :-)
Closing this now. A release of 0.4.0 follows tomorrow, I think.


Terraform apply never completes

I'm attempting to deploy the template in main.tf.txt to my Proxmox server. The VM is created with the correct settings in cloud-init, but terraform apply never completes. It just says Still creating... for 8+ minutes. Is there something I'm doing wrong?
Variables are defined in vars.tf.txt

Hi, @PopeFelix,
I ran a test using your tf files, modifying some variables such as storage name and template name, and it was successful. I found no issues with those files.
The target ProxmoxVE version is 8.1.4.
proxmox_vm_qemu.cloudinit-test: Creation complete after 5m55s [id=gemini/qemu/16000326]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

Have you checked the task status on PVE? Also, it might be helpful to check the Cloud-Init status in the VM's console.

How do I check the task status on PVE?

This might be probitive:
proxmox_vm_qemu.cloudinit-test: Creation complete after 20m29s [id=thebeast/qemu/101]

│ Warning: Qemu Guest Agent is enabled but not working
│
│   with proxmox_vm_qemu.cloudinit-test,
│   on main.tf line 22, in resource "proxmox_vm_qemu" "cloudinit-test":
│   22: resource "proxmox_vm_qemu" "cloudinit-test" {
│
│ error from PVE: "500 QEMU guest agent is not running"
│ , Qemu Guest Agent is enabled in you configuration but non installed/not working on your vm

I'll check that out. Maybe the QEMU guest agent isn't installed on the Ubuntu image.

Yeah, that must be it. This is cloned from the current (as of 2024-07-10) Ubuntu 24.04 Cloud Image, and when I disable the agent = 1 line, VM creation completes in under 30s. So I need to update my Terraform template to install qemu-guest-agent on VM creation.


Cellular call interrupts VoIP call

Hi,
Its known issue that if Voip call is in progress and phone receives a normal cellular call then Voip call is sent to background and after call is disconencted VoIP call is retrievd and is still in progress but media is lost. Can you please check it

Hi,
Any Update on this thread

+1


feat: subgroup G1/G2 membership BW6-761 and BLS12-377

Description

This PR adds G1 and G2 subgroup memberships for BW6-761. It's up to the user to call these circuits for example before a pairing call.
Type of change

[x] New feature (non-breaking change which adds functionality)

How has this been tested?

Added new tests for subgroup membership tests.
How has this been benchmarked?

For BLS12-377:

G1 curve membership
G2 curve membership
G1 subgroup membership
G2 subgroup membership

SCS
11
32
971
2,267

So a total of 3,280 (without separate equality checks of each sub-circuit) if we want to test all membership for e.g. before a pairing circuit.

For BW6-761:

G1 curve membership
G2 curve membership
G1 subgroup membership
G2 subgroup membership

SCS
15,412
15,390
1,210,276
1,210,276

So a total of 2,189,173 (without separate equality checks of each sub-circuit) if we want to test all membership for e.g. before a pairing circuit.
N.B.: note that for KZG verifier we (might) only need G1 membership as G2 points are fixed and corresponding lines pre-computed in the SRS.
Checklist:

[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] I did not modify files generated from templates
[x] golangci-lint does not output errors locally
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Looks good. For sw_bw6761 package we also have doc_test.go for the runnable example. Maybe we can add the group membership test there? Right now we only have a comment that we do not check the membership.

Added 👍


OCI Ampere Support

Feature Request
Support for OCI Ampere needs to be validated. Validation has to be done for:

[ ]  enforcement supported? What is the LSM used?
[ ] Audit/Observability supported
[ ] Paste the output of karmor probe

Currently having some issues deploying KubeArmor on OCI Ampere based cluster

kubectl get pods -A
NAMESPACE     NAME                                             READY   STATUS             RESTARTS      AGE
kube-system   coredns-69d7b9d5f4-6gg27                         1/1     Running            2             18h
kube-system   csi-oci-node-9h6bd                               1/1     Running            2             18h
kube-system   kube-dns-autoscaler-d8996d8b8-lq6sv              1/1     Running            2             18h
kube-system   kube-flannel-ds-v4p74                            1/1     Running            4             18h
kube-system   kube-proxy-s7r2m                                 1/1     Running            2             18h
kube-system   kubearmor-annotation-manager-7fc8d9b964-g8lhf    1/2     CrashLoopBackOff   4 (48s ago)   2m36s
kube-system   kubearmor-host-policy-manager-5644c558d8-grn7f   0/2     CrashLoopBackOff   8 (52s ago)   2m42s
kube-system   kubearmor-policy-manager-5cc6867465-7h4v5        0/2     CrashLoopBackOff   8 (62s ago)   2m42s
kube-system   kubearmor-qzxl5                                  0/1     CrashLoopBackOff   4 (4s ago)    2m44s
kube-system   kubearmor-relay-6fddb8865b-5bjhf                 1/1     Running            0             2m44s
kube-system   proxymux-client-2p4bn                            1/1     Running            2             18h

Pod logs
kubectl logs -n kube-system kubearmor-qzxl5
Defaulted container "kubearmor" out of: kubearmor, init (init)
2023-02-03 03:18:17.665419	INFO	Build Time: 2023-02-02 09:08:00.067521323 +0000 UTC
2023-02-03 03:18:17.665601	INFO	Arguments [cluster:default coverageTest:false criSocket: defaultCapabilitiesPosture:audit defaultFilePosture:audit defaultNetworkPosture:audit enableKubeArmorHostPolicy:false enableKubeArmorPolicy:true enableKubeArmorVm:false gRPC:32767 host:oke-cc2xs7urxaa-nddk6kgcxrq-snkwcxc5thq-0 hostDefaultCapabilitiesPosture:audit hostDefaultFilePosture:audit hostDefaultNetworkPosture:audit hostVisibility:default k8s:true logPath:none lsm:bpf,apparmor,selinux seLinuxProfileDir:/tmp/kubearmor.selinux visibility:process,file,network,capabilities]
2023-02-03 03:18:17.665708	INFO	Configuration [{Cluster:default Host:oke-cc2xs7urxaa-nddk6kgcxrq-snkwcxc5thq-0 GRPC:32767 LogPath:none SELinuxProfileDir:/tmp/kubearmor.selinux CRISocket: Visibility:process,file,network,capabilities HostVisibility:default Policy:true HostPolicy:true KVMAgent:false K8sEnv:true DefaultFilePosture:audit DefaultNetworkPosture:audit DefaultCapabilitiesPosture:audit HostDefaultFilePosture:audit HostDefaultNetworkPosture:audit HostDefaultCapabilitiesPosture:audit CoverageTest:false LsmOrder:[]}]
2023-02-03 03:18:17.665735	INFO	Final Configuration [{Cluster:default Host:oke-cc2xs7urxaa-nddk6kgcxrq-snkwcxc5thq-0 GRPC:32767 LogPath:none SELinuxProfileDir:/tmp/kubearmor.selinux CRISocket: Visibility:process,file,network,capabilities HostVisibility:none Policy:true HostPolicy:true KVMAgent:false K8sEnv:true DefaultFilePosture:audit DefaultNetworkPosture:audit DefaultCapabilitiesPosture:audit HostDefaultFilePosture:audit HostDefaultNetworkPosture:audit HostDefaultCapabilitiesPosture:audit CoverageTest:false LsmOrder:[bpf apparmor selinux]}]
2023-02-03 03:18:17.666470	INFO	Initialized Kubernetes client
2023-02-03 03:18:17.666517	INFO	Started to monitor node events
2023-02-03 03:18:17.666558	INFO	GlobalCfg.Host=oke-cc2xs7urxaa-nddk6kgcxrq-snkwcxc5thq-0, KUBEARMOR_NODENAME=<IP_ADDRESS>
2023-02-03 03:18:18.667393	INFO	Node Name: oke-cc2xs7urxaa-nddk6kgcxrq-snkwcxc5thq-0
2023-02-03 03:18:18.667452	INFO	Node IP: <IP_ADDRESS>
2023-02-03 03:18:18.667479	INFO	Node Annotations: map[alpha.kubernetes.io/provided-node-ip:<IP_ADDRESS> csi.volume.kubernetes.io/nodeid:{"blockvolume.csi.oraclecloud.com":"<IP_ADDRESS>","fss.csi.oraclecloud.com":"<IP_ADDRESS>"} flannel.alpha.coreos.com/backend-data:{"VNI":1,"VtepMAC":"5e:2d:86:ff:e9:81"} flannel.alpha.coreos.com/backend-type:vxlan flannel.alpha.coreos.com/kube-subnet-manager:true flannel.alpha.coreos.com/public-ip:<IP_ADDRESS> kubearmor-policy:audited kubearmor-visibility:none node.alpha.kubernetes.io/ttl:0 oci.oraclecloud.com/compartment-id:ocid1.tenancy.oc1..aaaaaaaatfk4q3erag6x5cnhdebcgyjs43rtntiiheudddb22jiovdqznfdq oci.oraclecloud.com/node-pool-id:ocid1.nodepool.oc1.ap-mumbai-1.aaaaaaaahgnlrq7w2prhfhua7daead5sxbail3wsbdphlizkknddk6kgcxrq volumes.kubernetes.io/controller-managed-attach-detach:true]
2023-02-03 03:18:18.667526	INFO	OS Image: Oracle Linux Server 8.7
2023-02-03 03:18:18.667537	INFO	Kernel Version: 5.15.0-<IP_ADDRESS>.el8uek.aarch64
2023-02-03 03:18:18.667544	INFO	Kubelet Version: v1.25.4
2023-02-03 03:18:18.667551	INFO	Container Runtime: cri-o://1.25.1-111.el8
2023-02-03 03:18:18.668051	INFO	Initialized KubeArmor Logger
2023-02-03 03:18:18.669553	INFO	Initializing eBPF system monitor
2023-02-03 03:18:18.669593	INFO	eBPF system monitor object file path: /opt/kubearmor/BPF/system_monitor.bpf.o
2023-02-03 03:18:19.862321	INFO	Initialized the eBPF system monitor
2023-02-03 03:18:21.014721	INFO	Initialized KubeArmor Monitor
2023-02-03 03:18:21.014795	INFO	Started to monitor system events
2023-02-03 03:18:21.017682	INFO	Supported LSMs: capability,yama,selinux,bpf
2023-02-03 03:18:21.638004	ERROR	opening lsm LSM(enforce_proc)#156: errno 524
github.com/kubearmor/KubeArmor/KubeArmor/log.Err
	/usr/src/KubeArmor/KubeArmor/log/logger.go:97
github.com/kubearmor/KubeArmor/KubeArmor/feeder.(*Feeder).Errf
	/usr/src/KubeArmor/KubeArmor/feeder/feeder.go:491
github.com/kubearmor/KubeArmor/KubeArmor/enforcer/bpflsm.NewBPFEnforcer
	/usr/src/KubeArmor/KubeArmor/enforcer/bpflsm/enforcer.go:94
github.com/kubearmor/KubeArmor/KubeArmor/enforcer.selectLsm
	/usr/src/KubeArmor/KubeArmor/enforcer/runtimeEnforcer.go:101
github.com/kubearmor/KubeArmor/KubeArmor/enforcer.NewRuntimeEnforcer
	/usr/src/KubeArmor/KubeArmor/enforcer/runtimeEnforcer.go:153
github.com/kubearmor/KubeArmor/KubeArmor/core.(*KubeArmorDaemon).InitRuntimeEnforcer
	/usr/src/KubeArmor/KubeArmor/core/kubeArmor.go:259
github.com/kubearmor/KubeArmor/KubeArmor/core.KubeArmor
	/usr/src/KubeArmor/KubeArmor/core/kubeArmor.go:433
main.main
	/usr/src/KubeArmor/KubeArmor/main.go:44
runtime.main
	/usr/local/go/src/runtime/proc.go:250
2023-02-03 03:18:21.638470	INFO	Error Initialising BPF-LSM Enforcer, Cleaning Up
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x11b81cc]

goroutine 1 [running]:
github.com/kubearmor/KubeArmor/KubeArmor/enforcer/bpflsm.(*BPFEnforcer).DestroyBPFEnforcer(0x40058d6080)
	/usr/src/KubeArmor/KubeArmor/enforcer/bpflsm/enforcer.go:169 +0xfc
github.com/kubearmor/KubeArmor/KubeArmor/enforcer.selectLsm(0x40058ae2a0, {0x400022be30?, 0x11344bc?, 0x40058840d0?}, {0x40058ae270?, _, _}, {_, _, _}, ...)
	/usr/src/KubeArmor/KubeArmor/enforcer/runtimeEnforcer.go:105 +0x318
github.com/kubearmor/KubeArmor/KubeArmor/enforcer.NewRuntimeEnforcer({{0x16fcc93, 0x7}, {0x400011fd40, 0x29}, {0x40004a11f0, 0xb}, 0x40003f6270, 0x40003f62a0, {0x40003a4a00, 0x16, ...}, ...}, ...)
	/usr/src/KubeArmor/KubeArmor/enforcer/runtimeEnforcer.go:153 +0x268
github.com/kubearmor/KubeArmor/KubeArmor/core.(*KubeArmorDaemon).InitRuntimeEnforcer(...)
	/usr/src/KubeArmor/KubeArmor/core/kubeArmor.go:259
github.com/kubearmor/KubeArmor/KubeArmor/core.KubeArmor()
	/usr/src/KubeArmor/KubeArmor/core/kubeArmor.go:433 +0x7cc
main.main()
	/usr/src/KubeArmor/KubeArmor/main.go:44 +0x2a8

$ kubectl logs -n kube-system kubearmor-annotation-manager-7fc8d9b964-g8lhf
Defaulted container "kube-rbac-proxy" out of: kube-rbac-proxy, manager
I0203 03:15:52.857202       1 main.go:190] Valid token audiences:
I0203 03:15:52.857284       1 main.go:262] Generating self signed cert as no cert is provided
I0203 03:16:07.456386       1 main.go:311] Starting TCP socket on <IP_ADDRESS>:8443
I0203 03:16:07.457371       1 main.go:318] Listening securely on <IP_ADDRESS>:8443

$ kubectl logs -n kube-system kubearmor-host-policy-manager-5644c558d8-grn7f
Defaulted container "kube-rbac-proxy" out of: kube-rbac-proxy, kubearmor-host-policy-manager
exec ./kube-rbac-proxy: exec format error

$ kubectl logs -n kube-system kubearmor-policy-manager-5cc6867465-7h4v5
Defaulted container "kube-rbac-proxy" out of: kube-rbac-proxy, kubearmor-policy-manager
exec ./kube-rbac-proxy: exec format error

Currently BPF-LSM programs are not supported for arm64 platform, therefore KubeArmor Can't support enforcement on OCI Ampere and at this point only Observability/Audit mode is supported.
Enforment Supported: No
Audit/Observability supported: Yes

karmor probe
Found KubeArmor running in Kubernetes

Daemonset :
 	kubearmor 	Desired: 1	Ready: 1	Available: 1
Deployments :
 	kubearmor-relay	Desired: 1	Ready: 1	Available: 1
Containers :
 	kubearmor-68dll                               	Running: 1	Image Version: kubearmor/kubearmor:latest
 	kubearmor-annotation-manager-7fc8d9b964-9n4qq 	Running: 2	Image Version: gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0
 	kubearmor-host-policy-manager-5644c558d8-nfrb7	Running: 2	Image Version: gcr.io/kubebuilder/kube-rbac-proxy:v0.5.0
 	kubearmor-policy-manager-5cc6867465-6xwf5     	Running: 2	Image Version: gcr.io/kubebuilder/kube-rbac-proxy:v0.5.0
 	kubearmor-relay-6fddb8865b-n8d8h              	Running: 1	Image Version: kubearmor/kubearmor-relay-server:latest
Node 1 :
 	OS Image:                 	Oracle Linux Server 8.7
 	Kernel Version:           	5.15.0-<IP_ADDRESS>.el8uek.aarch64
 	Kubelet Version:          	v1.25.4
 	Container Runtime:        	cri-o://1.25.1-111.el8
 	Active LSM:
 	Host Security:            	false
 	Container Security:       	false
 	Container Default Posture:	audit(File)                   	audit(Capabilities)	audit(Network)
 	Host Default Posture:     	audit(File)                   	audit(Capabilities)	audit(Network)

KubeArmor Telemetry
kubectl exec -it -n wordpress-mysql   wordpress-787f45786f-hzfp4 -- bash
root@wordpress-787f45786f-hzfp4:/var/www/html# ls
index.php    readme.html      wp-admin            wp-comments-post.php  wp-config.php  wp-cron.php  wp-links-opml.php  wp-login.php  wp-settings.php  wp-trackback.php
license.txt  wp-activate.php  wp-blog-header.php  wp-config-sample.php  wp-content     wp-includes  wp-load.php        wp-mail.php   wp-signup.php    xmlrpc.php

karmor log --logFilter system --operation process                                                                                [918/918]
local port to be used for port forwarding kubearmor-relay-6fddb8865b-n8d8h: 32767
== Log / 2023-02-08 11:11:55.677353 ==
ClusterName: default
HostName: oke-cc2xs7urxaa-nddk6kgcxrq-snkwcxc5thq-1
Labels: app=wordpress
ContainerName: wordpress
ContainerID: bcf855aa4e263220ec0a88215126386b38c1fee6d1f4ae0b4b1af42c3b4cd342
ContainerImage: docker.io/library/wordpress:4.8-apache@sha256:6216f64ab88fc51d311e38c7f69ca3f9aaba621492b4f1fa93ddf63093768845
Type: ContainerLog
Source: /bin/bash
Resource: /bin/tar xf -
Operation: Process
Data: syscall=SYS_EXECVE
Result: Passed
HostPID: 2.720645e+06
HostPPID: 2.720623e+06
PID: 8
PPID: 1
ParentProcessName: /bin/bash
ProcessName: /bin/tar

Handled and updated the support matrix.

Oracle kernel team member has provided a response for the possible issue here. Quoting it verbatim:
On 7/27/23, 4:34 AM, "Alan Maguire" <[xxxx@xxxxx](mailto:xxxx@xxxx)> wrote:

hi folks

the background here is that the aarch64 platform until very recently
did not support the BPF trampoline, which is the basis for BPF tracing
programs, fentry, fexit and fmodify_return. The latter two in particular
are used in BPF LSM. We have a long-standing bug to backport this
functionality to UEK7 once it lands upstream:

Bug 34405795 - [UEK-7-U1] bpf: backport arm64 trampoline support from
upstream

This would benefit BPF tracing also. Support upstream is very fresh; the
patches landed within the last few months.

The challenge with this backport is that we end up bringing in a lot of
other pieces, but last time I did a proof-of-concept on the in-progress
patches it did seem tractable.

However, as a first step, I wonder if it would be feasible to get our
partners to check if a LUCI-based kernel resolves the issues they
currently face? This would help ensure that the blocking issues are
resolved by arm64 BPF trampoline support. I will also start looking into
any other potential missing pieces as I haven't explored BPF LSM much yet.

Thanks!

Alan


Enable SSE4 support on Windows

OpenEXR currently uses the macro "SSE4_1" to determine whether to enable SSE4.1 support, for example in:
https://github.com/AcademySoftwareFoundation/openexr/blob/main/src/lib/OpenEXR/ImfSimd.h
Unfortunately it looks like this macro is not defined by Visual Studio and the function __cpuid() should be used instead:
https://docs.microsoft.com/en-us/cpp/intrinsics/cpuid-cpuidex?view=msvc-170
This PR adds a CMake test using __cpuid() to determine if SSE4.1 support can be enabled on Windows.

Drat, I think I made a mess of the Git history on this trying to add the DCOs. I'll create a clean branch and new PR...


After crash theres zero notifications

A guy tried running another spammer simultaneously, the dtlg spammer stopped working, no error, nothing in logs, just stopped...

Can't reproduce without more details.


[FEATURE]: Basic feature card in tailwindcss

Description
Need to create code for Basic feature card  as per below image.

The final code should be placed under path tailwind_components/feature_cards with file name as basic_card.jsx
The file as to be imported to tailwind_components/feature_cards/collection.js file as per example and added to the featureCardColletion list
Post these process, go to components tab (components/feature_cards) in website and check whether the codepen is updated

For PR reference - https://github.com/jsvigneshkanna/tailwind_ui_components/pull/76/files
For any issue while creating / importing the component code file, check below sample files
https://github.com/jsvigneshkanna/tailwind_ui_components/tree/master/tailwind_components/buttons
For icons please refer - https://heroicons.com/
Screenshot of the tailwind component

Are you taking this fetaure implementaion
no

@jsvigneshkanna   assign me

@iamkennis  Sure, also check other issues

Hi @iamkennis , let me know if help needed

@jsvigneshkanna  sorry i was cut up with other things, I will make some PR soon

@iamkennis take your time


while I use @Autowired In CommandLineRunner To inject  dubb proxy .  spring could not found the beanDefinition

DemoService  is a dubbo proxy 。
expected： inject and worked fine
actually:  Field demoService in XXX.ConsumerCommandLineRunner required a bean of type 'XXX.api.DemoService' that could not be found.
code is here
@Component
@Slf4j
public class ConsumerCommandLineRunner implements CommandLineRunner {

    @Autowired
    private DemoService demoService;

    @Override
    public void run(String... args) throws Exception {
        log.info(demoService.sayHello("world"));

        log.info("☺");
    }
}

only use this  it  cloud work
    @Reference
    private DemoService demoService;

Please add  Dubbo 2.6.5  in order to override indirectly dependencies:
<dependency>
    <groupId>com.alibaba.boot</groupId>
    <artifactId>dubbo-spring-boot-starter</artifactId>
    <version>0.2.0</version>
</dependency>

<!-- Dubbo -->
<dependency>
    <groupId>com.alibaba</groupId>
    <artifactId>dubbo</artifactId>
    <version>2.6.5</version>
</dependency>
<!-- Spring Context Extras -->
<dependency>
    <groupId>com.alibaba.spring</groupId>
    <artifactId>spring-context-support</artifactId>
    <version>1.0.2</version>
</dependency>

There was a legacy issue in Dubbo.


not working while using live server

When it comes to check for documented view while creating html objects, it's not calls the css and js files.!
unable to connect files within a folder.
it's accruing since 20 days.

/causedByExtension
If css/scripts are not loaded in browser - report this problem in Live Server extension repo.
If there is some editor functionality (not related to dev/live server) that is broken - provide more details.

/causedByExtension
If css/scripts are not loaded in browser - report this problem in Live Server extension repo.
If there is some editor functionality (not related to dev/live server) that is broken - provide more details.


AJAX Content-Type Handling.

When sending data using the AJAX methods the existing code attempts to serialise the data using its own rules which do not match the XHR serialisation rules.  For my use notably it doesn't automatically handle XML Document objects which XHR does.  I'm not sure why the decision was made to make 'application/x-www-form-urlencoded' the default content type, and while the serialisation code is helpful I feel it should be opt in rather than the default behaviour.
Additionally, when checking to see if the user has supplied a 'Content-Type' header to override the default behaviour it only does a case-sensitive check despite the fact that HTTP headers are case insensitive.  It should instead either normalise user provided headers, or else do case insensitive checks for relevant headers, or else it should be clearly documented that it will interrogate specific headers in a case insensitive fashion.  See: https://github.com/ReactiveX/rxjs/blob/7bb8280181bf1d5b0a2d3338ede8bea5e30f64c7/src/observable/dom/AjaxObservable.ts#L201-L211
At the very least clearly documenting the default serialisation behaviour and how to use 'Content-Type' to override the default behaviour is required.

Is there a reason why we can't let browser detect it automatically ? That's what axios does at the moment.
At least when uploading FormData data of Content-Type multipart/form-data, browser would automatically write the type and boundaries.


Relax the conditions for stable-compatibility

Specifically, with respect to this passage in this document:

The stable-compatible relation is quite conservative. In the future, it may be relaxed to accommodate a change in field mutability and/or abandoning fields from  (but with a warning).

^ I think abandoning fields would be helpful even without changing field mutability, as it would allow the programmer to add a new field, migrate data from the old field to the new field in a pre-upgrade or post-upgrade hook, and then abandon the new field.

This is implemented now.


Hillas intersection (algorithm 1)

Simple Hillas axis intersection code, based on the implementation of read_hess. This code was created as a comparison the the HillasReconstructor.py code to check that the two approaches are functionally identical.

seems to be a problem with imports in the test:
ctapipe/reco/tests/test_hillas_intersection.py:1: in <module>
    from ctapipe.reco.hillas_intersection import intersect_lines
E   ImportError: cannot import name 'intersect_lines'

We can refactor this to have a common interface with the other reconstructors separately (see #471), so for now I'll merge it


Add LogFilePath parameter

Just added LogFilePath parameter for any WinEvent log to allow for alternate log file location scenarios.
Original Pester test has been updated, together with README as per contribution guidelines.

Hi @leshkinski, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@leshkinski, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

Thank you for your contribution @leshkinski , looks good!


Docker swarm example with config

Hi,
I wanted to check the performance with the docker compose example, but it misses the configuration file.
Can you provide a full example with config and compose?

Hey @bgervan, of course! Let's take an example where I have 1 docker service exposed through swarm or through just a docker compose up setup:
If you are only using docker, you probably don't even need the config file -- just labels and environment variables.
TL;DR:

If you are running docker compose up, labels are at the same level or ports/image etc
If you are running swarm mode, update to PROKSI_DOCKER__MODE: "swarm" and move the labels to be inside the deploy: key.

Docker compose
The important piece here is that via docker compose your container labels are not part of the deploy: key, so you have to put the labels in the same level as image/ports etc:
networks:
  public:
    name: public
    external: true

 # Proksi
 proksi:
    image: luizfonseca/proksi:latest
    environment:
      PROKSI_LOGGING__LEVEL: "info" # change to `debug` if you want more logging
      PROKSI_WORKER_THREADS: 4 # this only applies for the :443 port

      # Docker
      PROKSI_DOCKER__ENABLED: "true"
      PROKSI_DOCKER__MODE: "compose"

      # Lets Encrypt
      PROKSI_LETS_ENCRYPT__ENABLED: "true"
      PROKSI_LETS_ENCRYPT__STAGING: "true" # If you want real certs, change to "false"
      PROKSI_LETS_ENCRYPT__EMAIL<EMAIL_ADDRESS>      PROKSI_PATHS__LETS_ENCRYPT: "/app/data/letsencrypt" # volume for your certs
    ports:
      - "80:80"
      - "443:443"
    volumes:
      # before: create this folder `data` with `mkdir ./data` (or any other folder)
      - ./data/letsencrypt:/app/data/letsencrypt # this is important, we save certs here
      - /var/run/docker.sock:/var/run/docker.sock # how we get containers
    networks:
      - public

  # Example webserver
  nginx-demo:
    image: nginxdemos/hello

    networks:
      - public
    labels:
      proksi.enabled: "true"
      proksi.host: "nginx-demo.localhost" # update your /etc/hosts if possible
      proksi.port: "80"

      # IMPORTANT: if you don't actually have a real domain, use this to get LOCAL certs.
      proksi.ssl_certificate.self_signed_on_failure: "true"

      # Optional path matching
      # proksi.match_with.path.pattern.any: "/*"
    deploy:
      replicas: 2 # Proksi will automatically load-balance between replicas

Docker swarm
Simply move the labels: piece inside the deploy: key, like so:
  # Example webserver
  nginx-demo:
    image: nginxdemos/hello

    networks:
      - public

    deploy:
      replicas: 2 # Proksi will automatically load-balance between replicas
      labels:
        proksi.enabled: "true"
        proksi.host: "nginx-demo.localhost" # update your /etc/hosts if possible
        proksi.port: "80"

        # IMPORTANT: if you don't actually have a real domain, use this to get LOCAL certs.
        proksi.ssl_certificate.self_signed_on_failure: "true"

and change the environment variable on proksi: to be PROKSI_DOCKER__MODE: "swarm". The rest stays the same.

Btw, if you are running on a mac, it's unlikely you will get good performance because the Unix environment is virtualized, but you should get around 30K~60K req/s give or take.
If you are testing on a linux host, then you should get a close result around 80~100K req/s and upwards (depending on what you are running of course)

Thanks for the quick reply.
Modified a bit, the compose mode doesn't exist.
networks:
  web:
    name: web
    # external: true

services:
  # Proksi
  proksi:
    image: luizfonseca/proksi:latest
    logging:
      driver: none
    environment:
      PROKSI_LOGGING__LEVEL: "INFO" # change to `debug` if you want more logging
      PROKSI_LOGGING__ACCESS_LOGS_ENABLED: "false"
      PROKSI_WORKER_THREADS: 4 # this only applies for the :443 port

      # Docker
      PROKSI_DOCKER__ENABLED: "true"
      PROKSI_DOCKER__MODE: "container"

      # Lets Encrypt
      PROKSI_LETS_ENCRYPT__ENABLED: "true"
      PROKSI_LETS_ENCRYPT__STAGING: "true" # If you want real certs, change to "false"
      PROKSI_LETS_ENCRYPT__EMAIL<EMAIL_ADDRESS>      PROKSI_PATHS__LETS_ENCRYPT: "/app/data/letsencrypt" # volume for your certs
    ports:
      - "80:80"
      - "443:443"
    volumes:
      # before: create this folder `data` with `mkdir ./data` (or any other folder)
      - ./data/letsencrypt:/app/data/letsencrypt # this is important, we save certs here
      - /var/run/docker.sock:/var/run/docker.sock # how we get container info
    networks:
      - web

  # Example webserver
  nginx-demo:
    image: nginxdemos/hello

    networks:
      - web
    labels:
      proksi.enabled: "true"
      proksi.host: "nginx-demo.localhost" # update your /etc/hosts if possible
      proksi.port: "80"

      # IMPORTANT: if you don't actually have a real domain, use this to get LOCAL certs.
      proksi.ssl_certificate.self_signed_on_failure: "true"

      # Optional path matching
      # proksi.match_with.path.pattern.any: "/*"
    deploy:
      replicas: 2 # Proksi will automatically load-balance between replicas

If I disable logging, I got 10-12K/s, which is great, considering I got 6-8K with traefik and nginx on the same VPS.
docker compose up --attach nginx-demo
Tried to disable access logs, but PROKSI_LOGGING__ACCESS_LOGS_ENABLED: "false" doesn't seem to work and the logs affect the result heavily. (7k/s)

Ah @bgervan, good point about the mode -- 😓  (updated the example just in case someone else copies it)
Yeah, I've been running it for a while on a VPS and I'm monitoring these specifically (and thus optimizing them)

Logging: seems that even though it's in another thread, it's blocking others threads more than it should
Connection pool: Pingora doesn't evict old connections memory blocks so long-running processes tend to get memory-hungry (slowly but yeah)

So you will see some updates soon while I get more data.

I think I haven't added support for disabling the logs yet, but I will do that tonight 👍🏽

@bgervan In version 0.2.13 you will be able to pass PROKSI_LOGGING__ENABLED: false to disable all logging (it will no-op)
See https://github.com/luizfonseca/proksi/pull/36

Hey @bgervan I will close this one since I've answered the main question it but feel free to reopen if you have any feedback or more questions. 🙇🏽
Logging wise, I will be monitoring closing the performance for now.


Invite encryptionKeys should be required

Description
We always need an auth core encryption key for invites, so the encryptionKeys property should be required.
Tasks

[ ]

No as simple as first appears due to not having required messages in ts-proto. Made a start in #223 but needs more work, to be assigned to someone in sprint 5


fix: Load favicon.png instead of favicon.ico

A minor fix, but the favicon is currently not displayed, as it is incorrectly autoloaded (favicon.ico instead of favicon.png).

Thanks Sean!


Client-side Threats

Compromised client machine

Added details regarding the importance of certificate transparency and private key management for users utilizing our services. It is crucial for users to be vigilant and cautious with their sensitive information.
Added comprehensive instructions for users to ensure the safety of their data and workstation.
Furthermore, proposed network security precautions to reinforce the overall security of our services.


[SKPR-551]: Restore the latest backup.

Is there anything else we need to do here, or can we merge?

LGTM!


net/http/httputil: Reverse Proxy X-Forwarded-For include Port

In the reverse proxy the port is not being added to the header X-Forwarded-For. The port is not a requirement but optional. From RFC 7329
If the server receiving proxied requests requires some
   address-based functionality, this parameter MAY instead contain an IP
   address (and, potentially, a port number).

As the port currently isn't being included by default, and it is something I need, I am explicitly setting the header. The result is I end up with X-Forwarded-For: 123.34.567.89:9876, 123.34.567.89. It would be great to either add an option to include the ports or do a check that the value about to be added doesn't already exist in the string (duplicate without the port).
https://github.com/golang/go/blob/3089d189569ed272eaf2bc6c4330e848a46e9999/src/net/http/httputil/reverseproxy.go#L249-L257

Sure, we could add a bool on ReverseProxy for including the port. Or maybe make it an new enum type where zero value means current behavior but let people turn it off, on explicitly (despite it being the default), or on with port.
But the behavior you mention of dup-suppressing by matching on the IP with any port is also fine to do by default without knobs. Or maybe it wouldn't matter with the previous knob, actually.

Acc to https://golang.org/pkg/net/http/#Request,  server sets `RemoteAddr` to an "IP:port" then It should have been concatenated with the final `X-Forwarded-For` in above snippet.

The functionality to include a port number is specified in RFC 7329, which defines the Forwarded header, not the non-standard X-Forwarded-For header.
I still stand by that a better option is to support the Forwarded header and add the port to it rather than debate the merits and update implementation for a header that has no rules.

How does the support for Forwarded header relate to backward compatibility?
I think backward compatibility is missing in the linked patch. The X-Forwarded-For is still a de-facto standard.
After the backward compatibility is in place, even this issue could be easily solved, e.g. a boolean to forward client port could apply to either of the header fields.
ps I'm looking for a way to make first contribution.


Orientation: Landscape, Rendering behaviour

I want to achieve this kind of effect:

However, when generating the output, the right side of the site gets pushed within the correct format, I guess:

I don't think, that this might be a bug. But might it be possible to render objects that reach above the correct format on all sides of the pdf?

hmm, could you please try to implement that layout with PageOverlay ?

yes, but the overlay will apply to the section's page, you could have multiple sections to limit the PageOverlay.
I'll create a feature request for a page-specific PageOverlay component

I think it is related to page size, could you use a custom page size? something like
<Section
    margin={pageMargin.None}
    dimension={{height: '296.7mm', width: '209.7mm'}}
    orientation={"landscape"}
>

can you decrease the height and width by 1 mm in each try and test? I believe the issue is happening with different page sizes in chromium with standard page sizes.

ok, thank you. so it should be a bug in the lib layout system, I'll take a look

@PejmanNik  your recent commit or ver 0.4.1 has caused few issues.
On website it looks good but when pdf is generated it creates space in bottom and affects the footer as well...
Below 2 images in bottom looks good in website.

Below 2 images in bottom from PDF file.

PDF File with issues
out.pdf
Below is the github repo link which can be used for testing purpose.
Repo Link
Sample code setup is done in codesandbox...
https://codesandbox.io/s/report-web-app-mm4l5l?file=/src/App.js

@sharathm89 it seems i overcorrected the page dimensions, will try to find something in the middle

Sure will be waiting...

ok just taught of keep the latest version...  But yes will downgrade for now


Adding SDC metric and tested

Implemented sørensendice_coefficient(SDC) metric to close #73
Due to the similarity of this metric to Jaccard score, the evaluation function is adopted from sklearn.metrics.jaccard_score. It has also already been tested.

Please remove all .ipynb_checkpoint files before a review will be started

Hi, all ipynb_checkpoints file should be deleted! :))

Yea it's the same! If we have F1 score maybe we can close it? I thought we didn't implement F1 score....

We have a domain/cluster-specific F1 score (which also includes the overall score I think) already. So I guess this can be closed


heroku  (web-scraper) api not working

will have to look into it &  update it to latest fork of anikimiapi.

fixed by adding user-agent headers in requests made through scraper.


Updated kfam & profile-controller version

@TakoB222 could you update the tag used in this PR to be v1.8.0 since the branch now is track/1.8?

@TakoB222 could you update the tag used in this PR to be v1.8.0 since the branch now is track/1.8?

Updated


test(robot): volume should not reattach after node eviction

Which issue(s) this PR fixes:

Issue longhorn/longhorn#9781
What this PR does / why we need it:
Adding a test case to reproduce https://github.com/longhorn/longhorn/issues/9781.
Special notes for your reviewer:
None
Additional documentation or context
None

@coderabbitai review


Issue: Ws url is getting strange values

Description
The sync between setting ws url and https url is not working properly. Usually there is an extra ://
Suggested Improvements
Either they should be split into two nodes. Then there is no problem anymore. Otherwise make them sync properly
Extra Information
No response

:// is removed and seems to work.


Allow referencing a particular sheet of a Google Sheet as evaluation source

Is your feature request related to a problem? Please describe.
I need to test multiple prompts with different evaluations, where evaluations:prompts have a n:1 relationship. I want to keep all evaluations in a single Google Sheet for convenience of the end-users. At the moment, when I reference a particular sheet of a Google Sheet via URL, it still grabs the first sheet.
Describe the solution you'd like
In config, if I put in a reference to the "bird" sheet of the example Google Sheets file and then run promptfoo eval, it should run tests from that particular sheet.
tests: https://docs.google.com/spreadsheets/d/1xHVjPg8nGU96FV-KXIhtD7GfvUzyy6Y1WW4kX8aLK9s/edit?gid=1649698752#gid=1649698752

Describe alternatives you've considered
I'll use separate Google Sheets and keep another Google Sheet as the table of contents - but that's very brittle.

Added in #1942


render error with box-shadow at list

the code  http://dotwe.org/vue/99ff08ce3e0ca3e53f0ad1f812472580

using HUAWEI Android 8.1  Weex Playground App

We will look into it, not sure when to solve.

Ref #1684


hpack adds Paths_foo to other-modules without adding dependency on base

hpack is adding Paths_* to the other-modules sections of executables (and tests?), but it's not adding a corresponding dependency on base.  I'm seeing build failures when trying to compile the Paths_ module.
This is using stack 1.6.3/hpack 0.20.0 with the lts-10.3 resolver.
Example package.yaml:
name:                waka
version:             <IP_ADDRESS>
license:             BSD3

executables:
  waka-exe:
    main:                Main.hs
    dependencies:
      - protolude

Corresponding Main.hs:
{-# LANGUAGE NoImplicitPrelude #-}
{-# LANGUAGE OverloadedStrings #-}
module Main where

import Protolude

main :: IO ()
main = putStrLn ("ohai" :: Text)

Generated waka.cabal:
-- This file has been generated from package.yaml by hpack version 0.20.0.
--
-- see: https://github.com/sol/hpack
--
-- hash: a31ef4f39a7af096cd34ae4690cfca80fe95969a17c6e692f71c55a8bfdad95e

name:           waka
version:        <IP_ADDRESS>
license:        BSD3
build-type:     Simple
cabal-version:  >= 1.10

executable waka-exe
  main-is: Main.hs
  build-depends:
      protolude
  other-modules:
      Paths_waka
  default-language: Haskell2010

Build errors:
$ stack build
waka-<IP_ADDRESS>: configure (exe)
Configuring waka-<IP_ADDRESS>...
waka-<IP_ADDRESS>: build (exe)
Preprocessing executable 'waka-exe' for waka-<IP_ADDRESS>..
Building executable 'waka-exe' for waka-<IP_ADDRESS>..
[2 of 2] Compiling Paths_waka       ( .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/waka-exe/autogen/Paths_waka.hs, .stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/waka-exe/waka-exe-tmp/Paths_waka.o )

/Users/josh/work/tmp/waka/.stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/waka-exe/autogen/Paths_waka.hs:10:1: error:
    Could not find module ‘Control.Exception’
    Use -v to see a list of the files searched for.
   |
10 | import qualified Control.Exception as Exception
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/Users/josh/work/tmp/waka/.stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/waka-exe/autogen/Paths_waka.hs:11:1: error:
    Could not find module ‘Data.Version’
    Use -v to see a list of the files searched for.
   |
11 | import Data.Version (Version(..))
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/Users/josh/work/tmp/waka/.stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/waka-exe/autogen/Paths_waka.hs:12:1: error:
    Could not find module ‘System.Environment’
    Use -v to see a list of the files searched for.
   |
12 | import System.Environment (getEnv)
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

/Users/josh/work/tmp/waka/.stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS>/build/waka-exe/autogen/Paths_waka.hs:13:1: error:
    Could not find module ‘Prelude’
    Use -v to see a list of the files searched for.
   |
13 | import Prelude
   | ^^^^^^^^^^^^^^

--  While building custom Setup.hs for package waka-<IP_ADDRESS> using:
      /Users/josh/.stack/setup-exe-cache/x86_64-osx/Cabal-simple_mPHDZzAJ_<IP_ADDRESS>_ghc-8.2.2 --builddir=.stack-work/dist/x86_64-osx/Cabal-<IP_ADDRESS> build exe:waka-exe --ghc-options " -ddump-hi -ddump-to-file -fdiagnostics-color=always"
    Process exited with code: ExitFailure 1

It looks like either adding a dependency on base to package.yaml or removing Paths_waka from waka.cabal fixes the problem.
It seems like if hpack is introducing a dependency on base by automatically adding Paths_waka, it should also add the dependency.

Closing in favor of #303.  Feedback and suggestions are very much welcome!


Make the remote API work as well

Is your feature request related to a problem? Please describe:
Only local API is supported, but some people like to use the remote API.
Describe the solution you'd like:
Add a remoteAccessory.js which handles the remote slides & update platform to register remote Slides

Fixed in: 730dfae98fce159167ec66288becdd1df371f5a4


Itests

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/fabric8-quickstarts-master-pullreq/266/
Test PASSed.


[MKT-217]: feat/add currency param to get the correct prices

Currency param has been added for:

Get the USD prices.
Send the currency param when creating a checkout payment.

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (0c3ff28) 65.74% compared to head (fae8126) 65.61%.

Files
Patch %
Lines

src/drive/payments/index.ts
25.00%
2 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #183      +/-   ##
==========================================
- Coverage   65.74%   65.61%   -0.13%
==========================================
  Files          39       39
  Lines        1080     1082       +2
  Branches      149      150       +1
==========================================
  Hits          710      710
- Misses        329      330       +1
- Partials       41       42       +1

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


Modeline colors don't seem to work since faces don't exist

Currently doom theme defines things like:
     ;; Custom (doom)
     `(doom-modeline-buffer-path       ((,c (:foreground ,white :bold ,bold))))
     `(doom-modeline-buffer-project    ((,c (:foreground ,fg))))
     `(doom-modeline-buffer-modified   ((,c (:foreground ,blue))))
     `(doom-modeline-buffer-major-mode ((,c (:foreground ,white :bold ,bold))))

     `(doom-modeline-highlight     ((,c (:foreground ,blue))))
     `(doom-modeline-panel         ((,c (:foreground ,black :background ,blue))))
     `(doom-modeline-bar           ((,c (:background ,blue))))
     `(doom-modeline-eldoc-bar     ((,c (:background ,yellow))))

     ;; Powerline/Spaceline
     `(spaceline-highlight-face    ((,c (:inherit doom-modeline-panel))))
     `(powerline-active1           ((,c (:inherit doom-modeline-panel))))
     `(powerline-active2           ((,c (:inherit doom-modeline-highlight))))
     `(powerline-inactive1         ((,c (:inherit mode-line-inactive))))
     `(powerline-inactive2         ((,c (:inherit mode-line-inactive))))

However, since the doom-modeline-panel (all doom-modeline-* faces) don't exist, the spaceline/powerline faces end up referencing a face that does not exist. This causes the modeline to be entirely uncolored, like:

I think the faces need to be created somewhere, as evaling the custom-theme-set-faces s-exp doesn't create them. This is also necessary since your custom modeline does not exist in an installable package, so it's not marked as a dependency for this theme.

You're right. Those faces are defined in a mode-line component I haven't published yet. I'll put up a skeleton file with the faces defined for the team being.


Map undo redo

A user should be able to undo or redo her actions on the map.
Implements Map Undo Redo

[X] Undo an action
[X] Redo an action
Currently supported actions:

[x] create
[x] update single-element (drag, resize, rotate)
[x] update multi-element

[ ] display which action was undone
[ ] display possible error (I don't know what could go wrong at this point)
[ ] documentation for frontend devs how to use undo/redo, answering questions like how multiple actions can be merged to a single undo/redo step.

Thank you for creating this issue!

Please create a PR so the diff can be shown more easily in GitHub.
Please also write in the documentation how multiple actions can be merged to a single undo/redo step etc. (or what else devs need to know about undo/redo)

@markus2330 What do you mean by merging multiple actions into a single undo/redo step?
Can you give me an example please?

E.g.: if a group is moved around that the whole group would move back on undo.
Probably nothing needs to be done specifically for undo, but one must be careful in updating the state atomically.

E.g.: if a group is moved around that the whole group would move back on undo.
Probably nothing needs to be done specifically for undo, but one must be careful in updating the state atomically.

@markus2330 Perfect, I already implemented this for the default elements on the map that Giancarlo provided 😄


Fixing loading within 1.4.10

Updated the viewer loader so that it will default to standard data instead of an undefined value.
Updated the upgrade function for meta.json so it will properly set the subType if not available.

My fault for not properly implementing the subType loading.


Update CHANGELOG for v2023.11.07 release

Please let me know of any important changes that you want to make visible by adding to the Change log.

I uploaded new versions for IJ and CLion 2023.3